[Bug 400483] New: initrd ignores root= parameter
https://bugzilla.novell.com/show_bug.cgi?id=400483 Summary: initrd ignores root= parameter Product: openSUSE 11.0 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: Basesystem AssignedTo: hare@novell.com ReportedBy: lnussel@novell.com QAContact: qa@suse.de Found By: --- The initrd ignores root= parameter at the kernel command line. It always uses the built in device ie the one from the system mkinitrd was run on. By using rootdev= instead of root= it's possible to override that but that's not documented and sucks for scripts that are intended to work with multiple distros. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=400483 User hare@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=400483#c1 Hannes Reinecke <hare@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|hare@novell.com |agraf@novell.com --- Comment #1 from Hannes Reinecke <hare@novell.com> 2008-06-16 07:09:55 MDT --- Alex? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=400483 User agraf@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=400483#c2 Alexander Graf <agraf@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |lnussel@novell.com --- Comment #2 from Alexander Graf <agraf@novell.com> 2008-06-23 23:25:12 MDT --- What exactly does not work? If you boot and specify 'root=/dev/sda3' during bootup? I use that all the time, so I doubt that's broken. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=400483 User lnussel@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=400483#c3 Ludwig Nussel <lnussel@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|lnussel@novell.com | --- Comment #3 from Ludwig Nussel <lnussel@novell.com> 2008-06-24 02:23:30 MDT --- You almost made me question my mind as it worked just now when I tried manually :-) However it fails with the build script. The difference is that the build script adds init=/something as first argument: $ /usr/bin/qemu-kvm -no-reboot -nographic -net none -kernel /boot/vmlinuz -initrd /boot/initrd -append "panic=1 quiet root=/dev/sda rw console=ttyS0,115200" -serial stdio -hda /abuild/build-root.lnussel.img qemu: loading initrd (0x584dc5 bytes) at 0x7a6b000 pci 0000:00:01.0: PIIX3: Enabling Passive Release doing fast boot Boot logging started on /dev/ttyS0(/dev/console) at Tue Jun 24 08:16:57 2008 Creating device nodes with udev Trying manual resume from /dev/sda1 resume device /dev/sda1 not found (ignoring) Trying manual resume from /dev/sda1 resume device /dev/sda1 not found (ignoring) Waiting for device /dev/sda to appear: ok fsck 1.40.8 (13-Mar-2008) fsck: fsck.ext2: not found fsck: Error 2 while executing fsck.ext2 for /dev/sda fsck succeeded. Mounting root device read-write. Mounting root /dev/sda sh-3.2# exit Kernel panic - not syncing: Attempted to kill init! Rebooting in 1 seconds. -> ok. now with init= $ /usr/bin/qemu-kvm -no-reboot -nographic -net none -kernel /boot/vmlinuz -initrd /boot/initrd -append "init=/bin/bash panic=1 quiet root=/dev/sda rw console=ttyS0,115200" -serial stdio -hda /abuild/build-root.lnussel.img qemu: loading initrd (0x584dc5 bytes) at 0x7a6b000 pci 0000:00:01.0: PIIX3: Enabling Passive Release doing fast boot Boot logging started on /dev/ttyS0(/dev/console) at Tue Jun 24 08:17:38 2008 Creating device nodes with udev Trying manual resume from /dev/sda1 resume device /dev/sda1 not found (ignoring) Trying manual resume from /dev/sda1 resume device /dev/sda1 not found (ignoring) Waiting for device /dev/disk/by-id/scsi-SATA_ST3320820AS_6QF4MDVH-part2 to appear: ..............................Could not find /dev/disk/by-id/scsi-SATA_ST3320820AS_6QF4MDVH-part2. Want me to fall back to /dev/disk/by-id/scsi-SATA_ST3320820AS_6QF4MDVH-part2? (Y/n) n not found -- exiting to /bin/sh $ exit /dev/disk/by-id/scsi-SATA_ST3320820AS_6QF4MDVH-part2: error opening volume invalid root filesystem -- exiting to /bin/sh $ exit Mounting root /dev/disk/by-id/scsi-SATA_ST3320820AS_6QF4MDVH-part2 mount: you must specify the filesystem type could not mount root filesystem -- exiting to /bin/sh $ exit No init found. Try passing init= option to the kernel. umount: /dev/pts: device is busy umount: /dev/pts: device is busy umount: /dev: device is busy umount: /dev: device is busy Kernel panic - not syncing: Attempted to kill init! -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=400483 User agraf@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=400483#c4 --- Comment #4 from Alexander Graf <agraf@novell.com> 2008-06-24 10:55:07 MDT --- Looks fine to me. Everything after init= are usually command line arguments for init. It's good to know people are using KVM though ;-). -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=400483 User agraf@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=400483#c5 Alexander Graf <agraf@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED --- Comment #5 from Alexander Graf <agraf@novell.com> 2008-07-17 16:06:51 MDT --- Looks like you were right. init= should not end argument processing. The issue should be gone with the next update. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com