Hello all,

 

I'm trying to upgrade from 4.7 to 5.0-rc8a.  I currently have two disks in a working array on 4.7 along with a cache drive.  I have a few other drives in my server that are not currently assigned to the array.  I followed the instructions for the upgrade and unfortunately 5.0 will not finish booting.  It gets stuck in the process and repeats this error:

waiting for usb subsystem

 

I imagine something on my flash drive is causing this error.  I've reset the "go" file to the default values and have tried to clear out any unneeded files in the /boot/config folder.  However, I'm uncertain as to which files are actually needed to maintain my array and which ones I can get rid of.  In my 4.7 setup, the only add-ons I have installed include unmenu and a few packages from there to enable e-mail and screen.

 

Any ideas as to why I'm not able to successfully start 5.0?

 

Here are the contents of my /boot folder:

bootls.txt*
bzimage*
bzroot*
config/
ldlinux.sys*
license.txt*
make_bootable.bat*
memtest*
memtest-old*
menu.c32*
packages/
preclear_disk.sh*
preclear_reports/
preclear_results121001.txt*
readme.txt*
syslinux.cfg*
syslinux.exe*
ubnfilel.txt*
ubnpathl.txt*
unmenu/

 

Here are the contents of my /boot/config folder:

Plus.key*
configls.txt*
disk.cfg*
go*
go~*
ident.cfg*
network.cfg*
secrets.tdb*
share.cfg*
shares/
super.dat*

Run the new "make bootable" on the flash.

I will give this a shot later today.

 

Just to clarify, doesn't "make bootable" simply make the flash drive a bootable drive?  I know the flash drive is booting as I see the default boot loader screen, followed by unraid starting to load along with bzroot and bzimage.  The problem occurs during booting once it reaches the "waiting for usb subsystem" error that then continuously loops.

Run Chkdsk on the flashdrive.

 

What type of computer did you initially use to format your flashdrive?  There have been reports of people having difficulties with flashdrives that were formatted on apple computers. 

I used gparted in Ubuntu. I did have to rename the drive a second time as the volume drive wasn't named properly the first time.

 

What I'm not understanding is why 4.7 works completely fine on the exact same flash drive, but once I copy over bzimage and bzroot to upgrade, I get the error. 

I used gparted in Ubuntu. I did have to rename the drive a second time as the volume drive wasn't named properly the first time.

 

What I'm not understanding is why 4.7 works completely fine on the exact same flash drive, but once I copy over bzimage and bzroot to upgrade, I get the error. 

 

While I am not a real Linux expert, I believe that once the first bzimage is loaded (and it is a new file that is that was not a part of version 4.7), control is transfer to the code within bzimage which then starts the loading of the files within bzroot.  That code has to be able to read the files that are on your flashdrive. 

 

Both bzimage and bzroot contain a new version of Linux and a good portion of the old code has been replaced.  So while you might think that the new version 'only' requires the replacement of two files and most of the rest of the stuff is the really important stuff--unRAID, you are really dealing with a new operating system and a mixture of new and old unRAID code that will make up version 5.0.  The problems always lie in the details... 

 

One thing you might try is to load v5.0-rc8a onto any flashdrive that you might have laying around and see if it boots up.  That will eliminate the possibility of a hardware conflict between your system and unRAID.  If it does boot, you will know that the problem is somewhere on that old flashdrive.  At that point, we (collectively) will have to figure out what the issue is. 

I will give this a shot later today.

 

Just to clarify, doesn't "make bootable" simply make the flash drive a bootable drive?  I know the flash drive is booting as I see the default boot loader screen, followed by unraid starting to load along with bzroot and bzimage.  The problem occurs during booting once it reaches the "waiting for usb subsystem" error that then continuously loops.

 

The new "make bootable" is not the same as the old make bootable. This has previously been reported as a fix.

I tried to run the make_bootable.bat file in Windows as administrator and it copied over a new syslinux, however, the flash drive would no longer boot.  At this point I recreated the flash drive using unetbootin in ubuntu, copied over the 5.0-rc8a image and then restored my config folder.  This worked and unRaid booted up just fine.

 

One side note, I am running unRaid on a Supermicro X9SCM-F-O board with dual NICs.  First LAN is Intel 82579LM, the second is Intel 82574L.  After upgrading to 5.0, I could not get a network connection on the first LAN, had to switch to the second and the networking connections were back.  I added my drives back, started up the array and so far, so good.  More details about these NICs in this forum post.

 

Thanks to all for your suggestions.