January 8, 201016 yr Hey guys, I'm adding two drives to my unraid system, one is a WD 1TB Green that was my former parity drive, and the other is a WD 1.5TB Green that is new. If someone could take a look at this syslog and let me know if it's normal for it to repeat all that information about the drives over and over while it's clearing I'd appreciate it. First time i've done this. Also hidden in there is this error: Jan 8 14:55:55 Tower emhttp: ... clearing 56% complete Jan 8 15:01:16 Tower emhttp: ... clearing 57% complete Jan 8 15:01:34 Tower kernel: hdc: dma_intr: status=0x51 { DriveReady SeekComplete Error } Jan 8 15:01:34 Tower kernel: hdc: dma_intr: error=0x84 { DriveStatusError BadCRC } Jan 8 15:01:34 Tower kernel: ide: failed opcode was: unknown Jan 8 15:04:57 Tower kernel: md: import disk0: [8,32] (sdc) WDC WD15EADS-00P8B0 WD-WMAVU0931463 offset: 63 size: 1465138552 Jan 8 15:04:57 Tower kernel: md: import disk1: [8,0] (sda) WDC WD10EADS-00L5B1 WD-WCAU45178405 offset: 63 size: 976761496 Jan 8 15:04:57 Tower kernel: md: import disk2: [8,16] (sdb) WDC WD10EADS-00L5B1 WD-WCAU45177770 offset: 63 size: 976761496 Jan 8 15:04:57 Tower kernel: md: import disk3: [8,48] (sdd) WDC WD15EADS-00P8B0 WD-WMAVU1030189 offset: 63 size: 1465138552 Jan 8 15:04:57 Tower kernel: md: disk3 new disk Jan 8 15:04:57 Tower kernel: md: import disk4: [22,0] (hdc) WDC WD10EADS-00L5B1 WD-WCAU45405441 offset: 63 size: 976762552 Jan 8 15:04:57 Tower kernel: md: disk4 new disk Jan 8 15:06:48 Tower emhttp: ... clearing 58% complete Jan 8 15:14:39 Tower emhttp: ... clearing 59% complete It only happened once so I don't know if I should be worried or not... smartctl -a -d ata /dev/hdc (disk4) smartctl version 5.38 [i486-slackware-linux-gnu] Copyright (C) 2002-8 Bruce Allen Home page is http://smartmontools.sourceforge.net/ === START OF INFORMATION SECTION === Device Model: WDC WD10EADS-00L5B1 Serial Number: WD-WCAU45405441 Firmware Version: 01.01A01 User Capacity: 1,000,204,886,016 bytes Device is: Not in smartctl database [for details use: -P showall] ATA Version is: 8 ATA Standard is: Exact ATA specification draft version not indicated Local Time is: Fri Jan 8 17:36:52 2010 Local time zone must be set--see zic m 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: (0x84) Offline data collection activity was suspended by an interrupting command from host. 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: (24000) 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: ( 5) minutes. SCT capabilities: (0x303f) 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 0x002f 200 200 051 Pre-fail Always - 0 3 Spin_Up_Time 0x0027 160 160 021 Pre-fail Always - 6966 4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 312 5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail Always - 0 7 Seek_Error_Rate 0x002e 100 253 000 Old_age Always - 0 9 Power_On_Hours 0x0032 089 089 000 Old_age Always - 8548 10 Spin_Retry_Count 0x0032 100 100 000 Old_age Always - 0 11 Calibration_Retry_Count 0x0032 100 253 000 Old_age Always - 0 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 11 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 4 193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 312 194 Temperature_Celsius 0x0022 122 117 000 Old_age Always - 28 196 Reallocated_Event_Count 0x0032 200 200 000 Old_age Always - 0 197 Current_Pending_Sector 0x0032 200 200 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0030 200 200 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 1 200 Multi_Zone_Error_Rate 0x0008 200 200 000 Old_age Offline - 0 SMART Error Log Version: 1 No Errors Logged 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% 230 - # 2 Short offline Aborted by host 80% 230 - 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. There's the smartcl on that drive... that's the drive that use to be my parity drive and it ran with no errors for about a year. I moved it to a new SATA channel/cable... just don't know if I should be worried here from any of this. It's been doing the clear for about 10 hours now hopefully it'll be done soon and all will be alright. If you guys could let me know if that syslog is alright and how worried i should be over that error I'd appreciate it. Thanks
January 9, 201016 yr Author Alright, the clearing finished and after a format of the new drives the array appears to be up with the new discs added. After that one error there were no further errors in the syslog, nor any when I powered down and started back up. Before today the last time that disc that gave the error was used was when I did a parity check a few nights ago when that drive was still my parity drive before I replaced it. The check went through no problem and like I said it's never given me any errors before. Should I be worried about that lone error it gave me during the cleaning?
January 16, 201016 yr The repeating of the reporting of the import table of the array does seem unnecessary, but is harmless. As far as I know, it only happens when the array is offline and the refresh button is clicked on the web management page, or possibly at set intervals. In the error message, the key word there is BadCRC, which is generally associated with a bad cable if repeated. Your SMART report also notes a UDMA_CRC_Error_Count of one, so it appears you have had a single corrupted packet, not something to worry about. It just means that a packet of data was corrupted in transit, and the corruption was detected on receipt when the calculated CRC did not match the expected CRC transmitted with it. Even the very best cable could possibly have a single CRC error, if for example a cosmic ray or some other random interference caused the alteration of a single bit. If you get any more bad CRC errors, then I would replace the cable. This error does not cause data errors, it just causes the data packet to be resent/retried, so no further issue or concern, nothing to fix. Disclaimer: When I make blanket statements like this, I often feel a little guilty, knowing I have not examined ALL of the code that might possibly be involved. But I tend to have an optimistic view of other programmers, that they will do the perfectly reasonable and logical thing, unless I have any reason whatsoever to doubt them. I feel free therefore to apply common sense to the 'way things work' in computers, until I see evidence of incompetence or carelessness.
Archived
This topic is now archived and is closed to further replies.