Join Date: Sep 2006
Posts: 426 (0.17/day)
Thanked 22 Times in 22 Posts
DFI lanparty ULTRA D NF4 and SSD RAID 0 help
I need help with my DFI lanpartu Ultra D nf4 chipset..
Here's the kicker... Windows installed and configured on a single 30GB IDE disk, plugged into IDE-0 on the DFI lanparty, and also have 2 130GB IDE disks in RAID 0, using a Promise Fast-track 100 RAID controller.
I have setup windows XP pro sp2 with Nlited nvraid drivers, reconfigured windows/registry to move profiles, system writes, temp files, page file, temp internet files, cache and other frequent System drive writes to a partition on the IDE RAID-0 Promise fasttrack array, to reduce system writes, to preserve the SSD Array..
I have cloned my C: xp installation from a single ATA disk, over to a partition on the IDE RAID-0 promise fasttrack array, to see if it would work, and have booted from that and have since removed the single 30GB disk from the DFI onboard IDE controller.. Windows working fine after cloning over to the promise array..
I only have a single opticle IDE disk connected to the DFI onboard IDE controller..
And 2 IDE disks connected to the promise RAID controller, setup in RAID 0..
I went into the bios, enable RAID, opened up the f10 console, setup the stripe for the SSD's, booted windows off the fast-track Array, aligned and partitioned the SSD array and have cloned my XP installation from the Promise array, over to the SSD array primary/active partition, then went into regedit and swapped drive letters between the IDE array and the SSD array and rebooted..
Now unable to boot off the SATA SSD, and unable to set the SSD array to BOOT via the F10 RAID configuration/bios..
I think This is because the DFI lanparty NF4 bios detects the IDE disks on the promise controller so, the bios/F10 thing won't allow me to set the SSD array as "bootable"
Also, since i have configured the SATA array, and done all the partition/formatting, once in a while the bios hangs on "detecting disks" at the mediashield bios.. It takes a couple of reboots before the NVIDIA STRIPE is re-detected... This is only after setting the partition to "active" before this, the NVIDIA STRIPE was detected on every single reboot...
Do I need to add "hard disk delay" in the bios? is that what the delay for hard disks setting is for?
I have read that the only way to get the SATA array bootable is to remove ALL P-ATA, IDE disks physically from the computer, then reboot and open F10 configuration, set the array to bootable, and then boot/install windows on the SATA array, then re-install the IDE disks after booting windows.
I have not tried removing the promise array/IDE disks, because they are hard coded in my xp installation to used one of the partitions on that array as cache/profiles/temp files etc..
I do not want to attempt to boot windows off the SSD array without these disks installed, in fear of windows freaking out, because I have the profiles and such, already set to be written to another IDE RAID volume.. Any ideas? If I unplug the promise controller/disks, then open f10 mediashield thing, set the array to boot; turn off computer/reconnect the promise controller...
One thing that I can try is to delete the C: partition off the Promise controller ARRAY. Remove the promise controller/disks, the open F10, set array to bootable if it allows... then boot the windows installation CD "nvraid" nlited, and attempt to "repair" the installation, if it allows.. then before windows reboots after copying files, re-install the promise controller/disks??
lota different things to try..
I have everything backed up, and can reconnect the single 30GB disk, clone my install to it, then remove it and have that backed up, ready to go, just incase..
I don't mind borking the fast-track RAID-0 C: install but I seriously don't want to bork the install on the SSD's because it means re-flashing each SSD and resetting bios a few times, configuring the stripe, align/partition rinse spin/dry etc... Any suggestions?