I've had a working 10 drive system for quite some time now with no issues.  I had to upgrade my parity to allow the array to grow into 2TB drives.  This is the second WDC WD20EADS-00S2B0 drive I've tried to use.  In both cases the parity build fails and a DISK_DSBL occurs.  I don't believe the issue is with cable or power, since the new drive is using the old parity drive's connectors. 

 

I still had my old parity drive in the computer, plugged it back in and used the procedures to "trust" the configuration.  The parity check is currently running (a lot longer than the build did using the 2TB drives). 

 

Any help would be greatly appreciated!

 

unRAID 4.5

Linux Movie-Server 2.6.31.6-unRAID #6 SMP Thu Dec 3 10:00:15 MST 2009 i686 Intel(R) Pentium(R) Dual  CPU  E2200  @ 2.20GHz GenuineIntel GNU/Linux

 

preclear output:

===========================================================================
=                unRAID server Pre-Clear disk /dev/sdl
=                       cycle 1 of 1 
= Disk Pre-Clear-Read completed                                 DONE
= Step 1 of 10 - Copying zeros to first 2048k bytes             DONE
= Step 2 of 10 - Copying zeros to remainder of disk to clear it DONE
= Step 3 of 10 - Disk is now cleared from MBR onward.           DONE
= Step 4 of 10 - Clearing MBR bytes for partition 2,3 & 4       DONE
= Step 5 of 10 - Clearing MBR code area                         DONE
= Step 6 of 10 - Setting MBR signature bytes                    DONE
= Step 7 of 10 - Setting partition 1 to precleared state        DONE
= Step 8 of 10 - Notifying kernel we changed the partitioning   DONE
= Step 9 of 10 - Creating the /dev/disk/by* entries             DONE
= Step 10 of 10 - Testing if the clear has been successful.     DONE
= Disk Post-Clear-Read completed                                DONE
Elapsed Time:  29:37:58
============================================================================
==
== Disk /dev/sdl has been successfully precleared
==
============================================================================
S.M.A.R.T. error count differences detected after pre-clear 
note, some 'raw' values may change, but not be an indication of a problem
19,20c19,20
< Offline data collection status:  (0x80)       Offline data collection activity
<                                       was never started.
---
> Offline data collection status:  (0x84)       Offline data collection activity
>                                       was suspended by an interrupting command from host.
54c54
<   1 Raw_Read_Error_Rate     0x002f   100   253   051    Pre-fail  Always       -       0
---
>   1 Raw_Read_Error_Rate     0x002f   200   200   051    Pre-fail  Always       -       0
58c58
<   7 Seek_Error_Rate         0x002e   100   253   000    Old_age   Always       -       0
---
>   7 Seek_Error_Rate         0x002e   200   200   000    Old_age   Always       -       0
63c63
< 193 Load_Cycle_Count        0x0032   200   200   000    Old_age   Always       -       58
---
> 193 Load_Cycle_Count        0x0032   200   200   000    Old_age   Always       -       63 
============================================================================

 

syslog:

May  7 07:07:42 Movie-Server kernel: ata12.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
May  7 07:07:42 Movie-Server kernel: ata12.00: cmd 35/00:00:3f:60:2e/00:04:12:00:00/e0 tag 0 dma 524288 out
May  7 07:07:42 Movie-Server kernel:          res 40/00:ff:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
May  7 07:07:42 Movie-Server kernel: ata12.00: status: { DRDY }
May  7 07:07:42 Movie-Server kernel: ata12: hard resetting link
May  7 07:07:43 Movie-Server kernel: ata12: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
May  7 07:07:43 Movie-Server kernel: ata12.00: configured for UDMA/133
May  7 07:07:43 Movie-Server kernel: ata12.00: device reported invalid CHS sector 0
May  7 07:07:43 Movie-Server kernel: ata12: EH complete
May  7 07:32:59 Movie-Server kernel: ata12.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
May  7 07:32:59 Movie-Server kernel: ata12.00: cmd 35/00:00:3f:2c:b3/00:04:17:00:00/e0 tag 0 dma 524288 out
May  7 07:32:59 Movie-Server kernel:          res 40/00:ff:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
May  7 07:32:59 Movie-Server kernel: ata12.00: status: { DRDY }
May  7 07:32:59 Movie-Server kernel: ata12: hard resetting link
May  7 07:33:09 Movie-Server kernel: ata12: softreset failed (device not ready)
May  7 07:33:09 Movie-Server kernel: ata12: hard resetting link
May  7 07:33:19 Movie-Server kernel: ata12: softreset failed (device not ready)
May  7 07:33:19 Movie-Server kernel: ata12: hard resetting link
May  7 07:33:30 Movie-Server kernel: ata12: link is slow to respond, please be patient (ready=0)
May  7 07:33:54 Movie-Server kernel: ata12: softreset failed (device not ready)
May  7 07:33:54 Movie-Server kernel: ata12: limiting SATA link speed to 1.5 Gbps
May  7 07:33:54 Movie-Server kernel: ata12: hard resetting link
May  7 07:33:59 Movie-Server kernel: ata12: softreset failed (device not ready)
May  7 07:33:59 Movie-Server kernel: ata12: reset failed, giving up
May  7 07:33:59 Movie-Server kernel: ata12.00: disabled
May  7 07:33:59 Movie-Server kernel: ata12.00: device reported invalid CHS sector 0
May  7 07:33:59 Movie-Server kernel: ata12: EH complete
May  7 07:33:59 Movie-Server kernel: sd 12:0:0:0: [sdl] Unhandled error code
May  7 07:33:59 Movie-Server kernel: sd 12:0:0:0: [sdl] Result: hostbyte=0x04 driverbyte=0x00
May  7 07:33:59 Movie-Server kernel: end_request: I/O error, dev sdl, sector 397618239
May  7 07:33:59 Movie-Server kernel: md: disk0 write error
May  7 07:33:59 Movie-Server kernel: handle_stripe write error: 397618176/0, count: 1

syslog.txt

Unfortunately, I had to just give up using this type of drive and switched to Hitachi HDS722020ALA330.