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/5154B1E99870
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:48 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: (19635) 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: ( 328) minutes.
Conveyance self-test routine
recommended polling time: ( 34) 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 - 2
3 Spin_Up_Time POS--- 063 063 011 - 11970
4 Start_Stop_Count -O--CK 100 100 000 - 109
5 Reallocated_Sector_Ct PO--CK 100 100 010 - 0
7 Seek_Error_Rate POSR-- 099 099 051 - 23
8 Seek_Time_Performance P-S--K 100 100 015 - 12588
9 Power_On_Hours -O--CK 083 083 000 - 87038
10 Spin_Retry_Count PO--CK 100 100 051 - 0
11 Calibration_Retry_Count -O--C- 100 100 000 - 46
12 Power_Cycle_Count -O--CK 100 100 000 - 109
13 Read_Soft_Error_Rate -OSR-- 100 100 000 - 2
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 - 3
188 Command_Timeout -O--CK 100 100 000 - 0
190 Airflow_Temperature_Cel -O---K 069 066 000 - 31 (Min/Max 16/31)
194 Temperature_Celsius -O---K 066 065 000 - 34 (Min/Max 7/44)
195 Hardware_ECC_Recovered -O-RC- 100 100 000 - 1211415679
196 Reallocated_Event_Count -O--CK 100 100 000 - 0
197 Current_Pending_Sector -O--C- 100 100 000 - 1
198 Offline_Uncorrectable ----CK 100 100 000 - 0
199 UDMA_CRC_Error_Count -OSRCK 099 099 000 - 542
200 Multi_Zone_Error_Rate -O-R-- 100 100 000 - 0
201 Soft_Read_Error_Rate -O-R-- 099 099 000 - 1
||||||_ 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: 544 (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 544 [7] occurred at disk power-on lifetime: 19734 hours (822 days + 6 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 -- 52 00 00 00 00 64 0b 4e 25 40 00 at LBA = 0x640b4e25 = 1678462501
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 07 af 00 00 00 0b 62 ea 40 00 45d+21:31:34.706 READ FPDMA QUEUED
60 00 00 01 56 00 00 00 0b 61 3f 40 00 45d+21:31:34.676 READ FPDMA QUEUED
60 00 00 07 59 00 00 00 0b 59 62 40 00 45d+21:31:34.676 READ FPDMA QUEUED
60 00 00 07 59 00 00 00 0b 4c ca 40 00 45d+21:31:34.676 READ FPDMA QUEUED
2f 00 00 00 01 00 00 00 00 00 10 00 08 45d+21:31:34.676 READ LOG EXT
Error 543 [6] occurred at disk power-on lifetime: 19734 hours (822 days + 6 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 -- 52 00 00 00 00 64 0b 4e 25 40 00 at LBA = 0x640b4e25 = 1678462501
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 07 59 00 00 00 0b 59 62 40 00 45d+21:31:31.266 READ FPDMA QUEUED
60 00 00 00 ab 00 00 00 0b 58 55 40 00 45d+21:31:31.126 READ FPDMA QUEUED
60 00 00 02 ac 00 00 00 0b 54 f6 40 00 45d+21:31:31.106 READ FPDMA QUEUED
60 00 00 07 59 00 00 00 0b 4c ca 40 00 45d+21:31:31.096 READ FPDMA QUEUED
60 00 00 00 ab 00 00 00 0b 4b 9a 40 00 45d+21:31:31.086 READ FPDMA QUEUED
Error 542 [5] occurred at disk power-on lifetime: 47597 hours (1983 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 00 00 02 0e 40 00 at LBA = 0x0000020e = 526
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 10 00 00 00 00 02 00 40 00 00:00:49.870 READ FPDMA QUEUED
60 00 00 00 10 00 00 00 00 00 00 40 00 00:00:49.870 READ FPDMA QUEUED
60 00 00 00 10 00 00 00 00 00 10 40 00 00:00:49.870 READ FPDMA QUEUED
60 00 00 00 10 00 00 00 00 00 80 40 00 00:00:49.870 READ FPDMA QUEUED
60 00 00 00 01 00 00 ff a8 7b 2f 40 00 00:00:49.860 READ FPDMA QUEUED
Error 541 [4] occurred at disk power-on lifetime: 47597 hours (1983 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 03 73 f6 40 00 at LBA = 0x750373f6 = 1963160566
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 02 00 00 00 03 7b ab 40 00 6d+15:14:57.444 READ FPDMA QUEUED
60 00 00 00 0e 00 00 00 03 73 ea 40 00 6d+15:14:57.434 READ FPDMA QUEUED
60 00 00 00 04 00 00 00 25 f5 de 40 00 6d+15:14:57.434 READ FPDMA QUEUED
60 00 00 00 03 00 00 00 21 5f ac 40 00 6d+15:14:57.414 READ FPDMA QUEUED
60 00 00 00 10 00 00 00 21 5c 62 40 00 6d+15:14:57.414 READ FPDMA QUEUED
Error 540 [3] occurred at disk power-on lifetime: 47597 hours (1983 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 08 a4 bf 54 40 00 at LBA = 0x08a4bf54 = 145014612
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 a4 bf 01 40 00 6d+15:13:46.634 READ FPDMA QUEUED
ea 00 00 00 00 00 00 00 00 00 00 40 08 6d+15:13:46.474 FLUSH CACHE EXT
61 00 00 00 02 00 00 ff a8 3a aa 40 00 6d+15:13:46.474 WRITE FPDMA QUEUED
61 00 00 00 02 00 00 ff a8 38 aa 40 00 6d+15:13:46.474 WRITE FPDMA QUEUED
61 00 00 00 02 00 00 00 00 04 aa 40 00 6d+15:13:46.474 WRITE FPDMA QUEUED
Error 539 [2] occurred at disk power-on lifetime: 45168 hours (1882 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 25 00 00 6b 00 bc 1d 40 00 at LBA = 0x6b00bc1d = 1795210269
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 00 bb ec 40 00 37d+18:00:22.258 READ FPDMA QUEUED
60 00 00 00 55 00 00 00 00 bc 42 40 00 37d+18:00:22.248 READ FPDMA QUEUED
60 00 00 00 55 00 00 00 00 bb 97 40 00 37d+18:00:22.248 READ FPDMA QUEUED
60 00 00 00 56 00 00 00 00 bb 41 40 00 37d+18:00:22.248 READ FPDMA QUEUED
60 00 00 00 55 00 00 00 00 ba ec 40 00 37d+18:00:22.248 READ FPDMA QUEUED
Error 538 [1] occurred at disk power-on lifetime: 41075 hours (1711 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 45 00 00 45 16 f7 35 40 00 at LBA = 0x4516f735 = 1159132981
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 f7 24 40 00 19d+13:37:47.170 READ FPDMA QUEUED
60 00 00 00 55 00 00 00 16 f6 cf 40 00 19d+13:37:47.100 READ FPDMA QUEUED
60 00 00 00 55 00 00 00 16 f6 24 40 00 19d+13:37:47.100 READ FPDMA QUEUED
60 00 00 00 55 00 00 00 16 f5 79 40 00 19d+13:37:47.100 READ FPDMA QUEUED
60 00 00 00 55 00 00 00 16 f4 ce 40 00 19d+13:37:47.090 READ FPDMA QUEUED
Error 537 [0] occurred at disk power-on lifetime: 40606 hours (1691 days + 22 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 26 2e 07 d7 40 00 at LBA = 0x262e07d7 = 640550871
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 2e 07 b6 40 00 10d+20:02:11.170 READ FPDMA QUEUED
60 00 00 00 56 00 00 00 2e 07 60 40 00 10d+20:02:11.170 READ FPDMA QUEUED
60 00 00 00 55 00 00 00 2e 07 0b 40 00 10d+20:02:11.170 READ FPDMA QUEUED
60 00 00 00 55 00 00 00 2e 06 60 40 00 10d+20:02:11.160 READ FPDMA QUEUED
60 00 00 00 55 00 00 00 2e 05 b5 40 00 10d+20:02:11.090 READ 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% 47598 -
# 2 Short offline Completed without error 00% 4 -
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: 33 Celsius
Power Cycle Min/Max Temperature: --/44 Celsius
Lifetime Min/Max Temperature: --/45 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 (127)
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 18 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