shooga

I've been doing some research, looking for a small case that has 9 5.25" external bays so I can use 5 in 3 cages. I have found several, but keep striking out as they all seem to be discontinued. My requirements are 9 bays and less than 18" tall (which rules out many cases). I prefer simple aluminum and mATX over micro-ITX. Here's what I've found: LIAN LI PC-A17B (discontinued) Sharkoon Rebel9 Aluminum U3 (discontinued) Cooler Master Centurion 590 (out of stock/discontinued) My top choice is the iStarUSA S-919, but it's only build to order (and you probably have to order many). Anyone have any ideas or know of anything out there? I found lots of info on this forum, but most of it is out of date since many of the cases aren't available anymore. Thanks!

Thanks again guys! I ordered the AOC-SASLP-MV8 from eBay. Really appreciate all of the help.

How important is x8 vs x4 for an 8 port card? I just saw that I could get a used AOC-SASLP-MV8 on eBay for $50. That's hardly more than the new Syba and with more ports and more speed.

It's definitely not PCIe, but it's been totally reliable (albeit slowly) for years now. That's why I was asking about an upgrade. The motherboard I have is an Asrock Z77m so I have PCIe x16 slots that I could use. I've been doing a little research and I don't see an obvious card that seems like a unanimous choice. This one looks good on paper, but there isn't much about it on the forums except for one person who says it may not support drives over 3TB.

Thanks for the advice guys! The SATA card I have is a 4 port Silicon Image card from monoprice. Is there a 4 port PCIe card that you'd recommend as an upgrade? The card that itimpi has is a bit overkill for me as I don't have room for 4 more drives in my case. Thanks again!

I have a combination of (2) SATA III, (4) SATA II, and (4) SATA I ports on my motherboard and PCI card. It seems obvious that my cache drive should be on SATA III, but what about the parity drive? Will I get better performance with the parity drive on SATA III? Or is it CPU bound so I should actually just put it on one of the SATA I ports? Maybe I'm over thinking this because the bottleneck is the gigabit ethernet connection? The SATA I ports on are on a PCI card. Is it risky to put the parity drive on a PCI card that could fail? I'm in the process of an upgrade to some of my drives so any advice on how to use this combination of ports would be much appreciated.

Thanks everyone. I forgot that new cleared drives could be added to the array so quickly and without rebuilding parity. I think I will take the approach suggested by lionelhutz. Secondary question: preclearing 6TB drives takes a LONG time. Is it necessary to do two passes? Or can I stop it after the first pass completes? I had hoped to get this done before going out of town, but the preclear is taking about 90 hours per pass.

I'm pre-clearing a couple 6TB drives that I will use to upgrade my parity drive and add more storage to my array. I'd also like to transfer the current parity drive to the array as a storage drive. Is there any problem with doing at all at one time by creating a new config? Parity needs to be recalculated anyway, so I thought I'd cut down on unprotected time by doing it only once. I've read about people changing the parity drive first, recalculating parity, then adding the old parity drive to the array and recalculating. If I were to do just do one drive at a time then wouldn't I have to go through three parity recalculations and have three days or so of being unprotected? Is that really necessary? Thanks!

My solution (working so far) was to remove the drive with the offending files and create a new config. I was without protection while the parity was rebuilding, so there was risk involved. I precleared the drive and added it back to the array and all is well for now. I guess this is really more of a work-around than a solution...

