http://bugzilla.suse.com/show_bug.cgi?id=1000940 Bug ID: 1000940 Summary: empty /etc/crypttab in initrd after latest update Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: SUSE Other Status: NEW Severity: Major Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening@forge.provo.novell.com Reporter: martin.wilck@suse.com QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- I did a large factory update last night over night (possible user error here - the last update had been done on Sep. 1, a total of 2442 packages was installed). This morning the system had rebooted an was hanging. I couldn't get it up again until I realized that I wasn't asked a password for my encrypted swap partition any more. My crypttab looks like this: # cat /etc/crypttab cr_swap /dev/disk/by-id/ata-SK_hynix_SC300_M.2_2280_512GB_FJ63N456110303C1E-part6 none none I managed to boot from a snapshot and found that /etc/crypttab in the newly generated initrd was actually empty. I restored an old initrd from the snapshot to the main subvol and I was able to boot and to verify that the initrds for 4.7.2-1 and 4.7.4-default that had been created after the update contained an empty crypttab file. First I suspected the updated dracut (before: 004-9.1, now: 004-12.1), but rebuilding the initrd with the updated dracut worked now and resulted in a valid crypttab in the initrd. So, I can't reproduce the problem and I have no idea what caused it. Looking at the dracut code /usr/lib/dracut/modules/90crypt/module-setup.sh, the problem must have been caused by no host device being recognized as being of crypto_LUKS type, but I can't imagine why this wouldn't have worked when the initrd was rebuilt after the package update. If I run dracut now, it finds the swap device in /etc/fstab and correctly derives that it's on top of a crypto_LUKS device. The journals at the time of the initrd rebuild show no sign of anything unusual, except that the system suddenly rebooted about 30min after the update finished, with no log traces explaining it. The only idea I have it that this may be related to the fact that cryptsetup itself and various libraries belonging to it were in the list of updated packages. Not sure what to do with this, but I thought I'd put it down here anyway, in case anything similar might happen to someone again. -- You are receiving this mail because: You are on the CC list for the bug.