Personally since you already have lost all the data. Break the Array and do as I instructed. Break Array by press CTR I at boot up. Then install as I instructed, on my previous posting. At the end your be RAID ready and can migrate to RAID 1. I did that initially with my system, was able to migrate to RAID 1 with np. Also did the the same on a re-load about 9 months ago.
Thanks for the tips, TomXPS. The problem I seem to be having involves the fact that I cannot boot to any device after creating the RAID. I have created the RAID driver disk as you mention, but I can't get far enough in the process to use it. Here are the steps I followed:
1. Reset the RAID
2. Reboot re-create the RAID (RAID 1 using the two primary drives on ports SATA-0 and SATA-1)
3. Reboot and set appropriate boot device order in BIOS (the RAID is the first disc listed after the USB floppy and USB CD-ROM)
4. Reboot and attempt to boot to the Recovery Disc. The drive spins up and I get the "Setup is inspecting your computer's hardware configuration..." message. At this point the CD spins back down and the machine hangs.
More info:
- I have two other drives installed in SATA-2 and SATA-3. They are standalone drives and are not being used in the array.
- I am using Intel RAID version 4.0.0.6211, which I believe is bundled with BIOS update A07.
I noticed that Intel has released version 5.1. Is that available for the Dell machines?
I may end up calling into Dell support for this one.
Thanks for you help, Tom. I've already tried installing to a single disk, followed by a migration to RAID 1, which gave me the same problems as with creating a RAID from scratch. In RAID mode, the machine will not boot to any media. I don't see why a missing driver would cause floppy and CD-ROM's to fail to boot.
I gave Dell a call, and they're sending a new mobo. I have my doubts, but will give it a try. In the meantime, I may try the single disk installation/migration path again.
Problem resolved (sort of)! A new motherboard did not do the trick, as I suspected. It ends up that there was a conflict between my IDE controller and the Intel RAID ROM. Once I pulled out the Promise Ultra 100 TX2 card used to support an older EIDE drive, things worked beautifully. I was then able to create the RAID before installing Windows.
One thing to note: The F6 install DID NOT work. Using the driver from the floppy disc caused a stop error on my machine. Luckily, I'm using the XP SP2 recovery disc which contained drivers for the Intel Controller. Those drivers DID work and I was able to install successfully.
After installing, I immediately installed the Intel Chipset drivers followed by various updates. Things are now running smoothly.
Now I need to figure out how to hook up my EIDE drive without using the Promise controller. I want that data! I have some leftover IDE/SATA cards from the Maxtor drives that I bought...
Thanks for your persistence, Tom. I appreciate your help.
Thanks for the update. Always good when someone responds with the resolution to the problem, makes it easier as contributors to know that you gave information that was helpfull to resolve the issue.
TomXPS
1.3K Posts
0
October 3rd, 2005 23:00
On my XPS gen 2, I have reloaded once and broke my RAID 1 before and hand.
The process to load was as follows: (Note your BIOS has to be setup with the RAID on) in my case it was SATA RAID=YES.
I never have tried setting up the RAID 1 from BIOS and then load the system, see no advantage for RAID 1, the migration task worked well.
TomXPS
1.3K Posts
0
October 4th, 2005 02:00
Personally since you already have lost all the data. Break the Array and do as I instructed. Break Array by press CTR I at boot up. Then install as I instructed, on my previous posting. At the end your be RAID ready and can migrate to RAID 1. I did that initially with my system, was able to migrate to RAID 1 with np. Also did the the same on a re-load about 9 months ago.
brad77
1 Rookie
•
6 Posts
0
October 4th, 2005 02:00
1. Reset the RAID
2. Reboot re-create the RAID (RAID 1 using the two primary drives on ports SATA-0 and SATA-1)
3. Reboot and set appropriate boot device order in BIOS (the RAID is the first disc listed after the USB floppy and USB CD-ROM)
4. Reboot and attempt to boot to the Recovery Disc. The drive spins up and I get the "Setup is inspecting your computer's hardware configuration..." message. At this point the CD spins back down and the machine hangs.
More info:
- I have two other drives installed in SATA-2 and SATA-3. They are standalone drives and are not being used in the array.
- I am using Intel RAID version 4.0.0.6211, which I believe is bundled with BIOS update A07.
I noticed that Intel has released version 5.1. Is that available for the Dell machines?
I may end up calling into Dell support for this one.
Thanks,
Brad
brad77
1 Rookie
•
6 Posts
0
October 4th, 2005 14:00
I gave Dell a call, and they're sending a new mobo. I have my doubts, but will give it a try. In the meantime, I may try the single disk installation/migration path again.
I'll let you know what I find.
Brad
TomXPS
1.3K Posts
0
October 4th, 2005 16:00
Do you have your boot order set properly. Have not gone into my BIOS lately but seems like I have my CD and Floopy destinated first as my boot order.
brad77
1 Rookie
•
6 Posts
0
October 6th, 2005 16:00
One thing to note: The F6 install DID NOT work. Using the driver from the floppy disc caused a stop error on my machine. Luckily, I'm using the XP SP2 recovery disc which contained drivers for the Intel Controller. Those drivers DID work and I was able to install successfully.
After installing, I immediately installed the Intel Chipset drivers followed by various updates. Things are now running smoothly.
Now I need to figure out how to hook up my EIDE drive without using the Promise controller. I want that data! I have some leftover IDE/SATA cards from the Maxtor drives that I bought...
Thanks for your persistence, Tom. I appreciate your help.
Brad
TomXPS
1.3K Posts
0
October 6th, 2005 22:00
Thanks for the update. Always good when someone responds with the resolution to the problem, makes it easier as contributors to know that you gave information that was helpfull to resolve the issue.
Thanks again for the update.
Tom