mdadm raid1 stops to work after kernel panic

mdadm raid1 stops to work after kernel panic

[Federico]

Accidentally I've booted with wrong grub parameters and my systems
hanged with a kernel panic. After reboot my /dev/md2 device (raid1)
stopped to work.
These are some logs:

wax@persifae:~$cat /proc/mdstat
Personalities : [raid1]
md2 : inactive sda1[0](S)
      293049600 blocks

md1 : active raid1 sdc6[0] sdb2[1]
      152264000 blocks [2/2] [UU]

md0 : active raid1 sdb1[1] sdc5[0]
      7815488 blocks [2/2] [UU]

unused devices: <none>

wax@persifae:~$sudo mdadm -Q /dev/md2
/dev/md2: is an md device which is not active

wax@persifae:~$sudo mdadm --assemble --scan /dev/md2
mdadm: failed to add /dev/sdc1 to /dev/md2: Invalid argument
mdadm: /dev/md2 assembled from 0 drives - not enough to start the array.

wax@persifae:~$cat /etc/mdadm.conf
ARRAY /dev/md0 level=raid1 num-devices=2
UUID=2a37b0a1:4b6b28fc:0209446b:c3b28f2a
ARRAY /dev/md1 level=raid1 num-devices=2
UUID=19c49c5d:e3193aa1:657f267b:b23c2dee
ARRAY /dev/md2 level=raid1 num-devices=2
UUID=62a5cb51:36ca61a3:1298e6c2:30fde3ba

Thanks in advance for your help

Re: mdadm raid1 stops to work after kernel panic

[NeilBrown]

On Mon, May 5, 2008 4:47 pm, Federico wrote:
> Accidentally I've booted with wrong grub parameters and my systems
> hanged with a kernel panic. After reboot my /dev/md2 device (raid1)
> stopped to work.
> These are some logs:
>
> wax@persifae:~$cat /proc/mdstat
> Personalities : [raid1]
> md2 : inactive sda1[0](S)
>       293049600 blocks
>
> md1 : active raid1 sdc6[0] sdb2[1]
>       152264000 blocks [2/2] [UU]
>
> md0 : active raid1 sdb1[1] sdc5[0]
>       7815488 blocks [2/2] [UU]
>
> unused devices: <none>
>
> wax@persifae:~$sudo mdadm -Q /dev/md2
> /dev/md2: is an md device which is not active
>
> wax@persifae:~$sudo mdadm --assemble --scan /dev/md2
> mdadm: failed to add /dev/sdc1 to /dev/md2: Invalid argument
> mdadm: /dev/md2 assembled from 0 drives - not enough to start the array.
>
> wax@persifae:~$cat /etc/mdadm.conf
> ARRAY /dev/md0 level=raid1 num-devices=2
> UUID=2a37b0a1:4b6b28fc:0209446b:c3b28f2a
> ARRAY /dev/md1 level=raid1 num-devices=2
> UUID=19c49c5d:e3193aa1:657f267b:b23c2dee
> ARRAY /dev/md2 level=raid1 num-devices=2
> UUID=62a5cb51:36ca61a3:1298e6c2:30fde3ba
>

What does
  mdadm --examine /dev/sda1 /dev/sdc1

show?

NeilBrown

Re: mdadm raid1 stops to work after kernel panic

[NeilBrown]

[please don't drop the list from the cc: line - I've re-added it]

On Mon, May 5, 2008 7:56 pm, Federico wrote:
> wax@persifae:~$sudo !!
> sudo mdadm --examine /dev/sda1 /dev/sdc1

Thanks.  That looks fairly normal.  sda1 is thought to be out-of-date
so you would expect mdadm to assemble the array with just sdc1
as a member.  You would then need to add sda1 as a spare and it would
rebuild.
I wonder why it isn't including sdc1 at first.

What happens if you:
  mdadm -S /dev/md2
  mdadm -A /dev/md2 /dev/sda1 /dev/sdc1
??

NeilBrown


