Here's the workaround I came up with.
I encountered this problem on a do-release-upgrade from Intrepid to Jaunty on
my Mythbuntu box. (RAID1 array)
<code>
no-ar...@mythbuntu:~$ cat /proc/mdstat
Personalities : [linear] [multipath] [raid0] [raid1] [raid6] [raid5] [raid4]
[raid10]
md_d0 : inactive sdc1[1](S)
488383936 blocks
unused devices: <none>
</code>
First, stop the bogus array:
<code>
no-ar...@mythbuntu:~$ sudo mdadm --misc -S /dev/md_d0
mdadm: stopped /dev/md_d0
</code>
Reassemble the array properly:
<code>
no-ar...@mythbuntu:~$ sudo mdadm --assemble -v /dev/md0 /dev/sdc1 /dev/sdb1
mdadm: looking for devices for /dev/md0
mdadm: /dev/sdc1 is identified as a member of /dev/md0, slot 1.
mdadm: /dev/sdb1 is identified as a member of /dev/md0, slot 0.
mdadm: added /dev/sdc1 to /dev/md0 as 1
mdadm: added /dev/sdb1 to /dev/md0 as 0
mdadm: /dev/md0 has been started with 2 drives.
</code>
Now you shouldn't be bummin':
<code>
no-ar...@mythbuntu:~$ cat /proc/mdstat
Personalities : [linear] [multipath] [raid0] [raid1] [raid6] [raid5] [raid4]
[raid10]
md0 : active raid1 sdb1[0] sdc1[1]
488383936 blocks [2/2] [UU]
unused devices: <none>
</code>
If you have an LVM volume on the array you can start it manually:
<code>
no-ar...@mythbuntu:~$ sudo vgchange -a y mythtv_vg
1 logical volume(s) in volume group "mythtv_vg" now active
</code>
Then make sure your volumes are mounted as per fstab:
<code>
no-ar...@mythbuntu:~$ sudo mount -a
</code>
Now, if you reboot, you STILL won't have an array (that's the bug - I guess
mdadm isn't scanning the superblocks properly.)
To get your system to activate the array on bootup, issue this command AFTER
you've activated the array manually:
<code>
no-ar...@mythbuntu:~$ sudo mdadm --detail --scan --verbose
mdadm: metadata format 00.90 unknown, ignored.
ARRAY /dev/md0 level=raid1 num-devices=2 metadata=00.90
UUID=8363b3a4:7d3241a4:826d159e:91e99981
devices=/dev/sdb1,/dev/sdc1
</code>
Copy the last two lines of your output (beginning with "ARRAY") and
paste them into your /etc/mdadm/mdadm.conf file.
Now if you reboot your array should be active.
Another source of the problem could be the metadata format of "00.90."
According to the post at
http://ubuntuforums.org/showthread.php?p=6345457#post6345457 the major
release format has changed so you might want to change "metadata=00.90"
to "metadata=0.90" in your mdadm.conf file. After you do that the
unknown format warning goes away in the mdadm detail scan (but it still
reports "metadata=00.90.")
--
md sw raid5 not detected on boot [jaunty regression]
https://bugs.launchpad.net/bugs/376984
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
