From: Roman Mamedov <rm@romanrm.ru>
To: "Mathias Burén" <mathias.buren@gmail.com>
Cc: Linux-RAID <linux-raid@vger.kernel.org>
Subject: Re: HDD reports errors while completing RAID6 array check
Date: Sat, 11 Jun 2011 00:00:00 +0600 [thread overview]
Message-ID: <20110611000000.76ca58e7@natsu> (raw)
In-Reply-To: <BANLkTik87PZChAzgBnDM170uJHU=3Yc6Eg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1472 bytes --]
On Fri, 10 Jun 2011 18:37:06 +0100
Mathias Burén <mathias.buren@gmail.com> wrote:
> 9 Power_On_Hours 0x0032 090 090 000 Old_age
> Always - 7781
> # 1 Extended offline Completed without error 00% 6827
> - # 2 Extended offline Completed without error 00%
> 6550 - # 3 Extended offline Completed without error
> 00% 6468 - # 4 Extended offline Completed without
> error 00% 6329 - # 5 Extended offline Completed
> without error 00% 6040 - # 6 Extended offline
> Completed without error 00% 5584 - # 7 Extended
> offline Completed without error 00% 5178 - # 8
> Extended offline Completed without error 00% 4761 - #
> 9 Short offline Completed without error 00% 2285 -
> #10 Extended offline Completed without error 00% 1514
I suggest that you do another "smartctl -t long" on it, the latest one was
done almost 1000 hours ago which is also much longer than the period between
previous tests. Freezes on reads could be a symptom of a bad (unreadable, or
very slowly readable - which is worse) sector, perhaps it could be detected by
the SMART test. Or also do a full read of the drive directly (not through the
RAID) e.g. with "badblocks" and see if you get any I/O errors that way.
--
With respect,
Roman
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2011-06-10 18:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-10 17:37 HDD reports errors while completing RAID6 array check Mathias Burén
2011-06-10 18:00 ` Roman Mamedov [this message]
2011-06-10 18:23 ` Mathias Burén
2011-06-11 9:49 ` Mathias Burén
2011-06-13 18:30 ` Tim Blundell
2011-06-13 18:41 ` Mathias Burén
2011-06-15 9:11 ` Gordon Henderson
2011-06-14 0:15 ` Brad Campbell
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=20110611000000.76ca58e7@natsu \
--to=rm@romanrm.ru \
--cc=linux-raid@vger.kernel.org \
--cc=mathias.buren@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 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.