or Connect
AVS › AVS Forum › Video Components › Home Theater Computers › 3tb drives AND supermicro aoc-saslp-mv8
New Posts  All Forums:Forum Nav:

3tb drives AND supermicro aoc-saslp-mv8 - Page 2

post #31 of 60
Quote:
Originally Posted by hatbrox View Post

A few modest comments:

1st gen card (AOC-SASLP-MV8):
Product page:
!!!.supermicro.com/products/accessories/addon/AOC-SAS2LP-MV8.cfm
driver + firmware:
!!!.supermicro.com/driver/SAS/Marvell/MV8/SAS1/
Drivers: V3.1.0.22
firmware: V3.1.0.21

2nd gen card (AOC-SAS2LP-MV8)
Product page:
!!!.supermicro.com/products/accessories/addon/AOC-SAS2LP-MV8.cfm
driver + firmware:
!!!.supermicro.com/driver/SAS/Marvell/MV8/SAS2/
Drivers: V4.0.0.1200
firmware: V4.0.0.1800

Note: It's really confusing what chip on the SAS2 card. you mentioned the 9485 (some firmware files suggest the same name). supermicro says the AOC-SAS2LP-MV8 card has a 9480 chip but they also say it is JBOB only, no RAID. this suggests they use the 9485 chip as the 9480 supports RAID.

Marvell product selector is very useful:
!!!.marvell.com/selector_guide/#
the 88SE6480 is a PCIe x4 to 8 SAS/SATA 3Gb/s Ports RAID Controller
the 88SE6485 is a PCIe x4 to 8 SAS/SATA 3Gb/s Ports I/O Controller

the same logic applies to the 948x
9480 = Raid controller
9485 = I/O controller


with the new card in mind (SAS2), it would be nice to re-confirm if the old one (SAS1) supports 3TB drives and with which firmware/driver

I agree, but there is no guarantee that the mfg (Supermicro) used all the features available of the chipset. It wouldn't be the first time.

That said, the answer to your last comment is Yes (Maybe). See my post above. Maybe with 3 posts now I won't have to butcher URLs anymore?
post #32 of 60
UPDATE:
Quote:
I can now confirm that the Windows_4.0.0.1200.zip driver posted 4/6 with V3.1.0.21 firmware on the AOC-SASLP-MV8 card DOES support the (Hitachi HDS5C3030A630) 3TB drives. The cyclic rebooting has stopped and the drive is usable. I am now testing by filling the drive totally and doing multiple verifications using TeraCopy2.2.
I have completed restoring backup to the Hitachi 3TB drive using the 4.0.0.1200 driver. I have done a through verify, shutdown for 24 hours and re-verify. The AOC-SASLP-MV8 is working albeit slooowly. Hopefully the 4.0.0.1200 driver is a beta and we'll see another in the future. I expected 60-80 MB/s but only saw ~20MB/s. But there were no errors and all files were still accessible after downtime, so the card is working.

My test bed is a Foxconn A7DA-S 3.0 with PhII 1055T running 3.6GHz with 8 GB 1600 DDR3, a Seagate 400 GB IDE boot drive into Window 7x64 Ultimate.
post #33 of 60
UPDATE:

Upon installing the 4.0.0.1200 driver in my server (the intended user of the 3TB drives) I discovered the 2 TB drives were shown as unformatted and Windows offered to format them! I rolled back the driver and the drives returned.
After trying several things I replaced the AOC-SASLP-MV8 with Highpoint 2680 SAS with v 1.1 firmware and 1.5x driver. While the 2680 doesn't play well with other controllers it does allow a mix of 2 TB and 3 TB drives. Speed is comparable at around 70 MB/sec.
NOTE: I am NOT using RAID features.

Server is DFI LanParty LT x48-T3R with 4 GB 1600 DDR3, iQ6600 moving to 50 TB storage.
post #34 of 60
I have bought 3 weeks ago 2 AOC-SAS2LP-MV8.
I've done a lot of data transfer (12 TB to be precise), sometimes having 4x 2TB drives being copied over to 4x 3TB drives. the transfer was done over the 2 HBA.

I never had any bug or issue during the copy. all files were copied with MD5 verification.

most files were from 10 to 30 GB each. Most of the time, I had 90+ MB/S (just under 100 MB/S without MD5 verification)

when moving files between the 3TB drives, it was closer to 110 MB/s (with MD5)

the old server had AOC-SASLP-MV8 cards. But I never liked them. Disk often dropped. the new cards seems to work very very well.... up to a point:

One card won't finish the boot process if there is a HDD detected in ports 3,4,5,7,8. A page (presumably from the MB BIOS) asks me to press the space bar to continue but this won't work. keyboard input is not accepted.

If the suposedly defective card is alone (ie, the other card is physically removed) it will work fine.

