Ran a parity sync over night, and when I checked the syslog this evening, I saw several lines reading:

Tower kernel: FAT-fs (sdi1): Directory bread(block 32768) failed

This is using 6.0 beta 3.

 

It looks like the USB with the unraid software got disconnected and did not get remounted. I'm wondering what I should do to remount the drive so it can save the array configuration, since it took a day to do a complete parity sync. Additionally, is there anything in my syslog that points to the cause of the disconnect? Could it be a bad flash drive?

 

I've been spending several days trying to get my new unraid server going, and this is just the latest hurdle to conquer. Thanks for any assistance!

 

UPDATE 3/26/2014

Not sure what the root cause is, but my workaround for now is to manually remount the flash to /boot when this occurs:

mount -o noatime,nodiratime,umask=0,shortname=mixed -t vfat /dev/sdX# /boot

I had to run fsck on the flash to clear the dirty bit, but otherwise, all seems good with the flash.

 

Just in case anyone else stumbles upon this through Google, I'm using a new ASRock C2550D4I motherboard with the 1.40 BIOS. No USB devices other than the flash drive are connected. There may still be bugs with this board's firmware, or the USB driver. It did not seem to make a difference when I used a different USB port.

unraid_syslog_disconnected_boot_flash.txt

I am getting the same issue on Beta9, did you find what was causing it?

Nope, I never found a root cause. I ended up getting a USB 3.0 card (from Anker I think - 2 port PCIe one) that seems to work much better than the onboard USB 2.0. I have my boot flash connected to that card and I haven't had the problem since. You might give it a shot if you have a spare PCIe slot; adapter cards are pretty cheap.