From: Hans Malissa <hmalissa@me.com>
To: linux-raid@vger.kernel.org
Subject: RAID1 degraded
Date: Mon, 03 Aug 2015 16:18:02 -0600 [thread overview]
Message-ID: <AA2DC53A-A663-45CE-A8FE-DF6C8C285F37@me.com> (raw)
Hi everybody,
It looks like one of my disks in my RAID1 just failed:
# cat /proc/mdstat
Personalities : [raid1]
md0 : active raid1 sdc1[1](F) sdb1[0]
976629568 blocks super 1.2 [2/1] [U_]
unused devices: <none>
and
# mdadm --detail /dev/md0
/dev/md0:
Version : 1.2
Creation Time : Sun May 17 15:21:30 2015
Raid Level : raid1
Array Size : 976629568 (931.39 GiB 1000.07 GB)
Used Dev Size : 976629568 (931.39 GiB 1000.07 GB)
Raid Devices : 2
Total Devices : 2
Persistence : Superblock is persistent
Update Time : Mon Aug 3 16:13:56 2015
State : clean, degraded
Active Devices : 1
Working Devices : 1
Failed Devices : 1
Spare Devices : 0
Name : eprb21:0
UUID : 0901fe50:444a29b6:d3caff14:e45ef9cc
Events : 7619
Number Major Minor RaidDevice State
0 8 17 0 active sync /dev/sdb1
1 0 0 1 removed
1 8 33 - faulty /dev/sdc1
Looks like there’s something wrong with /dev/sdc1:
# mdadm --examine /dev/sdb1
/dev/sdb1:
Magic : a92b4efc
Version : 1.2
Feature Map : 0x0
Array UUID : 0901fe50:444a29b6:d3caff14:e45ef9cc
Name : eprb21:0
Creation Time : Sun May 17 15:21:30 2015
Raid Level : raid1
Raid Devices : 2
Avail Dev Size : 1953259520 (931.39 GiB 1000.07 GB)
Array Size : 976629568 (931.39 GiB 1000.07 GB)
Used Dev Size : 1953259136 (931.39 GiB 1000.07 GB)
Data Offset : 262144 sectors
Super Offset : 8 sectors
State : clean
Device UUID : 3e6d5330:3ee6ef06:2acf46ad:44513d37
Update Time : Mon Aug 3 16:14:32 2015
Checksum : d474a441 - correct
Events : 7627
Device Role : Active device 0
Array State : A. ('A' == active, '.' == missing)
and
# mdadm --examine /dev/sdc1
mdadm: No md superblock detected on /dev/sdc1.
The file system seems to be ok for the time being:
# fsck -n /dev/md0
fsck from util-linux 2.21.2
e2fsck 1.42.6 (21-Sep-2012)
Warning! /dev/md0 is mounted.
Warning: skipping journal recovery because doing a read-only filesystem check.
/dev/md0: clean, 218192/61046784 files, 213484777/244157392 blocks
Are there any other tests I could run in order to figure out what’s going on? It looks like I will have to replace /dev/sdc1 with a new hard drive. What is the correct procedure to do so without loosing my data?
Best regards, and thanks a lot,
Hans--
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
next reply other threads:[~2015-08-03 22:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-03 22:18 Hans Malissa [this message]
2015-08-03 23:48 ` RAID1 degraded Adam Goryachev
2015-08-04 4:16 ` Hans Malissa
2015-08-04 4:33 ` Adam Goryachev
2015-08-04 5:55 ` Hans Malissa
2015-08-04 14:38 ` Anthonys Lists
2015-08-04 15:56 ` Robert L Mathews
[not found] ` <A5793A94-EC9B-4221-A420-9E39EF0ABEEC@me.com>
2015-08-04 6:02 ` Adam Goryachev
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=AA2DC53A-A663-45CE-A8FE-DF6C8C285F37@me.com \
--to=hmalissa@me.com \
--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