Package: grub-imageboot
Version: 0.5
Severity: normal
When I try to boot the isos, i get
"Linux-bzImage error: file not found"
i changed the conf-file to point to a directory on my home and run
udpate-grub2 successfully.
/home is in a lvm volume
example stanza generated:
menuentry "Bootable ISO Image: debian-6.0.2.1-i386-CD-1" {
insmod lvm
insmod part_msdos
insmod ext2
set root='(qindelbox-root)'
search --no-floppy --fs-uuid --set=root
9587ac94-262q-4cdc-9eba-fb86ab29924b
linux16 /boot/memdisk iso
initrd16 /afuentes/qindel/isos/debian-6.0.2.1-i386-CD-1.iso
}
ls /dev/disk/by-uuid/* -l
lrwxrwxrwx 1 root root 10 Dec 26
08:59 /dev/disk/by-uuid/59425b6f-b4cd-4120-b0b2-c3150a6da8eb
-> ../../dm-1
lrwxrwxrwx 1 root root 10 Dec 26
09:07 /dev/disk/by-uuid/5be4404e-c912-4b84-b584-9070ba110a8b
-> ../../dm-2
lrwxrwxrwx 1 root root 10 Dec 26
08:59 /dev/disk/by-uuid/9587ac94-260e-4cfc-9eba-fb86ab29924b
-> ../../dm-0
lrwxrwxrwx 1 root root 10 Dec 26
08:59 /dev/disk/by-uuid/ba4fd7bd-b59e-446e-b441-e07a3defd28c
-> ../../sda1
the insmod lvm makes me think it should work.
But Im not sure why it does not generate "home" anywhere, since its the
lv the path hangs on...
Also, I tried grml-rescueboot and its able to find the isos at boot time
but grub-imageboot can't.
In the description it says it cant boot from some kind isos
(http://syslinux.zytor.com/wiki/index.php/MEMDISK), the web is offline.
I tried a lot of different isos from different distributions (debian,
ubuntu, centos, fedora, opensuse) and it cant find any of them.
Greets!
aL
--- System information. ---
Architecture: amd64
Kernel: Linux 3.1.0-1-amd64
Debian Release: wheezy/sid
900 testing security.debian.org
900 testing ftp.debian.org
800 unstable ftp.debian.org
700 experimental ftp.debian.org
500 stable dl.google.com
--- Package information. ---
Depends (Version) | Installed
==============================-+-===========
syslinux-common (>= 4) | 2:4.04+dfsg-9
grub-pc | 1.99-14
Package's Recommends field is empty.
Package's Suggests field is empty.
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
