RAID BIOS controlling Sytem HDD, not AHCI

Hey All,
I have an XW8400 Bios 2.38, adn I enabled the RIAD+AHCI sata emulation (and I did the regedit trick too) . AHCI bios loads but it says the my System drive ( SATA DRIVE) is being controlled by the RAID BIOS and not AHCI
I do have a RAID 0 with LSI not the ESB RAID. Is there a way to disbale the ESB RAID bios so the drives will use AHCI only?
Salud

You really had it working before? Weird - it's not supposed to work! The Promise controller supports either 0 or 1. I can't see how you got 0+1.
And how can the second (bigger) HDD be the "other array" if you've got mirroring in there somewhere? OK, you can maybe fool a single drive into thinking it's a striped array but no way a mirror is anything other than a second drive which is part of the SAME array as the first drive.
It looks like you have successfully created a mirrored array using the 2 drives (RAID 1). There's no way you have a striped array accross the 2 drives since they have to be the same size for that to work. Mirroring is OK with drives of different sizes. The trouble is, the extra space on the larger drive is just wasted - the total array space is limited to the size of the smaller drive.
Since the second drive is just a mirror and the extra space is always unusable, it's no surprise you can't see it in XP. You would never want to read or write specifically to the mirror.

Similar Messages

RAID BIOS sees HDD but XP does not

I have a K7T266Pro2-RU (MSI 6380) mobo with an 80 GB Maxtor HDD on IDE3 and a 250 GB WD on IDE4, using the latest FastTrak100 RAID drivers from the promise website. On IDE 1 and 2 I have 3 optical drives installed.
The problem is that while the RAID bios detects the HDD's just fine (as two separate Stripe 1+0 arrays) and boots fine off IDE3, XP does not see the other array and therefore the larger HDD is invisible. Of course I have SP1 installed with the LBA support, and when I try the HDD on one of the primary IDE channels it is recognised just fine by XP.
So one might think that the problem lies with the RAID driver.....except to throw another spanner in the works, I did have this working fine on the RAID controller, until I decided to re-install XP from scratch on the smaller HDD (larger HDD is full of data). But for some reason this fresh install will not recognise the second HDD on the RAID controller... whats killing me is that it did work beforehand, and now it wont. I cant think what I have missed to make this work....
Any ideas appreciated please

You really had it working before? Weird - it's not supposed to work! The Promise controller supports either 0 or 1. I can't see how you got 0+1.
And how can the second (bigger) HDD be the "other array" if you've got mirroring in there somewhere? OK, you can maybe fool a single drive into thinking it's a striped array but no way a mirror is anything other than a second drive which is part of the SAME array as the first drive.
It looks like you have successfully created a mirrored array using the 2 drives (RAID 1). There's no way you have a striped array accross the 2 drives since they have to be the same size for that to work. Mirroring is OK with drives of different sizes. The trouble is, the extra space on the larger drive is just wasted - the total array space is limited to the size of the smaller drive.
Since the second drive is just a mirror and the extra space is always unusable, it's no surprise you can't see it in XP. You would never want to read or write specifically to the mirror.

Installed a RAID card in my Dell Inspiron 3847. However, the RAID BIOS does not show up and I cannot install Windows 7 to it.

That is basically a summary of the problem The Dell Inspiron 3847 does not come with RAID, so I tried installing a PCI-express 1x RAID card. However, the RAID BIOS never shows up. The HDDs show up when I install the RAID controller driver in Windows 7 setup, but I cannot install Windows 7. I am using an IOCrest SY-PEX40008 RAID card with a Silicon Image Sil3124 chipset.
I tried pressing the hotkeys for the RAID BIOS listed in the card's manual, but it seems to just cause bootup to freeze. BIOS also does not seem to detect the RAID card HDDs as boot options.

%AppData% is the name of an environment variable.
On XP that variable points to C:\Documents and Settings\<user>\Application Data\
"Application Data" in XP/Win2K and "AppData" in Vista/Windows 7 are hidden folders, use %APPDATA% in the File name field
See http://kb.mozillazine.org/Show_hidden_files_and_folders
You can use Help > Troubleshooting Information > Profile Directory > Open Containing folder
See also [[Using the Troubleshooting Information page]]

Problems with IDE2 & 3 not detecting IDE device - going to RAID bios

