27.10.2020 03:56, Robin Klitscher пишет:
Sorry about the length of this, but I need to explain the setting.
The machine is a brand new Intel i7, UEFI with NVMe and SATA SSDs in GPT mode. It carries two installations of Leap 15.2 (one for production and one to play with); and one installation of Tumbleweed. Each of these is stand-alone with its own separate / and /home, on ext4 filesystems throughout.
It was all going well, but then I made a silly mistake. When booted externally into Parted Magic from a USB stick I accidentally deleted a data partition
What exactly is "data partition"? Is it mounted in all operating systems?
on one of the drives with gparted. I’ve managed to reinstate the partition and its contents from backups, but the error has meant I could no longer boot into any of the internal systems installed. I just got thrown to a Dracut emergency shell and “enter root password for maintenance”.
dracut does not ask for password. What makes you believe it has anything to do with initramfs?
I’ve now reinstalled one of the Leaps from scratch, and it’s working. But the other Leap and the Tumbleweed aren’t. To cut a long story short, in each case the journal ends with dracut timeout errors; and there are messages that “not all disks have been found” and “you might want to regenerate your initramfs”.
Never describe computer output. Always provide exact content (copy-paste or upload, preferably to https://susepaste.org/).
From this it seems a fair bet that something to do with the external deletion and renewal of the partition with gparted has confused the installed kernel(s).
I’d prefer to fix this without re-installations. If there’s a way of invoking either mkinitramfs or dracut from the Dracut emergency shell, I can’t find it. Is there?
No, because it is most likely completely unrelated to dracut. You simply need to adjust /etc/fstab to use new UUID in each installed OS where your "data partition" is mounted. If you need help with that, provide information requested in another reply.
Alternatively, is there a way of rebuilding the initramfs in the two errant installations when booted to the one that works?
Or is there some other fix that will avoid starting over and reinstalling everything from scratch?
(Please understand that, being an 84-year-old novice in these matters, I am only partly knowledgeable and would appreciate simplicity.)
-- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org