I don't really know what I'm looking for, but I don't see any obvious problems. Here are the results of those commands: root@Bunker:~# lsmod Module Size Used by md_mod 47078 7 xor 11590 1 md_mod sg 13487 0 sata_sil 5391 3 i2c_i801 6466 0 i2c_core 13360 1 i2c_i801 coretemp 4447 0 hwmon 890 1 coretemp ahci 17138 6 libahci 14226 1 ahci r8168 258070 0 root@Bunker:~# ethtool -i eth0 driver: r8168 version: 8.035.00-NAPI firmware-version: bus-info: 0000:02:00.0 root@Bunker:~# ethtool eth0 Settings for eth0: Supported ports: [ TP ] Supported link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Full Supports auto-negotiation: Yes Advertised link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Full Advertised pause frame use: Symmetric Receive-only Advertised auto-negotiation: Yes Speed: 1000Mb/s Duplex: Full Port: Twisted Pair PHYAD: 0 Transceiver: internal Auto-negotiation: on MDI-X: Unknown Supports Wake-on: pumbg Wake-on: g Current message level: 0x00000033 (51) Link detected: yes root@Bunker:~# ifconfig eth0 Link encap:Ethernet HWaddr bc:5f:f4:56:2f:3b inet addr:192.168.1.200 Bcast:192.168.1.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:6793149 errors:0 dropped:44 overruns:0 frame:0 TX packets:9020961 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:2179999548 (2.0 GiB) TX bytes:599997589 (572.2 MiB) Interrupt:41 Base address:0x2000 lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:148058 errors:0 dropped:0 overruns:0 frame:0 TX packets:148058 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:22889979 (21.8 MiB) TX bytes:22889979 (21.8 MiB) root@Bunker:~# ethtool -S eth0 NIC statistics: tx_packets: 9021221 rx_packets: 6793423 tx_errors: 0 rx_errors: 0 rx_missed: 0 align_errors: 0 tx_single_collisions: 0 tx_multi_collisions: 0 unicast: 6716468 broadcast: 46238 multicast: 30717 tx_aborted: 0 tx_underrun: 0

Thanks Jonathanm. I knew there had to be a way, but I'm new to unraid so I didn't even know that new config button was there. I know there's risk involved, but that may be my only solution.

Thanks for the feedback Frank. I'm honestly not sure what to do at this point, so waiting for someone to get back to me is kind of my only option right now The reason I say it's a problem with these specific files is because everything works fine otherwise and the problem is 100% repeatable when I try to delete these files. It's never happened with any other files on that drive.

Does anyone have ideas on how to get rid of these files?

Here's the result of reiserfsck - looks normal: ########### reiserfsck --check started at Sun Mar 17 15:17:05 2013 ########### Replaying journal: Done. Reiserfs journal '/dev/md3' in blocks [18..8211]: 0 transactions replayed Checking internal tree.. finished Comparing bitmaps..finished Checking Semantic tree: finished No corruptions found There are on the filesystem: Leaves 103898 Internal nodes 703 Directories 89339 Other files 387312 Data block pointers 4743264 (2427 of them are zero) Safe links 0 ########### reiserfsck finished at Sun Mar 17 15:35:13 2013 ########### I'm attaching a copy of my syslog from restart to the time where I caused the failure by trying to rm the files. Any help would be greatly appreciated and like I said, if it means losing all the data on the drive I'm fine with that because I have everything I need off of that particular drive. unraid_syslog.zip

