Overclock.net banner

1 - 15 of 15 Posts

·
Registered
Joined
·
122 Posts
Discussion Starter · #1 ·
Hello people. I have got a little concern that I would like to share with you.
redface.gif


Summary
Reverting from RAID back to AHCI in BIOS and the 2 HDD are still running at RAID0 with the originally given "RAID0xxx" name. Is this a normal behavior?

The story in detail
It is an Asus p8z68 Deluxe Motherboard....
I have selected "RAID" in the Bios, then restarted and then configured RAID0 on the 2 hard drives leaving out the SSD....
Then I couldn't start the system up....Blue screens....
Then I revert setting of the BIOS back to "AHCI" and SSD worked as expected without blue screens.
The difference this time was that not only the system booted without problems but also the 2 hard drives which were configured as RAID0 in the previously BIOS RAID mode, were still running in RAID0 even if setting had been changed back to AHCI !

The Question
Is it normal that you set BIOS to work in RAID then set the 2HDD as RAID0, and then when you revert back to AHCI in BIOS the 2HDD are still working?????

Thanks in advance
 

·
Premium Member
Joined
·
1,871 Posts
Make sure that you have the 3 drives plugged into the correct SATA ports.

You have two different SATA controllers on your Motherboard capable of RAID. The Intel z68 PCH (SATA ports 0-5) and a seperate Marvel Controller (SATA ports 7&8). Which RAID OPROM did you set the RAID up in, and where are the drives attached on the motherboard?

You can change the SATA mode for the Intel controller to AHCI, and still maintain a RAID array on the Marvel Controller.
 

·
Registered
Joined
·
122 Posts
Discussion Starter · #3 ·
Dear xandypx,

Thanks for the reply, but I am pretty sure I have everything connected to the points 9 and 10 in the picture below which are INTEL SATA connectors.

700

Any ideas why my 2 HDD are still running at RAID0 ?
 

·
Premium Member
Joined
·
1,871 Posts
Sorry, more questions than answers at this point.

When you first POST your computer, does the Intel RAID OPROM screen pop up? ie. Press - Ctrl-I - to enter RAID utility?

I assume that where you are still "seeing" the RAID Array, is once you are in windows, correct? Do you have Intel Rapid Storage Technology (IRST) installed on your computer?

What does your UEFI show the HDDs as. Meaning, if you look at the PCH Sata configuration, it will show the individual drives (hopefully), and where they are connected to the PCH. Looking further in the UEFI, at the Boot Tab, and into the menu for the Hard Disk BBS priorities, does the RAID array show up here, or do the individual drives show?

Hopefully the answers to these questions may help to figure out whats going on.
 

·
Registered
Joined
·
122 Posts
Discussion Starter · #5 ·
Dear xandypx thank you for your support.

Your questions put me in a right direction I think.
  • When I POST, neither Intel RAID OPROM, Nor "Press - Ctrl-I - to enter RAID utility" appears on the screen
  • Yes, I see the Array only when I am in Windows. In the windows menu I go to: "Computer" right click on the disk then "Properties"/ "Hardware" tab and I get the name that I have initially given to the disk in the BIOS. (i7-Raid0)
  • Yes, I have Intel Rapid Storage Technology (IRST) installed.
  • "Advanced" Tab / "PCH Sata configuration" Menu shows the HDDs individually
  • "Boot" Tab / "Hard Disk BBS priorities" Menu also shows the HDDs individually (No RAID)
Again, I would like to thank you for your time.
 

·
Premium Member
Joined
·
1,871 Posts
Quote:
Originally Posted by Ahanasis View Post

Dear xandypx thank you for your support.

Your questions put me in a right direction I think.
  • When I POST, neither Intel RAID OPROM, Nor "Press - Ctrl-I - to enter RAID utility" appears on the screen
  • Yes, I see the Array only when I am in Windows. In the windows menu I go to: "Computer" right click on the disk then "Properties"/ "Hardware" tab and I get the name that I have initially given to the disk in the BIOS. (i7-Raid0)
  • Yes, I have Intel Rapid Storage Technology (IRST) installed.
  • "Advanced" Tab / "PCH Sata configuration" Menu shows the HDDs individually
  • "Boot" Tab / "Hard Disk BBS priorities" Menu also shows the HDDs individually (No RAID)
