[Bug 136252] Re: [->UUIDudev] mdadm.conf w/o ARRAY lines but udev/mdadm not assembling arrays. (boot & hotplug fails)

[ceg]

> It's surprising that initramfs-tools' init calls hostname, but doesn't
take any steps to make it available in the initramfs.

I guess it's quite sane to not have the hostname leak into the
initramfs. The initramfs stays universal to boot different root
filsystems. And if a root filesystem is encrypted, having the hostname
in initramfs might be even less desired.

The new mdadm should be able to incrementally assemble any arrays
plugged securely, without needing/doing any hostname checks on the
member devices, relying on UUIDs instead to prevent wrong assemblies. So
this hostname insertion should just be a temporary workaround, and go
away with an update to a more recent mdadm version.

-- 
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/136252

Title:
  [->UUIDudev]  mdadm.conf w/o ARRAY lines but udev/mdadm not assembling
  arrays. (boot & hotplug fails)

Status in “mdadm” package in Ubuntu:
  In Progress
Status in “mdadm” source package in Lucid:
  In Progress
Status in “mdadm” source package in Maverick:
  In Progress

Bug description:
  Binary package hint: mdadm

  Hi,

  I could not boot from my /dev/md1 -> /dev/vg01/lv_root partition,
  because the initrd could not assemble the md0 and md1 devices. After
  reading mdadm.conf, I added these two lines to my config:

  # definitions of existing MD arrays
  ARRAY /dev/md0 devices=/dev/sda1,/dev/sdb1
  ARRAY /dev/md1 devices=/dev/sda5,/dev/sdb5

  and updated initramfs. After this, the system started normally. Before
  figuring out this, I used dpkg-reconfigure mdadm. So this seems to
  produce a non working config, which is copied to the initrd.

  Kind regards

  Christian

  -> However on hotplug systems mdadm.conf should not have to contain
  any references to specific DEVICEs, ARRAYs or HOMEHOST.

  -> We need to switch to a pure and secure UUID-based raid assembly.
  The boot up scripts already support and use UUIDs, but mdadm needs to
  be convinced (-> comment #42)