Moin, seit einiger Zeit passiert es nach ein bis 2 Tagen das plötzlich die Festplatten "rödeln" und das sogar soweit geht das das das System unbedienbar wird und noch nicht mal mehr die Uhr aktuell ist. Im Prozessmonitor ist aber nichts zu sehen. Gibt es noch eine Möglichkeit festzustellen, was das System dermaßen belastet das kein arbeiten mehr möglich ist?
Extreme Festplattenbelastung bis zum Systemstillstand
Anmeldungsdatum: Beiträge: 38 |
|
Anmeldungsdatum: Beiträge: 11176 Wohnort: München |
Ich würde mir den Festplattenstatus ansehen (nicht dass Schreib- oder Lesefehler auf bestimmten Sektoren das System ausbremsen) und mit iotop nachsehen, wer da gerade viel Last erzeugt. |
(Themenstarter)
Anmeldungsdatum: Beiträge: 38 |
Tja, ich würde sagen, Fehler gefunden danke für den Tipp ☺ smartctl 6.6 2016-05-31 r4324 [x86_64-linux-4.8.0-37-generic] (local build) Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org Warning: DEFAULT entry missing in drive database file(s) === START OF INFORMATION SECTION === Model Family: Seagate Barracuda Green (AF) Device Model: ST2000DL003-9VT166 Serial Number: 5YD5SLGC LU WWN Device Id: 5 000c50 0440840f6 Firmware Version: CC3C User Capacity: 2,000,398,934,016 bytes [2.00 TB] Sector Sizes: 512 bytes logical, 4096 bytes physical Rotation Rate: 5900 rpm Device is: In smartctl database [for details use: -P show] ATA Version is: ATA8-ACS T13/1699-D revision 4 SATA Version is: SATA 3.0, 6.0 Gb/s (current: 6.0 Gb/s) Local Time is: Sun Feb 19 10:36:57 2017 CET 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 See vendor-specific Attribute list for marginal Attributes. 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: ( 0) The previous self-test routine completed without error or no self-test has ever been run. Total time to complete Offline data collection: ( 623) 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: ( 1) minutes. Extended self-test routine recommended polling time: ( 352) minutes. Conveyance self-test routine recommended polling time: ( 2) minutes. SCT capabilities: (0x30b7) SCT Status supported. SCT Feature Control supported. SCT Data Table supported. SMART Attributes Data Structure revision number: 10 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x000f 106 099 006 Pre-fail Always - 10862408 3 Spin_Up_Time 0x0003 093 092 000 Pre-fail Always - 0 4 Start_Stop_Count 0x0032 096 096 020 Old_age Always - 4956 5 Reallocated_Sector_Ct 0x0033 100 100 036 Pre-fail Always - 0 7 Seek_Error_Rate 0x000f 076 060 030 Pre-fail Always - 30459810655 9 Power_On_Hours 0x0032 059 059 000 Old_age Always - 36648 10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 098 098 020 Old_age Always - 2586 183 Runtime_Bad_Block 0x0032 073 073 000 Old_age Always - 27 184 End-to-End_Error 0x0032 100 100 099 Old_age Always - 0 187 Reported_Uncorrect 0x0032 081 081 000 Old_age Always - 19 188 Command_Timeout 0x0032 100 082 000 Old_age Always - 103080789099 189 High_Fly_Writes 0x003a 100 100 000 Old_age Always - 0 190 Airflow_Temperature_Cel 0x0022 064 038 045 Old_age Always In_the_past 36 (9 228 37 36 0) 191 G-Sense_Error_Rate 0x0032 100 100 000 Old_age Always - 0 192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 981 193 Load_Cycle_Count 0x0032 098 098 000 Old_age Always - 5339 194 Temperature_Celsius 0x0022 036 062 000 Old_age Always - 36 (0 14 0 0 0) 195 Hardware_ECC_Recovered 0x001a 028 006 000 Old_age Always - 10862408 197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0010 100 100 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x003e 200 197 000 Old_age Always - 542 240 Head_Flying_Hours 0x0000 100 253 000 Old_age Offline - 22254 (153 254 0) 241 Total_LBAs_Written 0x0000 100 253 000 Old_age Offline - 2087464448 242 Total_LBAs_Read 0x0000 100 253 000 Old_age Offline - 2804922953 SMART Error Log Version: 1 ATA Error Count: 19 (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 19 occurred at disk power-on lifetime: 32273 hours (1344 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 00 ff ff ff 0f Error: UNC at LBA = 0x0fffffff = 268435455 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 00 40 ff ff ff 4f 00 01:43:19.566 READ FPDMA QUEUED ef 02 00 00 00 00 00 00 01:43:19.554 SET FEATURES [Enable write cache] 00 00 00 00 00 00 00 ff 01:43:19.451 NOP [Abort queued commands] 60 00 40 ff ff ff 4f 00 01:43:16.121 READ FPDMA QUEUED ef 02 00 00 00 00 00 00 01:43:16.028 SET FEATURES [Enable write cache] Error 18 occurred at disk power-on lifetime: 32273 hours (1344 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 00 ff ff ff 0f Error: UNC at LBA = 0x0fffffff = 268435455 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 00 40 ff ff ff 4f 00 01:43:16.121 READ FPDMA QUEUED ef 02 00 00 00 00 00 00 01:43:16.028 SET FEATURES [Enable write cache] 00 00 00 00 00 00 00 ff 01:43:15.973 NOP [Abort queued commands] 60 00 40 ff ff ff 4f 00 01:43:12.656 READ FPDMA QUEUED ef 02 00 00 00 00 00 00 01:43:12.580 SET FEATURES [Enable write cache] Error 17 occurred at disk power-on lifetime: 32273 hours (1344 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 00 ff ff ff 0f Error: UNC at LBA = 0x0fffffff = 268435455 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 00 40 ff ff ff 4f 00 01:43:12.656 READ FPDMA QUEUED ef 02 00 00 00 00 00 00 01:43:12.580 SET FEATURES [Enable write cache] 00 00 00 00 00 00 00 ff 01:43:12.562 NOP [Abort queued commands] 60 00 40 ff ff ff 4f 00 01:43:09.243 READ FPDMA QUEUED ef 02 00 00 00 00 00 00 01:43:09.226 SET FEATURES [Enable write cache] Error 16 occurred at disk power-on lifetime: 32273 hours (1344 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 00 ff ff ff 0f Error: UNC at LBA = 0x0fffffff = 268435455 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 00 40 ff ff ff 4f 00 01:43:09.243 READ FPDMA QUEUED ef 02 00 00 00 00 00 00 01:43:09.226 SET FEATURES [Enable write cache] 00 00 00 00 00 00 00 ff 01:43:09.118 NOP [Abort queued commands] 60 00 40 ff ff ff 4f 00 01:43:05.778 READ FPDMA QUEUED ef 02 00 00 00 00 00 00 01:43:05.762 SET FEATURES [Enable write cache] Error 15 occurred at disk power-on lifetime: 32273 hours (1344 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 00 ff ff ff 0f Error: UNC at LBA = 0x0fffffff = 268435455 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 00 40 ff ff ff 4f 00 01:43:05.778 READ FPDMA QUEUED ef 02 00 00 00 00 00 00 01:43:05.762 SET FEATURES [Enable write cache] 00 00 00 00 00 00 00 ff 01:43:05.653 NOP [Abort queued commands] 60 00 40 ff ff ff 4f 00 01:43:02.313 READ FPDMA QUEUED ef 02 00 00 00 00 00 00 01:43:02.299 SET FEATURES [Enable write cache] 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. |
Anmeldungsdatum: Beiträge: 850 Wohnort: Berlin Weißensee |
Woran machst Du das fest? Ist es die "Power_On_Hours"? Nicht jeder ist so versiert und könnte was lernen, deshalb wär schön wenn Du verrätst wo Du den Fehler siehst. Die Attribute 5 und 197 stehen auf Null, defekte Sektoren scheinst Du nicht zu haben, wo ist denn jetzt der Fehler? |
(Themenstarter)
Anmeldungsdatum: Beiträge: 38 |
OK, da war ich wohl etwas voreilig. Ich habe nur das "Error" gesehen. Aber: Was mir jetzt aufgefallen ist, in Gparted bekomme ich die im Bild zu sehende Fehlermeldung. Aber netterweise nicht, auf welche Festplatte das zutrifft. Ich habe 3: 2 im Raid 0 und die Systemfestplatte. ich habe schon versucht, durch Tante Google herauszufinden wie ich eben genau diese Information bekomme. |