I see what you're asking. I don't remember what all the drives are. I'll check them tomorrow and do the math. Thanks again.

Looking at his syslog

 

1x 2TB EARS (green)

8x mixed older gas guzzling 7200 rpm drives.

 

that's a bit of a load on that PSU..

It sounds like the Antec PSU is finally giving up and dieing.

 

also, i did not look, but if the ears is the parity drive, it will be  a slow link in his writes.

The 7200 RPM drives are all at the 5400 drive's write limit. (although, i would bet that ears is faster then some of the "older" 7200's)

 

I just went out and bought a Corsair Gaming Series 600W PSU and installed it.  unRaid now shows the parity drive as a new drive.  Should I do a parity sync?  Nothing has been written to the array since the drive was red balled.

Are all other drives showing green?

Yes.

Yes, try to rebuild parity. Hopefully no other disk will have a problem before it's rebuilt.

It's been rebuilding parity for ~21 hours now and it's only 24% done it's been averaging 7 MB/s everytime I look at it.  Shouldn't the speed have increased if the PSU was the sole problem?  Here's a link to the log (too big to attach).  This server is Tower2.

 

http://pastesite.com/30739

 

What's really strange is I have a second unRAID server (Tower1) and it's started acting similarly.  It has a drive that is getting really slow write speeds (5-6 MB/s) and the SMART report again shows some pending sectors ( and zero reallocated.  How common is it to see pending sectors, but non reallocated?  This makes three drives across two servers.  Once again, when I try to write something to this drive from my Win 7 desktop I get the same error as I did on the other server, "There is a problem accessing \\Tower1\disk7. Make sure you are connected to the network and try again".  The SMART report on the parity drive of this system seems OK.  Only disk7 seems to be the problem.  It's showing the following lines in the syslog sometimes:

 

Jan 21 15:51:03 Tower1 kernel: ata9.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
Jan 21 15:51:03 Tower1 kernel: ata9.00: failed command: SMART
Jan 21 15:51:03 Tower1 kernel: ata9.00: cmd b0/d0:01:00:4f:c2/00:00:00:00:00/00 tag 0 pio 512 in
Jan 21 15:51:03 Tower1 kernel: res 40/00:ff:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Jan 21 15:51:03 Tower1 kernel: ata9.00: status: { DRDY }
Jan 21 15:51:03 Tower1 kernel: ata9: hard resetting link
Jan 21 15:51:09 Tower1 kernel: ata9: link is slow to respond, please be patient (ready=0)
Jan 21 15:51:13 Tower1 kernel: ata9: SRST failed (errno=-16)

 

Now I haven't looked and I don't remember what PSU is in this system, but I'm sure it's not up to snuff either as far as being single rail and having enough amps.  But it seems so strange that all this would happen to both servers at the same time. When they've both been running fine for so long.  I appreciate all the help and I'm sorry to require so much of it.  I'm just lost on trying to solve this.

I ran down and bought another Corsair GS600 PSU and replaced the one in the server.  It turns out it is an Antec EarthWattsd 430W.  Dual 12V rails at 14A a piece.    My ignorance strikes again!  Whether or not the PSU was the sole problem in either system, I still feel better knowing I now have proper power to both systems.  I had a spare 2TB drive that had preclearing and it's now finished so I also decided to just pull disk7 and replace it with this new one.  Once everything seems normal on this system I'll run preclear a few times on the drive I took out and see what that tells me.

 

I'm still miffed at the first system.  It's chugging along a parity rebuild at 4 MB/s now.  This could end up taking 3-4 days at this pace.  Is it possible the lack of proper power did irrevocable damage to the drive?

I think I finally got everything sorted out on both systems.  I bought two new hard drives.  They are precleared and installed and parity and data has been rebuilt all seems normal now and I'm getting write speeds ~30 MB/s on both drives.  After I pulled both questionable drives, I ran them both through WD's Data Lifeguard diagnostic software.  They both returned the same results.  They passed the short test and then completed the long test with some bad sectors that needed repaired.  When I instructed it to repair the sectors, both drives failed with a nondescript error message that said there was an error and the repair could not be completed (or something like that).  I RMA'd both drives.

 

I'm still wondering if the power supplies indeed caused this.  Either way, I'm glad I now have good power as it gives me peace of mind.  Anyhow thanks for all the help dgaschk and Johnm!