Yes, it should work.

 

Thanks for the info.

 

I definitely don't want to just exchange the PS, so if I am able I think I will try to switch to a different brand.

 

http://www.newegg.com/Product/Product.aspx?Item=9SIA1N83V01630&cm_re=evga_power_supply-_-17-438-017-_-Product

 

This is one that I was looking at. Think it will fit the bill?

 

To answer the questions above - I have yet to see any SMART errors, Unraid just disables them. In total I have had this happen 5 different times with 3 different disks in a 3 week time period. It has been just the WD RED drives that have been the issue.

 

One of them has been working great in a Buffalo NAS for about 5 months before it was moved to unraid, the other one was brand new and was RMA'd after the first failure. I then got the replacement that also failed.

 

And then as of last night they both failed .

 

So I can't imagine it is the drives themselves.

 

 

I've seen nothing but good reviews for that model (EVGA G2).

 

My only concern would be that it might be a bit small if you have big plans down the road. It's more than enough for 4 drives, but with the advent of GPU support and VMs, it might be worthwhile going slightly larger, if you have plans in that direction (Or if you plan on adding a bunch more drives down the road).

 

Perhaps someone else can weigh in on requirements to power 1 or more gaming video cards in an UnRaid server?

 

Also, I personally would buy directly from Newegg as opposed to one of their 'vendors'. That's just me though

 

Finally, assuming you can return the first PSU you bought, even if this new one does not solve your problem, rest assured you'll be getting a much more reliable PSU for long term use .

 

Let's hope this fixes your problems!

 
I also can't attach the logs because they are too large, is there something I can pick out of the logs to attach that would be helpful to get around the size restriction? I'm just not having luck with anything.

 

If you are willing to do this, find where the repeating errors begin and select about 100 lines before that point and about 50 lines after that point.  Many of the true experts who can read and interpret system logs says that the entries just prior to the error are often the ones which provide a clue as to the cause of the error.

Here is a partial log if anyone wants to take a look. Sorry I couldn't post the whole thing due to size restrictions even with the zipped file.

 

I am going to go ahead an replace the power supply tonight. I did notice in the bios was reporting 10 volts from from the Power Supply. I'm hoping this was the root cause of all of my issues. I will definitely report back with any updates.

4-7-16_Drive_Failure_Partial_Log.txt

From your syslog excerpt, Disk 2 begins responding strangely at first, then hardly responding at all and is dropped by the kernel (you can ignore all errors after it's disabled).  Errors indicate a DF (Device Fault) and Abrt.  Does seem like flaky power to the drive.

 

Power supply issues were suggested by someone, and seem plausible here.  Power supply problems never raise a clear flag or error saying "it's the PSU's fault!", so we have to guess at it from the failing behavior of other devices, like Disk 2 here.  But I can't say it's definitely the PSU, could also be a bad SATA port or a bad power splitter, or a flaky drive.  But if you reconnect the drive elsewhere and it's fine, then that should rule out the drive and its connectors, leaving the PSU or the original SATA port.

 

Just for curiosity, what is the size of your diagnostics.zip?  And if you look inside it, in the /logs folder, what is the size of the syslog files?

Just got done switching out the Corsair cx750 that was only providing 10V of power. I was able to exchange it at Microcenter and I splurged for a EVGA 220-G2-0650 80 Plus Gold CPU.

 

I am now getting 12V with the new PS. When I booted up one of the drives that was previously disconnected was back and green.

 

I started the array and left disk 2 unassigned, stopped it and then assigned disk 2 and started again. It is rebuilding now.

 

I really hope it was a bad power supply causing me so much grief.

 

 

RobJ - Thanks for the info, the .zip is 2.2 MB, the syslog is 357KB. I suppose I could have posted just that. I haven't been thinking clearly dealing with all of this.

 

I have changed all of the cables, routed them, switched SATA ports on the MB and pretty much anything else I could think of. So I am really hoping the PS does the trick.

RobJ - Thanks for the info, the .zip is 2.2 MB, the syslog is 357KB. I suppose I could have posted just that. I haven't been thinking clearly dealing with all of this.

 

Thanks for answering this!  I've another question, can you look through that diagnostics zip and figure out what is taking up the other 1.9MB?  Besides the syslog, there should normally only be about 100KB or less, usually much less.  It's got me curious!

Oh jeez. i'm glad you were curious.

 

The docker.log is 132MB of this error...

 

g \"****** PLEX MEDIA SERVER CRASHED, CRASH REPORT WRITTEN: /config/Library/Application Support/Plex Media Server/Crash Reports/686be645-efb0-7b88-70f6cc68-25f066df-v-0.9.16.3.1840-cece46d.dmp\" for logger json-file: write /var/lib/docker/containers/ddeaeaaf21e936996fdae46c2820c3001bc476d04f1201801504d0d2515efbf1/ddeaeaaf21e936996fdae46c2820c3001bc476d04f1201801504d0d2515efbf1-json.log: read-only file system"

time="2016-04-07T06:15:19.065845901-04:00" level=error msg="Failed to log msg

 

This looks like it is the same error repeating until....

 

time="2016-04-07T06:19:20.279233619-04:00" level=error msg="Failed to log msg \"****** PLEX MEDIA SERVER CRASHED, CRASH REPORT WRITTEN: /config/Library/Application Support/Plex Media Server/Crash Reports/686be645-efb0-7b88-70f6cc68-25f066df-v-0.9.16.3.1840-cece46d.dmp\" for logger json-file: write /var/lib/docker/containers/

 

I'm hoping all this was after the disk failed and was just the Plex docker getting really mad.

If the Dockers were depending on Disk 2, then that would definitely explain the issues.  And when that docker.log got that big, it filled up /var/log so that no more logging of any kind could happen, causing other bad behavior.

So I think I can call this resolved now. After replacing the brand new Corsair CX750M power supply my issues have gone away. I have been stable for 15 days, previously I always had the issue within 3 to 4 days.

 

There must have been something wrong with it and it wasn't providing enough power to the HD's and causing them to error out and become disconnected.

 

I don't know how to mark this as solved, but I hope it is for good.

 

Thanks for everyone's help/suggestions.

So I think I can call this resolved now. After replacing the brand new Corsair CX750M power supply my issues have gone away. I have been stable for 15 days, previously I always had the issue within 3 to 4 days.

 

There must have been something wrong with it and it wasn't providing enough power to the HD's and causing them to error out and become disconnected.

 

I don't know how to mark this as solved, but I hope it is for good.

 

Thanks for everyone's help/suggestions.

 

Glad to hear the problem is solved! *knocks on wood*

 

Note: I believe you can edit the subject line in your first post with a [solved] or something along those lines, if you wish...