hi
Ok well after many painstaking hours I finally managed to get the mobo(915G combo) up and running but encounter this problem.
IDE1 (third master) has hard drive on, this loads up ok
But if I connect my dvd rom and dvd writer as master & slave into either ide 2 or 3, I get the RAID bios utility load up and then only sometimes it lets me press the tab key, and all i can do is go in this circle.
If I unplug the cable and then attach a drive to my HDD as a slave this works fine. The mobo bios is currently set for optimized defaults. I know I could keep the drive as a slave on IDE 1 with the HDD but im going to be installing another HDD so will be using this as a slave, so that both HDD's are on one IDE and both drives are on a different IDE.
Can anyone help to try and resolve this?
Thanks

first off i would just like to say thanks for you help, everything is JUST ABOUT working!!
It does seem strange the instruction booklet informs you to put the primary boot device into IDE1 (blue socket) yet this doesnt qwork and you have to put the optical devices into this socket. Everything is now being recognised(within the bios) but I have now updated to XP with SP1 and the only problem i now face is that when the pc loads up it detects both ide HDD within the raid controllers BUT once into windows I can only see the c:/ not the secondary HDD. I dfid try to add this as a slave to the primary master HDD but got error on startup. I have since installed onto the 3rd IDE/RAID as a master and it is detected fine.
Within device manager in XP it shows as a device but i am unable to format the drive or save/map anything to it
Any further ideas?
Cheers
Paul

LAP-TOP HP PROBOOK 4330S hdd not show in the bios if I trouble shot show hdd not installed

LAP-TOP HP PROBOOK 4330S hdd not show in the bios if I trouble shot show hdd not installed

Hi ASMX,
Welcome to the HP forum!
Your HP Probook is a commercial product. I am sorry, but to get your issue more exposure, I would suggest posting it in the commercial forums, since this is a commercial product. You can do this at Commercial Forum/Notebook - HP ProBook, EliteBook, Compaq, Slate/Tablet PC, Armada, LTE.
In the mean time here is a link to your homepage.HP ProBook 6560b Notebook PC Support
I hope this helps.
Sparkles1
I work on behalf of HP
Please click “Accept as Solution ” if you feel my post solved your issue, it will help others find the solution.
Click the “Kudos, Thumbs Up" on the bottom right to say “Thanks” for helping!

Help me PLEASE kt4 raid bios

Ive already read through loads of posts but im not sure where im going wrong. i have a kt400 ultra and i use my pc as a HTPC, so as i fill a HDD with films i go out and buy another. now ive filled all my IDE1 and 2 ports and i just baught another 120gig maxtor drive and just wanna use it, for the time being on its own if possible in IDE3. Dont really care about performance just want it to work. Now ive plugged my hdd in and booted the machine , Gone in to the RAID BIOS and auto setup defined an array, witch went fine, re-booted and the drivers for the raid wouldent install properly it said CODE10 i beleave. So i restarted the machine to see if that sorts it and now the RAID BIOS has dissapeared. ive tried changing the IDE Cable and tried all the HDD jumper settings. i can get the bios to come up if i disconnect the hdd, boot, shutdown re-connect the hdd and boot again then its there and it sees the array but the drivers still wront start in winXP. Are u just not allowed to run one HDD on the raid in with case ill go out and buy anoter SATA drive, Or is this some weird fault.
Thanks for any replys
Lee

Surelly you will agree with me that the most common post about arrays, is the one that says that the array controller seems don´t like spare disks no matter what says the instructions. 8)

SATA RAID conflics with POMISE T3 RAID Bios

I've read quite a few of the RAID setup issues concerning the "Extra" RAID settings under "integrated peripherals" for the K9A2 Platinum. My problem seems to be a bit unique. I can't get both the SATA RAID and the Promise "Fast Track" to work together. If I enable the Extra RAID Controllers the Fastrack Bios does not recognize my SATA RAID.
This simply means that for some reason the motherboard SATA RAID conflicts or disables the PROMISE RAID Bios and vice versa. So I have not been able to activate my eSATA ports or use anything connected to the SATA5-6 ports without going into the CMOS and setting SATA DEVICES to IDE and then turning on the EXTRA Raid Controller under "Integrated Peripherals" in the CMOS. Unless I'm wrong. I am almost sure that this scenario is right.
The second issue is that I cannot get my ram to go in DUAL CHANNEL mode. But I will post that issue another time.
thx
Please Advise.
Ami Bios v1.4
K9A2 Platinum MB, 790FX,
AMD 9850 Black Edition,
8GB GSkill RAM (800Mhz),
Samsung 500GB SATA11 (x4),
Radeon HD 3870 512 MB Video,
Rosewill 950Watt PSU,
Pioneer DVD RW,
NEC DVD RW,
9-in-1 USB Card Reader
2 ext (USB/eSATA) hard Drives (eSATA will not work because these ports are controlled by the PROMISE T3 Bios)

