I had a power cut today, when I arrived home the wife said the there was a problem, I tried to access the tower via web interface but couldn't, I then used putty to reboot which usually works fine however I now have "Buffer I/O error on device md3" and do not know how to proceed, any help is much appreciated.

 

I have attached the syslog.

 

Thanks.

 

syslog.txt

See this: http://lime-technology.com/wiki/index.php?title=Check_Disk_Filesystems

Thanks but the tower will not start to enable me to do these checks, the tower will not boot and 2 keyboard lights are flashing on and off.

 

Is there anyway of bypassing the error and then running reiserfsck.

 

Would disconnecting disk 3 allow the system to boot up?

 

Regards.

I have tried disconnecting disk3 this has made no difference, I get the following on the display

 

VFS cannot open root device on null or unknown block

please append a correct root

kernal panic - not syncing

Run check disk on the flash drive in a PC.

Thanks dgaschk, Check disk found no errors?, is there anything else I can do?

 

Regards

Run a memory test. Preferably overnight

Joe, run the memory test for 18 hours and there are no errors. and it still will not boot.

 

Regards

Try to boot with a different flash using the free version.

Yes that worked, am I ok assigning the correct parity, disk 1 and 2 for now?, I guess the problem now is knowing which file to replace on the old usb stick or do I transfer the reg code over this stick?

 

Thanks alot.

Reformat and install unRAID the original Flash drive. Your key will only work on the original flash drive.

Thanks dgaschk & Joe L it is working again now, Thanks for taking the time to help me, I appreciate it.

 

Regards Gary.

so a format (on windows) and reinstall was all you did to fix it?

 

I am running a brand new mobo/cpu/memory combo, memtest works fine, yet I get that error very randomly... I've tried different combinations and once I DO get it to boot, it only boots once, the second time doesn't boot.... very weird, I'm HOPING it's not the motherboard