June 17, 201214 yr My first parity build has failed and the disk is now red-balled and showing DISK_DSBL. I have tried reseating the disk and checked to cable and all seems well. I have attached my syslog below and will also show the results of the SMART test (short). In the meantime, I will swap out the sata cable and try again. Can anyone see what the problem may be? Thanks. smartctl -a -d ata /dev/sdh (parity) smartctl 5.40 2010-10-16 r3189 [i486-slackware-linux-gnu] (local build) Copyright © 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net === START OF INFORMATION SECTION === Device Model: WDC WD30EZRX-00MMMB0 Serial Number: WD-WMAWZ0299781 Firmware Version: 80.00A80 User Capacity: 3,000,592,982,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: Sun Jun 17 10:19:23 2012 BOT 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: (51480) 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: (0x3035) 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 152 148 021 Pre-fail Always - 9400 4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 37 5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail Always - 0 7 Seek_Error_Rate 0x002e 200 200 000 Old_age Always - 0 9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 263 10 Spin_Retry_Count 0x0032 100 253 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 - 33 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 13 193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 84 194 Temperature_Celsius 0x0022 123 110 000 Old_age Always - 29 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 100 253 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0 200 Multi_Zone_Error_Rate 0x0008 100 253 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% 262 - 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. syslog-2012-06-17_shortened.txt
June 18, 201214 yr This indicates a cable or port problem: Jun 16 16:48:17 Aramis kernel: ata1: exception Emask 0x10 SAct 0x0 SErr 0x90202 action 0xe frozen Jun 16 16:48:17 Aramis kernel: ata1: irq_stat 0x00400000, PHY RDY changed Jun 16 16:48:17 Aramis kernel: ata1: SError: { RecovComm Persist PHYRdyChg 10B8B } Jun 16 16:48:17 Aramis kernel: ata1: hard resetting link Jun 16 16:48:18 Aramis kernel: ata1: SATA link down (SStatus 0 SControl 300) Jun 16 16:48:23 Aramis kernel: ata1: hard resetting link Jun 16 16:48:23 Aramis kernel: ata1: SATA link down (SStatus 0 SControl 300) Jun 16 16:48:23 Aramis kernel: ata1: limiting SATA link speed to 1.5 Gbps Jun 16 16:48:28 Aramis kernel: ata1: hard resetting link Jun 16 16:48:29 Aramis emhttp: mdcmd: write: No such device or address Jun 16 16:48:29 Aramis kernel: ata1: SATA link down (SStatus 0 SControl 310) Jun 16 16:48:29 Aramis kernel: ata1.00: disabled Jun 16 16:48:29 Aramis kernel: ata1: EH complete Jun 16 16:48:29 Aramis kernel: ata1.00: detaching (SCSI 0:0:0:0)
June 18, 201214 yr Author I was able to successfully build parity using a 2GB EARS that was in a different slot. The parity build on the 3GB EZRX failed when I tried a different cable, so its looking like it might be the port . I'll test some more scenarios. Are there any other tests I can run on the port?
June 18, 201214 yr You can run pre-clear on a disk connected to the subject port. This should reveal any problems.
June 19, 201214 yr Author So I pulled everything down and I reattached using different cables and different ports. Another failure, but this time i get 'attempt to access beyond end of device'. Any clues? syslog-2012-06-18.txt
June 19, 201214 yr So I pulled everything down and I reattached using different cables and different ports. Another failure, but this time i get 'attempt to access beyond end of device'. Any clues? No, but you might want to bring this to lime-tech's attention. It almost appears to be an off-by-one in that unRAID is attempting to get to a sector one greater than exists.
June 20, 201214 yr Author This is the smart report following the long test. Shows nothing wrong with the drive... Statistics for /dev/sdg WDC_WD30EZRX-00MMMB0_WD-WMAWZ0299781 smartctl -a -d ata /dev/sdg smartctl 5.40 2010-10-16 r3189 [i486-slackware-linux-gnu] (local build) Copyright © 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net === START OF INFORMATION SECTION === Device Model: WDC WD30EZRX-00MMMB0 Serial Number: WD-WMAWZ0299781 Firmware Version: 80.00A80 User Capacity: 3,000,592,982,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: Wed Jun 20 00:05:38 2012 BOT 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: ( 0) The previous self-test routine completed without error or no self-test has ever been run. Total time to complete Offline data collection: (51480) 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: (0x3035) 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 152 148 021 Pre-fail Always - 9400 4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 44 5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail Always - 0 7 Seek_Error_Rate 0x002e 200 200 000 Old_age Always - 0 9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 318 10 Spin_Retry_Count 0x0032 100 253 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 - 38 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 14 193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 262 194 Temperature_Celsius 0x0022 124 110 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 - 0 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 Extended offline Completed without error 00% 314 - # 2 Short offline Completed without error 00% 262 - 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.
June 21, 201214 yr Author It's not the port, not the cable, and the drive has passed both SMART tests. No clue what else to do. Jun 20 22:37:44 Aramis kernel: attempt to access beyond end of device Jun 20 22:37:44 Aramis kernel: sdg1: rw=1, want=4294967296, limit=4294967295 (Drive related) Jun 20 22:37:44 Aramis kernel: attempt to access beyond end of device Jun 20 22:37:44 Aramis kernel: sdg1: rw=1, want=4294967304, limit=4294967295 (Drive related) Jun 20 22:37:44 Aramis kernel: attempt to access beyond end of device Jun 20 22:37:44 Aramis kernel: sdg1: rw=1, want=4294967312, limit=4294967295 (Drive related) Jun 20 22:37:44 Aramis kernel: attempt to access beyond end of device Jun 20 22:37:44 Aramis kernel: md: disk0 write error (Errors) Jun 20 22:37:44 Aramis kernel: sdg1: rw=1, want=4294967320, limit=4294967295 (Drive related) Jun 20 22:37:44 Aramis kernel: handle_stripe write error: 4294967288/0, count: 1 (Errors) Jun 20 22:37:44 Aramis kernel: md: md_do_sync: got signal, exit... (unRAID engine) Jun 20 22:37:44 Aramis kernel: md: disk0 write error (Errors) Jun 20 22:37:44 Aramis kernel: handle_stripe write error: 4294967296/0, count: 1 (Errors) Jun 20 22:37:44 Aramis kernel: md: disk0 write error (Errors) Jun 20 22:37:44 Aramis kernel: handle_stripe write error: 4294967304/0, count: 1 (Errors) Jun 20 22:37:44 Aramis kernel: md: disk0 write error (Errors) Jun 20 22:37:44 Aramis kernel: handle_stripe write error: 4294967312/0, count: 1 (Errors) Jun 20 22:37:44 Aramis kernel: md: recovery thread sync completion status: -4 (unRAID engine) Jun 20 22:37:44 Aramis kernel: md: recovery thread woken up ... (unRAID engine) Jun 20 22:37:44 Aramis kernel: md: recovery thread has nothing to resync (unRAID engine)
June 21, 201214 yr It is the attempt to access beyond the physical disk that is the issue. That is an error when setting up the GPT partition. (and it might be the utility he is using to create the GPT partition, or his calculation of where it should end, but in either case, it is not going to go away until you work with him to resolve the cause) As I suggested, have you sent an e-mail to [email protected] or [email protected] to alert them of this thread? Joe L.
June 21, 201214 yr Author I didn't know if the fact that the partition format was showing GPT 4k-aligned (factory cleared) was a problem or not, but I removed the drive from the array, and then formatted it with the reiserfs using the Disk Management tab in unMenu. When it was done, the partition format was showing GPT 4k-aligned, no more (factory cleared). The parity build worked after that.
June 21, 201214 yr 3TB drives MUST have a GPT partiton. I would not use that drive the way you formatted it. You have set yourself up for massive errors.
June 21, 201214 yr Could I run another preclear cycle on it and then try again? You can. Before you do, what to you see when you click on the disk icon in the unRAID interface. How does it show it is formatted? If it re-wrote the MBR and partitioned the disk correctly, no need to do anything. It should say GPT partitioned... Joe L.
June 22, 201214 yr Author It does. While it was failing, it showed GPT: 4k-aligned (factory-erased). After I did the reiserfs format, the partition format showed GPT: 4k-aligned and I was instantly optimistic. And then the parity build and parity check were successful.
Archived
This topic is now archived and is closed to further replies.