Титла: Прочитане на SMART
Публикувано от: ivanpop в Apr 21, 2016, 21:16
Здравейте Използвам smartctl за да взема SMART информацията, но не знам какво точно да гледам. Получавам следният отговор: smartctl -a /dev/sdb smartctl 5.41 2011-06-09 r3365 [x86_64-linux-2.6.32-39-pve] (local build) Copyright (C) 2002-11 by Bruce Allen, http://smartmontools.sourceforge.net
=== START OF INFORMATION SECTION === Device Model: Hitachi HDS721010CLA330 Serial Number: JPS930N11MGLLV LU WWN Device Id: 5 000cca 39cd6f15c Firmware Version: JP4OA3MA User Capacity: 1,000,203,804,160 bytes [1.00 TB] Sector Size: 512 bytes logical/physical Device is: Not in smartctl database [for details use: -P showall] ATA Version is: 8 ATA Standard is: ATA-8-ACS revision 4 Local Time is: Thu Apr 21 21:12:22 2016 EEST 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: (0x84) Offline data collection activity was suspended by an interrupting command from host. 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: ( 9811) 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: ( 1) minutes. Extended self-test routine recommended polling time: ( 164) minutes. SCT capabilities: (0x003d) SCT Status supported. SCT Error Recovery Control supported. SCT Feature Control supported. SCT Data Table supported.
SMART Attributes Data Structure revision number: 16 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x000b 100 100 016 Pre-fail Always - 1 2 Throughput_Performance 0x0005 137 137 054 Pre-fail Offline - 90 3 Spin_Up_Time 0x0007 121 121 024 Pre-fail Always - 310 (Average 314) 4 Start_Stop_Count 0x0012 100 100 000 Old_age Always - 54 5 Reallocated_Sector_Ct 0x0033 100 100 005 Pre-fail Always - 0 7 Seek_Error_Rate 0x000b 100 100 067 Pre-fail Always - 0 8 Seek_Time_Performance 0x0005 138 138 020 Pre-fail Offline - 31 9 Power_On_Hours 0x0012 097 097 000 Old_age Always - 26187 10 Spin_Retry_Count 0x0013 100 100 060 Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 54 192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 271 193 Load_Cycle_Count 0x0012 100 100 000 Old_age Always - 271 194 Temperature_Celsius 0x0002 125 125 000 Old_age Always - 48 (Min/Max 6/53) 196 Reallocated_Event_Count 0x0032 100 100 000 Old_age Always - 0 197 Current_Pending_Sector 0x0022 100 100 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0008 100 100 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x000a 200 200 000 Old_age Always - 0
SMART Error Log Version: 1 ATA Error Count: 12 (device log contains only the most recent five errors) CR = Command Register [HEX] FR = Features Register [HEX] SC = Sector Count Register [HEX] SN = Sector Number Register [HEX] CL = Cylinder Low Register [HEX] CH = Cylinder High Register [HEX] DH = Device/Head Register [HEX] DC = Device Command Register [HEX] ER = Error register [HEX] ST = Status register [HEX] 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 12 occurred at disk power-on lifetime: 12785 hours (532 days + 17 hours) When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 40 51 04 c4 d2 09 0d Error: UNC at LBA = 0x0d09d2c4 = 218747588
Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 60 08 00 c0 d2 09 40 00 20d+08:29:03.187 READ FPDMA QUEUED ef 10 02 00 00 00 a0 00 20d+08:29:03.186 SET FEATURES [Reserved for Serial ATA] 27 00 00 00 00 00 e0 00 20d+08:29:03.185 READ NATIVE MAX ADDRESS EXT ec 00 00 00 00 00 a0 00 20d+08:29:03.179 IDENTIFY DEVICE ef 03 46 00 00 00 a0 00 20d+08:29:03.178 SET FEATURES [Set transfer mode]
Error 11 occurred at disk power-on lifetime: 12785 hours (532 days + 17 hours) When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 40 51 04 c4 d2 09 0d Error: UNC at LBA = 0x0d09d2c4 = 218747588
Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 60 08 00 c0 d2 09 40 00 20d+08:28:43.953 READ FPDMA QUEUED ef 10 02 00 00 00 a0 00 20d+08:28:43.952 SET FEATURES [Reserved for Serial ATA] 27 00 00 00 00 00 e0 00 20d+08:28:43.951 READ NATIVE MAX ADDRESS EXT ec 00 00 00 00 00 a0 00 20d+08:28:43.945 IDENTIFY DEVICE ef 03 46 00 00 00 a0 00 20d+08:28:43.945 SET FEATURES [Set transfer mode]
Error 10 occurred at disk power-on lifetime: 12785 hours (532 days + 17 hours) When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 40 51 04 c4 d2 09 0d Error: UNC at LBA = 0x0d09d2c4 = 218747588
Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 60 08 00 c0 d2 09 40 00 20d+08:28:24.766 READ FPDMA QUEUED ef 10 02 00 00 00 a0 00 20d+08:28:24.765 SET FEATURES [Reserved for Serial ATA] 27 00 00 00 00 00 e0 00 20d+08:28:24.764 READ NATIVE MAX ADDRESS EXT ec 00 00 00 00 00 a0 00 20d+08:28:24.759 IDENTIFY DEVICE ef 03 46 00 00 00 a0 00 20d+08:28:24.758 SET FEATURES [Set transfer mode]
Error 9 occurred at disk power-on lifetime: 12785 hours (532 days + 17 hours) When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 40 51 04 c4 d2 09 0d Error: WP at LBA = 0x0d09d2c4 = 218747588
Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 61 08 f0 5f bd 00 40 00 20d+08:28:05.487 WRITE FPDMA QUEUED 60 08 e8 c0 d2 09 40 00 20d+08:28:05.487 READ FPDMA QUEUED 61 08 e0 ff b3 2a 40 00 20d+08:28:05.487 WRITE FPDMA QUEUED 61 10 d8 0f b4 2a 40 00 20d+08:28:05.487 WRITE FPDMA QUEUED 61 18 d0 27 b4 2a 40 00 20d+08:28:05.486 WRITE FPDMA QUEUED
Error 8 occurred at disk power-on lifetime: 12785 hours (532 days + 17 hours) When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 40 51 04 c4 d2 09 0d Error: WP at LBA = 0x0d09d2c4 = 218747588
Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 61 08 00 5f bd 00 40 00 20d+08:27:46.299 WRITE FPDMA QUEUED 60 08 08 c0 d2 09 40 00 20d+08:27:46.295 READ FPDMA QUEUED 61 68 00 f7 bc 00 40 00 20d+08:27:46.295 WRITE FPDMA QUEUED ef 10 02 00 00 00 a0 00 20d+08:27:46.294 SET FEATURES [Reserved for Serial ATA] 27 00 00 00 00 00 e0 00 20d+08:27:46.293 READ NATIVE MAX ADDRESS EXT
SMART Self-test log structure revision number 1 No self-tests have been logged. [To run self-tests, use: smartctl -t]
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. Как мога да разбера дали диска е читав или не? Един познат ми каза да го сменям.
Титла: Re: Прочитане на SMART
Публикувано от: runtime в Apr 22, 2016, 00:16
На диска според мен нищо му няма (все още), но от написаното мога да си мисля, че има проблем със захранването... Грешките UNC at LBA са uncorrectable read/write error но са твърде малко за проблем с диска... Но, това си е мое мнение и ти си решавай какво да го правиш все пак :)
Титла: Re: Прочитане на SMART
Публикувано от: jet в Apr 22, 2016, 01:32
На диска според мен нищо му няма (все още), но от написаното мога да си мисля, че има проблем със захранването... Грешките UNC at LBA са uncorrectable read/write error но са твърде малко за проблем с диска... Но, това си е мое мнение и ти си решавай какво да го правиш все пак :)
+1 Аз също мисля че диска е добре, захранването се дъни.
Титла: Re: Прочитане на SMART
Публикувано от: Naka в Apr 22, 2016, 11:20
Много ми е тъпо да се самоцитиръм, обаче за каузата http://www.linux-bg.org/forum/index.php?topic=43458.msg263931#msg263931
Диска ти не изписва нищо нередно в основните SMART параметри. И бад секторите Offline_Uncorrectable 0 са ти нула и заместените/сменените Reallocated_Sector_Ct 0 са ти нула.
Дотук добре..... Обаче долу в логовете пише че има проблем при четенето на сектор номер 218747588
LBA = 0x0d09d2c4 = 218747588
Това със сигурност е грешка в сектор. Виждал съм дискове които като изпишат нещо проблем в сектор в лога, не го отбелязват веднага в основната горната таблица. Но със сигурност след време когато firmware реши ще го отбележи и в основната таблица.
Съветвам те да пуснеш едно празно четене на диска от край до край dd if=/dev/sda of=/dev/null bs=32768 и ще видиш че като стигне до сектор 218747588 ще почне да трака или ще избие с i/o error. това няма да оправи диска, но е само за твое потвърждение на грешката.
След това Намираш сервизната програма на Хитачи и избираш запълване с нули от край до край. Много е бавно поне 2-3 часа. Това ще предизвика заместване и поправяне на повредения сектор. Това също ще затърка и цялата информаци на диска!!!
Но дисковете се оправат след тази процедура, ако не е много повреден. ---
Колегата тука казва, че програмата на хитачи се нарича Drive fitness test 4.16 for DOS.
---- PS проблемният сектор се намира около 218747588 * 512 = 112 GB но може да има и още наоколо или други лоши сектори които още не ги е настъпил.
|