13.1 install fails in grub2 install

English Install/Boot/Login
#1

I wrote openSUSE-13.1-DVD-x86_64.iso to a USB flash drive and booted
a Tyan S2891 with AMD CPU in a 1U server with 4 hard drives.
The storage controller is a nVidia CK804
I created a MBR partition table,
then a 512MB /boot partition on sda1 with ext4, a 48G Linux RAID1 / on sd{a,b,c,d},
8GB of swap on sd{a,b,c,d},
and the rest of the hard drives was a Linux RAID6 data partition.
I picked the default software configuration and proceeded.
It gets to saving the bootloader configuration and hangs. I switch to the
console window and see:

*** Starting YaST2 ***
Perl-Bootloader: 2014-02-07 13:37:16 yast-1521.1 FileIO::ReadFile.85:
Error: Failed to open /etc/default/grub_installdevice: No such file or directory
Perl-Bootloader: 2014-02-07 13:37:16 yast-1521.1 FileIO::ReadFile.85:
Error: Failed to open /etc/default/grub: No such file or directory
…
Perl-Bootloader: 2014-02-07 13:37:16 yast-1521.1
Core::GRUB2::GrubDev2UnixDevices.215: Error: did not find a match for hd0 in
the device map
sh: /usr/bin/grub2-editenv: No such file or directory
sh: /usr/bin/grub2-editenv: No such file or directory
sh: /usr/bin/grub2-editenv: No such file or directory

Is there a workaround to get GRUB2 properly installed?

This is very repeatable (indeed I have tried it with many different install
options). I am guessing that some driver is not being loaded, since 13.1 obviously
installs fine for most systems, but not this one.

#2

Hi eak9000,

you mean during the installation?
Or before that?

#3

Check in BIOS settings if you have floppy controller; if yes, try to disable it. It is known to cause very long delay.

#4

During the installation. I clicked on Custom partitioning, then on sda, then Expert, and then Create New Partition Table and checked MSDOS. I wanted to start off fresh.

I have subsequently tried not using RAID1 on the / partition, but I got the same results. I didn’t expect that to make a difference from the error message, but it seemed worth a try.

#5

[quote="“eak9000,post:4,topic:97998”]

you mean during the installation?
Or before that?[/QUOTE]
During the installation. I clicked on Custom partitioning, then on sda, then Expert, and then Create New Partition Table and checked MSDOS. I wanted to start off fresh.[/QUOTE]

So, in effect, the MBR partition table may not have been created:
it was earmarked by the installer to be created, yes - but that may have failed.

Does that one needs a proprietary driver, or does it run natively under Linux?

That to me looks like your RAID can not be accessed by YaST/the openSUSE installer.

You may get a clue to that by booting a live openSUSE and look if you can access your RAID then.

Good luck
Mike

#6

fdisk run via the rescue system seems to show something reasonable.

Seems to be native. I don’t do anything except boot from the install media, and the install GUI clearly sees the disks.

I can access the RAID from the rescue system.