[pirivan]

Hi all,

This is a bit of a complicated issue which I have done a fair deal of work on up to this point so let me first lay out my WHS hardware setup before I explore the problem and some of the ideas I have tried:

• MSI K9N Platinum AM2 NVIDIA nForce 570 Ultra MCP ATX AMD Motherboard
  
  • AM2 motherboard, NVIDIA chipset, 6 SATA ports, 2 PCI-E X16 slots (the second operates at x1)
  
  
• Two Supermicro AOC-SASLP-MV8 controller cards
  
  • PCI-E x4 cards, these are NOT RAID CONTROLLER CARDS. They are simply for adding more SATA ports
    
  • The first card is placed in the primary x16 slot on the motherboard, the second card is placed in the secondary x16 slot, which for this motherboard, operates at x1 speed if understand the motherboard documentation properly
    
  • These cards have 2 mini-SAS ports on them per card. Each card has a mini-sas to 4x SATA connector going to the case backplane
    
  • This card is based on the Marvell 6480 host controller
    
  • Drivers for these cards were installed from the supplied SuperMicro driver disc
  
  
• Sil3132 PCI-E E-SATA controller
  
  • This card is to connect the linked enclosure however I have NOT done this yet, the card is only installed in the system along with the SIL3132 controller driver
  
  
• Norco 4020 case
  
  • The case has 5 rows of 4 hot swap drive bays (space for a total of 20 drives)
    
  • This is handled internally by having a backplane split into 5 parts. There are 2 pin molex inputs per backplane segment and 4 SATA ports. Thus, for each row of hot swap drive bays you can have 4 drives. 4 drives x 5 rows=20 drives
    
  • Look at the link and view the pictures to get an idea of what I am talking about here
    
  • he first 8 SATA ports on the backplane (top 2 rows in the Norco 4020 case on the backplane and externally) are connected to the first Supermicro AOC-SASLP-MV8 in the primary x16 slot
    
  • The next 8 SATA ports (next 2 rows of hot swap drive bays) are connected to the other Supermicro AOC-SASLP-MV8 controller card
    
  • The final and 5th row of hot swap drive bays are connected to 4 onboard SATA ports on the motherboard I linked above
  
  
• RAM
  
  • 4GB Corsair DDR2 800Mhz
  
  
• CPU
  
  • Athlon 64 X2 Model ADX6400CZBOX – 3.2GHz’
  
  
• Video Card
  
  • Generic PCI video card for a basic display
  
  
• Hard drives
  
  • OS is installed on 1 Western Digital 640GB hard drive, Model# WD6401AALS
    
  • Data is stored on 4 Seagate 1.5TB hard drives, Model # STS31500341AS
    
  • Data is stored on 2 Western Digital 1TB hard drives, Model# WD10EACS-00ZJB0
    
  • I am attempting to add 2 more Western Digital 1TB hard drives, Model# WD10EACS-00ZJB0
  
  
• Physical drive setup in the case
  
  • 640GB OS drive is connected to a motherboard SATA port in an internal hard drive storage area (not hot swap)
    
  • CD RW/DVD drive is connected to another motherboard SATA port
    
  • Top row/first row AND second row of hot swap drive bays are connected to the Supermicro AOC-SASLP-MV8 in the primary PCI-E x16 slot
    
  • I have 4 Seagate 1.5TB drives and 2 Western Digital 1TB 'Green' drives for a total of 6 drives connected
    
  • Third and fourth row of hot swap drive bays are connected to the second Supermicro AOC-SASLP-MV8
    
  • 5th row is connected with SATA cables to 4 onboard SATA ports on the motherboard

POST Order:

1. Motherboard BIOS detects RAM and drives
2. Supermicro AOC-SASLP-MV8 controller POST begins, both controllers detect what drives/how many are detected and spin the drives up one at a time
1. After this is done you can press CTRL M to go into the controller configuration utility
2. The controller utility shows which drives are connected to which controller, these have always been detected properly
3. System sits at a black screen for some amount of time and either sits there forever or waits 3-5 minutes before showing the WHS loading screen (depending on how many drives are connected)

What Is Working Properly:

With the drives in the physical configuration I outlined above (only 6 drives connected) WHS is able to boot although it does so slowly taking 3-5 minutes sitting at a black screen before the WHS loading screen displays. I should also note that when I attempt to power the system down with the shutdown command it does not shut down, it reboots, though this may be an unrelated issue.

What The Issue Is:

The issue arises when I attempt to insert 2 more WD 1TB green drives into the last two hot swap bays on row 2 (the last two available spots on the first controller) OR if I attempt to connect them to ANY of the other hot swap drive bays (the other drive bays being connected from the backplane to the other AOC-SASLP-MV8 controller or 4 of the onboard motherboard SATA ports). Basically, with 6 drives connected in the hot swap drive bays it boots (albeit slowly sitting at the black screen) with 8 drives it never boots at all. It is also worth noting that it appears the server is not 'hard locked' at this point, the monitor does not go to sleep, it acts as if it should be displaying something and is a 'bright black' not the "It's turned off" black. You can also press ctrl + alt + delete at this point and reboot it so it is responding to keyboard presses.

Now, the previous symptom happens if the server is turned off. If I am logged into WHS when I attempt to install 2 additional drives on my first AOC-SASLP-MV8 controller I can see both drives appear in the WHS console briefly and then the entire console locks up and the server becomes completely unstable, forcing me to hard reboot it with the switch on the case. The server then POSTS normally and the AOC-SASLP-MV8 controller detects ALL the drives correctly (including the 2 new additional drives, so it does see 4 1.5TB drives and 4 1TB drives). However, after the controller drive detection, after it spins up all 8 discs, the WHS boot screen never shows up, it just stays at a black screen as when you try to install the drives while the server is turned off. The server will not boot successfully until it is rebooted and the 2 1TB WD I just added to the AOC-SASLP-MV8 controller are removed from the hot swap drive bays.

What I have Tried to Resolve the Issue:

Installing the two 1TB WD drives in the next 'row' of hot swap drive bays, the 3rd row in the Norco 4020 case (ie connecting them to the other Supermicro AOC-SASLP-MV8 controller I have) WHILE WINDOWS HOME SERVER IS RUNNING allows the drives to work properly and does not cause any stability issues within WHS. If I reboot the server with these 2 additional drives connected, 8 drives total connected, 6 on the 1st controller, 2 drives on the second controller it boots to a black screen.

For troubleshooting purposes I have taken ALL 8 drives out of the first two rows and moved them to the 3rd and 4th rows of hot swap drive bays in the Norco 4020 case. Now, they are no longer on the first and second rows of the backplane AND now the drives are connected to the OTHER AOC-SASLP-MV8 controller I have. This was to determine if there was an issue with the first two rows of the backplane or with my first AOC-SASLP-MV8 controller. This test exhibits the exact same symptoms I outlined above. With 8 drives connected it won’t boot into WHS. If I remove 2 it boots without any issues on the other controller.