I have some files that seem to be corrupt. When I telnet in as root and try to do an ls on the directory or rm the whole thing recursively (or any other file operation on that directory) I just immediately get the message that "Transport endpoint is not connected" and all my shares are dropped. If I stop the array and reboot they come back up and work fine as long as I stay away from the corrupt data. How can I remove the files if the share drops when I try to delete them? Is there another way to deal with this? I have transferred all good data off the drive and was planning to just do a preclear and start over with it (thankfully there wasn't much on it). But then I realized that the parity drive keeps the corrupt data around. Any ideas? UPDATE: My solution (working so far) was to remove the drive with the offending files and create a new config. I was without protection while the parity was rebuilding, so there was risk involved. I precleared the drive and added it back to the array and all is well for now. I guess this is really more of a work-around than a solution...

Actually, it looks like unMenu was incorrectly mapping syslog entries to the cache drive. In this case ata4 is actually a drive that is failing in a way that even I can understand Think I just need to get rid of this old drive that is failing and I should be all good. Thanks again!

Thanks Joe. What happens to those sectors with the errors? Also, can you recommend a guide to this stuff so I can stop bothering people with my newbie questions? Here's the SMART report: === 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: (16980) 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: ( 196) minutes. Conveyance self-test routine recommended polling time: ( 5) minutes. SCT capabilities: (0x3037) 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 179 179 021 Pre-fail Always - 4033 4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 23 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 - 587 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 - 21 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 16 193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 6 194 Temperature_Celsius 0x0022 119 113 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 No self-tests have been logged. [To run self-tests, use: smartctl -t] 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.

Getting these errors over and over again on my cache drive. Can anyone help me understand this? What does this signify? The drive is pretty new, so I'd like to figure out if I should RMA it. Thanks! Mar 6 22:21:24 Bunker kernel: ata4.00: cmd c8/00:08:50:1a:28/00:00:00:00:00/e0 tag 0 dma 4096 in (Drive related) Mar 6 22:21:24 Bunker kernel: ata4.00: status: { DRDY ERR } (Drive related) Mar 6 22:21:24 Bunker kernel: ata4.00: error: { UNC } (Errors) Mar 6 22:21:30 Bunker kernel: ata4.00: configured for UDMA/100 (Drive related) Mar 6 22:21:30 Bunker kernel: ata4: EH complete (Drive related) Mar 6 22:21:33 Bunker kernel: ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 (Errors) Mar 6 22:21:33 Bunker kernel: ata4.00: BMDMA2 stat 0xc0009 (Drive related) Mar 6 22:21:33 Bunker kernel: ata4.00: failed command: READ DMA (Minor Issues) Mar 6 22:21:33 Bunker kernel: ata4.00: cmd c8/00:08:50:1a:28/00:00:00:00:00/e0 tag 0 dma 4096 in (Drive related) Mar 6 22:21:33 Bunker kernel: ata4.00: status: { DRDY ERR } (Drive related) Mar 6 22:21:33 Bunker kernel: ata4.00: error: { UNC } (Errors) Mar 6 22:21:39 Bunker kernel: ata4.00: configured for UDMA/100 (Drive related) Mar 6 22:21:39 Bunker kernel: ata4: EH complete (Drive related) Mar 6 22:21:42 Bunker kernel: ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 (Errors) Mar 6 22:21:42 Bunker kernel: ata4.00: BMDMA2 stat 0xc0009 (Drive related) Mar 6 22:21:42 Bunker kernel: ata4.00: failed command: READ DMA (Minor Issues) Mar 6 22:21:42 Bunker kernel: ata4.00: cmd c8/00:08:50:1a:28/00:00:00:00:00/e0 tag 0 dma 4096 in (Drive related) Mar 6 22:21:42 Bunker kernel: ata4.00: status: { DRDY ERR } (Drive related) Mar 6 22:21:42 Bunker kernel: ata4.00: error: { UNC } (Errors) Mar 6 22:21:48 Bunker kernel: ata4.00: configured for UDMA/100 (Drive related) Mar 6 22:21:48 Bunker kernel: ata4: EH complete (Drive related) Mar 6 22:22:07 Bunker kernel: ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 (Errors) Mar 6 22:22:07 Bunker kernel: ata4.00: BMDMA2 stat 0xc0009 (Drive related) Mar 6 22:22:07 Bunker kernel: ata4.00: failed command: READ DMA (Minor Issues) Mar 6 22:22:07 Bunker kernel: ata4.00: cmd c8/00:08:80:1a:28/00:00:00:00:00/e0 tag 0 dma 4096 in (Drive related) Mar 6 22:22:07 Bunker kernel: ata4.00: status: { DRDY ERR } (Drive related) Mar 6 22:22:07 Bunker kernel: ata4.00: error: { UNC } (Errors) Mar 6 22:22:12 Bunker kernel: ata4.00: configured for UDMA/100 (Drive related) Mar 6 22:22:12 Bunker kernel: ata4: EH complete (Drive related) Mar 6 22:22:15 Bunker kernel: ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 (Errors) Mar 6 22:22:15 Bunker kernel: ata4.00: BMDMA2 stat 0xc0009 (Drive related) Mar 6 22:22:15 Bunker kernel: ata4.00: failed command: READ DMA (Minor Issues) Mar 6 22:22:15 Bunker kernel: ata4.00: cmd c8/00:08:80:1a:28/00:00:00:00:00/e0 tag 0 dma 4096 in (Drive related) Mar 6 22:22:15 Bunker kernel: ata4.00: status: { DRDY ERR } (Drive related) Mar 6 22:22:15 Bunker kernel: ata4.00: error: { UNC } (Errors)

Ok, cool. Thats good news. Thanks Rob!

Ok, good to hear. I'm new to reading SMART results. I was concerned about the End_to_End_Error and Spin_Retry_Count as they are both very close to the threshold.

This is an old drive and I see a couple attributes that are near the threshold. Should it be retired? Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: SMART Attributes Data Structure revision number: 10 Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: Vendor Specific SMART Attributes with Thresholds: Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: 1 Raw_Read_Error_Rate 0x000f 117 099 006 Pre-fail Always - 137310847 Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: 3 Spin_Up_Time 0x0003 096 095 000 Pre-fail Always - 0 Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: 4 Start_Stop_Count 0x0032 100 100 020 Old_age Always - 98 Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: 5 Reallocated_Sector_Ct 0x0033 100 100 036 Pre-fail Always - 0 Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: 7 Seek_Error_Rate 0x000f 075 060 030 Pre-fail Always - 34750361 Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: 9 Power_On_Hours 0x0032 071 071 000 Old_age Always - 26180 Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: 10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0 Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: 12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 48 Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: 184 End-to-End_Error 0x0032 100 100 099 Old_age Always - 0 Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: 187 Reported_Uncorrect 0x0032 100 100 000 Old_age Always - 0 Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: 188 Command_Timeout 0x0032 100 100 000 Old_age Always - 0 Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: 189 High_Fly_Writes 0x003a 056 056 000 Old_age Always - 44 Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: 190 Airflow_Temperature_Cel 0x0022 070 059 045 Old_age Always - 30 (Min/Max 22/33) Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: 194 Temperature_Celsius 0x0022 030 041 000 Old_age Always - 30 (0 19 0 0) Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: 195 Hardware_ECC_Recovered 0x001a 053 048 000 Old_age Always - 137310847 Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: 197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always - 0 Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: 198 Offline_Uncorrectable 0x0010 100 100 000 Old_age Offline - 0 Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: 199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 2 Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: SMART Error Log Version: 1 Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: No Errors Logged Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: SMART Self-test log structure revision number 1 Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: No self-tests have been logged. [To run self-tests, use: smartctl -t] Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: SMART Selective self-test log data structure revision number 1 Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: 1 0 0 Not_testing Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: 2 0 0 Not_testing Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: 3 0 0 Not_testing Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: 4 0 0 Not_testing Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: 5 0 0 Not_testing Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: Selective self-test flags (0x0): Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: After scanning selected spans, do NOT read-scan remainder of disk. Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: If Selective self-test is pending on power-up, resume after 0 minute delay. Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: == Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: ============================================================================ Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: Mar 4 16:27:45 Bunker last message repeated 2 times Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: ============================================================================ Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: == Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: == S.M.A.R.T Final Report for /dev/sda Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: == Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: Disk: /dev/sda Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: smartctl 5.40 2010-10-16 r3189 [i486-slackware-linux-gnu] (local build) Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: === START OF INFORMATION SECTION === Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: Model Family: Seagate Pipeline HD 5900.2 family Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: Device Model: ST31000322CS Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: Serial Number: 9VX0JHEY Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: Firmware Version: SC13 Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: User Capacity: 1,000,204,886,016 bytes Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: Device is: In smartctl database [for details use: -P show] Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: ATA Version is: 8 Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: ATA Standard is: ATA-8-ACS revision 4 Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: Local Time is: Mon Mar 4 16:27:43 2013 PST Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: SMART support is: Available - device has SMART capability. Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: SMART support is: Enabled Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: === START OF READ SMART DATA SECTION === Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: SMART overall-health self-assessment test result: PASSED Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: General SMART Values: Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: Offline data collection status: (0x00)^IOffline data collection activity Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: ^I^I^I^I^Iwas never started. Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: ^I^I^I^I^IAuto Offline Data Collection: Disabled. Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: Self-test execution status: ( 0)^IThe previous self-test routine completed Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: ^I^I^I^I^Iwithout error or no self-test has ever Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: ^I^I^I^I^Ibeen run. Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: Total time to complete Offline Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: data collection: ^I^I ( 633) seconds. Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: Offline data collection Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: capabilities: ^I^I^I (0x73) SMART execute Offline immediate. Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: ^I^I^I^I^IAuto Offline data collection on/off support. Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: ^I^I^I^I^ISuspend Offline collection upon new Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: ^I^I^I^I^Icommand. Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: ^I^I^I^I^INo Offline surface scan supported. Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: ^I^I^I^I^ISelf-test supported. Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: ^I^I^I^I^IConveyance Self-test supported. Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: ^I^I^I^I^ISelective Self-test supported. Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: SMART capabilities: (0x0003)^ISaves SMART data before entering Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: ^I^I^I^I^Ipower-saving mode. Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: ^I^I^I^I^ISupports SMART auto save timer. Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: Error logging capability: (0x01)^IError logging supported. Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: ^I^I^I^I^IGeneral Purpose Logging supported. Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: Short self-test routine Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: recommended polling time: ^I ( 1) minutes. Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: Extended self-test routine Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: recommended polling time: ^I ( 215) minutes. Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: Conveyance self-test routine Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: recommended polling time: ^I ( 2) minutes. Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: SCT capabilities: ^I (0x103b)^ISCT Status supported. Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: ^I^I^I^I^ISCT Error Recovery Control supported. Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: ^I^I^I^I^ISCT Feature Control supported. Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: ^I^I^I^I^ISCT Data Table supported. Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: SMART Attributes Data Structure revision number: 10 Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: Vendor Specific SMART Attributes with Thresholds: Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: 1 Raw_Read_Error_Rate 0x000f 109 099 006 Pre-fail Always - 24025869 Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: 3 Spin_Up_Time 0x0003 096 095 000 Pre-fail Always - 0 Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: 4 Start_Stop_Count 0x0032 100 100 020 Old_age Always - 98 Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: 5 Reallocated_Sector_Ct 0x0033 100 100 036 Pre-fail Always - 0 Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: 7 Seek_Error_Rate 0x000f 075 060 030 Pre-fail Always - 34834273 Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: 9 Power_On_Hours 0x0032 071 071 000 Old_age Always - 26233 Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: 10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0 Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: 12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 48 Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: 184 End-to-End_Error 0x0032 100 100 099 Old_age Always - 0 Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: 187 Reported_Uncorrect 0x0032 100 100 000 Old_age Always - 0 Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: 188 Command_Timeout 0x0032 100 100 000 Old_age Always - 0 Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: 189 High_Fly_Writes 0x003a 056 056 000 Old_age Always - 44 Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: 190 Airflow_Temperature_Cel 0x0022 068 059 045 Old_age Always - 32 (Min/Max 22/33) Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: 194 Temperature_Celsius 0x0022 032 041 000 Old_age Always - 32 (0 19 0 0) Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: 195 Hardware_ECC_Recovered 0x001a 053 048 000 Old_age Always - 24025869 Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: 197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always - 0 Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: 198 Offline_Uncorrectable 0x0010 100 100 000 Old_age Offline - 0 Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: 199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 2 Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: SMART Error Log Version: 1 Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: No Errors Logged

Noticed these errors in my log during preclear. Does this indicate a controller problem? Edit: Realizing that this is actually my cache drive, not one being precleared. Also realizing that I used a cable on the cache drive that may not be compatible with SATAII or SATAIII (it came with a SATAI controller). Could this be the issue? Mar 3 19:09:00 Bunker kernel: ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen Mar 3 19:09:00 Bunker kernel: ata4.00: failed command: WRITE DMA EXT Mar 3 19:09:00 Bunker kernel: ata4.00: cmd 35/00:00:d0:4c:09/00:04:45:00:00/e0 tag 0 dma 524288 out Mar 3 19:09:00 Bunker kernel: res 40/00:00:01:4f:c2/00:00:45:00:00/10 Emask 0x4 (timeout) Mar 3 19:09:00 Bunker kernel: ata4.00: status: { DRDY } Mar 3 19:09:00 Bunker kernel: ata4: hard resetting link Mar 3 19:09:05 Bunker kernel: ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 310) Mar 3 19:09:05 Bunker kernel: ata4.00: configured for UDMA/100 Mar 3 19:09:05 Bunker kernel: ata4: EH complete Mar 3 19:10:18 Bunker kernel: ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen Mar 3 19:10:18 Bunker kernel: ata4.00: failed command: WRITE DMA EXT Mar 3 19:10:18 Bunker kernel: ata4.00: cmd 35/00:00:d0:b4:0a/00:04:45:00:00/e0 tag 0 dma 524288 out Mar 3 19:10:18 Bunker kernel: res 40/00:00:01:4f:c2/00:00:45:00:00/10 Emask 0x4 (timeout) Mar 3 19:10:18 Bunker kernel: ata4.00: status: { DRDY } Mar 3 19:10:18 Bunker kernel: ata4: hard resetting link Mar 3 19:10:23 Bunker kernel: ata4: link is slow to respond, please be patient (ready=-19) Mar 3 19:10:24 Bunker kernel: ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 310) Mar 3 19:10:24 Bunker kernel: ata4.00: configured for UDMA/100 Mar 3 19:10:24 Bunker kernel: ata4: EH complete Mar 3 19:11:08 Bunker kernel: ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen Mar 3 19:11:08 Bunker kernel: ata4.00: failed command: WRITE DMA EXT Mar 3 19:11:08 Bunker kernel: ata4.00: cmd 35/00:00:48:ca:0b/00:04:45:00:00/e0 tag 0 dma 524288 out Mar 3 19:11:08 Bunker kernel: res 40/00:00:01:4f:c2/00:00:45:00:00/10 Emask 0x4 (timeout) Mar 3 19:11:08 Bunker kernel: ata4.00: status: { DRDY } Mar 3 19:11:08 Bunker kernel: ata4: hard resetting link Mar 3 19:11:13 Bunker kernel: ata4: link is slow to respond, please be patient (ready=-19) Mar 3 19:11:18 Bunker kernel: ata4: COMRESET failed (errno=-16) Mar 3 19:11:18 Bunker kernel: ata4: hard resetting link Mar 3 19:11:23 Bunker kernel: ata4: link is slow to respond, please be patient (ready=-19) Mar 3 19:11:28 Bunker kernel: ata4: COMRESET failed (errno=-16) Mar 3 19:11:28 Bunker kernel: ata4: hard resetting link Mar 3 19:11:30 Bunker kernel: ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 310) Mar 3 19:11:30 Bunker kernel: ata4.00: configured for UDMA/100 Mar 3 19:11:30 Bunker kernel: ata4: EH complete Mar 3 19:12:01 Bunker kernel: ata4.00: limiting speed to UDMA/66:PIO4 Mar 3 19:12:01 Bunker kernel: ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen Mar 3 19:12:01 Bunker kernel: ata4.00: failed command: WRITE DMA EXT Mar 3 19:12:01 Bunker kernel: ata4.00: cmd 35/00:00:48:e2:0b/00:04:45:00:00/e0 tag 0 dma 524288 out Mar 3 19:12:01 Bunker kernel: res 40/00:00:01:4f:c2/00:00:45:00:00/10 Emask 0x4 (timeout) Mar 3 19:12:01 Bunker kernel: ata4.00: status: { DRDY } Mar 3 19:12:01 Bunker kernel: ata4: hard resetting link Mar 3 19:12:06 Bunker kernel: ata4: link is slow to respond, please be patient (ready=-19) Mar 3 19:12:11 Bunker kernel: ata4: COMRESET failed (errno=-16) Mar 3 19:12:11 Bunker kernel: ata4: hard resetting link Mar 3 19:12:16 Bunker kernel: ata4: link is slow to respond, please be patient (ready=-19) Mar 3 19:12:21 Bunker kernel: ata4: COMRESET failed (errno=-16) Mar 3 19:12:21 Bunker kernel: ata4: hard resetting link Mar 3 19:12:26 Bunker kernel: ata4: link is slow to respond, please be patient (ready=-19) Mar 3 19:12:56 Bunker kernel: ata4: COMRESET failed (errno=-16) Mar 3 19:12:56 Bunker kernel: ata4: hard resetting link Mar 3 19:13:00 Bunker kernel: ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 310) Mar 3 19:13:02 Bunker kernel: ata4.00: configured for UDMA/66 Mar 3 19:13:02 Bunker kernel: ata4: EH complete

