From: Markus Krainz <ldm@gmx.at>
To: linux-raid@vger.kernel.org
Subject: Building new RAID5 results in removed and failed devices
Date: Thu, 24 Jun 2010 22:26:33 +0200 [thread overview]
Message-ID: <4C23BF79.2070009@gmx.at> (raw)
1. I delete my old array md0
2. Then I create a new one as md1
3. The new md1 is not ok and shows removed, faulty and spare devices.
5. I tried this serveral times now, but i always get the same issue.
I am at my wits end and would very much appreciate your advice. Thank
you in advance.
This is what I did:
/dev/ mdadm --stop md0
mdadm: stopped md0
/dev/ mdadm --remove md0
/dev/ mdadm --detail md0
mdadm: md device md0 does not appear to be active.
/dev/ mdadm --zero-superblock /dev/sdd1
/dev/ mdadm --zero-superblock /dev/sdc1
mdadm: Unrecognised md component device - /dev/sdc1
/dev/ mdadm --zero-superblock /dev/sdb1
/dev/ mdadm --create --verbose /dev/md1 --chunk=64 --level=5
--raid-devices=2 /dev/sdd1 /dev/sdb1
mdadm: layout defaults to left-symmetric
mdadm: size set to 1953511936K
mdadm: array /dev/md1 started.
/dev/ mdadm --detail md1
md1:
Version : 00.90
Creation Time : Thu Jun 24 15:17:51 2010
Raid Level : raid5
Array Size : 1953511936 (1863.01 GiB 2000.40 GB)
Used Dev Size : 1953511936 (1863.01 GiB 2000.40 GB)
Raid Devices : 2
Total Devices : 2
Preferred Minor : 1
Persistence : Superblock is persistent
Update Time : Thu Jun 24 17:23:46 2010
State : clean, degraded, recovering
Active Devices : 1
Working Devices : 2
Failed Devices : 0
Spare Devices : 1
Layout : left-symmetric
Chunk Size : 64K
Rebuild Status : 36% complete
UUID : d83aec6d:a71a2345:4cbed0ec:a797be60 (local to host
d-serv)
Events : 0.12
Number Major Minor RaidDevice State
0 8 49 0 active sync /dev/sdd1
2 8 17 1 spare rebuilding /dev/sdb1
/dev/ mdadm --detail md1
md1:
Version : 00.90
Creation Time : Thu Jun 24 15:17:51 2010
Raid Level : raid5
Array Size : 1953511936 (1863.01 GiB 2000.40 GB)
Used Dev Size : 1953511936 (1863.01 GiB 2000.40 GB)
Raid Devices : 2
Total Devices : 2
Preferred Minor : 1
Persistence : Superblock is persistent
Update Time : Thu Jun 24 18:04:28 2010
State : clean, degraded
Active Devices : 0
Working Devices : 1
Failed Devices : 1
Spare Devices : 1
Layout : left-symmetric
Chunk Size : 64K
Number Major Minor RaidDevice State
0 0 0 0 removed
1 0 0 1 removed
2 8 17 - spare /dev/sdb1
3 8 49 - faulty spare /dev/sdd1
next reply other threads:[~2010-06-24 20:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-24 20:26 Markus Krainz [this message]
2010-06-24 21:03 ` Building new RAID5 results in removed and failed devices Dan Williams
2010-06-24 22:23 ` Markus Krainz
2010-06-24 21:38 ` Robin Hill
2010-06-24 22:10 ` Markus Krainz
2010-06-25 4:06 ` Mikael Abrahamsson
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=4C23BF79.2070009@gmx.at \
--to=ldm@gmx.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox