Hey guys, I hope someone can help.  I doing a new install of 4.5.1, preloaded on a USB drive bought from lime-technology.

 

I was able to run a preclear and assign drives to the array with no problems (35 hours for a 2TB!).

 

I first noticed a problem when none of my settings would seem to save between reboots.

 

I'm seeing the follow errors in the syslog:

Jan 31 07:29:58 Tower kernel: read_file: error 2 opening /boot/config/super.dat

Jan 31 07:29:58 Tower kernel: md: could not read superblock from /boot/config/super.dat

 

Then later on:

Jan 31 07:30:47 Tower kernel: usb 2-3: USB disconnect, address 2

Jan 31 07:30:47 Tower kernel: sd 8:0:0:0: [sdd] Unhandled error code

Jan 31 07:30:47 Tower kernel: sd 8:0:0:0: [sdd] Result: hostbyte=0x07 driverbyte=0x00

Jan 31 07:30:47 Tower kernel: end_request: I/O error, dev sdd, sector 109664

 

I've tried changing bios settings related to the usb with no luck.  The motherboard is a P5B Deluxe.

 

I also ran chkdsk on the usb key in windows and it reports no errors, and ran a few rounds of Memtest and didn't receive any errors.

 

I've attached the syslog.  Any suggestions?

 

Thanks

syslog.txt

I would first try a different USB port.  The errors look a lot like I'd expect it the connector was intermittent. Once the USB connection disconnects, all subsequent read or write attempts fail.

 

Jan 31 07:30:47 Tower kernel: usb 2-3: USB disconnect, address 2

Jan 31 07:30:47 Tower kernel: sd 8:0:0:0: [sdd] Unhandled error code

Jan 31 07:30:47 Tower kernel: sd 8:0:0:0: [sdd] Result: hostbyte=0x07 driverbyte=0x00

Jan 31 07:30:47 Tower kernel: end_request: I/O error, dev sdd, sector 109664

Jan 31 07:30:47 Tower kernel: sd 8:0:0:0: [sdd] Unhandled error code

Jan 31 07:30:47 Tower kernel: sd 8:0:0:0: [sdd] Result: hostbyte=0x07 driverbyte=0x00

Jan 31 07:30:47 Tower kernel: end_request: I/O error, dev sdd, sector 40

Jan 31 07:30:47 Tower kernel: Buffer I/O error on device sdd1, logical block 8

Jan 31 07:30:47 Tower kernel: lost page write due to I/O error on sdd1

Jan 31 07:30:47 Tower kernel: sd 8:0:0:0: [sdd] Unhandled error code

Jan 31 07:30:47 Tower kernel: sd 8:0:0:0: [sdd] Result: hostbyte=0x07 driverbyte=0x00

Jan 31 07:30:47 Tower kernel: end_request: I/O error, dev sdd, sector 279

Jan 31 07:30:47 Tower kernel: Buffer I/O error on device sdd1, logical block 247

Jan 31 07:30:47 Tower kernel: lost page write due to I/O error on sdd1

Changing ports doesn't seem to help.  I also have no issues with my USB keyboard.  I forgot to mention I bought the 2 usb drive deal, and both usb drives have the same issue.

 

Jan 31 08:29:50 Tower kernel: usb 2-4: USB disconnect, address 3

Jan 31 08:29:50 Tower kernel: sd 8:0:0:0: [sdc] Unhandled error code

Jan 31 08:29:50 Tower kernel: sd 8:0:0:0: [sdc] Result: hostbyte=0x07 driverbyte=0x00

Jan 31 08:29:50 Tower kernel: end_request: I/O error, dev sdc, sector 109664

 

and

 

Jan 31 08:36:04 Tower kernel: usb 2-5: USB disconnect, address 3

Jan 31 08:36:04 Tower kernel: sd 8:0:0:0: [sdc] Unhandled error code

Jan 31 08:36:04 Tower kernel: sd 8:0:0:0: [sdc] Result: hostbyte=0x07 driverbyte=0x00

Jan 31 08:36:04 Tower kernel: end_request: I/O error, dev sdc, sector 109664

 

 

Changing ports doesn't seem to help.  I also have no issues with my USB keyboard.  I forgot to mention I bought the 2 usb drive deal, and both usb drives have the same issue.

 

Jan 31 08:29:50 Tower kernel: usb 2-4: USB disconnect, address 3

Jan 31 08:29:50 Tower kernel: sd 8:0:0:0: [sdc] Unhandled error code

Jan 31 08:29:50 Tower kernel: sd 8:0:0:0: [sdc] Result: hostbyte=0x07 driverbyte=0x00

