Anyone else seen this problem?  My 512MB Cruzer Micro is able to boot into Linux, but once there the boot drive is gone, so it doesn't load network.cfg or ident.cfg or any of the rest of my config.  If I watch the startup, I see a bunch of "Unable to enumerate USB device on port 3".  Moving it to a different machine gets me an identical result.

 

If I plug the drive into Windows, I can read and write from it just fine.  Is this drive just dying?  I have another Cruzer Micro in a different Unraid that will only work if I set the USB speed in the BIOS to Full instead of High.  Are these USB drives just crap?

 

What does one do if their Unraid flash drive becomes unusable?

Anyone else seen this problem?  My 512MB Cruzer Micro is able to boot into Linux, but once there the boot drive is gone, so it doesn't load network.cfg or ident.cfg or any of the rest of my config.  If I watch the startup, I see a bunch of "Unable to enumerate USB device on port 3".  Moving it to a different machine gets me an identical result.

 

If I plug the drive into Windows, I can read and write from it just fine.  Is this drive just dying?  I have another Cruzer Micro in a different Unraid that will only work if I set the USB speed in the BIOS to Full instead of High.  Are these USB drives just crap?

 

What does one do if their Unraid flash drive becomes unusable?

http://lime-technology.com/wiki/index.php/FAQ#If_my_flash_drive_dies_or_is_lost.2C_will_I_lose_my_license.3F

In a fit of genius, I decided to format and re-syslinux the drive, and now it doesn't boot at all.  If I plug it into a high-speed USB port on my Windows machine, it also doesn't work.  So, time to find a new drive, I guess.

 

In a fit of genius, I decided to format and re-syslinux the drive, and now it doesn't boot at all.  If I plug it into a high-speed USB port on my Windows machine, it also doesn't work.  So, time to find a new drive, I guess.

 

I'm assuming you used the -ma option to syslinux, and set the volume name to UNRIAD, and re-loaded the unRAID distribution files?

Funny timing with this post. Happened just this weekend to my friend's disk as well. He had the 1gb cruzer micro with the same exact issue. He had noticed it occurred from the very beginning intermittently but we chalked it up to the network card or something.

 

Finally this weekend he took his server down to add some drives and this time it refused to load correctly after 10+ attempts of rebooting. Tested the free version of Unraid on a 4gb Kingston Datatraveler 2 and it had no issues on the same machine, so Tom was nice enough to send him a new key. Worked immediately and no issues at all.

 

I just don't understand how it would intermittently work, and also how it could partially load linux/unraid but not find the "UNRAID" drive.

What does one do if their Unraid flash drive becomes unusable?

 

I've read that people would do a complete reformat from scratch and it would start working again.

Also make sure you have UNRAID as the volume label.

 

In any case, if you are having intermittent problems now, you will have them later.

I would dump it in favor of something I could trust.

]I'm assuming you used the -ma option to syslinux, and set the volume name to UNRIAD, and re-loaded the unRAID distribution files?

Yeah.  What I also did accidentally was copy over the hidden ldlinux from the old drive, which caused a problem in boot.  I fixed that and got back to the old behavior, where it would boot and then fail to recognize the drive.

 

So I found another flash drive, prepped that one for Unraid, popped it in and it boots fine, and about 1,000 times faster than the old busted drive.  So it must just have been on its last legs or something.

 

I have five (well, four now) identical Cruzer Micros in my Unraid boxes, and this is, I believe, the second one to have problems - the first one, as I mentioned before, works but only if the BIOS is set to Full Speed instead of High Speed USB.  I wonder how long before the other three bite the wax tadpole as well.

 

Funny timing with this post. Happened just this weekend to my friend's disk as well. He had the 1gb cruzer micro with the same exact issue. He had noticed it occurred from the very beginning intermittently but we chalked it up to the network card or something.

It gives me a tiny bit of comfort to know that I am not alone.