Bugzilla – Bug 218525
Error occurred while installing GRUB
Last modified: 2006-11-22 09:25:39 UTC
Here's the screen I saw during "Install Boot Manager": Error occurred while installing GRUB. GNU GRUB version 0.97 (640K lower/3072K upper memory) [ Minimal BASH-like line editing is supported. For the first word, TAB lists possible command completions. Anywhere else TAB lists the possible completions of a device/filename.] grub> setup --stage2=/boot/grub/stage2 (hd0) (/dev/mapper/nvidia_hafdiidg,4) Error 23: Error while parsing number grub > quit This is a newly built machine---no OS installed previously and I started with new hard drives. Two hard drives in RAID mirroring. I read the bug about GRUB installing in the MBR no matter what. I tried checking both 'Boot from Boot partition' and 'Boot from MBR', but received the same message in both cases. AMD Athlon FX-55 DFI Lanparty UT nfF Ultra-D 2 Seagate 250 GB SATA in Raid Mirroring x86-64 Workarounds?
Please provide the YaST log files.
Created attachment 104670 [details] yast2 log On update from beta1, I had the following failing grub commandline: grub> setup --stage2=/boot/grub/stage2 (/dev/hda) (dev/hda,2) -> error 27, unrecognised number (same error as original report) /dev/hda2 is swap on this machine. I guess the code that generates the commandline is confusing "/dev/hda*" with "(hd0,2)" styles of addressing devices in grub, since hd0,2 or /dev/hda3 is the partition with /boot on it on this machine.
Created attachment 104671 [details] my fstab
Created attachment 104672 [details] menu.lst as generated by yast during upgrade
may be a problem within Storage.ycp::GetTranslatedDevices do not have the HW around :-( what does this block except this special piece of HW?
This may also be a subsequent fault of translating /dev/hd*/ (old naming of SATA devices) to /dev/sd* (new naming). Can you please provide "/boot/grub/device.map" to see if the mapping has gone wrong. If this was the case, please try to edit device.map manually during the installation and see if it works with a valid mapping.
I reinstalled the bootloader so my device.map is no longer useful. I got this bug when upgrading beta1plus to beta2, so my PATA disk went from being /dev/sda back to /dev/hda - could this be a factor? If necessary i can repeat the upgrade.
Yes, repeating the update would be very useful to encircle the problem.
I too encountered this very problem because of a change from the _wrong_ /dev/sda back to /dev/hda. Ended up having to boot to 10.2b1 mini install disk, change entries in the fstab file, boot using 10.2B2 install disk-->boot installed system and ran grub-install to fix grub entries. Should not be a problem for people upgrading from 10.1 as their fstab should point to the proper /dev/hda entries to start with.
AJ says my bug (sda->hda rename breaks grub) is impossible outside of the 10.2beta1plus ->beta2 case so I won't reinstall unless you think there is a deeper problem.
I'm downgrading this one to critical, because this error occurs on this special piece of HW, whereas other fake RAID systems are working properly. Current workaround is using soft RAID (md), we are investigating further.
The malfunctioning dmraid mechanism (in yast2-bootloader) is now fixed (in openSUSE 10.2 RC1). One should be able to install on Bios-RAIDs now. As this bug is now resolved, so I close it FIXED.