[Bug 940050] [NEW] software raid doesn't assemble before mount on boot

[Stephan Fabel]

Public bug reported:

I've configured a Software RAID5 using three hard drives and mdadm. The
RAID works, I can access the data, however for some reason it does not
"assemble" on boot, and the automount subsequently fails with and error
message offering me to Ignore or Skip the mounting process. Turns out
that after booting, the device /dev/md0 does not exist on my system.

I've configured /etc/mdadm/mdadm.conf (attached), ran "mdadm -As
/dev/md0" as suggested by various guides around the web and added
raid456 to /etc/modules in the hopes that this would somehow make it
work but to no avail.

In my /etc/fstab I'm not refering to the RAID as /dev/md0, but instead
use the UUID of md0.

My workaround currently is this:

Once I login, I can issue

# mdadm --assemble --scan

and it creates my /dev/md0 which is then accessible and works without a
problem.

** Affects: mdadm (Ubuntu)
     Importance: Undecided
         Status: New


** Tags: automount mdadm raid software

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

Title:
  software raid doesn't assemble before mount on boot

Status in “mdadm” package in Ubuntu:
  New

Bug description:
  I've configured a Software RAID5 using three hard drives and mdadm.
  The RAID works, I can access the data, however for some reason it does
  not "assemble" on boot, and the automount subsequently fails with and
  error message offering me to Ignore or Skip the mounting process.
  Turns out that after booting, the device /dev/md0 does not exist on my
  system.

  I've configured /etc/mdadm/mdadm.conf (attached), ran "mdadm -As
  /dev/md0" as suggested by various guides around the web and added
  raid456 to /etc/modules in the hopes that this would somehow make it
  work but to no avail.

  In my /etc/fstab I'm not refering to the RAID as /dev/md0, but instead
  use the UUID of md0.

  My workaround currently is this:

  Once I login, I can issue

  # mdadm --assemble --scan

  and it creates my /dev/md0 which is then accessible and works without
  a problem.

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