On Fri, Jun 26, 2020 at 8:17 PM Andrei Borzenkov <arvidjaar@gmail.com> wrote:
/dev/disk/by-uuid/0000-11111-22222-333333 You intentionally make it more difficult? What exactly are you hiding here?
I am hiding my UUIDs, obviously. as I fixed that second system already as well, is it still of any use to run that script on the now 15.2 normally booting system any more? maybe I find some more systems that go bust. I will run that script on all the machines I come across to be able to later provide some information? what more is there to do? for example just to make sure to not be stuck with a remote machine not booting, can I do something after the zypper dup finished inside ssh, at the very end, for example then run yast2 bootloader module there and fixing it before even running into a mess? my systems normally only boot from mbr disks usually, and from a or from the / (root) partition. so I guess that partition needs to be set as active bootflag and the / some generic mbr code of grub2 needs to be set? or which of those three or four checkboxes would I need to apply to have a normally booting single disk. the bios always points to the first disk (sda) to boot from. i always had thought this was the simple most way to use disks and boot from a select partition. first some mbr code, that bringing up grub2 bootloader and that reading from the proper root (/) partition the rest and the next steps. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org