Public bug reported:

A raid-1 array has two members:
a. a regular partition
b. a raid0 array consisting of two members

If you have a drive with msdos partition label, partitions are limited to 2 TiB.
- using a raid-0 array constructs a raid array that can be larger than 2 TiB
raid-1 brings redundancy with the all data contained in each member

(I have an old bios that does not allow for gtp partition labels and
barely boots with large drives)

On boot the following commands must be executed, or mdadm leaves the resulting 
array inactive:
/sbin/mdadm --incremental /dev/md44 --scan --run
/sbin/mdadm --manage /dev/md44 --add /dev/md41

- the first line starts the array in auto read-only
- the second line adds the second member so the array is complete [UU]

/dev/md44 is raid1
/dev/md41 is raid0

mdadm appears to not be looking at its started arrays for array members.
Ubuntu 13.04

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

** Package changed: ubuntu => mdadm (Ubuntu)

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

Title:
  array of array inactive on boot

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

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to