OK,  I'm running unRaid 4.7 with 1 parity drive, & 8 data drives, set into 4 user shares.

No special configurations, or plugins or anything other than the stock unRaid.

 

Last night, I decided to check out 5.0 rc11 since I had some free time.

 

I followed the instructions on the wiki, 

ie.. backed up my flash drive, & then copied bzimage, & bzroot over the old ones.

 

Put the drive back in the server, & booted it.

 

It got to the menu with unRaid & memtest, & then started loading unRaid.

Got about 5 rows of .......'s & then it just sat there & never went any further.

I waited about 30 min, before rebooting & trying again, but it went to the same spot & stopped again.

 

At this point, I've restored back to 4.7 & am running fine.

 

Any thoughts?

That's rather unusual, don't recall a report of that before.  I would first download a new copy of RC11, then verify the zip file, perhaps you got a bad download the first time?

 

Then try using Check Disk on your flash drive, on a Windows computer.

Will try downloading it again tonight.

 

Don't think it's the flash drive.  It's been working fine since I started using unRaid in '08

& is still working fine with the two 4.7 files back on it.

 

Thanks

... & is still working fine with the two 4.7 files back on it.

 

That suggests that maybe you only copied the bzroot and bzimage files.  While that trick can work for small incremental upgrades, you very probably need to to copy other files as well and then re-run the installer batch file.  There have been some users reporting boot failures when updating just those two files - in each case the solution has been to update including the newer syslinux.exe file.  If you didn't you should also refer to the release notes when going from 4.7 to 5.x

Here's what I followed:

1. Prepare the flash: either shutdown your server and plug the flash into your PC or Stop the array and perform the following actions referencing the flash share on your network:

o Copy the files bzimage and bzroot from the zip file to the root of your flash device, overwriting the same-named files already there.

o If present, delete these files from the flash (sorry, you will have to re-enter all your users after booting this release):

? config/passwd

? config/shadow

? config/smbpasswd

2. Reboot your server. Once boot-up has completed, you should see "Stopped. Configuration valid." array status with all disks assigned correctly except for the Cache disk. If you previously had a Cache disk assigned, you will need to re-assign it manually and re-apply any unique configuration settings for it.

3. Carefully examine the Identification strings for each disk. If you see "MBR: error", or "MBR: unknown" for any disk, do not Start the array; instead post your finding in the Forum announcement thread for this release. If everything looks ok, click Start to bring the array on-line. Note: there is a new configuration setting on the Disk Settings page called "Enable auto start". If you set this to "Yes", then upon next server boot, if the array is valid, then it will be automatically Started (this is the old behavior).

4. Go to Utils/New Permissions and execute that utility to change file ownership and permission settings. This is necessary for proper operation of the 5.0 security model.

5. Go to Users page and re-enter all of your users. If you plan on using SMB and/or AFP with either Secure or Private security mode, you must enter at least one user because the 'root' user name is no longer permitted for network share authentication.

 

 

Just didn't make it past step 2

OK - but the problem is in booting - that's why you also need to copy the syslinux.exe syslinux.cfg and perhaps the other files.  This only became a problem with rc10 or rc11 - it's possible the regular update instructions don't cover his case.

From the wiki here...    http://lime-technology.com/wiki/index.php/Migrating_from_unRAID_4.7_to_unRAID_5.0

 

Reboot and test

 

    Reboot the server

    Did it boot UnRAID up?

    If yes, proceed to next section

    If it did not boot at all, not even to the boot menu, it probably needs the new syslinux files

        Take the flash drive to any Windows computer, and plug it in

        Make sure that you copy from the UnRAID v5 AIO distro all of the files in the root to the flash drive (in particular, syslinux.exe, make_bootable.bat, and menu.c32)

        Run make_bootable.bat (yes, even though you may have run it in the past)

            For Windows Vista or Windows 7, right-click on the 'make_bootable' batch file and select 'Run as administrator'

            Note: users with non-English Windows systems may need to use the enhanced 'make_bootable' batch file found here

        Use the 'Safely Remove Hardware' tool and unplug the flash drive and reinstall in UnRAID server

        Now boot again and all should be fine

If it did not boot at all, not even to the boot menu, it probably needs the new syslinux files

 

Yeah,  saw that, but I did get past the boot menu..

 

But I will try this tonight & see what happens.

You might run chkdsk as well just to be sure.