Seagate Barracuda unsupported?

stefano franchi <[email protected]>
Newsgroups gmane.linux.utilities.smartmontools
Message-ID <CAJODLwaN94gHXVxMsSGoo9TNM5Rs5AyO-k9zga7ueECECEexjQ@mail.gmail.com>
I have four identical Seagate Barracuda 2TB HDD Sata drives (model#
ST2000DM001) in a zfs pool on a linux server. Today, zfs refused to
recognized one of the drives (drive is reported as UNAVAILABLE).

When I try to check the drive's health with smartctl I get the following
message:

 >sudo smartctl -H -d ata /dev/sdb
smartctl 6.3 2014-07-26 r3976 [x86_64-linux-3.19.2-1-ARCH] (local build)
Copyright (C) 2002-14, Bruce Allen, Christian Franke, www.smartmontools.org

Read Device Identity failed: Invalid argument

A mandatory SMART command failed: exiting. To continue, add one or more '-T
permissive' options.

The same smartctl command on the other three drives runs with no issues
(drives are accessed and health status is PASSED).


My question is:

Does smartctl's response indicate

(1) that the drive is completely toast or
(2) does it rather point toward a problem with the controller?
(3) or perhaps it means sometjhing different altogether?


Thanks for the help


Stefano
-- 
__________________________________________________
Stefano Franchi

[email protected] <[email protected]>
http://stefano.cleinias.org

------------------------------------------------------------------------------
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the 
conversation now. http://goparallel.sourceforge.net/

_______________________________________________
Smartmontools-support mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/smartmontools-support
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.