OmegaAvenger
2[H]4U
- Joined
- Sep 25, 2007
- Messages
- 3,240
Anyone?
Install the server 2003 driver from the CD?
Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
Anyone?
Install the server 2003 driver from the CD?
Load the XP driver. It works perfectly.It won't let me says invalid driver for the device. The controller shows up as a Primary IDE Channel in device manager with a yellow exclamation mark saying conflicting resources.
Load the XP driver. It works perfectly.
"The specified location does not contain a compatible software driver for your device. If the location contains a driver, make sure it is designed to work with Windows for 32 bit systems."
This is the classic Windows AHCI/Raid driver behavior. When you first boot and for the first few steps of windows startup, you are using the drivers built into the MB bios. At some point of the process, windows installs its own driver model and starts over. Unfortunately, unless you've done something to get the AHCI drivers loaded then you are SOL, windows will crash and everything starts over. It has nothing at all to do with your SASLP-MV8 controller.
You've got to get the AHCI windows driver loaded. Nothing in the WHS installer makes this easy. In the Vista/7 installer you can do this through the setup UI, in the NT/XP installer you do this through the "F6/floppy" process. Unfortunately, the WHS installer is a two-step process that is part 7 and part XP and it is pretty darn difficult to get the drivers in. The best way to do it is to slipstream it in.
Interesting... When I first setup WHS, I did slipstream the AHCI drivers into the USB. I setup bios for AHCI and booted with single OS drive from USB. WHS installed without any problems. After booting, checked the system and AMD AHCI drive is active and works okay. When I install the SASLP card, system locks up and can't boot into WHS if AHCI is setup in the bios. I can boot without any issues with the SASLP if the bios is set up for IDE. This is totally frustrating!
JB
Strange indeed! Are you still at a place where a re-install is possible? Why not try slipstreaming the Marvell drivers too?
So, I downgraded the SASLP firmware to 3.1.0.15N from 3.1.0.21 and viola! System boots up w/o any problems in AHCI mode and SASLP card installed. The 15N firmware is 1/2 the size or smaller than the 21 firmware.
JB
Where did you find the older version of the firmware? All I can seem to find is the latest 3.1.0.21 version.
G
Whats the new firmware have that the stock one doesn't?
DO NOT update to new firmware. I did it and spend a week trying to find old version to downgrade.
Do you have a link to the old version? I'm going to try updating to the new firmware to see if it fixes a problem i'm having with the hp sas expander. It would be nice to have the old firmware available already in case the new firmware introduces more problems. Thanks.
Found it on the internet:
3.1.0.15 FIRMWARE
http://www.mediafire.com/?xa2b4nsq7zwydbr
Use bootable DOS usb or CD and execute smc-n.bat.
DO NOT update to new firmware. I did it and spend a week trying to find old version to downgrade.
I had no intentions as my cards work fine (minus no smart data for WHS), but I was curious what they added.
That's good news. I just installed 2.6.35 on my system, seems that the mv_abort_task errors and subsequent controller freezes that i got when i was copying files with thunar have disappeared. Now I am trying all the other things that froze the controller, and will report back.
PS. When i am booting my fileserver, I get Port 3 errors from the MV8, and i need to press any key to continue. Everything works ok after that, but thats a PITA for a headless server(That only happens when I have the HP SAS expander connected)
Does this card support port multipliers?
Does this card work under FreeNAS or OpenIndiana?
Sorry to bring up such an old post, but I'm having a similar problem with my HP SAS expander. When my mv8 seems to hang once it gets to the part of detecting the drives attached to the sas expander. The difference between your problem and mine seems to be that this locks up my system, requiring a hard shutdown. The system refuses to boot once it tells me to press any key.
Would you mind telling me how you have your cards connected and, also, whether you have found a fix to this issue?
Thanks.
Unfortunately I have not solved this problem. If I disconnect every single drive from the expander the card boots ok, and then i reconnect them one by one so that the OS sees them.
@golemcito
with new kernels (2.6.38) everything works fine for me. If you have already bought this card then try it, but if you havent then there are some better alternatives around
anyone know where to get a SFF-8087 to 4 angled sata connector?
I read that the max speed on this controller was around 34mbp/s? is that correct?
I was planning on using some 5900rpm 2tb drives, what transfer speed could I expect between the drives?
Slight thread resurrection but I'm having a hell of a time with this card under windows and linux (about to try Solaris ). Drives just drop out all the time, even when they aren't in a bloody raid. Is it because all my HDs are WD Greens? Would I see less drop outs if I I replaced all the drives with Hitachi 3k5 drives?
A green will drop out if it finds a bad sector and spends a few minutes trying to read it before giving up. I used to have a couple of greens drop out at first, but running dd reads or whatever across them for a while (or badblocks if they're not full of data yet) fixed it. Not all of them had sectors they needed to reallocate, though.
This is the point of using the WDTLER tool to change their firmware to act like RAID edition drives, anyway.. so they give up sooner on such sectors. Although that stopped working with EARS I think.. :/
(Note: I don't have this card, but a similar one. MV88SX6081 - PCI-X)
Slight thread resurrection but I'm having a hell of a time with this card under windows and linux (about to try Solaris ). Drives just drop out all the time, even when they aren't in a bloody raid. Is it because all my HDs are WD Greens? Would I see less drop outs if I I replaced all the drives with Hitachi 3k5 drives?