Kyle Sebion | 26 Aug 16:10 2014

drivedb.h(978): Error in regular expression: Empty '|' subexpression

A Windows 7 Professional 64-bit, Windows Server 2012, and Windows Server 2012 R2 are getting the following error with a drivedb.h update near 8/23/2014:
  drivedb.h(978): Error in regular expression: Empty '|' subexpression

The error seems to come from the change at: http://www.smartmontools.org/changeset/3988
The change was done during: http://www.smartmontools.org/ticket/329

As a workaround, I changed the string on line 979 in drivedb.h from "SanDisk SD6SB[12]M[0-9]*G(1022I|)|" to "SanDisk SD6SB[12]M[0-9]*G(1022I)?|" on the computers I mentioned above.

--
Kyle Sebion
Developer
Digital Forces Corp

Contact Information
Support 24/7/364: 630-978-2000 X 1. Quickest response. Rings multiple people.
Direct: 630-299-4971. Follows me.
Office 7 am-5 pm: 630-978-2000 x 804. One business day.
Email: help <at> digitalforces.com. Fastest email response one business day.
Texting: 630-447-0804.  Texting is not dependable.
------------------------------------------------------------------------------
Slashdot TV.  
Video for Nerds.  Stuff that matters.
http://tv.slashdot.org/
_______________________________________________
Smartmontools-support mailing list
Smartmontools-support <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/smartmontools-support
Terry Kennedy | 26 Aug 04:05 2014

Smartmontools 6.3 defect list query increments error count on Pliant SSD

  Smartmontools 6.3 (installed from ports) on FreeBSD 8-STABLE amd64. The
system is a Dell PowerEdge R710 with a Dell PERC H700 RAID controller.

  The regular disks on this system can be probed by smartmontools without
incident. However, every time the Pliant LB206M SSD is polled with smartctl,
the "non-medium error count" increments by one, and the following error is
logged to the console:

mfi0: 3580 (462244799s/0x0002/info) - Unexpected sense: PD 07(e0x20/s7) Path 5001e820026e8092, CDB:
b7 0c 00 00 00 00 00 00 00 08 00 00, Sense: 1/1c/00

  B7 is "Read defect list" and 1/1C/00 is "Defect list not found". This
seems to correspond to smartctl reporting "defect list format 6 unknown"
The problem is that the reported "Non-medium error count:" increments by
one each time smartctl is run, and this is remembered by the drive.

  Is it possible to define a quirk for this family of drives to prevent
the defect list inquiry? I am attaching the output of "smartctl -a" for
reference. Note that this is a Dell-labeled drive with Dell firmware - I
don't know if it happens with the OEM firmware.

smartctl 6.3 2014-07-26 r3976 [FreeBSD 8.4-STABLE amd64] (local build)
Copyright (C) 2002-14, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Vendor:               Pliant
Product:              LB206M
Revision:             D323
Compliance:           SPC-4
User Capacity:        200,049,647,616 bytes [200 GB]
Logical block size:   512 bytes
LU is resource provisioned, LBPRZ=1
Rotation Rate:        Solid State Device
Form Factor:          2.5 inches
Logical Unit id:      0x5001e820026e8090
Serial number:        40796304
Device type:          disk
Transport protocol:   SAS (SPL-3)
Local Time is:        Mon Aug 25 22:14:36 2014 EDT
SMART support is:     Available - device has SMART capability.
SMART support is:     Enabled
Temperature Warning:  Disabled or Not Supported

=== START OF READ SMART DATA SECTION ===
SMART Health Status: OK

Percentage used endurance indicator: 0%
Current Drive Temperature:     39 C
Drive Trip Temperature:        60 C

Manufactured in week 36 of year 2013
Specified cycle count over device lifetime:  0
Accumulated start-stop cycles:  35
defect list format 6 unknown
Elements in grown defect list: 0

Error counter log:
           Errors Corrected by           Total   Correction     Gigabytes    Total
               ECC          rereads/    errors   algorithm      processed    uncorrected
           fast | delayed   rewrites  corrected  invocations   [10^9 bytes]  errors
read:          0        0         0         0          0        173.373           0
write:         0        0         0         0          0         52.992           0

Non-medium error count:        8

SMART Self-test log
Num  Test              Status                 segment  LifeTime  LBA_first_err [SK ASC ASQ]
     Description                              number   (hours)
