Problem with Software RAID5

Problem with Software RAID5

[Lars Schimmer]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi!

I´ve got a problem with a software raid5.
PC runs debian sarge/sid/etch mix with 2.6.16 self built and mdadm mdadm
2.5.3.git200608202239-7.
1 of 6 SATA 400GB drives failes and I rebooted the PC.
After reboot RAID was resyncing.
But again the HD died and the PC rebooted again, I pulled off the bad HD
and now the RAID5 won´t resync again.
I built a 2.6.17 kernel and replaced mdadm to  mdadm 2.5.4-1 and still
RAID5 won´t resync again:
cat /proc/mdstat
Personalities : [linear] [raid0] [raid1] [raid10] [raid5] [raid4]
[raid6] [multipath] [faulty]
md0 : inactive sda1[0] sde1[5] sdd1[4] sdc1[3] sdb1[1]
      1953543680 blocks

unused devices: <none>

 mdadm --detail /dev/md0
/dev/md0:
        Version : 00.90.03
  Creation Time : Fri May 12 16:10:24 2006
     Raid Level : raid5
    Device Size : 390708736 (372.61 GiB 400.09 GB)
   Raid Devices : 6
  Total Devices : 5
Preferred Minor : 0
    Persistence : Superblock is persistent

    Update Time : Tue Oct 17 14:11:56 2006
          State : active, degraded, Not Started
 Active Devices : 5
Working Devices : 5
 Failed Devices : 0
  Spare Devices : 0

         Layout : left-symmetric
     Chunk Size : 256K

           UUID : 5ce125ae:b76d7567:a531953b:fbba92fc
         Events : 0.2818447

    Number   Major   Minor   RaidDevice State
       0       8        1        0      active sync   /dev/sda1
       1       8       17        1      active sync   /dev/sdb1
       2       0        0        2      removed
       3       8       33        3      active sync   /dev/sdc1
       4       8       49        4      active sync   /dev/sdd1
       5       8       65        5      active sync   /dev/sde1

mdadm --stop /dev/md0
mdadm: stopped /dev/md0

sinope:~# mdadm --assemble /dev/md0
mdadm: failed to RUN_ARRAY /dev/md0: Input/output error

Any hints? tips?


MfG,
Lars Schimmer
- --
- -------------------------------------------------------------
TU Graz, Institut für ComputerGraphik & WissensVisualisierung
Tel: +43 316 873-5405       E-Mail: l.schimmer@cgv.tugraz.at
Fax: +43 316 873-5402       PGP-Key-ID: 0x4A9B1723
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFFNfZgmWhuE0qbFyMRAqBBAJoCcE4gMx83NQl8pksSqgEpBHWNiACfTpKr
NVHtinnXRPIbY2Rfv3BUC0s=
=svsf
-----END PGP SIGNATURE-----
-
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: Problem with Software RAID5

[Neil Brown]

On Wednesday October 18, l.schimmer@cgv.tugraz.at wrote:
> 
> Any hints? tips?
> 

If you crash and lose a drive at the same time you could have
undetectable data corruption.  If you are willing to accept that use
'--force'

  mdadm --assemble --force /dev/md0

Hopefully mdadm-2.6 will give a more useful error message here.

NeilBrown

problem with software RAID5

[Lars Schimmer]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi!

I run a 3 disk RAID5 on a debian 2.6.26 machine.

Last weekend one of that disk went bad and the raid went on with 2 disks.

Now I restarted and added the 3d disk and the RAID5 went crazy, callind
disks after disk faulty and (S)... and I do not know why.

Information:

mdadm -E /dev/md1 /dev/sde1
mdadm: No md superblock detected on /dev/md1.
/dev/sde1:
          Magic : a92b4efc
        Version : 00.90.02
           UUID : d9fde523:3bcc01a6:041868f5:0ec5fcb6
  Creation Time : Tue Jan 17 14:30:37 2006
     Raid Level : raid5
  Used Dev Size : 976759936 (931.51 GiB 1000.20 GB)
     Array Size : 1953519872 (1863.02 GiB 2000.40 GB)
   Raid Devices : 3
  Total Devices : 3
Preferred Minor : 1

    Update Time : Thu Dec 11 14:46:37 2008
          State : clean
 Active Devices : 2