So, basically what I am saying here is that the controller functions without ANY issues as long as there are only 6 drives connected to it. Connecting 8 to one AOC-SASLP-MV8 controller or 8 to the system total will not allow the Windows Home Server OS to load, it sits at a black screen after the controller POST. Connecting the drives to another controller, so the first AOC-SASLP-MV8 controller only has 6 drives connected, WHILE WHS IS ALREADY BOOTED allows the system to function without any issues (it doesn’t lock up like it might if you put all 8 drives on one controller forcing the hard reboot) but will hang at a black screen if you choose to reboot the system. So far in all configurations I have tried, if I enter the AOC-SASLP-MV8 configuration utility it ALWAYS sees the proper drives connected to the proper controller.

From what I can tell WHS becomes nonbootable with 8 drives connected no matter the configuration. From boot I have had 6 drives on the first controller and the final 2 on either the secondary controller OR the final 2 on the motherboard controller. Either way from boot the system finishes the controller boot screen and then goes to black. Now, I haven't tried swapping drives all over the place yet (4 on one controller, 2 on another, 2 on another etc) to see if I can get the server to be bootable with 8 total. However, I feel like that is defeating the purpose. Even if I got that to work, I want to be able to use ALL 20 available drive bays on the server someday.

So, to recap, so far the ONLY way I have been able to operate the server with 8 drives installed in the following conditions (even then it has the issue when you reboot):

1. Startup WHS with only 6 drives installed in the hot swap drive bays (none of this is counting the 1 OS drive internally). It will sit at a black screen for 3-4 minutes before showing the WHS loading screen.
2. Insert 2 additional hard drives connected to a SEPARATE CONTROLLER from the other 6 after WHS has fully booted. If these are placed on the same controller as the other 6 the server becomes unresponsive and has to be hard rebooted.
3. The 2 additional drives appear to function fine while on the other controller but if the server is rebooted the controllers detect all the drives fine and then it hangs at a black screen prior to the WHS loading screen
4. It is also worth noting that it appears the server is not 'hard locked' at this point, the monitor does not go to sleep, it acts as if it should be displaying something and is a 'bright black' not the "It's turned off" black. You can also press ctrl + alt + delete at this point and reboot it so it is responding to keyboard presses

Potential Solutions?