# 1  Background short  Completed                  48       3                 - [-   -    -]
# 2  Background long   Completed                  48       2                 - [-   -    -]
# 3  Background short  Completed                  48       1                 - [-   -    -]

Long (extended) Self Test duration: 4200 seconds [70.0 minutes]

  Please CC me directly on any replies, so I'm sure to see them. Also, if
anyone knows of a method to zero the non-medium error count, I'd appreciate
hearing about it. Thanks!

        Terry Kennedy             http://www.tmk.com
        terry <at> tmk.com             New York, NY USA

------------------------------------------------------------------------------
Slashdot TV.  
Video for Nerds.  Stuff that matters.
http://tv.slashdot.org/
John A. Wallace | 25 Aug 15:33 2014
Picon

Windows oddities


> John A. Wallace wrote:
> > Windows installation oddities
> >
> > I have installed the most recent Windows version6.3-1, whichIgot from
> >
> here:_http://sourceforge.net/projects/smartmontools/files/latest/downlo
> ad_.
> > All appears to be running well from what I have seen so far. Thanks
> > for that.I manually uninstalled the previous version.
> >
> > I ama bit puzzled by the versioning and such. Before I got this
> > version, I hadbeen using one labeled as?smartmontools-win-6.2-2.zip?.
> >
> We never provided such a file on the above download location.
>
> The file is possibly from independent project
> http://www.netpower.fr/smartmontools. It provides an alternative
> installer for smartmontools.
>
Yes, you're probably right about that as I see the different numbering
version available from there.

Regarding the other question I had:

So I am curious about whether it is possible whether a failing, or faulty,
controller on an external USB enclosure could result in a report indicating
that a disk was bad or failing although in fact it might just be that the
controller itself, not the disk, could have a problem? Thanks, Christian.

- John

------------------------------------------------------------------------------
Slashdot TV.  
Video for Nerds.  Stuff that matters.
http://tv.slashdot.org/
John A. Wallace | 22 Aug 20:58 2014
Picon

Windows installation oddities

I have installed the most recent Windows version 6.3-1, which I got from here: http://sourceforge.net/projects/smartmontools/files/latest/download. All appears to be running well from what I have seen so far. Thanks for that. I manually uninstalled the previous version.

I am a bit puzzled by the versioning and such. Before I got this version, I had been using one labeled assmartmontools-win-6.2-2.zip. However, your current program, along with its previous versions shown on the Sourceforge site, all appear to have*.exe formats, instead of the*.zip version; and your previous number shows to be version-6.2-1, not-6.2-2, such as I had. Im not 100% sure where I got the previous one, but I thought it was on your official site, but it appears now that might not have been so. Have you changed numbering in this way?

Also, when I installed the previous version (on Windows 7 Pro), it went intoC:\Program Files (x86)\smartmontools for Windows\. However, your current version ended up being installed toC:\Program Files\smartmontools\, since I chose to make use of the 64-bit version on my 64-bit OS. I presume that it would have gone toC:\Program Files (x86)\smartmontools\”, if I had not clicked the checkbox for 64-bit during installation. Even so, one of the leftover folders from the previously installed version isC:\Program Files (x86)\smartmontools for Windows\, which did not get removed completely while un-installing, and it left behind two files:smart.log and and smartmontools-install-6.2-1.log. Are these files in fact part of your program, or had I somehow gotten someone elses version of smartmontools for Windows?

Finally, on to an important question about functionality, instead of administration, which I was looking for in the FAQ, but nothing showed up. So I am curious about whether it is possible whether a failing, or faulty, controller on an external USB enclosure could result in a report indicating that a disk was bad or failing although in fact it might just be that the controller itself, not the disk, could have a problem? Thanks.

------------------------------------------------------------------------------
Slashdot TV.  
Video for Nerds.  Stuff that matters.
http://tv.slashdot.org/
_______________________________________________
Smartmontools-support mailing list
Smartmontools-support <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/smartmontools-support
Marcel Partap | 18 Aug 23:21 2014
Picon
Picon

USB: WD My Book 4TB 0x1058:0x1230 drivedb entry

..works with -d sat
f.e.
>   { "USB: WD My Book; ",
> -   "0x1058:0x1102",
> +   "0x1058:0x1(102|230)",
>     "", // 0x1028
>     "",
>     "-d sat"
>   },

