Menu
▾
▴
smartmontools-support — (old) mailing list for discussion, bug reports, support requests, and feature requests (2002-10-11 until 2017-07-30)
You can subscribe to this list here.
| 2002 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(50) |
Nov
(161) |
Dec
(84) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2003 |
Jan
(84) |
Feb
(103) |
Mar
(54) |
Apr
(63) |
May
(44) |
Jun
(45) |
Jul
(44) |
Aug
(55) |
Sep
(15) |
Oct
(99) |
Nov
(101) |
Dec
(104) |
| 2004 |
Jan
(76) |
Feb
(98) |
Mar
(99) |
Apr
(130) |
May
(107) |
Jun
(79) |
Jul
(94) |
Aug
(164) |
Sep
(115) |
Oct
(125) |
Nov
(160) |
Dec
(84) |
| 2005 |
Jan
(72) |
Feb
(85) |
Mar
(55) |
Apr
(109) |
May
(64) |
Jun
(33) |
Jul
(71) |
Aug
(77) |
Sep
(84) |
Oct
(102) |
Nov
(106) |
Dec
(51) |
| 2006 |
Jan
(47) |
Feb
(58) |
Mar
(60) |
Apr
(106) |
May
(73) |
Jun
(65) |
Jul
(109) |
Aug
(103) |
Sep
(73) |
Oct
(57) |
Nov
(94) |
Dec
(62) |
| 2007 |
Jan
(61) |
Feb
(67) |
Mar
(90) |
Apr
(90) |
May
(77) |
Jun
(82) |
Jul
(75) |
Aug
(74) |
Sep
(63) |
Oct
(70) |
Nov
(60) |
Dec
(59) |
| 2008 |
Jan
(68) |
Feb
(113) |
Mar
(128) |
Apr
(89) |
May
(57) |
Jun
(88) |
Jul
(74) |
Aug
(43) |
Sep
(77) |
Oct
(106) |
Nov
(99) |
Dec
(82) |
| 2009 |
Jan
(126) |
Feb
(49) |
Mar
(47) |
Apr
(26) |
May
(38) |
Jun
(75) |
Jul
(61) |
Aug
(45) |
Sep
(105) |
Oct
(77) |
Nov
(46) |
Dec
(47) |
| 2010 |
Jan
(58) |
Feb
(88) |
Mar
(54) |
Apr
(78) |
May
(30) |
Jun
(40) |
Jul
(46) |
Aug
(36) |
Sep
(30) |
Oct
(29) |
Nov
(80) |
Dec
(52) |
| 2011 |
Jan
(30) |
Feb
(27) |
Mar
(25) |
Apr
(77) |
May
(24) |
Jun
(45) |
Jul
(34) |
Aug
(24) |
Sep
(65) |
Oct
(55) |
Nov
(72) |
Dec
(19) |
| 2012 |
Jan
(58) |
Feb
(44) |
Mar
(90) |
Apr
(11) |
May
(27) |
Jun
(32) |
Jul
(61) |
Aug
(32) |
Sep
(39) |
Oct
(45) |
Nov
(50) |
Dec
(21) |
| 2013 |
Jan
(44) |
Feb
(26) |
Mar
(37) |
Apr
(46) |
May
(24) |
Jun
(44) |
Jul
(15) |
Aug
(16) |
Sep
(20) |
Oct
(36) |
Nov
(36) |
Dec
(41) |
| 2014 |
Jan
(21) |
Feb
(9) |
Mar
(14) |
Apr
(16) |
May
(32) |
Jun
(50) |
Jul
(71) |
Aug
(47) |
Sep
(17) |
Oct
(9) |
Nov
(40) |
Dec
(42) |
| 2015 |
Jan
(11) |
Feb
(25) |
Mar
(22) |
Apr
(21) |
May
(6) |
Jun
(3) |
Jul
(7) |
Aug
(42) |
Sep
(28) |
Oct
(33) |
Nov
(5) |
Dec
(7) |
| 2016 |
Jan
(12) |
Feb
(18) |
Mar
(19) |
Apr
(31) |
May
(27) |
Jun
(23) |
Jul
(12) |
Aug
(33) |
Sep
(5) |
Oct
(28) |
Nov
(19) |
Dec
(8) |
| 2017 |
Jan
(52) |
Feb
(36) |
Mar
(12) |
Apr
(17) |
May
(8) |
Jun
(12) |
Jul
(3) |
Aug
|
Sep
(2) |
Oct
|
Nov
|
Dec
|
| 2018 |
Jan
|
Feb
|
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
|
Aug
(2) |
Sep
|
Oct
|
Nov
|
Dec
|
| 2021 |
Jan
|
Feb
|
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Orsiris de J. <oz...@ne...> - 2017-05-11 09:54:40
|
Hello Alexander, Congratulations for the new version of your tool, really looks steamlined :) I just ran it on my Win10 x64 with an nvme and an ssd disk. The NVME disk is detected, but output is limited: smartctl 6.5 2016-05-07 r4318 [i686-w64-mingw32-win10(64)] (sf-6.5-1) Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Vendor: NVMe Product: Samsung SSD 950 Revision: 2B0Q Compliance: SPC-4 LU is resource provisioned, LBPRZ=1 Rotation Rate: Solid State Device Logical Unit id: YYYYYYYYYYYYYYYYYYYYY 2B0Q Serial number: XXXXXXXXXXXXXXXXXXX Device type: disk Local Time is: Thu May 11 11:34:15 2017 PM SMART support is: Available - device has SMART capability. SMART support is: Disabled Temperature Warning: Disabled or Not Supported === START OF READ SMART DATA SECTION === Request Sense failed, [Input/output error] Current Drive Temperature: 51 C Drive Trip Temperature: 80 C Error Counter logging not supported [GLTSD (Global Logging Target Save Disable) set. Enable Save with '-S on'] Device does not support Self Test logging ------------------------------ Doing the same with smartctl -a /dev/nvme0 C:\Program Files\smartmontools\bin>smartctl -a /dev/nvme0 smartctl 6.5 2016-05-07 r4318 [x86_64-w64-mingw32-win10] (sf-6.5-1) Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Model Number: Samsung SSD 950 PRO 256GB Serial Number: XXXXXXXXXXXXXXXXXXX Firmware Version: 2B0QBXX7 PCI Vendor/Subsystem ID: 0x144d IEEE OUI Identifier: 0x002538 Controller ID: 1 Number of Namespaces: 1 Namespace 1 Size/Capacity: 256 060 514 304 [256 GB] Namespace 1 Utilization: 153 960 095 744 [153 GB] Namespace 1 Formatted LBA Size: 512 Local Time is: Thu May 11 11:35:11 2017 PM Firmware Updates (0x06): 3 Slots Optional Admin Commands (0x0007): Security Format Frmw_DL Optional NVM Commands (0x001f): Comp Wr_Unc DS_Mngmt Wr_Zero Sav/Sel_Feat Maximum Data Transfer Size: 32 Pages Supported Power States St Op Max Active Idle RL RT WL WT Ent_Lat Ex_Lat 0 + 6.50W - - 0 0 0 0 5 5 1 + 5.80W - - 1 1 1 1 30 30 2 + 3.60W - - 2 2 2 2 100 100 3 - 0.0700W - - 3 3 3 3 500 5000 4 - 0.0050W - - 4 4 4 4 2000 22000 Supported LBA Sizes (NSID 0x1) Id Fmt Data Metadt Rel_Perf 0 + 512 0 0 === START OF SMART DATA SECTION === SMART overall-health self-assessment test result: PASSED SMART/Health Information (NVMe Log 0x02, NSID 0xffffffff) Critical Warning: 0x00 Temperature: 51 Celsius Available Spare: 100% Available Spare Threshold: 10% Percentage Used: 0% Data Units Read: 8 802 764 [4,50 TB] Data Units Written: 8 100 637 [4,14 TB] Host Read Commands: 163 470 567 Host Write Commands: 207 549 906 Controller Busy Time: 879 Power Cycles: 1 846 Power On Hours: 3 551 Unsafe Shutdowns: 210 Media and Data Integrity Errors: 0 Error Information Log Entries: 97 Error Information (NVMe Log 0x01, max 64 entries) Num ErrCount SQId CmdId Status PELoc LBA NSID VS 0 97 0 0x001d 0x4004 0x000 0 0 - 1 96 0 0x001c 0x4004 0x000 0 0 - 2 95 0 0x001d 0x4004 0x000 0 0 - 3 94 0 0x001c 0x4004 0x000 0 0 - 4 93 0 0x001d 0x4004 0x000 0 0 - 5 92 0 0x001c 0x4004 0x000 0 0 - 6 91 0 0x001f 0x4004 0x000 0 0 - 7 90 0 0x001e 0x4004 0x000 0 0 - 8 89 0 0x001f 0x4004 0x000 0 0 - 9 88 0 0x001e 0x4004 0x000 0 0 - 10 87 0 0x001d 0x4004 0x000 0 0 - 11 86 0 0x001c 0x4004 0x000 0 0 - 12 85 0 0x001d 0x4004 0x000 0 0 - 13 84 0 0x001c 0x4004 0x000 0 0 - 14 83 0 0x001d 0x4004 0x000 0 0 - 15 82 0 0x001c 0x4004 0x000 0 0 - ... (48 entries not shown) I've seen that smartctl --scan can't really find nvme devices as of v6.5. Is there a chance to run a pseudo code loop like for i in {0..15}; do smartctl -a /dev/nvme$i if [$! == 0]; then device_exists+=$i; fi done This would allow to detect those devices and get nvme output. Btw, the berlios.de link didn't work for me, had to go to sourceforge. Best regards, Orsiris de Jong oz...@ne... - http://www.netpower.fr <http://www.netpower.fr> Tel: 06 75 40 48 41 -----Message initial----- De: Alexander Shaduri <ash...@gm...> Envoyé: jeudi 11 mai 2017 11:27 À: sma...@li... Sujet: [smartmontools-support] GSmartControl 0.9.0 released Hello all, It's been a long while since the last release, but here it is: I just released GSmartControl 0.9.0 (a GUI for smartctl), you may find it at http://gsmartcontrol.berlios.de . Changes include: Implemented (untested) support for Linux-based Areca controllers with enclosures. Implemented (untested) support for Windows-based Areca controllers (thanks to Richard Kagerer). Implemented (untested) support for Linux-based HP controllers with cciss and hpsa/hpahcisr drivers (thanks to Fabrice Bacchella). Changes in Preferences no longer fail silently until rescan/restart. Better drive detection under Windows after removable drives are detached. Windows version is no longer marked as "dpi aware" since it's not supported that well. Drive attribute descriptions have been updated (including clarifications for SSDs). Added support for SSD-only and HDD-only vendor attributes. Devices having only basic info can be displayed now in the info window. Fixed BDRW drive detection (it was detected as a HDD). Other minor improvements. A number of issues have been fixed (including a crash). Any help with testing is really appreciated. Thanks, Alexander ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Smartmontools-support mailing list Sma...@li... https://lists.sourceforge.net/lists/listinfo/smartmontools-support |
|
From: Alexander S. <ash...@gm...> - 2017-05-11 09:26:31
|
Hello all, It's been a long while since the last release, but here it is: I just released GSmartControl 0.9.0 (a GUI for smartctl), you may find it at http://gsmartcontrol.berlios.de . Changes include: Implemented (untested) support for Linux-based Areca controllers with enclosures. Implemented (untested) support for Windows-based Areca controllers (thanks to Richard Kagerer). Implemented (untested) support for Linux-based HP controllers with cciss and hpsa/hpahcisr drivers (thanks to Fabrice Bacchella). Changes in Preferences no longer fail silently until rescan/restart. Better drive detection under Windows after removable drives are detached. Windows version is no longer marked as "dpi aware" since it's not supported that well. Drive attribute descriptions have been updated (including clarifications for SSDs). Added support for SSD-only and HDD-only vendor attributes. Devices having only basic info can be displayed now in the info window. Fixed BDRW drive detection (it was detected as a HDD). Other minor improvements. A number of issues have been fixed (including a crash). Any help with testing is really appreciated. Thanks, Alexander |
|
From: <ro...@sp...> - 2017-04-30 01:50:12
|
The problem is the data is getting corrupted in transit, some of the time. Kind of like a static phone call. Usually you can make out what they are saying, but not always. The CRC is catching those errors and the data is being re-transmitted. Hence if the problem is intermittent, the drive will still work, although slower. > > > On Sat, Apr 29, 2017, at 11:25 AM, Robert S wrote: >> Number 199 is indicating a problem. *USUALLY* it's cable related. Try >> replacing the sata cable and see if the raw value quits climbing. If you >> don't feel like playing with it, you can also change the sata port it's >> plugged into on the motherboard (or add-in card). > > Wow. Nice call, I woulda never have found that! Never thought that a > cable problem would allow the drive to boot and work afterwards ... > > Swapped the cable, and : > > dmesg | egrep -i "ata2|ata-2" > [ 2.771065] ata2: SATA max UDMA/133 abar m1024@0xf9fff800 port > 0xf9fffa80 irq 22 > [ 3.259806] ata2: softreset failed (device not ready) > [ 3.262990] ata2: applying PMP SRST workaround and retrying > [ 3.439709] ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300) > [ 3.455067] ata2.00: ATA-8: SAMSUNG HD103SJ, 1AJ10001, max UDMA/133 > [ 3.458119] ata2.00: 1953525168 sectors, multi 16: LBA48 NCQ (depth > 31/32), AA > [ 3.467512] ata2.00: configured for UDMA/133 > > Thanks a LOT! > > p.s. that "applying PMP SRST workaround and retrying" appears to be the > kernel successfully working around a problem becuase of > "CONFIG_SATA_PMP=y" in the kernel config. Not sure that I can do anything > abt that without compiling the kernel with a different option. Or whether > I need to. > > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > Smartmontools-support mailing list > Sma...@li... > https://lists.sourceforge.net/lists/listinfo/smartmontools-support > |
|
From: <al...@ai...> - 2017-04-29 18:41:37
|
On Sat, Apr 29, 2017, at 11:25 AM, Robert S wrote: > Number 199 is indicating a problem. *USUALLY* it's cable related. Try > replacing the sata cable and see if the raw value quits climbing. If you > don't feel like playing with it, you can also change the sata port it's > plugged into on the motherboard (or add-in card). Wow. Nice call, I woulda never have found that! Never thought that a cable problem would allow the drive to boot and work afterwards ... Swapped the cable, and : dmesg | egrep -i "ata2|ata-2" [ 2.771065] ata2: SATA max UDMA/133 abar m1024@0xf9fff800 port 0xf9fffa80 irq 22 [ 3.259806] ata2: softreset failed (device not ready) [ 3.262990] ata2: applying PMP SRST workaround and retrying [ 3.439709] ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300) [ 3.455067] ata2.00: ATA-8: SAMSUNG HD103SJ, 1AJ10001, max UDMA/133 [ 3.458119] ata2.00: 1953525168 sectors, multi 16: LBA48 NCQ (depth 31/32), AA [ 3.467512] ata2.00: configured for UDMA/133 Thanks a LOT! p.s. that "applying PMP SRST workaround and retrying" appears to be the kernel successfully working around a problem becuase of "CONFIG_SATA_PMP=y" in the kernel config. Not sure that I can do anything abt that without compiling the kernel with a different option. Or whether I need to. |
|
From: Robert S <ro...@sp...> - 2017-04-29 18:25:13
|
Number 199 is indicating a problem. *USUALLY* it's cable related. Try
replacing the sata cable and see if the raw value quits climbing. If you
don't feel like playing with it, you can also change the sata port it's
plugged into on the motherboard (or add-in card).
On 4/29/2017 1:09 PM, al...@ai... wrote:
> I've got a secondary (not 'boot' or 'root') drive attached in my system.
>
> It's "complaining" in boot logs, but seems to NOT have an issue reported by 'smartctl', and works OK after booting.
>
> I'd appreciate any ideas as to what the problem IS, or if there's really is one -- and what to do to fix it. Entirely poosible that I just don't understand what I'm seeing here :-/
>
> On boot I see these messages, but the system ends up booted and functional -- including all the data on this drive,
>
> dmesg | egrep -i "ata2|ata-2"
> [ 2.790815] ata2: SATA max UDMA/133 abar m1024@0xf9fff800 port 0xf9fff980 irq 22
> [ 3.273185] ata2: softreset failed (device not ready)
> [ 3.276322] ata2: applying PMP SRST workaround and retrying
> [ 3.456395] ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
> [ 3.468932] ata2.00: ATA-8: SAMSUNG HD103SJ, 1AJ10001, max UDMA/133
> [ 3.471995] ata2.00: 1953525168 sectors, multi 0: LBA48 NCQ (depth 31/32), AA
> [ 3.488495] ata2.00: configured for UDMA/133
> [ 35.922130] ata2.00: exception Emask 0x0 SAct 0x20000000 SErr 0x80000 action 0x6 frozen
> [ 35.926153] ata2: SError: { 10B8B }
> [ 35.930101] ata2.00: failed command: READ FPDMA QUEUED
> [ 35.934077] ata2.00: cmd 60/08:e8:00:00:00/00:00:00:00:00/40 tag 29 ncq dma 4096 in
> [ 35.942198] ata2.00: status: { DRDY }
> [ 35.946311] ata2: hard resetting link
> [ 36.426065] ata2: softreset failed (device not ready)
> [ 36.430247] ata2: applying PMP SRST workaround and retrying
> [ 36.594063] ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
> [ 36.603874] ata2.00: failed to IDENTIFY (I/O error, err_mask=0x100)
> [ 36.608124] ata2.00: revalidation failed (errno=-5)
> [ 41.797584] ata2: hard resetting link
> [ 42.277519] ata2: softreset failed (device not ready)
> [ 42.281749] ata2: applying PMP SRST workaround and retrying
> [ 42.445513] ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
> [ 42.455368] ata2.00: failed to IDENTIFY (I/O error, err_mask=0x100)
> [ 42.459702] ata2.00: revalidation failed (errno=-5)
> [ 42.464016] ata2: limiting SATA link speed to 1.5 Gbps
> [ 47.685034] ata2: hard resetting link
> [ 48.164970] ata2: softreset failed (device not ready)
> [ 48.169275] ata2: applying PMP SRST workaround and retrying
> [ 48.332964] ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
> [ 48.348678] ata2.00: configured for UDMA/133
> [ 48.352981] ata2.00: device reported invalid CHS sector 0
> [ 48.357355] ata2: EH complete
>
> 'ata2' corresponds to /dev/sdb on my system
>
> find /dev/disk | egrep -i "ata2|ata-2"
> /dev/disk/by-path/pci-0000:00:11.0-ata-2-part1
> /dev/disk/by-path/pci-0000:00:11.0-ata-2
>
> ls -al `find /dev/disk | egrep -i "ata2|ata-2"`
> lrwxrwxrwx 1 root root 9 Apr 29 10:50 /dev/disk/by-path/pci-0000:00:11.0-ata-2 -> ../../sdb
> lrwxrwxrwx 1 root root 10 Apr 29 10:50 /dev/disk/by-path/pci-0000:00:11.0-ata-2-part1 -> ../../sdb1
>
> Checking the smartctl data for that drive
>
> smartctl -H /dev/sdb
> smartctl 6.5 2016-05-07 r4318 [x86_64-linux-4.10.13-2.ge5d11ce-default] (SUSE RPM)
> Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org
>
> === START OF READ SMART DATA SECTION ===
> SMART overall-health self-assessment test result: PASSED
>
> smartctl -x /dev/sdb
> smartctl 6.5 2016-05-07 r4318 [x86_64-linux-4.10.13-2.ge5d11ce-default] (SUSE RPM)
> Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org
>
> === START OF INFORMATION SECTION ===
> Model Family: SAMSUNG SpinPoint F3
> Device Model: SAMSUNG HD103SJ
> Serial Number: S246J9EZC03669
> LU WWN Device Id: 5 0024e9 2042536ec
> Firmware Version: 1AJ10001
> User Capacity: 1,000,204,886,016 bytes [1.00 TB]
> Sector Size: 512 bytes logical/physical
> Rotation Rate: 7200 rpm
> Form Factor: 3.5 inches
> Device is: In smartctl database [for details use: -P show]
> ATA Version is: ATA8-ACS T13/1699-D revision 6
> SATA Version is: SATA 2.6, 3.0 Gb/s
> Local Time is: Sat Apr 29 10:57:37 2017 PDT
> SMART support is: Available - device has SMART capability.
> SMART support is: Enabled
> AAM feature is: Disabled
> APM feature is: Disabled
> Rd look-ahead is: Enabled
> Write cache is: Enabled
> ATA Security is: Disabled, NOT FROZEN [SEC1]
> Wt Cache Reorder: Enabled
>
> === START OF READ SMART DATA SECTION ===
> SMART overall-health self-assessment test result: PASSED
>
> General SMART Values:
> Offline data collection status: (0x82) Offline data collection activity
> was completed without error.
> 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: ( 9360) seconds.
> Offline data collection
> capabilities: (0x5b) SMART execute Offline immediate.
> Auto Offline data collection on/off support.
> Suspend Offline collection upon new
> command.
> Offline surface scan supported.
> Self-test supported.
> No 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: ( 156) minutes.
> SCT capabilities: (0x003f) 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 051 - 0
> 2 Throughput_Performance -OS--K 056 054 000 - 8531
> 3 Spin_Up_Time PO---K 075 069 025 - 7623
> 4 Start_Stop_Count -O--CK 098 098 000 - 2285
> 5 Reallocated_Sector_Ct PO--CK 252 252 010 - 0
> 7 Seek_Error_Rate -OSR-K 252 252 051 - 0
> 8 Seek_Time_Performance --S--K 252 252 015 - 0
> 9 Power_On_Hours -O--CK 100 100 000 - 27432
> 10 Spin_Retry_Count -O--CK 252 252 051 - 0
> 11 Calibration_Retry_Count -O--CK 252 252 000 - 0
> 12 Power_Cycle_Count -O--CK 098 098 000 - 2236
> 191 G-Sense_Error_Rate -O---K 100 100 000 - 24
> 192 Power-Off_Retract_Count -O---K 252 252 000 - 0
> 194 Temperature_Celsius -O---- 064 048 000 - 33 (Min/Max 15/52)
> 195 Hardware_ECC_Recovered -O-RCK 100 100 000 - 0
> 196 Reallocated_Event_Count -O--CK 252 252 000 - 0
> 197 Current_Pending_Sector -O--CK 252 252 000 - 0
> 198 Offline_Uncorrectable ----CK 252 252 000 - 0
> 199 UDMA_CRC_Error_Count -OS-CK 098 098 000 - 1162
> 200 Multi_Zone_Error_Rate -O-R-K 100 100 000 - 0
> 223 Load_Retry_Count -O--CK 252 252 000 - 0
> 225 Load_Cycle_Count -O--CK 100 100 000 - 2301
> ||||||_ K auto-keep
> |||||__ C event count
> ||||___ R error rate
> |||____ S speed/performance
> ||_____ O updated online
> |______ P prefailure warning
>
> General Purpose Log Directory Version 1
> SMART Log Directory Version 1 [multi-sector log support]
> Address Access R/W Size Description
> 0x00 GPL,SL R/O 1 Log Directory
> 0x01 SL R/O 1 Summary SMART error log
> 0x02 SL R/O 2 Comprehensive SMART error log
> 0x03 GPL R/O 2 Ext. Comprehensive SMART error log
> 0x06 SL R/O 1 SMART self-test log
> 0x07 GPL R/O 2 Extended self-test log
> 0x08 GPL R/O 2 Power Conditions log
> 0x09 SL R/W 1 Selective self-test log
> 0x10 GPL R/O 1 SATA NCQ Queued Error log
> 0x11 GPL R/O 1 SATA Phy Event Counters log
> 0x80-0x9f GPL,SL R/W 16 Host vendor specific log
> 0xe0 GPL,SL R/W 1 SCT Command/Status
> 0xe1 GPL,SL R/W 1 SCT Data Transfer
>
> SMART Extended Comprehensive Error Log Version: 1 (2 sectors)
> Device Error Count: 1162 (device log contains only the most recent 8 errors)
> CR = Command Register
> FEATR = Features Register
> COUNT = Count (was: Sector Count) Register
> LBA_48 = Upper bytes of LBA High/Mid/Low Registers ] ATA-8
> LH = LBA High (was: Cylinder High) Register ] LBA
> LM = LBA Mid (was: Cylinder Low) Register ] Register
> LL = LBA Low (was: Sector Number) Register ]
> DV = Device (was: Device/Head) Register
> DC = Device Control Register
> ER = Error register
> ST = Status register
> Powered_Up_Time is measured from power on, and printed as
> DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes,
> SS=sec, and sss=millisec. It "wraps" after 49.710 days.
>
> Error 1162 [1] occurred at disk power-on lifetime: 27432 hours (1143 days + 0 hours)
> When the command that caused the error occurred, the device was active or idle.
>
> After command completion occurred, registers were:
> ER -- ST COUNT LBA_48 LH LM LL DV DC
> -- -- -- == -- == == == -- -- -- -- --
> 84 -- 01 00 08 00 00 00 00 00 00 40 00 Error: ICRC, ABRT at LBA = 0x00000000 = 0
>
> Commands leading to the command that caused the error were:
> CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name
> -- == -- == -- == == == -- -- -- -- -- --------------- --------------------
> 60 00 00 00 08 00 00 00 00 00 00 40 00 00:00:00.000 READ FPDMA QUEUED
> 60 00 10 00 08 00 00 00 00 00 00 40 08 00:00:00.044 READ FPDMA QUEUED
> ef 00 10 00 02 00 00 00 00 00 00 a0 08 00:00:00.043 SET FEATURES [Enable SATA feature]
> 27 00 00 00 00 00 00 00 00 00 00 e0 08 00:00:00.043 READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]
> ec 00 00 00 00 00 00 00 00 00 00 a0 08 00:00:00.043 IDENTIFY DEVICE
>
> Error 1161 [0] occurred at disk power-on lifetime: 27431 hours (1142 days + 23 hours)
> When the command that caused the error occurred, the device was active or idle.
>
> After command completion occurred, registers were:
> ER -- ST COUNT LBA_48 LH LM LL DV DC
> -- -- -- == -- == == == -- -- -- -- --
> 84 -- 01 00 08 00 00 00 00 00 00 40 00 Error: ICRC, ABRT at LBA = 0x00000000 = 0
>
> Commands leading to the command that caused the error were:
> CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name
> -- == -- == -- == == == -- -- -- -- -- --------------- --------------------
> 60 00 00 00 08 00 00 00 00 00 00 40 00 00:00:00.000 READ FPDMA QUEUED
> 60 00 10 00 08 00 00 00 00 00 00 40 08 00:00:00.046 READ FPDMA QUEUED
> ef 00 10 00 02 00 00 00 00 00 00 a0 08 00:00:00.046 SET FEATURES [Enable SATA feature]
> 27 00 00 00 00 00 00 00 00 00 00 e0 08 00:00:00.046 READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]
> ec 00 00 00 00 00 00 00 00 00 00 a0 08 00:00:00.046 IDENTIFY DEVICE
>
> Error 1160 [7] occurred at disk power-on lifetime: 27431 hours (1142 days + 23 hours)
> When the command that caused the error occurred, the device was active or idle.
>
> After command completion occurred, registers were:
> ER -- ST COUNT LBA_48 LH LM LL DV DC
> -- -- -- == -- == == == -- -- -- -- --
> 84 -- 51 00 01 00 00 00 00 00 00 e0 00 Error: ICRC, ABRT 1 sectors at LBA = 0x00000000 = 0
>
> Commands leading to the command that caused the error were:
> CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name
> -- == -- == -- == == == -- -- -- -- -- --------------- --------------------
> 25 20 20 00 01 00 00 00 00 00 00 e0 00 00:00:00.036 READ DMA EXT
> c6 00 20 00 10 00 00 00 00 00 00 ef 00 00:00:00.036 SET MULTIPLE MODE
> 91 00 20 00 3f 00 00 00 00 00 00 ef 00 00:00:00.036 INITIALIZE DEVICE PARAMETERS [OBS-6]
> 10 00 20 00 01 00 00 00 00 00 01 e0 00 00:00:00.036 RECALIBRATE [OBS-4]
> 00 00 00 00 01 00 00 00 00 00 01 40 00 00:00:00.036 NOP [Abort queued commands]
>
> Error 1159 [6] occurred at disk power-on lifetime: 27431 hours (1142 days + 23 hours)
> When the command that caused the error occurred, the device was active or idle.
>
> After command completion occurred, registers were:
> ER -- ST COUNT LBA_48 LH LM LL DV DC
> -- -- -- == -- == == == -- -- -- -- --
> 84 -- 51 00 3f 00 00 00 00 00 00 e0 00 Error: ICRC, ABRT 63 sectors at LBA = 0x00000000 = 0
>
> Commands leading to the command that caused the error were:
> CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name
> -- == -- == -- == == == -- -- -- -- -- --------------- --------------------
> 25 20 20 00 3f 00 00 00 00 00 00 e0 00 00:00:00.036 READ DMA EXT
> c6 00 20 00 10 00 00 00 00 00 00 ef 00 00:00:00.036 SET MULTIPLE MODE
> 91 00 20 00 3f 00 00 00 00 00 00 ef 00 00:00:00.036 INITIALIZE DEVICE PARAMETERS [OBS-6]
> 10 00 20 00 01 00 00 00 00 00 01 e0 00 00:00:00.036 RECALIBRATE [OBS-4]
> 00 00 00 00 01 00 00 00 00 00 01 40 00 00:00:00.036 NOP [Abort queued commands]
>
> Error 1158 [5] occurred at disk power-on lifetime: 27431 hours (1142 days + 23 hours)
> When the command that caused the error occurred, the device was active or idle.
>
> After command completion occurred, registers were:
> ER -- ST COUNT LBA_48 LH LM LL DV DC
> -- -- -- == -- == == == -- -- -- -- --
> 84 -- 51 00 3f 00 00 00 00 00 00 e0 00 Error: ICRC, ABRT 63 sectors at LBA = 0x00000000 = 0
>
> Commands leading to the command that caused the error were:
> CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name
> -- == -- == -- == == == -- -- -- -- -- --------------- --------------------
> 25 20 20 00 3f 00 00 00 00 00 00 e0 00 00:00:00.036 READ DMA EXT
> c6 00 20 00 10 00 00 00 00 00 00 ef 00 00:00:00.036 SET MULTIPLE MODE
> 91 00 20 00 3f 00 00 00 00 00 00 ef 00 00:00:00.036 INITIALIZE DEVICE PARAMETERS [OBS-6]
> 10 00 20 00 01 00 00 00 00 00 01 e0 00 00:00:00.036 RECALIBRATE [OBS-4]
> 00 00 00 00 01 00 00 00 00 00 01 40 00 00:00:00.036 NOP [Abort queued commands]
>
> Error 1157 [4] occurred at disk power-on lifetime: 27431 hours (1142 days + 23 hours)
> When the command that caused the error occurred, the device was active or idle.
>
> After command completion occurred, registers were:
> ER -- ST COUNT LBA_48 LH LM LL DV DC
> -- -- -- == -- == == == -- -- -- -- --
> 84 -- 51 00 3f 00 00 00 00 00 00 e0 00 Error: ICRC, ABRT 63 sectors at LBA = 0x00000000 = 0
>
> Commands leading to the command that caused the error were:
> CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name
> -- == -- == -- == == == -- -- -- -- -- --------------- --------------------
> 25 20 20 00 3f 00 00 00 00 00 00 e0 00 00:00:00.036 READ DMA EXT
> 25 20 20 00 01 00 00 00 00 00 08 e0 00 00:00:00.036 READ DMA EXT
> c6 00 20 00 10 00 00 00 00 00 00 ef 00 00:00:00.036 SET MULTIPLE MODE
> 91 00 20 00 3f 00 00 00 00 00 00 ef 00 00:00:00.036 INITIALIZE DEVICE PARAMETERS [OBS-6]
> 10 00 20 00 01 00 00 00 00 00 01 e0 00 00:00:00.036 RECALIBRATE [OBS-4]
>
> Error 1156 [3] occurred at disk power-on lifetime: 27431 hours (1142 days + 23 hours)
> When the command that caused the error occurred, the device was active or idle.
>
> After command completion occurred, registers were:
> ER -- ST COUNT LBA_48 LH LM LL DV DC
> -- -- -- == -- == == == -- -- -- -- --
> 84 -- 51 00 09 00 00 00 00 00 00 e0 00 Error: ICRC, ABRT 9 sectors at LBA = 0x00000000 = 0
>
> Commands leading to the command that caused the error were:
> CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name
> -- == -- == -- == == == -- -- -- -- -- --------------- --------------------
> 25 20 20 00 01 00 00 00 00 00 08 e0 00 00:00:00.036 READ DMA EXT
> c6 00 20 00 10 00 00 00 00 00 00 ef 00 00:00:00.036 SET MULTIPLE MODE
> 91 00 20 00 3f 00 00 00 00 00 00 ef 00 00:00:00.036 INITIALIZE DEVICE PARAMETERS [OBS-6]
> 10 00 20 00 01 00 00 00 00 00 01 e0 00 00:00:00.036 RECALIBRATE [OBS-4]
> 00 00 00 00 01 00 00 00 00 00 01 40 00 00:00:00.036 NOP [Abort queued commands]
>
> Error 1155 [2] occurred at disk power-on lifetime: 27431 hours (1142 days + 23 hours)
> When the command that caused the error occurred, the device was active or idle.
>
> After command completion occurred, registers were:
> ER -- ST COUNT LBA_48 LH LM LL DV DC
> -- -- -- == -- == == == -- -- -- -- --
> 84 -- 51 00 3f 00 00 00 00 00 00 e0 00 Error: ICRC, ABRT 63 sectors at LBA = 0x00000000 = 0
>
> Commands leading to the command that caused the error were:
> CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name
> -- == -- == -- == == == -- -- -- -- -- --------------- --------------------
> 25 20 20 00 3f 00 00 00 00 00 00 e0 00 00:00:00.036 READ DMA EXT
> c6 00 20 00 10 00 00 00 00 00 00 ef 00 00:00:00.036 SET MULTIPLE MODE
> 91 00 20 00 3f 00 00 00 00 00 00 ef 00 00:00:00.036 INITIALIZE DEVICE PARAMETERS [OBS-6]
> 10 00 20 00 01 00 00 00 00 00 01 e0 00 00:00:00.036 RECALIBRATE [OBS-4]
> 00 00 00 00 01 00 00 00 00 00 01 40 00 00:00:00.036 NOP [Abort queued commands]
>
> SMART Extended Self-test Log Version: 1 (2 sectors)
> Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error
> # 1 Short offline Completed without error 00% 4157 -
> # 2 Short offline Completed without error 00% 4114 -
> # 3 Extended offline Completed without error 00% 4073 -
> # 4 Short offline Completed without error 00% 4056 -
> # 5 Short offline Completed without error 00% 4011 -
> # 6 Extended offline Completed without error 00% 3968 -
> # 7 Short offline Completed without error 00% 3949 -
> # 8 Short offline Completed without error 00% 3905 -
> # 9 Extended offline Completed without error 00% 3903 -
> #10 Short offline Completed without error 00% 3846 -
> #11 Short offline Completed without error 00% 3801 -
> #12 Extended offline Completed without error 00% 3761 -
> #13 Short offline Completed without error 00% 3745 -
> #14 Extended offline Completed without error 00% 3664 -
> #15 Short offline Completed without error 00% 3646 -
> #16 Short offline Completed without error 00% 3606 -
> #17 Extended offline Completed without error 00% 3568 -
> #18 Short offline Completed without error 00% 3552 -
> #19 Short offline Completed without error 00% 3507 -
> #20 Extended offline Completed without error 00% 3468 -
> #21 Short offline Completed without error 00% 3451 -
>
> SMART Selective self-test log data structure revision number 0
> Note: revision number not 1 implies that no selective self-test has ever been run
> SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS
> 1 0 0 Completed [00% left] (0-65535)
> 2 0 0 Not_testing
> 3 0 0 Not_testing
> 4 0 0 Not_testing
> 5 0 0 Not_testing
> Selective self-test flags (0x0):
> After scanning selected spans, do NOT read-scan remainder of disk.
> If Selective self-test is pending on power-up, resume after 0 minute delay.
>
> SCT Status Version: 2
> SCT Version (vendor specific): 256 (0x0100)
> SCT Support Level: 1
> Device State: Active (0)
> Current Temperature: 33 Celsius
> Power Cycle Min/Max Temperature: 33/33 Celsius
> Lifetime Min/Max Temperature: 18/65 Celsius
> Under/Over Temperature Limit Count: 0/0
>
> SCT Temperature History Version: 2
> Temperature Sampling Period: 5 minutes
> Temperature Logging Interval: 5 minutes
> Min/Max recommended Temperature: -5/80 Celsius
> Min/Max Temperature Limit: -10/85 Celsius
> Temperature History Size (Index): 128 (114)
>
> Index Estimated Time Temperature Celsius
> 115 2017-04-29 00:20 32 *************
> ... ..( 5 skipped). .. *************
> 121 2017-04-29 00:50 32 *************
> 122 2017-04-29 00:55 34 ***************
> 123 2017-04-29 01:00 36 *****************
> 124 2017-04-29 01:05 36 *****************
> 125 2017-04-29 01:10 37 ******************
> ... ..( 10 skipped). .. ******************
> 8 2017-04-29 02:05 37 ******************
> 9 2017-04-29 02:10 36 *****************
> 10 2017-04-29 02:15 35 ****************
> 11 2017-04-29 02:20 35 ****************
> 12 2017-04-29 02:25 34 ***************
> ... ..( 6 skipped). .. ***************
> 19 2017-04-29 03:00 34 ***************
> 20 2017-04-29 03:05 33 **************
> ... ..( 3 skipped). .. **************
> 24 2017-04-29 03:25 33 **************
> 25 2017-04-29 03:30 34 ***************
> ... ..( 26 skipped). .. ***************
> 52 2017-04-29 05:45 34 ***************
> 53 2017-04-29 05:50 35 ****************
> ... ..( 11 skipped). .. ****************
> 65 2017-04-29 06:50 35 ****************
> 66 2017-04-29 06:55 36 *****************
> 67 2017-04-29 07:00 35 ****************
> ... ..( 5 skipped). .. ****************
> 73 2017-04-29 07:30 35 ****************
> 74 2017-04-29 07:35 36 *****************
> 75 2017-04-29 07:40 35 ****************
> ... ..( 10 skipped). .. ****************
> 86 2017-04-29 08:35 35 ****************
> 87 2017-04-29 08:40 34 ***************
> 88 2017-04-29 08:45 33 **************
> 89 2017-04-29 08:50 33 **************
> 90 2017-04-29 08:55 21 **
> 91 2017-04-29 09:00 24 *****
> 92 2017-04-29 09:05 26 *******
> 93 2017-04-29 09:10 27 ********
> 94 2017-04-29 09:15 28 *********
> 95 2017-04-29 09:20 29 **********
> 96 2017-04-29 09:25 30 ***********
> 97 2017-04-29 09:30 30 ***********
> 98 2017-04-29 09:35 31 ************
> 99 2017-04-29 09:40 31 ************
> 100 2017-04-29 09:45 32 *************
> ... ..( 2 skipped). .. *************
> 103 2017-04-29 10:00 32 *************
> 104 2017-04-29 10:05 33 **************
> ... ..( 9 skipped). .. **************
> 114 2017-04-29 10:55 33 **************
>
> SCT Error Recovery Control:
> Read: Disabled
> Write: Disabled
>
> Device Statistics (GP/SMART Log 0x04) not supported
>
> SATA Phy Event Counters (GP Log 0x11)
> ID Size Value Description
> 0x0001 4 1 Command failed due to ICRC error
> 0x0002 4 5 R_ERR response for data FIS
> 0x0003 4 5 R_ERR response for device-to-host data FIS
> 0x0004 4 0 R_ERR response for host-to-device data FIS
> 0x0005 4 1 R_ERR response for non-data FIS
> 0x0006 4 1 R_ERR response for device-to-host non-data FIS
> 0x0007 4 0 R_ERR response for host-to-device non-data FIS
> 0x0008 4 1 Device-to-host non-data FIS retries
> 0x0009 4 8 Transition from drive PhyRdy to drive PhyNRdy
> 0x000a 4 6 Device-to-host register FISes sent due to a COMRESET
> 0x000b 4 0 CRC errors within host-to-device FIS
> 0x000d 4 0 Non-CRC errors within host-to-device FIS
> 0x000f 4 0 R_ERR response for host-to-device data FIS, CRC
> 0x0010 4 0 R_ERR response for host-to-device data FIS, non-CRC
> 0x0012 4 0 R_ERR response for host-to-device non-data FIS, CRC
> 0x0013 4 0 R_ERR response for host-to-device non-data FIS, non-CRC
> 0x8e00 4 1 Vendor specific
> 0x8e01 4 6 Vendor specific
> 0x8e02 4 0 Vendor specific
> 0x8e03 4 0 Vendor specific
> 0x8e04 4 0 Vendor specific
> 0x8e05 4 0 Vendor specific
> 0x8e06 4 1 Vendor specific
> 0x8e07 4 2 Vendor specific
> 0x8e08 4 6 Vendor specific
> 0x8e09 4 0 Vendor specific
> 0x8e0a 4 26 Vendor specific
> 0x8e0b 4 1792 Vendor specific
> 0x8e0c 4 110 Vendor specific
> 0x8e0d 4 0 Vendor specific
> 0x8e0e 4 26 Vendor specific
> 0x8e0f 4 0 Vendor specific
> 0x8e10 4 104 Vendor specific
> 0x8e11 4 6 Vendor specific
>
>
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> Smartmontools-support mailing list
> Sma...@li...
> https://lists.sourceforge.net/lists/listinfo/smartmontools-support
|
|
From: <al...@ai...> - 2017-04-29 18:19:07
|
I've got a secondary (not 'boot' or 'root') drive attached in my system.
It's "complaining" in boot logs, but seems to NOT have an issue reported by 'smartctl', and works OK after booting.
I'd appreciate any ideas as to what the problem IS, or if there's really is one -- and what to do to fix it. Entirely poosible that I just don't understand what I'm seeing here :-/
On boot I see these messages, but the system ends up booted and functional -- including all the data on this drive,
dmesg | egrep -i "ata2|ata-2"
[ 2.790815] ata2: SATA max UDMA/133 abar m1024@0xf9fff800 port 0xf9fff980 irq 22
[ 3.273185] ata2: softreset failed (device not ready)
[ 3.276322] ata2: applying PMP SRST workaround and retrying
[ 3.456395] ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 3.468932] ata2.00: ATA-8: SAMSUNG HD103SJ, 1AJ10001, max UDMA/133
[ 3.471995] ata2.00: 1953525168 sectors, multi 0: LBA48 NCQ (depth 31/32), AA
[ 3.488495] ata2.00: configured for UDMA/133
[ 35.922130] ata2.00: exception Emask 0x0 SAct 0x20000000 SErr 0x80000 action 0x6 frozen
[ 35.926153] ata2: SError: { 10B8B }
[ 35.930101] ata2.00: failed command: READ FPDMA QUEUED
[ 35.934077] ata2.00: cmd 60/08:e8:00:00:00/00:00:00:00:00/40 tag 29 ncq dma 4096 in
[ 35.942198] ata2.00: status: { DRDY }
[ 35.946311] ata2: hard resetting link
[ 36.426065] ata2: softreset failed (device not ready)
[ 36.430247] ata2: applying PMP SRST workaround and retrying
[ 36.594063] ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 36.603874] ata2.00: failed to IDENTIFY (I/O error, err_mask=0x100)
[ 36.608124] ata2.00: revalidation failed (errno=-5)
[ 41.797584] ata2: hard resetting link
[ 42.277519] ata2: softreset failed (device not ready)
[ 42.281749] ata2: applying PMP SRST workaround and retrying
[ 42.445513] ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 42.455368] ata2.00: failed to IDENTIFY (I/O error, err_mask=0x100)
[ 42.459702] ata2.00: revalidation failed (errno=-5)
[ 42.464016] ata2: limiting SATA link speed to 1.5 Gbps
[ 47.685034] ata2: hard resetting link
[ 48.164970] ata2: softreset failed (device not ready)
[ 48.169275] ata2: applying PMP SRST workaround and retrying
[ 48.332964] ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[ 48.348678] ata2.00: configured for UDMA/133
[ 48.352981] ata2.00: device reported invalid CHS sector 0
[ 48.357355] ata2: EH complete
'ata2' corresponds to /dev/sdb on my system
find /dev/disk | egrep -i "ata2|ata-2"
/dev/disk/by-path/pci-0000:00:11.0-ata-2-part1
/dev/disk/by-path/pci-0000:00:11.0-ata-2
ls -al `find /dev/disk | egrep -i "ata2|ata-2"`
lrwxrwxrwx 1 root root 9 Apr 29 10:50 /dev/disk/by-path/pci-0000:00:11.0-ata-2 -> ../../sdb
lrwxrwxrwx 1 root root 10 Apr 29 10:50 /dev/disk/by-path/pci-0000:00:11.0-ata-2-part1 -> ../../sdb1
Checking the smartctl data for that drive
smartctl -H /dev/sdb
smartctl 6.5 2016-05-07 r4318 [x86_64-linux-4.10.13-2.ge5d11ce-default] (SUSE RPM)
Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED
smartctl -x /dev/sdb
smartctl 6.5 2016-05-07 r4318 [x86_64-linux-4.10.13-2.ge5d11ce-default] (SUSE RPM)
Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF INFORMATION SECTION ===
Model Family: SAMSUNG SpinPoint F3
Device Model: SAMSUNG HD103SJ
Serial Number: S246J9EZC03669
LU WWN Device Id: 5 0024e9 2042536ec
Firmware Version: 1AJ10001
User Capacity: 1,000,204,886,016 bytes [1.00 TB]
Sector Size: 512 bytes logical/physical
Rotation Rate: 7200 rpm
Form Factor: 3.5 inches
Device is: In smartctl database [for details use: -P show]
ATA Version is: ATA8-ACS T13/1699-D revision 6
SATA Version is: SATA 2.6, 3.0 Gb/s
Local Time is: Sat Apr 29 10:57:37 2017 PDT
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
AAM feature is: Disabled
APM feature is: Disabled
Rd look-ahead is: Enabled
Write cache is: Enabled
ATA Security is: Disabled, NOT FROZEN [SEC1]
Wt Cache Reorder: Enabled
=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED
General SMART Values:
Offline data collection status: (0x82) Offline data collection activity
was completed without error.
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: ( 9360) seconds.
Offline data collection
capabilities: (0x5b) SMART execute Offline immediate.
Auto Offline data collection on/off support.
Suspend Offline collection upon new
command.
Offline surface scan supported.
Self-test supported.
No 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: ( 156) minutes.
SCT capabilities: (0x003f) 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 051 - 0
2 Throughput_Performance -OS--K 056 054 000 - 8531
3 Spin_Up_Time PO---K 075 069 025 - 7623
4 Start_Stop_Count -O--CK 098 098 000 - 2285
5 Reallocated_Sector_Ct PO--CK 252 252 010 - 0
7 Seek_Error_Rate -OSR-K 252 252 051 - 0
8 Seek_Time_Performance --S--K 252 252 015 - 0
9 Power_On_Hours -O--CK 100 100 000 - 27432
10 Spin_Retry_Count -O--CK 252 252 051 - 0
11 Calibration_Retry_Count -O--CK 252 252 000 - 0
12 Power_Cycle_Count -O--CK 098 098 000 - 2236
191 G-Sense_Error_Rate -O---K 100 100 000 - 24
192 Power-Off_Retract_Count -O---K 252 252 000 - 0
194 Temperature_Celsius -O---- 064 048 000 - 33 (Min/Max 15/52)
195 Hardware_ECC_Recovered -O-RCK 100 100 000 - 0
196 Reallocated_Event_Count -O--CK 252 252 000 - 0
197 Current_Pending_Sector -O--CK 252 252 000 - 0
198 Offline_Uncorrectable ----CK 252 252 000 - 0
199 UDMA_CRC_Error_Count -OS-CK 098 098 000 - 1162
200 Multi_Zone_Error_Rate -O-R-K 100 100 000 - 0
223 Load_Retry_Count -O--CK 252 252 000 - 0
225 Load_Cycle_Count -O--CK 100 100 000 - 2301
||||||_ K auto-keep
|||||__ C event count
||||___ R error rate
|||____ S speed/performance
||_____ O updated online
|______ P prefailure warning
General Purpose Log Directory Version 1
SMART Log Directory Version 1 [multi-sector log support]
Address Access R/W Size Description
0x00 GPL,SL R/O 1 Log Directory
0x01 SL R/O 1 Summary SMART error log
0x02 SL R/O 2 Comprehensive SMART error log
0x03 GPL R/O 2 Ext. Comprehensive SMART error log
0x06 SL R/O 1 SMART self-test log
0x07 GPL R/O 2 Extended self-test log
0x08 GPL R/O 2 Power Conditions log
0x09 SL R/W 1 Selective self-test log
0x10 GPL R/O 1 SATA NCQ Queued Error log
0x11 GPL R/O 1 SATA Phy Event Counters log
0x80-0x9f GPL,SL R/W 16 Host vendor specific log
0xe0 GPL,SL R/W 1 SCT Command/Status
0xe1 GPL,SL R/W 1 SCT Data Transfer
SMART Extended Comprehensive Error Log Version: 1 (2 sectors)
Device Error Count: 1162 (device log contains only the most recent 8 errors)
CR = Command Register
FEATR = Features Register
COUNT = Count (was: Sector Count) Register
LBA_48 = Upper bytes of LBA High/Mid/Low Registers ] ATA-8
LH = LBA High (was: Cylinder High) Register ] LBA
LM = LBA Mid (was: Cylinder Low) Register ] Register
LL = LBA Low (was: Sector Number) Register ]
DV = Device (was: Device/Head) Register
DC = Device Control Register
ER = Error register
ST = Status register
Powered_Up_Time is measured from power on, and printed as
DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes,
SS=sec, and sss=millisec. It "wraps" after 49.710 days.
Error 1162 [1] occurred at disk power-on lifetime: 27432 hours (1143 days + 0 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER -- ST COUNT LBA_48 LH LM LL DV DC
-- -- -- == -- == == == -- -- -- -- --
84 -- 01 00 08 00 00 00 00 00 00 40 00 Error: ICRC, ABRT at LBA = 0x00000000 = 0
Commands leading to the command that caused the error were:
CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name
-- == -- == -- == == == -- -- -- -- -- --------------- --------------------
60 00 00 00 08 00 00 00 00 00 00 40 00 00:00:00.000 READ FPDMA QUEUED
60 00 10 00 08 00 00 00 00 00 00 40 08 00:00:00.044 READ FPDMA QUEUED
ef 00 10 00 02 00 00 00 00 00 00 a0 08 00:00:00.043 SET FEATURES [Enable SATA feature]
27 00 00 00 00 00 00 00 00 00 00 e0 08 00:00:00.043 READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]
ec 00 00 00 00 00 00 00 00 00 00 a0 08 00:00:00.043 IDENTIFY DEVICE
Error 1161 [0] occurred at disk power-on lifetime: 27431 hours (1142 days + 23 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER -- ST COUNT LBA_48 LH LM LL DV DC
-- -- -- == -- == == == -- -- -- -- --
84 -- 01 00 08 00 00 00 00 00 00 40 00 Error: ICRC, ABRT at LBA = 0x00000000 = 0
Commands leading to the command that caused the error were:
CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name
-- == -- == -- == == == -- -- -- -- -- --------------- --------------------
60 00 00 00 08 00 00 00 00 00 00 40 00 00:00:00.000 READ FPDMA QUEUED
60 00 10 00 08 00 00 00 00 00 00 40 08 00:00:00.046 READ FPDMA QUEUED
ef 00 10 00 02 00 00 00 00 00 00 a0 08 00:00:00.046 SET FEATURES [Enable SATA feature]
27 00 00 00 00 00 00 00 00 00 00 e0 08 00:00:00.046 READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]
ec 00 00 00 00 00 00 00 00 00 00 a0 08 00:00:00.046 IDENTIFY DEVICE
Error 1160 [7] occurred at disk power-on lifetime: 27431 hours (1142 days + 23 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER -- ST COUNT LBA_48 LH LM LL DV DC
-- -- -- == -- == == == -- -- -- -- --
84 -- 51 00 01 00 00 00 00 00 00 e0 00 Error: ICRC, ABRT 1 sectors at LBA = 0x00000000 = 0
Commands leading to the command that caused the error were:
CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name
-- == -- == -- == == == -- -- -- -- -- --------------- --------------------
25 20 20 00 01 00 00 00 00 00 00 e0 00 00:00:00.036 READ DMA EXT
c6 00 20 00 10 00 00 00 00 00 00 ef 00 00:00:00.036 SET MULTIPLE MODE
91 00 20 00 3f 00 00 00 00 00 00 ef 00 00:00:00.036 INITIALIZE DEVICE PARAMETERS [OBS-6]
10 00 20 00 01 00 00 00 00 00 01 e0 00 00:00:00.036 RECALIBRATE [OBS-4]
00 00 00 00 01 00 00 00 00 00 01 40 00 00:00:00.036 NOP [Abort queued commands]
Error 1159 [6] occurred at disk power-on lifetime: 27431 hours (1142 days + 23 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER -- ST COUNT LBA_48 LH LM LL DV DC
-- -- -- == -- == == == -- -- -- -- --
84 -- 51 00 3f 00 00 00 00 00 00 e0 00 Error: ICRC, ABRT 63 sectors at LBA = 0x00000000 = 0
Commands leading to the command that caused the error were:
CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name
-- == -- == -- == == == -- -- -- -- -- --------------- --------------------
25 20 20 00 3f 00 00 00 00 00 00 e0 00 00:00:00.036 READ DMA EXT
c6 00 20 00 10 00 00 00 00 00 00 ef 00 00:00:00.036 SET MULTIPLE MODE
91 00 20 00 3f 00 00 00 00 00 00 ef 00 00:00:00.036 INITIALIZE DEVICE PARAMETERS [OBS-6]
10 00 20 00 01 00 00 00 00 00 01 e0 00 00:00:00.036 RECALIBRATE [OBS-4]
00 00 00 00 01 00 00 00 00 00 01 40 00 00:00:00.036 NOP [Abort queued commands]
Error 1158 [5] occurred at disk power-on lifetime: 27431 hours (1142 days + 23 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER -- ST COUNT LBA_48 LH LM LL DV DC
-- -- -- == -- == == == -- -- -- -- --
84 -- 51 00 3f 00 00 00 00 00 00 e0 00 Error: ICRC, ABRT 63 sectors at LBA = 0x00000000 = 0
Commands leading to the command that caused the error were:
CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name
-- == -- == -- == == == -- -- -- -- -- --------------- --------------------
25 20 20 00 3f 00 00 00 00 00 00 e0 00 00:00:00.036 READ DMA EXT
c6 00 20 00 10 00 00 00 00 00 00 ef 00 00:00:00.036 SET MULTIPLE MODE
91 00 20 00 3f 00 00 00 00 00 00 ef 00 00:00:00.036 INITIALIZE DEVICE PARAMETERS [OBS-6]
10 00 20 00 01 00 00 00 00 00 01 e0 00 00:00:00.036 RECALIBRATE [OBS-4]
00 00 00 00 01 00 00 00 00 00 01 40 00 00:00:00.036 NOP [Abort queued commands]
Error 1157 [4] occurred at disk power-on lifetime: 27431 hours (1142 days + 23 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER -- ST COUNT LBA_48 LH LM LL DV DC
-- -- -- == -- == == == -- -- -- -- --
84 -- 51 00 3f 00 00 00 00 00 00 e0 00 Error: ICRC, ABRT 63 sectors at LBA = 0x00000000 = 0
Commands leading to the command that caused the error were:
CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name
-- == -- == -- == == == -- -- -- -- -- --------------- --------------------
25 20 20 00 3f 00 00 00 00 00 00 e0 00 00:00:00.036 READ DMA EXT
25 20 20 00 01 00 00 00 00 00 08 e0 00 00:00:00.036 READ DMA EXT
c6 00 20 00 10 00 00 00 00 00 00 ef 00 00:00:00.036 SET MULTIPLE MODE
91 00 20 00 3f 00 00 00 00 00 00 ef 00 00:00:00.036 INITIALIZE DEVICE PARAMETERS [OBS-6]
10 00 20 00 01 00 00 00 00 00 01 e0 00 00:00:00.036 RECALIBRATE [OBS-4]
Error 1156 [3] occurred at disk power-on lifetime: 27431 hours (1142 days + 23 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER -- ST COUNT LBA_48 LH LM LL DV DC
-- -- -- == -- == == == -- -- -- -- --
84 -- 51 00 09 00 00 00 00 00 00 e0 00 Error: ICRC, ABRT 9 sectors at LBA = 0x00000000 = 0
Commands leading to the command that caused the error were:
CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name
-- == -- == -- == == == -- -- -- -- -- --------------- --------------------
25 20 20 00 01 00 00 00 00 00 08 e0 00 00:00:00.036 READ DMA EXT
c6 00 20 00 10 00 00 00 00 00 00 ef 00 00:00:00.036 SET MULTIPLE MODE
91 00 20 00 3f 00 00 00 00 00 00 ef 00 00:00:00.036 INITIALIZE DEVICE PARAMETERS [OBS-6]
10 00 20 00 01 00 00 00 00 00 01 e0 00 00:00:00.036 RECALIBRATE [OBS-4]
00 00 00 00 01 00 00 00 00 00 01 40 00 00:00:00.036 NOP [Abort queued commands]
Error 1155 [2] occurred at disk power-on lifetime: 27431 hours (1142 days + 23 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER -- ST COUNT LBA_48 LH LM LL DV DC
-- -- -- == -- == == == -- -- -- -- --
84 -- 51 00 3f 00 00 00 00 00 00 e0 00 Error: ICRC, ABRT 63 sectors at LBA = 0x00000000 = 0
Commands leading to the command that caused the error were:
CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name
-- == -- == -- == == == -- -- -- -- -- --------------- --------------------
25 20 20 00 3f 00 00 00 00 00 00 e0 00 00:00:00.036 READ DMA EXT
c6 00 20 00 10 00 00 00 00 00 00 ef 00 00:00:00.036 SET MULTIPLE MODE
91 00 20 00 3f 00 00 00 00 00 00 ef 00 00:00:00.036 INITIALIZE DEVICE PARAMETERS [OBS-6]
10 00 20 00 01 00 00 00 00 00 01 e0 00 00:00:00.036 RECALIBRATE [OBS-4]
00 00 00 00 01 00 00 00 00 00 01 40 00 00:00:00.036 NOP [Abort queued commands]
SMART Extended Self-test Log Version: 1 (2 sectors)
Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error
# 1 Short offline Completed without error 00% 4157 -
# 2 Short offline Completed without error 00% 4114 -
# 3 Extended offline Completed without error 00% 4073 -
# 4 Short offline Completed without error 00% 4056 -
# 5 Short offline Completed without error 00% 4011 -
# 6 Extended offline Completed without error 00% 3968 -
# 7 Short offline Completed without error 00% 3949 -
# 8 Short offline Completed without error 00% 3905 -
# 9 Extended offline Completed without error 00% 3903 -
#10 Short offline Completed without error 00% 3846 -
#11 Short offline Completed without error 00% 3801 -
#12 Extended offline Completed without error 00% 3761 -
#13 Short offline Completed without error 00% 3745 -
#14 Extended offline Completed without error 00% 3664 -
#15 Short offline Completed without error 00% 3646 -
#16 Short offline Completed without error 00% 3606 -
#17 Extended offline Completed without error 00% 3568 -
#18 Short offline Completed without error 00% 3552 -
#19 Short offline Completed without error 00% 3507 -
#20 Extended offline Completed without error 00% 3468 -
#21 Short offline Completed without error 00% 3451 -
SMART Selective self-test log data structure revision number 0
Note: revision number not 1 implies that no selective self-test has ever been run
SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS
1 0 0 Completed [00% left] (0-65535)
2 0 0 Not_testing
3 0 0 Not_testing
4 0 0 Not_testing
5 0 0 Not_testing
Selective self-test flags (0x0):
After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.
SCT Status Version: 2
SCT Version (vendor specific): 256 (0x0100)
SCT Support Level: 1
Device State: Active (0)
Current Temperature: 33 Celsius
Power Cycle Min/Max Temperature: 33/33 Celsius
Lifetime Min/Max Temperature: 18/65 Celsius
Under/Over Temperature Limit Count: 0/0
SCT Temperature History Version: 2
Temperature Sampling Period: 5 minutes
Temperature Logging Interval: 5 minutes
Min/Max recommended Temperature: -5/80 Celsius
Min/Max Temperature Limit: -10/85 Celsius
Temperature History Size (Index): 128 (114)
Index Estimated Time Temperature Celsius
115 2017-04-29 00:20 32 *************
... ..( 5 skipped). .. *************
121 2017-04-29 00:50 32 *************
122 2017-04-29 00:55 34 ***************
123 2017-04-29 01:00 36 *****************
124 2017-04-29 01:05 36 *****************
125 2017-04-29 01:10 37 ******************
... ..( 10 skipped). .. ******************
8 2017-04-29 02:05 37 ******************
9 2017-04-29 02:10 36 *****************
10 2017-04-29 02:15 35 ****************
11 2017-04-29 02:20 35 ****************
12 2017-04-29 02:25 34 ***************
... ..( 6 skipped). .. ***************
19 2017-04-29 03:00 34 ***************
20 2017-04-29 03:05 33 **************
... ..( 3 skipped). .. **************
24 2017-04-29 03:25 33 **************
25 2017-04-29 03:30 34 ***************
... ..( 26 skipped). .. ***************
52 2017-04-29 05:45 34 ***************
53 2017-04-29 05:50 35 ****************
... ..( 11 skipped). .. ****************
65 2017-04-29 06:50 35 ****************
66 2017-04-29 06:55 36 *****************
67 2017-04-29 07:00 35 ****************
... ..( 5 skipped). .. ****************
73 2017-04-29 07:30 35 ****************
74 2017-04-29 07:35 36 *****************
75 2017-04-29 07:40 35 ****************
... ..( 10 skipped). .. ****************
86 2017-04-29 08:35 35 ****************
87 2017-04-29 08:40 34 ***************
88 2017-04-29 08:45 33 **************
89 2017-04-29 08:50 33 **************
90 2017-04-29 08:55 21 **
91 2017-04-29 09:00 24 *****
92 2017-04-29 09:05 26 *******
93 2017-04-29 09:10 27 ********
94 2017-04-29 09:15 28 *********
95 2017-04-29 09:20 29 **********
96 2017-04-29 09:25 30 ***********
97 2017-04-29 09:30 30 ***********
98 2017-04-29 09:35 31 ************
99 2017-04-29 09:40 31 ************
100 2017-04-29 09:45 32 *************
... ..( 2 skipped). .. *************
103 2017-04-29 10:00 32 *************
104 2017-04-29 10:05 33 **************
... ..( 9 skipped). .. **************
114 2017-04-29 10:55 33 **************
SCT Error Recovery Control:
Read: Disabled
Write: Disabled
Device Statistics (GP/SMART Log 0x04) not supported
SATA Phy Event Counters (GP Log 0x11)
ID Size Value Description
0x0001 4 1 Command failed due to ICRC error
0x0002 4 5 R_ERR response for data FIS
0x0003 4 5 R_ERR response for device-to-host data FIS
0x0004 4 0 R_ERR response for host-to-device data FIS
0x0005 4 1 R_ERR response for non-data FIS
0x0006 4 1 R_ERR response for device-to-host non-data FIS
0x0007 4 0 R_ERR response for host-to-device non-data FIS
0x0008 4 1 Device-to-host non-data FIS retries
0x0009 4 8 Transition from drive PhyRdy to drive PhyNRdy
0x000a 4 6 Device-to-host register FISes sent due to a COMRESET
0x000b 4 0 CRC errors within host-to-device FIS
0x000d 4 0 Non-CRC errors within host-to-device FIS
0x000f 4 0 R_ERR response for host-to-device data FIS, CRC
0x0010 4 0 R_ERR response for host-to-device data FIS, non-CRC
0x0012 4 0 R_ERR response for host-to-device non-data FIS, CRC
0x0013 4 0 R_ERR response for host-to-device non-data FIS, non-CRC
0x8e00 4 1 Vendor specific
0x8e01 4 6 Vendor specific
0x8e02 4 0 Vendor specific
0x8e03 4 0 Vendor specific
0x8e04 4 0 Vendor specific
0x8e05 4 0 Vendor specific
0x8e06 4 1 Vendor specific
0x8e07 4 2 Vendor specific
0x8e08 4 6 Vendor specific
0x8e09 4 0 Vendor specific
0x8e0a 4 26 Vendor specific
0x8e0b 4 1792 Vendor specific
0x8e0c 4 110 Vendor specific
0x8e0d 4 0 Vendor specific
0x8e0e 4 26 Vendor specific
0x8e0f 4 0 Vendor specific
0x8e10 4 104 Vendor specific
0x8e11 4 6 Vendor specific
|
|
From: Franc Z. <fz...@in...> - 2017-04-28 03:51:27
|
Here are several vendor specific SMART attributes for SSDs by Apple, Dell, HP and Lenovo: http://www.hddoracle.com/viewtopic.php?f=59&t=2034 -Franc Zabkar |
|
From: Christian F. <Chr...@t-...> - 2017-04-17 11:46:00
|
Dan Lukes wrote: > jonghwan Choi wrote: >> "The STANDBY command (see 7.45) and STANDBY IMMEDIATE command (see 7.46) move a device to Standby mode immediately from the Active mode or Idle mode. The STANDBY command also sets the Standby timer count." >> >> What I understood is : > ... >> But If the standby command is executed with sector count non-zero, it does >> not enter the standby mode immediately but it enters the standby mode when >> the timer expires. > I understand it different way. STANDBY (IMMEDIATE) command puts disk > into Standby mode regardless the timer setting operation (e.g. all the > times). Moreover it can modify Standby Time Counter configuration. Correct. Both commands causes drive to enter standby mode. The STANDBY command also modifies the timer configuration. These commands exist since the early days. Quote from X3T10/791D Revision 4c (ATA[-1], 1994): " 9.25 Standby This command causes the drive to enter the Standby Mode. ... If the Sector Count Register is non-zero then the automatic power down sequence shall be enabled and the timer will begin counting down when the drive returns to Idle mode. If the Sector Count Register is zero then the automatic power down sequence shall be disabled. 9.26 Standby immediate This command causes the drive to enter the Standby Mode. ... " The peculiar mapping of Standby Timeout to Sector Count value was later added in ATA-2 (1996) and is still the same in recent ACS-4 draft (April 2017). AFAICS there is still no command which could modify the standby timer configuration without affecting the power mode itself. Regards, Christian |
|
From: Dan L. <da...@ob...> - 2017-04-17 06:06:31
|
jonghwan Choi wrote: > "The STANDBY command (see 7.45) and STANDBY IMMEDIATE command (see 7.46) move a device to Standby mode immediately from the Active mode or Idle mode. The STANDBY command also sets the Standby timer count." > > What I understood is : ... > But If the standby command is executed with sector count non-zero, it does > not enter the standby mode immediately but it enters the standby mode when > the timer expires. I understand it different way. STANDBY (IMMEDIATE) command puts disk into Standby mode regardless the timer setting operation (e.g. all the times). Moreover it can modify Standby Time Counter configuration. If you wish not to put drive into Standby use IDLE (IMMEDIATE) command instead. > Is it right that I understood it? Such question is rather meaningless ;-) Most important question is - how the author of particular drive firmware has understood it. Dan |
|
From: jonghwan C. <jhb...@gm...> - 2017-04-14 09:33:23
|
Hi all Sorry to bother you. 4.16.2 Power management commands The CHECK POWER MODE command (see 7.3) allows a host to determine if a device is in, going to, or leaving Active mode, Standby mode, or Idle mode. The CHECK POWER MODE command shall not change the power mode or affect the operation of the Standby timer. The IDLE command (see 7.13) and IDLE IMMEDIATE command (see 7.14) move a device to Idle mode immediately from the Active mode or Standby mode. The IDLE command also sets the Standby timer count (i.e., enables or disables the Standby timer). The STANDBY command (see 7.45) and STANDBY IMMEDIATE command (see 7.46) move a device to Standby mode immediately from the Active mode or Idle mode. The STANDBY command also sets the Standby timer count. The SLEEP command (see 7.43) moves a device to Sleep mode. The device's interface becomes inactive (see the applicable transport standard) after the device reports command completion for the SLEEP command. A device only transitions from Sleep mode after processing a hardware reset or a software reset. 4.16.3 Standby timer The Standby timer provides a method for the device to enter Standby mode from either Active mode or Idle mode following a host programmed period of inactivity. If: a) the Standby timer is enabled; b) the device is in the Active mode or the Idle mode; and c) the Standby timer expires, then the device enters the Standby mode if no media access command is received. If a media access command is received and the Standby timer is enabled, the Standby timer is: a) reinitialized to the value specified by the most recent IDLE command (see 7.13) or STANDBY command (see 7.45); and b) started. If the Standby timer is disabled, the device may automatically enter Standby mode after a vendor specific time has expired for a vendor specific reason. I have a question about Standby timer. According to ACS spec, the device can enter into Standby mode. "The STANDBY command (see 7.45) and STANDBY IMMEDIATE command (see 7.46) move a device to Standby mode immediately from the Active mode or Idle mode. The STANDBY command also sets the Standby timer count." What I understood is : If the standby command is executed with sector count zero(disable standby timer), it enters the standby mode immediately) But If the standby command is executed with sector count non-zero, it does not enter the standby mode immediately but it enters the standby mode when the timer expires. (The standby command is executed as a standby timer when the sector count is not zero.) Is it right that I understood it? Thanks Best Regards.! |
|
From: jonghwan C. <jhb...@gm...> - 2017-04-14 01:17:35
|
Hi all. I would like to add the new features. ( https://www.smartmontools.org/ticket/832) There are already the ability to turn specific device features on and off. But it only supports some functions. To add more functionality, we have to add code for each function. To solve this problem, I added code to turn on / off specific functions by specifying features value and sector count value. I also know that using it wrong can be a problem. However, this problem is solved by forbidding some fatal commands. It is useful for fw developers like me. I send e-mail because I want to hear other people's opinions according to Christian Franke's advice. thanks. Best Regards.! |
|
From: Christian F. <Chr...@t-...> - 2017-04-13 05:49:00
|
jonghwan Choi wrote: > Hi all > > I could not find the answer on the mailing list. > I am sorry to bother you. > > To make a windows binary files, I followed the steps below. > > 1. git clone smartmontools source All possible git mirrors are independent projects and may be outdated. Checkout from smartmontools SVN or download latest source tarball from builds.smartmontools.org. https://www.smartmontools.org/wiki/Download#InstalllatestunreleasedcodefromSVNrepository > 2. open the *.sln file in os_win32 via visual studio > 3. run build > 4. config.h : No such file or directory file. > This requires a run of "make config-vc14" first in a POSIX environment. See [10] in INSTALL file (somewhat outdated, as it still assumes VC10). > How do I create binary files for windows in windows environment? Smartmontools is open source, therefore the recommended way to build uses open source tools :-) For 64-bit version, run this on Windows+Cygwin, Debian, Ubuntu, etc with MinGW-w64 packages installed: $ ./configure --build=$(./config.guess) \ --host=x86_64-w64-mingw32 \ $ make All releases and daily builds for Windows are cross-compiled under Linux. Thanks, Christian |
|
From: jonghwan C. <jhb...@gm...> - 2017-04-12 06:56:10
|
Hi all I could not find the answer on the mailing list. I am sorry to bother you. To make a windows binary files, I followed the steps below. 1. git clone smartmontools source 2. open the *.sln file in os_win32 via visual studio 3. run build 4. config.h : No such file or directory file. How do I create binary files for windows in windows environment? Thanks Best Regards! |
|
From: Robin H. J. <ro...@ge...> - 2017-04-07 20:55:12
|
On Fri, Apr 07, 2017 at 04:28:43PM -0400, David Niklas wrote: ... > > If you can repeat it, consider some of the following to get a better > > insight as to what's going on. > > - set up serial kernel console or network kernel console logging. > > - set up kdump or similar. > No, It's random so far. Ok, get yourself network console logging, since networking was still working, and you can just let the kernel send a copy of all klog entries over the network. See in the kernel sources, see Documentation/networking/netconsole.txt or examples in the Ubuntu & Arch wikis. > > That's not to say that the drive isn't the source of the problem, just > > that it's not likely based on the output you've shown. > Why not? > What else causes all writes to the drive to stop except a problem with > the drive or MB (my laptop has not cabling)? Most failure modes of a spinning drive would cause various error counters to be incremented. The few that I could think of that wouldn't involve specific component failures on the drive PCB. Drive PCB-originating failures should NOT cause your video to lock up, but may stop the logging to disk of any errors. I can start up a linux system, running off a sata drive, open a terminal, suddenly disconnect the drive, and still be able to run dmesg and/or see live kernel log entries (Provided that dmesg itself is at least already cached and running doesn't need anything to be read off disk). So what we're looking for as root cause is some manner of error that causes both video & drive to become unresponsive, but the kernel to still respond to ICMP ping (ergo network stack is operational). That root cause COULD have other effects (like a power spike that then damages the drive PCB), but it's the root cause we care about. Overheating causing a component fault (like causing a capacitor to go out of tolerance or fail) on one of the PCI/PCIe busses, and therein affecting the drive & graphics. The networking might be on a different bus, and continues to function. > > You say this is a laptop, and the drive by power hours has racked up > > ~1.5 years of usage, so it possibly hasn't been opened in at least that > > long. How much dust has built up inside it? Overheating of the graphics > > CAN cause the symptoms you've described. > The laptop is my primary way to get online, it's not be left off for more > than 2 days unless it's HW failed (the original drive died). > > So, I'm not misreading the S.M.A.R.T. data? No values that aught to be > interpreted in HEX, OCTAL or something? No, the drive data seems good, and representative of a health & well-used drive. No reallocated sectors, no other issues, not that many power cycles even for a laptop drive w/ aggressive power saving. -- Robin Hugh Johnson Gentoo Linux: Dev, Infra Lead, Foundation Trustee & Treasurer E-Mail : ro...@ge... GnuPG FP : 11ACBA4F 4778E3F6 E4EDF38E B27B944E 34884E85 GnuPG FP : 7D0B3CEB E9B85B1F 825BCECF EE05E6F6 A48F6136 |
|
From: David N. <do...@ma...> - 2017-04-07 20:28:56
|
On Thu, 6 Apr 2017 20:51:51 +0000 "Robin H. Johnson" <ro...@ge...> wrote: > On Wed, Apr 05, 2017 at 08:26:12PM -0400, David Niklas wrote: > > The symptoms leading up to the event was a sudden freeze of the OS. I > > was not too bright about Linux at the time, so I thought that perhaps > > X froze. Now I'm getting the identical thing, a sudden freeze. I can > > ping the kernel, I cannot restore the frame buffer, sync, or umount > > the file systems. My syslog metalog records no messages during this > > period, it is set to sync the dmesg messages. I cannot ssh, but I can > > uses sysreq to reboot. I'm using OpenRC. > Metalog would only be useful is writes to disk were succeeding. It's > certainly possible for the kernel to hang in such a state that there is > kernel panic, and writes to disk are not happening (this includes > sending the sysrq-sync command). > > That you can ping the kernel simply says that there's enough left > running for the kernel to handle ICMP without going to userspace. > > That you can't SSH says something in userspace failed (which could be a > myriad of reasons). > > Just because the system seems to freeze does not mean that the drive is > faulty. Also entirely possible there is a logged drive event in dmesg > that you can't see. > > If you can repeat it, consider some of the following to get a better > insight as to what's going on. > - set up serial kernel console or network kernel console logging. > - set up kdump or similar. No, It's random so far. > That's not to say that the drive isn't the source of the problem, just > that it's not likely based on the output you've shown. Why not? What else causes all writes to the drive to stop except a problem with the drive or MB (my laptop has not cabling)? > You say this is a laptop, and the drive by power hours has racked up > ~1.5 years of usage, so it possibly hasn't been opened in at least that > long. How much dust has built up inside it? Overheating of the graphics > CAN cause the symptoms you've described. The laptop is my primary way to get online, it's not be left off for more than 2 days unless it's HW failed (the original drive died). So, I'm not misreading the S.M.A.R.T. data? No values that aught to be interpreted in HEX, OCTAL or something? Thanks, David |
|
From: Robin H. J. <ro...@ge...> - 2017-04-06 20:52:03
|
On Wed, Apr 05, 2017 at 08:26:12PM -0400, David Niklas wrote: > The symptoms leading up to the event was a sudden freeze of the OS. I was > not too bright about Linux at the time, so I thought that perhaps X froze. > Now I'm getting the identical thing, a sudden freeze. I can ping the > kernel, I cannot restore the frame buffer, sync, or umount the > file systems. My syslog metalog records no messages during this period, > it is set to sync the dmesg messages. I cannot ssh, but I can uses sysreq > to reboot. I'm using OpenRC. Metalog would only be useful is writes to disk were succeeding. It's certainly possible for the kernel to hang in such a state that there is kernel panic, and writes to disk are not happening (this includes sending the sysrq-sync command). That you can ping the kernel simply says that there's enough left running for the kernel to handle ICMP without going to userspace. That you can't SSH says something in userspace failed (which could be a myriad of reasons). Just because the system seems to freeze does not mean that the drive is faulty. Also entirely possible there is a logged drive event in dmesg that you can't see. If you can repeat it, consider some of the following to get a better insight as to what's going on. - set up serial kernel console or network kernel console logging. - set up kdump or similar. That's not to say that the drive isn't the source of the problem, just that it's not likely based on the output you've shown. You say this is a laptop, and the drive by power hours has racked up ~1.5 years of usage, so it possibly hasn't been opened in at least that long. How much dust has built up inside it? Overheating of the graphics CAN cause the symptoms you've described. -- Robin Hugh Johnson Gentoo Linux: Dev, Infra Lead, Foundation Trustee & Treasurer E-Mail : ro...@ge... GnuPG FP : 11ACBA4F 4778E3F6 E4EDF38E B27B944E 34884E85 GnuPG FP : 7D0B3CEB E9B85B1F 825BCECF EE05E6F6 A48F6136 |
|
From: <ro...@sp...> - 2017-04-06 14:30:15
|
I'll second "Carlos E. R."'s verdict. I see nothing wrong either. However, that does not guarantee there isn't something wrong. Somewhere I read a study that said SMART only predicts about 60% of hard drive failures. The other 40% give no warning. Backups are always a good idea. They protect not only against hard drive failures, but also accidental or malicious data loss. Now have you tested those backups? I remember when I was free-lance going to a brand new client (first visit). They needed me to do a restore. OK, got their backup media (it was back in the zip disk days). Every disk was write-protected, and blank. Needless to say, that day didn't go well. > Hello, > First of all, I *have* been backing up my data. > I'm going to post LOTS of details here, fell free to skim. > > My problem is that once upon a time my drived failed < 6 months after I > bought my laptop. Sending it to a professional did not help, nor did > replacing the PCB, it was dead. > The symptoms leading up to the event was a sudden freeze of the OS. I was > not too bright about Linux at the time, so I thought that perhaps X froze. > Now I'm getting the identical thing, a sudden freeze. I can ping the > kernel, I cannot restore the frame buffer, sync, or umount the > file systems. My syslog metalog records no messages during this period, > it is set to sync the dmesg messages. I cannot ssh, but I can uses sysreq > to reboot. I'm using OpenRC. > > This has happened twice or three times. > I just ran a self test and it says PASSED, I'm not seeing anything that > stands out. > > smartmontools-6.4 > Gentoo Linux 4.9.x > > Below is my S.M.A.R.T. data. BTW: it is unwrapped. > What do you think? > Thanks, David > > > === START OF INFORMATION SECTION === > Model Family: Western Digital Blue Mobile > Device Model: WDC WD7500BPVX-22JC3T0 > Serial Number: WD-WXC1A14E1823 > LU WWN Device Id: 5 0014ee 209f3d675 > Firmware Version: 01.01A01 > User Capacity: 750,156,374,016 bytes [750 GB] > Sector Sizes: 512 bytes logical, 4096 bytes physical > Rotation Rate: 5400 rpm > Device is: In smartctl database [for details use: -P show] > ATA Version is: ACS-2 (minor revision not indicated) > SATA Version is: SATA 3.0, 6.0 Gb/s (current: 6.0 Gb/s) > Local Time is: Tue Apr 4 14:47:54 2017 UTC > SMART support is: Available - device has SMART capability. > SMART support is: Enabled > > === START OF READ SMART DATA SECTION === > SMART overall-health self-assessment test result: PASSED > > General SMART Values: > Offline data collection status: (0x00) Offline data collection activity > was never started. > Auto Offline Data Collection: Disabled. > 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: (13920) 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: ( 157) minutes. > Conveyance self-test routine > recommended polling time: ( 5) minutes. > SCT capabilities: (0x7035) SCT Status 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 FLAG VALUE WORST THRESH TYPE UPDATED > WHEN_FAILED RAW_VALUE > 1 Raw_Read_Error_Rate 0x002f 200 200 051 Pre-fail Always > - 0 > 3 Spin_Up_Time 0x0027 196 179 021 Pre-fail Always > - 1166 > 4 Start_Stop_Count 0x0032 058 058 000 Old_age Always > - 42367 > 5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail Always > - 0 > 7 Seek_Error_Rate 0x002e 200 200 000 Old_age Always > - 0 > 9 Power_On_Hours 0x0032 082 082 000 Old_age Always > - 13532 > 10 Spin_Retry_Count 0x0032 100 100 000 Old_age Always > - 0 > 11 Calibration_Retry_Count 0x0032 100 100 000 Old_age Always > - 0 > 12 Power_Cycle_Count 0x0032 099 099 000 Old_age Always > - 1695 > 191 G-Sense_Error_Rate 0x0032 001 001 000 Old_age Always > - 124 > 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always > - 158 > 193 Load_Cycle_Count 0x0032 183 183 000 Old_age Always > - 51774 > 194 Temperature_Celsius 0x0022 107 091 000 Old_age Always > - 40 > 196 Reallocated_Event_Count 0x0032 200 200 000 Old_age Always > - 0 > 197 Current_Pending_Sector 0x0032 200 200 000 Old_age Always > - 0 > 198 Offline_Uncorrectable 0x0030 100 253 000 Old_age Offline > - 0 > 199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always > - 0 > 200 Multi_Zone_Error_Rate 0x0008 200 200 000 Old_age Offline > - 0 > > SMART Error Log Version: 1 > No Errors Logged > > SMART Self-test log structure revision number 1 > Num Test_Description Status Remaining > LifeTime(hours) LBA_of_first_error > # 1 Extended offline Completed without error 00% 13529 > - > # 2 Extended offline Completed without error 00% 12288 > - > # 3 Extended offline Completed without error 00% 9247 > - > # 4 Extended offline Completed without error 00% 7609 > - > # 5 Extended offline Completed without error 00% 5469 > - > # 6 Short offline Completed without error 00% 0 > - > # 7 Short offline Completed without error 00% 0 > - > > SMART Selective self-test log data structure revision number 1 > SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS > 1 0 0 Not_testing > 2 0 0 Not_testing > 3 0 0 Not_testing > 4 0 0 Not_testing > 5 0 0 Not_testing > Selective self-test flags (0x0): > After scanning selected spans, do NOT read-scan remainder of disk. > If Selective self-test is pending on power-up, resume after 0 minute > delay. > > > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > Smartmontools-support mailing list > Sma...@li... > https://lists.sourceforge.net/lists/listinfo/smartmontools-support > |
|
From: Carlos E. R. <rob...@te...> - 2017-04-06 10:09:47
|
On 2017-04-06 02:26, David Niklas wrote: > Hello, > First of all, I *have* been backing up my data. > I'm going to post LOTS of details here, fell free to skim. > > My problem is that once upon a time my drived failed < 6 months after I > bought my laptop. Sending it to a professional did not help, nor did > replacing the PCB, it was dead. > The symptoms leading up to the event was a sudden freeze of the OS. I was > not too bright about Linux at the time, so I thought that perhaps X froze. > Now I'm getting the identical thing, a sudden freeze. I can ping the > kernel, I cannot restore the frame buffer, sync, or umount the > file systems. My syslog metalog records no messages during this period, > it is set to sync the dmesg messages. I cannot ssh, but I can uses sysreq > to reboot. I'm using OpenRC. > > This has happened twice or three times. > I just ran a self test and it says PASSED, I'm not seeing anything that > stands out. > > smartmontools-6.4 > Gentoo Linux 4.9.x > > Below is my S.M.A.R.T. data. BTW: it is unwrapped. > What do you think? No evidence of problem here, that I can see. If it were the disk, you typically would see messages of the kernel complaining in "dmesg". -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" (Minas Tirith)) |
|
From: David N. <do...@ma...> - 2017-04-06 00:26:26
|
Hello,
First of all, I *have* been backing up my data.
I'm going to post LOTS of details here, fell free to skim.
My problem is that once upon a time my drived failed < 6 months after I
bought my laptop. Sending it to a professional did not help, nor did
replacing the PCB, it was dead.
The symptoms leading up to the event was a sudden freeze of the OS. I was
not too bright about Linux at the time, so I thought that perhaps X froze.
Now I'm getting the identical thing, a sudden freeze. I can ping the
kernel, I cannot restore the frame buffer, sync, or umount the
file systems. My syslog metalog records no messages during this period,
it is set to sync the dmesg messages. I cannot ssh, but I can uses sysreq
to reboot. I'm using OpenRC.
This has happened twice or three times.
I just ran a self test and it says PASSED, I'm not seeing anything that
stands out.
smartmontools-6.4
Gentoo Linux 4.9.x
Below is my S.M.A.R.T. data. BTW: it is unwrapped.
What do you think?
Thanks, David
=== START OF INFORMATION SECTION ===
Model Family: Western Digital Blue Mobile
Device Model: WDC WD7500BPVX-22JC3T0
Serial Number: WD-WXC1A14E1823
LU WWN Device Id: 5 0014ee 209f3d675
Firmware Version: 01.01A01
User Capacity: 750,156,374,016 bytes [750 GB]
Sector Sizes: 512 bytes logical, 4096 bytes physical
Rotation Rate: 5400 rpm
Device is: In smartctl database [for details use: -P show]
ATA Version is: ACS-2 (minor revision not indicated)
SATA Version is: SATA 3.0, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is: Tue Apr 4 14:47:54 2017 UTC
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED
General SMART Values:
Offline data collection status: (0x00) Offline data collection activity
was never started.
Auto Offline Data Collection: Disabled.
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: (13920) 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: ( 157) minutes.
Conveyance self-test routine
recommended polling time: ( 5) minutes.
SCT capabilities: (0x7035) SCT Status 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 FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE
1 Raw_Read_Error_Rate 0x002f 200 200 051 Pre-fail Always - 0
3 Spin_Up_Time 0x0027 196 179 021 Pre-fail Always - 1166
4 Start_Stop_Count 0x0032 058 058 000 Old_age Always - 42367
5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail Always - 0
7 Seek_Error_Rate 0x002e 200 200 000 Old_age Always - 0
9 Power_On_Hours 0x0032 082 082 000 Old_age Always - 13532
10 Spin_Retry_Count 0x0032 100 100 000 Old_age Always - 0
11 Calibration_Retry_Count 0x0032 100 100 000 Old_age Always - 0
12 Power_Cycle_Count 0x0032 099 099 000 Old_age Always - 1695
191 G-Sense_Error_Rate 0x0032 001 001 000 Old_age Always - 124
192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 158
193 Load_Cycle_Count 0x0032 183 183 000 Old_age Always - 51774
194 Temperature_Celsius 0x0022 107 091 000 Old_age Always - 40
196 Reallocated_Event_Count 0x0032 200 200 000 Old_age Always - 0
197 Current_Pending_Sector 0x0032 200 200 000 Old_age Always - 0
198 Offline_Uncorrectable 0x0030 100 253 000 Old_age Offline - 0
199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0
200 Multi_Zone_Error_Rate 0x0008 200 200 000 Old_age Offline - 0
SMART Error Log Version: 1
No Errors Logged
SMART Self-test log structure revision number 1
Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error
# 1 Extended offline Completed without error 00% 13529 -
# 2 Extended offline Completed without error 00% 12288 -
# 3 Extended offline Completed without error 00% 9247 -
# 4 Extended offline Completed without error 00% 7609 -
# 5 Extended offline Completed without error 00% 5469 -
# 6 Short offline Completed without error 00% 0 -
# 7 Short offline Completed without error 00% 0 -
SMART Selective self-test log data structure revision number 1
SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS
1 0 0 Not_testing
2 0 0 Not_testing
3 0 0 Not_testing
4 0 0 Not_testing
5 0 0 Not_testing
Selective self-test flags (0x0):
After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.
|
|
From: Christian F. <Chr...@t-...> - 2017-03-27 19:56:24
|
Jorge Bozzarello wrote: > > Hello, I'm sorry to bother you, I'm using your tool and I get this > result in the line "sector size", I do not know how to interpret it. > If physical and logical are the same or there was no reading of > physical sector, thank you. > > C:\Program Files\smartmontools\bin>smartctl.exe -a /dev/sda > > smartctl 6.5 2016-05-07 r4318 [x86_64-w64-mingw32-2008r2] (sf-6.5-1) > > ... > > Sector Size: 512 bytes logical/physical > > ... The above sector size is reported if the corresponding field in IDENTIFY data (word 106) is unset (0x0000) or valid (0x4000). To check what the drive actually returns in IDENTIFY data, try: # smartctl --identify=wn /dev/sda ... 106 0x4000 Physical sector size / logical sector size ... Regards, Christian |
|
From: Jorge B. <jgb...@sc...> - 2017-03-23 12:24:54
|
Hello, I'm sorry to bother you, I'm using your tool and I get this result in the line "sector size", I do not know how to interpret it. If physical and logical are the same or there was no reading of physical sector, thank you. C:\Program Files\smartmontools\bin>smartctl.exe -a /dev/sda smartctl 6.5 2016-05-07 r4318 [x86_64-w64-mingw32-2008r2] (sf-6.5-1) Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Device Model: MB1000EAMZE Serial Number: 9WK2XK8J LU WWN Device Id: 5 000c50 02d798ec0 Firmware Version: HPG1 User Capacity: 1.000.204.886.016 bytes [1,00 TB] Sector Size: 512 bytes logical/physical Rotation Rate: 7200 rpm Form Factor: 3.5 inches Device is: Not in smartctl database [for details use: -P showall] ATA Version is: ATA8-ACS T13/1699-D revision 6 SATA Version is: SATA 2.6, 3.0 Gb/s Local Time is: Wed Mar 22 12:53:58 2017 AST SMART support is: Available - device has SMART capability. SMART support is: Enabled Jorge G Bozzarello Área Infraestructura y Administración de Base de Datos Subsecretaría de Tecnología Informática Suprema Corte de Justicia Provincia de Buenos Aires jgb...@sc... |
|
From: Gandalf C. <gan...@gm...> - 2017-03-19 11:56:43
|
I'm getting the following in syslog: Mar 19 01:52:50 x smartd[5280]: Device: /dev/sda [SAT], SMART Usage Attribute: 7 Seek_Error_Rate changed from 200 to 100 Mar 19 01:52:50 x smartd[5280]: Device: /dev/sdb [SAT], SMART Usage Attribute: 7 Seek_Error_Rate changed from 200 to 100 Mar 19 01:52:50 x smartd[5280]: Device: /dev/sdc [SAT], SMART Usage Attribute: 7 Seek_Error_Rate changed from 200 to 100 Mar 19 08:22:50 x smartd[5280]: Device: /dev/sda [SAT], SMART Usage Attribute: 7 Seek_Error_Rate changed from 100 to 200 Mar 19 08:22:50 x smartd[5280]: Device: /dev/sdc [SAT], SMART Usage Attribute: 7 Seek_Error_Rate changed from 100 to 200 Mar 19 08:52:51 x smartd[5280]: Device: /dev/sdb [SAT], SMART Usage Attribute: 7 Seek_Error_Rate changed from 100 to 200 Mar 19 09:22:50 x smartd[5280]: Device: /dev/sda [SAT], SMART Usage Attribute: 7 Seek_Error_Rate changed from 200 to 100 Mar 19 09:22:50 x smartd[5280]: Device: /dev/sdb [SAT], SMART Usage Attribute: 7 Seek_Error_Rate changed from 200 to 100 Mar 19 09:22:50 x smartd[5280]: Device: /dev/sdc [SAT], SMART Usage Attribute: 7 Seek_Error_Rate changed from 200 to 100 as you can see, all drives are getting the same change at the same time for the same value. Pretty strange. Is this a bug or something is happening ? Disks are pretty new, only about 5600 hours. |
|
From: Brian B. <br...@pu...> - 2017-03-15 21:25:01
|
Hello all,
I was looking for an answer in the same vein as the question posted by
Derek Lambert, but that said I can answer his.
What is happening is here:
...
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
...
Your drive is responding to a mode sense command page called
Informational Exceptions. The response from your drive is going to
dictate what happens next. So since you are getting SMART available
and enabled, you are inviting the next request from the smart tools
which is an ATA_PASSTHROUGH. You will typically see the opcode 0x85
which is the 16 byte SCSI version of the command that you are seeing
0xA1. If your drive can answer SMART is Available but Disabled you
will likely find that the kernel warnings will stop.
Here is the ESX variant of your Solaris issue:
https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1036874
The answer to the Informational Exceptions is key. So, for example,
PURE LUNs from our array:
[root@init101-11 ~]# sg_modes -p 0x1c /dev/sg1
PURE FlashArray 8888 peripheral_type: disk [0x0]
Mode parameter header from MODE SENSE(10):
Mode data length=28, medium type=0x00, WP=0, DpoFua=0, longlba=0
Block descriptor length=8
> Direct access device block descriptors:
Density code=0x0
00 3e 7f ff ff 00 00 02 00
>> Informational exceptions control, page_control: current
00 1c 0a 08 00 00 00 00 00 00 00 00 00
It is the presence of the 08 that is key. If you run that command and
you see 00 there it probably explains what you see. Here is the
smartctl on the PURE LUN:
...
Device supports SMART and is Disabled
Temperature Warning Disabled or Not Supported
....
I can give you more details if you need them.
Thanks,
Brian
|
|
From: Gabriele P. <gp...@di...> - 2017-03-14 11:59:16
|
Dear smartmontools users, I would like to update our collection of example reports: https://www.smartmontools.org/wiki/Help#Howtoreadsmartctlreports Current reason is the development / improvement of Munin plugins http://gallery.munin-monitoring.org/sensors-index.html for graphical monitoring of SMART data based on smartctl reports. Therefore I am interested in a wide range of different reports especially for report type scsi / sas and also for new type nvme and ssd disks. Your contributions are highly appreciated :-) Please use "-q noserial" and note that all content of our wiki is published under GPL if not stated otherwise. Contributions under FDL (https://www.gnu.org/licenses/fdl.html) are also welcome! I will mark the pages accordingly. Full of expectations and cheers to all! Gabriele |
|
From: Christian F. <Chr...@t-...> - 2017-03-13 20:25:18
|
l...@av... wrote: > Hello. > > My questions could be silly and answers could be obvious, but I'll be glad if you point me to the right docs. See https://www.smartmontools.org/wiki/Links#ATAATAPIReferences https://www.smartmontools.org/wiki/Links#TheoriginalSMARTspecification > What exactly does the Offline data collection? As far as I understood, it's contrary to short and long self-tests, and results are written to "Offline" attributes such as "Offline_uncorrectable". This was possibly the original idea. What actually happens is hidden in firmware and typically not documented by device vendors. > Long self-test, above all, tries to read and verify every sector of the hard drive. This test can run for 214 minutes on my 2TB Seagate Barracuda 7200.14, but the Offline data collection runs only for 575 seconds. > Does it mean that Offline data collection is not trying to read/verify every sector, and there could be dozens of unreadable sectors out there, and I'll know about them only after long selftest? Yes. > The other question is about Auto Offline data collection: I cannot enable it on my drives: > ... > # smartctl -s on -S on -o on /dev/sda > ... > # smartctl -c /dev/sda > === START OF READ SMART DATA SECTION === > General SMART Values: > Offline data collection status: (0x00) Offline data collection activity > was never started. > Auto Offline Data Collection: Disabled. > > I've tried to issue the test with '-t offline', and I saw errors in '-l error' log, but the Auto collection cannot be enabled without any reasons. Then the "SMART ENABLE AUTOMATIC OFF-LINE" ATA command is unsupported by the drive firmware (see -o option on smartctl man page). Regards, Christian |
58 messages has been excluded from this view by a project administrator.
