From: "Brian J. Murrell" <brian@interlinx.bc.ca>
To: linux-raid@vger.kernel.org
Subject: raid1 recoverable after system crash?
Date: Thu, 07 Apr 2016 08:44:46 -0400 [thread overview]
Message-ID: <1460033086.27740.145.camel@interlinx.bc.ca> (raw)
[-- Attachment #1: Type: text/plain, Size: 4193 bytes --]
Hi
I had a system crash. When it came back up, one of my arrays was
degraded:
# cat /proc/mdstat
Personalities : [linear] [multipath] [raid0] [raid1] [raid6] [raid5] [raid4] [raid10]
md0 : active raid1 sdd[0]
1953514496 blocks [2/1] [U_]
md1 : active raid0 sdc[1] sdb[0]
1953524736 blocks super 1.2 512k chunks
unused devices: <none>
md1 is supposed to be a member of md0 but it's not currently:
/dev/md0:
Version : 0.90
Creation Time : Mon Jan 26 19:51:38 2009
Raid Level : raid1
Array Size : 1953514496 (1863.02 GiB 2000.40 GB)
Used Dev Size : 1953514496 (1863.02 GiB 2000.40 GB)
Raid Devices : 2
Total Devices : 1
Preferred Minor : 0
Persistence : Superblock is persistent
Update Time : Thu Apr 7 08:19:25 2016
State : clean, degraded
Active Devices : 1
Working Devices : 1
Failed Devices : 0
Spare Devices : 0
UUID : 2f8fc5e0:a0eb646a:2303d005:33f25f21
Events : 0.5030755
Number Major Minor RaidDevice State
0 8 48 0 active sync /dev/sdd
1 0 0 1 removed
It doesn't seem to be re-addable:
# mdadm --stop /dev/md0
mdadm: stopped /dev/md0
# mdadm --manage /dev/md0 --re-add /dev/md1
mdadm: --re-add for /dev/md1 to /dev/md0 is not possible
It doesn't seem to be assemble-able:
# mdadm --stop /dev/md0
mdadm: stopped /dev/md0
# mdadm --assemble /dev/md0 /dev/sdd /dev/md1
mdadm: /dev/md0 has been started with 1 drive (out of 2).
even when forced:
# mdadm --stop /dev/md0
mdadm: stopped /dev/md0
# mdadm --assemble --force /dev/md0 /dev/sdd /dev/md1
mdadm: /dev/md0 has been started with 1 drive (out of 2).
Is my only option here to fail/remove /dev/md1 from the array and re-
add it that way or is there a more graceful recovery possible here?
Some additional info:
mdadm --examine /dev/md1
/dev/md1:
Magic : a92b4efc
Version : 0.90.00
UUID : 2f8fc5e0:a0eb646a:2303d005:33f25f21
Creation Time : Mon Jan 26 19:51:38 2009
Raid Level : raid1
Used Dev Size : 1953514496 (1863.02 GiB 2000.40 GB)
Array Size : 1953514496 (1863.02 GiB 2000.40 GB)
Raid Devices : 2
Total Devices : 2
Preferred Minor : 0
Update Time : Thu Apr 7 00:18:47 2016
State : active
Active Devices : 2
Working Devices : 2
Failed Devices : 0
Spare Devices : 0
Checksum : e5ddeac5 - correct
Events : 5030737
Number Major Minor RaidDevice State
this 1 9 1 1 active sync /dev/md1
0 0 8 48 0 active sync /dev/sdd
1 1 9 1 1 active sync /dev/md1
# mdadm --examine /dev/sdd
/dev/sdd:
Magic : a92b4efc
Version : 0.90.00
UUID : 2f8fc5e0:a0eb646a:2303d005:33f25f21
Creation Time : Mon Jan 26 19:51:38 2009
Raid Level : raid1
Used Dev Size : 1953514496 (1863.02 GiB 2000.40 GB)
Array Size : 1953514496 (1863.02 GiB 2000.40 GB)
Raid Devices : 2
Total Devices : 1
Preferred Minor : 0
Update Time : Thu Apr 7 08:37:04 2016
State : clean
Active Devices : 1
Working Devices : 1
Failed Devices : 1
Spare Devices : 0
Checksum : e62b232b - correct
Events : 5030757
Number Major Minor RaidDevice State
this 0 8 48 0 active sync /dev/sdd
0 0 8 48 0 active sync /dev/sdd
1 1 0 0 1 faulty removed
Most happy to provide any additional information needed.
Cheers,
b.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next reply other threads:[~2016-04-07 12:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-07 12:44 Brian J. Murrell [this message]
2016-04-07 13:00 ` raid1 recoverable after system crash? Roman Mamedov
2016-04-07 16:11 ` Brian J. Murrell
2016-04-07 16:59 ` Roman Mamedov
2016-04-07 17:10 ` Brian J. Murrell
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=1460033086.27740.145.camel@interlinx.bc.ca \
--to=brian@interlinx.bc.ca \
--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.