Again, I would like to thank you for your time.
This may work.

It's very possibly IRST is putting the RAID back together in software. On your taskbar, you should have an icon for IRST (a little silver looking HDD with a check mark on it). Right click on it and select "open application". Accept the UAC prompt.

On the "manage" screen, select the RAID ARRAY you are trying to get rid of. On the left side of the application, the screen (what is shown) should change. Hopefully you have an option to "Delete Volume". If you do, make that selection by clicking on the blue words. You will be prompted that deleting the volume will make data on the ARRAY unrecoverable.

If this is successful, if you start "disk management" you should now see two HDD that are listed as "unallocated". you can then format them as simple disk drives.

If you are unsuccessful, post back... we'll try something else.
 

·
Registered
Joined
·
122 Posts
Discussion Starter · #7 ·
Really thanks.

I did as you said. It looks like there is no RAID array shown in IRST. This is the result:

362

But when I go to my computer and properties this is what I get:

389

I assure you in BIOS it is all in AHCI mode.....

If you need any other info please let me know.....

REP+ given !!!!
 

·
Premium Member
Joined
·
1,871 Posts
That's the strangest thing I've ever seen.

Take a look at the drives in windows 7 "disk management".

Click your start globe, and in the search box, type "disk management". At the top, select the option to "Create and format hard disk partitions".

I'm wondering if possibly the "system reserved" partition is on the RAID array, and that's what's holding them together, although from what you've posted in your screen shot... there just shouldn't be an ARRAY on your system.

Post a screen shot of the disk management window, and we'll go from there. I assume you have already backed up the files you would need that were on the array. Make sure you capture the lower part of the disk management window in your screen shot.

Depending on what is shown in Disk Management, I think you can use the command line utility "DiskPart" to get rid of the Array, but we need to make sure the system partition is not there, because if it is, and we delete the Array... Your system won't boot. If it is, we'll get it moved to your SSD before cleaning the two 500GB drives.
 

·
Premium Member
Joined
·
1,871 Posts
Again, as I said before.. really weird.

EDIT: But a quick question before you follow the below steps. Your screenie of disk management doesn't show the partition "style", but I notice that your "system" partition is an EFI partition... Are your drives initialized as GPT? If the drives initialize as GPT, rather than MBR, this can be causing your problem. GPT disks are "self identifying", and this identification can be telling your system that the two drives are actually part of an array. If they are configured as GPT, the GPT attributes may first need to be re-written to the drives, or the drives converted to MBR before windows will actually allow you to perform the following steps. You would have had to actively done this when you initially formatted the drives, as the standard initialization of new drives is MBR. Do you recall converting them (actually the ARRAY) to GPT?

In disk management, you can change the "view" of the top pane, and select "disk list" to show the drive "style" column of your attached drives.


ok, disk management has them as an array also, so the only way to fix this is to reformat the two drives seperately. You are going to need to physically disconnect one of the two drives from your system. All you need to do is pull its SATA connector from the motherboard. there is no need to remove the drive from the case, or disconnect its power plug.

Hopefully (and i don't see why it shouldn't) your windows installation will boot, as the files required are all on your SSD.

Once into windows, go into disk management, and select the (what should now be 500GB; effective 465GB), drive that is still attached.

The drive "should" show up as unallocated, but I'm curious as to how it is actually reported.

Right click on the drive in the lower pane, and select format, and then proceed to format it as a "simple" disk. If the disk shows up as anything else but unallocated, you may need to first select "delete volume" before you can format it, but try the format command first. If you do need to delete the volume, the bar above the disk should turn from blue to black and then show as unallocated. You may (but may not) need to reinitialize the drive. You can then proceed with the formatting steps. Don't forget to assign the drive a letter if the formatting doesn't assign one itself.

