All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lars Schimmer <l.schimmer@cgv.tugraz.at>
To: linux-raid@vger.kernel.org
Subject: Problem with Software RAID5
Date: Wed, 18 Oct 2006 11:39:44 +0200	[thread overview]
Message-ID: <4535F660.90901@cgv.tugraz.at> (raw)

-----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

             reply	other threads:[~2006-10-18  9:39 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-18  9:39 Lars Schimmer [this message]
2006-10-23  4:35 ` Problem with Software RAID5 Neil Brown
2006-10-24 10:33 ` Raid5 or 6 here... ? Gordon Henderson
2006-10-24 14:34   ` David Greaves
2006-10-24 14:45     ` Gordon Henderson
2006-10-24 14:50     ` David Greaves
  -- strict thread matches above, loose matches on Subject: below --
2008-12-11 14:03 problem with software RAID5 Lars Schimmer
2008-12-11 18:08 ` Justin Piszcz

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4535F660.90901@cgv.tugraz.at \
    --to=l.schimmer@cgv.tugraz.at \
    --cc=linux-raid@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.