[->UUIDudev] "HOMEHOST <system>" does not work inside initrd
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
mdadm (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: mdadm
This concerns mdadm 2.6.7-3ubuntu8 in Intrepid.
I have a system with "/" on a RAID1 device.
/etc/mdadm/
The system fails to boot in this configuration. Why? Because a homehost of "<system>" means that the current system hostname (as returned by gethostname()) is used, and yet in the initrd environment, _no hostname is set_. You run "hostname" at the BusyBox prompt, and you get "(none)".
The workaround is to hard-code the hostname as HOMEHOST in mdadm.conf (and re-generate the initrd image). The fix would be to have initrd pull in /etc/hostname and any other requisite bits so that the system hostname is available in the initrd environment, so that "HOMEHOST <system>" works as intended.
This should be no issue with UUID-based raid assembly that makes mdadm.conf ARRAY definition maintenance obsolete. Bug #158918