> Bus 002 Device 002: ID 1058:1230 Western Digital Technologies, Inc. 
> Device Descriptor:
>   bLength                18
>   bDescriptorType         1
>   bcdUSB               3.00
>   bDeviceClass            0 (Defined at Interface level)
>   bDeviceSubClass         0 
>   bDeviceProtocol         0 
>   bMaxPacketSize0         9
>   idVendor           0x1058 Western Digital Technologies, Inc.
>   idProduct          0x1230 
>   bcdDevice           10.50
>   iManufacturer           2 Western Digital
>   iProduct                3 My Book 1230

#Regards!

------------------------------------------------------------------------------
Slashdot TV.  
Video for Nerds.  Stuff that matters.
http://tv.slashdot.org/
John Teddy | 18 Aug 18:57 2014
Picon

Smart behind a raid

I'm trying to get smartd to run and report to syslog. There are a lot of options in smart.conf, are there any recommended setups? My command for using smartctl manually is this: 

sudo smartctl -l ssd -d megaraid,0 -H /dev/sda

How can I get smartd to dump to syslog?

Does it report any errors it would find from smart onto syslog?

Do I need to have cronjobs to run smartctl manually? Or if I setup smartd, does smartd do that itself?

------------------------------------------------------------------------------
Slashdot TV.  
Video for Nerds.  Stuff that matters.
http://tv.slashdot.org/
_______________________________________________
Smartmontools-support mailing list
Smartmontools-support <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/smartmontools-support
John Theodore | 20 Aug 03:35 2014
Picon

smartd.conf advice, how often to run scans, what options?

I finally got smartd working and the puppet-smartd module works now too. I realized how useful devicescan is.

How often are you guys having short or long tests occur?

Currently my smartd.conf looks like this:

DEVICESCAN -S on -o on -a -I 194 -s (S/../.././02|L/../../6/03)

Do I need additional options to cause it to dump errors it finds to syslog? or does devicescan do that automatically? All these disks are behind a megaraid controller, will the query work properly through devicescan?

------------------------------------------------------------------------------
Slashdot TV.  
Video for Nerds.  Stuff that matters.
http://tv.slashdot.org/
_______________________________________________
Smartmontools-support mailing list
Smartmontools-support <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/smartmontools-support
Christian Franke | 18 Aug 21:05 2014
Picon

Re: smartctl output for Crucial 512Gb SSD

Mike wrote:
> Great thanks. I've applied the patch and ran the same command, which
> initially takes around 30 seconds to return any data at all, it then
> hung for about 1 minute after printing the GPL table.

This is because, with the patch, these large logs are completely read 
into memory. Smartctl should only read sectors needed but this requires 
some rework.

> ...
> Self-test execution status:      (  80) The previous self-test completed having
> the electrical element of the test failed.

This suggests a serious problem with the drive.

> ...
>
> SMART Extended Comprehensive Error Log Version: 1 (16383 sectors)
> No Errors Logged
>
> SMART Extended Self-test Log Version: 1 (3449 sectors)

smartctl should print one entry here but doesn't. There is either a bug 
in smartctl or the drive does not fill the self-test log as specified by 
the standard.

Please provide output of "smartctl -l gplog,0x07,0-1 /dev/sdb" as 
attachment(!).

Connecting to another SATA controller with better pass-through support 
may help to read the old Self-test Log (don't use -x, use -a or -l 
selftest).

Thanks,
Christian

------------------------------------------------------------------------------
Mike | 16 Aug 23:47 2014
Picon

Fwd: smartctl output for Crucial 512Gb SSD

Great thanks. I've applied the patch and ran the same command, which
initially takes around 30 seconds to return any data at all, it then
hung for about 1 minute after printing the GPL table.  Here is the
output:

