11.12.2017 23:49, Paul Neuwirth пишет:
On Monday 2017-12-11 20:57, Paul Neuwirth wrote:
On Monday 2017-12-11 12:52, Andrei Borzenkov wrote:
managed to boot into installation system. so, # cat /mnt/etc/default/grub_installdevice /dev/disk/by-uuid/9f47366c-5819-447b-b6c5-398a9e21538c /dev/sda activate generic_mbr # file /dev/disk/by-uuid/9f47366c-5819-447b-b6c5-398a9e21538c /dev/disk/by-uuid/9f47366c-5819-447b-b6c5-398a9e21538c: symbolic link to `../../sdb2'
this seems indeed to be messed up.. what should be the content for raid redundancy (boot partitions /dev/sdb2 / dev/sdc2) and generic MBR on /dev/sdb and /dev/sdc
addendum, just noticed some things while fixing using chroot.. identifying partitions by UUID won't work on RAID1..
Welcome to the wonderful world of multi-device btrfs and udev.
so: # ls -l /dev/disk/by-uuid/ total 0 lrwxrwxrwx 1 root root 9 Dec 11 19:04 1e170d10-9587-40d9-afe5-bdf6e903fb8b -> ../../md0 lrwxrwxrwx 1 root root 10 Dec 11 19:04 9f47366c-5819-447b-b6c5-398a9e21538c -> ../../sdb2
shows only up the first partition of the raidset
of course. Both partitions have the same UUID, how do you expect to have two links with the same name but pointing to different content? Whatever was the first (or last, not sure) wins. ...
how to reboot? # shutdown -r now Failed to start reboot.target: Failed to execute program org.freedesktop.systemd1: Success Failed to talk to init daemon. # init 6 Couldn't find an alternative telinit implementation to spawn # reboot Failed to start reboot.target: Failed to execute program org.freedesktop.systemd1: Success Failed to talk to init daemon.
reboot -f
ok.. # echo "b" > /proc/sysrq-trigger worked
and no success... i mounted everything in the right paths, chrooted, fixed device.map and grub_installdevices ran yast bootloader
In the past it most definitely did not reinstall bootloader again. If you are sure you fixed grub_installdevice, run "update-bootloader --reinit". ...
changed disk order in BIOS
now I got into grub,
Did not you say earlier that you did it and it did not help?
but there are signs of errors (messed up on serial console):
error:beforelbootingcor0`c'sfor aocommand-line. err e e t o error:
system up and running, btrfs raid assembled correctly. Thanks for any help.
but bootloader installation is not correct yet, any help appreciated.
Use /dev/disk/by-id to identify individual partitions. I am not sure what is high-level command to write generic bootloader (I think only YaST does it), so I usually change bootloader to NONE in YaST, exit bootloader module and then call bootloader module again and select grub2. In this case yast goes through normal sequence to initialize bootloader including all settings. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org