From: Wols Lists <antlists@youngman.org.uk>
To: Dark Penguin <darkpenguin@yandex.ru>, linux-raid@vger.kernel.org
Subject: Re: md failing mechanism
Date: Fri, 22 Jan 2016 20:00:02 +0000 [thread overview]
Message-ID: <56A28A42.8060707@youngman.org.uk> (raw)
In-Reply-To: <56A28309.9080806@turmel.org>
On 22/01/16 19:29, Phil Turmel wrote:
> What you've described does sound like a bug, maybe. It also sounds
> similar to traditional timeout mismatch caused by cheap desktop drives
> used in a raid array.
man smartctl
smartctl -i /dev/sd-dodgy-drive
If I run that on my drives I get
smartctl 6.4 2015-06-04 r4109 [x86_64-linux-4.1.12-gentoo] (local build)
Copyright (C) 2002-15, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF INFORMATION SECTION ===
Model Family: Seagate Barracuda 7200.14 (AF)
Device Model: ST3000DM001-1CH166
Serial Number: W1F50K0F
LU WWN Device Id: 5 000c50 0737a98a4
Firmware Version: CC27
User Capacity: 3,000,592,982,016 bytes [3.00 TB]
Sector Sizes: 512 bytes logical, 4096 bytes physical
Rotation Rate: 7200 rpm
Form Factor: 3.5 inches
Device is: In smartctl database [for details use: -P show]
ATA Version is: ACS-2, ACS-3 T13/2161-D revision 3b
SATA Version is: SATA 3.1, 6.0 Gb/s (current: 3.0 Gb/s)
Local Time is: Fri Jan 22 19:56:47 2016 GMT
SMART support is: Available - device has SMART capability.
SMART support is: Disabled
NOTE THAT SMART SUPPORT IS DISABLED.
Yes I know I'm running with dodgy drives and a dodgy config, but smart
support should be enabled and things like ERC should be turned on. If
they're not ...
Cheers,
Wol
next prev parent reply other threads:[~2016-01-22 20:00 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-22 17:59 md failing mechanism Dark Penguin
2016-01-22 19:29 ` Phil Turmel
2016-01-22 20:00 ` Wols Lists [this message]
2016-01-22 21:44 ` Dark Penguin
2016-01-22 22:18 ` Phil Turmel
2016-01-22 22:50 ` Dark Penguin
2016-01-22 23:23 ` Edward Kuns
2016-01-22 23:34 ` Wols Lists
2016-01-23 0:09 ` Dark Penguin
2016-01-22 22:37 ` Edward Kuns
2016-01-22 23:07 ` Dark Penguin
2016-01-22 23:39 ` Wols Lists
2016-01-23 0:09 ` Dark Penguin
2016-01-23 0:34 ` Phil Turmel
2016-01-23 10:33 ` Dark Penguin
2016-01-23 15:12 ` Phil Turmel
2016-01-22 23:40 ` James J
2016-01-23 0:44 ` Phil Turmel
2016-01-23 14:09 ` Wols Lists
2016-01-23 19:02 ` James J
2016-01-24 22:13 ` 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=56A28A42.8060707@youngman.org.uk \
--to=antlists@youngman.org.uk \
--cc=darkpenguin@yandex.ru \
--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.