[Bug 330399] Re: [->UUIDudev] "HOMEHOST <system>" does not work inside initrd

[JC]

*** This bug is a duplicate of bug 136252 ***
    https://bugs.launchpad.net/bugs/136252

** This bug has been marked a duplicate of bug 136252
   [->UUIDudev]  mdadm.conf w/o ARRAY lines but udev/mdadm not assembling arrays. (boot & hotplug fails)

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to mdadm in Ubuntu.
https://bugs.launchpad.net/bugs/330399

Title:
  [->UUIDudev] "HOMEHOST <system>" does not work inside initrd

Status in “mdadm” package in Ubuntu:
  Confirmed

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/mdadm.conf specifies "HOMEHOST <system>", and no
  information on the structure of the RAID1 device. (The intent, of
  course, is to have mdadm auto-assemble it.) The RAID1 device
  superblocks have the homehost properly set to the current system
  hostname.

  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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/330399/+subscriptions