July 10, 201510 yr Hi All, I followed the steps in the following thread to upgrade to unRAID 6, including getting a full backup of my flash drive: http://lime-technology.com/forum/index.php?topic=41061.0 What has happened is now my system hangs on boot. One thing I should add is that I am running a custom kernel that I compiled using this thread: http://lime-technology.com/forum/index.php?topic=33118.0 Just so people don't need to read the thread to see what I did, I created a custom syslinux.cfg as follows: default /syslinux/menu.c32 menu title Lime Technology prompt 0 timeout 50 label unRAID OS Custom Kernel menu default kernel /bzimaged append initrd=/bzrootd label unRAID OS Custom Kernel (no plugins) kernel /bzimaged append initrd=/bzrootd unraidsafemode label unRAID OS Standard kernel /bzimage append initrd=/bzroot label unRAID OS Standard (no plugins) kernel /bzimage What I see now is the custom boot menu just continues to loop. I'm assuming it is because it can't find the custom kernel since it has been moved to the ./unRAID5 folder when the update occurred. I have an IPMI enabled system, so I am able to try and manually pick the kernel to load, but all that I try result in the IPMI console start the load and then nothing else happens. This is normal if the system is booting normally, but the system never comes up. It never gets an IP address from my router and isn't accessible. I have tried the following from the IPMI console: /bzimage initrd=bzroot /unRAID5/bzimage /bzroot /unRAID5/bzimage All of these options result in the same thing, the system doesn't boot successfully so I can't telnet to the server to change anything. Any way for me to revert to the old setup from IPMI or resolve this? Thanks in Advance!
July 10, 201510 yr I am sorry to say, but the title of your topic is very misleading. It is not an upgrade problem but a configuration problem. Have you tried to upgrade in the standard way first ?
July 10, 201510 yr Some observations - * Sorry, this one is off-topic but I just wanted to comment on the first URL. The 'topic=41061' part is correct and all you need, points to the topic you wanted it too. The 'msg388631' part is really odd, because post 388631 occurred BEFORE the first post of the topic! I don't know how that URL construction could happen! The last part '#new' is unwanted, as it would take each user to a different post in the topic based on what that user had already read. * The first URL and your stated intent is to run a v6 unRAID. The second URL (as far as I can tell) is strictly a v5 based custom kernel. I'm not completely sure I understand what you are trying to do, but there is no way a v5 system can coexist with a v6 system. If you are trying to set up syslinux to provide a dual boot capability (very interesting idea though!), there's no way I know of to set up coexisting config folders, or extra or packages folders either. You do have a backup of your v5 boot drive. Your only solution is to have one SD card with v5 and another with v6 (solely v6 on it). As you probably know, v5 is 32 bit (and all its addons). The v6 software and all its addons (plugins and Dockers) are all 64 bit, and CANNOT be mixed with 32 bit. * You never mention running make_bootable, so that may have been a contributing factor. The syslinux support often has to be updated. Then you HAVE to make sure that only the current version of all syslinux files are present, old and new can't be mixed. * Your syslinux.cfg file above is missing the last append. Hopefully, this will give you the ideas you need to make it work?
July 10, 201510 yr Author I apologize if the subject is misleading and if anything is unclear based on what I posted. The only reason why I posted the part about the custom kernel was it was the only thing I could think of that would cause the upgrade not to work from 5.05 to 6. Following the first article posted, I suspected that I would be able to reboot after the upgrade and it would work, but when I when I loaded the console in IPMI I saw the menu from my syslinux.cfg was looping which made me believe it was due to the upgrade moving the files to the /unRAID5 folder. I was able to finally get my system booted by using the following from IPMI: /unRAID5/bzimaged initrd=/unRAID5/bzrootd Unfortunately I am still unable to figure out why my upgrade didn't complete. The upgrade via plugin didn't mention the make_bootable portion. I figured that it was already set since my usb boot was working before. I would just reconfigure my thumb drive, but it is mounted inside my unRAID and I would like to try and upgrade without having to pull the drive if at all possible.
July 10, 201510 yr Author Some observations - * Sorry, this one is off-topic but I just wanted to comment on the first URL. The 'topic=41061' part is correct and all you need, points to the topic you wanted it too. The 'msg388631' part is really odd, because post 388631 occurred BEFORE the first post of the topic! I don't know how that URL construction could happen! The last part '#new' is unwanted, as it would take each user to a different post in the topic based on what that user had already read. * The first URL and your stated intent is to run a v6 unRAID. The second URL (as far as I can tell) is strictly a v5 based custom kernel. I'm not completely sure I understand what you are trying to do, but there is no way a v5 system can coexist with a v6 system. If you are trying to set up syslinux to provide a dual boot capability (very interesting idea though!), there's no way I know of to set up coexisting config folders, or extra or packages folders either. You do have a backup of your v5 boot drive. Your only solution is to have one SD card with v5 and another with v6 (solely v6 on it). As you probably know, v5 is 32 bit (and all its addons). The v6 software and all its addons (plugins and Dockers) are all 64 bit, and CANNOT be mixed with 32 bit. * You never mention running make_bootable, so that may have been a contributing factor. The syslinux support often has to be updated. Then you HAVE to make sure that only the current version of all syslinux files are present, old and new can't be mixed. * Your syslinux.cfg file above is missing the last append. Hopefully, this will give you the ideas you need to make it work? After reading your post and one from the upgrade plugin thread, is there no way to upgrade to unRAID 6 from 5.05 without running make_bootable from a desktop machine even though the current USB drive boots 5.05 just fine?
July 10, 201510 yr I mixed up your situation a little with another user, who was swapping SD cards. My apologies for that, and ignore the comment about SD cards. When you're a bit scatter-brained and you look at too many support requests ... Syslinux, whether the Windows, Mac, or Linux versions, has to adjust the MBR to boot the appropriate boot files. Currently, your flash is set to boot the syslinux files from the v5 distro, so the only chance it can work without running syslinux again (that's basically all that make_bootable does) is to make sure that only the syslinux files from the v5 distro are installed, and in their same locations. You'll need to use either the root folder OR the syslinux folder depending on how it used to be, the way it used to work. Check your backup of the flash drive, and make sure the correct ldlinux files are where they belong. The ldlinux file(s) are not necessarily part of the unRAID distro, they are set up by syslinux when it's run. Try booting, if it works, great. The problem is that a change was made somewhere in the v5 betas to v6 betas to v6 final, and MOST users have had to update the syslinux support, or booting would fail before the boot menu appears. So if the above attempt fails, then you'll HAVE to install the newer syslinux files and run syslinux on it. It doesn't matter whether you run the Windows, Mac, or Linux version, and Tom mentioned about adding a syslinux version to the unraidserver.plg upgrade method, but it hasn't happened yet, and I haven't heard of anyone else trying it. If you can locate the correct files, probably have to be Slack compatible, then you can try that. Otherwise, you'll have to run it from Windows or Mac. Have you tried booting it with v5, then mapping a drive to the flash, and running make_bootable that way, on a Windows or Mac?
July 10, 201510 yr Community Expert Have you tried booting it with v5, then mapping a drive to the flash, and running make_bootable that way, on a Windows or Mac? I hate to sound like a complete noob, but I'm trying to do that and can't seem to figure it out on my Mac. I've tried smb://tower/boot but that doesn't work because there is no share. What's the easiest way for me to do that? Thanks! You cannot run syslinux over the network. If using a Mac, then the USB stick needs to be plugged into a USB port on the Mac and you run the make_bootable.mac file from it.
July 10, 201510 yr Author Have you tried booting it with v5, then mapping a drive to the flash, and running make_bootable that way, on a Windows or Mac? I hate to sound like a complete noob, but I'm trying to do that and can't seem to figure it out on my Mac. I've tried smb://tower/boot but that doesn't work because there is no share. What's the easiest way for me to do that? Thanks! You cannot run syslinux over the network. If using a Mac, then the USB stick needs to be plugged into a USB port on the Mac and you run the make_bootable.mac file from it. Ok, thanks. So basically there is no way to upgrade from 5.05 to 6 without pulling the USB drive from my unRAID box? It's mounted internally and I'm accessing the box remotely at the moment.
July 10, 201510 yr Doesn't look like it's going to work without physical access. I'm sorry. Thanks for the correction, itimpi, rather thoughtless of me. Obviously, boot sector access is not possible over the file-centric access of the network link.
July 10, 201510 yr Author Doesn't look like it's going to work without physical access. I'm sorry. Thanks for the correction, itimpi, rather thoughtless of me. Obviously, boot sector access is not possible over the file-centric access of the network link. Ok thanks. I'll pull the drive when I get physical access. Thanks again for your help!
July 11, 201510 yr Community Expert Doesn't look like it's going to work without physical access. I'm sorry. Thanks for the correction, itimpi, rather thoughtless of me. Obviously, boot sector access is not possible over the file-centric access of the network link. I must admit that I am surprised that Limetech have never gotten around to including syslinux in the basic build so that it COULD be done from within unRAID itself.
July 11, 201510 yr Doesn't look like it's going to work without physical access. I'm sorry. Thanks for the correction, itimpi, rather thoughtless of me. Obviously, boot sector access is not possible over the file-centric access of the network link. I must admit that I am surprised that Limetech have never gotten around to including syslinux in the basic build so that it COULD be done from within unRAID itself. Don't you have a chicken-and-egg problem here ? How to run the utility from unRAID if it isn't able to start in the first place ...
July 11, 201510 yr Community Expert Doesn't look like it's going to work without physical access. I'm sorry. Thanks for the correction, itimpi, rather thoughtless of me. Obviously, boot sector access is not possible over the file-centric access of the network link. I must admit that I am surprised that Limetech have never gotten around to including syslinux in the basic build so that it COULD be done from within unRAID itself. Don't you have a chicken-and-egg problem here ? How to run the utility from unRAID if it isn't able to start in the first place ... Possibly - but could not the plugin itself install include it, install it, and then make use of it as part of doing the upgrade process? The upgrade plugin knows what version of unRAID it is using so can make sure it uses a compatible version of syslinux.
Archived
This topic is now archived and is closed to further replies.