[Bug 534905] New: yast2 bootloader 2.18.14-1.2 damages /etc/grub.conf
http://bugzilla.novell.com/show_bug.cgi?id=534905 Summary: yast2 bootloader 2.18.14-1.2 damages /etc/grub.conf Classification: openSUSE Product: openSUSE 11.2 Version: Factory Platform: Other OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: holler@nefkom.info QAContact: jsrain@novell.com Found By: --- Created an attachment (id=315594) --> (http://bugzilla.novell.com/attachment.cgi?id=315594) y2log Working /etc/grub.conf before calling yast2 bootloader: setup --stage2=/boot/grub/stage2 --force-lba (hd0,3) (hd0,3) quit Excerpt from y2log (full log attached): 2009-08-27 17:40:35 <1> holler-n2(17441) [Bootloader_API] modules/Bootloader_API.pm(Bootloader_API::DumpLog):28 GRUB::UnixDev2GrubDev: Translated UNIX->GRUB: /dev/disk/by-id/scsi-SATA_WDC_WD3200BEVT-_WD-WXE608HE87174 to (hd0,87173) hd0,87173 is being written back to /etc/grub.conf: setup --stage2=/boot/grub/stage2 --force-lba (hd0,87173) (hd0,3) quit Please note: this is done without applying any changes in yast2 bootloader. You just have to say "OK" right after calling the module. You can imagine what will happen on next boot: All you can see is "GRUB" :-( -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=534905
Hans-Peter Holler
http://bugzilla.novell.com/show_bug.cgi?id=534905
User juhliarik@novell.com added comment
http://bugzilla.novell.com/show_bug.cgi?id=534905#c1
Jozef Uhliarik
http://bugzilla.novell.com/show_bug.cgi?id=534905
User holler@nefkom.info added comment
http://bugzilla.novell.com/show_bug.cgi?id=534905#c2
--- Comment #2 from Hans-Peter Holler
http://bugzilla.novell.com/show_bug.cgi?id=534905
User holler@nefkom.info added comment
http://bugzilla.novell.com/show_bug.cgi?id=534905#c3
--- Comment #3 from Hans-Peter Holler
http://bugzilla.novell.com/show_bug.cgi?id=534905
Hans-Peter Holler
http://bugzilla.novell.com/show_bug.cgi?id=534905
User jreidinger@novell.com added comment
http://bugzilla.novell.com/show_bug.cgi?id=534905#c4
Josef Reidinger
http://bugzilla.novell.com/show_bug.cgi?id=534905
User holler@nefkom.info added comment
http://bugzilla.novell.com/show_bug.cgi?id=534905#c5
Hans-Peter Holler
http://bugzilla.novell.com/show_bug.cgi?id=534905 User holler@nefkom.info added comment http://bugzilla.novell.com/show_bug.cgi?id=534905#c6 --- Comment #6 from Hans-Peter Holler2009-09-07 13:45:07 MDT --- 11.1 rescue system's fdisk shows the same info about ID 0x27, namely "Unknown", so I guess there was/is some magic in installation, right? >From my understanding this could help resolving: - install/installed system could be aware of ID 0x27 (util-linux package?) - perl-bootloader could have a (hardcoded) exception for ID 0x27 - yast2-bootloader could do a check for (in my case hd0,3 <--> hd0,87173) changes in partition numbers before (old entry in /etc/grub.conf) and after (returning results from perl-bootloader). -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=534905
User coolo@novell.com added comment
http://bugzilla.novell.com/show_bug.cgi?id=534905#c8
Stephan Kulow
http://bugzilla.novell.com/show_bug.cgi?id=534905
User juhliarik@novell.com added comment
http://bugzilla.novell.com/show_bug.cgi?id=534905#c10
Jozef Uhliarik
participants (1)
-
bugzilla_noreply@novell.com