If I connect the drive after the boot process, it works again. Very strange.
the motherboard is also from supermicro ( X9SCM-F) They're working on it at the moment. But none of their suggestions has worked so far.

I bet the support engineer wishes I had bought a motherboard of another brand!!!!! now he can't blame the MB maker.

I still hope that eventually it will work.
Their support has been so far supportive and rather prompt to reply and help. At least I deal with serious people.
post #35 of 60
I guess the windows drivers has various issues but I had absolutely no issues using two of these cards to setup a 15x3TB array in raid6 using linux software raid (mdadm). I was able to get about 740 MB/sec read and 270 MB/sec write.
post #36 of 60
Quote:
Originally Posted by Xevious View Post

I guess the windows drivers has various issues but I had absolutely no issues using two of these cards to setup a 15x3TB array in raid6 using linux software raid (mdadm). I was able to get about 740 MB/sec read and 270 MB/sec write.

Can you please indicate which HBA Card you are talking about?
aoc-saslp-mv8
or
aoc-sas2lp-mv8
post #37 of 60
How do you actually update bios firmware?
Where is that kind of option?
What kind of means are you using flopppy, cd-rom? Or you open up a command prompt
I am running Whs v1
post #38 of 60
Quote:
Originally Posted by pettakos View Post

How do you actually update bios firmware?
Where is that kind of option?
What kind of means are you using flopppy, cd-rom? Or you open up a command prompt
I am running Whs v1

Check the manual. A bootable USB flash drive works.
post #39 of 60
Did anybody confirm that the 4.0.0.1200 driver works with the 1. gen card, i.e. AOC-SASLP-MV8 (rather than AOC-SAS2LP-MV8)? Any downsides/stability issues - since it is meant for another chipset...

Do you need to update the bios as well, or can 4.0.0.1200 driver work with 3.1.0.21 bios?

Thanks,
Jacob
post #40 of 60
Confirmed. The 4.0.0.1200 driver works with the Generation 1 / SAS1 Supermicro AOC-SASLP-MV8 (Marvell 64xx series), running firmware 3.1.0.21.

I have 3x 4TB Hitachi drives and two AOC-SASLP-MV8 cards, and it all works fine. I also have 3x 250GB drives on the same card, and they are recognized fine as well.

Using the 3.1.0.22 driver with 3TB or above drives causes an immediate BSOD on inserting the drive, and also if you try to boot with the drive in place.


You cannot download the 4.0.0.1200 driver from Supermicro's FTP site (at least, not as of right now). The 4.0.0.2010 driver on the website is for the Generation 2 / SAS2 card, AOC-SAS2LP-MV8 (Marvell 94xx series).

Also, the 4.0.0.1800 firmware on the Supermicro FTP site is only for the SAS2 card. It cannot (and should not) be installed onto the SAS1 card.

You can have Supermicro support email you the 4.0.0.1200 driver. Or you can download it here: http://www.hdsentinel.com/driver/marvell_64xx_windows_4.0.0.1200.zip

They are the same. I used the one from Hard Disk Sentinel's website, then got the driver from Supermicro support afterwards.
post #41 of 60
Thanks a lot! :-)
post #42 of 60
Is that the same driver that is on the Sonnettech/Tempo site?
post #43 of 60
The Sonnettech driver is different. I would use the one from the Hard Disk Sentinel website, as that is the same as the one Supermicro support emails out.

Note that the AOC-SASLP-MV8 reports all drives with the same UniqueID. This can cause problems in Windows Storage Spaces in the current Windows Server 2012 Release Candidate. See here: http://social.technet.microsoft.com/Forums/en-US/winserver8gen/thread/578a4c17-ed61-4d1a-837b-bdde46f2e7fe
post #44 of 60
On Windows Server 2012 RC, I am getting recurrent STOP 0A (IRQL_NOT_LESS_OR_EQUAL) in partmgr.sys under heavy VM/network/storage load.

I have 3x Hitachi HDS5C404 4TB drives attached to one of my AOC-SASLP-MV8 controllers. They are passed through to a Ubuntu 12.04 Server Hyper-V VM, which is running ZFS on Linux, to give me a ZFS raid-z ZVOL, which is passed back to Windows via iSCSI and formatted as NTFS.

An aside on why I am doing this. This allows me to use a ZFS ZVOL to provide a reliable virtual disk on which to store Windows NTFS volume. I've finally given up on hardware RAID, due to TLER drops on consumer SATA drives, and the lack of end-to-end consistency without checksums, which causes corruption problems when dealing with many TBs of data. Windows Storage Spaces with parity are too slow, hence ZFS. Also I'm using NTFS rather than ReFS as I need DFSR to keep two servers in sync, and ReFS doesn't support DFSR.

The system is more stable when the drives are connected to the motherboard SATA ports instead of the AOC-SASLP-MV8, but it still eventually crashes. I'm not certain if it is the 4.0.0.1200 driver that is causing these problems, or the fact this is the Windows 2012 Server Release Candidate. But there is some stability problem with pass-through disks to a Hyper-V VM.

