milosz_bozenski Napisano Sierpień 24, 2007 Zgłoszenie Share Napisano Sierpień 24, 2007 dzisiaj zaniepokoiła mnie jedna sytuacja. parę razy dysk mi się wyłączył i od razu włączył. postanowiłem zrobić smartctl --test=LONG /dev/hda i baaaaaaardzo zaniepokoiło mnie parę lini potem gdy wywołałem smartctl -a /dev/hda . oto one: Error 46 occurred at disk power-on lifetime: 681 hours (28 days + 9 hours) When the command that caused the error occurred, the device was active or idle. .... SMART Self-test log structure revision number 1 Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error # 1 Extended offline Completed: read failure 90% 681 417244 # 2 Conveyance offline Completed without error 00% 321 - # 3 Conveyance offline Completed without error 00% 769 - jak nie mam powodów do niepokoju to powiedźcie - nie będę się martwił bezpodstawnie ... ps. a tu jeszcze gdyby ktoś chciał zobaczyć całość co wypluł smartctl === START OF INFORMATION SECTION === Model Family: Western Digital Caviar family Device Model: WDC WD200BB-00CLB0 Serial Number: WD-WMAAR2611449 Firmware Version: 05.04E05 User Capacity: 20,020,396,032 bytes Device is: In smartctl database [for details use: -P show] ATA Version is: 5 ATA Standard is: Exact ATA specification draft version not indicated Local Time is: Fri Aug 24 19:16:21 2007 CEST 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: (0x82) Offline data collection activity was completed without error. Auto Offline Data Collection: Enabled. Self-test execution status: ( 121) The previous self-test completed having the read element of the test failed. Total time to complete Offline data collection: (1584) seconds. Offline data collection capabilities: (0x3b) 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. No 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. No General Purpose Logging support. Short self-test routine recommended polling time: ( 2) minutes. Extended self-test routine recommended polling time: ( 28) minutes. Conveyance self-test routine recommended polling time: ( 5) minutes. 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 195 195 051 Pre-fail Always - 52 3 Spin_Up_Time 0x0007 116 088 021 Pre-fail Always - 1550 4 Start_Stop_Count 0x0032 093 093 040 Old_age Always - 7062 5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail Always - 0 7 Seek_Error_Rate 0x000b 200 200 051 Pre-fail Always - 0 9 Power_On_Hours 0x0032 077 077 000 Old_age Always - 17066 10 Spin_Retry_Count 0x0013 100 100 051 Pre-fail Always - 0 11 Calibration_Retry_Count 0x0013 100 100 051 Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 094 094 000 Old_age Always - 6615 196 Reallocated_Event_Count 0x0032 200 200 000 Old_age Always - 0 197 Current_Pending_Sector 0x0012 200 200 000 Old_age Always - 1 198 Offline_Uncorrectable 0x0012 200 200 000 Old_age Always - 1 199 UDMA_CRC_Error_Count 0x000a 200 200 000 Old_age Always - 796 200 Multi_Zone_Error_Rate 0x0009 200 200 051 Pre-fail Offline - 0 SMART Error Log Version: 1 ATA Error Count: 50 (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 50 occurred at disk power-on lifetime: 681 hours (28 days + 9 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 30 dc 5d 06 e0 Error: UNC 48 sectors at LBA = 0x00065ddc = 417244 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 30 d5 5d 06 e0 00 00:22:57.750 READ DMA c8 00 38 cd 5d 06 e0 00 00:22:55.150 READ DMA c8 00 40 c5 5d 06 e0 00 00:22:52.500 READ DMA c8 00 48 bd 5d 06 e0 00 00:22:49.900 READ DMA c8 00 50 b5 5d 06 e0 00 00:22:47.400 READ DMA Error 49 occurred at disk power-on lifetime: 681 hours (28 days + 9 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 38 dc 5d 06 e0 Error: UNC 56 sectors at LBA = 0x00065ddc = 417244 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 38 cd 5d 06 e0 00 00:22:55.150 READ DMA c8 00 40 c5 5d 06 e0 00 00:22:52.500 READ DMA c8 00 48 bd 5d 06 e0 00 00:22:49.900 READ DMA c8 00 50 b5 5d 06 e0 00 00:22:47.400 READ DMA c8 00 58 ad 5d 06 e0 00 00:22:44.850 READ DMA Error 48 occurred at disk power-on lifetime: 681 hours (28 days + 9 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 40 dc 5d 06 e0 Error: UNC 64 sectors at LBA = 0x00065ddc = 417244 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 40 c5 5d 06 e0 00 00:22:52.500 READ DMA c8 00 48 bd 5d 06 e0 00 00:22:49.900 READ DMA c8 00 50 b5 5d 06 e0 00 00:22:47.400 READ DMA c8 00 58 ad 5d 06 e0 00 00:22:44.850 READ DMA c8 00 60 a5 5d 06 e0 00 00:22:42.250 READ DMA Error 47 occurred at disk power-on lifetime: 681 hours (28 days + 9 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 48 dc 5d 06 e0 Error: UNC 72 sectors at LBA = 0x00065ddc = 417244 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 48 bd 5d 06 e0 00 00:22:49.900 READ DMA c8 00 50 b5 5d 06 e0 00 00:22:47.400 READ DMA c8 00 58 ad 5d 06 e0 00 00:22:44.850 READ DMA c8 00 60 a5 5d 06 e0 00 00:22:42.250 READ DMA c8 00 68 9d 5d 06 e0 00 00:22:39.400 READ DMA Error 46 occurred at disk power-on lifetime: 681 hours (28 days + 9 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 50 dc 5d 06 e0 Error: UNC 80 sectors at LBA = 0x00065ddc = 417244 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 50 b5 5d 06 e0 00 00:22:47.400 READ DMA c8 00 58 ad 5d 06 e0 00 00:22:44.850 READ DMA c8 00 60 a5 5d 06 e0 00 00:22:42.250 READ DMA c8 00 68 9d 5d 06 e0 00 00:22:39.400 READ DMA c8 00 70 95 5d 06 e0 00 00:22:36.900 READ DMA SMART Self-test log structure revision number 1 Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error # 1 Extended offline Completed: read failure 90% 681 417244 # 2 Conveyance offline Completed without error 00% 321 - # 3 Conveyance offline Completed without error 00% 769 - Odnośnik do komentarza Udostępnij na innych stronach More sharing options...
exbros Napisano Wrzesień 6, 2007 Zgłoszenie Share Napisano Wrzesień 6, 2007 Co prawda pytanie stare jak swiat, ale ze nie doczekalo sie odpowiedzi... Tak - to co widzisz w logach to w 100% padaczka. Taki stan moze potrwac kilka dni/tygodni/miesiecy zanim dysk sie kompletnie wysypie (lub zacznie tracic kolejne sektory z czestotliwoscia uniemozliwiajaca normalna prace), w kazdym badz razie ja jak najszybciej przeniosl bym system i dane na nowy (a przynajmniej w 100% sprawny) dysk, a tego uzywal jako skladowiska niewaznych smieci Pozdro Odnośnik do komentarza Udostępnij na innych stronach More sharing options...
Rekomendowane odpowiedzi
Jeśli chcesz dodać odpowiedź, zaloguj się lub zarejestruj nowe konto
Jedynie zarejestrowani użytkownicy mogą komentować zawartość tej strony.
Zarejestruj nowe konto
Załóż nowe konto. To bardzo proste!
Zarejestruj sięZaloguj się
Posiadasz już konto? Zaloguj się poniżej.
Zaloguj się