sdumas Posted November 30, 2011 Posted November 30, 2011 It's been over 8 days that I am trying to figure this out and bring my array into a somewhat better state. If you want to read the details of what I have done so far you can check it here: http://lime-technology.com/forum/index.php?topic=16859.0 This is a quick summary: I upgraded my standard PC case about three months ago to a Norco 4220. Everything seemed to be running fine until one day I had a drive that red balled. I got another drive and like usual put the drive in and let the machine rebuild the drive. Except that this time it did not work. Not only did it not rebuild the drive but on boot up another one failed as well, and then parity did the same. Too many drives in too little time to be "real" hard drive failures. Looked up the case - verify connectors - backplane - drives in the box and outside the box - did stupid things (rebuild-sb) - and I ended up loosing one drive of data. After a long tedious process - I got my main drives up and running (changed motherboard from Asus P5K-E to a Gigabyte GA-Z68XP-UD3 - upgraded to Beta 14 (onboard SATA controller not recognized by 4.7 - then downgraded to Beta 13 when I suspected other issues) Now I have an unprotected array that works. But it's unprotected. I precleared a new parity drive and installed it in the box. Parity is extremely slow to rebuild (89000+ minutes) and errors now on another drive; ata3- (highly unlikely). I can't have lost 4 drives in the matter of a week. Different brands - different sizes... Running 5.0 Beta 13 Pro - Gigabyte GA-Z68XP-UD3 - i3 processor - 4 GB of RAM - 8 onboard SATA ports - 6 usable (2 onboard controllers 1-Intel Z68 Sata, 2-Marvel 88SE9172) - SuperMicro AOC-SASLP-MV8 and a Sil3132 2 ports SATA controller (PCIe 1x) I unnassigned the parity drive and I am still getting errors on ata3. Here is my latest logs - screenshot of the main menu on following post unraidbeta13lognov302011.zip
dgaschk Posted November 30, 2011 Posted November 30, 2011 Nov 29 20:21:40 HTPCRAID kernel: ata3.00: ATA-8: WDC WD10EARS-00Y5B1, 80.00A80, max UDMA/133 Nov 29 20:21:40 HTPCRAID kernel: ata3.00: 1953525168 sectors, multi 16: LBA48 NCQ (depth 0/32) Nov 29 20:21:40 HTPCRAID kernel: ata3.01: ATA-8: ST32000542AS, CC34, max UDMA/133 Nov 29 20:21:40 HTPCRAID kernel: ata3.01: 3907029168 sectors, multi 16: LBA48 NCQ (depth 0/32) ata3 appears to be the 2-port card.
sdumas Posted November 30, 2011 Author Posted November 30, 2011 I have two of these controllers. I'll switch them to see if it makes a difference.
dgaschk Posted December 1, 2011 Posted December 1, 2011 Can you determine by the drive types which one it is?
JonathanM Posted December 1, 2011 Posted December 1, 2011 In my brief read, I didn't see any mention of your power supply. A flaky supply can make drives drop out, or even cause real hardware failures.
sdumas Posted December 15, 2011 Author Posted December 15, 2011 SOLVED Playing around with many variables - Disks - Controllers - Backplanes - Cables - Motherboard - Power Supply, I could eliminate most of them and it would seem that the Power Supply made the whole difference. I had a 650W (Corsair T650W) and even with the amount of drives I had (11), it would seem that switching to a 1000W PS worked out things. There are still in my mind some issues that are kinda unanswered, but overall it now works and I am happy. As an aside, I also played in the BIOS. Before, I had issues with write performance - 6 to 10 MB/sec - always banged my head on the wall on this, and finally I had the "Duh" moment. My drives were set at Compatibility Mode (IDE) - changed that to AHCI and surprisingly enough - I now get 70MB/Sec writes... Duh.
Recommended Posts
Archived
This topic is now archived and is closed to further replies.