The elilo script does not properly initialize the loop variable. If this variable, for whatever reason, contains garbage then the mount will fail. Example: For some reason on my system loop initialized to contain "/image.squashfs" which caused the following error: FAT: Unrecognized mount option "umask=077/image.squashfs" or missing value. Reproducible: Always This bug is easily fixed by adding loop= on line 327 immediately before the 'if [ -f "$boot" ]' test.
The workaround specified was for elilo-3.10. I upgraded to ~ia64 as a test, I experienced this problem with the ia64 build (elilo-3.6_p20060314) as well.
Hrm...i don't get it. Why its not properly initialized?
(In reply to comment #2) > Hrm...i don't get it. > > Why its not properly initialized? > I honestly have no idea where that "/image.squashfs" came from. However, it looks to me that $loop is never initialized anywhere if it is supposed to be blank. It is just assumed that it will be blank if it is unset. Based on my knowledge of bash scripting that should be correct, but it doesn't seem like good programming practice. Curiously, If I run the unmodified script now on my working system it runs as expected. I experienced this problem when chrooted in from the livecd.
it is more than likely because of the options used to boot the livecd. I encountered the env var $loop set after using gentoo-ilo. if you just boot the live cd with no special options the env var does not get set and elilo will work just fine. elilo should still have this fixed though...
I wrote a patch for this. See also: http://sourceforge.net/tracker/?func=detail&atid=598709&aid=3606213&group_id=91879
See also: http://forums.gentoo.org/viewtopic-t-684290.html
Created attachment 372516 [details, diff] elilo-3.12-loop.patch Please set Keywords+=PATCH
i've added your fix to the new 3.16 ebuild: http://gitweb.gentoo.org/repo/gentoo.git/commit/?id=b6344f771c7953a9cda0765ea27e701c117f2cd1 probably should get e-mailed to the debian guys since it's a bug in their script :)
