update-initramfs truncates initrd if MINKVER not met
Bug #101844 reported by
Soren Hansen
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
initramfs-tools (Ubuntu) |
Fix Released
|
High
|
Ben Collins |
Bug Description
Binary package hint: initramfs-tools
When update-initramfs runs it creates a backup of the current initrd. If one of the hooks has a MINKVER set that's not fulfilled, update-initramfs leaves an initrd of 0 bytes and the backup. If update-initramfs runs again, it overwrites the old backup with a new backup of the 0 bytes initrd. During an edgy->feisty userland upgrade, "update-initramfs -u" is run numerous times, nuking the current initrd, rendering the system unbootable.
Attaching a fix that restores the backup. I'm not sure, though, if restore_backup should be called only if minversion isn't met, or in all cases where update-initramfs fails.
Changed in initramfs-tools: | |
assignee: | nobody → ben-collins |
status: | Unconfirmed → Fix Committed |
To post a comment you must log in.
Attaching output of "sh -x update-initramfs -u". Output of second run is identical.