Working Devices : 3
 Failed Devices : 0
  Spare Devices : 1
       Checksum : 9972dbb9 - correct
         Events : 2851680

         Layout : left-symmetric
     Chunk Size : 128K

      Number   Major   Minor   RaidDevice State
this     1       8       65        1      active sync   /dev/sde1

   0     0       0        0        0      removed
   1     1       8       65        1      active sync   /dev/sde1
   2     2       8       97        2      active sync   /dev/sdg1
   3     3       8       49        3      spare   /dev/sdd1


trinculo:~# mdadm -E /dev/md1 /dev/sdg1
mdadm: No md superblock detected on /dev/md1.
/dev/sdg1:
          Magic : a92b4efc
        Version : 00.90.02
           UUID : d9fde523:3bcc01a6:041868f5:0ec5fcb6
  Creation Time : Tue Jan 17 14:30:37 2006
     Raid Level : raid5
  Used Dev Size : 976759936 (931.51 GiB 1000.20 GB)
     Array Size : 1953519872 (1863.02 GiB 2000.40 GB)
   Raid Devices : 3
  Total Devices : 2
Preferred Minor : 1

    Update Time : Thu Dec 11 14:55:06 2008
          State : clean
 Active Devices : 1
Working Devices : 1
 Failed Devices : 1
  Spare Devices : 0
       Checksum : 9972ddaf - correct
         Events : 2851688

         Layout : left-symmetric
     Chunk Size : 128K

      Number   Major   Minor   RaidDevice State
this     2       8       97        2      active sync   /dev/sdg1

   0     0       0        0        0      removed
   1     1       0        0        1      faulty removed
   2     2       8       97        2      active sync


mdadm -E /dev/md1 /dev/sdd1
mdadm: No md superblock detected on /dev/md1.
/dev/sdd1:
          Magic : a92b4efc
        Version : 00.90.02
           UUID : d9fde523:3bcc01a6:041868f5:0ec5fcb6
  Creation Time : Tue Jan 17 14:30:37 2006
     Raid Level : raid5
  Used Dev Size : 976759936 (931.51 GiB 1000.20 GB)
     Array Size : 1953519872 (1863.02 GiB 2000.40 GB)
   Raid Devices : 3
  Total Devices : 3
Preferred Minor : 1

    Update Time : Thu Dec 11 14:46:49 2008
          State : clean
 Active Devices : 1
Working Devices : 2
 Failed Devices : 1
  Spare Devices : 1
       Checksum : 9972dbca - correct
         Events : 2851686

         Layout : left-symmetric
     Chunk Size : 128K

      Number   Major   Minor   RaidDevice State
this     3       8       49        3      spare   /dev/sdd1

   0     0       0        0        0      removed
   1     1       0        0        1      faulty removed
   2     2       8       97        2      active sync   /dev/sdg1
   3     3       8       49        3      spare   /dev/sdd1


In which /dev/sdd went bad and was offline.

How can I try to reassemble that raid5?

MfG,
Lars Schimmer
- --
- -------------------------------------------------------------
TU Graz, Institut für ComputerGraphik & WissensVisualisierung
Tel: +43 316 873-5405       E-Mail: l.schimmer@cgv.tugraz.at
Fax: +43 316 873-5402       PGP-Key-ID: 0x4A9B1723
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAklBHasACgkQmWhuE0qbFyM1ugCeMwRpI6mv8rps8B51l4sNxBZo
KH0An3OsTEOlKtoQugxiE7pC5S7xnQl2
=7rDg
-----END PGP SIGNATURE-----
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: problem with software RAID5

[Justin Piszcz]

On Thu, 11 Dec 2008, Lars Schimmer wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Hi!
>
> I run a 3 disk RAID5 on a debian 2.6.26 machine.
>
> Last weekend one of that disk went bad and the raid went on with 2 disks.
>
> Now I restarted and added the 3d disk and the RAID5 went crazy, callind
> disks after disk faulty and (S)... and I do not know why.
>

Sounds like you want to try:
mdadm --assemble --force /dev/md1 /dev/sde1 /dev/sdg1 missing

When you do it, it should look like this (example)
# mdadm --assemble --force /dev/md3 /dev/sd[c-l]1 
mdadm: forcing event count in /dev/sdd1(1) from 151848 upto 151856 -> mdadm: clearing FAULTY flag for device 1 in /dev/md3 for /dev/sdd1 
mdadm: /dev/md3 has been started with 9 drives (out of 10) and 1 spare.

Justin.