RockDawg

Yes.

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.

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.

That one is 25 amp, right?

What do you think about swapping it with this one as a test? I know it's a cheap no name, but it's a single rail and has more amps. I have one of these in a desktop I could pull to test. http://www.newegg.com/Product/Product.aspx?Item=N82E16817170017

I just received an email from the server that unRaid just red balled my parity drive showing 768 errors. I can't get a SMART report now either: Device: /5:0:0:0 Version: scsiModePageOffset: response length too short, resp_len=47 offset=50 bd_len=46 >> Terminate command early due to bad response to IEC mode page A mandatory SMART command failed: exiting. To continue, add one or more '-T permissive' options..

I'll check it out. Thanks for your help!

Any way to check? I hate to put money into a new PSU and find out that doesn't fix it. The dual rails didnt seem to be a problem before, and I haven't changed anything in 6-8 months.

Here is my PSU: http://www.antec.com/specs/SP500_spe.html The drives do not share a power splitter, but they are on the same cord. Both drives are connected to the onboard SATA.

OK now they I can finally get into the configuration, when I set Boot Support to "disabled" it disables the card altogether. The other options are, enabled BIOS only, enables IS only and enabled BIOS & IS only. EDIT: It turns out that the drives show up in unRaid even though I get the message "adapter disabled by user" during boot. I guess that just means the RAID controller is disabled.

Boy do I feel stupid. Thanks.

I also noticed this: sdf is my parity drive. I'm assuming that I can take it from all this that my parity drive is dying?

OK. I performed a parity rebuild and man it was slow (~33 hrs for my 6.7 TB array), but it found no errors. The parity drive's pending sectors count did increase by one though. Writes are still very slow. In fact the last few times I tried to write a large file, after a few minutes Windows gives me an error saying, "There is a problem accessing \\tower1\disk1\. Make sure you are connected to the network and try again.". I've tried to copy the same file to a couple other disks on the server and the same thing keeps happening. I'm basically unable to write anything even remotely large to my server now. The WebGUI takes a long time to load pages. Sometimes a minute or two. That's not new since the parity rebuild, but has been going on for a little while now. I'm really at a loss now and I have no clue where to go from here. Is the parity drive toast with 4 pending sectors and 0 reallocated sectors? It syas it passed the SMART test. Is the mobo going bad? The server didn't use to be like this and I haven't added anything new to it in quite some time. I've attached a new SMART report for parity and Disk1 along with a syslog. SMART_Disk1.txt SMART_Parity.txt Syslog.txt

I finally go into my board's BIOS config. Removing another SATA controller card I had installed and disabling all onboard HDD controllers didn't fix it either. It wasn't until I removed the flash drive that I was finally able to get in. Anyhow, now I'm a little uncertain because my config screen looks nothing like that one in the OP. It has a Boot Order field, but not a Boot Support field. How do I set this up properly? Here's a pic: IMAG0006 by rockdawg2232, on Flickr

Thanks. I'll try both of those when my server is finished with a parity check.

Anyone have any ideas on how I can get into the config for the card? Would it have anything to do with not having a drive connected? I did the same thing before I flashed the card. I was hoping that might fix the problem. Could this be a sign of a defective card?

I just start a parity rebuild. Just curious, how does that help with the pending sectors?

Thanks for the tip, but unfortunately, it didn't work for me. It just went into the BIOS setting and I never got the LSI configuration utility.

Yah, I know I have old drives in there. I think some are even SATA I. I don't need top notch performance as it's only a media server, but what I'm getting seems really slow. Don't forget that while we all seem to agree that 5-6 MB/s is slow the drive I initially posted about is only getting ~1 MB/s. I see a lot of "configured for UDMA/133" in the syslog. What is that about? I find it hard to read the log in terms of telling if drives are configured for SATA I or II? Also, was there something in the log that told you the Samsung drive is pretty slow or are you just familiar with that drive?

Thanks. I did the same and it seemed to work. I do have a problem where I can't get into the configuration. When it boots, I hit ctrl+C when prompted and it says it's loading the configuration utility, then it says configuration will launch after initialization. Then a line pops up for a split second and, as best I can tell, it says something about boot ROM successfully loaded and then the computer continues booting. The configuration utility never opens. I've tried many times. I don't have any drives connected if that matters (I'm waiting for my cable to arrive).

I bought a IBM ServeRAID M1015 from Ebay and the sticker on it says SAS9220-8i. I've searched, but I don't see that one mentioned in this thread. Which flash procedure should I follow with this card? And what is the difference between the P10 and P11 files?

That's where I get confused. If I keep moving the file around to different drives, doesn't it's location change? Also, I have copied other similarly sized files to the server and I get the same speeds.

I thought that was only a problem if it kept happening. I'll rebuild parity when I get a chance. That wouldn't cause slow write speeds would it (especially to only one drive)?

I'm getting similar speeds when transferring that file from another drive on the server via Midnight Commander. Although, I did that via a telnet session from my Win 7 desktop. That would still rule out a network problem right?

I've been noticing some really slow write speeds when copying files from my Win 7 desktop to my unRAID server disk share. I am copying a 981 MB file and Winodws reports an avg of 900 KB/s. I timed it took 18 minutes and 30 seconds which comes out to 1.13 MB/s by my math. Both computers are using Gbe at full duplex according to Device Manager for the Win desktop and ethtool for the unRaid server. Ping time is <1 ms. between the two computers. Both drives are SATA II and connected to the SATA ports on the mobo. The mobo is a MSI P43 Neo3-F with 3 Gb/s SATA ports. I've changed cables to rule them out and the results are the same. When I try writing the same file to other disks on the server I get 5-6 MB/s. I'm not an expert on this stuff, but isn't that still slow even with parity? I've attached the syslog and SMART reports for both drives below. Does anyone see anything that could be causing this? What kind of speeds should I be seeing? EDIT: AHCI is enabled in BIOS. ParitySMART.txt Disk1SMART.txt Syslog.txt