[Bug 649503] New: Bootloader uses wrong root partition
https://bugzilla.novell.com/show_bug.cgi?id=649503 https://bugzilla.novell.com/show_bug.cgi?id=649503#c0 Summary: Bootloader uses wrong root partition Classification: openSUSE Product: openSUSE 11.3 Version: Final Platform: x86-64 OS/Version: openSUSE 11.3 Status: NEW Severity: Major Priority: P5 - None Component: Bootloader AssignedTo: jsrain@novell.com ReportedBy: speilicke@novell.com QAContact: jsrain@novell.com Found By: --- Blocker: --- After a hard disc change, the fstab entries where adapted accordingly. Together with the openSUSE-DVD, the bootloader was newly written. After a recent kernel upgrade, the early boot complains about beeing unable to mount "/dev/disc/by-id/ata-ST3250318AS_6VY6Y6F5-part2". I can be fixed by hand by issuing the command: "mount /dev/disk/by-id/ata-ST3250318AS_6VY6Y6F5-part2 /root" Strangely, a typo occured in the fstab. I'm unsure whether this was my fault or Yast-Bootloader's. Anyway, fstab and /boot/grub/menu.lst where fixed accordingly and a 'sudo mkinitrd" was issued. Unfortunately, the issue is still there. The question now is, which component fails to update to the 'fixed' partition path and where is the old value still lying around... This is the current /etc/fstab: /dev/disk/by-id/ata-ST3250318AS_6VY6Y6F5-part1 swap swap defaults 0 0 /dev/disk/by-id/ata-ST3250318AS_6VY6Y6F5-part2 / ext4 acl,user,xattr 1 1 proc /proc proc defaults 0 0 sysfs /sys sysfs noauto 0 0 debugfs /sys/kernel/debug debugfs noauto 0 0 usbfs /proc/bus/usb usbfs noauto 0 0 devpts /dev/pts devpts mode=0620,gid=5 0 0 This is the current /boot/grub/menu.lst (relevant section): default 0 timeout 3 gfxmenu (hd0,1)/boot/message ##YaST - activate ###Don't change this comment - YaST2 identifier: Original name: linux### title Desktop -- openSUSE 11.3 - 2.6.34.7-0.4 root (hd0,1) kernel /boot/vmlinuz-2.6.34.7-0.4-desktop root=/dev/disk/by-id/ata-ST3250318AS_6VY6Y6F5-part2 resume=/dev/disk/by-id/ata-ST3250318AS_6VY6Y6F5-part1 splash=silent quiet showopts vga=0x31a initrd /boot/initrd-2.6.34.7-0.4-desktop -- 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=649503 https://bugzilla.novell.com/show_bug.cgi?id=649503#c2 Thomas Fehr <fehr@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |speilicke@novell.com --- Comment #2 from Thomas Fehr <fehr@novell.com> 2010-11-02 12:11:10 UTC ---
From what I can see, /etc/fstab and /boot/grub/menu.lst look fine. So if there is still something using "disc" instead of "disk" it could only be initrd itself. Maybe mkinitrd wrongly detects the running root fs and puts the wrong name into generated initrd.
So please check the following things: - make sure mkinitrd really created the initrd file that is booted, maybe there was some bug in mkinitrd that prevented new initrd file or the initrd file was created with different name - check if the correct spelling is also in /boot/grub/device.map if this file exists - unpack the newly created initrd and check if there is still a mention of "/dev/disc/" somewhere in the files. This can be done the followng way: cd /tmp mkdir t cd t zcat /boot/initrd-2.6.34.7-0.4-desktop | cpio -idv grep "/dev/disc/" * - please provide content of /etc/mtab and /proc/mounts both are used by mkinitrd to determine current root filesystem -- 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=649503 https://bugzilla.novell.com/show_bug.cgi?id=649503#c3 Sascha Peilicke <speilicke@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|speilicke@novell.com | --- Comment #3 from Sascha Peilicke <speilicke@novell.com> 2010-11-02 12:51:14 UTC --- Issue resolved, there was another typo contained, "user, xattr" instead of "user_xattr". -- 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=649503 https://bugzilla.novell.com/show_bug.cgi?id=649503#c4 Sascha Peilicke <speilicke@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |CLOSED Resolution| |INVALID --- Comment #4 from Sascha Peilicke <speilicke@novell.com> 2010-11-02 12:51:51 UTC --- Marking as closed as this seemed to be done by me accidentally. -- 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