May 15, 201016 yr Wow... So I'm running 4.3.3 Pro and wanted to upgrade unMENU 1.2 to 1.3. I tried to execute the install commands given by Joe, but it seems wget is not installed on 4.3.x software. So I copied wget over to my /boot/packages dir on the flash drive and that is when everything went wrong. I tried to reboot because the server began to hang and when I was telneted into the box and noticed that there were no viewable files/dir in /boot. At reboot it made it through POST and then said no bootable disk. So I did something to the flash drive when copying over the wget dir. I plugged the flash drive into my PC and it saw the dir and files. So what the heck happened and how do I recover? Thank you,
May 15, 201016 yr Wow... So I'm running 4.3.3 Pro and wanted to upgrade unMENU 1.2 to 1.3. I tried to execute the install commands given by Joe, but it seems wget is not installed on 4.3.x software. So I copied wget over to my /boot/packages dir on the flash drive and that is when everything went wrong. I tried to reboot because the server began to hang and when I was telneted into the box and noticed that there were no viewable files/dir in /boot. At reboot it made it through POST and then said no bootable disk. So I did something to the flash drive when copying over the wget dir. I plugged the flash drive into my PC and it saw the dir and files. So what the heck happened and how do I recover? Thank you, First run scandisk on the flash drive. (move it to your PC to perform that test) Check to make sure it is selected as the boot device. If you do not see the boot menu where you can see the memory test, you may need to run syslinux on the flash drive. It should show up as a boot device. How did you attempt to load "wget" ?? There is a Slackware package for it, but I'm not sure if a .conf file for unMENU was posted. (I think it was) It is good that the flash drive shows up on your PC. You should see a config folder with your config files. Just run scandisk to make sure it is not corrupted, and select it as the boot device, and it will likely boot. As long as you did not remove the bzroot and bzimage files, it should boot. As I said, worst case, you'll need to run syslinux on it. You should NOT need to re-format it. It is already formatted and loaded. Joe L.
May 15, 201016 yr The package for the older version of unMENU to install wget is attached to this post http://lime-technology.com/forum/index.php?topic=6018.msg57535#msg57535
May 16, 201016 yr Author Sweet... I'm back up and running, a parity check started on the boot as I wasn't able to shutdown cleanly! I did get wget installed and now I'm trying to upgrade to unMENU 1.3, but I received some errors... errors received after trying to install unMENU 1.3: (just a sample) rev $Revision: 7 $ $Date: 2010-03-29 23:12:23 -0400 (Mon, 29 Mar 2010) $ grep: htop-unmenu-package.conf: No such file or directory mv: cannot stat `htop-unmenu-package.conf': No such file or directory Moved current htop-unmenu-package.conf to ./unmenu_old_2010-05-16_0601/htop-unme nu-package.conf cp: cannot create regular file `htop-unmenu-package.conf': Input/output error Installed htop-unmenu-package.conf Downloading iftop-unmenu-package.conf rev $Revision: 7 $ $Date: 2010-03-29 23:12:23 -0400 (Mon, 29 Mar 2010) $ grep: iftop-unmenu-package.conf: No such file or directory mv: cannot stat `iftop-unmenu-package.conf': No such file or directory Moved current iftop-unmenu-package.conf to ./unmenu_old_2010-05-16_0601/iftop-un menu-package.conf cp: cannot create regular file `iftop-unmenu-package.conf': Input/output error Installed iftop-unmenu-package.conf Downloading inotify-tools-unmenu-package.conf rev $Revision: 7 $ $Date: 2010-03-29 23:12:23 -0400 (Mon, 29 Mar 2010) $ grep: inotify-tools-unmenu-package.conf: No such file or directory
May 16, 201016 yr These errors seem to indicate your "tmp" directory is un-writable. (or the directory you are in when invoking unmenu_install is not writable) Or... perhaps it is that these packages don't currently exist and it is attempting to save the old versions of them. I can investigate if I have coded the logic in there for that correctly.I did not have the logic in place to deal with an initial install when looking for the AUTO_UPDATE tag in files. I had just added that ability recently. That tag allows you to make local changes to files and not have them updated, or to be alerted if they are update. The error messages were not a real issue, just that the files did not yet exist and it was trying to save backup copies for you of the old versions. Thanks to your report of the errors, I've just added the appropriate logic. Thanks The updated version will be on google.code once I'm through testing it. Joe L.
May 16, 201016 yr Author Joe, It doesn't seem that I can use the 'uu' command to start unMENU root@Tower:~# cd /boot root@Tower:/boot# cd unmenu root@Tower:/boot/unmenu# uu -bash: uu: command not found root@Tower:/boot/unmenu#
May 16, 201016 yr Joe, It doesn't seem that I can use the 'uu' command to start unMENU root@Tower:~# cd /boot root@Tower:/boot# cd unmenu root@Tower:/boot/unmenu# uu -bash: uu: command not found root@Tower:/boot/unmenu# Does the command file exist there? Type ls -l uu If it does, invoke it as ./uu or /boot/unmenu/uu
May 16, 201016 yr EDIT: Nevermind I see you got it mostly resolved! I think I had a similar issue yesterday when I upgraded finally my 4.4.2 version of unraid. It would just say boot error as if it didn't detect the flash as a bootable device. The fix was easy fortunately, I had to re-run the syslinux.exe command (see http://lime-technology.com/wiki/index.php?title=USB_Flash_Drive_Preparation#Instructions) on the flash drive and it made it bootable again. Hope this helps!
June 17, 201016 yr Author Joe, Well I wanted to mess around and try and get unMENU back installed: check this out Tower login: root Linux 2.6.24.4-unRAID. root@Tower:~# cd /boot/unmenu/uu -bash: cd: /boot/unmenu/uu: No such file or directory root@Tower:~# cd /boot root@Tower:/boot# ls root@Tower:/boot# cd /unmenu -bash: cd: /unmenu: No such file or directory root@Tower:/boot# cd unmenu root@Tower:/boot/unmenu# ls -l uu /bin/ls: cannot access uu: No such file or directory root@Tower:/boot/unmenu# I recall that once I get into the /boot dir that when I type ls, I would see the different files and dir within /boot. Why is it that I'm not seeing any of the directories? seems strange to me... and I would really like to get unMENU working again. I love that tool
June 17, 201016 yr Joe, Well I wanted to mess around and try and get unMENU back installed: check this out Tower login: root Linux 2.6.24.4-unRAID. root@Tower:~# cd /boot/unmenu/uu -bash: cd: /boot/unmenu/uu: No such file or directory "uu" is a file in the /boot/unmenu directory. You cannot change directory to a file. root@Tower:~# cd /boot "/boot" is a directory, this would work. root@Tower:/boot# ls The "ls" command should have listed a config directory, a bzimage file, a bzroot file, a syslinux.cfg file, and one or two others. The fact that it shows nothing indicates that the flash drive probably does not have the proper UNRAID volume label. Looking further in your series of commands, it must have some files and directories since you were able to "cd" to the /boot/unmenu directory. root@Tower:/boot# cd /unmenu -bash: cd: /unmenu: No such file or directory The /unmenu directory does not exist. It is usually created at /boot/unmenu root@Tower:/boot# cd unmenu root@Tower:/boot/unmenu# ls -l uu /bin/ls: cannot access uu: No such file or directory root@Tower:/boot/unmenu# I recall that once I get into the /boot dir that when I type ls, I would see the different files and dir within /boot. Why is it that I'm not seeing any of the directories? seems strange to me... me too and I would really like to get unMENU working again. I love that tool I would look to see if you've got the volume label properly set on your flash drive. You should see the config directory and the other two bzroot/bgimage files at the least. I'd also put your flash drive back in your PC and run scandisk on it. It might just have some file-system corruption on it keeping it from showing you the files. This highly likely if you did not eject it safely after you copied files to it. Perhaps it did not get mounted properly. Try these commands: mount ls -l /dev/disk/by-label let me know what you see as output. Joe L.
Archived
This topic is now archived and is closed to further replies.