Actually, another question:  Lots of PCI-E cards will work, albeit with impaired performance, but WORK in a x1 slot.  Anyone with this card tried this? 

 

(It's all I've got for the given build, and it's more than enough bandwidth for me: 250-500 mb/sec)

 

 

 

I've tested AOC-SASLP-MV8 at PCIe X1 slot, I can't estimate the performance impact, but it actually work.

 

How did you get it to fit in a x1 slot?

 

How did you get it to fit in a x1 slot?

I've melted the back of the slot with a soldering iron.

There are no active components in a SAS-SATA cable (reverse or forward); But they are wired differently!!.  The SATA side has different pin locations for The transmit pair and the Receive pair depending on wether it is  a connector on a disk or on a controller/mobo.  ERGO Forward and Reverse breakout cables are not the same and must be used properly for them to work.

 

In my SAS to SATA cable there is an extra connector broken out as a header type connector.  Is this standardized and if so does anyone know what the pinouts are?

Checkout the following website. Has pinouts for the various cables used in SAS/SATA world.

 

http://www.cs-electronics.com/sas-cables.htm

 

Make sure you select the correct host/target (forward) or target/host (reverse cable). 

Is anyone else getting a syslog full of these messages with this card?

 

Apr 28 18:10:47 Tower ata_id[2753]: HDIO_GET_IDENTITY failed for '/dev/block/8:64'

Apr 28 18:10:47 Tower ata_id[2768]: HDIO_GET_IDENTITY failed for '/dev/block/8:48'

Apr 28 18:10:48 Tower ata_id[2814]: HDIO_GET_IDENTITY failed for '/dev/block/8:32'

 

 

There are no active components in a SAS-SATA cable (reverse or forward) so I can't see how they differ in any way except possibly in lead length.  It is just wire.

 

In my SAS to SATA cable there is an extra connector broken as a header type connector.  Is this standardized and if so does anyone know what the pinouts are?

 

sas is electrically differnet to sata.

 

^^ ignore errors, the drivers are immature.

I just picked up this card and of course, now I'm doing my research...  I've been running 4.4.2 for a few years now, very happily.  What version do I need to upgrade to to get this working?

 

Also, once I upgrade, is this basically plug-n-play?  I'm using the supermicro recommended board.  I've got a mix of drives, but I just picked up a couple of the hitachi deskstar 2TB drives that I plan to plug into this card.

 

Thanks,

Chris

4.5.4 is the current release with the corrections for the format problem.  It supports the controller you are interested in.  I use it and the supermicro controller and Hitachi 2TB drives exclusively.  I run 4 ports off the mobo and the rest off the controller card.

Is anyone using two of these in on system AND also using the magic packet to do WOL successfully?

 

When I have just one card installed WOL works as expect however when I install a second SASLP-MV8 card the sytem does not shut down properly. The power goes off but then a couple seconds later it starts back up, just like it received the magic packet. In order to get the system to shutdown and stay shutdown, I have to disable WOL in the BIOS. Of course that means I can't start it up remotely. Kind of a catch 22.

 

Anyway not sure if I should contact the mobo support or Supermicro support. So I was wondering if anyone has this working and if so what mobo you are using?

Is anyone using two of these in on system AND also using the magic packet to do WOL successfully?

 

When I have just one card installed WOL works as expect however when I install a second SASLP-MV8 card the sytem does not shut down properly. The power goes off but then a couple seconds later it starts back up, just like it received the magic packet. In order to get the system to shutdown and stay shutdown, I have to disable WOL in the BIOS. Of course that means I can't start it up remotely. Kind of a catch 22.

 

Anyway not sure if I should contact the mobo support or Supermicro support. So I was wondering if anyone has this working and if so what mobo you are using?

 

This might be a stretch, but here's something to try:

 

When getting wake-on-usb to work correctly on my XBMC frontend, I had to make sure that USB was enabled in /proc/acpi/wakeup.  Maybe you have something enabled in /proc/acpi/wakeup that is causing the machine to be woken up?  I'd do a cat /proc/acpi/wakeup and check for anything that is marked as enabled.  Since you're using WOL, I don't think you'll need anything in there enabled.

Is anyone else getting a syslog full of these messages with this card?

 

Apr 28 18:10:47 Tower ata_id[2753]: HDIO_GET_IDENTITY failed for '/dev/block/8:64'

Apr 28 18:10:47 Tower ata_id[2768]: HDIO_GET_IDENTITY failed for '/dev/block/8:48'

Apr 28 18:10:48 Tower ata_id[2814]: HDIO_GET_IDENTITY failed for '/dev/block/8:32'

 

 

^^ ignore errors, the drivers are immature.

 

Is there any way to suppress them so that the log can become useful once again?

pfp you may want to look at this post.

 

http://lime-technology.com/forum/index.php?topic=6007.0

pfp you may want to look at this post.

 

http://lime-technology.com/forum/index.php?topic=6007.0

 

While the HDIO_GET_IDENTITY messages are there too it would appear that that thread appears to be about these lines in the log:

Apr 13 07:13:30 Unraid unmenu[5991]: WARNING: SetDriveValue(md10, share, Movies [P-S]

Movies [T-Z]) - No drive found

Apr 13 07:13:30 Unraid unmenu[5991]: WARNING: SetDriveValue(md11, share, Movies [T-Z]) - No drive found

Apr 13 07:13:30 Unraid unmenu[5991]: WARNING: SetDriveValue(hdi, usage, "Unprotected" temp files) - No drive found

Apr 13 07:13:30 Unraid unmenu[5991]: WARNING: SetDriveValue(md11, usage, Usage note disk11) - No drive found

Apr 13 07:13:30 Unraid unmenu[5991]: WARNING: SetDriveValue(md10, usage, Usage note disk10) - No drive found

I've found that HDIO_GET_IDENTITY error is an incompatibility between hdparm and the mv_sas driver. Every time unMENU, for example, runs "hdparm -C" to get the drive power status, the error is added to the syslog.

 

I don't know if this can help suppressing syslog messages.

So newbi to unraid here.  But I have two of these cards and the Norco 4220 case.  Can anyone point me in the direction of cables that are a direct hookup for this case?  Thanks so much in advance...

Edit: Looks like I misunderstood RobinSJ, my bad.

Well I have read through the whole thread, and I just read through the first two pages again to look for what you are talking about.  I am not talking about the SFF-8087 Breakout Cables.  I am talking about the cables that are a straight hookup from the card to the backplane of the Norco 4220 Case.  So, thanks for the reply I guess.

These were the cables I am looking at for when I finally take the leap ...

http://www.ncix.com/products/index.php?sku=48800

 

Just building my new SageTV Server and went with the RPC-470 case for that and when I finally get off my butt and decide whether a c-channel or aluminum tubing will be better for the home made server rack ....

 

I'll start in on the move to the RPC-4220 with 2 x  AOC-SASLP-MV8 and 4 cables ...

 

Has anyone built a server with the RPC-4224 case ? and are the temperatures much worse than the RPC-4220?

I am just curious when you say much worse?  That implies not very good tempatures in the 4220.  Have people had High tempatures in it?  I just checked the tempatures of mine, and my drives are at 28C/82F, doesn't seem that bad, or is it?

I've often seen people complaining of poor drive temps in the old Norco 20 bay cases. (on other forums).

I've often seen people complaining of poor drive temps in the old Norco 20 bay cases. (on other forums).

 

There was some punctual problems with faulty backplanes on the 4020 model too, but never see this happen with the 4220. I personally hate backplanes since my two Norcos SS-500 became faulty and I lost 5TB of data from a RAID5 array, but everyone from this forum that use 4220 seem very happy with them. I suggest using or mixing low power drives.

 

OFF TOPIC:

 

Chris Pollard, you have an amazing Lian Li 343-B case, what about posting some pictures to the "Pimp Your Rig" topic?

Hmm I haven't heard of any problems yet, I have had my 4220 case for about a year, man I hope I don't get a faulty backplane.  Are they faulty from the get go, or do they go faulty..... 

Mine became faulty as the 4020 backplane problem I've heard of, but the issue seems related to the SATA connectors in the rear part, where the cables are connected. Since the 4220 uses SFF-8087 connectors, it's certainly less susceptible to this kink of issue.

Looks like the pricing on these is coming down. $113 at ncix.com now, I think it's finally time to order. I'm out of space and sata ports. 

I've found that HDIO_GET_IDENTITY error is an incompatibility between hdparm and the mv_sas driver. Sata PCI-E 4x non-raid controller card.