> Parola d'ordine:
> /dev/sda1:
>           Magic : a92b4efc
>         Version : 00.90.00
>            UUID : 62a5cb51:36ca61a3:1298e6c2:30fde3ba
>   Creation Time : Mon May  5 04:39:59 2008
>      Raid Level : raid1
>   Used Dev Size : 293049600 (279.47 GiB 300.08 GB)
>      Array Size : 293049600 (279.47 GiB 300.08 GB)
>    Raid Devices : 2
>   Total Devices : 2
> Preferred Minor : 2
>
>     Update Time : Mon May  5 06:15:31 2008
>           State : active
>  Active Devices : 2
> Working Devices : 2
>  Failed Devices : 0
>   Spare Devices : 0
>        Checksum : 27e6bd76 - correct
>          Events : 0.9
>
>
>       Number   Major   Minor   RaidDevice State
> this     0       8        1        0      active sync   /dev/sda1
>
>    0     0       8        1        0      active sync   /dev/sda1
>    1     1       8       33        1      active sync   /dev/sdc1
> /dev/sdc1:
>           Magic : a92b4efc
>         Version : 00.90.00
>            UUID : 62a5cb51:36ca61a3:1298e6c2:30fde3ba
>   Creation Time : Mon May  5 04:39:59 2008
>      Raid Level : raid1
>   Used Dev Size : 293049600 (279.47 GiB 300.08 GB)
>      Array Size : 293049600 (279.47 GiB 300.08 GB)
>    Raid Devices : 2
>   Total Devices : 1
> Preferred Minor : 0
>
>     Update Time : Mon May  5 09:16:19 2008
>           State : active
>  Active Devices : 1
> Working Devices : 1
>  Failed Devices : 0
>   Spare Devices : 0
>        Checksum : 27e6e7e5 - correct
>          Events : 0.11
>
>
>       Number   Major   Minor   RaidDevice State
> this     1       8       33        1      active sync   /dev/sdc1
>
>    0     0       0        0        0      removed
>    1     1       8       33        1      active sync   /dev/sdc1
>

Re: mdadm raid1 stops to work after kernel panic

[Federico]

>  What happens if you:
>   mdadm -S /dev/md2
>   mdadm -A /dev/md2 /dev/sda1 /dev/sdc1

root@persifae:~#mdadm -S /dev/md2
mdadm: stopped /dev/md2
root@persifae:~#mdadm -A /dev/md2 /dev/sda1 /dev/sdc1
mdadm: failed to add /dev/sdc1 to /dev/md2: Invalid argument
mdadm: /dev/md2 assembled from 0 drives - not enough to start the array.

Re: mdadm raid1 stops to work after kernel panic

[Neil Brown]

On Monday May 5, undicizeri@gmail.com wrote:
> >  What happens if you:
> >   mdadm -S /dev/md2
> >   mdadm -A /dev/md2 /dev/sda1 /dev/sdc1
> 
> root@persifae:~#mdadm -S /dev/md2
> mdadm: stopped /dev/md2
> root@persifae:~#mdadm -A /dev/md2 /dev/sda1 /dev/sdc1
> mdadm: failed to add /dev/sdc1 to /dev/md2: Invalid argument
> mdadm: /dev/md2 assembled from 0 drives - not enough to start the array.

Ahhh... They have a different "preferred minor".  Presumably when you
tried to boot with the wrong grub parameters it tried to assemble the
array as /dev/md0 instead of /dev/md2.

You can fix with:

  mdadm -A /dev/md2 /dev/sdc1
  mdadm /dev/md2 -a /dev/sda1

NeilBrown

Re: mdadm raid1 stops to work after kernel panic

[Federico]

Yeah! thank you for your help! :D

2008/5/6 Neil Brown <neilb@suse.de>:
>
> On Monday May 5, undicizeri@gmail.com wrote:
>  > >  What happens if you:
>  > >   mdadm -S /dev/md2
>  > >   mdadm -A /dev/md2 /dev/sda1 /dev/sdc1
>  >
>  > root@persifae:~#mdadm -S /dev/md2
>  > mdadm: stopped /dev/md2
>  > root@persifae:~#mdadm -A /dev/md2 /dev/sda1 /dev/sdc1
>  > mdadm: failed to add /dev/sdc1 to /dev/md2: Invalid argument
>  > mdadm: /dev/md2 assembled from 0 drives - not enough to start the array.
>
>  Ahhh... They have a different "preferred minor".  Presumably when you
>  tried to boot with the wrong grub parameters it tried to assemble the
>  array as /dev/md0 instead of /dev/md2.
>
>  You can fix with:
>
>   mdadm -A /dev/md2 /dev/sdc1
>   mdadm /dev/md2 -a /dev/sda1
>
>  NeilBrown
>