Linux RAID subsystem development
 help / color / mirror / Atom feed
From: Adam Goryachev <mailinglists@websitemanagers.com.au>
To: Hans Malissa <hmalissa@me.com>, linux-raid@vger.kernel.org
Subject: Re: RAID1 degraded
Date: Tue, 04 Aug 2015 09:48:35 +1000	[thread overview]
Message-ID: <55BFFDD3.5000005@websitemanagers.com.au> (raw)
In-Reply-To: <AA2DC53A-A663-45CE-A8FE-DF6C8C285F37@me.com>

On 04/08/15 08:18, Hans Malissa wrote:
> Hi everybody,
>
> It looks like one of my disks in my RAID1 just failed:
>
> [SNIP]
>
> 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?
>
Have a look at dmesg or your system kernel logs for details.
Also, use smartctl to examine what the drive itself thinks.
Also, try to use dd to read/write the drive.

One common scenario is that you haven't configured the timing for the 
drive correctly, and the drive is working perfectly, but didn't respond 
to the kernel quickly enough. Research SCT/ERC on this list

Regards,
Adam
-- 
Adam Goryachev Website Managers www.websitemanagers.com.au
--
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

  reply	other threads:[~2015-08-03 23:48 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-03 22:18 RAID1 degraded Hans Malissa
2015-08-03 23:48 ` Adam Goryachev [this message]
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=55BFFDD3.5000005@websitemanagers.com.au \
    --to=mailinglists@websitemanagers.com.au \
    --cc=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