July 7, 201411 yr I decided I was going to upgrade from 4.7 to 5.0.5 I did a parity check, and then began to follow the steps from http://lime-technology.com/wiki/index.php/Upgrade_Instructions. I renamed the old bzimage and bzroot, and copied the new ones from the zip. Upon rebooting it just hangs, the web GUI never comes up and the IP is not pingable. But, if delete those two files, and rename the old ones back to normal, it then boots up without a problem. Anyone see this before or have any ideas what could be causing it? It's not in a spot where I can easy get a monitor to it, so I wanted to see what other troubleshooting could be done before I start moving things around.
July 7, 201411 yr I decided I was going to upgrade from 4.7 to 5.0.5 I did a parity check, and then began to follow the steps from http://lime-technology.com/wiki/index.php/Upgrade_Instructions. I renamed the old bzimage and bzroot, and copied the new ones from the zip. Upon rebooting it just hangs, the web GUI never comes up and the IP is not pingable. But, if delete those two files, and rename the old ones back to normal, it then boots up without a problem. Anyone see this before or have any ideas what could be causing it? It's not in a spot where I can easy get a monitor to it, so I wanted to see what other troubleshooting could be done before I start moving things around. First, I would do a full backup of your USB drive if not done already. Also, take a screenshot of your GUI showing drive placements. For booting I would suggest you re-run the make bootable batch file to try and fix this. If that doesn't fix it, then it may be some of your legacy 4.7 files causing issues in the new version. If this is the case there is a longer list of things I would suggest, including a clean boot of 5.0.5 (i.e. reformat the USB, copy over UnRAID files, rerun make bootable and let the system come up. If this is needed you can copy a few files from the config folder to keep things pretty much the same: ident.cfg - for hostname network.cfg for ip info (if statically set) share.cfg for all your existing shares. Plus any Pro/Plus license key. You can potentially use your 4.7 plugins (other than Simple Features), but there may be value in doing new installs based on PhAzE's plugins to make sure everything is current.
July 8, 201411 yr Author I ran the make bootable batch as administrator and it didn't fix things. So then I did a format, then clean install of 5.0.5 onto the USB, copying over ident.cfg, network.cfg. and share.cfg. Same result. I shuffled things around, and was able to hookup a monitor to the box. The box was at a login prompt, but still when i went to the web GUI, it would not come up at all. And the IP is not pingable. (I have a static IP set in network.cfg ) What should I try next?
July 8, 201411 yr Save a syslog to the USB at the local console prompt from a failed 5.x boot, zip it up and attach it to your first post, and if you can, also a syslog from a successful 4.7 boot and do the same. Possibly also try using the stock network.cfg and see if it successfully pulls an ip address from your dhcp. I suspect your network card isn't supported in 5.x. If you have a spare NIC, you could try booting 5.x with that.
July 8, 201411 yr now that you have a monitor hooked up, attache a keyboard, login and issue the following command "ifconfig eth0". Verify the IP address is the one you expect.
July 9, 201411 yr Author Using a stock network.cfg, same thing. ifconfig only shows loopback, it doesn't see the eth0 at all. The NIC is actually part of the motherboard ( ASRock A55M-VS FM1 AMDMicro ATX )
July 9, 201411 yr Using a stock network.cfg, same thing. ifconfig only shows loopback, it doesn't see the eth0 at all. The NIC is actually part of the motherboard ( ASRock A55M-VS FM1 AMDMicro ATX ) If you've done a stock network.cfg this is unlikely, but try completely stock. Wipe the USB, copy the files over, make bootable and then try. If it fails, then I would also try the same with the latest 6.0 beta. See if either build will recognize your NIC. Another thing to try is if you have a PCI based NIC you can try booting with that. I usually keep an Intel 1000 Pro card around as it's recognized by everything under the sun.
July 9, 201411 yr According to your motherboard specs, you have a Realtek PCIE x1 LAN RTL8105E 10/100 NIC. In the past Realtek NICs could be an issue getting the correct drivers. That may be the case here. While I never had an issue with mine, I purchased an Intel PCI-E NIC. You might want to upgrade your Nic to a GigE version if you have to upgrade it.
July 9, 201411 yr Author Using version 6.0-beta6 I was able to boot successfully! I assume at this point, I assign the drives as they were in 4.7 (from my screenshot), and then bring the array online?
July 9, 201411 yr Using version 6.0-beta6 I was able to boot successfully! I assume at this point, I assign the drives as they were in 4.7 (from my screenshot), and then bring the array online? Yes
July 9, 201411 yr Using version 6.0-beta6 I was able to boot successfully! I assume at this point, I assign the drives as they were in 4.7 (from my screenshot), and then bring the array online? Yes, just keep in mind that if you had any plugins in 4.7 that they will not work in version 6. Assuming you just want to get back to operational you can look at PhAzE's plugins as he offers 64-bit plugins for version 6.0. You can also still install UnMENU if you used that (though you have to still stay away from Simple Features). UnRAID 6.0 plugins for most users are moving over to Docker, but there is going to be a learning curve required for this, so you are likely better to get stable with standard plugins and can then look at Docker down the road if desired.
July 14, 201411 yr Author I've been running the 6 Beta...so far, so good! It's just learning curve from 4.7 I'm used to. Thanks for everyone's suggestions and advice!
Archived
This topic is now archived and is closed to further replies.