user <at> w530:~/Downloads/smartmontools-6.3$ sudo ./smartctl -x /dev/sdb
smartctl 6.3 2014-07-26 r3976 [x86_64-linux-3.13.0-34-generic] (local build)
Copyright (C) 2002-14, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family:     Crucial/Micron RealSSD m4/C400/P400
Device Model:     M4-CT512M4SSD1
Serial Number:    000000001249091FCC21
LU WWN Device Id: 5 00a075 1091fcc21
Firmware Version: 070H
User Capacity:    512,110,190,592 bytes [512 GB]
Sector Size:      512 bytes logical/physical
Rotation Rate:    Solid State Device
Form Factor:      2.5 inches
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   ACS-2, ATA8-ACS T13/1699-D revision 6
SATA Version is:  SATA 3.0, 6.0 Gb/s (current: 1.5 Gb/s)
Local Time is:    Sat Aug 16 21:43:33 2014 BST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
AAM feature is:   Unavailable
APM level is:     254 (maximum performance)
Rd look-ahead is: Enabled
Write cache is:   Enabled
ATA Security is:  Disabled, NOT FROZEN [SEC1]
Write SCT (Get) Feature Control Command failed: scsi error medium or
hardware error (serious)
Wt Cache Reorder: Unknown (SCT Feature Control command failed)

=== START OF READ SMART DATA SECTION ===
SMART Status command failed: scsi error medium or hardware error (serious)
SMART overall-health self-assessment test result: PASSED
Warning: This result is based on an Attribute check.

General SMART Values:
Offline data collection status:  (0x80) Offline data collection activity
was never started.
Auto Offline Data Collection: Enabled.
Self-test execution status:      (   0) The previous self-test routine completed
without error or no self-test has ever
been run.
Total time to complete Offline
data collection: ( 2380) seconds.
Offline data collection
capabilities: (0x7b) SMART execute Offline immediate.
Auto Offline data collection on/off support.
Suspend Offline collection upon new
command.
Offline surface scan supported.
Self-test supported.
Conveyance Self-test supported.
Selective Self-test supported.
SMART capabilities:            (0x0003) Saves SMART data before entering
power-saving mode.
Supports SMART auto save timer.
Error logging capability:        (0x01) Error logging supported.
General Purpose Logging supported.
Short self-test routine
recommended polling time: (   2) minutes.
Extended self-test routine
recommended polling time: (  39) minutes.
Conveyance self-test routine
recommended polling time: (   3) minutes.
SCT capabilities:       (0x003d) SCT Status supported.
SCT Error Recovery Control supported.
SCT Feature Control supported.
SCT Data Table supported.

SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAGS    VALUE WORST THRESH FAIL RAW_VALUE
  1 Raw_Read_Error_Rate     POSR-K   100   100   050    -    0
  5 Reallocated_Sector_Ct   PO--CK   100   100   010    -    0
  9 Power_On_Hours          -O--CK   100   100   001    -    4439
 12 Power_Cycle_Count       -O--CK   100   100   001    -    515
170 Grown_Failing_Block_Ct  PO--CK   100   100   010    -    0
171 Program_Fail_Count      -O--CK   100   100   001    -    0
172 Erase_Fail_Count        -O--CK   100   100   001    -    0
173 Wear_Leveling_Count     PO--CK   100   100   010    -    0
174 Unexpect_Power_Loss_Ct  -O--CK   100   100   001    -    398
181 Non4k_Aligned_Access    -O---K   100   100   001    -    144 45 99
183 SATA_Iface_Downshift    -O--CK   100   100   001    -    0
184 End-to-End_Error        PO--CK   100   100   050    -    0
187 Reported_Uncorrect      -O--CK   100   100   001    -    0
188 Command_Timeout         -O--CK   100   100   001    -    0
189 Factory_Bad_Block_Ct    -OSR--   100   100   001    -    215
194 Temperature_Celsius     -O---K   100   100   000    -    0
195 Hardware_ECC_Recovered  -O-RCK   100   100   001    -    0
196 Reallocated_Event_Count -O--CK   100   100   001    -    0
197 Current_Pending_Sector  -O--CK   100   100   001    -    0
198 Offline_Uncorrectable   ----CK   100   100   001    -    0
199 UDMA_CRC_Error_Count    -O--CK   100   100   001    -    0
202 Perc_Rated_Life_Used    ---RC-   100   100   001    -    0
206 Write_Error_Rate        -OSR--   100   100   001    -    0
                            ||||||_ K auto-keep
                            |||||__ C event count
                            ||||___ R error rate
                            |||____ S speed/performance
                            ||_____ O updated online
                            |______ P prefailure warning

Read SMART Log Directory failed: scsi error medium or hardware error (serious)

