Raid controller disappears from BIOS

Hi,
I got a strange problem: everytime I pull out the power cord from the computer-the Raid controller disappers from Bios and of course the comp. cant find the HDD`s.
After some time I found out how to get it work again,
I have to pull out the IDE cable and power cable from the HDD and put it back again. Then the Fast Track Controller comes up again in BIOS.
Any one has an idea what that could be?
I use The Promise Fast Trak 100 Raid driver.
Thanks for reply.

Quote
Originally posted by Bas
Hi,
You should use the MSI raid drivers....
Also, check the jumper on your harddisk and the way the cables are connected, the blue connector should be on the raid controller...
What harddisks do you use?
Hi Bas,
Thanks for reply, I use 2x IBM 60GXP, 60GB HDD.
My drivers are from MSI.
Every thing worked fine almost 1 year, I did not change anything.
First I thougt maybe it could be a battery the voltage is 3.41V as it was when I bought the mobo.

Similar Messages

Internal RAID Drives Disappeared from Desktop & Finder

A few days ago, one of my two internal mirrored RAID sets no longer showed on the desktop or in the Finder Sidebar. A day later, the other internal RAID set disappeared from desktop and sidebar. The two remaining internal non-RAID drives show up as do two external drives. All internal and external hard drives still show under Disk Utility and Photoshop Bridge CS3.
I checked Finder Preferences and boxes are checked to show internal and external drives on the desktop and sidebar. I looked at the drive detail under Disk Utility and nothing looks wrong with the two RAID sets ON-LINE. I unmounted one RAID set and re-mounted without any change. I tried unchecking the two preference boxes to not show the drives and rebooted, rechecking the boxes and rebooting and nothing changed on the desktop or sidebar.
Does anyone have any suggestions to resolve this?

Well our invisible drives problem is resolved but it's not the solution that I'd hoped for.
We visited the Genius Bar at a local Apple store and they denied any knowledge of problems with invisible drives in Macs and discounted my reports from Mac forums.
I went home and ordered a new 1tb Seagate drive. When it arrived, I installed it in bay 2, copied each invisible drive to the new drive one-at-a-time, broke my two sets of internal mirrored drives, erased all the affected drives and reloaded them. Now all drives are visible on the Desktop and Finder again.
I'm hoping that the disappearing drive problem doesn't surface again but view this as an unresolved Apple issue. Now I can look at other mass storage options for future growth.

Gspeed ES Pro RAID keeps disappearing from Mac, have to re-initialize!

UPDATED VERSION:
MAC PRO KEEPS LOSING CONNECTION TO RAID DRIVE.
After 9 months of organizing a documentary film edit on an external RAID drive (12TB, Raid 0. Yes, I have 2 layers of backup), I purchased the PNY Nvidia Quadro 4000 video card for the primary edit. Soon after, I began having boot up issues. The screen would freeze at various points during the startup process, requiring manual power-downs.
Over the past two months, my computer has lost communication with the RAID 3 times, forcing me to rebuild it from my backup drives (10TB). One tech at Diskwarrior said my computer lost the partition, and that the 1s and 0s had been largely replaced with gibberish.
The Raid becomes unrecognized by my computer in one of two ways:
1- After two days of copying data back over to the raid (rebuilding it), I get an error code -36, saying a file cannot be read or written, then the Raid partition disappears from disk utility and the next time I start up the computer says it doesn’t recognize my drive. The ATTO configuration tool (the card that attaches my raid to the computer) sees the drive, but my computer does not. I have to re-initialize it and start over again.
2- The Raid will go from being recognized to not being recognized when I reboot one day. Again, I have to re-initialize and rebuild.
I removed the PNY Graphics card and put in the stock ATI Radeon HD 5770 it came with. On day 2 of rebuilding the RAID, I got the error -36 and the Raid disappeared from disk utility again. When I opened the raid folder, which seconds before had 10 TB of data on it, it read as zero items. So the PNY Nvidia card was NOT the problem.
Apple has worked on the computer 3 times, running extensive hardware tests, but the same problem persists. At one point they said my blackmagic card was the problem, and more recently they said I probably have bad ram. I tried separate ram (the old 6GB my computer came with), and my computer seemed to begin booting up okay, but one day later I had the -36 error, the RAID couldn’t be recognized again and I lost the data during another rebuild. Apple even replaced the Ram Tray, but the same problem persists.
G technology says my RAID’s hardware is fine, and ATTO, who makes the Raid card, says it looks fine to them too. This does not mean they are 100% not the problem though.
Yesterday as I was attempting to rebuild the RAID again, I saw the -36 error come up, and files stopped copying. I immediately made a screenshot and noted the time.
Today I spoke with a really cool tech at Apple named Ron who helped me investigate the Kernel log, and this is what it said (the RAID is called FadingWest):
Dec 6 17:05:36 Jesses-Mac-Pro kernel[0]: hfs_swap_BTNode: invalid forward link (0xbb739311 >= 0x0000df00)
Dec 6 17:05:36 Jesses-Mac-Pro kernel[0]: hfs: node=2717 fileID=4 volume=FadingWest device=/dev/disk3s2
Dec 6 17:05:36 Jesses-Mac-Pro kernel[0]: hfs: Runtime corruption detected on FadingWest, fsck will be forced on next mount.
Ron believes my problem is with the RAID card. He thinks it’s dropping the connection. So I’ve got an RMA going with ATTO for a new one.
Here are the final things I can troubleshoot at this point:
New RAID card (ATTO)
New RAID drive (G-Technology)
Motherboard / PCI lanes (Apple).
NEW COMPUTER (Apple)
Any ideas are appreciated. Here are the items in question:
Mac Pro mid 2010 2x2.66 Ghz 6 core Intel Xeon OS X Lion 10.7.5
G speed ES Pro (G Technology) – 12TB @ RAID 0
ATTO R680 RAID card

I found this on another help site, I think it's the trick:
there are 2 halves to the Dock. With a bar in the middle.
on the left side, there are 2 sections. the furthest left are the icons that will stay in the dock, then on the right side of the left half of the dock, are the temporary icons, the ones that just stay there till the program is done.
You can freely move a temporary icon to the left and it will be come a permanent icon.
I am reminded of the wizard of OZ here... you could always get to firefox... you just had to click your mouse (and drag an icon)..

K8TM-ILSR how to disable raid controller in bios?

Hi,
I have a MSI motherboard K8TM-ILSR, and have 2 sata hdd’s connected.
I want to test my Maxtor hdd’s with the tool called “powermax” but this tool, don’t see my hdd’s
Because it’s on a raid controller. I have my hdd’s in non-raid , when I’m booting I see non-raid, but seems still not disabled.
Is it possible to disable the raid controller in the bios, or are there other ways?
The pata controller is used for my cd-rom and writer.
Please let me know.

You can actually disable the controller, but you cannot use the disks then.
I wouldn't try messing with your raid configuration, you may lose data doing so.
You can try the following: find someone with a mainboard that supports single SATA drives. Install one drive and set the bios setting of the mainboard to IDE for that channel. Now you must be able to use the Maxtor utility. Be aware NOT to let the tool make any changes to the disk. This goes for the mainboard's bios as well. Letting these things change anything to the disk, will cause data loss / distruction of your RAID configuration.
If you use these two drives in a non-raid mode, you will be fine doing this.

Bad RAID Controller Card?

One of the arrays in my Xserve RAID had disappeared from the network and RAID admin software. All the disks that make up the array have green lights and appear in RAID admin. When the host PC reboots this array is no longer detected in the Apple Fibre Channel card BIOS. After having swapped cables around I reckon the RAID controller card has failed.
Is it safe to swap the top and bottom RAID controller cards to prove the diagnosis or does the controller hold information specific to the diskset it is connected to?

The diskset info is stored on the drives, so its perfectly fine to swap controllers.
On that note however, first of all make sure you really jam that controller board in there well... first time we swapped and it wasnt in there perfectly secure, 3 drives went red and the rest was history. Also, if your controller is acting up, definitly make sure things are backed up when swapping between sets... when we've had controller issues, its usually only been volumes going down on the computer's side, but I have heard of raid admin shooting back drive errors and turning things red as well.

Second IDE Raid controller

I have MSI K7T 266 Pro 2 RU board, onboard raid, i want to install second raid controller card. I cant get into a bios of second card. Second card is CMD PCI - 0649 Ultra 100 Raid controller.
If the a problems when running two raid controllers in one system?
And how can i get into the bios of second raid card.
P.S. card is installed in Windows XP fine. i can see two hard drives connected to it. Right after raid bios on onboard raid it looks windows.
Please help
Thanks

Quote
Originally posted by pcman12345
My pc boots of onboard raid. (2) 40gig drives. What do new drivers have to do with getting into bios of pci raid card. I have all the latest drivers anyway.
Any other ideas?
Thanks for your help.
It sounds like you are booting from the promise RAID controller. If so, you are well familiar with the way in which it dominates the bootup process for the first 30 seconds or so.........(dots look familiar?...)
I wonder if the second RAID card is also initiating its bios sequence at the same time underneath the Promise boot screen (underneath, so to speak) so that when the Promise routine is finished, so is the CMD routine, and you proceed from that point with both RAID controllers initialized (but can only see one of them at a time from the bios screen.)
Do you you have "boot from other device" enabled in the bios? If so you might try disabling that to see if it will sequence the RAID controllers initialization so that the CMD bios appears after the Promise bios is done (I assume you have the onboard Promise array selected as the boot device.)
A bit more trouble would be to reboot to main bios, disable the onboard RAID controller in the bios, save and reboot. At this point the Promise bios will not display and you should see a CMD bios display which you could manipulate--then reenable the Promise controller to boot, etc. If you disable the Promise controller and you still don't see a bios for the CMD RAID device you need to look elsewhere. Also, it might be that the CMD bios access requires a certain key sequence pressed during post to display?....Just some random thoughts...

MSI845PE Max2: booting from the RAID controller

Hi,
I have an MSI 845PE Max2 motherboard. This board comes with 2 extra IDE connectors from an onboard RAID controller. I managed to put this controller to work as a regular UDMA133 controller with an modified BIOS.
I have a CD-ROM connected to one of those IDE connectors. The CD-ROM is detected, but I didn't manage to boot from that drive.
I tried to alter the boot sequence on the BIOS. I even disabled the 3 pre-configured steps, leaving the option "Try other devices" enabled, but still wasn't able to boot from the CD-ROM.
So, this is my question: it there any way to get a drive (wether it is a CD-ROM or a hard drive) to boot, when it is connected to the RAID/UDMA133 controller?
Best regards,
Norberto Henriques

I Download mod bios and went to flash and the Msi instructions on flashing were insufficent for the job. For one thing when I got to A prompt after bios. There was no c drive detected. Couldn't get to bios in C:test. Hard drive was connected to Ide 3 where i installed it with the 133 drivers during installation. I tried connecting it to Ide 1 to see if it would boot. It did and seemed to work but still couldn't get to c drive from A prompt after bios with C: . Tried booting with Me Boot Disk (the one I installed Me with on other systems). There was no ramdisk loaded. It just acted like I wanted to install Me. I gave up on the flash (but still would like to know how??) Got my maching running with 430watt antec, msi 845pe max2-fir, 40 and 60 gig maxtor 133 drives, pent 4 2.4B ghz. asus Dvdrom and Asus cdrw,512Mb crucial 2700,Radeon 8500LE,Sound Blaster 5.1. Had only a few problems. Still trying to figure out some of the Bios settings. Will post more later if anyone can help. P.S. How do you get all your statistics to show up at the end of your post without typing it out each time?? Any help appreciated. May the force be with you

Moving from VIA RAID controller to another RAID controller?!?

Hello
I'm going to install a RAID-1 with 2 SATA harddisks from seagate using the onboard VT8237 RAID controller of my KT6 Delta.
I guess there should be no problems and that the temperature on the motherboard will be fine.
However, what will happen if I want to move later on to a new motherboard with another raid controller or install a dedicated RAID controller?!?
Will I loose all my data? Or will the new raid controller duplicate the data based on the source drive?
Thanks
JohnQM

I have read somewhere that the following migration paths apply for raid:
1. raid-1 can always be migrated to a new RAID controller, no matter which brand, because raid-1 is just a mirror and no important information is written in the partition table
2. raid-0 or other raid-levels
2.0 from one brand of RAID controller to the same version of the RAID controller of the same brand: no problem
2.1 from one brand of RAID controller to a new version of the RAID controller of the same brand: usually no problem (upwards compatible)
2.1 from one brand of RAID controller to a RAID controller of another brand: no go
Can someone confirm this please?
Thanks
JohnQM

If you replace raid controller of hardware raid do you have to rebuild raid from beginning or not?

hi,
I like to know if the raid controller is damaged and you replace it with a raid card in a PCI slot .do you have to rebuild the raid from begin if it is hardware raid ?
the same question I ask for software raid ? this question is for raid 0,1,5,6,ect.
if you have to rebuild from begin then it means if you don't have good back-up then the data is gone!
thanks
johan
h.david

Hello,
Enterprise controllers will read the metadata of the array, as it's stored on the disks, and recognize the configuration. Then you and you can choose to 'mount' it or create
a new array.
But, I suggest you to go to the manufacturer of the controller and get detailed information for scenarios like that.
For software raid, the only experience I have is that Windows can recognize a set of drives when they are configured as Dynamic Disks.
best regards
jesper vindum, denmark

V2P Virtual Machine to physical Server migration on IBM x3650 M4 and switch from BIOS to UEFI Boot environment

Hi there,
just wanted to share my experience with a manual P2V Migration. The VM became to ressource hungry and it was decided to move it off an ESX 5 Cluster to a dedicated physical Machine.
V2P Virtual Machine to physical Server IBM x3650 M4 and switch from BIOS to UEFI Boot environment
Task:
V2P Migrate a VMware virtual machine to a IBM x3650 M4 with a ServeRAID 5110e RAID Controller or any other LSI RAID Controller without 3rd Party tools.
This should also work with other RAID Controllers or Servers but be sure to pick the right drivers then.
Extra Task:
The VM's boot environment/virtual BIOS is BIOS, not UEFI (as per default VMware Setting). The physical Server is running in UEFI mode.
The Challenge:
After restore the Server won't boot or get into a BSOD (7B), because the RAID drivers are missing.
After restore the VM won't boot because the boot environment has changed from BIOS to UEFI
Preparations:
An existing physical Server of the same type and with the same RAID controller and same OS would be nice for troubleshooting and checking the registry.
An existing DHCP server will make networking things easier.
Connect the new physical server x3650 M4 to power and network
   create a virtual drive that has at least the size of the existing VM plus the size of the full backup (.vhd). Should be about twice the size of the original vmdk.
Get a USB Flash stick (I used a 8GB modell so no problem with larger sticks)
Download and extract LSI MegaRAID Driver on that USB media (I used 6.705.05.00-MR_Windows_Driver directly from LSI website)
Download and extract INTEL Network Adapter Driver on that USB media (I used 12.11.97.0 of e1r62x64.inf from 19.5 driver release from 2014.09.26 directly from LSI website)
Step by Step:
if you have an other physical Server of the same type and same Controller and same OS:
1.   open regedit and export everything related to SCSIAdapter and megasas2 to .reg files or skip this step and use my files below
   some of this (sub)keys may not be accesible - you will then first take ownership and/or modify permissions to read them
   HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4D36E97B-E325-11CE-BFC1-08002BE10318}
   HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\PCI\VEN_1000&DEV_005B&SUBSYS_04121014&REV_05
   HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\megasas2
   this one is more complicated:
   HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase (only relevant are those devices where the service name is megasas2 - export the whole subkey and get the filtering done with tools like notepad++)
   Make a copy of the following files/folders:
   c:\programdata\LSI\
   c:\windows\inf\megasas2.INF
   c:\windows\inf\megasas2.PNF
   c:\windows\system32\drivers\megasas2.SYS
on the existing VM:
1.   create a full backup (image) with the built-in Windows Backup Utility and save it in an accessible network location (you will need this one, if anything goes wrong or you want to come back to this point.
   Alternatively you could create a VMware snapshot.
2.   import the .reg files you created earlier or import my files below.
   Attention: This will make the VM unbootable!
   But it is required to prepare the VM for the new RAID controller when it will be restored on the physical server.
   Do NOT reboot now as this will make the VM unbootable!
4.   Copy the LSI folder and the megasas2.INF/PNF/SYS files to the appropriate destination folders on the VM.
3.   again create a full backup (image) with the built-in Windows Backup Utility and save it in an other accessible network location but not where you safed the first backup.
   This will be the "golden" backup if you want, where the RAID controller is prepares. We will rebuild the new machine with this second backup.
4.   Optional: you could use the Backuputility now to restore the Systemstate of the first backup and reboot or restore the VMware snapshot.
   This will undo the changes we made to the VM.
on the new physical server:
1.   boot the physical server from Windows Server 2008 R2 SP1 DVD
2.   when it is ready to install, press shift+F10 to get command prompt and do not click to install Server 2008
3.   check driveletter of the USB stick with diskpart list vol (was C: at my Server, so don't wonder about that letter)
3.   load drivers for ServeRAID SAS controller (this is mandatory to see the volume in diskpart)
   drvload c:\srv_2008_x64\megasas2.inf
4.   load drivers for INTEL I350 Gigabit NIC's (you will need this to access the backup that is on the network)
   drvload c:\PRO1000\NDIS62\e1r62x64.inf
5.   wpeinit (will start network. wait ~15 sec to let it start and get IP address)
   check if you have IP connectivity an address with ipconfig, if not, use an other NIC driver and repeat steps 4+5
6.   create the EFI and BCD
   diskpart
   list disk
   select disk x (where x is the number of the disk to convert)
   clean
   convert gpt
   create partition EFI size=128
   format fs=fat32 quick label=EFI
   assign letter=i or any other free drive letter
   create partition MSR size=128
6.1   Copy EFI bootloader to EFI partition
    i: (where i is the letter of your EFI partition)
    mkdir EFI\Boot
   mkdir EFI\Microsoft\Boot
    copy x:\Windows\Boot\EFI\bootmgfw.efi i:\EFI\Microsoft\Boot (where x ist the default letter of the current Windows PE environment)
    copy x:\Windows\Boot\EFI\bootmgfw.efi i:\EFI\Boot\bootx64.efi (note that the file will be renamed to bootx64.efi)
7.   create the new partitions
   diskpart
   create partition primary size=100000 (edit the size to your needs. this will later become the system drive of your server)
   format fs=ntfs quick label=Windows
   assign letter=Y or any other free drive letter
   create partition primary size=990000 (this will temporarily store your backup and we need it for the restore process)
   format fs=ntfs quick label=Backup
   assign letter=B or any other free drive letter
   exit
8.   map network drive and copy the backup .vhd to the local disk
   net use L: \\networklocation\where\you\saved\the\backup (enter the credentials when asked)
       copy the .vhd file that contains the OS of your VM to the local Backup Partition B. The relevant vhd file is usually the largest file in that fileset.
       Note that the names are very similarly - be sure to get the correct file!
   copy "L:\WindowsImageBackup\VMNAME\Backup 2015-02-03 123456\00e767c6-xxxx-xxxx-xxxxxxxxxxxx.vhd" B:\
       give it time, this is slow and will take some minutes/hours and you will not see any progress! Look at the disk-LED's to see if anything is still happening
9.   mount the .vhd and copy it's contents to the new system partition
       Note that you can only mount a locally stored .vhd. You cannot mount a .vhd in a network location.
   diskpart
   select vdisk file=B:\00e767c6-xxxx-xxxx-xxxxxxxxxxxx.vhd
   attach vdisk
   select vol 5 (where 5 is the number of the mounted vdisk)
   assign letter=Z or any other free drive letter
   exit
10. Restore the files from the image
   z: (where z is the letter of your mounted .vhd)
   xcopy * Y:\ /e /c /h /k /o /b /q /y (where Y: is the letter of your new partition with the label "Windows")
       several "Access denied" messages appear, ignore them. Those are SystemVolumeInformation folders.
11.   Create Boot Configuration Data (BCD)
    bootrec /RebuildBcd
       this will try to repair the missing BCD on the second of the two small partitions we created earlier in and should normally work, otherwise you'll have to create BCD manually (search google for that procedure)
       Note that it may find more than one Windows installation and ask which sould be added to the boot list. Be sure to select only the one that is in the correct Volume (Y:\)
   that's it - exit the DOS command box and close the "Install Windows" Window, after a prompt it will reboot.
   Select "Start Windows Normally", if Windows Error Recovery appears.
12. Preparing Windows
   When Windows boots for the first time, DO NOT reboot if you are asked, it won't come back at this stage!
   Install Intel chipset drivers for the Server (I used "intc_dd_inteldp_9.4.0.1026_windows_32-64.exe" from IBM website)
   Open Device Manager, uninstall the "RAID-Controller" with the exclamation mark. You cannot install the correct driver for this Device at this point, it will bring you the error: "Cannot create a stable subkey under a volatile
parent key"
   Once again, DO NOT reboot!
   In Device Manager select Action>Add Legacy Hardware
   click Next
   select Hardware manually
   select Storage Controller as Type
   LSI should be listed, select "LSI MegaRAID SAS 9281-8E"
   click Next, ignore the error "Code 10" Message.
   Click Done.
   Rightclick the LSI MegaRAID SAS 9281-8E device with the exclamation mark in Device Manager
   select Update driver
   select Browse my computer for driver software
   select let me pick from a list of device drivers on my computer
   select "Have Disk"
   browse to the folder where the extracted RAID driver 6.705.05.00-MR_Windows_Driver is located (e.g. USB Flash stick E:\6.705.05.00-MR_Windows_Driver\srv_2008_x64)
   then unselect "Show Compatible Hardware"
   on the right side, scroll up and select "IBM ServeRAID M5110e SAS/SSATA Controller"
   ignore the Update Driver Warning and click Yes
   click Next, ignore the error "Code 10" Message.
   ignore the exclamation mark on "IBM ServeRAID M5110e SAS/SSATA Controller" in Device Manager but be sure that there is only this controller and no other RAID-Controller or LSI SAS Controller listed under "Other Devices"
or "Storage Controllers"
   NOW you are safe to reboot
   After reboot you will find two "IBM ServeRAID M5110e SAS/SSATA Controller" in Device Manager
   Rightclick and uninstall the one with the exclamation mark. Do not tick the checkbox to remove the driver as well!
You're done!! (hopefully)

Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase]
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0060&SUBSYS_C31115D9]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0060&SUBSYS_C38015D9]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0060&SUBSYS_C41115D9]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0060&SUBSYS_C48015D9]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0060&SUBSYS_C51115D9]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0060&SUBSYS_C58015D9]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0060&SUBSYS_C61115D9]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0060&SUBSYS_C68015D9]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0060&SUBSYS_C71115D9]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0060&SUBSYS_C78015D9]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0060&SUBSYS_C81115D9]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0060&SUBSYS_C88015D9]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0060&SUBSYS_C91115D9]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0060&SUBSYS_C98015D9]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0060&SUBSYS_D20219E5]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0060&SUBSYS_D20319E5]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0071&SUBSYS_00721137]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_00011BD4]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_00721137]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_00731137]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_008F1137]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_00B01137]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_00B11137]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_00B61137]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_00B71137]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_00C21137]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_00C31137]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_03B11014]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_040015D9]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_040D1014]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_10541000]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_11771734]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_14581002]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_1F201462]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_30351054]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_350C8086]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_350D8086]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_822910F1]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_843B1043]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_84711043]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_92211000]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_92401000]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_92408086]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_92411000]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_92418086]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_92421000]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_92431000]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_92441000]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_92A01000]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_92A11000]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0078&SUBSYS_92501000]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0078&SUBSYS_92511000]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0078&SUBSYS_92701000]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_00011BAA]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_00021BD4]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_00791137]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_02001AE3]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_03B21014]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_03B31014]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_03C71014]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_070015D9]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_11761734]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_11B31734]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_30361054]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_350B8086]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_84731043]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_84801043]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_8985152D]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92551000]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92561000]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92568086]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92601000]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92608086]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92611000]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92618086]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92621000]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92631000]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92641000]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92648086]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92671000]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92678086]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92681000]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92688086]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92751000]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92758086]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92761000]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92768086]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92771000]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92801000]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92808086]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92811000]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92821000]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92828086]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92841000]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92881000]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92891000]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92901000]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92908086]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_D20819E5]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_D20919E5]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0409&SUBSYS_10091000]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0411&SUBSYS_10011000]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0411&SUBSYS_10018086]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0411&SUBSYS_10021000]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0411&SUBSYS_10031000]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0411&SUBSYS_10038086]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0411&SUBSYS_10041000]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0411&SUBSYS_10081000]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0411&SUBSYS_10088086]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0411&SUBSYS_100C1000]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0411&SUBSYS_100D1000]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0411&SUBSYS_10811734]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0411&SUBSYS_10a31734]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0411&SUBSYS_20041000]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0411&SUBSYS_20051000]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0411&SUBSYS_30161054]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0411&SUBSYS_34908086]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0411&SUBSYS_35008086]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0411&SUBSYS_35018086]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0411&SUBSYS_35048086]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0411&SUBSYS_35078086]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0411&SUBSYS_82871033]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0413&SUBSYS_10051000]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"

K8N master2-far doesn't detect Areca 1220 raid controller

Today i purchased the last components for my system. Everything works perfectly except for my Areca 1220 8x pci-e raid controller. As i feared the controller is nowhere to be seen, not in the bios, not in windows. I already had bios version v1.10 but flashed the bios version on the msi site anyway. Nothing changed. On the msi site under "QVL" i see my Areca at the bottom of the list. Does that mean that this MB can work with this controller? What must i do to make it work? I think i have to see it at least in the bios!
Your help is appreciated. Now 5x 300 GB of storage is doing nothing.

Quote from: Bas on 10-November-05, 20:30:00
Maybe you need to update the cards firmware.
I already looked into that matter and found out that the only way to upgrade the firmware or bios is to use their http tool McRAID Storage Manager. This of course is done in windows. Now windows doesn't see my Areca 1200 and so McRAID doesn't see it either. I can't update my Areca.
This problem is well known by the motherboard manufacturers. Let me quote something from the Areca site:
Q10150407 - Is there any socket 939 motherboards that work with your model ARC-1210 raid controller? In a SLI board I would use one 16x slot for Graphics card.
Our PCIe ARC-12xx series controller uses Intel IOP332/333 processor. The Intel high performance IOP (IOP331/332/333) has integrated the bridge chip in the controller. But the original NVIDIA nForce4 SLI chipset BIOS has the problem after Bridge IRQ routing. All controllers use Intel new IOP 332/333, such as Areca, Intel, and LSI have the same IRQ routing problem. Those NVIDIA 939 M/Bs can be worked in the Windows environment. Due to the Windows system takes over the BIOS job, and Linux & FreeBSD need to use the M/B BIOS, so it has problem with our PCIe controller.
Currently, DFI, Ausu, MSI and Gigabyte have BIOS to solve the problem. If you have problem in this kind of mainboard, please try to manufacture latest BIOS.
We have tested DFI Lanparty NF4 SLI & ASUS A8N-SLI Deluxe, and Asus A8N-SLI Premium. It works very well with our firmware 1.38 and newest mainboard BIOS. Try to swap the graphic and our controller, if you find some warm boot problem in the Asus A8N-SLI Premium.
I still think i need an updated bios for the k8n master2-far (ms-9620). The fact remains that there are problems reported with every SLI motherboard. I knew this already from the socket 939 platforms. I was sceptical about the k8n master2-far but thought that a server MB should have no problems. I did ask a question about this however at the shop where i bought this MB. I even found an reply from you to another user who had similar concerns about the Areca controllers and an SLI MB. You said that it should not be a problem. Even so i always kept the possibily open that this problem can happen. And here i am
Thanks for your help. More input is always appreciated as i am still waiting for an answer from MSI in the Netherlands about this problem. Right now my server is doing nothing. I hope my raid controller will work very soon.

On-board RAID and PCI RAID controller

Hello everybody,
I am new to the forum. So, please excuse me if that topic was already covered...
I have MSI MAX2-LR (MS-6398E) board. It works just fine, no problem so far. Though I have 2 problems with add-on cards:
1. I was planning to use on-board RAID and additional PCI RAID controller = FastTrack 100 TX2 to cover 6 hard drives into 2 mirrored sets: 4drives one and 2 drives the other.
It doesn't work! I can use either on-board RAID or PCI RAID. As soon as I have any drive connected to on-board RAID, the PCI RAID disappeares. If I have no drives connected to on-board RAID, I can see both RAID controllers, they have different I/O and IRQs, and PCI RAID is working just fine. If only I connect one drive to the on-board RAID, it gets activated on startup, and the other one disappeares. :O
I believe it's a BIOS bug. I wander, if that can be fixed easily????? :D
2. I have a new Matrox Video card = Parhelia. It doesn't work in AGP slot! System doesn't recognize it, and beeps non-stop. I am dealing with Matrox Tech Support on that matter. ?(
Maybe, it's a known issue, and somebody can save me time by telling what's that about.
Appreciate any imput. Have a great weekend.!!! :]

Hey I also have the same Raid card and also the Matrox Parhelia, and I see that you also have some problems with the card I got also problems with the card, but they couldnt help me at theire forums (http://forum.matrox.com/mgaforum/Forum10/HTML/005085.html), I hope we have got more luck here :D

Promise PDC20579 SATA/RAID controller

I'm trying to get the piece of shit working with Linux, but haven't had any luck. I'm not sure which Promise add-on cards use this chip as this one is built into my mobo, where it provides 2-SATA and 1-PATA port. I'm using the PATA with 2 drives (160GB, 60GB) and I don't want to setup a RAID array, but just use it as an extra IDE controller.
The BIOS detects the drives correctly but linux doesn't recognize the Promise controller, so it's not assigning device nodes for the drives (no hd* or sd*) and I can't seem to make it work. The correct kernel module, according to the net, is sata_promise, but I'm not certain it supports the PATA part of the controller. When loaded, it prints info about the connected drives to dmesg, but never assigns device nodes.

Okay, so I found a patch in the Red Hat kernel mailing list that seems to work. It patches the sata-promise module to attempt to detect PATA ports when nothing is connected via SATA. I don't have any SATA discs so I cannot check to see if it breaks anything in regards to SATA.
If anyone else is interested, I'll strip the RH specific stuff from the patch and submit it to the Arch kernel devs for review. Not sure if enough people would find is useful tho.

PPC G5 compatibility of Areca PCIE RAID controller arc-1280?

Subject: Mac compatibility of Areca ARC-1280 24 ports PCI Express to SATA II RAID adapter.
At Areca's Internet site ( www.areca.com.tw) consumers can read at pages concerning arc-1280 card that: « The SATA RAID controllers support broad operating systems including ... MAC ... ».
At Specifications page, under: Operating system, it is written: « Mac OS X (no_bootable) ».
Absolutely no other warning appear about MAC owners.
So, if you are just a basic computer consumer, you are now strongly tempted to believe that if you got a MAC with PCIExpress technology & OS X, you can safely buy arc 1280 PCIE.
This is because (nearly) everyone knows that in real pragmatic actual life OS X exclusively runs on Apple Mac machines. In the case of arc-1280, as it is a PCIExpress adapter, only two Apple Mac models are possible: the very recent MACPro (Intel cpu based) & late 2005 PPC G5 dualcore (IBM cpu based). As Areca mentions nowhere any warning between MACPro & G5 dualcore, only owners of either of those PCIE machines may logically have the opportunity to run OS X with an arc-1280 connected!
If you are a little bit more paranoïd, before to buy such an expensive adapter, you will check if there are other stuffs to confirm your deductions. You then will find Areca's online user's manual 3.2, where it is stated that a bios configuration utility, contained into card's firmware, is « OS independant » & can be accessed at startup by pressing TAB or F6. About « MAC X » driver installation, user is invited to follow a readme.txt (that in fact does not exist nowhere). It is the same for archttp proxy server installation, which is also asserted to support Mac OS.
Moreover, a Mac driver is freely downloadable online, called arcmsr-1.3.1.pkg. Now you are ready to trust!
Having arc-1280 plugged, you start your Mac (happy to hear that card beep after startup) then install driver (the same is present online & on Areca's companion CD). A text appear:
« This driver supports...arc 1280...PCIE... Please note that this is a pre-release version of the driver for testing purpose, and is *NOT * for general distribution. ». But installation completes succesfully and you pay no attention to this frightening sentence hidden into Areca's driver package.
What then arise when you have your computer restarted? Nothing: except the beep at startup, Areca's high end Raid controller simply do not appear anywhere into Mac OS X!
As I cannot afford paying more than 1200 euro for just a startup beep, I decided to require help from distributor & Areca's very enigmatic support. Lastly distributor decided to try with another arc-1280 which was as useless on my Mac than the first one. I again protested, Areca's support seeming to have totally resign for quite a lot of time now, distributor blaming me not to have been carefull enough ?!
Distributor ask me now to re-send back the card. They will try to get their money back from Areca, then maybe will I have my money back ? They asked me to write a letter with a description of the problem & why I want a full refund.
This is now done, hoping this will help to avoid further misinformation.

MacGurus PCIE which are supported.
I saw the Areca reviewed xbitlabs
AMUG http://www.amug.com does great reviews of Mac compatible drives, enclosures, and controllers.

Promise RAID controller & WinXP - 845 ultra

I finally got around to connected a couple of drives to the Promise Fasttrack 133 RAID controller.
When I go into windows.. It finds the controller..
So if I look in Device Manager, I do see the Promise MBFasttrak 133 Lite..
But under DISK DRIVES, the Promise 2+0 stripe /raid0 scsi device shows up as an unknown, and if I try to update the drivers.. nothing ever changes..
The drive(s) does work, more of a comsmetic issue?
Thank you,
Fred R

Some of the suggestions I don't understand quite well. Please could you explain further:
> remove the other two drives leaving the raid pair
> and cd only
>
> put raid 2nd in boot order
What do you mean with that?
> reboot press the key you need to get in to raid bios
> create the array and make it bootable
array is already created (Note: there is important data on it, can't recreate it! Only Segate 80GB is free and empty)
I don't want to boot from raid.
>
> now boot to cd to install,right at beginning it will say
> press f6 to install mass storage drive you need the
> driver on floppy to install it
I already tried the XP-Install routine to specify additional mass storage drivers. (Note: 1 single 80GB Drive was attached) Which are the suitable ones? As mentioned I tried the following:
1. Attached floppy 'Fasttrack family drivers'
Result: Message: Driver is for Win2k only. Not a single Harddrive shows for installing XP.
2. Attached Floppy (Promise Ultra 100 lite, 256 only)
Result: Driver is for Win2k only. Installation procedure hangs.
3. Driver from MSI-Site for pdc20265. Same as 2.
4. Extracting via4in1 drivers and putting WinXPIDE drivers on floppy:
Result: Installation routine doesn't recoginze drivers on floppy.
> rest should be the same as normal
>
> this should be similar as well
>
> http://www.amdforums.com/showindex.php?s=&threadid=146384
Which is the right driver for WinXP to specify for mass storage device at WinXP installation?

Raid controller disappears from BIOS

Similar Messages

Maybe you are looking for