With Vista Ultimate SP1 on my machine the USB Flasher Tool kept on crashing when the BIOS was at v 1.2 on the KA92 mainboard.
The DOS window came up fine but it appeared that every susequent module that was brought up for detecting the motherboard caught some kind of conlfict and terminated causing Vista to summon the program terminated message box. Eventually the dos prompt would state that it could not detect the motherboard and close. All in red text. This happened only when I flashed the BIOS with v1.2. I wanted to go back to 1.3 just to verify that the BIOS version was the cause and the only reason I got back to 1.3 or 1.4 easily was becaus it was backed up by the tool so all I had to do was rename the backup.bin file(s). Again everything went as expected with the USB Flasher Tool until I loaded the v1.2 BIOS. It could not even detect the mainboard.
The only reason I didn't need the tool anymore was that it backed up the versions of the bios for each time that I had flashed the bios previously.
Ami Bios v1.2
K9A2 Platinum MB, 790FX,
AMD 9850 Black Edition,
8GB GSkill RAM (800Mhz),
Samsung 500GB SATA2 (x4),
Radeon HD 3870 512 MB Video,
Rosewill 950Watt PSU,
Pioneer DVD RW,
NEC DVD RW,
9-in-1 USB Card Reader

Satellite A105 boot up only from HDD not from Floppy or CD-ROM

Even after C-MOS Set up, system is booting only from HDD not from Floppy or CD-ROM.
Is there any sepcific setting to set these controls in Satellite A-105 Model ?

Hi
Do you mean an external floppy drive and external CD-ROM drive or a one which is built-in?
If you want to boot from the internal CD-rom drive so you have 3 possibilities.
1. Changing the booting order in the BIOS to CD drive
2. pressing the C button immediately after notebook starting
3. pressing the F12 button immediately after notebook starting and choosing the CD drive
I think you should also be sure that you want to boot from the bootable CD.
If the CD is not bootable you will be not able to boot from the drive.
PS: If you want to boot from the floppy drive you can press instead of C button the U button

MS-6590 ATX Motherboard - SATA HDD not picked up by WinXP.

I have recently rebuilt an old PC which has a KT6 Delta/MS-6590 (v2.0) ATX Motherboard (AMD processor).
I have installed a new HDD - an ATA type - with WinXP as the booted operating system, and this is working fine, with this drive coming up as C:.
I have also installed a SATA drive which I was planning to set as D: However, although the SATA drive is being shown in the BIOS - and is therefore presumably running OK - once Windows has fired up the drive is not showing in Windows Explorer.
Do I somehow need to install a driver somewhere, or is it likely to be something in the BIOS that I have not set correctly?
Thanks,
Kevin

Quote from: Stu on 15-June-09, 00:52:22
EDIT: Svet, you just beat me to it!
:D
Quote from: Kev888 on 15-June-09, 00:59:07
Ah, that's the problem - it is not showing there - or indeed anywhere else - once Windows has fired up.
It is in any case formatted (NTFS).
Kevin
Setup HDD to work as Sata 1 {Normally via HDD jumper config}
Also make sure that the necessary Promise drivers are installed:
==> http://eu.msi.com/index.php?func=downloaddetail&type=driver&maincat_no=1&prod_no=557
VIA VT8237(R) SATA RAID Driver (For floppy driver) or Promise 20378 S-ATA RAID/Ultra Drivers

K9AG Neo2-DIgital: AMI BIOS v1.7 has no AHCI setting