See here for details: http://social.technet.microsoft.com/Forums/en-US/winserver8gen/thread/cb6fbadb-f2a7-4b4e-904a-ccb1c72f413b
Edited by dtrounce - 6/14/12 at 8:52am
post #45 of 60
Update: the STOP 0A is unrelated to the AOC-SASLP-MV8. I get the same problem with USB attached disks, and also on Server 2008 R2. I have an open case with Microsoft about this. It looks like a bug in pass-through disks to Hyper-V VMs. See http://social.technet.microsoft.com/Forums/en-US/winserver8gen/thread/cb6fbadb-f2a7-4b4e-904a-ccb1c72f413b

Note also that the AOC-SASLP-MV8 reports the same UniqueID for all attached disks. This causes problems with all but one disk being missing in the Server 2012 Storage Spaces UI. See http://social.technet.microsoft.com/Forums/en-US/winserver8gen/thread/578a4c17-ed61-4d1a-837b-bdde46f2e7fe
post #46 of 60
Anyone running it on 64 bit WHS ?
post #47 of 60
Any updates on using the AOC-SASLP-MV8 with win server 2012? If not, is there another card in the same price range that is rock solid? Maybe one of the M1015 units? I have three of the supermicro a and I'm just doing my build, and do not want to regret going with them.
post #48 of 60
Has anyone tried the 3.1.0.23 firmware? It isn't posted on their site but I just had it sent to me. Trying to get release notes...
post #49 of 60
can you please share that new firmware with us please?
post #50 of 60
Quote:
Originally Posted by unstrain View Post

can you please share that new firmware with us please?
Sure. How would you like me to get it to you? I don't have release notes for it, but I just updated and still have the same results...3TB works fine, but no unique ID.
post #51 of 60
Also, does anyone know how to disable the raid option on these cards?
post #52 of 60
I will pm you my email address thanks
post #53 of 60
I could use the firmware too, can you send it to me also?

Thanks!
post #54 of 60
Quote:
Originally Posted by Kamus View Post

I could use the firmware too, can you send it to me also?

Thanks!
PM me your email address
post #55 of 60
Quote:
Originally Posted by Mfusick View Post

Anyone running it on 64 bit WHS ?
I am running a AOC-SASLP-MV8 with WHS 2011 (which is 64 bit), using firmware 3.1.0.21. and the 4.0.0.1200 driver.
It has been stable for a year. I just added a M1015 crossflashed to LSI 9211-8I (IT) firmware, with no rom flashed. They work fine together, so far.

Jacob
post #56 of 60
I'm running WHS2011 with DriveBender and my AOC-SASLP-MV8 is running firmware 3.1.0.21 with driver 4.0.0.1200. I went to the 4.0.0.1200 (from this forum) driver due the fact that 3.1.0.22 would BSOD after a minute. This has been quite stable for me running WD Red 2TB drives, but I'm trying to add my first WD Red 3TB and I can't seem to get the drive recognized by the card. It appears that others have 3TB working in there setups and it looks like I have the same firmware/driver, so I'm at a loss why my WD Red 3TB is not recognized.

Any ideas or suggestions?

Thanks in advance.
Charlie
post #57 of 60
FYI, I'm running WHS 2011 using FlexRaid with this card on firmware 3.1.0.21 and driver 4.0.0.1200. 18TB total and 1 of the drives is a 3TB (Seagate Barracuda.) Had problems with the 3TB on the card so I just used one of the motherboard ports (Gigabyte 945GCM). Not sure if that's an option for your but it's working well for me so far.

Tony
post #58 of 60
My fall back plan was to remove one of the 2TB already attached to the motherboard SATA from the pool via DriveBender and put the 3TB on that connection and move the 2TB to the card. Before I did that, I wanted to give this board a shot to see if anyone could provide other guidance. I'll be in this boat (removing/reattaching) again soon or stuck using 2TB drives on the card.
post #59 of 60
Confirming that this card supports also the 4TB. They are however not seen during boot but not a problem using them from within the booted OS (Linux for example).
post #60 of 60
I've got two of these controllers in my 24-bay unRAID server. I just installed two Seagate 4TB drives in the array, one as the new parity drive and the 2nd as a new data drive and they work fine.

One caveat that may or may not be related is that after I upgraded the firmware on the cards to 0.21 the server takes forever to boot. I turned off the RAID function in the confgiuration files for each card but they both still act as if they're trying to scan the array for a RAID setup. I've jumped through every hoop specified over at the unRAID forums for these cards with no luck.
New Posts  All Forums:Forum Nav:
  Return Home
  Back to Forum: Home Theater Computers
AVS › AVS Forum › Video Components › Home Theater Computers › 3tb drives AND supermicro aoc-saslp-mv8