July 17, 201411 yr I've been running unRAID fairly error free for about a year and a half but after running out of storage space, I added a 4 bay Sans Digital enclosure (based upon several recommendations posted on here). Since then, I've had three drives give me write failures. First two were both from the same HDD batch, so I thought I just had a couple bad drives. After replacing them with different brands, still had the same errors though...and here I am. The odd thing that I noticed was that after running all drives error free for several days or weeks, the GUI would show errors on 3 drives (with two having identical stats). After restarting, it would only show one as having write errors though. A bit on the specs: Running unRAID Pro 5.0-r16c Mobo: ASRock 880GM-LE FX CPU: AMD Athlon II X2 270 Regor Dual-Core 3.4GHz 3 Norco 5 bay enclosures SUPERMICRO AOC-SASLP-MV8 PCI-Express x4 Low Profile SAS RAID Controller SYBA SY-PCI40010 PCI SATA II (3.0Gb/s) 4 Port RAID 0/1/5/10 JBOD Card SYBA SY-PEX40038 PCI-Express 2.0 SATA III (6.0Gb/s) Controller Card Sans Digital 4 Bay eSATA Port Multiplier JBOD Tower Storage Enclosure Syslog attached and I can get the SMART reports tomorrow if necessary. I'm a bit of a novice at this, so any help is appreciated. syslog.txt
July 18, 201411 yr Author Screencap of the errors during data rebuild. Why does it show errors on 3 discs, but only one is red? Notice how the read numbers are exactly the same for 15, 16, 17 which are the discs in the Sans Digital case.
July 19, 201411 yr Author Smartdisks for the 3 drives at question. Any help? smart15.txt smart16.txt smart17.txt
July 19, 201411 yr Author What do I need to do differently to get some help on this? Are these drives really bad? If so, what is causing them to have these errors, and what do I need to replace?
July 19, 201411 yr Smart reports look fine. I can only guess that the overall cable length from the controller to the disk is too long. I am not familiar with the Sans Digital unit you are using, have have had problems with eSATA enclosures for this exact reason. A shorter cable fixed it for me.
July 20, 201411 yr I recently had to replace my (crappy) drive cages as I was getting random disk errors on random disks. I found the issue after removing all drives from the cages. Once I did that, the drives started behaving as expected. Split-half searching is sometimes the best way to figure it out.
July 20, 201411 yr Author Thanks for the suggestions. I'm glad to know the Hard Drives are ok. I'll try swapping eSATA cables first. I have a 3 foot cable now to try to keep the units and their heat away from each other.
July 21, 201411 yr I have a Rosewill RSV-8 (I think the build is very similar to yours) - and 3 of my friends have it as well. I and one of my friends had issues with the eSATA connector in the back of the case, after replacing the eSATA connectors all the errors went away. I've replace it using this bracket that I got from Amazon (remove the connector from the bracket and careful install it in the back of your Sans Digital case) http://www.amazon.com/KingWin-Esata-Bracket-Cable-ESAC-02/dp/B002TMPWH8/ I can't confirm 100% your problem is the same but that worked for me (my disks had ATA errors showing up in the SMART reports). I think my eSATA cable it's pretty large but it's working fine for me. Good luck and please keep us posted on the results.
September 3, 201411 yr Author Well, I tried the 18" cable and things seemed to go smoothly for about a month. Then the errors started happening again. This time the errors only show up on one drive though, so I'm questioning whether it's the same problem as before. Attached are three smart reports. SDO is the one that is currently showing errors and the report shows UDMA CRC Error count = 4. The wiki says this is caused by bad cables. Is my best option right now to go through the cabling for this drive? smartsdo.txt smartsdn.txt smartsdp.txt
Archived
This topic is now archived and is closed to further replies.