Optiplex 755, RAID 1, BSOD, Clone Disk

Hi Darien,

 

Well, you were very close to having this configuration working without any problems.  However, there's a step that you'll need to do before performing the cloning.

 

First of all..... 

Getting the BSOD to show...

Press "F8" during the startup for the OS Startup Menu.  Scroll down to the option "disable automatic restart upon error" or somethig close to that.

 

Then, allow the system to boot normally.  You'll notice the BSOD actually states STOP error 0x0000007b (this means that the controller mode being used does not match the controller current driver in the OS)

 

You see when using the single drive the controller is in either ATA or AHCI mode.  The PnP code on the controller will change between all 3 settings (including RAID mode)

 

So, now back to your dilemma...

 

1. Go ahead and rebuild the array to delete the data. (eliminate probs booting with two OS's)

2. Boot the single drive with array enabled.

3. Allow Windows to enumerate the array (This will load the RAID driver for the new controller mode).

4. After the driver installs reboot to make sure the array is seen in Windows properly.

5. Clone the single drive to the newly created array.

6. When booting the first time MAKE SURE THE SINGLE DRIVE IS DISCONNECTED (per step 1 - This will allow Windows to renumerate the new array with the OS installed on it)

 

After booting a couple of times, it will be safe to reattach the single drive.  The file system should just see the single as another drive then.  Then play with the boot order to boot your array.

Hi Ryanh, thanks a lot for your ideas. When I first read your idea I thought It was perfect. Unfortunately it didn't work, some problem with the DELL behavior. Here is why?

 

Apparently, the Optiplex 755 cannot boot from the SATA drive, when there is also a RAID array in the computer. It is really unexpected to me, but there was no way for me to make it start from the SATA drive if the RAID was also recognized.  The Intel Matrix Storage Manager kicks in, it shows: Raid Volumes: "my Raid Array", Physical Disks "1. The SATA drive, and 2 and 3. the other two disks identifying them correctly as part of a RAID 1 array" Yet, the next message is "Error Loading Opperative System"

 

the way I have them connected right now (I tried other way, with same results) is in the SATA-0 port is my HDD, in SATA-1 is the DVD-ROM, in SATA-2 and 3, the other two HDD's part of the RAID-1 Array.

 

If I disable SATA-2 and 3. the computer starts with no problem (I am in the RAID/ACHI mode) from the SATA HDD, but if there is a RAID volume in the system it always says "Error loading opperative system".

 

I tried with the SATA drive being the only device in the boot list (defined in the BIOS)

 

I tried pressing F-12 during Startup and it shows both the RAID-1, and the SATA HDD as posibilities, I choose the SATA HDD, and still says "error loading opperative system".

 

Yet, if I disable the SATA-2 and 3 (i.e. the raid drives) or physically disconnect drives, the SATA HDD starts at once with no problem.

 

I played with the Disk mode in the BiOS. I tried obviously the RAID/ACHI mode, I tried the RAID/ATA mode (which I didn't expected to work anyway, since I don't have IDE HDD's), I tried the Legacy mode. I didn't try the "only RAID" mode since the non-raid volume probably would not work.

 

Anyway, the thing is that apparently I cannot start the computer from the SATA HDD, if the RAID volume was recognized and present in the system. I have not idea as to why...

 

Again, thanks for your help. If you have an idea of what can be the issue please let me know or at least give me a hint of what could be the issue. Thank you.

 

Darien

 

p.s. by the way, F8 does nothing in my machine. I have F2 for Bios, F12 for boot, CTRL-P for MEBx, and now CTRL-I for Raid. I couldn't find the "disable automatic restart upon error" in the Bios or any other place. I wonder. Thanks

 

 

Chcastan,

 

The "F8" option is just a keystroke you press after the RAID rom loads, but before the Windows Logo screen.  It will invoke the startup menu.

 

As far as the booting problem.  Did you rebuild the RAID array (deleting any previous data from the original cloning) first?

 

Then boot the SATA drive with the RAID array attached?

 

Its important that you do it in that order otherwise the cloned OS on the new RAID will cause Windows some grief when booting and/or operating in the GUI environment.

 

Once the SATA enters Windows with the (now blank) RAID array, the driver will load for the array onto the original SATA drive.  After that is complete then you can clone the OS from the single to the RAID.

 

After the cloning you boot only the array.  If you leave the SATA connected and try booting the array from the boot menu Windows will see both volumes and try to configure with both together causing havoc.

Hi Ryan, I do not have the F8 option. The only thing the system shows to me as an option is CTRL-I, which gets me in the Intel Matrix Storage Manager.

 

That sayd, I did delete the RAID array before I atempted to run the RAID-1 and SATA HDD  together. I just tried again, and I noticed something extra. As I said before, if the system sees my RAID-1 array, even if there is another HDD, apparently the system attempts to start ONLY from the RAID-1.

 

However, this time I noticed one more thing. Inside the Intel Matrix Storage Manager (IMSM), I erased the RAID-1 array, such that the system was showing 3 NON-RAID hard drives. Then I exited the IMSM and the system still did NOT start up. It gave me the same error as before: "Error Loading Opperating System". However if I then restart the computer with no other changes (nor entering the BIOS), then the system started just fine, and recognized the 3 harddrives (althought the 2 that used to be part of the array don't have letters assigned).

 

This to me points to the IMSM as the culprit of my problems. Apparently it will only allow RAID start up, if it is loaded at all. If there are no RAID-ready volumes, the IMSM does not load and the computer behaves as I would expect.

 

Following these ideas, I found this place in Intel:

 

http://www.intel.com/support/chipsets/imst/sb/CS-015988.htm

 

Apparently that warning message at the top is the problem I am having (BSOD + Reboot). Except that it is too easy for them to say it is not supported. I will not reinstall my operative system from scratch, there are just way too many things configured and working on my system, I can't afford the time and effort to do that.

 

Now my question is this: Can I install the IMSM driver in my current SATA HDD manually (runing setup), such that once I clone its contents to the RAID-1 array it will be able to function properly? I am afraid to try until I can get another HDD to have a backup just in case

 

I guess other way to ask the same is: Can my HDD function normally with "IDE ATA/ATAPI Controllers" being present at the same time as "SCSI and RAID Controllers" in the Device Manager?? I wonder if I can install the IMSM in my current drive.

 

 

 

If nothing else works, could I do a software level RAID array using Windows XP, and clone to that ARRAY probably without the issues of using the IMSM?

 

 

Thanks for any ideas.

 

 Darien

 

 

 

 

Darien,

 

Firstly, you won't see an "F8" option.  You need only to start pressing "F8" during the Dell Logo.  The system will show the Intel RAID Rom, then show the Startup menu.  (Sorry, I didn't clarify the "F8" thing well enough before)

 

I'm still curious about your boot sequence.  I'm pretty sure that if the single drive is before the RAID array it should boot normally.

 

As far as loading the driver...

 

If your BIOS options have a "RAID on" selection for then you don't really have to connect the drives (for array) yet.  With the "RAID on" selection the controller setting for the other drives should be in RAID mode and the operating system should detect that change and load the driver.

 

Also, your "Missing operating system" message could be that even though you removed the RAID 1 array, it may only be removing the "metadata" and not the previously ghosted OS.  If you remove a RAID 0 array then the data would be gone on both drives.

Hi Ryan, yes I finally understood the F8. Funny I neved had used that before. Now I can see the error and it is exactly as you said.

 

About the RAID1 I still can't make it work. I tried installing WinXP in the array and then restoring a full backup of my system done under windows XP but it didn't work. The installation of XP was ok on teh new RAID, but once I restored all my info into that new drive no programs were installed, or anything else. I don't need just copy files, I could do that any day. I need to make a clone of the system so that in the new RAID array I have all my programs, files, configuration, etc.

 

I tried many things, but nothing works. I am pretty sure the problem is that the installation currently in the SATA HDD does not have a driver for the RAID mode.  But I just do not know how to install the RAID controller to the SATA HDD while it is still single, so that once I clone using the Symantec Ghost I could start from the new harddrive (RAID 1 Array).

 

Ho to install a RAID controller into the current (non-raid) drive? How to force it to be there,ready and available when the operative system tries to boot from that disk?

 

Darien

Darien,

 

Well that's going to depend on the system.  The only way I know without trying to manipulate the drivers into the already installed OS is dependent upon how the BIOS manages each hard drive port. 

 

For instance, my 720 allows me to configure a single port to RAID ON, just ON, or OFF.  With that I can boot my original drive with just ON, add two additional drives configured to RAID ON and configure the array on the next boot.  Once the array is created I can boot my drive with the array attached.  Windows will pick the array as "New hardware" and load drivers for it.  Now that the drivers are loaded, I can Ghost my single drive to the array.

 

After the cloning is complete I remove my single drive (to eliminate OS confusion) and boot to the array.  Now that the driver is installed it should boot fine, get into Windows and detect a change in hardware (I'm now booting the array and there's no other drive).  Now the enumeration is complete and I'm up and running on the RAID.  I can add the single drive now and use it for additional storage or whatever.

 

Now, that's all great, but if your system has a "blanket" setting for the SATA MODE then you're probably out of luck.  You would need to boot your drive (in whatever mode it is) and be able to detect the RAID (which wouldn't really be there if your mode covers "all at once")

 

I'll check to see if the 755 could work.

Darien,

 

I'm really not sure if it will work, but you could try it this way.

 

1. Make note of what mode your original drive is in (RAID auto/ATA, RAID auto/AHCI)

2. Take your original drive out of the system and install two drives on port 2 & 3.

3. Set the "SATA Operation Mode" to "RAID ON".

4. Create your Array.

5. Add your original drive back in on port 0 and change SATA Operation Mode to ("RAID auto/???" <-- whichever mode your drive was in)

 

Try to boot your system configured that way.  If it boots then you're in luck and the driver should load.  Once that's done then you can perform the Ghost.

 

If it doesn't work then I'll have to see if there's a way to force the RAID driver into the OS without RAID being enabled.  That might work too (I've done that with ATA and AHCI mode)

Hi Ryan, thanks for answering. Unfortunatly with your last suggestion I am pretty sure it will not work. As I mentioned before, if there is raid array in the system that system will not start up from SATA, even when the system "sees" all harddrives (the SATA and the RAID1), and even when I press F12 and manually tell it to start up from the correct (SATA) hard disk (I tried several in several "sata operating mode"). Trying the working SATA drive and the new RAID-1 always tells me the same message "error loading opperative system". I don't understand why that is, apparently the Intel Matrix Storage Manager does not allow the hybrid mode to start from SATA (but yes the other way around, startup from RAID with SATA showing). Both HDD and RAID show just fine in the startup screen (where I could press CTRL-I).

 

Actually, if you remember this was your very first suggestion about how to fix the problem. It makes a lot of sense to me, it is just that I cannot implement it. I just does not allow me to start from the SATA HDD if there is a RAID array in the computer...

 

That said, if you find a way to force the RAID driver into the OS some other way, please let me know. I am ready to try that. By the way, I also downloaded the Intel Matrix Storage Manager and installed it into my current SATA drive. I was looking for the option "make a RAID array" which apparently is available if I had a raid ready array, but of course my system is not RAID ready and I cannot find the option.

 

Please if you know a way to try to force the driver to my current disk, please let me know. I am close to giving up. I don't know what else to try. Thanks a lot.

 

Darien 

 

That winking happy face was not meant to be there. I don't know where it came from