Comment 2 for bug 573477

I'm experiencing something somewhat similar on a home server of ours. The four partitions (/, /boot. /home, /var) are all MD RAID1 arrays.

On a reboot yesterday morning, the MD array /boot was on failed to start. This morning, it was the /home array.

When I logged in this morning, /home was not mounted. The reason was that the MD array was down:

gavin@robin:/$ sudo mdadm --detail /dev/md3
/dev/md3:
        Version : 00.90
  Creation Time : Mon Sep 18 23:27:46 2006
     Raid Level : raid1
  Used Dev Size : 292439104 (278.89 GiB 299.46 GB)
   Raid Devices : 2
  Total Devices : 2
Preferred Minor : 3
    Persistence : Superblock is persistent

    Update Time : Thu May 6 23:43:34 2010
          State : active, Not Started
 Active Devices : 2
Working Devices : 2
 Failed Devices : 0
  Spare Devices : 0

           UUID : 0019b5ec:1ad12c80:0df67ddf:f4706d12
         Events : 0.4177842

    Number Major Minor RaidDevice State
       0 8 7 0 active sync /dev/sda7
       1 8 23 1 active sync /dev/sdb7

I then ran:

gavin@robin:/$ sudo mdadm --stop /dev/md3
mdadm: stopped /dev/md3
gavin@robin:/$ sudo mdadm --assemble /dev/md3
mdadm: /dev/md3 has been started with 2 drives.

mounted the drive and all was well. However, there definitely seems to be some problem with the MD raid arrays.

Any suggestions for what to look at. I found this bug via this thread which seems to have some more people seeing similar issues:

http://ubuntuforums.org/showthread.php?p=9240332

Gavin