mobo; ASUS crosshair
memory; Buffalo Firestix PYRO pc2-8500 fsx1066d2c-1g
2x250GB SataII WD in RAID-1
1-DvD RW
1-CD-RW
xp pro sp2
Very Experienced Programmer/Technician
Hello all, my memory went bad, and caused my bios to lockup. i reset my bios in desperation. didnt get it to boot, so i sent my memory to manufacturer and waited 2 weeks. they sent me some splendid new memory, i put it in, and viola, computer boots right up.
right away im thinking all is normal, but then somedriver installation prompts come up. so as i always do, i click next, next, continue anyway, blah blah.
one of the drivers that needed to install was a generic volume for the hard drive, this struck my attention, but i went ahead and installed the driver, then for the other disk the same thing, it came up again, and i installed the other generic i believe. and a floppy disk controller came up, and wouldnt install because couldnt find the driver on the system. big deal, not a priority now anyway.
PROBLEM;
The problem came in when i looked in "my computer" and noticed a C drive, and a F drive, both 250GB, oh ****. the RAID array was defunct!! I immediately realized that the array was reset when i reset the bios, atleast i believe the CMOS reset affects the NVIDIA raid array controller too doesnt it? So i shut it down, looked in the bios, it was TOTALLY default, BIG OOPS! So i programed it by enabling the RAID CONTROLLER, and putting drives 1 and 2 onto the RAID controller. These are my only 2 hard drives, and their locaitons.
*note* mind you, the nVidia mirror was still active as soon as i turned back on the RAID and applied drives 1 and 2 to RAID in BIOS. Hmm, where is this info stored? see question about this at the end...
Everything ok, now lets reboot......
ERROR;
WHAM, HAL.DLL Error. I think i may have goofed the boot.ini by booting into the system without the array active, or by installing the generic volume drivers, or could it be some driver list in a registry or somethign else? i dont think its memory, nor bad drives, nor power supply, nor do i think replacing the hal.dll will fix this, nor do i want to go into the recovery panel and risk messing up the master boot record, but this may be necessary.
SOLUTION1;
So, from there i tried a couple things, i went into bios and took sata drive slot 2 and removed it from the RAID array, leaving only sata slot 1 on the RAID array and SLOT 2 as a free drive. This caused the RAID drive to be in boot order 1, and the free drive as boot order 2. I removed it from the RAID as an attempt to get the system to boot back up so i can edit the boot.ini file. This worked, when the system booted, i saw UNHEALTHY RAID ARRAY, as expected, and also the system booted off the drive that was pulled from the RAID. So, i made a bit of progress here.
Once back into XP with one raid drive pulled ffrom the array i checked the boot.ini's and they both looked default, and were the same as each other.
I went into Drive F and added an entry into the boot.ini like this
SOLUTION1 FAILED;
Editing the boot.ini didnt work so far.
So i rebooted to see if i could boot into the C drive still and selected option1 the default and it still booted into the C drive that was NOT on the raid controller. IT DID boot back into the NON RAID DRIVE opsys no problem again.
SOLUTION2;
next i went into bios and switched the boot order and placed the RAID Drive into Boot order#2, and the Free drive as Boot order 1. This time i didnt get the options, indicating that it was now reading the boot.ini from the C Drive and not the F drive. Now i went into disk management and hoped to find that the RAID controlled drive was now the system drive. It wasnt, The C Drive Free Drive was now listed as SYSTEm drive, but still C:\ and Still Disk0 of course. The RAID controlled drive F:\ Drive was now listed as just ACTIVE.
SOLUTION2 FAILED;
This is where im at. a system that will boot only into a free drive, but not into the raid mirror.
IMPORTANT QUESTIONS;
Can i rebuild the Raid Array with the NVidia Bios without losing data?
Do i even need to rebuild the array?
Cant i just edit the boot.ini some more to fix this?
Was the installing of the generic hard drive drivers that did me in, or simply the fact that i booted it without the active mirror, or just by wiping out the bios in the first place?
LESS IMPORTANT QUESTION;
is there some kind of eeprom memory in the nVidia nforce chipset seperate from the asus bios that holds the RAID1 Mirror intact, or is that information included in a file on the drive?
memory; Buffalo Firestix PYRO pc2-8500 fsx1066d2c-1g
2x250GB SataII WD in RAID-1
1-DvD RW
1-CD-RW
xp pro sp2
Very Experienced Programmer/Technician
Hello all, my memory went bad, and caused my bios to lockup. i reset my bios in desperation. didnt get it to boot, so i sent my memory to manufacturer and waited 2 weeks. they sent me some splendid new memory, i put it in, and viola, computer boots right up.
right away im thinking all is normal, but then somedriver installation prompts come up. so as i always do, i click next, next, continue anyway, blah blah.
one of the drivers that needed to install was a generic volume for the hard drive, this struck my attention, but i went ahead and installed the driver, then for the other disk the same thing, it came up again, and i installed the other generic i believe. and a floppy disk controller came up, and wouldnt install because couldnt find the driver on the system. big deal, not a priority now anyway.
PROBLEM;
The problem came in when i looked in "my computer" and noticed a C drive, and a F drive, both 250GB, oh ****. the RAID array was defunct!! I immediately realized that the array was reset when i reset the bios, atleast i believe the CMOS reset affects the NVIDIA raid array controller too doesnt it? So i shut it down, looked in the bios, it was TOTALLY default, BIG OOPS! So i programed it by enabling the RAID CONTROLLER, and putting drives 1 and 2 onto the RAID controller. These are my only 2 hard drives, and their locaitons.
*note* mind you, the nVidia mirror was still active as soon as i turned back on the RAID and applied drives 1 and 2 to RAID in BIOS. Hmm, where is this info stored? see question about this at the end...
Everything ok, now lets reboot......
ERROR;
WHAM, HAL.DLL Error. I think i may have goofed the boot.ini by booting into the system without the array active, or by installing the generic volume drivers, or could it be some driver list in a registry or somethign else? i dont think its memory, nor bad drives, nor power supply, nor do i think replacing the hal.dll will fix this, nor do i want to go into the recovery panel and risk messing up the master boot record, but this may be necessary.
SOLUTION1;
So, from there i tried a couple things, i went into bios and took sata drive slot 2 and removed it from the RAID array, leaving only sata slot 1 on the RAID array and SLOT 2 as a free drive. This caused the RAID drive to be in boot order 1, and the free drive as boot order 2. I removed it from the RAID as an attempt to get the system to boot back up so i can edit the boot.ini file. This worked, when the system booted, i saw UNHEALTHY RAID ARRAY, as expected, and also the system booted off the drive that was pulled from the RAID. So, i made a bit of progress here.
Once back into XP with one raid drive pulled ffrom the array i checked the boot.ini's and they both looked default, and were the same as each other.
So i thought maybe the disk locations were off. So i went into disk management and found that DISK0 is the C:\ Drive and is listed as a PAGE FILE, and DISK1 is the RAID controlled drive F:\ and is listed as the SYSTEM drive.[boot loader]
timeout=30
default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Professional" /noexecute=optin /fastdetect
I went into Drive F and added an entry into the boot.ini like this
I then rebooted to see if i could boot from the RAID now. The options came up, and i selected the 2nd option, the RAID option of course. This gave me a Drive configuration error, probably because its i put the wrong drive location in the boot.ini it was just a stab as im not totally versed on boot.ini, im trying more options there now.[boot loader]
timeout=30
default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Professional" /noexecute=optin /fastdetect[boot loader]
multi(0)disk(1)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Professional - RAID" /noexecute=optin /fastdetect
SOLUTION1 FAILED;
Editing the boot.ini didnt work so far.
So i rebooted to see if i could boot into the C drive still and selected option1 the default and it still booted into the C drive that was NOT on the raid controller. IT DID boot back into the NON RAID DRIVE opsys no problem again.
SOLUTION2;
next i went into bios and switched the boot order and placed the RAID Drive into Boot order#2, and the Free drive as Boot order 1. This time i didnt get the options, indicating that it was now reading the boot.ini from the C Drive and not the F drive. Now i went into disk management and hoped to find that the RAID controlled drive was now the system drive. It wasnt, The C Drive Free Drive was now listed as SYSTEm drive, but still C:\ and Still Disk0 of course. The RAID controlled drive F:\ Drive was now listed as just ACTIVE.
SOLUTION2 FAILED;
This is where im at. a system that will boot only into a free drive, but not into the raid mirror.
IMPORTANT QUESTIONS;
Can i rebuild the Raid Array with the NVidia Bios without losing data?
Do i even need to rebuild the array?
Cant i just edit the boot.ini some more to fix this?
Was the installing of the generic hard drive drivers that did me in, or simply the fact that i booted it without the active mirror, or just by wiping out the bios in the first place?
LESS IMPORTANT QUESTION;
is there some kind of eeprom memory in the nVidia nforce chipset seperate from the asus bios that holds the RAID1 Mirror intact, or is that information included in a file on the drive?