Andrei
I checked and this option is offered only if there are exactly two disks RAID1. Sorry.
You can manually edit /etc/default/grub_installdevice and add each disk; it is the file that is used by update-bootloader so if it is correct subsequent bootloader updates should be correct as well. But I'm afraid it means you won't be able to edit bootloader configuration by YaST then.
I'm ok with manual files. Prefer them, fewer surprises. That file exists here but it's empty. I can't find Suse documentation for its usage yet.
From other distros I figure I'd add those four disks as
/etc/default/grub_installdevice /dev/disk/by-id/ata-ST31000528AS_AAAAAAAA /dev/disk/by-id/ata-ST31000528AS_BBBBBBBB /dev/disk/by-id/ata-ST31000528AS_CCCCCCCC /dev/disk/by-id/ata-ST31000528AS_DDDDDDDD activate for d in /dev/disk/by-id/ata* do ls $d readlink -f $d echo -e "\n" done ... /dev/disk/by-id/ata-ST31000528AS_AAAAAAAA /dev/sda /dev/disk/by-id/ata-ST31000528AS_BBBBBBBB /dev/sdc /dev/disk/by-id/ata-ST31000528AS_CCCCCCCC /dev/sdb /dev/disk/by-id/ata-ST31000528AS-DDDDDDDD /dev/sdd ... /etc/default/grub_installdevice /dev/disk/by-id/ata-ST31000528AS_AAAAAAAA /dev/disk/by-id/ata-ST31000528AS_BBBBBBBB /dev/disk/by-id/ata-ST31000528AS_CCCCCCCC /dev/disk/by-id/ata-ST31000528AS-DDDDDDDD activate update-bootloader --reinit tail -f /var/log/YaST/y2log /var/log/pbl.log ... { '/etc/default/grub_installdevice' => [ '/dev/disk/by-id/ata-ST31000528AS_AAAAAAAA', '/dev/disk/by-id/ata-ST31000528AS_BBBBBBBB', '/dev/disk/by-id/ata-ST31000528AS_CCCCCCCC', '/dev/disk/by-id/ata-ST31000528AS-DDDDDDDD', 'activate', '' ] } 2015-11-27 11:11:12 <1> pbl-7539.2 Core::GRUB2::InitializeBootloader.1356: devices = [ '/dev/disk/by-id/ata-ST31000528AS_AAAAAAAA', '/dev/disk/by-id/ata-ST31000528AS_BBBBBBBB', '/dev/disk/by-id/ata-ST31000528AS_CCCCCCCC', '/dev/disk/by-id/ata-ST31000528AS-DDDDDDDD', 'activate', '' ] 2015-11-27 11:11:37 <1> pbl-7539.2 Core::RunCommand.1654: '/usr/sbin/grub2-install --target=i386-pc --force --skip-fs-probe "/dev/disk/by-id/ata-ST31000528AS_AAAAAAAA"' = 0, output: <<<<<<<<<<<<<<<< Installing for i386-pc platform. Installation finished. No error reported. >>>>>>>>>>>>>>>> 2015-11-27 11:12:00 <1> pbl-7539.2 Core::RunCommand.1654: '/usr/sbin/grub2-install --target=i386-pc --force --skip-fs-probe "/dev/disk/by-id/ata-ST31000528AS_BBBBBBBB"' = 0, output: <<<<<<<<<<<<<<<< Installing for i386-pc platform. Installation finished. No error reported. >>>>>>>>>>>>>>>> 2015-11-27 11:12:24 <1> pbl-7539.2 Core::RunCommand.1654: '/usr/sbin/grub2-install --target=i386-pc --force --skip-fs-probe "/dev/disk/by-id/ata-ST31000528AS_CCCCCCCC"' = 0, output: <<<<<<<<<<<<<<<< Installing for i386-pc platform. Installation finished. No error reported. >>>>>>>>>>>>>>>> 2015-11-27 11:12:44 <1> pbl-7539.2 Core::RunCommand.1654: '/usr/sbin/grub2-install --target=i386-pc --force --skip-fs-probe "/dev/disk/by-id/ata-ST31000528AS-DDDDDDDD"' = 0, output: <<<<<<<<<<<<<<<< Installing for i386-pc platform. Installation finished. No error reported. >>>>>>>>>>>>>>>> 2015-11-27 11:13:07 <3> pbl-7539.2 Core::RunCommand.1658: Error: '/usr/sbin/grub2-install --target=i386-pc --force --skip-fs-probe ""' failed with exit code 1, output: <<<<<<<<<<<<<<<< Installing for i386-pc platform. /usr/sbin/grub2-install: error: cannot find a GRUB drive for . Check your device.map. >>>>>>>>>>>>>>>> Not sure what to do with that. cat /boot/grub2/device.map cat /boot/grub2/device.map (hd0) /dev/disk/by-id/ata-ST31000528AS_AAAAAAAA (hd1) /dev/disk/by-id/ata-ST31000528AS_BBBBBBBB (hd2) /dev/disk/by-id/ata-ST31000528AS_CCCCCCCC (hd3) /dev/disk/by-id/ata-ST31000528AS_DDDDDDDD
An error occurred during boot loader installation. Retry boot loader configuration? [Yes] [No]
Well, if you unchecked everything this may be expected. I never really tried it, although update-bootloader should work.
I'm a little confused then. I asked which boxes to check
Just to be clear, that means which of the two boxes in the UI
[ ] Boot from Master Record [ ] Write Generic Boot Code to MBR
?
You said
None of them. MBR here means "MBR of the first disk", in whatever disk order YaST finds them.
So I unchecked both of them. Not the right action? - Garrett -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org