[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: debian testing and mdadm

Just some more information:

After boot, during the recovery when I add the second disk, mdadm --examine /dev/sdb2 shows this:

      Number   Major   Minor   RaidDevice State
this     0       8       18        0      active sync   /dev/sdb2

   0     0       8       18        0      active sync   /dev/sdb2
   1     1       0        0        1      faulty removed
   2     2       8        2        1      spare   /dev/sda2

so it appears that it thinks the second device is faulty and that I'm adding /dev/sda2 as a spare.


Adam Olsen wrote:

I just recently attempted to use this method: http://synic.ath.cx/raid1.txt to create full software raid 1 on our server running debian testing. I replaced all the references to raidtools with mdadm.

It seems to be working, cat /proc/mdstat shows:

Personalities : [raid1]
md2 : active raid1 sda2[1] sdb2[0]
      155308288 blocks [2/2] [UU]

unused devices: <none>

However, when I reboot, sda2 does not come up - I have to mdadm -a /dev/md2 /dev/sda2 to get it to come up. It has to rebuild, which takes about an hour.

My /etc/mdadm/mdadm.conf looks like this:

DEVICE /dev/sda2,/dev/sdb2
ARRAY /dev/md2 level=raid1 num-devices=2 devices=/dev/sda1,/dev/sda2

How can I get /dev/sda2 to come up automatically?


Reply to: