From: Wols Lists <antlists@youngman.org.uk>
To: Rickard Svensson <myhex2020@gmail.com>, linux-raid@vger.kernel.org
Subject: Re: Debian Squeeze raid 1 0
Date: Tue, 14 Jan 2020 07:23:58 +0000 [thread overview]
Message-ID: <5E1D6C8E.8030607@youngman.org.uk> (raw)
In-Reply-To: <CAC4UdkbjUVSpkBM88HB0UJMqXh+Pd7CRLaya=s81xMGs-9+m_Q@mail.gmail.com>
On 13/01/20 23:34, Rickard Svensson wrote:
> Hi all
>
> One disk in my raid 1 0 failed the other night.
> It has been running for +8 years, on my server, a Debian Squeeze.
8 years old, debian squeeze, what version of mdadm is that.
> (And yes, I was just about to update them, bought the HD's and everything)
>
Great. First things first, ddrescue all drives on to the new ones! I
think recovering your data won't be too hard, so might as well back up
the data on to your new drives then recover that.
> I thought that i would be able to backup the data, but i got ext4
> error aswell, and when i tried to repair that with fsck i got:
> "
> # fsck -n /dev/md0
> fsck.ext4: Attempt to read block from filesystem resulted in short
> read while trying to open /dev/md0
> Could this be a zero-length partition?
> "
My fu isn't good here but I strongly suspect the read failed with an
"array not running" problem ...
>
> So i am wondering if my mdadm raid is okay.
> The "State [clean|active]" and "Array State : AA.." is not so easy
> to interpret, tried to read parts of the threads, but at the same time
> is worried that more disks should failt... And I'm starting to get
> really stressed :(
All the more reason to ddrescue your disks ...
>
> All the disk are the same type. And apparently does not support SCT,
> which I was not aware of before.
> /dev/sde2 seems to be gone.
>
Can you check the drive in another system? Is it the drive, or is it a
controller issue?
The fact that the three event counts we have are near-identical is a
good sign. The worry is that sde2 disappeared a long time ago - have you
been monitoring the system? If you ddrescue it will it give an event
count almost the same as the others? If it does, that makes me suspect a
controller issue has knocked two drives out, one of which has recovered
and the other hasn't ...
> "
> cat /proc/mdstat
> Personalities : [raid10]
> md0 : active raid10 sda2[0] sde2[3](F) sdc2[2](F) sdb2[1]
> 5840999424 blocks super 1.2 512K chunks 2 near-copies [4/2] [UU__]
> "
<snip>
>
>
> I really hope someone can help me!
>
https://raid.wiki.kernel.org/index.php/Linux_Raid#When_Things_Go_Wrogn
Note that when it says "use the latest version of mdadm" it means it - I
suspect your version may be well out-of-date.
Give us a bit more information, especially the version of mdadm you're
using. See if you can ddrescue /dev/sde, and what that tells us, and I
strongly suspect a forced assembly of (copies of) your surviving disks
will recover almost everything.
Cheers,
Wol
next prev parent reply other threads:[~2020-01-14 7:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-13 23:34 Debian Squeeze raid 1 0 Rickard Svensson
2020-01-14 7:23 ` Wols Lists [this message]
2020-01-14 8:08 ` Gandalf Corvotempesta
2020-01-14 23:11 ` Rickard Svensson
2020-01-15 0:06 ` Wols Lists
2020-01-16 10:41 ` Rickard Svensson
2020-01-28 21:57 ` Rickard Svensson
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=5E1D6C8E.8030607@youngman.org.uk \
--to=antlists@youngman.org.uk \
--cc=linux-raid@vger.kernel.org \
--cc=myhex2020@gmail.com \
/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