All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ken Drummond <linuxraid@kendrummond.com>
To: Linux RAID <linux-raid@vger.kernel.org>
Subject: Re: Help with degraded array
Date: Sun, 15 Dec 2013 20:14:13 +1000	[thread overview]
Message-ID: <52AD80F5.1080309@kendrummond.com> (raw)
In-Reply-To: <CAB1R3sgU5eOh_MTtY=7ZwWwbvQV6py2dzNFku0PKzjB4-oEuRg@mail.gmail.com>

On 15/12/2013 10:34 AM, Alex wrote:
> Hi,
>
>>    What I would do is run smartctl -t short /dev/sdc, then smartctl -a /dev/sdc
>> and make sure the drive was reported as PASSED and not in imminent failure. Then
>> run fsck on /dev/sdc2 (the partition reporting the I/O error on what was sda2 --
>> DO NOT fsck /dev/sdc3.
> I ran a short (which succeeded) then a long (which also succeeded)
> test on /dev/sdc.
>
> I realized that /dev/sdc2 is a non-raid partition mounted as /boot, so
> it can't be checked.
>
> This box is in a remote datacenter. Still think it's okay to boot remotely?
>
> Thanks,
> Alex
> --
> 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

  You could also try running a non destructive badblocks check on the 
partition "badblocks -nsv /dev/sdc3" and see if it fails again, it could 
be the cable rather than the disk that is at fault.  I would expect that 
a reboot would set the drive back to sda.


  reply	other threads:[~2013-12-15 10:14 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-13 22:11 Help with degraded array Alex
2013-12-14 10:38 ` David C. Rankin
2013-12-14 17:40   ` Alex
2013-12-14 18:25     ` David C. Rankin
2013-12-15  0:34       ` Alex
2013-12-15 10:14         ` Ken Drummond [this message]
2013-12-16 23:21         ` David C. Rankin
2013-12-18 16:49       ` Alex

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=52AD80F5.1080309@kendrummond.com \
    --to=linuxraid@kendrummond.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 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.