Jan 31 08:29:50 Tower kernel: end_request: I/O error, dev sdc, sector 109664

 

and

 

Jan 31 08:36:04 Tower kernel: usb 2-5: USB disconnect, address 3

Jan 31 08:36:04 Tower kernel: sd 8:0:0:0: [sdc] Unhandled error code

Jan 31 08:36:04 Tower kernel: sd 8:0:0:0: [sdc] Result: hostbyte=0x07 driverbyte=0x00

Jan 31 08:36:04 Tower kernel: end_request: I/O error, dev sdc, sector 109664

 

 

You can give one or more of the boot codes a try.  One post I found on a google search suggested adding

pci=noacpi

as a boot code to your syslinux.cfg file. It worked on his MB with a USB disconnect issue similar to yours..

 

See here for some examples of boot codes:

http://lime-technology.com/wiki/index.php?title=Boot_Codes

and here:

http://lime-technology.com/forum/index.php?topic=1676.msg11412#msg11412

I tried pci=noacpi and it still gave the same error.  I also got the same error with the other boot codes.  Any other ideas?

I tried pci=noacpi and it still gave the same error.  I also got the same error with the other boot codes.  Any other ideas?

 

It may be a good idea to check if it is (or it isn't) 4.5.1 related:

-- Download 4.5.0-final, and unzip it somewhere;

-- Move your 4.5.1 bzimage and bzroot files to a safe location;

-- Replace them with bzimage and bzroot from the 4.5.0 archive;

-- Reboot your server.  See if you still have the errors.

 

I put 4.5 on the other USB, and it gives a different error message.

 

Jan 31 21:06:51 Tower kernel: FAT: Filesystem error (dev sdd1)

Jan 31 21:06:51 Tower kernel:    invalid access to FAT (entry 0x58540041)

Jan 31 21:06:51 Tower kernel:    File system has been set read-only

 

syslog4.5.txt

I know you tried a different USB flash drive, but did you try a different USB port on the MB?

 

Also, are you using a USB HUB?

 

Joe L.

I put 4.5 on the other USB, and it gives a different error message.

 

Jan 31 21:06:51 Tower kernel: FAT: Filesystem error (dev sdd1)

Jan 31 21:06:51 Tower kernel:     invalid access to FAT (entry 0x58540041)

Jan 31 21:06:51 Tower kernel:     File system has been set read-only

 

 

 

shut down the unRAID system, unplug the drive and plug it into a windows machine.  Run a checkdisk on it and see if it finds any problems.  If it does repair it and be done. Plug the drive back into the unRAID system and see if it works!

That was with a different port from where I last had 4.5.1. 

 

I just tried 4.5 on the same port as 4.5.1 and got the same error.  It does seem to take much longer on 4.5 to get an error than it did on 4.5.1. As soon as I changed any setting on 4.5.1, it would error.  With 4.5, I am able to change multiple settings before it gives an error.

 

Jan 31 21:20:16 Tower kernel: FAT: Filesystem error (dev sdd1)

Jan 31 21:20:16 Tower kernel:    invalid access to FAT (entry 0x58540041)

Jan 31 21:20:16 Tower kernel:    File system has been set read-only

 

No, I'm not using a USB hub.

I just put 4.5 on the original flash drive I was trying, and it gives the original error message:

 

Jan 31 19:29:55 Tower kernel: usb 2-4: USB disconnect, address 3

Jan 31 19:29:55 Tower kernel: sd 8:0:0:0: [sdd] Unhandled error code

Jan 31 19:29:55 Tower kernel: sd 8:0:0:0: [sdd] Result: hostbyte=0x07 driverbyte=0x00

Jan 31 19:29:55 Tower kernel: end_request: I/O error, dev sdd, sector 217568

 

Are there any USB related settings in the BIOS you could play with?

 

Or maybe check for a newer bios available?

 

 

 

Are there any USB related settings in the BIOS you could play with?

 

Or maybe check for a newer bios available?

 

I'll post a list of the usb bios options I have tonight.  I'm stuck in the office all day.

 

I upgraded to the newest bios before trying unraid.  I've been considering downgrading the bios to where I was before to see if that helps.  I'm on the newest (1238) right now, and I was on 1004 previously when this mobo ran windows.  Attached is the bios changelog from Asus's site - I don't see anything that would be related to this.  Also, I didn't notice this when I upgraded, but everything after 1101 is listed as Beta on their site.

 

p5b_bios_changelog.txt

Three things to try.

 

Try enabling "Legacy USB Support" in the bios.

Try setting the USB mode to Full speed rather than High speed. (It will use slower speed access to the flash drive and take a lot longer to load, but it might get rid of the disconnects.)

Try loading a different brand/model of flash drive with unRAID.  (you won't be able to assign all your drives if you have more than 3, but you see if the disconnects go away)

 

Joe L.

Three things to try.

 

Try enabling "Legacy USB Support" in the bios.

Try setting the USB mode to Full speed rather than High speed. (It will use slower speed access to the flash drive and take a lot longer to load, but it might get rid of the disconnects.)

Try loading a different brand/model of flash drive with unRAID.  (you won't be able to assign all your drives if you have more than 3, but you see if the disconnects go away)

 

Joe L.

 

I tried the Full Speed option yesterday, but did not change the Legacy settings - I'll try that tonight.  I requisitioned a USB drive from work that I'll try tonight also.

 

Thanks for all the help.

Try loading a different brand/model of flash drive with unRAID.  (you won't be able to assign all your drives if you have more than 3, but you see if the disconnects go away)

 

Joe L.

 

It looks like it was the flash drives.  I've been up and running for nearly 2 hours now with no errors on a no-name 1GB flash drive.  It shows up as "USB Mass Storage" in unraid, and the vendor ID/product ID identifies it as an Alcor Micro Corp drive.  I guess my motherboard doesn't like the 2GB Lexar Jumpdrive for some reason.

 

I've been able to change settings, copy about 80 gigs of data to the array (no parity drive assigned yet), and start/stop the array multiple times with no issues.  The syslog is attached if anyone wants to check it out. 

 

Thanks for all the help.

 

syslog.txt

It looks like it was the flash drives.  I've been up and running for nearly 2 hours now with no errors on a no-name 1GB flash drive.  It shows up as "USB Mass Storage" in unraid, and the vendor ID/product ID identifies it as an Alcor Micro Corp drive.  I guess my motherboard doesn't like the 2GB Lexar Jumpdrive for some reason.

 

I've been able to change settings, copy about 80 gigs of data to the array (no parity drive assigned yet), and start/stop the array multiple times with no issues.  The syslog is attached if anyone wants to check it out. 

 

Thanks for all the help.

 

 

 

Did you try running a chdk on the old flash drive?  I have had problems were the flash drive "goes bad" in certain areas and the chdk scans and fixes those problems.  Try doing that to the old drive and see if it will start working again.

Did you try running a chdk on the old flash drive?  I have had problems were the flash drive "goes bad" in certain areas and the chdk scans and fixes those problems.  Try doing that to the old drive and see if it will start working again.

 

Yes, I ran chkdsk on both the drives and it reported no errors.  These were brand new flash drives straight from limetech that never worked.

Did you try running a chdk on the old flash drive?  I have had problems were the flash drive "goes bad" in certain areas and the chdk scans and fixes those problems.  Try doing that to the old drive and see if it will start working again.

 

Yes, I ran chkdsk on both the drives and it reported no errors.  These were brand new flash drives straight from limetech that never worked.

I'm reasonably sure they work, but not on your motherboard's USB ports.  I'd almost suggest you try a USB HUB if you have one around... In any case, an e-mail to lime-tech is in order.

I'm reasonably sure they work, but not on your motherboard's USB ports.   I'd almost suggest you try a USB HUB if you have one around... In any case, an e-mail to lime-tech is in order.

 

I agree, I should have said they didn't work with the Asus P5B Deluxe.  They worked fine when they were plugged into my Windows machine.  I do have a usb hub I can try.

 

I'm not entirely confident in this flash drive I'm using now - it was warm after being plugged in all night and I'm afraid of it going the way of the SuperTalent Pico.  I plan on picking up a couple flash drives on the recommended list and testing them.  I'll email lime-tech once I'm more confident my setup is solid, since I'll need to sort out my licensing.

 

I'm running a parity check now and all seems to be going fine.

The Lexar Jumpdrive seemed to run ok (but very slow) on a hub.  Unraid listed the hub's GUID instead of the flash drive, so my license showed as invalid.  But, when I rebooted, the system hung.  I put the flash drive in my windows machine and it showed up as unformatted.  I received an error trying to format it through windows, but was able to format it with the HP formatting tool.  Plugging it into the unraid box again immediately seems to corrupt files on the flash drive.  I'm giving up on the Lexar - it doesn't like my setup.

 

The good news: I bought 2 SanDisk Cruzer Micro flash drives, and they both run fine.  I'll be emailing lime-tech shortly.

 

Thanks again for all the help.