On 27/10/2020 06.13, Robin Klitscher wrote:
On 27/10/2020 16:30, Felix Miata wrote:
Robin Klitscher composed on 2020-10-27 13:56 (UTC+1300): ...
Knowing each of the following inputs & their outputs run while booted to the working Leap will help us help you:
1-content of /etc/fstab on all three installations 2-parted -l 3-blkid
These should not be allowed to wrap. If you can't prevent wrapping in the reply, instead upload to https://susepaste.org/ and provide the URL(s) in reply here. You may also try using the susepaste command, which commonly reports upload failed and yet if you goto https://susepaste.org/lists in web browser you might find that the attempt(s) actually succeeded. If susepaste.org completely fails you try https://pastebin.com/ or one of a number of alternate services intended for temporary text file sharing that does not depend on scripting or login by those wishing to view uploads.
Or just attach to the email: parted -l > outputofparted.txt and attach outputofparted.txt. same with the other operations.
Thanks for your reply. For the fstab info below, Leap 15.2-1 is the installation that's working; Leap 15.2-2 and Tumbleweed are not. /vms at /dev/sda1 is the partition I deleted and rebuilt.
fstab Leap 15.2-1:
UUID=84a01450-8779-44a3-9be6-73e0b1f4de6d / ext4 defaults 0 1 UUID=e6d79374-c1e0-4d51-8bfe-076b0c1ab592 /avstuff ext4 data=ordered 0 2 UUID=84168ba6-727d-4751-8cc3-8570e5999d40 /vms ext4 data=ordered 0 2 UUID=028e6f21-13ae-47ca-b895-e0f3a7231ed1 /home ext4 data=ordered 0 2 UUID=5a691959-e8b4-4908-bf6a-e021d0b88205 /data2 ext4 data=ordered 0 2 UUID=60f0cb8e-d2dc-465d-80c7-43889088a341 /data1 ext4 data=ordered 0 2 UUID=4D62-1AA8 /boot/efi vfat defaults 0 2
All in disk /dev/nvme0n1
fstab Leap 15.2-2
UUID=4e4aacff-8ee7-496f-98d1-2e2451c5e986 / ext4 defaults 0 1 UUID=e6d79374-c1e0-4d51-8bfe-076b0c1ab592 /avstuff ext4 data=ordered 0 2 UUID=47b7e31e-cbc4-4597-8bee-1ce39ee7f9dc /vms ext4 data=ordered 0 2 --> Does not exist (2)
UUID=5c5d12a4-d148-4b54-8d1d-c1c4b00afb82 /home ext4 data=ordered 0 2 UUID=5a691959-e8b4-4908-bf6a-e021d0b88205 /data2 ext4 data=ordered 0 2 UUID=60f0cb8e-d2dc-465d-80c7-43889088a341 /data1 ext4 data=ordered 0 2 UUID=0908-2851 /boot/efi vfat defaults 0 2 --> Does not exist. (1)
fstab Tumbleweed
UUID=480fb714-3c98-41a1-9ad8-2c1bf006c9df / ext4 defaults 0 1 UUID=e6d79374-c1e0-4d51-8bfe-076b0c1ab592 /avstuff ext4 data=ordered 0 2 UUID=47b7e31e-cbc4-4597-8bee-1ce39ee7f9dc /vms ext4 data=ordered 0 2 --> Does not exist (2) UUID=53c9e18d-c164-435f-a0bc-549b89395d6d /home ext4 data=ordered 0 2 UUID=5a691959-e8b4-4908-bf6a-e021d0b88205 /data2 ext4 data=ordered 0 2 UUID=60f0cb8e-d2dc-465d-80c7-43889088a341 /data1 ext4 data=ordered 0 2 UUID=0908-2851 /boot/efi vfat utf8 0 2 --> Does not exist. (1)
Note 1: As /boot/efi points to the same (not existing) partition, you have to make sure that in file "/etc/default/grub" the line GRUB_DISTRIBUTOR="whatever" is different for each. Note 2: as you rebuilt that partition on sda, you probably have to point to it on all systems. You have to correct those two errors, and probably run "mkinitrd" on the two failing systems. Huh, not enough, you need rebuild EFI as well. See later. ....
and blkid (I hope this works re wrapping!):
It did. /dev/sda
/dev/sda1: UUID="84168ba6-727d-4751-8cc3-8570e5999d40" TYPE="ext4" PARTUUID="094cbde3-3b3d-43b2-8812-dc03a87a620a" --> /vms of Leap 15.2-1
/dev/nvme 1 TB
/dev/nvme1n1: PTUUID="b6504902-92d4-4ac9-ae7e-9f715090cfb8" PTTYPE="gpt" /dev/nvme1n1p1: UUID="ab08f233-f5d1-408c-8102-f3b5611b1a36" TYPE="swap" PARTUUID="43d5ee35-9564-4227-8876-74256b7ee3be" /dev/nvme1n1p2: UUID="4e4aacff-8ee7-496f-98d1-2e2451c5e986" TYPE="ext4" PARTUUID="b931e72b-c111-44bf-a1f9-66bdd64d5747" --> / of Leap 15.2-2 /dev/nvme1n1p3: UUID="5c5d12a4-d148-4b54-8d1d-c1c4b00afb82" TYPE="ext4" PARTUUID="fca57644-f40f-4ffc-84d1-f2a2629dd810" --> home of Leap 15.2-2 /dev/nvme1n1p4: UUID="480fb714-3c98-41a1-9ad8-2c1bf006c9df" TYPE="ext4" PARTUUID="9cfc0bbc-9fb5-40f0-902d-fce5027f99e5" --> / of TW /dev/nvme1n1p5: UUID="53c9e18d-c164-435f-a0bc-549b89395d6d" TYPE="ext4" PARTUUID="6963981f-762f-4296-ad14-c7e2fe937d21" --> /home of TW /dev/nvme1n1p6: UUID="5a691959-e8b4-4908-bf6a-e021d0b88205" TYPE="ext4" PARTUUID="5c432136-96bd-4aa6-a366-454629e685ff" --> /data2
/dev/nvme 1 TB
/dev/nvme0n1: PTUUID="7ccdd54c-83ce-48b9-b5c4-bf287d1fe5f6" PTTYPE="gpt" /dev/nvme0n1p1: SEC_TYPE="msdos" UUID="4D62-1AA8" TYPE="vfat" PARTUUID="7ccc1488-b39a-4993-922d-af39e42d8c7c" --> /boot/efi of Leap 15.2-1 /dev/nvme0n1p2: UUID="84a01450-8779-44a3-9be6-73e0b1f4de6d" TYPE="ext4" PARTUUID="e21a19fa-74e8-45c9-8d92-3e2d0038f0d2" --> / of Leap 15.2-1 /dev/nvme0n1p3: UUID="028e6f21-13ae-47ca-b895-e0f3a7231ed1" TYPE="ext4" PARTUUID="c56b077b-1ade-4dc7-b7c1-4b273a94f19f" --> /home of Leap 15.2-1 /dev/nvme0n1p4: UUID="60f0cb8e-d2dc-465d-80c7-43889088a341" TYPE="ext4" PARTUUID="1b57af9d-de15-4ca0-a152-d91af4aba9ac" --> /data1 /dev/nvme0n1p5: UUID="e6d79374-c1e0-4d51-8bfe-076b0c1ab592" TYPE="ext4" PARTUUID="8af24f30-3073-4f78-a89c-b0e0ddaeff8e" --> /avstuff
I see there are differences in UUIDs for /dev/sda1 and the efi partition between the working installation and the other two, and assume that's relevant, but just changing the numbers in the appropriate fstab doesn't seem to improve things. Should it have?
Nope... (change the names below to your liking) Ok boot the one system that works. Then, you have to mount ALL the partitions of Leap 15.2-2 under, say, /mnt/leap152, and those of TW under, say, /mnt/tw. Edit on /etc/default/grub: GRUB_DISTRIBUTOR="Leap 15.2-1" Edit on /mnt/leap152/etc/default/grub: GRUB_DISTRIBUTOR="Leap 15.2-2" Edit on /mnt/tw/etc/default/grub: GRUB_DISTRIBUTOR="TW" Then you have to do (as root in a terminal): yast You will get to YaST in text mode. Do not try to use the GUI version (it will not work with the other two chroot operations later). Move with the tab key, or use the highlighted letter (with Alt). Go to "System/Boot Loader" module, then to the "Bootloader Options" tab. Then change the number of seconds in "Timeout in Seconds" by one up or down. Then push the Ok button to apply the changes. Changing the seconds is a trick that forces YaST to write it all again to disk. mount --bind /proc /mnt/leap152/proc mount --bind /sys /mnt/leap152/sys mount --bind /dev /mnt/leap152/dev mount --bind /proc /mnt/tw/proc mount --bind /sys /mnt/tw/sys mount --bind /dev /mnt/tw/dev chroot /mnt/leap152/ yast (same as above) exit chroot /mnt/tw/ yast (same as above) exit I hope this is all you need. :-) -- Cheers / Saludos, Carlos E. R. (from 15.1 x86_64 at Telcontar)