At this point I am running out of ideas. This afternoon I am going to try booting into WHS, inserting 2 drives on another controller (so that the system doesn’t lock up and then 'add' them to WHS so that they are formatted as backup drives so that they aren't added to the storage pool; I don't want any data placed on them (they are currently full of data that I already migrated over to other drives in the server). I will see if the server is bootable after I do this. I don’t see why it should matter if they have been formatted by WHS or not but I don’t have many other ideas.

I have a ticket open with supermicro but I don't believe they will be able to help me for two reasons. A) All the drives are correctly detected in the controller configuration prior to WHS loading, leading me to think this is a WHS software issue and Their English language skills didn't appear to be top-notch which leads me to wonder how easily they will understand my support ticket. Hopefully they will simply provide me with a different/newer driver or controller BIOS but I have a feeling it won't be that simple. I am particularly doubtful that it is a controller BIOS issue because in the controller configuration utility it sees all the drives properly, even with 8 connected.

I'm contemplating spending the $80 and opening a support ticket with Microsoft but I am not sure how helpful that will be either. I am wondering if there is some issue with my WHS setup anyhow as it takes sitting 3-4 minutes at a black screen before it shows the WHS loading screen even with just the 6 drives installed; this doesn't seem normal either. Also the fact that it reboots when I tell it to shutdown from WHS is concerning.

Several days prior to adding the 2 additional drives I also installed an NVIDIA motherboard utility to enable teaming, along with updated NFORCE drivers. I may try to uninstall the NVIDA drivers and go back with some other motherboard drivers from MSI’s website but I think that's a stretch for a solution to this issue. If this was an issue, why would it work with 6 drives connected but not with 4? It seems like if it was a motherboard driver issue the system wouldn’t work period. Plus, unless I move drives to row 5, only the OS drive and the CD/RW are connected to the motherboard SATA ports.

It’s possible that this is a motherboard BIOS configuration issue, but with 8 drives physically installed, connected to 1 controller card it sees all the drives (as does the controller BIOS). There doesn’t seem to be any options in the BIOS that really relate to this situation though I could be wrong.

I have theSIL3132 PCI-E x1 card in the system was well with 2 e-sata ports. I've tried physically removing that but it didn't appear to make any difference. I will also try to remove the secondary AOC-SASLP-MV8 controller to see if this makes any difference; though as I have mentioned this before it does almost defeat the purpose. However, if it does boot properly with 8 drives connected to one card with the other physically removed at least it might point me to what the issue is.

If anyone else has any suggestions I'm open to hearing them. Please let me know if you require additional details, I have tried my best to be thorough with this complicated issue. I appreciate the time it took anyone to fully read this post, I know it was a long one but I wanted to be detailed.

[wardog (WGS)]

Damn thorough explanation.

The only thing withheld was the PSU. ??

The second AOC-SASLP-MV8, being an x4 functional card, in a x1 functional slot will probably be a no go from the start. Most if not all PCIE cards are "upwardly' compatible, meaning an x1 card might probably work in an x4, x8, or an x16 slot. Unfortunately, the AOC-SASLP-MV8 is designed as an x4 functional meant to operate in an x4 functional at minimum, of which your current MB doesn't have a second x4 available.

Have you attempted this with both the "PCIE Spread Spectrum" and "SATA Spread Spectrum" enabled in the BIOS? I ask this as you say it is repeatable upon using these two "more' HD's on either the SASLP or the MB's nForce controller.

[pirivan]

wardog, on Apr 10 2009, 06:44 PM, said:

Damn thorough explanation.

The only thing withheld was the PSU. ??

The second AOC-SASLP-MV8, being an x4 functional card, in a x1 functional slot will probably be a no go from the start. Most if not all PCIE cards are "upwardly' compatible, meaning an x1 card might probably work in an x4, x8, or an x16 slot. Unfortunately, the AOC-SASLP-MV8 is designed as an x4 functional meant to operate in an x4 functional at minimum, of which your current MB doesn't have a second x4 available.

Have you attempted this with both the "PCIE Spread Spectrum" and "SATA Spread Spectrum" enabled in the BIOS? I ask this as you say it is repeatable upon using these two "more' HD's on either the SASLP or the MB's nForce controller.

Hi Wardog,

Thanks for the reply, I really appreciate you reading through my entire post. I just wanted to make sure I included all the relevant details. I will try to address your points 1 by 1. First, the PSU is:

CORSAIR CMPSU-850TX 850W ATX12V

As far as the card working in an X1 slot, I believe it should actually work just fine. I did some reading into it and it should simple just operate as fast as the X1 bus can go; it shouldn't not function at all. I hate to reference wikipedia but the article here seems to state that it should work fine

Quote

An example is a x8 slot that actually only runs at x1; these slots will allow any x1, x2, x4 or x8 card to be used, though only running at the x1 speed. This type of socket is described as a "x8 (x1 mode)" slot, meaning it physically accepts up to x8 cards but only runs at x1 speed. The advantage gained is that a larger range of PCIe cards can still be used without requiring the motherboard hardware to support the full transfer rate — in so doing keeping design and implementation costs down.

Thus, my x4 controller card should fit in my x16 SIZED slot and it should work fine, only running at x1 speeds (because this secondary x16 SIZED slot is reduced to x1).

Anyhow, I even have evidence to prove that it does work. For example, during some of my trials I moved 6 drives over to the secondary controller (in the x16 slot running at x1 speed) and the server was able to boot. It's simply using 8 drives (between 2 controllers or on any 1 controller) that doesn't work. Either way, the x4 SuperMicro card in the x16 slot doesn't work with 8 drives either. So I think we can rule out any issues with the Supermicro x4 controller in the X1 slot; I think that is fine.

As far as PCIE Spread Spectrum and SATA Spread Spectrum, they were both enabled by default (I am not honestly sure what they do but they are set to enabled).

Also, just to update my post I tried several "ideas" today to no avail. I tried:

• Rolling back the NVIDIA drivers to the original version, pre update; still not able to have 8 drives connected
  
• Uninstalled the NVIDIA Teaming utility; no change
  
• Attempted booting with 8 drives connected without the secondary AOC-SASLP-MV8 Controller in the x1 slot; no change, still not bootable with 8 drives
  
• Booted into WHS with 6 drives connected, inserted an additional 2 drives (the additional 2 drives were connected to the secondary AOC-SASLP-MV8 controller), formatted them as backup drives (wroked fine) and then rebooted. It hung on the reboot at the black screen. So as had happened before, as long as I connect the 2 additional drives to another controller (it locks up if I put them on the same controller as the other 6), while in the OS they function fine and then it hangs on reboot at the black screen before the WHS loading screen.

Now I am REALLY running out of ideas. Barring a driver update provided from SuperMicro (not likely) all I can think of is:

1. Trying to reinstall WHS without losing any of the data on my drives (not sure how to do this)
2. Start a Microsoft WHS support call (not sure what they could tell me really)
3. Start migrating all my data off of the WHS slowly to another PC and then move to a server 2003, server 2008 platform etc (maybe use DFS?)

[wardog (WGS)]

pirivan, on Apr 10 2009, 10:57 PM, said:

1. Trying to reinstall WHS without losing any of the data on my drives (not sure how to do this)

Using the WHS installation DVD you want to do a "Server Reinstall'. This will keep your data 'intact' but you'll need to reinstall any add-ins and also add your Users and their permissions back.

I'm going to finish reading your [H] posts concerning this.

[pirivan]

wardog, on Apr 10 2009, 08:53 PM, said:

Using the WHS installation DVD you want to do a "Server Reinstall'. This will keep your data 'intact' but you'll need to reinstall any add-ins and also add your Users and their permissions back.

I'm going to finish reading your [H] posts concerning this.

Well based on what you had said previously I looked into PCI-E Spread Spectrum and SATA Spectrum. And I found this page that lead me to believe that it might assist me to turn these OFF

Quote

However, spread spectrum clocking can interfere with the operation of timing-critical devices like clock-sensitive SCSI devices. If you are using such devices on the PCI Express interconnect, you must disable this feature.

So, this is where it gets complicated (I know I am leaving out some details unfortunately as I have just haphazardly been trying to troubleshoot his and wasn't taking notes so I am missing some information and this might be slightly out of order). So I disabled these with 8 drives inserted, 6 on the primary SuperMicro controller, 2 on the other. And lo and behold the server booted; I was amazed. It didn't even appear to have a delay showing the WHS loading screen. So, excitedly I shut down the server and placed the 2 drives on the primary controller. Unfortunately this didn't work and I got the blank screen again. So, thinking this might also help in the same error as the other spread spectrum options is "CPU/LDT Spread Spectrum" which is set to "Center Spread". I set this to disabled thinking this might help.

However, as soon as I did this I ran into other issues. The super micro controllers would run their configuration and then instead of a blank screen the 'blue' light on the monitor would turn to amber, indicating it was getting no signal (this had never happened before). So I immediately rebooted and tried to get into the BIOS and found that I could not; no display, just the amber light.

So, I was forced to use the reset CMOS button. This worked and the BIOS was accessible again. However, as soon as I did this on boot I was greeted with the message:

“No enough space to copy PCI option rom [05:00:00]”
“No enough space to copy PCI option rom [04:00:00]”
And some error about wanting to load CMOS failsafe defaults and that there is no floppy drive

I had seen the same PCI option ROM error in this server before so I looked up what the situation and solution was then that I had posted on a forum a few days back:

Quote

Removing the drives from the hot swap drive bays allows the PC to boot normally. I also have a Sil3232 eSata controller card (I may use this card in the future to connect 2 of the 5 bay eSata AMS enclosures I have). If I remove this Sil3232 card I can leave the hard drives in and the PC boots normally. So, as I have determined that the Sil3232 controller card is the issue. The solution turned out that I had to boot into WHS without any drives connected to the SuperMicro cards and flash the firmware on the Sil3232 card to a different version (I forget which firmware finally allowed this for me). I haven't yet tested if the 5-bay AMS e-sata enclosures works with this firmware but I assume that they will.

So, knowing this I immediately shut off the server, removed the SIL3232 PCI-E x1 card and disabled the floppy drive and controller in the BIOS (as I don't have a floppy drive). This removed both of these messages on boot.

So then, on a subsequent reboot (this is all still with 8 drives in the bays, 6 on 1 super micro controller 2 on the other) after running the controller configuration I got some graphical corruption, vertical and horizontal lines on the display and had to reboot. Changing the graphics card order from PCI-E to PCI first seemed to fix this and now it is back to booting to a black screen with 8 drives installed SOME of the time.

I disabled the PCI-E spread spectrum and SATA spread spectrum again and I was just now (as in 2 minutes ago) able to get it to boot into WHS with 6 drives on the primary super micro controller 2 on the secondary, as I did before. HOWEVER, I then tried to shut down the server, changing nothing and it rebooted (as it has done in the past, issuing a shutdown reboots it) and it booted to a black screen again. I can't seem to get it to behave consistently.

[pirivan]

Well, in case anyone is interested I thought I might update this thread just a bit. It has been a long couple of days working on this and I haven't been taking notes so I will do my best to summarize my findings (I have forgotten all that I have tried by now anyhow). Basically, I think that Wardog was on to the right train of thought here. I think there IS some sort of IRQ/PCI/motherboard ROM resource/other motherboard related issue going on. I can't seem to get it to behave consistently while posting. Through numerous CMOS resets, disabling items in the BIOS, removing and reinserting PCI video cards I have seen a variety of POST errors and I can only RARELY get it to POST properly with 8 drives (as long as 2 are on a secondary controller).

Based on the advice of Wardog I've experimented a bit with disabling PCI-E Spread Spectrum and SATA Spread Spectrum. I can think of at least one time where after I disabled these, with 8 drives inserted (6 on one controller 2 on another) it rapid booted no problem. Excitedly I shut it down and placed them all on 1 controller; no dice.

Also I've seen a few times (based on resetting the CMOS usually):

No enough space to copy PCI option rom [05:00:00]”
“No enough space to copy PCI option rom [04:00:00]”
And some error about wanting to load CMOS failsafe defaults and that there is no floppy drive

Occasionally I have seen some graphical errors when attempting to boot and I have a feeling that the PCI video card is causing some of these issues, unfortunately if I remove it the machine doesn't boot. My guess is that it is sitting at a POST screen with some error that says "Press F1" or F11 to continue. I've also tried moving the PCI video card around to various PCI slots to no avail. I've put a solid 10 hours or so into this problem over the last few days and no matter what I can't get it to work with 8 drives consistently. Also, even when it DOES boot properly with 6 inserted it still hangs on the black screen before booting into WHS for FAR too long.

On another forum a user had this insight, which I believe does directly relate to my issue, but I was unable to move cards around to make this solution work for me:

Quote

I had a very similar symptom but with, of course, a completely different system. I had two Sil3114 PCI Sata cards and the more drives I added to them the longer and longer it sat on the black screen until finally it around 6 or 7, it would never boot at all. I also had an PCI 4 port IDE card (sil0680a) I only had 4 PCI slots, so I had them lined up sil3144, sil3144, sil0680a, empty.

I think there was some sort of channel interference, because when I lined them up, sil3144, sil0680a, sil3144, empty - it recognized all drives quickly and proceeded to a rapid boot.

This may or may not be your issue, but the symptoms were so similar, I thought I'd share my experience.

So, like any true American consumer I've given up and have decided to throw some money into the issue. I ordered a replacement motherboard and CPU from newegg instead. This time with several features to combat possible issues:

1. The motherboard has onboard graphics, so no need to use the PCI graphics card
2. The motherboard has 3 x PCI Express x16 (dual x16 or triple x8), instead of 1 PCI-E x16 slot and another PCI-E x16 that runs at x1. At first I was only interested in TWO PCI-E x16 slots but I decided that there was a potential that using my onboard SATA ports was also contributing to the issue. So, this way, with 3 slots, if I need to migrate away from the onboard SATA ports I can buy a third AOC-SASLP-MV8 controller card and place an additional 4 drives on it. So that ALL of the 20 hard drives are off the motherboard controller. Heck, I could place the boot disk on controller as well and fully disbale the motherboard ports
4. The CPU I ordered is a 45W AMD dual core CPU. Hopefully, this might reduce any power issues I might be encountering. However. the PSU is a 850W Corsair, so in all honestly I doubt this is poart of the issue.

Hopefully I will be able to migrate to the new motherboard and CPU without requiring a WHS reinstall. I have been able to do this in the past (as in 2 weeks ago) with both a Windows XP and Windows Vista system.

The CPU and motherboard I ordered are:

ASUS M3N-HT Deluxe/HDMI AM2+/AM2 NVIDIA nForce 780a SLI HDMI ATX AMD Motherboard
AMD Athlon 64 X2 5050e Brisbane 2.6GHz 2 x 512KB L2 Cache Socket AM2 45W Dual-Core Processor


It was incredibly difficult to find an AMD AM2/AM2+ motherboard that was:

1. A decent price
2. Had 3 or 4 PCI-E slots
3. 6 SATA ports
4. Onboard video
5. Potentially dual NIC's (I gave up on this)

I considered Foxconn Destroyer AM2+/AM2 NVIDIA nForce 780a SLI ATX AMD Motherboard for quite a while but ultimately I decided that I didn't like that it had 2 motherboard ports that REQUIRED you to use AHCI to use them. I liked that it had quad PCI-E and Dual NIC's but I thought I might run into some issues in the future if I had SATA ports that required the use of AHCI. I wasn't sure but at this point I felt like this motherboard and the one I chose were fairly equivalent anyhow. I also looked at a few options from both MSI and DFI that had all the features I wanted but lacked onboard video. Due to all the issues I had had with the PCI video card (potentially) I decided this was a deal breaker for me and looked at other options.

I wasn't thrilled with either Foxxcon OR ASUS's support and RMA track record but I couldn't find many better options. As I said before, it was incredibly hard finding a motherboard that had all these features (at least 3 PCI-E ports really narrowed the selection but I REALLY wanted the option to have a 3rd AOC-SASLP-MV8 controller if everything fell through).

[texterted]

Maybe you are running out of IRQ's? Try setting "Plug and Play" aware OS to "No" in the bios and disable any LPT and serial ports that you don't need etc.

[pirivan]

texterted, on Apr 12 2009, 10:57 PM, said:

Maybe you are running out of IRQ's? Try setting "Plug and Play" aware OS to "No" in the bios and disable any LPT and serial ports that you don't need etc.

Good suggestion. I should have mentioned I did try that as well. Following are disabled:

1394 controller
Audio controller
Onboard Floppy
Com Port 1
IR Function
Parallel
PC IDE Busmaster
On-Chip IDE Controller

All the PCI IRQ's are currently set to auto (I wouldn't have a clue where to start manually setting vlaues here) and the PCI Latency Timer is set to 64 (I tried setting this to lowest and highest value, didn't seem to matter).

Unfortunately I didn't see "Plug and Play Aware OS" anywhere in this BIOS; I have seen it on others but it looks like its not an option here.

[wardog (WGS)]

pirivan, on Apr 13 2009, 02:14 AM, said:

Unfortunately I didn't see "Plug and Play Aware OS" anywhere in this BIOS; I have seen it on others but it looks like its not an option here.

According to the M3N-HD Deluxe manual online at Asus:

BIOS Menu > Advanced > PCIPnP > Plug & Play OS > default is NO

[pirivan]

wardog, on Apr 13 2009, 01:42 AM, said:

According to the M3N-HD Deluxe manual online at Asus:

BIOS Menu > Advanced > PCIPnP > Plug & Play OS > default is NO

Oh that is good to know; hopefully the new motherboard will have a few new options to try and perhaps will just work out of the box with more than 6 drives. I couldn't find much information that would tell me that one way or another as this is a pretty specific issue. Hopefully I won't need to reinstall WHS to upgrade to the new OS as I am concerned with keeping my data intact. However, if the new motherboard doesn't cure the issues anyhow I suppose I am looking at an OS reinstall as a troubleshooting step anyhow!

[wardog (WGS)]

Hey pirivan,

If the new MB is of a different or otherwise incompatible chipset for the drivers installed on the HD currently I'd venture a reinstall would be needed.

Keep us posted pleased.


.. wardog

Edit: Just noted you're going from a 570 to 780 board.

[pirivan]

wardog, on Apr 13 2009, 08:32 AM, said:

Hey pirivan,

If the new MB is of a different or otherwise incompatible chipset for the drivers installed on the HD currently I'd venture a reinstall would be needed.

Keep us posted pleased.


.. wardog

Edit: Just noted you're going from a 570 to 780 board.

My plan is to uninstall any of the installed motherboard/graphics card drivers (via add/remove), power down the server and install the new hardware (motherboard/CPU). Prior to a couple of weeks ago I would have felt pretty nervous about doing this. However, I was able to take a Vista installation AND an XP installation and migrate them both to completely different hardware (the XP installation went from AMD/Nvidia chipset -> Intel platform). I had intended to use Acronis to image the XP system but after the image was taken and the new hardware was installed I accidentally bumped the power button and was shocked to see that it booted without any issues, besides some obvious 'found new hardware' popups. I reinstalled drivers, reactivated Windows and then removed hidden nonpresent devices; 0 issues. I am expecting/hoping WHS is the same way. I may take an image of the C: drive anyhow just to be safe.

I've looked around a fair amount and it seems like the suggestion whenever someone wants to do this is the 'data migration' solution. Which is basically, slowly move all data off of the WHS data drives to other hard drives, then once this is done, reinstall WHS, move the drives back, reformat, copy data back. To be honest, I'd like to avoid this. The only spare 'empty' drives I have are 1TB drives and the biggest in the server are 1.5TB. I am hoping to just slip the motherboard and CPU in instead and reinstall some drivers. If this fails I may try to do the repair/WHS reinstall, where it locates the tombstones on all of the data drives (this seems to be less documented and people tend to not recommend doing this for some reason).

[pirivan]

Argh frustrating. After very carefully reading the PDF manual of the motherboard I chose it turns out that it as well has two ports on it that utilize AHCI mode and can't run in IDE (4 can run in IDE). As I installed WHS originally using IDE mode I am going to have to place the OS drive on the IDE mode SATA ports along with the CD/DVDRW drive. That means that 2 ports on the backplane will then be on IDE mode, 2 on AHCI. I am not sure how WHS will handle this if I plug a drive into a hot swap bay on the backplane that is in AHCI mode. I assume that as long as I supply WHS with some drivers it will be able to interact with the drive without any issues (being as it isn't an OS/boot drive anyhow)?

I guess in the end I could have gone with the other motherboard as well (the Foxxconn) as my primary reason for not choosing it turns out to apply to this motherboard as well; argh.

[pirivan]

Based on the suggestion of a user from another forum who has the same AOC-SASLP-MV8 controller cards and encountered a similiar issue he suggested that I disable INT13H in the controller card BIOS. Unfortunately it doesn't look like that works for this issue. I was very excited when I read the post and went to try it right away. However, even after disabling INT13H on both AOC-SASLP-MV8 controllers it still boots to a black screen. Though, it did, slightly, fix another issue. That other issue being that when I have both controllers in and the server filled with 8 drives on the first controller, I can't select my 640GB hard drive as a bootable drive option. The BIOS boot drive select screen only lists the 8 hard drives on the first controller; none of the onboard ports as selectable boot devices. When I disabled INT 13h I was able to select hard drives connected to the motherboard as boot devices without any of the drives on the AOC-SASLP-MV8 controller showing up as bootable devices in the motherboard BIOS. However, even this small fix doesn't appear to be completely repeatable. Sometimes, disabling INT13H still doesn't allow me to select my 640GB drive as a bootable device. It prevents listing the AOC-SASLP-MV8 primary controller devices as bootable but then only lists SOME of the drives connected to the onboard ports, not the 640GB drive.

I should also note that I did get the new motherboard I linked above installed and WHS reinstalled with the SATA ports set to AHCI (I slipstreamed the AHCI drivers onto a flash drive to do the WHS install):

ASUS M3N-HT Deluxe/HDMI AM2+/AM2 NVIDIA nForce 780a SLI HDMI ATX AMD Motherboard

However, of course this did not resolve the issue it just changed what the issue is slightly. Here are the differences between the issue now and when I had the previous motherboard:

1. It now shows the WHS loading splash screen and then boots to black, with the prior motherboard it would simply go to black after posting without showing the WHS loading screen
2. The controllers detect drives much quicker, it used to be that there would be 4-5 .... periods before it moved to detecting the next drivem now there is only 1
3. When WHS is booted (only workable when I have only 4-6 drives inserted) the machine obeys shut down commands normally; on the previous motherboard if you told it to shut down it would reboot
4. I was able to get the machine to boot into WHS ONCE with 6 drives on the first controller, 3 on the onboad ports (not counting the OS drive also on onboard) AFTER I DISABLED SATA SPREAD SPECTRUM. However, I am unable to replicate this. Currently even with 6 on the primary, 3 on the secondary, sata spread spectrum disabled it still doesn't seem to work.

I've tried many different combinations of things at this point. I've tried moving around the AOC-SASLP-MV8 controllers to different PCI-E slots, I tried disabling all the onboard SATA ports and moving the boot drive to the AOC-SASLP-MV8 controller (this made it easier to select the OS drive as a bootable device), various settings with INT13H disabled, various settings with PCI-E spread spectrum enabled and disabled, various settings with SATA spread sprectrum enabled or disabled. I've tried a variety of settings with only just one controller card installed. The net result seems to be that no matter what now it shows the WHS loading splash screen and then goes to a black screen as long as there is 8 or more drives installed. I have to imagine there is some secret combination of motherboard BIOS settings that will allow this to work, I just can't seem to find it. It may be that I have to do something with setting IRQ's but I wouldn't have the foggiest idea of how to start with that.

I have to say I am just a tad more than slightly agitated at this point; it's difficult when it doesn't SEEM to follow any pattern. I may try to reinstall the OS with INT13H disabled on both controllers and if that doesn't work try another OS reinstall with the boot drive connected to the controllers and the motherboard ports disabled (I will probably have to slipstream AOC-SASLP-MV8 drives into the WHS install if I do this).

[pirivan]

I decided to reinstall WHS again and take a few notes this time.

BIOS Setup Prior to OS Installation:

1. Basically disabled anything I don't use (audio, HDMI, COM ports, serial ports, IDE drives etc)
2. Set SATA devices to AHCI mode
3. SATA spread spectrum and PCI-E Spread Spectrum are both set to disabled
4. In the AOC-SASLP-MV8 controller card BIOS BOTH card are set to have int13h disabled
5. In the motherboard BIOS (with int13h disabled on the controller cards) on the list to select bootable hard drive priorities ONLY the hard drives connected to the internal SATA controller are listed as options and I correctly placed the 640GB drive at the top of the list

Reinstalled WHS

1. Reinstalled WHS via a flash drive that has AHCI drivers for my motherboard SATA ports slipstreamed in
2. While the install was taking place there were 7 disks on the primary AOC-SASLP-MV8 controller card and 4 drives connected to the onboard SATA ports in hot swap drive bays, with an internal SATA drive (640GB OS drive) and SATA DVD-RW drive connected as well
3. The installer correctly used the 640GB drive as the installation drive, even though it didn't really noticably let me specify
4. After the installation finished the server booted without any issues
5. All drives on the motherboard SATA controller ports show up in the OS

Driver Installation

1. Installed NVIDIA motherboard drivers, boots without any issues
2. Installed drivers for the primary AOC-SASLP-MV8 card (drivers from the Super Micro disc) by manually pointing the driver installation wizard to the .inf location . After this driver is installed Windows pops up with a notification that it wants to install a 'Marvell RAID virtual device' which I clicked OK to. If you try to manually point the 'Marvell RAID virtual device' installation to the inf file from the supermicro disc it says "access is denied" and won't install. If you let it install 'automatically' it appears to install properly.
3. After this driver installation was done I was able to see the 7 disks on the primary AOC-SASLP-MV8 controller card in disk management and was able to briefly see them in the WHS console. Afterwards the entire machine locks up. I am able to press control alt delete and try to force a restart but the machine never responds and eventually I have to just manually press the reboot key.
4. After this the machine boots to a black screen after showing the WHS loading splash screen. You cannot press ctrl alt delete at this screen to start the post/boot process again, you have to manully press the restart button
5. Rebooting the server and pressing F8 to select last known good configuration allows WHS to boot again and as you can imagine it uninstalls the AOC-SASLP-MV8 controller card driver

The only driver I have is the one that came on the SM disc, version 3.1.0.17 and I am selecting the i386 driver, not the amd64 of course. I can't seem to find any other drivers for that card online either.

I am going to play with the driver installation some more and see if there is any way to get it to work under WHS; obviously it looks like it is working for some people. Barring that as a troubleshooting method all I can think of to do is:

1. Try to slipstream the AOC-SASLP-MV8 controller card driver into my WHS installation like I did with the motherboard SATA AHCI driver and see if the OS is bootable afterwards
2. Try to install Vista, XP or Server 2008 onto the server and see if I the OS is operable with the controller card drivers installed and multiple drives connected. I would PREFER not to do this because then I would have to again slipstream AHCI drivers again. Chances are if I did this I would use Vista.
3. Install some other OS like FreeNas etc to see if the Linux drivers that SuperMicro provides work from there.
4. Contact SuperMicro again (I have a week or so ago already) and check again to see if there is another driver to use or a different method to install the driver

[wardog (WGS)]

If I were to guess, the "Marvell RAID virtual device" driver is the driver for the MB's e-Sata backplane port.

Ok ...........

In simply trying to assist I'll post here some things I'd try. This is NOT a "Holy Grail' of posts, instead more of a brain-storming of ideas. For reference, I'm viewing the online manual "e3710_M3N-HT_Dlx_Series.pdf"



The MV8's in the two blue PCIe slots. No other PCIe or PCI slots populated for the time being.

"Plug & Play OS" to "Yes"

I'd at least try and install with enabling "PCIE Spread Spectrum". This might eliminate some chatter over the bus.

To simplify matters I'd be using the onboard video by setting "Onboard GPU" to "Always Enable" NOTE: If I understand the options here Always Enable will force the BIOS to NOT look for/consider other PCIe devices. Maybe hopefully easing some automatic BIOS assumptions should it consider the MV8's as something they're not.

In the BIOS I'd disable the "Asus Express Gate" and in doing so on this same screen so I'd also enable "Reset User Data". The Reset User Data should revert back to disable after a successful reboot.

-------------------------
IDE, AHCI, RAID modes of/for the onboard sata controller?!? Friggin' Technical Writers can kiss my [censored]!

Quote

Only SATA 1-4 connectors support IDE mode. If you want to use SATA 5-6
connectors, set the SATA Operation Mode item to [AHCI] or [RAID]. Refer to
page 4-28 for more details

Actually, pg 4-29 of the online manual I have describes "SATA Operation Mode"

Well phooey. So, 1-4 support IDE(but not only IDE) and 5-6 only support AHCI or RAID.

Quote

If you want to create a RAID 0, RAID 1, RAID 5, or RAID 10 configuration
from the Serial ATA hard disk drives, set this item to [RAID]

After reading pg 4-29 I'd set "SATA Operation Mode" to RAID then damnit. Knowing you can't create a RAID 5 or 10 array on only the two 5-6 ports as you'd be a few disks shy doesn't necessarily mean you need to define an array at all to operate. If I read it correctly the only thing setting the six ports to RAID implies is they'll all 6 be NON-AHCI raid capable. Not having to install the AHCI drivers should UN-complicate the install as most users go bald trying to get 'em installed and/or correctly working anyways.


Please forgive me if the above reads funny or make absolutely NO sense at all. A screaming case of heartburn woke me an hour ago in mid-sleep and I'm still popping Tums in the hopes of it subsiding. Note to self: No more eating six stuffed peppers for dinner and then promptly falling alseep on the couch while watching the Nascar race at Phoenix. Pheww .......

[pirivan]

wardog, on Apr 19 2009, 03:09 AM, said:

If I were to guess, the "Marvell RAID virtual device" driver is the driver for the MB's e-Sata backplane port.

Ok ...........

In simply trying to assist I'll post here some things I'd try. This is NOT a "Holy Grail' of posts, instead more of a brain-storming of ideas. For reference, I'm viewing the online manual "e3710_M3N-HT_Dlx_Series.pdf"

The MV8's in the two blue PCIe slots. No other PCIe or PCI slots populated for the time being.

"Plug & Play OS" to "Yes"

I'd at least try and install with enabling "PCIE Spread Spectrum". This might eliminate some chatter over the bus.

To simplify matters I'd be using the onboard video by setting "Onboard GPU" to "Always Enable" NOTE: If I understand the options here Always Enable will force the BIOS to NOT look for/consider other PCIe devices. Maybe hopefully easing some automatic BIOS assumptions should it consider the MV8's as something they're not.

In the BIOS I'd disable the "Asus Express Gate" and in doing so on this same screen so I'd also enable "Reset User Data". The Reset User Data should revert back to disable after a successful reboot.

I just moved the two MV8's to the blue slots (previously one was in the blue closest to the CPU and the other was in the black slot). I set "Plug and Play OS" to "Yes" and set "PCI-E Spread Spectrum" to "Down Spread". "Onbord GPU" was already set to "Always Enable" (I should have noted that before. "ASUS Express Gate" was also already set to off. The "Reset User Data" option is greyed out if you have set "ASUS Express Gate" to disabled.

After these making these changes I rebooted and attempted to again install the MV8 drivers. As per usual it detected an 'unknown scsi' device and I pointed it to the MV8 drivers. It notifies you that the drivers have not passed the Microsoft compatibility testing. As soon as that driver is installed it pops up with the wizard wanting to install the 'Marvel RAID Virtual' device. To which I simply allowed it to install and then rebooted the PC. On reboot it displays a black screen after showing the WHS loading screen. Using F8 and selecting 'Last Known Good Configuration' allows it to boot again and removes the drive.

As a side note I really think the 'Marvel RAID Virtual' device is associated with the MV8's and not that eSATA port. Namely because it pops up and wants to install DIRECTLY after you finish the driver install for the MV8's. Plus, the MV8's are also based on a Marvel chipset.

I may try to reinstall WHS with the above configuration changes in place before the install takes place (rather than after it is already installed like I just did). I may try this while I am attempting to slipstream MV8 drivers into the install as well.

wardog, on Apr 19 2009, 03:09 AM, said:

-------------------------
IDE, AHCI, RAID modes of/for the onboard sata controller?!? Friggin' Technical Writers can kiss my [censored]!
Actually, pg 4-29 of the online manual I have describes "SATA Operation Mode"

Well phooey. So, 1-4 support IDE(but not only IDE) and 5-6 only support AHCI or RAID.

After reading pg 4-29 I'd set "SATA Operation Mode" to RAID then damnit. Knowing you can't create a RAID 5 or 10 array on only the two 5-6 ports as you'd be a few disks shy doesn't necessarily mean you need to define an array at all to operate. If I read it correctly the only thing setting the six ports to RAID implies is they'll all 6 be NON-AHCI raid capable. Not having to install the AHCI drivers should UN-complicate the install as most users go bald trying to get 'em installed and/or correctly working anyways.

Yeah, the manual is horrible, I agree with that. But yes you are correct, 1-4 ports support, IDE, AHCI and RAID but ports 5-6 ONLY support AHCI or RAID. So if you set IDE SATA mode in the BIOS, ports 5-6 are disabled essentially. I understand what you are getting at by saying to set them to RAID but in all my past experiences you would still need the RAID drivers slipstreamed into the WHS install in this case; just like I did with AHCI drivers. It appears that my slipstreaming job of these worked just perfectly as all 6 drives connected to the motherboard ports are operable. So I am not sure if setting it to RAID would do much good in this situation.

wardog, on Apr 19 2009, 03:09 AM, said:

Please forgive me if the above reads funny or make absolutely NO sense at all. A screaming case of heartburn woke me an hour ago in mid-sleep and I'm still popping Tums in the hopes of it subsiding. Note to self: No more eating six stuffed peppers for dinner and then promptly falling alseep on the couch while watching the Nascar race at Phoenix. Pheww .......

Ouch take it easy there! Thanks again very much for the above post, it is nice to at least have a few different things to try. At this point it looks like my only options are still to try to slipstream the MV8 drivers or try to install Vista (again with slipstreamed drivers) just to see if the OS is stable with drives connected to the MV8's in another OS.

[wardog (WGS)]

pirivan, on Apr 19 2009, 02:04 PM, said:

As a side note I really think the 'Marvel RAID Virtual' device is associated with the MV8's and not that eSATA port. Namely because it pops up and wants to install DIRECTLY after you finish the driver install for the MV8's. Plus, the MV8's are also based on a Marvel chipset.

I may try to reinstall WHS with the above configuration changes in place before the install takes place (rather than after it is already installed like I just did). I may try this while I am attempting to slipstream MV8 drivers into the install as well.

Ok, after just now visiting the Supermicro(SM) site I see the card uses the Marvell 6480 controller. I PM'd you my email for a link or direct attachment email to get the drivers SM supplied for this card. I'd like to nose around in them if it can be arranged for me to get 'em.

You might still slipstream the RAID drivers and give that a whirl if the AHCI route lays an egg. And as time consuming as it is I would suggest a fresh install, regardless.

As for this maybe being a nightmare install, just to make matters that much more fun, on pg 2-27 you can view the IRQ sharing schema of the 3 PCIe slots. Not a good word to say about it.

You may be forced in the end into assigning IRQ's to these two cards, and I just know you're looking forward to that And again looking at the IRQ sharing schema during you're nect fresh OS install I would have all the MB's USB controllers disabled too, to rule out a possible sharing problem with the PCIe slots, of which the USB IRQ's are shared with also. In viewing this sharing schema I'm leaning more and more to this being an IRQ assignment problem/headache. A screenshot of the BIOS POST where it shows the assignments would be wonderful if you have the capability.

I don't remember. Have you tried installing with just one card seated and hoping for a "Houston, we have lift off." moment? Might prove to be a waste of time to add the second card in only after developing a stable system, then again it might prove a learning experience too. If on the (now probable)chance it is IRQ related with two cards, having a bootable system with only one card might provide some valuable insight into what needed done prior to adding the second in.

By all means try installing using a different OS. And yea, keep plugging away here and the SM Techs with what you see/experience as it may lead to an "Aha' moment.

[pirivan]

Well, I set the BIOS to IDE emulation mode for the SATA ports and reinstalled with only one controller card in the system. Same symptoms as before, after I installed the controller card drivers I was able to see the 7 drives connected to the controller in the WHS console for a brief moment before it hard locked. A reboot had the same symptoms as usual, WHS loading screen and then to black.

I am going to try another WHS reinstall with NO drives connected other than the OS drive and internal DVD/RW (I will just pull everything out of the hot swap drive bays) AND neither of the AOC-SASLP-MV8 controllers installed in the PC. After boot I will install the motherboard drivers, reboot, install the controller card physically (and drivers), reboot, then slide all the controller card drives in to the hot swap drive bays.

***UPDATE***

I tried another WHS install with NO drives connected other than the OS drive and DVD-RW/RW, in SATA IDE mode, not AHCI. After WHS was up and running I installed the motherboard drivers and then rebooted. Afterwards I shut down and physically installed the AOC-SASLP-MV8 in the primary PCI-E slot, then booted up and installed the drivers. With no drives connected to the AOC-SASLP-MV8 I was able to boot into WHS without any issues.

After rebooting with 7 drives connected to the AOC-SASLP-MV8 it hung at a black screen after the WHS loading screen again. Another reboot with 4 drives on the primary controller controller allowed it to boot. I then shutdown and inserted another drive on the primary controller, total of 5 on the first controller (6 total in the system counting the OS drive). The system then booted without any issues. I shut down again and inserted another drive on the primary controller, total of 6 on the first controller (7 total in the system counting the OS drive). This is where it hung on loading at a black screen. So as soon as I hit 6 drives on the primary controller, it hangs.

So, I moved the drive in bay 6 (the Norco 4020 has 5 rows of 4 drives, I am counting starting on the left going right, top to bottom so bay 6 is row 2 drive 2) to bay 7 and it booted! So I slowly added drives to each bay until all of the first two rows EXCEPT bay 6 was full and it continued to boot. I added drives to the onboard ports (the two that I could use), still boots (I was shutting down in between adding each drive). Then, I shut down and installed the other AOC-SASLP-MV8. Afterwards I continued to slowly add drives until I had the machine up and booting with 16 drives (I ran out of drives to use)! Currently all slots are filled except bay 6, 1 bay on controller 2 (ran out of drives) and 2 bays on the bottom row (these are connected to AHCI only ports and I couldn't plug anything into them for the moment as I had installed the OS in SATA IDE mode). If I had 3 more drives and was operating in AHCI mode I suspect I could fil all the ports. After it was up and running I moved a drive back to bay 6 and it worked! My only guess is that the drives I had been placing in it before during my testing were not fitting right in the connectors. Tomorrow I intend to mess around quite a bit with drives in bay 6 and see what was causing it to malfunction with certain drives that would prevent WHS from booting. I also plan to reinstall WHS in AHCI mode, which I fully expect will work this time. It looks like that damn bay 6 was messing everything up. I will also try to borrow a few more drives, so that I can make sure it works if all 20 bays are filled.

It looks like I am finally getting somewhere; I am going to try to not be excited.

[pirivan]

In case this might be helpful to anyone I was able to slipstream both my motherboard AHCI drivers (NVIDIA 780a drivers) and the AOC-SASLP-MV8 drivers into a WHS installation. I followed the slipstream install guide here and copied the drivers into the DOS folder. However, as both drivers have a txtsetup.oem file I "joined" those two files together so that both drivers would install. I should note that during the "nLite" portion of the above instructions when you can click to select drivers, I DID NOT add the x64 AOC-SASLP-MV8 driver even though it was in my DOS drivers folder and was available in the txtsetup.oem file (forgot to remove the drivers but this didn't interfere with anything as I didn't add them in nlite). I was able to see drives connected to all the controllers during WHS setup with this method. The install worked perfectly from a flash drive.

After boot I simply installed the motherboard drivers which worked fine (though I believe at some point my onboard NIC went bad as it doesn't appear to work, oh well).

Here are the contents of the txtsetup.oem file I joined together/created on my own (obviously this will be different depending on what motherboard controller drivers you have):

[Disks]
d1 = "NVIDIA AHCI DRIVER (SCSI) disk 1",\disk1,\
d2 = "NVIDIA AHCI DRIVER (SCSI) disk 2",\disk2,\
d3 = "Marvell SAS Driver Diskette", \mv64xx, \
d4 = "Marvell SAS Driver Diskette", \mv64xx, \i386
d5 = "Marvell SAS Driver Diskette", \mv64xx, \amd64

[Defaults]
SCSI = BUSDRV

[SCSI]
BUSDRV = "NVIDIA nForce Storage Controller (required)"
i386_64xx   = "Marvell 64xx/63xx SAS Controller 32bit Driver", mv64xx 
amd64_64xx  = "Marvell 64xx/63xx SAS Controller 64bit Driver", mv64xx

[Files.scsi.BUSDRV]
driver = d1,nvgts.sys,BUSDRV
inf	= d1, nvgts.inf
catalog = d1, nvata.cat
dll	= d1,nvraidco.dll
dll	 = d1,NvRCoENU.dll
dll	 = d2,NvRCoAr.dll
dll	 = d2,NvRCoCs.dll
dll	 = d2,NvRCoDa.dll
dll	 = d2,NvRCoDe.dll
dll	 = d2,NvRCoEl.dll
dll	 = d2,NvRCoEng.dll
dll	 = d2,NvRCoEs.dll
dll	 = d2,NvRCoEsm.dll
dll	 = d2,NvRCoFi.dll
dll	 = d2,NvRCoFr.dll
dll	 = d2,NvRCoHe.dll
dll	 = d2,NvRCoHu.dll
dll	 = d2,NvRCoIt.dll
dll	 = d2,NvRCoJa.dll
dll	 = d2,NvRCoKo.dll
dll	 = d2,NvRCoNl.dll
dll	 = d2,NvRCoNo.dll
dll	 = d2,NvRCoPl.dll
dll	 = d2,NvRCoPt.dll
dll	 = d2,NvRCoPtb.dll
dll	 = d2,NvRCoRu.dll
dll	 = d2,NvRCoSk.dll
dll	 = d2,NvRCoSl.dll
dll	 = d2,NvRCoSv.dll
dll	 = d2,NvRCoTh.dll
dll	 = d2,NvRCoTr.dll
dll	 = d2,NvRCoZhc.dll
dll	 = d2,NvRCoZht.dll

[Files.SCSI.i386_64xx] 
inf	= d4, mv64xx.inf
inf 	= d4, mvnodrv.inf
driver	= d4, mv64xx.sys, mv64xx
catalog = d4, mv64xx.cat

[Files.SCSI.amd64_64xx] 
inf	= d5, mv64xx.inf
inf 	= d5, mvnodrv.inf
driver	= d5, mv64xx.sys, mv64xx
catalog = d5, mv64xx.cat

[Config.BUSDRV]
value = parameters\PnpInterface,5,REG_DWORD,1

[Config.mv64xx]
value = parameters\PnpInterface,5,REG_DWORD,1

[HardwareIds.scsi.BUSDRV]
id = "PCI\VEN_10DE&DEV_0036", "nvgts"
id = "PCI\VEN_10DE&DEV_003E", "nvgts"
id = "PCI\VEN_10DE&DEV_0054", "nvgts"
id = "PCI\VEN_10DE&DEV_0055", "nvgts"
id = "PCI\VEN_10DE&DEV_0266", "nvgts"
id = "PCI\VEN_10DE&DEV_0267", "nvgts"
id = "PCI\VEN_10DE&DEV_037E", "nvgts"
id = "PCI\VEN_10DE&DEV_037F", "nvgts"
id = "PCI\VEN_10DE&DEV_036F", "nvgts"
id = "PCI\VEN_10DE&DEV_03F6", "nvgts"
id = "PCI\VEN_10DE&DEV_03F7", "nvgts"
id = "PCI\VEN_10DE&DEV_03E7", "nvgts"
id = "PCI\VEN_10DE&DEV_044D", "nvgts"
id = "PCI\VEN_10DE&DEV_044E", "nvgts"
id = "PCI\VEN_10DE&DEV_044F", "nvgts"
id = "PCI\VEN_10DE&DEV_0554", "nvgts"
id = "PCI\VEN_10DE&DEV_0555", "nvgts"
id = "PCI\VEN_10DE&DEV_0556", "nvgts"
id = "PCI\VEN_10DE&DEV_07F4", "nvgts"
id = "PCI\VEN_10DE&DEV_07F5", "nvgts"
id = "PCI\VEN_10DE&DEV_07F6", "nvgts"
id = "PCI\VEN_10DE&DEV_07F7", "nvgts"
id = "PCI\VEN_10DE&DEV_0768", "nvgts"
id = "PCI\VEN_10DE&DEV_0AD5", "nvgts"
id = "PCI\VEN_10DE&DEV_0AD4", "nvgts"
id = "PCI\VEN_10DE&DEV_0AB9", "nvgts"
id = "PCI\VEN_10DE&DEV_0AB8", "nvgts"

[HardwareIds.SCSI.i386_64xx] 
id = "PCI\VEN_11AB&DEV_6440", "mv64xx" 
id = "PCI\VEN_11AB&DEV_6485", "mv64xx"

[HardwareIds.SCSI.amd64_64xx] 
id = "PCI\VEN_11AB&DEV_6440", "mv64xx" 
id = "PCI\VEN_11AB&DEV_6485", "mv64xx"