General Purpose Log Directory Version 1
Address    Access  R/W   Size  Description
0x00       GPL     R/O      1  Log Directory
0x03       GPL     R/O  16383  Ext. Comprehensive SMART error log
0x04       GPL     R/O    255  Device Statistics log
0x07       GPL     R/O   3449  Extended self-test log
0x10       GPL     R/O      1  NCQ Command Error log
0x11       GPL     R/O      1  SATA Phy Event Counters
0x80-0x9f  GPL     R/W     16  Host vendor specific log
0xa0       GPL     VS    2000  Device vendor specific log
0xa1-0xbf  GPL     VS       1  Device vendor specific log
0xc0       GPL     VS      80  Device vendor specific log
0xc1-0xdf  GPL     VS       1  Device vendor specific log
0xe0       GPL     R/W      1  SCT Command/Status
0xe1       GPL     R/W      1  SCT Data Transfer

SMART Extended Comprehensive Error Log Version: 1 (16383 sectors)
No Errors Logged

SMART Extended Self-test Log Version: 1 (3449 sectors)
No self-tests have been logged.  [To run self-tests, use: smartctl -t]

Read SMART Selective Self-test Log failed: scsi error medium or
hardware error (serious)

SCT Status Version:                  3
SCT Version (vendor specific):       1 (0x0001)
SCT Support Level:                   0
Device State:                        Active (0)
Current Temperature:                  0 Celsius
Power Cycle Max Temperature:          0 Celsius
Lifetime    Max Temperature:          0 Celsius

SCT Temperature History Version:     2
Temperature Sampling Period:         10 minutes
Temperature Logging Interval:        10 minutes
Min/Max recommended Temperature:      0/70 Celsius
Min/Max Temperature Limit:           -5/75 Celsius
Temperature History Size (Index):    478 (37)

Index    Estimated Time   Temperature Celsius
  38    2014-08-13 14:10     ?  -
 ...    ..(476 skipped).    ..  -
  37    2014-08-16 21:40     ?  -

Write SCT (Get) Error Recovery Control Command failed: scsi error
medium or hardware error (serious)
SCT (Get) Error Recovery Control command failed

Device Statistics (GP Log 0x04)
Page Offset Size         Value  Description
  1  =====  =                =  == General Statistics (rev 2) ==
  1  0x008  4              515  Lifetime Power-On Resets
  1  0x010  4             4439  Power-on Hours
  1  0x018  6        933634265  Logical Sectors Written
  1  0x020  6          2708986  Number of Write Commands
  1  0x028  6        852431906  Logical Sectors Read
  1  0x030  6          6049196  Number of Read Commands
  4  =====  =                =  == General Errors Statistics (rev 1) ==
  4  0x008  4                0  Number of Reported Uncorrectable Errors
  4  0x010  4                0  Resets Between Cmd Acceptance and Completion
  5  =====  =                =  == Temperature Statistics (rev 1) ==
  5  0x008  1                0  Current Temperature
  5  0x010  1                0  Average Short Term Temperature
  5  0x018  1                0  Average Long Term Temperature
  5  0x020  1                0  Highest Temperature
  5  0x028  1                0  Lowest Temperature
  5  0x030  1                0  Highest Average Short Term Temperature
  5  0x038  1                0  Lowest Average Short Term Temperature
  5  0x040  1                0  Highest Average Long Term Temperature
  5  0x048  1                0  Lowest Average Long Term Temperature
  5  0x050  4                -  Time in Over-Temperature
  5  0x058  1               70  Specified Maximum Operating Temperature
  5  0x060  4                -  Time in Under-Temperature
  5  0x068  1                0  Specified Minimum Operating Temperature
  6  =====  =                =  == Transport Statistics (rev 1) ==
  6  0x008  4                0  Number of Hardware Resets
  6  0x010  4                0  Number of ASR Events
  6  0x018  4                0  Number of Interface CRC Errors
  7  =====  =                =  == Solid State Device Statistics (rev 1) ==
  7  0x008  1               21~ Percentage Used Endurance Indicator
                              |_ ~ normalized value

SATA Phy Event Counters (GP Log 0x11)
ID      Size     Value  Description
0x0001  4            0  Command failed due to ICRC error
0x000a  4            0  Device-to-host register FISes sent due to a COMRESET

I then ran a -t short and a --test=long, and then issued the same
command as above:

