From: Mitchell Laks <mlaks@post.harvard.edu>
To: linux-raid@vger.kernel.org
Subject: raid 1 errors then I failed and removed the drive. now cant tell which one it was?
Date: Tue, 16 Apr 2013 00:27:42 -0400 [thread overview]
Message-ID: <20130416042742.GA12964@earthlink.net> (raw)
Hi,
I store lots of data on a raid1 created with mdadm on debian sid using kernel
Linux 3.2.0-2-amd64 #1 SMP Fri Apr 6 05:01:55 UTC 2012 x86_64 GNU/Linux.
Now I was backing up the data from the raid to another external drive and the errors began
[730636.445918] ata1.00: error: { UNC }
[730636.464576] ata1.00: configured for UDMA/33
[730636.464584] ata1: EH complete
[730638.110558] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[730638.115052] ata1.00: port_status 0x20200000
[730638.119441] ata1.00: failed command: READ DMA
[730638.123848] ata1.00: cmd c8/00:08:ef:9f:90/00:00:00:00:00/e1 tag 0 dma 4096 in
[730638.123850] res 51/40:00:f4:9f:90/40:00:01:00:00/e1 Emask 0x9 (media error)
[730638.132821] ata1.00: status: { DRDY ERR }
[730638.137305] ata1.00: error: { UNC }
[730638.157256] ata1.00: configured for UDMA/33
[730638.157262] ata1: EH complete
[730639.802239] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[730639.806730] ata1.00: port_status 0x20200000
[730639.811111] ata1.00: failed command: READ DMA
[730639.815511] ata1.00: cmd c8/00:08:ef:9f:90/00:00:00:00:00/e1 tag 0 dma 4096 in
[730639.815513] res 51/40:00:f4:9f:90/40:00:01:00:00/e1 Emask 0x9 (media error)
[730639.824457] ata1.00: status: { DRDY ERR }
[730639.828930] ata1.00: error: { UNC }
[730639.848936] ata1.00: configured for UDMA/33
they seemed to be coming from drive /dev/sda1 of the raid while /dev/sdb1 was ok
so i did
mdadm /dev/md0 -f /dev/sda1
mdadm /dev/md0 -r /dev/sda1
then I rsynced from the remaining drive to /dev/sdd1 an external drive. No more errors.
However I forgot to label the usable drive by creating a file on it or editing a file on it.
But now I shut down and unplug one of the two drives, then run
mdadm -E /dev/sda1
it seems to be the good (unfailed) drive
But similarly when I unplug the other drive and put this one back
i still get it listed as an unfailed drive
how can i figure out which is the failed drive and which is the remaining one????
Mitchell
next reply other threads:[~2013-04-16 4:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-16 4:27 Mitchell Laks [this message]
2013-04-16 7:46 ` raid 1 errors then I failed and removed the drive. now cant tell which one it was? Robin Hill
2013-04-15 17:20 ` Oliver Schinagl
2013-04-16 16:03 ` Roy Sigurd Karlsbakk
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=20130416042742.GA12964@earthlink.net \
--to=mlaks@post.harvard.edu \
--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