Bug ID | 1205261 |
---|---|
Summary | dracut/hooks/emergency...ESP's FAT serial number in initrd halts boot in dracut emergency shell after rsync migration to new GPT system disk |
Classification | openSUSE |
Product | openSUSE Tumbleweed |
Version | Current |
Hardware | x86-64 |
OS | Other |
Status | NEW |
Severity | Normal |
Priority | P5 - None |
Component | Basesystem |
Assignee | screening-team-bugs@suse.de |
Reporter | mrmazda@earthlink.net |
QA Contact | qa-bugs@suse.de |
Found By | --- |
Blocker | --- |
Created attachment 862770 [details] rdsosreport.txt from TW boot attempt Original Summary: dracut/hooks/emergency...ESP's FAT serial number in initrd halts boot in dracut emergency shell after rsync migration to new GPT system disk Initial state: 1-configured booting & mounting are via LABELs (making UUIDs administratively unimportant, and grub.cfg's own auto-generated stanzas uncommonly necessary or desired), with /etc/grub.d/06_custom causing /boot/grub2/custom.cfg's vmlinuz & initrd symlink stanzas to precede auto-generated entries at boot time. Example: <https://forums.opensuse.org/showthread.php/533087-How-to-have-a-custom-UEFI-grub-menu-for-a-multiboot-system?p=2880389#post2880389> 2-in /etc/default/grub: GRUB_DISTRIBUTOR="opensusetw" # TW20221008 last zypper dup 3-multiboot of TW with Leap 15.1, 15.2, 15.3, 15.4, Debian 11 & 12, Ubuntu 20.04 & 22.04 on single NVME 4-only TW installation is configured to touch NVRAM or ESP for writing (e.g., other OSes' fstabs don't mount ESP, and/or they have no bootloader installed) To reproduce: 1-GPT partition new NVME with ESP, swap, and / targets for TW, and / for at least one additional distro 2-format new NVME's matching targets ESP FAT32, swap swap, and / EXT4 for TW 3-"rsync -rlptgoDHAX --exclude 'lost+found'" from old NVME's ESP and / to new ESP and / filesystems for TW 4-appropriately edit volume LABELs on new NVME /boot/grub2/grub.cfg, /boot/grub2/custom.cfg, /etc/fstab 5-repeat create/format/rsync/edit for additional distro(s) 6-remove original NVME 7-try to boot from new NVME Actual behavior: 1-all other distro(s) boot normally (via TW's custom.cfg entries) as if nothing had been changed 2-TW boot halts in dracut emergency shell because the original ESP's FAT serial number cannot be found (see attached rdsosreport.txt) Expected behavior: 1-all distros boot normally (via custom.cfg entries) as if nothing had been changed Notes: 1-Boot is normal since rebuilding of initrds post-migration. 2-I looked for ESP FAT serial references in several non-TW initrds and found none. 3-from lsinitrd of original initrd-5.19.13-default: -rw-r--r-- 1 root root 92 Oct 9 23:10 usr/lib/dracut/hooks/emergency/80-\x2fdev\x2fdisk\x2fby-uuid\x2f20A0-1003.sh 4-# lsblk -f | grep vfat # (current state, not initial state) ������������������nvme1n1p1 vfat FAT16 PI3P01ESP 20A0-1003 (*original* ESP on 120G NVME) ������������������nvme0n1p1 vfat FAT32 PNY5P01ESP 4C58-8D7E 294.1M 8% /boot/efi (*new* ESP on 500G NVME) 5-This issue complicates restoring from backups.