hi. I am trying to boot crux using the menuentry of the grub of another distro. both the distro and its grub are installed on /dev/sda (crux is installed on /dev/sde). all the other menuentries manage to boot the distros they refer to. However, when I try to boot crux I get a kernel panic. I must remark that If I boot crux with the installation media I can boot without any problem. *menuentry 'crux 3.1 (on /dev/sde1)' --class gnu-linux --class gnu --class os $menuentry_id_option 'osprober-gnulinux-/boot/vmlinuz-3.12.24-$ insmod part_msdos insmod ext2 set root='hd4,msdos1' if [ x$feature_platform_search_hint = xy ]; then search --no-floppy --fs-uuid --set=root --hint-bios=hd4,msdos1 --hint-efi=hd4,msdos1 --hint-baremetal=ahci4,msdos1 98ece8d4-ef04-48a6-a58e-c654314* *67f1f else search --no-floppy --fs-uuid --set=root 98ece8d4-ef04-48a6-a58e-c65431467f1f fi linux /boot/vmlinuz-3.12.24 root=/dev/sde1 }}* *### END /etc/grub.d/30_os-prober ###*I wonder if there is any changes I have to make on crux system to help it be booted this way. Besides If I install crux grub/lilo will it recognize the other distros I have on the other disks on this machine? And third I think if I decide to install crux grub/lilo it will have to be installed on /dev/sda(mbr). Or maybe I should change the boot order on bios (to boot /dev/sde in first place) and install it on /dev/sde. but I wonder if the other disks will be recognized and booted. *thanks for your attention*
On Sun, 1 Feb 2015 10:24:00 -0200 Cezar Rangel <cezar.rangel@gmail.com> wrote:
hi. I am trying to boot crux using the menuentry of the grub of another distro. both the distro and its grub are installed on /dev/sda (crux is installed on /dev/sde). all the other menuentries manage to boot the distros they refer to. However, when I try to boot crux I get a kernel panic. I must remark that If I boot crux with the installation media I can boot without any problem.
*menuentry 'crux 3.1 (on /dev/sde1)' --class gnu-linux --class gnu --class os $menuentry_id_option 'osprober-gnulinux-/boot/vmlinuz-3.12.24-$ insmod part_msdos insmod ext2 set root='hd4,msdos1' if [ x$feature_platform_search_hint = xy ]; then search --no-floppy --fs-uuid --set=root --hint-bios=hd4,msdos1 --hint-efi=hd4,msdos1 --hint-baremetal=ahci4,msdos1 98ece8d4-ef04-48a6-a58e-c654314*
*67f1f else search --no-floppy --fs-uuid --set=root 98ece8d4-ef04-48a6-a58e-c65431467f1f fi linux /boot/vmlinuz-3.12.24 root=/dev/sde1 }}*
*### END /etc/grub.d/30_os-prober ###*I wonder if there is any changes I have to make on crux system to help it be booted this way.
Besides If I install crux grub/lilo will it recognize the other distros I have on the other disks on this machine?
And third I think if I decide to install crux grub/lilo it will have to be installed on /dev/sda(mbr). Or maybe I should change the boot order on bios (to boot /dev/sde in first place) and install it on /dev/sde. but I wonder if the other disks will be recognized and booted.
*thanks for your attention*
Sounds like kernel problem to me. Probably the root filesystem module isn't built into the kernel.
tks John. I must confess I have enormous difficult with it. I have googled after your warning but did not find anything could help me. Would you suggest any way to take please Em 01/02/2015 10:55, "John Vogel" <jvogel4@stny.rr.com> escreveu:
On Sun, 1 Feb 2015 10:24:00 -0200 Cezar Rangel <cezar.rangel@gmail.com> wrote:
hi. I am trying to boot crux using the menuentry of the grub of another distro. both the distro and its grub are installed on /dev/sda (crux is installed on /dev/sde). all the other menuentries manage to boot the distros they refer to. However, when I try to boot crux I get a kernel panic. I must remark that If I boot crux with the installation media I can boot without any problem.
*menuentry 'crux 3.1 (on /dev/sde1)' --class gnu-linux --class gnu --class os $menuentry_id_option 'osprober-gnulinux-/boot/vmlinuz-3.12.24-$ insmod part_msdos insmod ext2 set root='hd4,msdos1' if [ x$feature_platform_search_hint = xy ]; then search --no-floppy --fs-uuid --set=root --hint-bios=hd4,msdos1 --hint-efi=hd4,msdos1 --hint-baremetal=ahci4,msdos1 98ece8d4-ef04-48a6-a58e-c654314*
*67f1f else search --no-floppy --fs-uuid --set=root 98ece8d4-ef04-48a6-a58e-c65431467f1f fi linux /boot/vmlinuz-3.12.24 root=/dev/sde1 }}*
*### END /etc/grub.d/30_os-prober ###*I wonder if there is any changes I have to make on crux system to help it be booted this way.
Besides If I install crux grub/lilo will it recognize the other distros I have on the other disks on this machine?
And third I think if I decide to install crux grub/lilo it will have to be installed on /dev/sda(mbr). Or maybe I should change the boot order on bios (to boot /dev/sde in first place) and install it on /dev/sde. but I wonder if the other disks will be recognized and booted.
*thanks for your attention*
Sounds like kernel problem to me. Probably the root filesystem module isn't built into the kernel. _______________________________________________ CRUX mailing list CRUX@lists.crux.nu https://lists.crux.nu/mailman/listinfo/crux
Quoting Cezar Rangel <cezar.rangel@gmail.com>:
tks John. I must confess I have enormous difficult with it. I have googled after your warning but did not find anything could help me. Would you suggest any way to take please
nobody is going to be able to help you without the actual kernel panic error message khm
Of course not Kurt, thanks for your attention. here is the error message, sorry for the delay Kernel panic - not syncing: VFS: unable to mount root fs on unknown - block (0,0) CPU: 5 PID: 1 comm: swapper/0 not tainted 3.12.24 #8 hardware name: system manufacturer. System Product name/M5A 78L-M/USB3, BIOS 1801: 11/12/2013 thanks
Quoting Cezar Rangel <cezar.rangel@gmail.com>:
Of course not Kurt, thanks for your attention. here is the error message, sorry for the delay
Kernel panic - not syncing: VFS: unable to mount root fs on unknown - block (0,0) CPU: 5 PID: 1 comm: swapper/0 not tainted 3.12.24 #8 hardware name: system manufacturer. System Product name/M5A 78L-M/USB3, BIOS 1801: 11/12/2013
thanks
John Vogel's guess is probably correct. Either your kernel does not have your filesystem driver compiled in, or your kernel does not have your SATA driver compiled in, or possibly both. khm
participants (3)
-
Cezar Rangel -
John Vogel -
Kurt H Maier