user <at> w530:~/Downloads/smartmontools-6.3$ sudo ./smartctl -x /dev/sdb
[sudo] password for user:
smartctl 6.3 2014-07-26 r3976 [x86_64-linux-3.13.0-34-generic] (local build)
Copyright (C) 2002-14, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family:     Crucial/Micron RealSSD m4/C400/P400
Device Model:     M4-CT512M4SSD1
Serial Number:    000000001249091FCC21
LU WWN Device Id: 5 00a075 1091fcc21
Firmware Version: 070H
User Capacity:    512,110,190,592 bytes [512 GB]
Sector Size:      512 bytes logical/physical
Rotation Rate:    Solid State Device
Form Factor:      2.5 inches
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   ACS-2, ATA8-ACS T13/1699-D revision 6
SATA Version is:  SATA 3.0, 6.0 Gb/s (current: 1.5 Gb/s)
Local Time is:    Sat Aug 16 22:44:54 2014 BST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
AAM feature is:   Unavailable
APM level is:     254 (maximum performance)
Rd look-ahead is: Enabled
Write cache is:   Enabled
ATA Security is:  Disabled, NOT FROZEN [SEC1]
Write SCT (Get) Feature Control Command failed: scsi error medium or
hardware error (serious)
Wt Cache Reorder: Unknown (SCT Feature Control command failed)

=== START OF READ SMART DATA SECTION ===
SMART Status command failed: scsi error medium or hardware error (serious)
SMART overall-health self-assessment test result: PASSED
Warning: This result is based on an Attribute check.

General SMART Values:
Offline data collection status:  (0x80) Offline data collection activity
was never started.
Auto Offline Data Collection: Enabled.
Self-test execution status:      (  80) The previous self-test completed having
the electrical element of the test
failed.
Total time to complete Offline
data collection: ( 2380) seconds.
Offline data collection
capabilities: (0x7b) SMART execute Offline immediate.
Auto Offline data collection on/off support.
Suspend Offline collection upon new
command.
Offline surface scan supported.
Self-test supported.
Conveyance Self-test supported.
Selective Self-test supported.
SMART capabilities:            (0x0003) Saves SMART data before entering
power-saving mode.
Supports SMART auto save timer.
Error logging capability:        (0x01) Error logging supported.
General Purpose Logging supported.
Short self-test routine
recommended polling time: (   2) minutes.
Extended self-test routine
recommended polling time: (  39) minutes.
Conveyance self-test routine
recommended polling time: (   3) minutes.
SCT capabilities:       (0x003d) SCT Status supported.
SCT Error Recovery Control supported.
SCT Feature Control supported.
SCT Data Table supported.

SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAGS    VALUE WORST THRESH FAIL RAW_VALUE
  1 Raw_Read_Error_Rate     POSR-K   100   100   050    -    0
  5 Reallocated_Sector_Ct   PO--CK   100   100   010    -    0
  9 Power_On_Hours          -O--CK   100   100   001    -    4440
 12 Power_Cycle_Count       -O--CK   100   100   001    -    515
170 Grown_Failing_Block_Ct  PO--CK   100   100   010    -    0
171 Program_Fail_Count      -O--CK   100   100   001    -    0
172 Erase_Fail_Count        -O--CK   100   100   001    -    0
173 Wear_Leveling_Count     PO--CK   100   100   010    -    0
174 Unexpect_Power_Loss_Ct  -O--CK   100   100   001    -    398
181 Non4k_Aligned_Access    -O---K   100   100   001    -    144 45 99
183 SATA_Iface_Downshift    -O--CK   100   100   001    -    0
184 End-to-End_Error        PO--CK   100   100   050    -    0
187 Reported_Uncorrect      -O--CK   100   100   001    -    0
188 Command_Timeout         -O--CK   100   100   001    -    0
189 Factory_Bad_Block_Ct    -OSR--   100   100   001    -    215
194 Temperature_Celsius     -O---K   100   100   000    -    0
195 Hardware_ECC_Recovered  -O-RCK   100   100   001    -    0
196 Reallocated_Event_Count -O--CK   100   100   001    -    0
197 Current_Pending_Sector  -O--CK   100   100   001    -    0
198 Offline_Uncorrectable   ----CK   100   100   001    -    0
199 UDMA_CRC_Error_Count    -O--CK   100   100   001    -    0
202 Perc_Rated_Life_Used    ---RC-   100   100   001    -    0
206 Write_Error_Rate        -OSR--   100   100   001    -    0
                            ||||||_ K auto-keep
                            |||||__ C event count
                            ||||___ R error rate
                            |||____ S speed/performance
                            ||_____ O updated online
                            |______ P prefailure warning

