July 4, 201412 yr When I try to boot up my unRaid server, it gets to a point where it just repeatedly reads "waiting for USB subsystem". I can break out of this, but the server never finishes booting. I've tried pulling the power and waiting, but it continues to do the same thing. I'm not even sure at this point how to grab the syslogs since it never finishes booting up. I've recently upgraded to the Pro license, but it was working fine for a few weeks after. It seems we had a power outage which caused the server to shutdown, which is why I am rebooting. Normally it just runs all the time. So any thoughts on how I can get back up and running?
July 4, 201412 yr I would put the unRAID USB stick into a PC/Mac and run checkdsk on it in case there has been corruption. Also check that it is showing a volume label of UNRAID - the error message suggests that a USB device with the label UNRAID cannot be found.
July 4, 201412 yr Author Check disk came back with no errors. Drive volume is "UNRAID" (without quotes)
July 4, 201412 yr Author I should mention that I had this happen once before but power cycling resolved it. That is not the case this time. I also installed 2 new drives while the servers was powered down (figured I take advantage of the downtime). I'll try removing those and see if that makes any difference.
July 4, 201412 yr Does it even start the boot process? i.e. Does the unRAID Boot menu get displayed so you can select a boot option? Just wondering if you are even getting that far - it was not clear from your original post. That would at least help determine where the message originates in case it is prior to the boot even starting. If it is prior to the unRAID boot menu it might be something relating to your Bios Boot settings.
July 4, 201412 yr Author Yes it boots I get the GUI that asks me to select Unraid or memetest86. I can select the Unraid option, then it runs through a number of things, no errors from what I can tell, but then gets to the message Waiting for USB subsystem, and just keeps repeating that message indefinately.
July 4, 201412 yr Author Well it actually booted up finally. I didn't do anything other than power down, and power back up. After about 15 times of this, it booted without the repeating USB subsystem warning. I'm glad it booted, but I don't have the warm and fuzzies about this not happening again. Anyway thanks for the help.
July 4, 201412 yr At a bit of a loss then for what could be causing that. If you cannot get any further forward then I would suggest an approach along the lines of: Copy the current contents of the USB drive to a folder on your PC/Mac Reformat the USB stick and put a 'clean' install of unRAID on it (may have tun make_bootable.bat to make it bootable). Copy the .key file from the backed up files to the /config folder on the USB drive. Check the system boots OK at this point - if it does you have a good starting point for the next stage. You could then copy back the configuration files from the backup to see if it still boots OK. If that all works then look at any progressively introducing any plugins that you may be using. I remember seeing a post a few days a go where this approach resolved a problem.
July 4, 201412 yr Well it actually booted up finally. I didn't do anything other than power down, and power back up. After about 15 times of this, it booted without the repeating USB subsystem warning. I'm glad it booted, but I don't have the warm and fuzzies about this not happening again. Anyway thanks for the help. Strongly suggest some sort of potential hardware problem. Makes one wonder if the USB drive might be on the verge of failing? It could also be something like the motherboard I guess?
July 4, 201412 yr Author Well it is older hardware, so something could be on the way out. I'll try the steps you've outlined, seems pretty easy to do. I should have a spare USB drive laying around, so if it turns out to be the USB drive, at least I'll have everything backed up and ready to move over. Again, thanks for all the help.
Archived
This topic is now archived and is closed to further replies.