sindreij Skrevet 26. januar 2012 Rapporter Del Skrevet 26. januar 2012 Hei Jeg har problemer med en disk som står i raid. Jeg har 3 disker i et raid5 (md0), som igjen er sammensatt med lvm. Maskinen kjører Arch Linux. Plutselig har den begynt å gå tregt til tider. Jeg ser mdstat og den sier at raidet blir resyncet. Console spytter ut kontinuerlig meldinger som ser helt like ut: [ 4769.012968] ata7.00: failed command: READ DMA EXT [ 4769.016866] ata7.00: cmd 25/00:00:95:a2:60/00:04:03:00:00/e0 tag 0 dma 524288 in [ 4769.016867] res 51/40:33:62:a5:60/40:01:03:00:00/e0 Emask 0x9 (media error) [ 4769.024780] ata7.00: status: { DRDY ERR } [ 4769.028720] ata7.00: error: { UNC } [ 4769.176554] ata7.00: configured for UDMA/133 [ 4769.176592] ata7: EH complete [ 4770.155856] ata7.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 [ 4770.159815] ata7.00: BMDMA stat 0x24 Når jeg sjekker kernel.log, ser jeg starten på rebyggingen: Jan 25 22:09:39 localhost kernel: [ 2.330640] md: md0 stopped. Jan 25 22:09:39 localhost kernel: [ 2.748465] md/raid:md0: device sda3 operational as raid disk 0 Jan 25 22:09:39 localhost kernel: [ 2.748468] md/raid:md0: device sdc3 operational as raid disk 2 Jan 25 22:09:39 localhost kernel: [ 2.748469] md/raid:md0: device sdb3 operational as raid disk 1 Jan 25 22:09:39 localhost kernel: [ 2.748822] md/raid:md0: allocated 3220kB Jan 25 22:09:39 localhost kernel: [ 2.748855] md/raid:md0: raid level 5 active with 3 out of 3 devices, algorithm 2 Jan 25 22:09:39 localhost kernel: [ 2.748892] md0: detected capacity change from 0 to 1996108070912 Jan 25 22:09:39 localhost kernel: [ 2.758811] md0: unknown partition table Jan 26 02:19:56 localhost kernel: [15025.695448] md/raid:md0: read error corrected (8 sectors at 50342784 on sdc3) Jan 26 12:13:17 localhost kernel: [ 3.334721] md: md0 stopped. Jan 26 12:13:17 localhost kernel: [ 3.751772] md/raid:md0: not clean -- starting background reconstruction Jan 26 12:13:17 localhost kernel: [ 3.751782] md/raid:md0: device sda3 operational as raid disk 0 Jan 26 12:13:17 localhost kernel: [ 3.751784] md/raid:md0: device sdc3 operational as raid disk 2 Jan 26 12:13:17 localhost kernel: [ 3.751786] md/raid:md0: device sdb3 operational as raid disk 1 Jan 26 12:13:17 localhost kernel: [ 3.752135] md/raid:md0: allocated 3220kB Jan 26 12:13:17 localhost kernel: [ 3.752167] md/raid:md0: raid level 5 active with 3 out of 3 devices, algorithm 2 Jan 26 12:13:17 localhost kernel: [ 3.752202] md0: detected capacity change from 0 to 1996108070912 Jan 26 12:13:17 localhost kernel: [ 3.752733] md: resync of RAID array md0 Jan 26 12:13:17 localhost kernel: [ 3.790583] md0: unknown partition table Jan 26 12:13:17 localhost kernel: [ 58.787694] md/raid:md0: read error corrected (8 sectors at 52436232 on sdc3) Jan 26 12:53:30 localhost kernel: [ 2474.146713] md/raid:md0: read error corrected (8 sectors at 45753344 on sdc3) Jan 26 12:53:30 localhost kernel: [ 2474.146720] md/raid:md0: read error corrected (8 sectors at 45753352 on sdc3) Jan 26 12:53:30 localhost kernel: [ 2474.146723] md/raid:md0: read error corrected (8 sectors at 45753360 on sdc3) Den fortsetter å spytte ut "read error corrected" på forskjellige sektorer kontinuerlig. Output fra smartctl -a /dev/sdc: (Jeg har kjørt en lang og en kort test nå nylig) smartctl 5.42 2011-10-20 r3458 [x86_64-linux-3.1.8-1-ARCH] (local build) Copyright (C) 2002-11 by Bruce Allen, http://smartmontools.sourceforge.net Smartctl open device: /dev/sdc failed: Permission denied [sindre@sindreLinux ~]$ sudo smartctl -a /dev/sdc smartctl 5.42 2011-10-20 r3458 [x86_64-linux-3.1.8-1-ARCH] (local build) Copyright (C) 2002-11 by Bruce Allen, http://smartmontools.sourceforge.net === START OF INFORMATION SECTION === Model Family: SAMSUNG SpinPoint F3 Device Model: SAMSUNG HD103SJ Serial Number: S246J1CZ302338 LU WWN Device Id: 5 0024e9 0032f56c0 Firmware Version: 1AJ10001 User Capacity: 1,000,204,886,016 bytes [1.00 TB] Sector Size: 512 bytes logical/physical Device is: In smartctl database [for details use: -P show] ATA Version is: 8 ATA Standard is: ATA-8-ACS revision 6 Local Time is: Thu Jan 26 13:41:48 2012 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 General SMART Values: Offline data collection status: (0x80) Offline data collection activity was never started. 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: ( 9360) 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: ( 2) minutes. Extended self-test routine recommended polling time: ( 156) 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 FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x002f 100 100 051 Pre-fail Always - 17078 2 Throughput_Performance 0x0026 252 252 000 Old_age Always - 0 3 Spin_Up_Time 0x0023 070 069 025 Pre-fail Always - 9348 4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 40 5 Reallocated_Sector_Ct 0x0033 252 252 010 Pre-fail Always - 0 7 Seek_Error_Rate 0x002e 252 252 051 Old_age Always - 0 8 Seek_Time_Performance 0x0024 252 252 015 Old_age Offline - 0 9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 13588 10 Spin_Retry_Count 0x0032 252 252 051 Old_age Always - 0 11 Calibration_Retry_Count 0x0032 252 252 000 Old_age Always - 0 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 40 191 G-Sense_Error_Rate 0x0022 252 252 000 Old_age Always - 0 192 Power-Off_Retract_Count 0x0022 252 252 000 Old_age Always - 0 194 Temperature_Celsius 0x0002 062 059 000 Old_age Always - 38 (Min/Max 17/41) 195 Hardware_ECC_Recovered 0x003a 100 100 000 Old_age Always - 0 196 Reallocated_Event_Count 0x0032 252 252 000 Old_age Always - 0 197 Current_Pending_Sector 0x0032 099 095 000 Old_age Always - 147 198 Offline_Uncorrectable 0x0030 252 252 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x0036 100 100 000 Old_age Always - 1 200 Multi_Zone_Error_Rate 0x002a 100 100 000 Old_age Always - 8277 223 Load_Retry_Count 0x0032 252 252 000 Old_age Always - 0 225 Load_Cycle_Count 0x0032 100 100 000 Old_age Always - 40 SMART Error Log Version: 1 ATA Error Count: 2940 (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 2940 occurred at disk power-on lifetime: 13588 hours (566 days + 4 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 0d b8 a6 3a e3 Error: UNC 13 sectors at LBA = 0x033aa6b8 = 54175416 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 80 45 a6 3a e3 08 00:00:04.617 READ DMA 27 00 00 00 00 00 e0 08 00:00:04.617 READ NATIVE MAX ADDRESS EXT ec 00 00 00 00 00 a0 08 00:00:04.617 IDENTIFY DEVICE ef 03 46 00 00 00 a0 08 00:00:04.617 SET FEATURES [set transfer mode] 27 00 00 00 00 00 e0 08 00:00:04.617 READ NATIVE MAX ADDRESS EXT Error 2939 occurred at disk power-on lifetime: 13588 hours (566 days + 4 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 0d b8 a6 3a e3 Error: UNC 13 sectors at LBA = 0x033aa6b8 = 54175416 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 80 45 a6 3a e3 08 00:00:04.614 READ DMA 27 00 00 00 00 00 e0 08 00:00:04.614 READ NATIVE MAX ADDRESS EXT ec 00 00 00 00 00 a0 08 00:00:04.614 IDENTIFY DEVICE ef 03 46 00 00 00 a0 08 00:00:04.614 SET FEATURES [set transfer mode] 27 00 00 00 00 00 e0 08 00:00:04.614 READ NATIVE MAX ADDRESS EXT Error 2938 occurred at disk power-on lifetime: 13588 hours (566 days + 4 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 0d b8 a6 3a e3 Error: UNC 13 sectors at LBA = 0x033aa6b8 = 54175416 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 80 45 a6 3a e3 08 00:00:04.613 READ DMA 27 00 00 00 00 00 e0 08 00:00:04.613 READ NATIVE MAX ADDRESS EXT ec 00 00 00 00 00 a0 08 00:00:04.613 IDENTIFY DEVICE ef 03 46 00 00 00 a0 08 00:00:04.613 SET FEATURES [set transfer mode] 27 00 00 00 00 00 e0 08 00:00:04.613 READ NATIVE MAX ADDRESS EXT Error 2937 occurred at disk power-on lifetime: 13588 hours (566 days + 4 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 0d b8 a6 3a e3 Error: UNC 13 sectors at LBA = 0x033aa6b8 = 54175416 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 80 45 a6 3a e3 08 00:00:04.611 READ DMA 27 00 00 00 00 00 e0 08 00:00:04.611 READ NATIVE MAX ADDRESS EXT ec 00 00 00 00 00 a0 08 00:00:04.611 IDENTIFY DEVICE ef 03 46 00 00 00 a0 08 00:00:04.611 SET FEATURES [set transfer mode] 27 00 00 00 00 00 e0 08 00:00:04.611 READ NATIVE MAX ADDRESS EXT Error 2936 occurred at disk power-on lifetime: 13588 hours (566 days + 4 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 0d b8 a6 3a e3 Error: UNC 13 sectors at LBA = 0x033aa6b8 = 54175416 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 80 45 a6 3a e3 08 00:00:04.609 READ DMA 27 00 00 00 00 00 e0 08 00:00:04.609 READ NATIVE MAX ADDRESS EXT ec 00 00 00 00 00 a0 08 00:00:04.609 IDENTIFY DEVICE ef 03 46 00 00 00 a0 08 00:00:04.609 SET FEATURES [set transfer mode] 27 00 00 00 00 00 e0 08 00:00:04.609 READ NATIVE MAX ADDRESS EXT 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% 13587 49946309 # 2 Short offline Completed: read failure 70% 13587 50082807 Note: selective self-test log revision number (0) not 1 implies that no selective self-test has ever been run SMART Selective self-test log data structure revision number 0 Note: revision number not 1 implies that no selective self-test has ever been run SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS 1 0 0 Completed_read_failure [90% left] (0-65535) 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. Er det noen som kan hjelpe meg? Er der hovedkortet som har gått, eller er det disken? Eller er det linux som tuller? Lenke til kommentar
vidarkri Skrevet 26. januar 2012 Rapporter Del Skrevet 26. januar 2012 (endret) Hvis statistikken som listes er riktig og det faktisk er 252 reallokerte sectorer på disken som det kjøres måling på der så er den skikkelig ute og kjører ja. Jeg ville testet disken med fabrikantens testverktøy for å verifisere SMARTlistingen der. 252 skadete sektorer er en klar indikasjon på at disken er på tur til de evige jaktmarker. De fleste fabrikanter opererer med under halvparten av den verdien som grense for å bytte disken på garanti.(Eller opererte er vel mer riktig, siden de fleste har gjort om litt på reglene etter diskkrisen) EDIT: Hyppig reallokering av sektorer vil vel muligens kunne medføre en resync av raidet. Endret 26. januar 2012 av vidarkri Lenke til kommentar
mikeys Skrevet 27. januar 2012 Rapporter Del Skrevet 27. januar 2012 Du har også en del sektorer som venter på å bli reallokert 197 Current_Pending_Sector 0x0032 099 095 000 Old_age Always - 147 Det enkleste du kan gjøre for å få reallokert de dårlige blokkene er å lese hele disken og se hva som skjer, feks med md5sum /dev/sdc, som er en nokså hardhendt måte å gjør det på. Hvis du har god tid og innsatsvilje kan du se på http://smartmontools.sourceforge.net/badblockhowto.html for en litt mer elegant løsning. Hvis disken fortsetter slik den gjør er det godt mulig at den vil ta kvelden om en liten stund, det kan være en god ide og skaffe seg en ny disk (av samme størrelse) og legge den inn som "hot-spare". Lenke til kommentar
Anbefalte innlegg
Opprett en konto eller logg inn for å kommentere
Du må være et medlem for å kunne skrive en kommentar
Opprett konto
Det er enkelt å melde seg inn for å starte en ny konto!
Start en kontoLogg inn
Har du allerede en konto? Logg inn her.
Logg inn nå