Read SMART Log Directory failed: scsi error medium or hardware error (serious)

General Purpose Log Directory Version 1
Address    Access  R/W   Size  Description
0x00       GPL     R/O      1  Log Directory
0x03       GPL     R/O  16383  Ext. Comprehensive SMART error log
0x04       GPL     R/O    255  Device Statistics log
0x07       GPL     R/O   3449  Extended self-test log
0x10       GPL     R/O      1  NCQ Command Error log
0x11       GPL     R/O      1  SATA Phy Event Counters
0x80-0x9f  GPL     R/W     16  Host vendor specific log
0xa0       GPL     VS    2000  Device vendor specific log
0xa1-0xbf  GPL     VS       1  Device vendor specific log
0xc0       GPL     VS      80  Device vendor specific log
0xc1-0xdf  GPL     VS       1  Device vendor specific log
0xe0       GPL     R/W      1  SCT Command/Status
0xe1       GPL     R/W      1  SCT Data Transfer

SMART Extended Comprehensive Error Log Version: 1 (16383 sectors)
No Errors Logged

SMART Extended Self-test Log Version: 1 (3449 sectors)

Read SMART Selective Self-test Log failed: scsi error medium or
hardware error (serious)

SCT Status Version:                  3
SCT Version (vendor specific):       1 (0x0001)
SCT Support Level:                   0
Device State:                        Stand-by (1)
Current Temperature:                  0 Celsius
Power Cycle Max Temperature:          0 Celsius
Lifetime    Max Temperature:          0 Celsius

SCT Temperature History Version:     2
Temperature Sampling Period:         10 minutes
Temperature Logging Interval:        10 minutes
Min/Max recommended Temperature:      0/70 Celsius
Min/Max Temperature Limit:           -5/75 Celsius
Temperature History Size (Index):    478 (40)

Index    Estimated Time   Temperature Celsius
  41    2014-08-13 15:10     ?  -
 ...    ..(473 skipped).    ..  -
  37    2014-08-16 22:10     ?  -
  38    2014-08-16 22:20     0  -
  39    2014-08-16 22:30     0  -
  40    2014-08-16 22:40     0  -

Write SCT (Get) Error Recovery Control Command failed: scsi error
medium or hardware error (serious)
SCT (Get) Error Recovery Control command failed

Device Statistics (GP Log 0x04)
Page Offset Size         Value  Description
  1  =====  =                =  == General Statistics (rev 2) ==
  1  0x008  4              515  Lifetime Power-On Resets
  1  0x010  4             4440  Power-on Hours
  1  0x018  6        933634265  Logical Sectors Written
  1  0x020  6          2708986  Number of Write Commands
  1  0x028  6        852431906  Logical Sectors Read
  1  0x030  6          6049196  Number of Read Commands
  4  =====  =                =  == General Errors Statistics (rev 1) ==
  4  0x008  4                0  Number of Reported Uncorrectable Errors
  4  0x010  4                0  Resets Between Cmd Acceptance and Completion
  5  =====  =                =  == Temperature Statistics (rev 1) ==
  5  0x008  1                0  Current Temperature
  5  0x010  1                0  Average Short Term Temperature
  5  0x018  1                0  Average Long Term Temperature
  5  0x020  1                0  Highest Temperature
  5  0x028  1                0  Lowest Temperature
  5  0x030  1                0  Highest Average Short Term Temperature
  5  0x038  1                0  Lowest Average Short Term Temperature
  5  0x040  1                0  Highest Average Long Term Temperature
  5  0x048  1                0  Lowest Average Long Term Temperature
  5  0x050  4                -  Time in Over-Temperature
  5  0x058  1               70  Specified Maximum Operating Temperature
  5  0x060  4                -  Time in Under-Temperature
  5  0x068  1                0  Specified Minimum Operating Temperature
  6  =====  =                =  == Transport Statistics (rev 1) ==
  6  0x008  4                0  Number of Hardware Resets
  6  0x010  4                0  Number of ASR Events
  6  0x018  4                0  Number of Interface CRC Errors
  7  =====  =                =  == Solid State Device Statistics (rev 1) ==
  7  0x008  1               21~ Percentage Used Endurance Indicator
                              |_ ~ normalized value