I haven't tie wrapped any cables together...but I'll admit that I was tempted to do that before closing my case. I'll make sure I don't and will re-route SATA cables to spread them out a bit more. I went back and double checked my log and don't see any other CRC errors, so hopefully it's not a power issue. What's the best way to keep an eye on this? Just check the log periodically while using the drives? Should I preclear again with a new cable to test? Do the bad sectors indicate a drive that is nearing end of life? Is it still worth adding these to my array? The SATA controller card is from Monoprice and it's SATA I, so yes it's slow. I think it'll be fast enough for my media streaming and I do have a cache drive to help with write performance. Thanks again for all the info guys. I really appreciate that the unRAID community is so responsive and helpful. I definitely have a lot to learn.

Thanks Rob. Which error indicates the bad cable? These drives are connected via a 4 port SATA card. Could that have something to do with it? (I haven't noticed errors for the other two drives on that card though.)

Thanks for the reply on my slow preclear Joe. I am seeing the following errors: This one is repeated over and over again: Feb 26 21:46:17 Bunker kernel: ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Feb 26 21:46:17 Bunker kernel: ata4.00: BMDMA2 stat 0xd0009 Feb 26 21:46:17 Bunker kernel: ata4.00: failed command: READ DMA Feb 26 21:46:17 Bunker kernel: ata4.00: cmd c8/00:00:20:a2:ed/00:00:00:00:00/e0 tag 0 dma 131072 in Feb 26 21:46:17 Bunker kernel: res 51/40:df:3c:a2:ed/00:00:00:00:00/f0 Emask 0x9 (media error) Feb 26 21:46:17 Bunker kernel: ata4.00: status: { DRDY ERR } Feb 26 21:46:17 Bunker kernel: ata4.00: error: { UNC } Feb 26 21:46:25 Bunker kernel: ata4.00: configured for UDMA/100 Feb 26 21:46:25 Bunker kernel: ata4: EH complete This one shows up less frequently: Feb 26 21:46:39 Bunker kernel: end_request: I/O error, dev sdd, sector 15573615 Feb 26 21:46:39 Bunker kernel: Buffer I/O error on device sdd, logical block 1946701 Feb 26 21:46:39 Bunker kernel: Buffer I/O error on device sdd, logical block 1946702 Feb 26 21:46:39 Bunker kernel: Buffer I/O error on device sdd, logical block 1946703 Feb 26 21:46:39 Bunker kernel: Buffer I/O error on device sdd, logical block 1946704 Feb 26 21:46:39 Bunker kernel: Buffer I/O error on device sdd, logical block 1946705 Feb 26 21:46:39 Bunker kernel: Buffer I/O error on device sdd, logical block 1946706 Feb 26 21:46:39 Bunker kernel: Buffer I/O error on device sdd, logical block 1946707 Feb 26 21:46:39 Bunker kernel: Buffer I/O error on device sdd, logical block 1946708 Feb 26 21:46:39 Bunker kernel: Buffer I/O error on device sdd, logical block 1946709 Feb 26 21:46:39 Bunker kernel: Buffer I/O error on device sdd, logical block 1946710 Strangely though, it looks like later in the log those errors are showing for a different drive: complete Feb 27 16:10:51 Bunker kernel: ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x200000 action 0x0 Feb 27 16:10:51 Bunker kernel: ata2.00: BMDMA2 stat 0x6c0009 Feb 27 16:10:51 Bunker kernel: ata2: SError: { BadCRC } Feb 27 16:10:51 Bunker kernel: ata2.00: failed command: READ DMA Feb 27 16:10:51 Bunker kernel: ata2.00: cmd c8/00:00:e8:10:0a/00:00:00:00:00/e1 tag 0 dma 131072 in Feb 27 16:10:51 Bunker kernel: res 51/40:00:2b:11:0a/00:00:00:00:00/11 Emask 0x9 (media error) Feb 27 16:10:51 Bunker kernel: ata2.00: status: { DRDY ERR } Feb 27 16:10:51 Bunker kernel: ata2.00: error: { UNC } Feb 27 16:10:51 Bunker kernel: ata2.00: configured for UDMA/100 Feb 27 16:10:51 Bunker kernel: ata2: EH complete Feb 27 16:10:54 Bunker kernel: ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x200000 action 0x0 Feb 27 16:10:54 Bunker kernel: ata2.00: BMDMA2 stat 0x6c0009 Feb 27 16:10:54 Bunker kernel: ata2: SError: { BadCRC } Feb 27 16:10:54 Bunker kernel: ata2.00: failed command: READ DMA Feb 27 16:10:54 Bunker kernel: ata2.00: cmd c8/00:00:e8:10:0a/00:00:00:00:00/e1 tag 0 dma 131072 in Feb 27 16:10:54 Bunker kernel: res 51/40:00:2b:11:0a/00:00:00:00:00/11 Emask 0x9 (media error) Feb 27 16:10:54 Bunker kernel: ata2.00: status: { DRDY ERR } Feb 27 16:10:54 Bunker kernel: ata2.00: error: { UNC } Feb 27 16:10:54 Bunker kernel: ata2.00: configured for UDMA/100 Feb 27 16:10:54 Bunker kernel: ata2: EH complete Feb 27 16:10:57 Bunker kernel: ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x200000 action 0x0 Feb 27 16:10:57 Bunker kernel: ata2.00: BMDMA2 stat 0x6c0009 Feb 27 16:10:57 Bunker kernel: ata2: SError: { BadCRC } Feb 27 16:10:57 Bunker kernel: ata2.00: failed command: READ DMA Feb 27 16:10:57 Bunker kernel: ata2.00: cmd c8/00:00:e8:10:0a/00:00:00:00:00/e1 tag 0 dma 131072 in Feb 27 16:10:57 Bunker kernel: res 51/40:00:2b:11:0a/00:00:00:00:00/11 Emask 0x9 (media error) Feb 27 16:10:57 Bunker kernel: ata2.00: status: { DRDY ERR } Feb 27 16:10:57 Bunker kernel: ata2.00: error: { UNC } Feb 27 16:10:57 Bunker kernel: ata2.00: configured for UDMA/100 Feb 27 16:10:57 Bunker kernel: sd 1:0:0:0: [sdb] Unhandled sense code Feb 27 16:10:57 Bunker kernel: sd 1:0:0:0: [sdb] Result: hostbyte=0x00 driverbyte=0x08 Feb 27 16:10:57 Bunker kernel: sd 1:0:0:0: [sdb] Sense Key : 0x3 [current] [descriptor] Feb 27 16:10:57 Bunker kernel: Descriptor sense data with sense descriptors (in hex): Feb 27 16:10:57 Bunker kernel: 72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 00 Feb 27 16:10:57 Bunker kernel: 01 0a 11 2b Feb 27 16:10:57 Bunker kernel: sd 1:0:0:0: [sdb] ASC=0x11 ASCQ=0x4 Feb 27 16:10:57 Bunker kernel: sd 1:0:0:0: [sdb] CDB: cdb[0]=0x28: 28 00 01 0a 10 e8 00 01 00 00 Feb 27 16:10:57 Bunker kernel: end_request: I/O error, dev sdb, sector 17436971 Feb 27 16:10:57 Bunker kernel: Buffer I/O error on device sdb, logical block 2179621 Feb 27 16:10:57 Bunker kernel: Buffer I/O error on device sdb, logical block 2179622 Feb 27 16:10:57 Bunker kernel: Buffer I/O error on device sdb, logical block 2179623 Feb 27 16:10:57 Bunker kernel: Buffer I/O error on device sdb, logical block 2179624 Feb 27 16:10:57 Bunker kernel: Buffer I/O error on device sdb, logical block 2179625 Feb 27 16:10:57 Bunker kernel: Buffer I/O error on device sdb, logical block 2179626 Feb 27 16:10:57 Bunker kernel: Buffer I/O error on device sdb, logical block 2179627 Feb 27 16:10:57 Bunker kernel: Buffer I/O error on device sdb, logical block 2179628 Feb 27 16:10:57 Bunker kernel: Buffer I/O error on device sdb, logical block 2179629 Feb 27 16:10:57 Bunker kernel: ata2: EH complete Feb 27 16:11:00 Bunker kernel: ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x200000 action 0x0 Feb 27 16:11:00 Bunker kernel: ata2.00: BMDMA2 stat 0x6c0009 Feb 27 16:11:00 Bunker kernel: ata2: SError: { BadCRC } Feb 27 16:11:00 Bunker kernel: ata2.00: failed command: READ DMA Feb 27 16:11:00 Bunker kernel: ata2.00: cmd c8/00:08:28:11:0a/00:00:00:00:00/e1 tag 0 dma 4096 in Feb 27 16:11:00 Bunker kernel: res 51/40:00:2b:11:0a/00:00:00:00:00/11 Emask 0x9 (media error) Feb 27 16:11:00 Bunker kernel: ata2.00: status: { DRDY ERR } Feb 27 16:11:00 Bunker kernel: ata2.00: error: { UNC } Feb 27 16:11:00 Bunker kernel: ata2.00: configured for UDMA/100 Feb 27 16:11:00 Bunker kernel: ata2: EH complete Feb 27 16:11:03 Bunker kernel: ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x200000 action 0x0 Feb 27 16:11:03 Bunker kernel: ata2.00: BMDMA2 stat 0x6c0009 Feb 27 16:11:03 Bunker kernel: ata2: SError: { BadCRC } Feb 27 16:11:03 Bunker kernel: ata2.00: failed command: READ DMA Feb 27 16:11:03 Bunker kernel: ata2.00: cmd c8/00:08:28:11:0a/00:00:00:00:00/e1 tag 0 dma 4096 in Feb 27 16:11:03 Bunker kernel: res 51/40:00:2b:11:0a/00:00:00:00:00/11 Emask 0x9 (media error) Feb 27 16:11:03 Bunker kernel: ata2.00: status: { DRDY ERR } Feb 27 16:11:03 Bunker kernel: ata2.00: error: { UNC } Feb 27 16:11:03 Bunker kernel: ata2.00: configured for UDMA/100 Feb 27 16:11:03 Bunker kernel: ata2: EH complete Advice? Are these drives hosed?