| Summary: | boot-error after installing online-updates (encrypted swap on intel-fake-raid) | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Walter Mageia-User <sch-nospam> |
| Component: | RPM Packages | Assignee: | Kernel and Drivers maintainers <kernel> |
| Status: | NEW --- | QA Contact: | |
| Severity: | normal | ||
| Priority: | Normal | CC: | davidwhodgins, doktor5000 |
| Version: | 8 | ||
| Target Milestone: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| URL: | https://forums.mageia.org/de/viewtopic.php?f=7&t=3942&p=40648#p40648 | ||
| Whiteboard: | |||
| Source RPM: | dracut-051-4.mga8 kernel-desktop-5.15.65-1.mga8-1-1.mga8 (and earlier) | CVE: | |
| Status comment: | |||
| Attachments: | /run/initramfs/rdsosreport.txt with rd.debug kernel-option | ||
|
Description
Walter Mageia-User
2022-09-18 17:45:37 CEST
Created attachment 13383 [details]
/run/initramfs/rdsosreport.txt with rd.debug kernel-option
Does it just happen once and is ok after that, or does it now happen every boot? It's likely from bug 29884, It's reference, https://www.openwall.com/lists/oss-security/2022/01/13/2 has ... ===================== The former reencryption operation (without the additional digest) is no longer supported (reencryption with the digest is not backward compatible). You need to finish in-progress reencryption before updating to new packages. The alternative approach is to perform a repair command from the updated package to recalculate reencryption digest and fix metadata. The reencryption repair operation always require a user passphrase. An alternative fix is to use the newly introduced configure option --disable-luks2-reencryption to completely disable LUKS2 reencryption code. ===================== Assigning to kernel and drivers team. CC:
(none) =>
davidwhodgins For further information please also see the thread in the german forum: https://forums.mageia.org/de/viewtopic.php?f=7&t=3942 To summarize, either doing swapoff -a before regenerating initrd after updates or using 'dracut -f --omit "resume"' enables to boot normally, so this might be an issue from dracut handling encrypted swap on an Intel RAID. OP mentioned he does have encrypted swap etc. on another box without the Intel RAID and it works fine there. FWIW, another issue seems to be that adding 'omit_dracutmodules+=" resume "' to /etc/dracut.conf.d/99-disable-resume.conf seems to be read by dracut, but it does not have the same effect as 'dracut -f --omit "resume"' (although it should.) CC:
(none) =>
doktor5000 (In reply to Dave Hodgins from comment #2) > Does it just happen once and is ok after that, or does it now happen every > boot? This happens on every boot. A workaround is to generate an initrd like Florian told. do you have /etc/dracut.conf.d/51-mageia-resume.conf if you comment out the add_device* line there, does it work automatically then when regenerating initrd without having to pass '--omit "resume"' (In reply to Thomas Backlund from comment #5) > do you have /etc/dracut.conf.d/51-mageia-resume.conf > > if you comment out the add_device* line there, does it work automatically > then when regenerating initrd without having to pass '--omit "resume"' The file exists but is empty. |