Am Donnerstag, 5. Oktober 2006 23:55 schrieb David Haller:
Meintest du 'smartctl -H'? Das ist nicht sehr Aussagekraeftig. Schau dir mal die Ausgabe von 'smartctl -A' an.
Ja, ich meinte -H.
Eventuell auch die von 'smartctl -a' die die Ausgabe von -A nochmal enthaelt. In der Ausgabe sind v.a. die folgenden Werte interessant: Raw_Read_Error_Rate, Reallocated_Sector_Ct, Reallocated_Event_Count, Current_Pending_Sector und Offline_Uncorrectable(?).
Raw_Read_Error_Rate gibts hier nicht, die anderen stehen auf 0. Hier der Rest: ---------8<-------------------------------------------------------------- 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 3 Spin_Up_Time 0x0027 225 221 063 Pre-fail Always - 7306 4 Start_Stop_Count 0x0032 252 252 000 Old_age Always - 3512 5 Reallocated_Sector_Ct 0x0033 253 253 063 Pre-fail Always - 0 6 Read_Channel_Margin 0x0001 253 253 100 Pre-fail Offline - 0 7 Seek_Error_Rate 0x000a 253 252 000 Old_age Always - 0 8 Seek_Time_Performance 0x0027 244 244 187 Pre-fail Always - 33381 9 Power_On_Minutes 0x0032 240 240 000 Old_age Always - 474h+13m 10 Spin_Retry_Count 0x002b 253 252 157 Pre-fail Always - 0 11 Calibration_Retry_Count 0x002b 253 252 223 Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 249 249 000 Old_age Always - 1822 192 Power-Off_Retract_Count 0x0032 253 253 000 Old_age Always - 0 193 Load_Cycle_Count 0x0032 253 253 000 Old_age Always - 0 194 Temperature_Celsius 0x0032 253 253 000 Old_age Always - 44 195 Hardware_ECC_Recovered 0x000a 253 252 000 Old_age Always - 34749 196 Reallocated_Event_Count 0x0008 253 253 000 Old_age Offline - 0 197 Current_Pending_Sector 0x0008 253 253 000 Old_age Offline - 0 198 Offline_Uncorrectable 0x0008 253 253 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x0008 199 199 000 Old_age Offline - 0 200 Multi_Zone_Error_Rate 0x000a 253 252 000 Old_age Always - 0 201 Soft_Read_Error_Rate 0x000a 253 252 000 Old_age Always - 28 202 TA_Increase_Count 0x000a 253 252 000 Old_age Always - 0 203 Run_Out_Cancel 0x000b 253 252 180 Pre-fail Always - 0 204 Shock_Count_Write_Opern 0x000a 253 252 000 Old_age Always - 0 205 Shock_Rate_Write_Opern 0x000a 253 252 000 Old_age Always - 0 207 Spin_High_Current 0x002a 253 252 000 Old_age Always - 0 208 Spin_Buzz 0x002a 253 252 000 Old_age Always - 0 209 Offline_Seek_Performnce 0x0024 150 150 000 Old_age Offline - 0 99 Unknown_Attribute 0x0004 253 253 000 Old_age Offline - 0 100 Unknown_Attribute 0x0004 253 253 000 Old_age Offline - 0 101 Unknown_Attribute 0x0004 253 253 000 Old_age Offline - 0 ---------8<--------------------------------------------------------------
Evtl. auch noch Seek_Error_Rate, Temperature_Celsius, Hardware_ECC_Recovered, UDMA_CRC_Error_Count, Multi_Zone_Error_Rate und Soft_Read_Error_Rate
Hardware_ECC_Recovered steht bei 34749, was ja mal eine heftige Zahl ist. Muss ich mir da Sorgen machen? Und dann sagt smartctl -a auch noch das hier: ---------8<-------------------------------------------------------------- SMART Error Log Version: 1 Warning: ATA error count 488 inconsistent with error log pointer 5 ATA Error Count: 488 (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 488 occurred at disk power-on lifetime: 1633 hours (68 days + 1 hours) When the command that caused the error occurred, the device was in an unknown state. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 40 51 01 b4 04 1b e1 Error: UNC 1 sectors at LBA = 0x011b04b4 = 18547892 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- c8 00 01 b4 04 1b e1 00 03:58:15.136 READ DMA e5 00 00 b4 04 1b a0 00 03:58:15.120 CHECK POWER MODE c8 00 01 b4 04 1b e1 00 03:58:10.144 READ DMA e5 00 00 52 20 00 a0 00 03:58:10.144 CHECK POWER MODE c8 00 01 52 20 00 e0 00 03:58:10.144 READ DMA Error 487 occurred at disk power-on lifetime: 1633 hours (68 days + 1 hours) When the command that caused the error occurred, the device was in an unknown state. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 40 51 01 b4 04 1b e1 Error: UNC 1 sectors at LBA = 0x011b04b4 = 18547892 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- c8 00 01 b4 04 1b e1 00 03:58:10.144 READ DMA e5 00 00 52 20 00 a0 00 03:58:10.144 CHECK POWER MODE c8 00 01 52 20 00 e0 00 03:58:10.144 READ DMA c8 00 bc 50 20 00 e0 00 03:58:10.128 READ DMA e5 00 00 54 20 00 a0 00 03:58:10.128 CHECK POWER MODE Error 486 occurred at disk power-on lifetime: 1633 hours (68 days + 1 hours) When the command that caused the error occurred, the device was in an unknown state. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 40 51 01 b4 04 1b e1 Error: UNC 1 sectors at LBA = 0x011b04b4 = 18547892 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- c8 00 01 b4 04 1b e1 00 03:56:47.904 READ DMA e5 00 00 b4 04 1b a0 00 03:56:47.888 CHECK POWER MODE c8 00 01 b4 04 1b e1 00 03:56:42.928 READ DMA e5 00 00 b4 04 1b a0 00 03:56:42.896 CHECK POWER MODE c8 00 01 b4 04 1b e1 00 03:56:37.952 READ DMA Error 485 occurred at disk power-on lifetime: 1633 hours (68 days + 1 hours) When the command that caused the error occurred, the device was in an unknown state. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 40 51 01 b4 04 1b e1 Error: UNC 1 sectors at LBA = 0x011b04b4 = 18547892 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- c8 00 01 b4 04 1b e1 00 03:56:42.928 READ DMA e5 00 00 b4 04 1b a0 00 03:56:42.896 CHECK POWER MODE c8 00 01 b4 04 1b e1 00 03:56:37.952 READ DMA e5 00 00 b4 04 1b a0 00 03:56:37.920 CHECK POWER MODE c8 00 01 b4 04 1b e1 00 03:55:27.424 READ DMA Error 484 occurred at disk power-on lifetime: 1633 hours (68 days + 1 hours) When the command that caused the error occurred, the device was in an unknown state. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 40 51 01 b4 04 1b e1 Error: UNC 1 sectors at LBA = 0x011b04b4 = 18547892 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- c8 00 01 b4 04 1b e1 00 03:56:37.952 READ DMA e5 00 00 b4 04 1b a0 00 03:56:37.920 CHECK POWER MODE c8 00 01 b4 04 1b e1 00 03:55:27.424 READ DMA e5 00 00 b4 04 1b a0 00 03:55:27.408 CHECK POWER MODE c8 00 01 b4 04 1b e1 00 03:55:22.448 READ DMA SMART Self-test log structure revision number 1 Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error # 1 Short offline Completed without error 00% 4529 - 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. ---------8<-------------------------------------------------------------- Die Platte ist eigentlich aus einem Topfield-Satreceiver, der kaputt gegangen ist und kam jetzt erst in einen neuen Rechner rein. Am Anfang konnte SUSE mit dem Rechner noch nicht richtig umgehen, und zwar weil der Original-Kernel 2.6.16(?) von SUSE 10.1 nicht richtig mit dem Via-P4M890/VT8237A-Chipsatz umgehen kann. Das äußerte sich darin, daß SUSE die IDE-Geräte nicht fand (auch schon beim Installieren), erst ein "insmod=ide-generic" als Übergabe an grub hat überhaupt eine Installation ermöglicht. Und bis dann der Kernel 2.6.18-5 installiert war, liefen die Platten damit. Da gingdann kein DMA usw. Vielleicht rühren die Einträge auch daher? mfG, Jens