networking and i/o error on vortexbox
My network connection to the vortexbox has been rather flaky this past week (everything else on the network appears to be fine, i.e. internet connection, mysqueezebox.com), so I wanted to do a complete power cycle of the system. I connected a monitor and keyboard to the vortexbox (can't shut it down remotely) and got the following error:
[39043.976795] end_request: i/o error, dev sda, sector 4755720 after I typed in my login name. The numbers at the beginning and end change but the wording is consistent. Right now the screen is filled with this error message. I hooked up the keyboard and monitor without turning off the vortexbox. Is that why I'm getting this i/o error or is this part of the networking error? Right now nothing sees the vortexbox, it had been working off and on all week. I updated it via webmin a couple of days ago and perform regular updates. Yesterday I was able to look at the network configuration and everything looked okay. Once I can get in again I can post the file if necessary.
edit: I can still navigate to my vortexbox from my other computer but none of the links work. There are other errors too:
EXT4-fs (dm-1): previous I/O error to superblock detected.
Buffer I/O error on device dm-1, logical block 0
EXT4-fs error (device dm-1) ext4_find_entry:935: inode #1570451: comm sshd: reading directory lblock 0
Thanks for your help!
Last edited by happygirl; 06-10-2012 at 11:02 AM.
Reason: additional info
Update: I shutoff the vortexbox, unplugged everything and let sit. Everything came back up online however about 30 minutes later, I had a kernel panic. I rebooted, but the strange thing is I had to select my boot device. I have an ssd for the os and a regular hard drive for storage. Somehow the regular drive was chosen as the boot drive. I have never changed this. I re-installed the kernel, and fixed the boot drive sequence. So now I will wait to see if this fixes everything. The error messages I got indicate a drive failure :'( The ssd is less than a year old so I hope not. Storage is backed up just in case the unspeakable occurs...
Sounds like root filesystem corruption. You could try booting into rescue mode and running fsck on the root logical volume to fix filesystem errors; see http://info.vortexbox.org/tiki-index.php?page=Rescue
If that fails, and you have an up-to-date backup of your media library, you could also do a clean reinstall of the VB 2.0 ISO; see http://info.vortexbox.org/tiki-index...ge=ISO+Install
Thanks for the advice. It hasn't been prompting me to boot in safe mode so I will burn a new iso give safe mode a try.