On 27/06/2020 16.37, cagsm wrote:
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.
Obviously, but that information is not security or privacy important, and impedes checking of files that should point to that partition.
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?
When you posted yesterday you were in the middle of the process with a second machine that failed. I asked you to halt and wait, and produce the information that was asked. I don't know if the information is of use now or not.
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?
When you hit the problem in one, just stop, do not repair. Just produce the information with bootinfoscript and post here or upload to susepaste.org and paste the link here.
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?
I am not Andrei, I don't have his knowledge. The idea is to find out what is the problem, with the information requested, then you can locate it yourself and correct before running the zypper dup. -- Cheers / Saludos, Carlos E. R. (from 15.1 x86_64 at Telcontar)