SATA Phy Event Counters (GP Log 0x11)
ID      Size     Value  Description
0x0001  4            0  Command failed due to ICRC error
0x000a  4            0  Device-to-host register FISes sent due to a COMRESET

On 16 August 2014 20:06, Christian Franke <Christian.Franke <at> t-online.de> wrote:
> Mike wrote:
>>
>> Greetings
>>
>> Following on from previous message, where running smartctl with the
>> disk connected via SATA returns a 600PB disk (it is actually 512Gb
>> Crucial M4), I followed advice from the Crucial message boards and
>> left the disk idle over night in order to trigger automatic garbade
>> collection.  No change the next morning, below is some smartctl
>> output.  I've tried ddrescue to no avail, reads just fail completely.
>> ...
>>
>> smartctl 6.3 2014-07-26 r3976 [x86_64-linux-3.13.0-34-generic] (local
>> build)
>> Copyright (C) 2002-14, Bruce Allen, Christian Franke,
>> www.smartmontools.org
>>
>> === START OF INFORMATION SECTION ===
>> Model Family:     Crucial/Micron RealSSD m4/C400/P400
>> Device Model:     M4-CT512M4SSD1
>> ...
>>
>> Read SMART Log Directory failed: scsi error medium or hardware error
>> (serious)
>>
>
> This error message is probably due to a limitation/bug in driver/firmware of
> the used (which?) controller. The device itself should support SMART Log
> Directory.
>
>
>> General Purpose Log Directory Version 1
>> Address    Access  R/W   Size  Description
>> 0x00       GPL     R/O      1  Log Directory
>> 0x03       GPL     R/O  16383  Ext. Comprehensive SMART error log
>> 0x04       GPL     R/O    255  Device Statistics log
>> 0x07       GPL     R/O   3449  Extended self-test log
>> ..
>>
>> SMART Extended Comprehensive Error Log size 16383 not supported
>>
>> Read SMART Error Log failed: scsi error medium or hardware error (serious)
>>
>> SMART Extended Self-test Log size 3449 not supported
>>
>> Read SMART Self-test Log failed: scsi error medium or hardware error
>> (serious)
>
>
> The extended error/self-test logs may contain useful info. Unfortunately
> smartctl does not print the extended logs due to a historic size limitation.
> In the early days of these logs, sizes were <= 8.
>
> If possible, apply the attached patch and try whether the logs could be read
> then.
>
> Thanks,
> Christian
>

------------------------------------------------------------------------------
Anthony Nemmer | 16 Aug 08:51 2014
Picon

invalid SMART checksum

Greetings!

when I run smartctl -a I get an error message "invalid SMART checksum" but I googled it and I can't find anything that can explain why I am getting the error.

Help?

Thank You,
Anthony Nemmer

--
I always have coffee when I watch radar!
------------------------------------------------------------------------------
_______________________________________________
Smartmontools-support mailing list
Smartmontools-support <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/smartmontools-support
George R Goffe | 16 Aug 07:59 2014
Picon

2TB Seagate gets msg "SMART Status command failed"

Hi,

I just installed a brand new Seagate 2TB hdd, 

 Model Family:     Seagate Barracuda 7200.14
(AF)                                                                                                                      
Device Model:    
ST2000DM001-1CH164                                                                                                                                  

When I execute this command (/usr/sbin/smartctl -a -d sat /dev/sdc), I get the following:

=== START OF READ SMART DATA SECTION
===                                                                                                                              
SMART Status command
failed                                                                                                                                           
Please get assistance from
http://smartmontools.sourceforge.net/                                                                                                      
Register values returned from SMART Status command
are:                                                                                                               
 ERR=0x00, SC=0x00, LL=0xb7, LM=0x2d, LH=0x04, DEV=0x40,
STS=0x50                                                                                                     
SMART overall-health self-assessment test result:
PASSED                                                                                                              
Warning: This result is based on an Attribute
check.                                                                                                                  
 

Am I doing something wrong? I don't know how to handle this situation. The hdd is behind a SIIG USB docking
station. The os is Fedora 19 x86_64. Smartmon is at this level: smartmontools-6.2-5.fc19.x86_64

Any/all hints/tips/suggestions would be appreciated.

Regards,

George...

------------------------------------------------------------------------------

Gmane