fedora 28 up-to-date.
I have a new array, not yet commissioned, and one disk now complains Device: /dev/sde [SAT], FAILED SMART self-check. BACK UP DATA NOW! and the reason, I understand, is this ID# ATTRIBUTE_NAME FLAGS VALUE WORST THRESH FAIL RAW_VALUE 200 Multi_Zone_Error_Rate PO---K 001 001 001 NOW 0
My issue is that the disk works fine and never had any errors reported. Also, smartmontools db does not include this disk ST12000NM0007-2A1101 and update-smart-drivedb is failing with /usr/share/smartmontools/drivedb.h.error.raw: *** BAD signature ***
I know that some disks report funny numbers and smartmontools needs to know which one to trust. I see a relevant ticket from 2018-06-15.... https://www.smartmontools.org/attachment/ticket/1042/smartctl-SEAGATE-ST1200... And I see that smartmontools has other issues with these disks: Write SCT (Get) Feature Control Command failed: scsi error badly formed scsi parameters Wt Cache Reorder: Unknown (SCT Feature Control command failed)
I ran some short and long smart tests but all failed immediately. SMART Extended Self-test Log Version: 1 (1 sectors) Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error # 1 Extended offline Completed: unknown failure 90% 250 0 # 2 Short offline Completed: unknown failure 90% 247 0 # 3 Short offline Completed: unknown failure 90% 247 0 # 4 Extended offline Completed without error 00% 17 -
The other (identical) disks in the array report ID# ATTRIBUTE_NAME FLAGS VALUE WORST THRESH FAIL RAW_VALUE 200 Multi_Zone_Error_Rate PO---K 100 100 001 - 0
I can request a replacement, but want to ensure that this is not just a smart software issue which may pop up again on another disk.
Should we have smartmontools v7.0 (released end of last year) by now? It includes this disk.
As I mentioned, the array is not yet commissioned and I can afford to fiddle with it for a while.
TIA
On 4/5/19 5:05 PM, Eyal Lebedinsky wrote:
Should we have smartmontools v7.0 (released end of last year) by now? It includes this disk.
Looks as if this is in the works. You could download from here and give it a try.
https://koji.fedoraproject.org/koji/buildinfo?buildID=1241515
On 5/4/19 8:38 pm, Ed Greshko wrote:
On 4/5/19 5:05 PM, Eyal Lebedinsky wrote:
Should we have smartmontools v7.0 (released end of last year) by now? It includes this disk.
Looks as if this is in the works. You could download from here and give it a try.
https://koji.fedoraproject.org/koji/buildinfo?buildID=1241515
Thanks, downloaded and tested. No change.
I still see the error Write SCT (Get) Feature Control Command failed: scsi error badly formed scsi parameters Wt Cache Reorder: Unknown (SCT Feature Control command failed) and Multi_Zone_Error_Rate still says NOW and smartd reports: Device: /dev/sde [SAT], FAILED SMART self-check. BACK UP DATA NOW!
I do not like the "badly formed scsi parameters" message - is this the disk not accepting the commands issued by smartmontools?
Being unable to run a smart test (short and long fail) seems to suggest that it is the disk itself enforcing this, and maybe smartmontools is not to blame after all?
Is there a way to reset the smart data on the disk and have it reevaluate the attributes?
I will take this up with the smartmontools mailing list at https://listi.jpberlin.de/mailman/subscribe/smartmontools-support which looks active.
On Fri, Apr 05, 2019 at 09:42:20PM +1100, Eyal Lebedinsky wrote:
On 5/4/19 8:38 pm, Ed Greshko wrote:
On 4/5/19 5:05 PM, Eyal Lebedinsky wrote:
Should we have smartmontools v7.0 (released end of last year) by now? It includes this disk.
Looks as if this is in the works. You could download from here and give it a try.
https://koji.fedoraproject.org/koji/buildinfo?buildID=1241515
Thanks, downloaded and tested. No change.
You know the koji package mentionend above seems to be made for F29, right?
I just downloaded the original tarball via
https://www.smartmontools.org/wiki/Download#Installfromthesourcetarball
configure and make worked like a charm here, on a freshly upgraded F28 - no dependency problems here. They even gave a oneliner on how to install it on a directory of a user's choice ...
The Fedora package seems to be patched: might be worth a try to build from the original source and test it ..
Good luck! Wolfgang
I'm NO expert with raid array's and I don't know how long it will last to check a 12 TB disk, but maybe this could be an option:
SeaTools from Seagate https://www.seagate.com/support/downloads/seatools/seatools-win-master/
On 8/4/19 12:57 am, Wolfgang Pfeiffer wrote:
On Fri, Apr 05, 2019 at 09:42:20PM +1100, Eyal Lebedinsky wrote:
On 5/4/19 8:38 pm, Ed Greshko wrote:
On 4/5/19 5:05 PM, Eyal Lebedinsky wrote:
Should we have smartmontools v7.0 (released end of last year) by now? It includes this disk.
Looks as if this is in the works. You could download from here and give it a try.
https://koji.fedoraproject.org/koji/buildinfo?buildID=1241515
Thanks, downloaded and tested. No change.
You know the koji package mentionend above seems to be made for F29, right?
I just downloaded the original tarball via
https://www.smartmontools.org/wiki/Download#Installfromthesourcetarball
configure and make worked like a charm here, on a freshly upgraded F28 - no dependency problems here. They even gave a oneliner on how to install it on a directory of a user's choice ...
The Fedora package seems to be patched: might be worth a try to build from the original source and test it ..
Did this, smooth build (to private directory) but same results, meaning that even for the good disks I see this notification (now 'In database' but note the last two lines):
=== START OF INFORMATION SECTION === Model Family: Seagate Exos X12 Device Model: ST12000NM0007-2A1101 Serial Number: xxxxxxxx LU WWN Device Id: 5 000c50 xxxxxxxxx Firmware Version: SN02 User Capacity: 12,000,138,625,024 bytes [12.0 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-3 T13/2161-D revision 5 SATA Version is: SATA 3.1, 6.0 Gb/s (current: 6.0 Gb/s) Local Time is: Mon Apr 8 08:53:47 2019 AEST SMART support is: Available - device has SMART capability. SMART support is: Enabled AAM feature is: Unavailable APM feature is: Unavailable Rd look-ahead is: Enabled Write cache is: Enabled DSN feature is: Unavailable ATA Security is: Disabled, NOT FROZEN [SEC1] Write SCT (Get) Feature Control Command failed: scsi error badly formed scsi parameters Wt Cache Reorder: Unknown (SCT Feature Control command failed)
Regards
Good luck! Wolfgang _______________________________________________ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
On Mon, 8 Apr 2019 09:14:28 +1000 Eyal Lebedinsky wrote:
Write SCT (Get) Feature Control Command failed: scsi error badly formed scsi parameters
I have certainly had disk drives that had defective SMART firmware.
You might want to check and see if segate has a firmware update available for the ST12000NM0007-2A1101.
Or maybe a 12TB drive needs special support in SMART to deal with huge addresses?
On 8/4/19 4:24 am, sixpack13 wrote:
sorry wrong link !
this one should do:
Ran non-destructive tests. Generic short was OK. SMART still failed.
There is no indication that any of the tests (even the full zero erase) will "fix" the Multi_Zone_Error_Rate failure.
On 8/4/19 9:55 am, Tom Horsley wrote:
On Mon, 8 Apr 2019 09:14:28 +1000 Eyal Lebedinsky wrote:
Write SCT (Get) Feature Control Command failed: scsi error badly formed scsi parameters
I have certainly had disk drives that had defective SMART firmware.
You might want to check and see if segate has a firmware update available for the ST12000NM0007-2A1101.
First thing I checked, there is none.
Or maybe a 12TB drive needs special support in SMART to deal with huge addresses?
Possible, and a test with the latest released smartmontools did not change the report. I wrote to smartmontools-support@listi.jpberlin.de, no response yet. I hope someone on linux-raid list has some experience but got no response yet.
Thanks everyone
As you are replying to my contribution I guess (?) you did that test with SeaTools ?!
So, in my view it's clear that there is something up with that disk cause the tests failed even with the *vendor specific tool*.
I would request the vendor to replace it !
did you save the output of that tool (log, photo) ?
On 9/4/19 1:19 am, sixpack13 wrote:
As you are replying to my contribution I guess (?) you did that test with SeaTools ?!
Yes.
So, in my view it's clear that there is something up with that disk cause the tests failed even with the *vendor specific tool*.
Agreed.
I would request the vendor to replace it !
I will, but hoped the smartmontools people may want to test a fix to the SCSI error: Write SCT (Get) Feature Control Command failed: scsi error badly formed scsi parameters Wt Cache Reorder: Unknown (SCT Feature Control command failed)
did you save the output of that tool (log, photo) ?
I kept the log. I used the USB version (a bootable FAT32) and it saves the log by default.
cheers
-
Ed Greshko -
Eyal Lebedinsky -
sixpack13 -
Tom Horsley -
Wolfgang Pfeiffer