Bug 610878
Summary: | mdadm blocks on boot if initrams doesn't support latest superblock of a new encrypted md device | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Kai Engert (:kaie) (inactive account) <kengert> |
Component: | mdadm | Assignee: | Doug Ledford <dledford> |
Status: | CLOSED NOTABUG | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | high | Docs Contact: | |
Priority: | low | ||
Version: | 13 | CC: | dledford, harald |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2010-07-20 16:28:20 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Kai Engert (:kaie) (inactive account)
2010-07-02 16:30:55 UTC
I'm not sure if you need to see the actual mdadm.conf The only difference is, the /dev/md0 configuration line was changed to have a new UUID. There are additional steps necessary to do what you want. Specifically, the device uuid for the root array is specified on the grub boot line as a boot parameter. So not only do you need to update the mdadm.conf file with the new uuid, you also need to modify /etc/grub.conf to reflect the new uuid so that dracut will look for it. If you don't, then what's happening is when you boot with the old drive removed, the old uuid specified on the grub boot command is simply not present and so no device is started. The reason mdadm doesn't issue an error is that mdadm is never invoked. Dracut scans for the old uuid, doesn't find it, never invokes mdadm, and then says it can't find the boot device and sleeps forever. Simply updating the grub.conf file should solve your problem. If it doesn't, then reopen the bug. |