When this is complete, shut down your system... reattach the second drive, boot the computer, and follow the same steps to format the second drive. That should take care of the problem.

If for some reason you can't do this in disk management, post back, and I'll walk you through how to do it with the DiskPart command line utility.
 

·
Registered
Joined
·
122 Posts
Discussion Starter · #11 ·
Some google research below......

Is this probably because the OS is loading a RAID driver! and when switching to non RAID mode, it will BSOD ?

When switching to AHCI mode, there is no RAID support. RAID support is mostly provided by the OS and drivers, often called fake raid controller.

Probably this is the reason why... ?????
 

·
Premium Member
Joined
·
1,871 Posts
I actually can't speculate on the exact reason why, I just don't know.

The Intel RAID driver actually has the AHCI driver incorporated into it. The RAID driver is used for the drives that in RAID, and the AHCI driver is used by drives that are plugged into the same controller (in your case the z68 PCH), but are not members of the ARRAY. Something is holding the ARRAY together as far as Windows is concerned. The "fake RAID" (software driven) that you mention, is what I initially thought IRST was doing, until you posted the screen shot. It wasn't that... I've never heard of, or seen Windows hold a RAID ARRAY together.

And you are correct... I don't know why no BSOD when accessing the ARRAY. the OS doesn't need the array to function, so I can see Windows loading and operating without issue.

But as I mentioned earlier, your issue is very strange.

EDIT: Just a thought... that if you don't mind, I'd like you to test. It will set everything you have changed in your UEFI back to default settings, so I understand if you choose not to do it.

I am wondering if somehow the UEFI itself is causing the RAID to stay together. A UEFI, unlike a traditional BIOS, is a mini OS on its own. I think if I'm correct, you are booting using Windows Boot Manager, rather than booting directly from your SSD. Is that correct? If so, I'm wondering if an entry exists in the Boot manager that is causing this. My though is to reset the CMOS/BIOS/UEFI on your motherboard. It is as simple as shutting down your system, and pushing the "Clear CMOS" button on the back panel of your PC. I beleive the button on your motherboard is locate directly above the audio out connectors of the back panel.
 

·
Registered
Joined
·
1 Posts
Hi

I am having the exact same issue as previously described. Only one thing differs. I'm using a Rampage IV Formula. I've downloaded the latest Intel RST drivers from the asus site for that board (dated 4/16). I have windows installed to an SSD and created a raid using two 1.5 TB HDDs. However, when the bios is set to RAID I blue screen and cannot boot into windows. With it set to ACHI I can boot into windows and it seems as if the raid array is recognized. Even device manager shows it. I have one issue different than the above person. The IAStorUI will not load and when I boot I cannot access the cntr+I menu. However, when bios is set to raid, I can access the cntrl+I menu.

Something really weird is going on. I'm glad to see I was not the only with this problem (if it even is that.) I'm curious if the above poster found a solution.
 

·
Registered
Joined
·
1 Posts
Again, same problem this time on a P9x79 motherboard.

I was using RAID1 on two hard drives (non boot disk), and then one day my EFI settings got reset. I didn't realize at first because the computer booted up just fine, and my drives still showed up as a single RAID volume. Read Write speeds are typical of two hard drives on RAID1.

The Ctrl+I menu does not appear at all at boot time, and SATA mode is set to AHCI in EFI.

Problem is now I want to put it back into mirrored mode, and I can't because Ctrl+I doesn't show up. If I set SATA mode back to RAID in EFI, I can enter the Ctrl+I menu at boot time but all disks are set to Non Raid volumes. Intel RST config crashes on launch.

This is the second time this has happened to me. Going to try moving data off the drives and formatting them, but it will take a while.
 

·
Registered
Joined
·
11 Posts
same thing here can not get into Raid option try 10 times and just not there i guess did it before but now cannot access raid that all with the keys ctrl I don't know what to do get a new board really wanted that Raid to work .ray

Asus p8z68-v pro with I7 3400 to 4600

2ssd

radeon 6770
 
1 - 15 of 15 Posts
Top