![](https://seccdn.libravatar.org/avatar/851a3c5e1f11f380856bf7d3bd9137cb.jpg?s=120&d=mm&r=g)
I installed a 2nd version of suse8.1 on the same system/harddisk. version 1, called linux ;) boots fine version 2, called suse panics during grub stage 2 with the following error msg: kernel panic: no init found, try passing init= option to kernel What does the kernel proposal involve? The version called "suse" boots fine if invoked from suse's rescue disk (boot installed system. And it boots fine if grub is configured from within the version called "suse". However, in this configuration the other suse version called "linux" does panic with the same error. What may be the cause of this trouble? I searched the internet, sdb, experimented with grub's shell. The latter told that /vmlinuz is located at: (hd1,4) and (hd1,7). Below the current configuration of grub. I must say that the entry for suse has been altered by me. The original yast version is: title suse kernel (hd1,4)/vmlinuz root=/dev/hdb8 the init_rd modules have been set to INITRD_MODULES="reiserfs ide-scsi" 1 thing I did not do is to perform an mk_initd. I assume however that yast will take for that if that is required. yast2-bootloader version: :/etc/sysconfig> rpm -q yast2-bootloader yast2-bootloader-2.6.68-1 I hope someone has the golden hint! -- Richard Bos Without a home the journey is endless # Modified by YaST2. Last modification on Tue Apr 29 21:11:45 2003 gfxmenu (hd1,4)/message color white/blue black/light-gray default 0 timeout 8 title linux kernel (hd1,4)/vmlinuz root=/dev/hdb7 hdc=ide-scsi vga=791 initrd (hd1,4)/initrd title windows root (hd0,0) makeactive chainloader +1 title suse kernel (hd1,4)/vmlinuz root=/dev/hdb8 hdc=ide-scsi vga=791 initrd (hd1,7)/initrd title floppy root (fd0) chainloader +1 title failsafe kernel (hd1,4)/vmlinuz.shipped root=/dev/hdb7 ide=nodma apm=off acpi=off vga=normal nosmp maxcpus=0 disableapic 3 initrd (hd1,4)/initrd.shipped
![](https://seccdn.libravatar.org/avatar/adcd76e9bfc12b1fa0e7e216eabb9d9b.jpg?s=120&d=mm&r=g)
Richard Bos <radoeka@xs4all.nl> writes:
# Modified by YaST2. Last modification on Tue Apr 29 21:11:45 2003
title linux kernel (hd1,4)/vmlinuz root=/dev/hdb7 hdc=ide-scsi vga=791 initrd (hd1,4)/initrd
...
title suse kernel (hd1,4)/vmlinuz root=/dev/hdb8 hdc=ide-scsi vga=791
^^^^^, Here, I am a little surprised, why did you share the same kernel? Is it just a typo?
initrd (hd1,7)/initrd
-- Yongtao Yang email: yongtao.yang@telia.com
![](https://seccdn.libravatar.org/avatar/ae06dbef78077414ec8139481d771c82.jpg?s=120&d=mm&r=g)
On Tue April 29 2003 5:01 pm, Yongtao Yang wrote:
Richard Bos <radoeka@xs4all.nl> writes:
# Modified by YaST2. Last modification on Tue Apr 29 21:11:45 2003
title linux kernel (hd1,4)/vmlinuz root=/dev/hdb7 hdc=ide-scsi vga=791 initrd (hd1,4)/initrd
...
title suse kernel (hd1,4)/vmlinuz root=/dev/hdb8 hdc=ide-scsi vga=791
^^^^^, Here, I am a little surprised, why did you share the same kernel? Is it just a typo?
initrd (hd1,7)/initrd
-- Yongtao Yang
email: yongtao.yang@telia.com
You should change the "kernel (hd1,4)" to "kernel (hd1,7)", without the quotes of course, to match the root=/dev/hdb8 and initrd (hd1,7). title suse kernel (hd1,7)/vmlinuz root=/dev/hdb8 hdc=ide-scsi vga=791 initrd (hd1,7)/initrd Stan
![](https://seccdn.libravatar.org/avatar/851a3c5e1f11f380856bf7d3bd9137cb.jpg?s=120&d=mm&r=g)
Op woensdag 30 april 2003 03:08, schreef Stan Glasoe:
On Tue April 29 2003 5:01 pm, Yongtao Yang wrote:
Richard Bos <radoeka@xs4all.nl> writes:
# Modified by YaST2. Last modification on Tue Apr 29 21:11:45 2003
title linux kernel (hd1,4)/vmlinuz root=/dev/hdb7 hdc=ide-scsi vga=791 initrd (hd1,4)/initrd
...
title suse kernel (hd1,4)/vmlinuz root=/dev/hdb8 hdc=ide-scsi vga=791
^^^^^, Here, I am a little surprised, why did you share the same kernel? Is it just a typo?
initrd (hd1,7)/initrd
-- Yongtao Yang
email: yongtao.yang@telia.com
You should change the "kernel (hd1,4)" to "kernel (hd1,7)", without the quotes of course, to match the root=/dev/hdb8 and initrd (hd1,7).
title suse kernel (hd1,7)/vmlinuz root=/dev/hdb8 hdc=ide-scsi vga=791 initrd (hd1,7)/initrd
Changed that as well, but that did not help either. Should it theoretically work if the the config file is as follows? .... title linux kernel (hd1,4)/vmlinuz root=/dev/hdb7 hdc=ide-scsi vga=791 initrd (hd1,4)/initrd title suse kernel (hd1,7)/vmlinuz root=/dev/hdb8 hdc=ide-scsi vga=791 initrd (hd1,7)/initrd ..... Yast made it without the "hdc=ide-scsi vga=791" and the initrd line. for "suse". -- Richard Bos Without a home the journey is endless
![](https://seccdn.libravatar.org/avatar/72ee3b9e0735cf98a1e936a90fc087ed.jpg?s=120&d=mm&r=g)
On Wednesday 30 April 2003 09:56, Richard Bos wrote:
Should it theoretically work if the the config file is as follows?
.... title linux kernel (hd1,4)/vmlinuz root=/dev/hdb7 hdc=ide-scsi vga=791 initrd (hd1,4)/initrd
title suse kernel (hd1,7)/vmlinuz root=/dev/hdb8 hdc=ide-scsi vga=791 initrd (hd1,7)/initrd
Is there a program /sbin/init on hdb8? Have you tried mounting it from the working installation and check? What exactly is the error you get? Could there be an "Unable to mount" somewhere? Have you tried rebuilding the initrd? Does "boot installed system" work on the new install?
![](https://seccdn.libravatar.org/avatar/851a3c5e1f11f380856bf7d3bd9137cb.jpg?s=120&d=mm&r=g)
Op woensdag 30 april 2003 10:42, schreef Anders Johansson:
On Wednesday 30 April 2003 09:56, Richard Bos wrote:
Should it theoretically work if the the config file is as follows?
.... title linux kernel (hd1,4)/vmlinuz root=/dev/hdb7 hdc=ide-scsi vga=791 initrd (hd1,4)/initrd
title suse kernel (hd1,7)/vmlinuz root=/dev/hdb8 hdc=ide-scsi vga=791 initrd (hd1,7)/initrd
Is there a program /sbin/init on hdb8? Have you tried mounting it from the working installation and check?
No this is located hdb9. Mounting works fine. The "suse" linux boots okay if started from a rescue cd.
What exactly is the error you get? Could there be an "Unable to mount" somewhere? Have you tried rebuilding the initrd?
Does "boot installed system" work on the new install?
Yes. If even did, after the installation => yast has made the menu.lst file and the system therefor booted "suse" linux. So I rebooted the system to go to my work linux and that version stopped with exactly the same error: msg: kernel panic: no init found, try passing init= option to kernel Than I booted the work linux (called linux) from rescue disk and run yast in the work linux to create a new grub. Worked fine the work linux now boots okay, but the newly installed linux comes with: msg: kernel panic: no init found, try passing init= option to kernel I bet that if I run linux from the newly installed system, that I can get it to boot nicely, but that the work version won't boot in that case.... The work linux has everything on 1 big partition. What should be passed to the kernel via the "init=" option? -- Richard Bos Without a home the journey is endless
![](https://seccdn.libravatar.org/avatar/ae06dbef78077414ec8139481d771c82.jpg?s=120&d=mm&r=g)
On Wed April 30 2003 9:01 am, Richard Bos wrote:
snip<
Than I booted the work linux (called linux) from rescue disk and run yast in the work linux to create a new grub. Worked fine the work linux now boots okay, but the newly installed linux comes with: msg: kernel panic: no init found, try passing init= option to kernel
snip<
I quit using YaST to edit my boot loader options for SuSE 8.0 and 8.1. YaST would not correctly edit the file whether lilo or grub based. You seem to be suffering the same problem now. YaST just doesn't edit lilo.conf or grub's menu.lst file correctly all the time especially when trying to create a dual boot situation where there are different drives and partitions. This seems to have been fixed very well for v8.2 where you edit the whole file and not just certain lines. You should manually edit /boot/grub/menu.lst on your primary partition where your work linux is located. Also add the absolute path to initrd for your new install. This worked for me and can't hurt even if grub should use relative paths based on the root partition definition. I got the same errors and eventually ended up specifying absolute paths and it works - for me. Stan
![](https://seccdn.libravatar.org/avatar/72ee3b9e0735cf98a1e936a90fc087ed.jpg?s=120&d=mm&r=g)
On Wednesday 30 April 2003 16:01, Richard Bos wrote:
Op woensdag 30 april 2003 10:42, schreef Anders Johansson:
Is there a program /sbin/init on hdb8? Have you tried mounting it from the working installation and check?
No this is located hdb9. Mounting works fine. The "suse" linux boots okay if started from a rescue cd.
hdb9? Is that your root partition? Shouldn't you try "root=/dev/hdb9"?
What should be passed to the kernel via the "init=" option?
nothing, if things work as they should. init= is the program the kernel runs after it finishes loading. Normally this is /sbin/init, but if that is on hdb9 when you give the root partition as hdb8 it's not surprising it can't be found
![](https://seccdn.libravatar.org/avatar/851a3c5e1f11f380856bf7d3bd9137cb.jpg?s=120&d=mm&r=g)
Op woensdag 30 april 2003 16:49, schreef Anders Johansson:
hdb9? Is that your root partition? Shouldn't you try "root=/dev/hdb9"?
Anders, another point on solution score card! It's indeed that easy! Thanks a lot :)) -- Richard Bos Without a home the journey is endless
![](https://seccdn.libravatar.org/avatar/ae06dbef78077414ec8139481d771c82.jpg?s=120&d=mm&r=g)
On Wed April 30 2003 12:20 pm, Richard Bos wrote:
Op woensdag 30 april 2003 16:49, schreef Anders Johansson:
hdb9? Is that your root partition? Shouldn't you try "root=/dev/hdb9"?
Anders,
another point on solution score card! It's indeed that easy!
Thanks a lot :))
-- Richard Bos Without a home the journey is endless
Dang! Missed that /dev/hdb9 before. Congratulations. Anders, you are very good! Stan
![](https://seccdn.libravatar.org/avatar/851a3c5e1f11f380856bf7d3bd9137cb.jpg?s=120&d=mm&r=g)
Op woensdag 30 april 2003 10:42, schreef Anders Johansson:
What exactly is the error you get? Could there be an "Unable to mount" somewhere? Have you tried rebuilding the initrd?
There is an error before indeed; ... VFS: mounted root (ext2 filesystem) readonly trying to move old root to initrd.... failed unmounting old root Warning: unable to open an initial console Kernel panic: no init found, try passing init= option to kernel -- Richard Bos Without a home the journey is endless
![](https://seccdn.libravatar.org/avatar/851a3c5e1f11f380856bf7d3bd9137cb.jpg?s=120&d=mm&r=g)
Op woensdag 30 april 2003 16:35, schreef Richard Bos:
Op woensdag 30 april 2003 10:42, schreef Anders Johansson:
What exactly is the error you get? Could there be an "Unable to mount" somewhere? Have you tried rebuilding the initrd?
There is an error before indeed;
... VFS: mounted root (ext2 filesystem) readonly trying to move old root to initrd.... failed unmounting old root Warning: unable to open an initial console Kernel panic: no init found, try passing init= option to kernel
Ah, forgot. During the boot I went into the grub editor and the setting for the newly installed system to: title suse kernel (hd1,7)/boot/vmlinuz root=/dev/hdb8 hdc=ide-scsi vga=791 initrd (hd1,7)/boot/initrd -- Richard Bos Without a home the journey is endless
![](https://seccdn.libravatar.org/avatar/ae06dbef78077414ec8139481d771c82.jpg?s=120&d=mm&r=g)
On Wed April 30 2003 2:56 am, Richard Bos wrote:
Op woensdag 30 april 2003 03:08, schreef Stan Glasoe:
On Tue April 29 2003 5:01 pm, Yongtao Yang wrote:
Richard Bos <radoeka@xs4all.nl> writes:
# Modified by YaST2. Last modification on Tue Apr 29 21:11:45 2003
title linux kernel (hd1,4)/vmlinuz root=/dev/hdb7 hdc=ide-scsi vga=791 initrd (hd1,4)/initrd
...
title suse kernel (hd1,4)/vmlinuz root=/dev/hdb8 hdc=ide-scsi vga=791
^^^^^, Here, I am a little surprised, why did you share the same kernel? Is it just a typo?
initrd (hd1,7)/initrd
-- Yongtao Yang
email: yongtao.yang@telia.com
You should change the "kernel (hd1,4)" to "kernel (hd1,7)", without the quotes of course, to match the root=/dev/hdb8 and initrd (hd1,7).
title suse kernel (hd1,7)/vmlinuz root=/dev/hdb8 hdc=ide-scsi vga=791 initrd (hd1,7)/initrd
Changed that as well, but that did not help either.
Should it theoretically work if the the config file is as follows?
.... title linux kernel (hd1,4)/vmlinuz root=/dev/hdb7 hdc=ide-scsi vga=791 initrd (hd1,4)/initrd
title suse kernel (hd1,7)/vmlinuz root=/dev/hdb8 hdc=ide-scsi vga=791 initrd (hd1,7)/initrd .....
Yast made it without the "hdc=ide-scsi vga=791" and the initrd line. for "suse".
-- Richard Bos Without a home the journey is endless
In my theory, no, it shouldn't work. My /boot/grub/menu.lst has absolute path names. Specifying /vmlinuz looks to be a relative path and AFAIK grub don't do relative paths. Change these relative paths to absolutes. On my system I've quit using a separate /boot partition and leave it as a directory off /. My grub then has /boot/vmlinuz and /boot/initrd after the drive/partition designations. Change yours as follows and see what happens. The root=/dev/hd?? is OK. title linux kernel (hd1,4)/boot/vmlinuz root=/dev/hdb7 hdc=ide-scsi vga=791 initrd (hd1,4)/boot/initrd title suse kernel (hd1,7)/boot/vmlinuz root=/dev/hdb8 hdc=ide-scsi vga=791 initrd (hd1,7)/boot/initrd
![](https://seccdn.libravatar.org/avatar/72ee3b9e0735cf98a1e936a90fc087ed.jpg?s=120&d=mm&r=g)
On Wednesday 30 April 2003 15:26, Stan Glasoe wrote:
In my theory, no, it shouldn't work. My /boot/grub/menu.lst has absolute path names. Specifying /vmlinuz looks to be a relative path and AFAIK grub don't do relative paths.
grub follows the directory layout on the partition. grub's paths are relative to the partition you specify
Change these relative paths to absolutes. On my system I've quit using a separate /boot partition and leave it as a directory off /. My grub then has /boot/vmlinuz and /boot/initrd after the drive/partition designations. Change yours as follows and see what happens. The root=/dev/hd?? is OK.
title linux kernel (hd1,4)/boot/vmlinuz root=/dev/hdb7 hdc=ide-scsi vga=791
This will work if hd1,4 (hdb5) has a /boot and fail otherwise
![](https://seccdn.libravatar.org/avatar/ae06dbef78077414ec8139481d771c82.jpg?s=120&d=mm&r=g)
On Wed April 30 2003 8:32 am, Anders Johansson wrote:
On Wednesday 30 April 2003 15:26, Stan Glasoe wrote:
In my theory, no, it shouldn't work. My /boot/grub/menu.lst has absolute path names. Specifying /vmlinuz looks to be a relative path and AFAIK grub don't do relative paths.
grub follows the directory layout on the partition. grub's paths are relative to the partition you specify
My mileage varied greatly with grub under SuSE 8.1 and I had to specify absolute paths because grub didn't follow relative paths on the partitions. grub couldn't find /boot off / by itself. Took me a while to figure that out. grub would error out of the GUI and throw up the text version of its menu where I then had a chance to specify drive, partition and absolute path. Worked for me!
Change these relative paths to absolutes. On my system I've quit using a separate /boot partition and leave it as a directory off /. My grub then has /boot/vmlinuz and /boot/initrd after the drive/partition designations. Change yours as follows and see what happens. The root=/dev/hd?? is OK.
title linux kernel (hd1,4)/boot/vmlinuz root=/dev/hdb7 hdc=ide-scsi vga=791
This will work if hd1,4 (hdb5) has a /boot and fail otherwise
Correct. You'd need to adjust both kernel and initrd drive/partition and root=/dev/hdxx for separate /boot and / "root" partitions. Stan
participants (4)
-
Anders Johansson
-
Richard Bos
-
Stan Glasoe
-
Yongtao Yang