80486DX2-66/SMART-open-study
1
0
Fork 0
mirror of https://github.com/bsdhw/SMART.git synced 2025-05-31 16:21:41 +05:30
Code Issues Activity
Files
master
SMART-open-study/HDD/Samsung/HD154/HD154UI/1C1B50B66364
Andrey Ponomarenko 06d1e49c98 Update of reports (new: 3633, modified: 0)
2023-02-14 01:25:13 +03:00

329 lines
16 KiB
Plaintext
Raw Permalink Blame History

smartctl 7.3 2022-02-28 r5338 [FreeBSD 13.1-RELEASE amd64] (local build)
Copyright (C) 2002-22, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF INFORMATION SECTION ===
Model Family: SAMSUNG SpinPoint F2 EG
Device Model: SAMSUNG HD154UI
Serial Number: --
LU WWN Device Id: 5 0024e9 ...
Firmware Version: 1AG01118
User Capacity: 1,500,301,910,016 bytes [1.50 TB]
Sector Size: 512 bytes logical/physical
Device is: In smartctl database 7.3/5319
ATA Version is: ATA/ATAPI-7, ATA8-ACS T13/1699-D revision 3b
Local Time is: Tue Jun 21 11:33:50 2022 CEST
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
DSN feature is: Unavailable
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: (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: (18645) 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: ( 312) minutes.
Conveyance self-test routine
recommended polling time: ( 33) 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-- 100 100 051 - 11
3 Spin_Up_Time POS--- 063 063 011 - 11860
4 Start_Stop_Count -O--CK 100 100 000 - 110
5 Reallocated_Sector_Ct PO--CK 064 064 010 - 1582
7 Seek_Error_Rate POSR-- 100 100 051 - 0
8 Seek_Time_Performance P-S--K 100 100 015 - 11352
9 Power_On_Hours -O--CK 083 083 000 - 87013
10 Spin_Retry_Count PO--CK 100 100 051 - 0
11 Calibration_Retry_Count -O--C- 100 100 000 - 0
12 Power_Cycle_Count -O--CK 100 100 000 - 110
13 Read_Soft_Error_Rate -OSR-- 100 100 000 - 11
183 Runtime_Bad_Block -O--CK 100 100 000 - 0
184 End-to-End_Error PO--CK 100 100 000 - 0
187 Reported_Uncorrect -O--CK 100 100 000 - 36
188 Command_Timeout -O--CK 100 100 000 - 0
190 Airflow_Temperature_Cel -O---K 068 065 000 - 32 (Min/Max 17/32)
194 Temperature_Celsius -O---K 066 064 000 - 34 (Min/Max 8/44)
195 Hardware_ECC_Recovered -O-RC- 100 100 000 - 1260382509
196 Reallocated_Event_Count -O--CK 062 062 000 - 1582
197 Current_Pending_Sector -O--C- 100 100 000 - 0
198 Offline_Uncorrectable ----CK 100 100 000 - 0
199 UDMA_CRC_Error_Count -OSRCK 099 099 000 - 658
200 Multi_Zone_Error_Rate -O-R-- 099 099 000 - 512
201 Soft_Read_Error_Rate -O-R-- 100 100 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 2 Comprehensive SMART error log
0x03 GPL R/O 2 Ext. Comprehensive SMART error log
0x04 GPL R/O 2 Device Statistics log
0x06 SL R/O 1 SMART self-test log
0x07 GPL R/O 2 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
0x20 GPL R/O 2 Streaming performance log [OBS-8]
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
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: 663 (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 663 [6] occurred at disk power-on lifetime: 57077 hours (2378 days + 5 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
-- -- -- == -- == == == -- -- -- -- --
00 -- 80 00 01 00 00 00 00 00 01 a0 00 1 sectors at LBA = 0x00000001 = 1
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
-- == -- == -- == == == -- -- -- -- -- --------------- --------------------
35 00 00 00 ab 00 00 8e 15 6f 86 40 08 10d+01:48:58.564 WRITE DMA EXT
61 00 00 00 1c 00 00 ff 02 a4 9c 40 00 10d+01:48:58.554 WRITE FPDMA QUEUED
61 00 00 00 0f 00 00 00 39 0d 2d 40 00 10d+01:48:58.554 WRITE FPDMA QUEUED
61 00 00 00 01 00 00 00 05 78 21 40 00 10d+01:48:58.554 WRITE FPDMA QUEUED
61 00 00 00 02 00 00 00 05 65 01 40 00 10d+01:48:58.554 WRITE FPDMA QUEUED
Error 662 [5] occurred at disk power-on lifetime: 57077 hours (2378 days + 5 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
-- -- -- == -- == == == -- -- -- -- --
00 -- 80 00 01 00 00 00 00 00 01 a0 00 1 sectors at LBA = 0x00000001 = 1
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
-- == -- == -- == == == -- -- -- -- -- --------------- --------------------
35 00 00 00 ab 00 00 30 4c 40 78 40 08 10d+01:47:15.884 WRITE DMA EXT
61 00 00 00 1e 00 00 00 40 c7 ae 40 00 10d+01:47:15.874 WRITE FPDMA QUEUED
61 00 00 00 02 00 00 00 40 72 ab 40 00 10d+01:47:15.874 WRITE FPDMA QUEUED
61 00 00 00 1c 00 00 00 03 20 5a 40 00 10d+01:47:15.874 WRITE FPDMA QUEUED
61 00 00 00 02 00 00 00 3d 14 75 40 00 10d+01:47:15.874 WRITE FPDMA QUEUED
Error 661 [4] occurred at disk power-on lifetime: 47573 hours (1982 days + 5 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
-- -- -- == -- == == == -- -- -- -- --
00 -- 48 00 32 00 00 6f 01 e8 8b 40 00 at LBA = 0x6f01e88b = 1862396043
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
-- == -- == -- == == == -- -- -- -- -- --------------- --------------------
61 00 00 00 ab 00 00 00 01 e8 12 40 00 00:14:29.670 WRITE FPDMA QUEUED
61 00 00 01 00 00 00 00 01 e7 12 40 00 00:14:29.660 WRITE FPDMA QUEUED
61 00 00 00 56 00 00 00 01 c4 3c 40 00 00:14:29.650 WRITE FPDMA QUEUED
ea 00 00 00 00 00 00 00 00 00 00 40 08 00:14:24.950 FLUSH CACHE EXT
61 00 00 00 02 00 00 ff a8 3a a2 40 00 00:14:24.950 WRITE FPDMA QUEUED
Error 660 [3] occurred at disk power-on lifetime: 47573 hours (1982 days + 5 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
-- -- -- == -- == == == -- -- -- -- --
00 -- 4a 00 00 00 00 75 04 c1 6d 40 00 at LBA = 0x7504c16d = 1963245933
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 21 00 00 00 05 bc 0a 40 00 6d+15:14:52.004 READ FPDMA QUEUED
60 00 00 00 0b 00 00 00 04 c1 64 40 00 6d+15:14:52.004 READ FPDMA QUEUED
60 00 00 00 08 00 00 00 04 bc 56 40 00 6d+15:14:51.984 READ FPDMA QUEUED
60 00 00 00 02 00 00 00 03 fc f4 40 00 6d+15:14:51.984 READ FPDMA QUEUED
60 00 00 00 02 00 00 00 03 7b aa 40 00 6d+15:14:51.984 READ FPDMA QUEUED
Error 659 [2] occurred at disk power-on lifetime: 45144 hours (1881 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
-- -- -- == -- == == == -- -- -- -- --
00 -- 4a 00 34 00 00 56 05 6c 23 40 00 at LBA = 0x56056c23 = 1443195939
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 55 00 00 00 05 6c 02 40 00 37d+18:12:36.188 READ FPDMA QUEUED
60 00 00 00 55 00 00 00 05 6a ac 40 00 37d+18:12:36.168 READ FPDMA QUEUED
60 00 00 00 55 00 00 00 05 6a 01 40 00 37d+18:12:36.168 READ FPDMA QUEUED
60 00 00 00 56 00 00 00 05 69 00 40 00 37d+18:12:36.158 READ FPDMA QUEUED
60 00 00 00 55 00 00 00 05 67 55 40 00 37d+18:12:36.148 READ FPDMA QUEUED
Error 658 [1] occurred at disk power-on lifetime: 41051 hours (1710 days + 11 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
-- -- -- == -- == == == -- -- -- -- --
00 -- 4a 00 35 00 00 45 16 f6 ef 40 00 at LBA = 0x4516f6ef = 1159132911
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 56 00 00 00 16 f6 ce 40 00 19d+13:37:44.670 READ FPDMA QUEUED
60 00 00 00 56 00 00 00 16 f6 23 40 00 19d+13:37:44.670 READ FPDMA QUEUED
60 00 00 00 55 00 00 00 16 f5 ce 40 00 19d+13:37:44.660 READ FPDMA QUEUED
60 00 00 00 56 00 00 00 16 f5 78 40 00 19d+13:37:44.660 READ FPDMA QUEUED
60 00 00 00 55 00 00 00 16 f5 23 40 00 19d+13:37:44.660 READ FPDMA QUEUED
Error 657 [0] occurred at disk power-on lifetime: 33362 hours (1390 days + 2 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
-- -- -- == -- == == == -- -- -- -- --
00 -- 4a 00 04 00 00 51 06 8e 5a 40 00 at LBA = 0x51068e5a = 1359384154
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 55 00 00 00 06 8e 09 40 00 1d+21:38:39.590 READ FPDMA QUEUED
ea 00 00 00 00 00 00 00 00 00 00 40 08 1d+21:38:38.390 FLUSH CACHE EXT
61 00 00 00 02 00 00 ff a8 3a a0 40 00 1d+21:38:38.390 WRITE FPDMA QUEUED
61 00 00 00 02 00 00 ff a8 38 a0 40 00 1d+21:38:38.390 WRITE FPDMA QUEUED
61 00 00 00 02 00 00 00 00 04 a0 40 00 1d+21:38:38.390 WRITE FPDMA QUEUED
Error 656 [7] occurred at disk power-on lifetime: 33361 hours (1390 days + 1 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
-- -- -- == -- == == == -- -- -- -- --
00 -- 4a 00 24 00 00 53 1a 35 33 40 00 at LBA = 0x531a3533 = 1394226483
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 55 00 00 00 1a 35 02 40 00 1d+20:58:07.160 READ FPDMA QUEUED
ea 00 00 00 00 00 00 00 00 00 00 40 08 1d+20:58:05.460 FLUSH CACHE EXT
61 00 00 00 02 00 00 ff a8 3a e0 40 00 1d+20:58:05.460 WRITE FPDMA QUEUED
61 00 00 00 02 00 00 ff a8 38 e0 40 00 1d+20:58:05.460 WRITE FPDMA QUEUED
61 00 00 00 02 00 00 00 00 04 e0 40 00 1d+20:58:05.460 WRITE FPDMA QUEUED
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% 10942 -
# 2 Short offline Completed without error 00% 5 -
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: 2
SCT Version (vendor specific): 256 (0x0100)
Device State: Active (0)
Current Temperature: 34 Celsius
Power Cycle Min/Max Temperature: --/44 Celsius
Lifetime Min/Max Temperature: --/46 Celsius
SCT Temperature History Version: 2
Temperature Sampling Period: 1 minute
Temperature Logging Interval: 1 minute
Min/Max recommended Temperature: -4/72 Celsius
Min/Max Temperature Limit: -9/77 Celsius
Temperature History Size (Index): 128 (126)
SCT Error Recovery Control:
Read: Disabled
Write: Disabled
ATA_READ_LOG_EXT (addr=0x04:0x00, page=0, n=1) failed: Input/output error
Read Device Statistics page 0x00 failed
Pending Defects log (GP Log 0x0c) not supported
SATA Phy Event Counters (GP Log 0x11)
ID Size Value Description
0x000a 2 13 Device-to-host register FISes sent due to a COMRESET
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 19 Transition from drive PhyRdy to drive PhyNRdy
0x000b 2 0 CRC errors within host-to-device FIS
0x000d 2 0 Non-CRC errors within host-to-device FIS
0x000f 2 0 R_ERR response for host-to-device data FIS, CRC
0x0010 2 0 R_ERR response for host-to-device data FIS, non-CRC
0x0012 2 0 R_ERR response for host-to-device non-data FIS, CRC
0x0013 2 0 R_ERR response for host-to-device non-data FIS, non-CRC
View Git Blame Copy Permalink