[Bug 329154] New: perl-Bootloader: Cannot get device for (hd0,1)/boot/grub/ stage2
https://bugzilla.novell.com/show_bug.cgi?id=329154 Summary: perl-Bootloader: Cannot get device for (hd0,1)/boot/grub/stage2 Product: openSUSE 10.2 Version: Final Platform: x86 OS/Version: Linux Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: jengelh@gmx.de QAContact: qa@suse.de Found By: Beta-Customer I am using the 2.6.22.9 (factory) kernel with perl-Bootloader-0.4.30-4 (both recompiled) on 10.2, but get this on installing or removing the kernel rpm: 2007-09-28 00:07:19 ERROR: Core::SplitDevPath: Cannot get device for (hd0,1)/boot/grub/stage1 2007-09-28 00:07:20 ERROR: Core::SplitDevPath: Cannot get device for (hd0,1)/boot/grub/stage2 I added print STDERR Dumper($self) to the top of SplitDevPath to figure out what's going on, maybe you have some idea? -- 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=329154#c1 --- Comment #1 from Jan Engelhardt <jengelh@gmx.de> 2007-09-27 16:30:58 MST --- Created an attachment (id=175333) --> (https://bugzilla.novell.com/attachment.cgi?id=175333) Core.pm::SplitDevPath augmented by print STDERR Dumper($self) I am not sure where the (hd0,1)/boot/grub/stage1 even comes from. -- 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=329154 Andreas Jaeger <aj@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|bnc-team-screening@forge.provo.novell.com |aosthof@novell.com -- 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=329154#c2 --- Comment #2 from Jan Engelhardt <jengelh@gmx.de> 2007-09-28 04:04:11 MST --- It has something to do with fstab. /boot is on /. The following entry works: /dev/sda2 / xfs auto,nobarrier,noatime 0 0 This one does not: /dev/disk/by-id/ata-WDC_WD400EB-00CPF0_WD-WCAAT5461367-part2 / xfs auto,nobarrier,noatime 0 0 I further found out that it is irrelevant whether /dev/sda or /dev/disk is used in menu.lst or /boot/grub/device.map. -- 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=329154 Alexander Osthof <aosthof@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED -- 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=329154#c3 --- Comment #3 from Jan Engelhardt <jengelh@gmx.de> 2007-09-28 04:37:55 MST --- sub GrubPath2UnixPath { ... #FIXME: sf@ need to check for udev links here as well ... } This function does not handle /dev/disk. Additionally, the line $self->l_milestone ("GRUB::GrubPath2UnixPath: Device $dev does not have mount point, keeping GRUB path $orig_path"); should be l_warning or so, since l_milestones do not get printed by default. -- 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=329154#c4 Jan Engelhardt <jengelh@gmx.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |WORKSFORME --- Comment #4 from Jan Engelhardt <jengelh@gmx.de> 2007-09-28 06:14:07 MST --- udev is supported. here is the deal: # udevinfo -q symlink -n /dev/sda2 disk/by-id/scsi-SATA_WDC_WD400EB-00CWD-WCAAT5461367-part2 disk/by-id/ata-WDC_WD400EB-00CP_WD-WCAAT5461367-part2 disk/by-path/pci-0000:00:02.5-scsi-0:0:0:0-part2 disk/by-uuid/a2f6869a-ab54-484a-b895-49aab4a92de4 disk/by-label/root # ls -1 /dev/disk/by-id/ata-*WDC*part2 /dev/disk/by-id/ata-WDC_WD400EB-00CPF0_WD-WCAAT5461367-part2 /dev/disk/by-id/ata-WDC_WD400EB-00CP_WD-WCAAT5461367-part2 # dmesg ata1.00: ATA-5: WDC WD400EB-00CPF0, 06.04G06, max UDMA/100 scsi 0:0:0:0: Direct-Access ATA WDC WD400EB-00CP 06.0 PQ: 0 ANSI: 5 $ udevtest /sys/block/sda/sda2 2>&1 | grep 00CP udev_rules_get_name: add symlink 'disk/by-id/ata-WDC_WD400EB-00CP_WD-WCAAT5461367-part2' udev_node_add: creating symlink '/dev/disk/by-id/ata-WDC_WD400EB-00CP_WD-WCAAT5461367-part2' to '../../sda2' No 00CPF0. The solution is that I used udev-114 from 10.3 in 10.2 (to test something else...) to create my last working initrd, so it created 00CPF0 and propagated it into the live /dev. ATM I am on udev-103 again. The following rules are not in the udev-103 used in 10.2: # libata compat (links like hd*) KERNEL=="sd*[!0-9]|sr*", ENV{ID_VENDOR}=="ATA", PROGRAM="ata_id $tempnode", RES KERNEL=="sd*[0-9]", ENV{ID_ATA_COMPAT}=="?*", SYMLINK+="disk/by-id/ata-$env{ID_ So, solved :-/ -- 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=329154 Jan Engelhardt <jengelh@gmx.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |VERIFIED -- 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