Hi folks,
I recently upgraded my K9AG Neo2-Digital AMI BIOS from its original version (I don't remember what exactly) to v1.7 (the latest available on the MSI website). Before the upgrade I had three choices for the SATA mode: IDE, ACHI, and RAID. Now the setting is called "RAID Mode" and the only choices are: IDE, RAID.
What happened to the AHCI setting? I've been doing a lot of reading lately, and there doesn't seem to be a shortage of people having problems with AHCI and this board. Perhaps the latest BIOS simply disables it because of issues?
Anyway, it's a bit of a bummer because I finally got the latest Vista x64 AHCI drivers from both Microsoft (msahci.sys) and MSI (ahcix64s.sys) slipstreamed into my Vista setup DVD so I could try to do a repair install and get Vista to work in AHCI mode. I had originally installed it in IDE mode, and thought, hey why not try AHCI (or RAID in the future). Now I can't even choose AHCI mode in the BIOS. The original Vista install DVD wouldn't even load if I enabled AHCI in the BIOS - presumably due to the older msahci.sys drivers not supporting the SB600 at all.
I tried RAID mode, and the RAID BIOS detected my existing Vista drive as 1+0 JBOD, and the Vista install DVD detected the Vista installation on the drive (after loading the ahcix64s.sys driver), but I don't see any Vista repair installation option. This is off topic, but is there even such a thing in Vista? I know XP has a repair install that will fix the OS but leave all your apps and settings in tact.
I get the feeling that Vista and AHCI/RAID were just never meant to work with the SB600 :(
Any thoughts?
-Paul

sharfe, no need to hijack a 2 year old topic. Please start you're own new topic.
>> Please read and comply with the Forum Rules <<
>> Posting Guide <<

Snow Leopard on RAID 0, 1 remaining hdd, trying to install windows 7 on it

So i have snow leopard installed on a RAID 0. I also have a single remaining hdd that has my old Leopard on it. I want to install windows 7 on that remaining internal hdd but bootcamp won't allow me to run setup because it says it doesn't support RAIDs, even though i'm not trying to install windows on the RAID.
Can someone please help me out here? Someone on another forum suggested an AHCI, but i have no experience with them.

Hatter speaks in tongues. --actually phrases that often require interpretation. I think he means that you have 3 drives, 1, 2, and 3 and that 1 and 2 are your RAID drives. He says use Disk Utility to format 3 as Master Boot Record and MSDOS--which doesn't mean much to me. But, looking at the formatting options in Disk Utility might clarify things. I would have though that the appropriate formatting would be NTSF. Regardless, next he says disconnect or actually remove 1 and 2 and then start up to the Win7 DVD to install Win7 on 3. On a PC this step would make perfect sense to me, but I have never disconnected and installed on a Mac. I am not sure how you choose your boot drive having disconnected and installed. Perhaps all you have to do is use the option key when starting up.

6730 (655 Max-FISR) RAID BIOS menu - how to enter?

Hey all,
according to http://www.msi.com.tw/program/products/mainboard/mbd/pro_mbd_detail.php?UID=424, this model (6730) should have RAID 0 or 1 support.
But I can't quite figure out anything in the BIOS menu of it that has to do with this. So I installed two Serial ATA hdds onto my motherboard, and they are being detected just fine, no problem at all. So according to the Serial ATA menu, I start installing win2000 and do the F6 and S stuff, loading the drivers for the SATA drives. Then when I get to where it asks me where to install windows too, I get TWO harddrives listed for me to choose from, not one (I'm trying to do RAID 0 btw).
Well coming to think about it, that's logical: I did not set ANYTHING in the BIOS about the drives being in RAID -- I read some guides online on how to install RAID drives -- supposedly you press Ctrl-F to enter the BIOS for RAID controller and set RAID0, RAID1 and those stuff there. Where is this RAID BIOS menu for the MS-6730 motherboard?
most threads I read here, when people talk about doing RAID, most people get through the step "configure the hdds as RAID 0/1" really quickly by a mention with a sentence -- I think that's the part I'm stuck on. Maybe my question should be... how do I enter the RAID BIOS for this motherboard at all? The manuals that came with the mobo don't really have anything on RAID *at all*...
[edit]
btw... I'm new to RAID arrays, so I'm not sure if I'm doing this right. I put my two (identical) hdds one connected to ser1 and one connected to ser2, on the motherboard. is that how you are supposed to do it? they are WD Caviar SATA drives (120gb) btw. jumpers shouldn't be a problem, the WD web site says for a SATA drive, the jumpers are only for power settings, no master/slave things.
Thanks for any help.

http://wdc.custhelp.com/cgi-bin/wdc.cfg/php/enduser/std_adp.php?p_sid=CxTASuHg&p_lva=&p_faqid=958&p_created=1050530240&%20p_sp=cF9zcmNoPTEmcF9ncmlkc29ydD0mcF9yb3dfY250PTImcF9zZWFyY2hfdGV4dD1qdW1wZXImcF9zZWFyY2hfdHlwZT00JnB
fcHJvZF9sdmwxPTk1JnBfcHJvZF9sdmwyPX5hbn l_JnBfY2F0X2x2bDE9fmFueX4mcF9zb3J0X2J5P WRmbHQmcF9wYWdlPTE*&p_li=
well assuming you have connected the sata lead and a power connector all i can think is your psu is very poor on the 12v line,how many amps does it give
you might try the jumper bit in the link as well
you will have to paste the full link in

Hdd not picked up at right size

im sorry to post this here, im sure there a simple and easy answer but i am not in an environment to find that out right now so ill ask and hope i get a response.
My board detects the hdd as 180gb western digital, im using an 875p neo fis2r and it wont show the drive as 180 but 128binary. im wondering if this is a bios issue and i should update the bios. I am not able to find out any of this information for myself at this time and i was wondering if someone would kindly help. thanks

its set as a master. im using the bios that came with the board. when i first intalled the operating system is shows it as 137...kbytes indicating 128 gb and once the operating system (winxp) has been loaded it shows as 128. i thought it would be a bios issue since it detected it as 128gb before the operating system was installed and i read that it was a problem with 48bit lba and the fix was to update the operating system to a current service pack which had the fix. I tried updating but that didnt change anything, i also tried the registry fix. the bios detects the drive as model wd180jb and with a capacity of 180, however all other instances indicate the capacity as 128gb. i doubt it is an issue with the drive since its new and the operating system(s) because when i boot from the windows cd it shows the partition as 137...k(128gb). i tried both win2k-pro and winxp-pro.

Solaris possibly preventing RAID BIOS launch

Hello
I have installed a STLab A-230 2-Channel Serial ATA & ATA-133 RAID Combo and tried to boot into its RAID BIOS with no luck. The initial loading menu quickly switches to the multi-boot menu where you select to boot into Solaris or another OS. I am supposed to press Ctrl-Z, but it just switches to the boot menu without bringing up RAID BIOS. Please let me know if this would be to do with the installed Solaris and its uninstallation would solve it.
Regards,
Dai

You can use SMC for other purposes but it won't help your with RAID.
Sol 10 1/06 has raidctl which handles LSI1030 and LSI1064 RAID�enabled controllers (from raidctl(1M)).
Some of the PERCs (most?) are LSI but I don't know if they are chipsets used by your PoweEdge (I doubt it).
Generally you can break it down like this for x86:
If you are using hardware RAID with Solaris 10 x86 you have to use pre-Solaris (i.e. on the RAID controller) managment or hope that the manufacturer of the device has a Solaris managment agent/interface (good luck).
The only exception to this that I know of is the RAID that comes with V20z, V40z, X4100, X4200.
Otherwise you will want to go with SVM or VxVM and manage RAID within Solaris (software RAID).
SMC etc are only going to show you stuff if SVM is involved and VxVM has its own interface, otherwise the disks are controlled by PERC and just hanging out as far as Solaris is concerned.
Hope this helps.

Accessing Intel Raid Bios Utility

I've added a Maxtor 160gig Sata hdd to my motherboard and have been trying to set it up, but when i try and press CTRL + I nothing happens, it just continues to load up the bios and o/s.

Quote
Originally posted by Wolfspyder
I've added a Maxtor 160gig Sata hdd to my motherboard and have been trying to set it up, but when i try and press CTRL + I nothing happens, it just continues to load up the bios and o/s.
Set it up how? A single drive or are you preparing it for a Raid?
Which connector is it attached to?
What other drives do you have and where are they attached?
If you aren't interested in running a Raid then there's no need to access the Raid Bios utility. It will only be enabled if you have set the "Configure SATA As Raid" for the Intel controller in the Bios.
In WinXP Device Manager, it's normal for the OS to identify the extra SATA ports on the 865/875 chipsets as another primary and secondary IDE controller.
Reading THE FAQ POST (specifically #5 HDD's) would also be of interest to you.

RAID BIOS controlling Sytem HDD, not AHCI

Similar Messages

Maybe you are looking for