February 23, 201115 yr Hi during my last Parity-Check i had 1488 errors. (syslog_1). After the check i rebooted the server and did a Parity Verify with unmenu and the errors are still there (syslog_2). I did a Short SMART test on all my disks in the server. In the media_server.zip you can find the SMART test results and the Syslog from the Parity Check and the Parity Verify. I do not know what i should do next to get rid of the errors. Thanks in advance ps: unraid version: 4.6 media_server.zip
February 23, 201115 yr Author does anybody know what this means? and what i can do about it? Feb 22 10:39:26 media-server kernel: md: parity incorrect: 257256616 Feb 22 10:39:34 media-server kernel: md: parity incorrect: 257846112 Feb 22 10:39:36 media-server kernel: md: parity incorrect: 258051296 Feb 22 10:40:51 media-server kernel: md: parity incorrect: 264094528 Feb 22 10:41:27 media-server kernel: md: parity incorrect: 267038480 Feb 22 10:41:28 media-server kernel: md: parity incorrect: 267166624 Feb 22 10:42:14 media-server kernel: md: parity incorrect: 270991760 Feb 22 10:42:54 media-server kernel: md: parity incorrect: 274306424 Feb 22 10:42:54 media-server kernel: md: parity incorrect: 274306432 Feb 22 10:43:09 media-server kernel: md: parity incorrect: 275526576 Feb 22 10:43:23 media-server kernel: md: parity incorrect: 276469336 Feb 22 10:43:23 media-server kernel: md: parity incorrect: 276469344 Feb 22 10:43:32 media-server kernel: md: parity incorrect: 277235632 Feb 22 10:43:36 media-server kernel: md: parity incorrect: 277535792 Feb 22 10:43:43 media-server kernel: md: parity incorrect: 278058240 Feb 22 10:43:45 media-server kernel: md: parity incorrect: 278278200 Feb 22 10:43:45 media-server kernel: md: parity incorrect: 278278208 Feb 22 10:43:52 media-server kernel: md: parity incorrect: 278874040 Feb 22 10:43:52 media-server kernel: md: parity incorrect: 278874048 Feb 22 10:44:04 media-server kernel: md: parity incorrect: 279980192
February 23, 201115 yr does anybody know what this means? and what i can do about it? Feb 22 10:39:26 media-server kernel: md: parity incorrect: 257256616 Feb 22 10:39:34 media-server kernel: md: parity incorrect: 257846112 Feb 22 10:39:36 media-server kernel: md: parity incorrect: 258051296 Feb 22 10:40:51 media-server kernel: md: parity incorrect: 264094528 Feb 22 10:41:27 media-server kernel: md: parity incorrect: 267038480 Feb 22 10:41:28 media-server kernel: md: parity incorrect: 267166624 Feb 22 10:42:14 media-server kernel: md: parity incorrect: 270991760 Feb 22 10:42:54 media-server kernel: md: parity incorrect: 274306424 Feb 22 10:42:54 media-server kernel: md: parity incorrect: 274306432 Feb 22 10:43:09 media-server kernel: md: parity incorrect: 275526576 Feb 22 10:43:23 media-server kernel: md: parity incorrect: 276469336 Feb 22 10:43:23 media-server kernel: md: parity incorrect: 276469344 Feb 22 10:43:32 media-server kernel: md: parity incorrect: 277235632 Feb 22 10:43:36 media-server kernel: md: parity incorrect: 277535792 Feb 22 10:43:43 media-server kernel: md: parity incorrect: 278058240 Feb 22 10:43:45 media-server kernel: md: parity incorrect: 278278200 Feb 22 10:43:45 media-server kernel: md: parity incorrect: 278278208 Feb 22 10:43:52 media-server kernel: md: parity incorrect: 278874040 Feb 22 10:43:52 media-server kernel: md: parity incorrect: 278874048 Feb 22 10:44:04 media-server kernel: md: parity incorrect: 279980192 Is it always the same addresses? Or different ones each time you check parity? If different addresses each time you run it, you have probably have a disk, or disk controller, or motherboard that is mangling your data. IT will be a process of elimination to resolve which. In that case you do not want to tun the "Check" (and correct), because you cannot assume the parity disk is wrong) If the same addresses each time, The fix is to run the "Check" (and correct) It will assume the parity disk is wrong, your data disks correct, and correct parity to match.
February 23, 201115 yr Author does anybody know what this means? and what i can do about it? Feb 22 10:39:26 media-server kernel: md: parity incorrect: 257256616 Feb 22 10:39:34 media-server kernel: md: parity incorrect: 257846112 Feb 22 10:39:36 media-server kernel: md: parity incorrect: 258051296 Feb 22 10:40:51 media-server kernel: md: parity incorrect: 264094528 Feb 22 10:41:27 media-server kernel: md: parity incorrect: 267038480 Feb 22 10:41:28 media-server kernel: md: parity incorrect: 267166624 Feb 22 10:42:14 media-server kernel: md: parity incorrect: 270991760 Feb 22 10:42:54 media-server kernel: md: parity incorrect: 274306424 Feb 22 10:42:54 media-server kernel: md: parity incorrect: 274306432 Feb 22 10:43:09 media-server kernel: md: parity incorrect: 275526576 Feb 22 10:43:23 media-server kernel: md: parity incorrect: 276469336 Feb 22 10:43:23 media-server kernel: md: parity incorrect: 276469344 Feb 22 10:43:32 media-server kernel: md: parity incorrect: 277235632 Feb 22 10:43:36 media-server kernel: md: parity incorrect: 277535792 Feb 22 10:43:43 media-server kernel: md: parity incorrect: 278058240 Feb 22 10:43:45 media-server kernel: md: parity incorrect: 278278200 Feb 22 10:43:45 media-server kernel: md: parity incorrect: 278278208 Feb 22 10:43:52 media-server kernel: md: parity incorrect: 278874040 Feb 22 10:43:52 media-server kernel: md: parity incorrect: 278874048 Feb 22 10:44:04 media-server kernel: md: parity incorrect: 279980192 Is it always the same addresses? Or different ones each time you check parity? If different addresses each time you run it, you have probably have a disk, or disk controller, or motherboard that is mangling your data. IT will be a process of elimination to resolve which. In that case you do not want to tun the "Check" (and correct), because you cannot assume the parity disk is wrong) If the same addresses each time, The fix is to run the "Check" (and correct) It will assume the parity disk is wrong, your data disks correct, and correct parity to match. the first time i ran a parity check and correct and i had those errors: Feb 22 10:39:26 media-server kernel: md: parity incorrect: 257256616 Feb 22 10:39:34 media-server kernel: md: parity incorrect: 257846112 Feb 22 10:39:36 media-server kernel: md: parity incorrect: 258051296 Feb 22 10:40:51 media-server kernel: md: parity incorrect: 264094528 Feb 22 10:41:27 media-server kernel: md: parity incorrect: 267038480 Feb 22 10:41:28 media-server kernel: md: parity incorrect: 267166624 Feb 22 10:42:14 media-server kernel: md: parity incorrect: 270991760 Feb 22 10:42:54 media-server kernel: md: parity incorrect: 274306424 Feb 22 10:42:54 media-server kernel: md: parity incorrect: 274306432 Feb 22 10:43:09 media-server kernel: md: parity incorrect: 275526576 Feb 22 10:43:23 media-server kernel: md: parity incorrect: 276469336 Feb 22 10:43:23 media-server kernel: md: parity incorrect: 276469344 Feb 22 10:43:32 media-server kernel: md: parity incorrect: 277235632 Feb 22 10:43:36 media-server kernel: md: parity incorrect: 277535792 Feb 22 10:43:43 media-server kernel: md: parity incorrect: 278058240 Feb 22 10:43:45 media-server kernel: md: parity incorrect: 278278200 Feb 22 10:43:45 media-server kernel: md: parity incorrect: 278278208 Feb 22 10:43:52 media-server kernel: md: parity incorrect: 278874040 Feb 22 10:43:52 media-server kernel: md: parity incorrect: 278874048 Feb 22 10:44:04 media-server kernel: md: parity incorrect: 279980192 the second time i was running a parity check verify and i had the same errors: Feb 22 20:33:11 media-server kernel: md: parity incorrect: 257256616 Feb 22 20:33:18 media-server kernel: md: parity incorrect: 257846112 Feb 22 20:33:20 media-server kernel: md: parity incorrect: 258051296 Feb 22 20:34:34 media-server kernel: md: parity incorrect: 264094528 Feb 22 20:35:10 media-server kernel: md: parity incorrect: 267038480 Feb 22 20:35:12 media-server kernel: md: parity incorrect: 267166624 Feb 22 20:35:57 media-server kernel: md: parity incorrect: 270991760 Feb 22 20:36:36 media-server kernel: md: parity incorrect: 274306424 Feb 22 20:36:36 media-server kernel: md: parity incorrect: 274306432 Feb 22 20:36:51 media-server kernel: md: parity incorrect: 275526576 Feb 22 20:37:02 media-server kernel: md: parity incorrect: 276469336 Feb 22 20:37:02 media-server kernel: md: parity incorrect: 276469344 Feb 22 20:37:11 media-server kernel: md: parity incorrect: 277235632 Feb 22 20:37:15 media-server kernel: md: parity incorrect: 277535792 Feb 22 20:37:21 media-server kernel: md: parity incorrect: 278058240 Feb 22 20:37:23 media-server kernel: md: parity incorrect: 278278200 Feb 22 20:37:23 media-server kernel: md: parity incorrect: 278278208 Feb 22 20:37:31 media-server kernel: md: parity incorrect: 278874040 Feb 22 20:37:31 media-server kernel: md: parity incorrect: 278874048 Feb 22 20:37:43 media-server kernel: md: parity incorrect: 279980192 shouldn´t the first parity check and correct fix those problems?
February 23, 201115 yr Actually, that's worse. The first "check" changed parity based on what it "thought" it had read from the data disks. The second was a "NOCORRECT version, and apparently, it was able to read the data disks correctly but since the first "Check/correct" had already modified parity, it (parity) is now incorrect and needs to be corrected and it is being flagged in as wrong. I'd not trust the data disks at this point. One member had a similar issue and was able to figure out it was one of his disks by typing dd if=/dev/md1 count=10000 bs=1M iflag=direct | md5sum - again and again, for each of his disks in turn. ( /dev/md1, /dev/md2, /dev/md3, etc...) When he got to the bad disk it would return random checksums when it was read. I do not envy your position, since you do not know what to trust..., the data, or the parity... And you know you've already clobbered your parity, so it is not reliable unit you can ready your data disks consistently. Similar errors in the past have been traced to bad or incorrectly configured memory (most likely) a bad disk, a bad disk controller, or a bad motherboard chipset. Of course, it could be a noisy/overloaded power supply too. Joe L.
February 23, 201115 yr Author ok i did this dd if=/dev/md1 count=10000 bs=1M iflag=direct | md5sum - 3 times per disk. the checksum was always the same. so i would say that the disks are ok.? what should i do next... when the disks are ok a new parity check and correct and after this a parity verify? what would you recommend?
February 23, 201115 yr ok i did this dd if=/dev/md1 count=10000 bs=1M iflag=direct | md5sum - 3 times per disk. the checksum was always the same. so i would say that the disks are ok.? That is a really good first step. what should i do next... when the disks are ok a new parity check and correct and after this a parity verify? Sounds good to me too.
February 24, 201115 yr It would be nice if the syslog indicated the locations on disk of the parity errors. Never mind. I just found out those are sectors. Joe, is there any way to run the md5 over the sectors reported?
February 24, 201115 yr It would be nice if the syslog indicated the locations on disk of the parity errors. Never mind. I just found out those are sectors. Joe, is there any way to run the md5 over the sectors reported? Sure. Those should be sector numbers in the errors reported, so simply tell the "dd" to start the output there using "skip" like this: dd if=/dev/md1 count=100000 skip=257256616 iflag=direct | md5sum -
February 24, 201115 yr Are the sectors relative to the partition? If so, we need to add the size of the MBR to the value. Edit: Although the count is long enough to cover the MBR.
February 24, 201115 yr Are the sectors relative to the partition? If so, we need to add the size of the MBR to the value. Edit: Although the count is long enough to cover the MBR. The MBR is one sector, and, as far as I know, the sector numbers given are relative to the start of the partition.
February 24, 201115 yr Author ... i did this dd if=/dev/md1 count=100000 skip=257256616 iflag=direct | md5sum - 3 times per disk and the checksum was on every time ok. I recon I could try to do a new parity check and correct and after this a parity verify via unmenu? Any thoughts?
February 24, 201115 yr Yes, if parity is wrong this will correct things. If a data disk is wrong any files on those sectors will remain corrupted and you'll find out which files are corrupted when you try to use them. This is a worst case scenario. You could try the md5 test with a larger count but it will take a long time and you may not resolve the issue. Add "worst case scenario" to the title and you'll get more eyes on the problem.
February 24, 201115 yr Author Did someone look over my smart reports... I do not know how to interpret them correct (basically, I want to know if the drives are ok)
February 24, 201115 yr Did someone look over my smart reports... I do not know how to interpret them correct (basically, I want to know if the drives are ok) None of the SMART reports look unusual. There are no parameters FAILING_NOW, no re-allocated sectors, and none pending re-allocation. That does not indicate the drives are OK, but that SMART has not logged any errors.
February 24, 201115 yr Author is disk12 also ok? Because this smart report looks different at the end. Statistics for /dev/sdi SAMSUNG_HD154UI_S1XWJ1KSB15256 smartctl -a -d ata /dev/sdi smartctl 5.39.1 2010-01-28 r3054 [i486-slackware-linux-gnu] (local build) Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net === START OF INFORMATION SECTION === Device Model: SAMSUNG HD154UI Serial Number: S1XWJ1KSB15256 Firmware Version: 1AG01118 User Capacity: 1,500,301,910,016 bytes Device is: Not in smartctl database [for details use: -P showall] ATA Version is: 8 ATA Standard is: ATA-8-ACS revision 3b Local Time is: Wed Feb 23 10:14:54 2011 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: (0x00) Offline data collection activity was never started. Auto Offline Data Collection: Disabled. 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: (18751) 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: ( 2) minutes. Extended self-test routine recommended polling time: ( 255) minutes. Conveyance self-test routine recommended polling time: ( 33) minutes. SCT capabilities: (0x003f) SCT Status 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 0x000f 100 099 051 Pre-fail Always - 0 3 Spin_Up_Time 0x0007 062 062 011 Pre-fail Always - 12240 4 Start_Stop_Count 0x0032 099 099 000 Old_age Always - 1454 5 Reallocated_Sector_Ct 0x0033 100 100 010 Pre-fail Always - 0 7 Seek_Error_Rate 0x000f 253 253 051 Pre-fail Always - 0 8 Seek_Time_Performance 0x0025 100 100 015 Pre-fail Offline - 10864 9 Power_On_Hours 0x0032 098 098 000 Old_age Always - 10201 10 Spin_Retry_Count 0x0033 100 100 051 Pre-fail Always - 0 11 Calibration_Retry_Count 0x0012 100 100 000 Old_age Always - 0 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 97 13 Read_Soft_Error_Rate 0x000e 100 099 000 Old_age Always - 0 183 Runtime_Bad_Block 0x0032 100 100 000 Old_age Always - 0 184 End-to-End_Error 0x0033 100 100 000 Pre-fail Always - 0 187 Reported_Uncorrect 0x0032 100 100 000 Old_age Always - 16 188 Command_Timeout 0x0032 100 100 000 Old_age Always - 0 190 Airflow_Temperature_Cel 0x0022 079 068 000 Old_age Always - 21 (Lifetime Min/Max 9/24) 194 Temperature_Celsius 0x0022 090 067 000 Old_age Always - 10 (Lifetime Min/Max 9/25) 195 Hardware_ECC_Recovered 0x001a 100 100 000 Old_age Always - 775170981 196 Reallocated_Event_Count 0x0032 100 100 000 Old_age Always - 0 197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0030 100 100 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x003e 100 100 000 Old_age Always - 0 200 Multi_Zone_Error_Rate 0x000a 100 100 000 Old_age Always - 0 201 Soft_Read_Error_Rate 0x000a 100 100 000 Old_age Always - 0 SMART Error Log Version: 1 ATA Error Count: 5 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 5 occurred at disk power-on lifetime: 0 hours (0 days + 0 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 42 00 d4 ec Error: UNC at LBA = 0x0cd40042 = 215220290 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 08 3f 00 d4 ec 00 2d+04:36:42.340 READ DMA ec 00 00 00 00 00 a0 00 2d+04:36:42.330 IDENTIFY DEVICE ef 03 46 00 00 00 a0 00 2d+04:36:42.330 SET FEATURES [set transfer mode] ec 00 00 00 00 00 a0 00 2d+04:36:42.310 IDENTIFY DEVICE Error 4 occurred at disk power-on lifetime: 0 hours (0 days + 0 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 3f 00 d4 ec Error: UNC at LBA = 0x0cd4003f = 215220287 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 08 3f 00 d4 ec 00 2d+04:36:39.470 READ DMA c8 00 08 ef b6 3b e5 00 2d+04:36:39.340 READ DMA ca 00 1d 52 c0 d2 ec 00 2d+04:36:39.290 WRITE DMA c8 00 28 47 c0 d2 ec 00 2d+04:36:39.270 READ DMA ca 00 05 72 30 00 e0 00 2d+04:36:39.120 WRITE DMA Error 3 occurred at disk power-on lifetime: 0 hours (0 days + 0 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 48 00 d4 ec Error: UNC at LBA = 0x0cd40048 = 215220296 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 08 47 00 d4 ec 00 3d+22:47:41.790 READ DMA ec 00 00 00 00 00 a0 00 3d+22:47:41.770 IDENTIFY DEVICE ef 03 46 00 00 00 a0 00 3d+22:47:41.770 SET FEATURES [set transfer mode] ec 00 00 00 00 00 a0 00 3d+22:47:41.750 IDENTIFY DEVICE Error 2 occurred at disk power-on lifetime: 0 hours (0 days + 0 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 48 00 d4 ec Error: UNC at LBA = 0x0cd40048 = 215220296 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 08 47 00 d4 ec 00 3d+22:47:39.100 READ DMA ec 00 00 00 00 00 a0 00 3d+22:47:39.080 IDENTIFY DEVICE ef 03 46 00 00 00 a0 00 3d+22:47:39.080 SET FEATURES [set transfer mode] ec 00 00 00 00 00 a0 00 3d+22:47:39.070 IDENTIFY DEVICE Error 1 occurred at disk power-on lifetime: 0 hours (0 days + 0 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 48 00 d4 ec Error: UNC at LBA = 0x0cd40048 = 215220296 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 08 47 00 d4 ec 00 3d+22:47:36.360 READ DMA c8 00 08 47 00 38 e5 00 3d+22:47:36.350 READ DMA ca 00 02 ae 4b 00 e0 00 3d+22:47:36.340 WRITE DMA c8 00 08 a7 4b 00 e0 00 3d+22:47:36.340 READ DMA ca 00 05 92 4a 00 e0 00 3d+22:47:35.160 WRITE 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% 10201 - 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. if this is also ok i will do a new parity check.
February 24, 201115 yr is disk12 also ok? Because this smart report looks different at the end. Statistics for /dev/sdi SAMSUNG_HD154UI_S1XWJ1KSB15256 smartctl -a -d ata /dev/sdi smartctl 5.39.1 2010-01-28 r3054 [i486-slackware-linux-gnu] (local build) Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net === START OF INFORMATION SECTION === Device Model: SAMSUNG HD154UI Serial Number: S1XWJ1KSB15256 Firmware Version: 1AG01118 User Capacity: 1,500,301,910,016 bytes Device is: Not in smartctl database [for details use: -P showall] ATA Version is: 8 ATA Standard is: ATA-8-ACS revision 3b Local Time is: Wed Feb 23 10:14:54 2011 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: (0x00) Offline data collection activity was never started. Auto Offline Data Collection: Disabled. 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: (18751) 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: ( 2) minutes. Extended self-test routine recommended polling time: ( 255) minutes. Conveyance self-test routine recommended polling time: ( 33) minutes. SCT capabilities: (0x003f) SCT Status 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 0x000f 100 099 051 Pre-fail Always - 0 3 Spin_Up_Time 0x0007 062 062 011 Pre-fail Always - 12240 4 Start_Stop_Count 0x0032 099 099 000 Old_age Always - 1454 5 Reallocated_Sector_Ct 0x0033 100 100 010 Pre-fail Always - 0 7 Seek_Error_Rate 0x000f 253 253 051 Pre-fail Always - 0 8 Seek_Time_Performance 0x0025 100 100 015 Pre-fail Offline - 10864 9 Power_On_Hours 0x0032 098 098 000 Old_age Always - 10201 10 Spin_Retry_Count 0x0033 100 100 051 Pre-fail Always - 0 11 Calibration_Retry_Count 0x0012 100 100 000 Old_age Always - 0 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 97 13 Read_Soft_Error_Rate 0x000e 100 099 000 Old_age Always - 0 183 Runtime_Bad_Block 0x0032 100 100 000 Old_age Always - 0 184 End-to-End_Error 0x0033 100 100 000 Pre-fail Always - 0 187 Reported_Uncorrect 0x0032 100 100 000 Old_age Always - 16 188 Command_Timeout 0x0032 100 100 000 Old_age Always - 0 190 Airflow_Temperature_Cel 0x0022 079 068 000 Old_age Always - 21 (Lifetime Min/Max 9/24) 194 Temperature_Celsius 0x0022 090 067 000 Old_age Always - 10 (Lifetime Min/Max 9/25) 195 Hardware_ECC_Recovered 0x001a 100 100 000 Old_age Always - 775170981 196 Reallocated_Event_Count 0x0032 100 100 000 Old_age Always - 0 197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0030 100 100 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x003e 100 100 000 Old_age Always - 0 200 Multi_Zone_Error_Rate 0x000a 100 100 000 Old_age Always - 0 201 Soft_Read_Error_Rate 0x000a 100 100 000 Old_age Always - 0 SMART Error Log Version: 1 ATA Error Count: 5 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 5 occurred at disk power-on lifetime: 0 hours (0 days + 0 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 42 00 d4 ec Error: UNC at LBA = 0x0cd40042 = 215220290 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 08 3f 00 d4 ec 00 2d+04:36:42.340 READ DMA ec 00 00 00 00 00 a0 00 2d+04:36:42.330 IDENTIFY DEVICE ef 03 46 00 00 00 a0 00 2d+04:36:42.330 SET FEATURES [set transfer mode] ec 00 00 00 00 00 a0 00 2d+04:36:42.310 IDENTIFY DEVICE Error 4 occurred at disk power-on lifetime: 0 hours (0 days + 0 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 3f 00 d4 ec Error: UNC at LBA = 0x0cd4003f = 215220287 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 08 3f 00 d4 ec 00 2d+04:36:39.470 READ DMA c8 00 08 ef b6 3b e5 00 2d+04:36:39.340 READ DMA ca 00 1d 52 c0 d2 ec 00 2d+04:36:39.290 WRITE DMA c8 00 28 47 c0 d2 ec 00 2d+04:36:39.270 READ DMA ca 00 05 72 30 00 e0 00 2d+04:36:39.120 WRITE DMA Error 3 occurred at disk power-on lifetime: 0 hours (0 days + 0 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 48 00 d4 ec Error: UNC at LBA = 0x0cd40048 = 215220296 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 08 47 00 d4 ec 00 3d+22:47:41.790 READ DMA ec 00 00 00 00 00 a0 00 3d+22:47:41.770 IDENTIFY DEVICE ef 03 46 00 00 00 a0 00 3d+22:47:41.770 SET FEATURES [set transfer mode] ec 00 00 00 00 00 a0 00 3d+22:47:41.750 IDENTIFY DEVICE Error 2 occurred at disk power-on lifetime: 0 hours (0 days + 0 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 48 00 d4 ec Error: UNC at LBA = 0x0cd40048 = 215220296 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 08 47 00 d4 ec 00 3d+22:47:39.100 READ DMA ec 00 00 00 00 00 a0 00 3d+22:47:39.080 IDENTIFY DEVICE ef 03 46 00 00 00 a0 00 3d+22:47:39.080 SET FEATURES [set transfer mode] ec 00 00 00 00 00 a0 00 3d+22:47:39.070 IDENTIFY DEVICE Error 1 occurred at disk power-on lifetime: 0 hours (0 days + 0 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 48 00 d4 ec Error: UNC at LBA = 0x0cd40048 = 215220296 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 08 47 00 d4 ec 00 3d+22:47:36.360 READ DMA c8 00 08 47 00 38 e5 00 3d+22:47:36.350 READ DMA ca 00 02 ae 4b 00 e0 00 3d+22:47:36.340 WRITE DMA c8 00 08 a7 4b 00 e0 00 3d+22:47:36.340 READ DMA ca 00 05 92 4a 00 e0 00 3d+22:47:35.160 WRITE 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% 10201 - 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. if this is also ok i will do a new parity check. It shows no re-allocated sectors, nor any pending, but it does show reallocation events. (the sector pending re-allocation was apparently re-written in place) It might be the flaky drive. Since your errors seem to be occasional, it might be involved in the errors you are seeing. Joe L.
February 24, 201115 yr You have a lot of disks in your array. What power supply are you using? Are you using a back-plane based case?
February 24, 201115 yr Author What power supply are you using? 450w single rail CORSAIR Are you using a back-plane based case? no
February 24, 201115 yr Check out this thread: http://lime-technology.com/forum/index.php?topic=10364.0. This person had the same problem and fixed it.
February 26, 201115 yr Author OK after some more md5 checks and no errors it did a new parity check and correct. There i had as suspected the 1488 errors again. After the parity check i did several Parity verifies and guess what... no errors could be found. so i think everything is ok now. I do not know why i had those errors in the first time... anyway, thanks everybody for the help.
February 26, 201115 yr Personally I wouldn't consider anything fine since out of the blue all the errors started happening and now they are gone? Have you moved you machine or added anything in the case? Meaning have you possibly moved any cables?
February 26, 201115 yr Author Personally I wouldn't consider anything fine since out of the blue all the errors started happening and now they are gone? Have you moved you machine or added anything in the case? Meaning have you possibly moved any cables? I have not moved the Server around. And yes, i have checked all the cables. ... I don't Know what else i can do or what else i should do since 3 more parity verifies did Not Show any errors.
Archived
This topic is now archived and is closed to further replies.