From: "Stefan G. Weichinger" <lists@xunil.at>
To: linux-raid@vger.kernel.org
Subject: Re: emergency call for help: raid5 fallen apart
Date: Wed, 24 Feb 2010 18:02:04 +0100 [thread overview]
Message-ID: <4B855B8C.8080802@xunil.at> (raw)
In-Reply-To: <4B855987.1010605@xunil.at>
sda fails also:
Feb 24 17:57:42 server-gentoo ata1.00: configured for UDMA/133
Feb 24 17:57:42 server-gentoo sd 0:0:0:0: [sda] Result: hostbyte=0x00
driverbyte=0x08
Feb 24 17:57:42 server-gentoo sd 0:0:0:0: [sda] Sense Key : 0x3
[current] [descriptor]
Feb 24 17:57:42 server-gentoo Descriptor sense data with sense
descriptors (in hex):
Feb 24 17:57:42 server-gentoo 72 03 11 04 00 00 00 0c 00 0a 80 00 00 00
00 00
Feb 24 17:57:42 server-gentoo 01 3c ba 1a
Feb 24 17:57:42 server-gentoo sd 0:0:0:0: [sda] ASC=0x11 ASCQ=0x4
Feb 24 17:57:42 server-gentoo end_request: I/O error, dev sda, sector
20757018
Feb 24 17:57:42 server-gentoo raid5:md4: read error not correctable
(sector 1032 on sda4).
Feb 24 17:57:42 server-gentoo raid5: Disk failure on sda4, disabling
device. Operation continuing on 1 devices
Feb 24 17:57:42 server-gentoo raid5:md4: read error not correctable
(sector 1040 on sda4).
Feb 24 17:57:42 server-gentoo raid5:md4: read error not correctable
(sector 1048 on sda4).
(sector 1072 on sda4).
So I am down to one drive, from 3 ...
:-(
Does it make sense to repeat:
mdadm --assemble
xfs_repair
mount
and rsync stuff aside until it fails again?
I once was lucky with such a strategy ...
S
next prev parent reply other threads:[~2010-02-24 17:02 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-24 14:54 emergency call for help: raid5 fallen apart Stefan G. Weichinger
2010-02-24 15:05 ` Stefan G. Weichinger
2010-02-24 15:22 ` Robin Hill
2010-02-24 15:32 ` Stefan G. Weichinger
2010-02-24 16:38 ` Stefan G. Weichinger
2010-02-24 16:53 ` Stefan G. Weichinger
2010-02-24 17:02 ` Stefan G. Weichinger [this message]
2010-02-25 8:05 ` Giovanni Tessore
2010-02-25 16:27 ` Stefan /*St0fF*/ Hübner
2010-02-25 16:45 ` John Robinson
2010-02-25 17:41 ` Dawning Sky
2010-02-25 18:31 ` John Robinson
2010-02-26 2:42 ` Michael Evans
2010-02-26 20:15 ` Bill Davidsen
2010-02-28 11:50 ` Stefan /*St0fF*/ Hübner
2010-02-28 12:52 ` Stefan /*St0fF*/ Hübner
2010-02-24 17:09 ` Robin Hill
2010-02-24 17:28 ` Stefan G. Weichinger
2010-02-24 17:35 ` Stefan G. Weichinger
2010-02-24 18:12 ` Robin Hill
2010-02-24 19:54 ` Stefan G. Weichinger
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=4B855B8C.8080802@xunil.at \
--to=lists@xunil.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.