From owner-freebsd-current@freebsd.org Sat Dec 23 11:26:50 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8C97CEA3011 for ; Sat, 23 Dec 2017 11:26:50 +0000 (UTC) (envelope-from ohartmann@walstatt.org) Received: from mout.gmx.net (mout.gmx.net [212.227.17.20]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "mout.gmx.net", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id DAD168011E; Sat, 23 Dec 2017 11:26:49 +0000 (UTC) (envelope-from ohartmann@walstatt.org) Received: from thor.intern.walstatt.dynvpn.de ([85.180.33.201]) by mail.gmx.com (mrgmx103 [212.227.17.168]) with ESMTPSA (Nemesis) id 0MI5rO-1eOqal1PB8-003uut; Sat, 23 Dec 2017 12:26:17 +0100 Date: Sat, 23 Dec 2017 12:25:41 +0100 From: "O. Hartmann" To: Willem Jan Withagen Cc: "Rodney W. Grimes" , Cy Schubert , "O. Hartmann" , FreeBSD CURRENT , Freddie Cash , Alan Somers , "Rodney W. Grimes" , Daniel Kalchev Subject: Re: SMART: disk problems on RAIDZ1 pool: (ada6:ahcich6:0:0:0): CAMstatus: ATA Status Error Message-ID: <20171223122608.4ea4f097@thor.intern.walstatt.dynvpn.de> In-Reply-To: <4d58b06a-0dbe-af05-1bd2-e87929e3b7a5@digiware.nl> References: <201712131647.vBDGlrf2092528@pdx.rh.CN85.dnsmgr.net> <4d58b06a-0dbe-af05-1bd2-e87929e3b7a5@digiware.nl> Organization: WALSTATT User-Agent: OutScare 3.1415926 X-Operating-System: ImNotAnOperatingSystem 3.141592527 MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; boundary="Sig_/mdXl02WhP_PB/BOqOogssmV"; protocol="application/pgp-signature" X-Provags-ID: V03:K0:VKoGA8znLOWl4yEsr+84rqGxB/79VKWDkCi6cOGd99VvzaT+bWf WzObEJ9xFfZJOvz5P7mGKxpm0cARZ6wPqnsgSWJG+szQBUtR57n4O1JFudbJG2n3Wq/ln5H pQ/Z84YN0M7on9BjcAkBNSRB1kYrCrGMw8MDSxSuXfZ7D84fOvpMY+PrF4kK7Zvz0PNlDbC qRS36HawlaI/mqrf81sYg== X-UI-Out-Filterresults: notjunk:1;V01:K0:yvMrNro/Q5U=:WJs0Ync6ezi5HgxvwtBlOB d/h5d/ieiTunZK0JcW4yQn5V6LnYVjoIwNeylvgRMoIAscmqxzKmhjMI+m/gD0ik/K6al0DMq V0iPWix94yGhTIQBWCuU4w645BcElvARnWT+nFs8TpN8nWBVnpy3qg2opp+Vmq4kjVHO/qhs2 R5Uk1QBdLBkmuWg9FpBgREraRU/CUjC4PDZJm4HSyIrV6C8pVfhUfckCZlPeMQ6ZT6VpWYCIS hp7N1ozV8r1N3V8aYK83UHWIeEDWSoxhBuYdTGkarfar9MPJ2JjFpqcKd5yjuBZCzczcsGJKS q2jusiTYRp0J/lNUQ3TCgr8nqk+mI4QmlE7DQ5R5Utz4/0mwbLNyIk2fUPu62exuT6A699oay RGAfzqqhEWYM4lw8xS/MtGQIDTmz6T12uq/DbeWlikAne3Qz8GZfB8hfVhMg/qJYE6pWM0eRq 9t5GHt83pAqFLK5Alj7slzH/KBTh1BRWsgRClCWD8ty2fov7w8Oupg0l5r6pvkafOxTdcWMm3 fKg7c7nTIMS1k3rIwnxLS4TzJrBqD34aRV2PVD8MSZg4WaATVA+eH5ZMxNJ/ipt60CqVXlTdi /zQVwLqNOFwdVR0GmO4Wz5VJ9Sj/QbiWcpIU0JUCJcMQMzlY3XXEiiopGUCoNVGFxNOMUK7FS Ax4cFIO++yEW6U+ckM6ZUnVlmvTDk/PVyLfhV0QfMiDkMQ8pfbpGlVEipuorjk1IXgj34BeeH ZQG6RwdpsHnyCKyWOtPHz8W3QoAxLFRXsLo7i//MrY2pGI9/hTwQLCZUQfLnlR1Tp22bqsyUb jQuIqpFAdOi9znvyu/SlYmlwJORMQ== X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 23 Dec 2017 11:26:50 -0000 --Sig_/mdXl02WhP_PB/BOqOogssmV Content-Type: multipart/mixed; boundary="MP_/4F00pud+2Z/GXgo0SACKCEb" --MP_/4F00pud+2Z/GXgo0SACKCEb Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Am Thu, 14 Dec 2017 12:05:20 +0100 Willem Jan Withagen schrieb: > On 13/12/2017 17:47, Rodney W. Grimes wrote: > >> On Tue, 12 Dec 2017 14:58:28 -0800 > >> Cy Schubert wrote: > >> I think people responding to my thread made it clear that the WD Green > >> isn't the first-choice-solution for a 20/6 (not 24/7) duty drive and > >> the fact, that they have serviced now more than 25000 hours, it would > >> be wise to replace them with alternatives. =20 > >=20 > > I think someone had an apm command that turns off the head park, > > that would do wonders for drive life. On the other hand, I think > > if it was my data and I saw that the drive had 2M head load cycles > > I would be looking to get out of that driv with any data I could > > not easily replace. If it was well backed up or easily replaced > > my worries would be less. =20 >=20 > WD made their first series of Green disks green by aggressively turning=20 > them into sleep state. Like when few secs there was nog activity they=20 > would park the head, spin it down, and sleep the disk... > Access would need to undo the whole series of command. >=20 > This could be reset by writing in one of the disks registers. I remember= =20 > doing that for my 1,5G WDs (WD15EADS from 2009). That saved a lot of=20 > startups. I still have 'm around, but only use them for things that are=20 > not valuable at all. Some have died over time, but about half of them=20 > still seem to work without much trouble. >=20 > WD used to have a .exe program to actually do this. But that did not > work on later disks. And turning things of on those disks was=20 > impossible/a lot more complex. >=20 > This type of disk worked quite a long time in my ZFS setup. Like a few=20 > years, but I turned parking of as soon as there was a lot of turmoil=20 > about this in the community. > Now I using WD reds for small ZFS systems, and WD red Pro for large=20 > private storage servers. Professional server get HGST He disks, a bit=20 > more expensive, but very little fallout. >=20 > --WjW Hello fellows. First of all, I managed it over the past week+ to replace all(!) drives wit= h new ones. I decided to use this time HGST 4TB Deskstar NAS (HGST HDN726040ALE614) inste= ad of WD RED 4TB (WDC WD40EFRX-68N32N0). The one WD RED is about to be replaced in the n= ext days. Apart from the very long resilvering time (the first drive, the Western Dig= ital WD RED 4TB with 64MB cache and 5400 rpm) took 11 h, all HGST drives, although cons= idered faster (7200 rpm, 128 MB cache) took 15 - 16 h), everything ran smoothly - except,= as mentioned, the exorbitant times of recovery. A very interesting point in this story is: as you could see, the WD Caviar = Green 3TB drives suffered from a high "193 Load_Cycle_Count" - almost 85 per hour. Wh= en replacing the drives, I figured out, that one of the four drives was already a Wester= n Digital RED 3TB NAS drive, but investigating its "193 Load_Cycle_Count" revealed, that= this drive also had a unusual high reload count - see "smartctl -x" output attached. I= t seems, as you already stated, that the APM feature responsible for this isn't availab= le. The drive has been purchased Q4/2013. The HGST drives are very(!) noisy, th ehead movement induces a notable ring= ing, while the WD drive(s) are/were really silent. The power consumption of the HGST drive= s is higher. But apart from that, I'm disappointed about the fact that WD has also imple= mented this "timebomb" Load_Cycle_Count issue. Thanks a lot for your help and considerations! Kind regards, Oliver --=20 O. Hartmann Ich widerspreche der Nutzung oder =C3=9Cbermittlung meiner Daten f=C3=BCr Werbezwecke oder f=C3=BCr die Markt- oder Meinungsforschung (=C2=A7 28 Abs.= 4 BDSG). --MP_/4F00pud+2Z/GXgo0SACKCEb Content-Type: text/plain Content-Transfer-Encoding: quoted-printable Content-Disposition: attachment; filename=ada3.txt smartctl 6.6 2017-11-05 r4594 [FreeBSD 12.0-CURRENT amd64] (local build) Copyright (C) 2002-17, Bruce Allen, Christian Franke, www.smartmontools.org =3D=3D=3D START OF INFORMATION SECTION =3D=3D=3D Model Family: Western Digital Red Device Model: WDC WD30EFRX-68EUZN0 Serial Number: Seriennummer LU WWN Device Id: 5 0014ee 0ae56aef0 Firmware Version: 80.00A80 User Capacity: 3,000,592,982,016 bytes [3.00 TB] 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: 3.0 Gb/s) Local Time is: Sat Dec 23 11:59:30 2017 CET SMART support is: Available - device has SMART capability. SMART support is: Enabled AAM feature is: Unavailable APM feature is: Unavailable Rd look-ahead is: Enabled Write cache is: Enabled DSN feature is: Unavailable ATA Security is: Disabled, NOT FROZEN [SEC1] Wt Cache Reorder: Enabled =3D=3D=3D START OF READ SMART DATA SECTION =3D=3D=3D 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 comp= leted without error or no self-test has ever=20 been run. Total time to complete Offline=20 data collection: (38760) 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=20 recommended polling time: ( 2) minutes. Extended self-test routine recommended polling time: ( 389) minutes. Conveyance self-test routine recommended polling time: ( 5) minutes. SCT capabilities: (0x703d) 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 200 200 051 - 0 3 Spin_Up_Time POS--K 171 165 021 - 6416 4 Start_Stop_Count -O--CK 099 099 000 - 1860 5 Reallocated_Sector_Ct PO--CK 200 200 140 - 0 7 Seek_Error_Rate -OSR-K 200 200 000 - 0 9 Power_On_Hours -O--CK 072 072 000 - 20809 10 Spin_Retry_Count -O--CK 100 100 000 - 0 11 Calibration_Retry_Count -O--CK 100 100 000 - 0 12 Power_Cycle_Count -O--CK 099 099 000 - 1858 192 Power-Off_Retract_Count -O--CK 200 200 000 - 112 193 Load_Cycle_Count -O--CK 001 001 000 - 1974142 194 Temperature_Celsius -O---K 128 109 000 - 22 196 Reallocated_Event_Count -O--CK 200 200 000 - 0 197 Current_Pending_Sector -O--CK 200 200 000 - 0 198 Offline_Uncorrectable ----CK 200 200 000 - 0 199 UDMA_CRC_Error_Count -O--CK 200 200 000 - 0 200 Multi_Zone_Error_Rate ---R-- 200 200 000 - 0 ||||||_ 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 5 Comprehensive SMART error log 0x03 GPL R/O 6 Ext. Comprehensive SMART error log 0x06 SL R/O 1 SMART self-test log 0x07 GPL R/O 1 Extended self-test log 0x09 SL R/W 1 Selective self-test log 0x10 GPL R/O 1 NCQ Command Error log 0x11 GPL R/O 1 SATA Phy Event Counters log 0x21 GPL R/O 1 Write stream error log 0x22 GPL R/O 1 Read stream error log 0x80-0x9f GPL,SL R/W 16 Host vendor specific log 0xa0-0xa7 GPL,SL VS 16 Device vendor specific log 0xa8-0xb7 GPL,SL VS 1 Device vendor specific log 0xbd GPL,SL VS 1 Device vendor specific log 0xc0 GPL,SL VS 1 Device vendor specific log 0xc1 GPL VS 93 Device 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 (6 sectors) Device Error Count: 7 CR =3D Command Register FEATR =3D Features Register COUNT =3D Count (was: Sector Count) Register LBA_48 =3D Upper bytes of LBA High/Mid/Low Registers ] ATA-8 LH =3D LBA High (was: Cylinder High) Register ] LBA LM =3D LBA Mid (was: Cylinder Low) Register ] Register LL =3D LBA Low (was: Sector Number) Register ] DV =3D Device (was: Device/Head) Register DC =3D Device Control Register ER =3D Error register ST =3D Status register Powered_Up_Time is measured from power on, and printed as DDd+hh:mm:SS.sss where DD=3Ddays, hh=3Dhours, mm=3Dminutes, SS=3Dsec, and sss=3Dmillisec. It "wraps" after 49.710 days. Error 7 [6] occurred at disk power-on lifetime: 16151 hours (672 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 -- -- -- =3D=3D -- =3D=3D =3D=3D =3D=3D -- -- -- -- -- 10 -- 51 00 00 00 00 98 01 cd d0 40 00 Error: IDNF at LBA =3D 0x9801cdd0= =3D 2550255056 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 -- =3D=3D -- =3D=3D -- =3D=3D =3D=3D =3D=3D -- -- -- -- -- -------------= -- -------------------- 61 00 08 00 50 00 00 98 01 cd d0 40 08 00:12:14.943 WRITE FPDMA QUEU= ED ea 00 00 00 00 00 00 00 00 00 00 40 08 00:12:05.025 FLUSH CACHE EXT 61 00 08 00 40 00 01 5d 50 9f a0 40 08 00:12:05.024 WRITE FPDMA QUEU= ED 61 00 08 00 38 00 01 5d 50 9d a0 40 08 00:12:05.024 WRITE FPDMA QUEU= ED 61 00 08 00 30 00 00 00 00 13 a0 40 08 00:12:05.024 WRITE FPDMA QUEU= ED Error 6 [5] occurred at disk power-on lifetime: 10875 hours (453 days + 3 h= ours) 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 -- -- -- =3D=3D -- =3D=3D =3D=3D =3D=3D -- -- -- -- -- 10 -- 51 00 00 00 01 30 01 ce 78 40 00 Error: IDNF at LBA =3D 0x13001ce7= 8 =3D 5100392056 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 -- =3D=3D -- =3D=3D -- =3D=3D =3D=3D =3D=3D -- -- -- -- -- -------------= -- -------------------- 61 00 08 00 b0 00 01 30 01 ce 78 40 08 04:06:34.288 WRITE FPDMA QUEU= ED ea 00 00 00 00 00 00 00 00 00 00 40 08 04:06:24.234 FLUSH CACHE EXT 61 00 08 00 a0 00 01 5d 50 9f 30 40 08 04:06:24.234 WRITE FPDMA QUEU= ED 61 00 08 00 98 00 01 5d 50 9d 30 40 08 04:06:24.234 WRITE FPDMA QUEU= ED 61 00 08 00 90 00 00 00 00 13 30 40 08 04:06:24.233 WRITE FPDMA QUEU= ED Error 5 [4] occurred at disk power-on lifetime: 8417 hours (350 days + 17 h= ours) 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 -- -- -- =3D=3D -- =3D=3D =3D=3D =3D=3D -- -- -- -- -- 10 -- 51 00 00 00 00 c4 06 ba 08 40 00 Error: IDNF at LBA =3D 0xc406ba08= =3D 3288775176 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 -- =3D=3D -- =3D=3D -- =3D=3D =3D=3D =3D=3D -- -- -- -- -- -------------= -- -------------------- 61 00 08 00 a8 00 00 c4 06 ba 08 40 08 00:45:57.190 WRITE FPDMA QUEU= ED ea 00 00 00 00 00 00 00 00 00 00 40 08 00:45:47.264 FLUSH CACHE EXT 61 00 08 00 98 00 01 5d 50 9f b0 40 08 00:45:47.263 WRITE FPDMA QUEU= ED 61 00 08 00 90 00 01 5d 50 9d b0 40 08 00:45:47.263 WRITE FPDMA QUEU= ED 61 00 08 00 88 00 00 00 00 13 b0 40 08 00:45:47.263 WRITE FPDMA QUEU= ED Error 4 [3] occurred at disk power-on lifetime: 3423 hours (142 days + 15 h= ours) 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 -- -- -- =3D=3D -- =3D=3D =3D=3D =3D=3D -- -- -- -- -- 10 -- 51 00 00 00 00 b2 59 f6 a8 40 00 Error: IDNF at LBA =3D 0xb259f6a8= =3D 2992240296 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 -- =3D=3D -- =3D=3D -- =3D=3D =3D=3D =3D=3D -- -- -- -- -- -------------= -- -------------------- 61 00 08 00 f8 00 00 b2 59 f6 a8 40 08 12:09:22.415 WRITE FPDMA QUEU= ED ea 00 00 00 00 00 00 00 00 00 00 40 08 12:09:13.160 FLUSH CACHE EXT 61 00 08 00 f8 00 01 5d 50 9f 90 40 08 12:09:13.159 WRITE FPDMA QUEU= ED 61 00 08 00 f0 00 01 5d 50 9d 90 40 08 12:09:13.159 WRITE FPDMA QUEU= ED 61 00 08 00 e8 00 00 00 00 13 90 40 08 12:09:13.159 WRITE FPDMA QUEU= ED Error 3 [2] occurred at disk power-on lifetime: 2928 hours (122 days + 0 ho= urs) 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 -- -- -- =3D=3D -- =3D=3D =3D=3D =3D=3D -- -- -- -- -- 10 -- 51 00 00 00 00 c0 05 10 20 40 00 Error: IDNF at LBA =3D 0xc0051020= =3D 3221557280 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 -- =3D=3D -- =3D=3D -- =3D=3D =3D=3D =3D=3D -- -- -- -- -- -------------= -- -------------------- 61 00 08 00 00 00 00 c0 05 10 20 40 08 09:36:05.067 WRITE FPDMA QUEU= ED 61 00 08 00 00 00 01 5d 50 9f f0 40 08 09:35:50.674 WRITE FPDMA QUEU= ED 61 00 08 00 f8 00 01 5d 50 9d f0 40 08 09:35:50.674 WRITE FPDMA QUEU= ED 61 00 08 00 f0 00 00 00 00 13 f0 40 08 09:35:50.674 WRITE FPDMA QUEU= ED 61 00 08 00 e8 00 00 00 00 11 f0 40 08 09:35:50.674 WRITE FPDMA QUEU= ED Error 2 [1] occurred at disk power-on lifetime: 1989 hours (82 days + 21 ho= urs) 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 -- -- -- =3D=3D -- =3D=3D =3D=3D =3D=3D -- -- -- -- -- 10 -- 51 00 00 00 00 ae 07 ce 30 40 00 Error: IDNF at LBA =3D 0xae07ce30= =3D 2919747120 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 -- =3D=3D -- =3D=3D -- =3D=3D =3D=3D =3D=3D -- -- -- -- -- -------------= -- -------------------- 61 00 08 00 78 00 00 ae 07 ce 30 40 08 04:16:19.349 WRITE FPDMA QUEU= ED 61 00 08 00 78 00 01 5d 50 9f 98 40 08 04:16:05.011 WRITE FPDMA QUEU= ED 61 00 08 00 70 00 01 5d 50 9d 98 40 08 04:16:05.011 WRITE FPDMA QUEU= ED 61 00 08 00 68 00 00 00 00 13 98 40 08 04:16:05.011 WRITE FPDMA QUEU= ED 61 00 08 00 60 00 00 00 00 11 98 40 08 04:16:05.011 WRITE FPDMA QUEU= ED Error 1 [0] occurred at disk power-on lifetime: 1764 hours (73 days + 12 ho= urs) 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 -- -- -- =3D=3D -- =3D=3D =3D=3D =3D=3D -- -- -- -- -- 10 -- 51 00 00 00 00 aa 1a 86 e8 40 00 Error: IDNF at LBA =3D 0xaa1a86e8= =3D 2853865192 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 -- =3D=3D -- =3D=3D -- =3D=3D =3D=3D =3D=3D -- -- -- -- -- -------------= -- -------------------- 61 00 08 00 d0 00 00 aa 1a 86 e8 40 08 12:13:30.211 WRITE FPDMA QUEU= ED 61 00 08 00 d0 00 01 5d 50 9f 30 40 08 12:13:20.248 WRITE FPDMA QUEU= ED 61 00 08 00 c8 00 01 5d 50 9d 30 40 08 12:13:20.248 WRITE FPDMA QUEU= ED 61 00 08 00 c0 00 00 00 00 13 30 40 08 12:13:20.248 WRITE FPDMA QUEU= ED 61 00 08 00 b8 00 00 00 00 11 30 40 08 12:13:20.248 WRITE FPDMA QUEU= ED SMART Extended Self-test Log Version: 1 (1 sectors) Num Test_Description Status Remaining LifeTime(hours)= LBA_of_first_error # 1 Short offline Completed without error 00% 18023 = - # 2 Short offline Completed without error 00% 2620 = - 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. SCT Status Version: 3 SCT Version (vendor specific): 258 (0x0102) SCT Support Level: 1 Device State: Active (0) Current Temperature: 22 Celsius Power Cycle Min/Max Temperature: 22/22 Celsius Lifetime Min/Max Temperature: 11/41 Celsius Under/Over Temperature Limit Count: 0/0 Vendor specific: 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 SCT Temperature History Version: 2 Temperature Sampling Period: 1 minute Temperature Logging Interval: 1 minute Min/Max recommended Temperature: 0/60 Celsius Min/Max Temperature Limit: -41/85 Celsius Temperature History Size (Index): 478 (301) Index Estimated Time Temperature Celsius 302 2017-12-23 04:01 22 *** ... ..( 92 skipped). .. *** 395 2017-12-23 05:34 22 *** 396 2017-12-23 05:35 21 ** ... ..( 93 skipped). .. ** 12 2017-12-23 07:09 21 ** 13 2017-12-23 07:10 22 *** ... ..( 92 skipped). .. *** 106 2017-12-23 08:43 22 *** 107 2017-12-23 08:44 ? - 108 2017-12-23 08:45 21 ** ... ..( 29 skipped). .. ** 138 2017-12-23 09:15 21 ** 139 2017-12-23 09:16 22 *** ... ..( 21 skipped). .. *** 161 2017-12-23 09:38 22 *** 162 2017-12-23 09:39 ? - 163 2017-12-23 09:40 15 - 164 2017-12-23 09:41 15 - 165 2017-12-23 09:42 16 - 166 2017-12-23 09:43 16 - 167 2017-12-23 09:44 17 - ... ..( 5 skipped). .. - 173 2017-12-23 09:50 17 - 174 2017-12-23 09:51 18 - ... ..( 9 skipped). .. - 184 2017-12-23 10:01 18 - 185 2017-12-23 10:02 19 - ... ..( 7 skipped). .. - 193 2017-12-23 10:10 19 - 194 2017-12-23 10:11 20 * ... ..( 13 skipped). .. * 208 2017-12-23 10:25 20 * 209 2017-12-23 10:26 21 ** ... ..( 50 skipped). .. ** 260 2017-12-23 11:17 21 ** 261 2017-12-23 11:18 ? - 262 2017-12-23 11:19 13 - 263 2017-12-23 11:20 13 - 264 2017-12-23 11:21 14 - ... ..( 2 skipped). .. - 267 2017-12-23 11:24 14 - 268 2017-12-23 11:25 15 - 269 2017-12-23 11:26 15 - 270 2017-12-23 11:27 16 - 271 2017-12-23 11:28 16 - 272 2017-12-23 11:29 17 - ... ..( 4 skipped). .. - 277 2017-12-23 11:34 17 - 278 2017-12-23 11:35 18 - 279 2017-12-23 11:36 ? - 280 2017-12-23 11:37 22 *** ... ..( 20 skipped). .. *** 301 2017-12-23 11:58 22 *** SCT Error Recovery Control: Read: 70 (7.0 seconds) Write: 70 (7.0 seconds) Device Statistics (GP/SMART Log 0x04) not supported Pending Defects log (GP Log 0x0c) not supported SATA Phy Event Counters (GP Log 0x11) ID Size Value Description 0x0001 2 0 Command failed due to ICRC error 0x0002 2 0 R_ERR response for data FIS 0x0003 2 0 R_ERR response for device-to-host data FIS 0x0004 2 0 R_ERR response for host-to-device data FIS 0x0005 2 0 R_ERR response for non-data FIS 0x0006 2 0 R_ERR response for device-to-host non-data FIS 0x0007 2 0 R_ERR response for host-to-device non-data FIS 0x0008 2 0 Device-to-host non-data FIS retries 0x0009 2 1 Transition from drive PhyRdy to drive PhyNRdy 0x000a 2 1 Device-to-host register FISes sent due to a COMRESET 0x000b 2 0 CRC errors within host-to-device FIS 0x000f 2 0 R_ERR response for host-to-device data FIS, CRC 0x0012 2 0 R_ERR response for host-to-device non-data FIS, CRC 0x8000 4 911 Vendor specific --MP_/4F00pud+2Z/GXgo0SACKCEb-- --Sig_/mdXl02WhP_PB/BOqOogssmV Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- iLUEARMKAB0WIQQZVZMzAtwC2T/86TrS528fyFhYlAUCWj49UAAKCRDS528fyFhY lFXHAf4iBVK6BUfo1fH//mGlWP5OpL6cSFmFPT00k+3uPWqR/PU2BRrCTalDXFRx rVO0b7UNBt6tBLBylvTBtcfjCx75Af4l/rTR42dmRiyGUXWf55Y+jiX52PfrhRBL 44zSdBOAk44ejHU8MUV84SI6TYDcI22Di/yf4hhReLZRkV4iP/ia =WeZR -----END PGP SIGNATURE----- --Sig_/mdXl02WhP_PB/BOqOogssmV--