New
#11
Quikly Un hook the raid temporarly...
Then fully format your os drive.... if you have a spare drive....
then reconnect the raid drives and use them as your storage....
or use partion magic / or simular program to create the 100 mb fat32 partition....then using BCDEDIT to point to your ORIGINAL Installation of WIndows....
use bcd edit to list the partition information....
You will need to boot up into a windows PE ENVRONMENT or RE Environment, Which can be made on another machine....
If you have unallocated disk space on the raid then you could quickly Re-Install windows on to the unallocated disk space and windows should RE-Create the SYSTEM hidden partion drive..... On the Window dVD the is also a BOOSECTOR COMMAND To REPLACE DELETED BOOT PARTITIONS...
BOOTSECT.EXE > WINDOWS DISK/BOOT <<<<<<< THIS WILL REPAIR IT!
Depending on how you have it set up - you may get the same problem again - in case you missed the edit to my last post:
Windows will always install the boot files on the first Active partition the installer comes across. The rest of the o/s installs on the partition you pointed at.
Not sure what he was getting at , bootsect.exe can be used to write the bootsector code only, or optionally the mbr code as well.
It won't , to my knowledge , replace/rebuild any of the boot critical files (bootmgr and the Boot folder containing bcd).
The syntax goes like this:
bootsect {/nt60|/nt52} {SYS|ALL|<DriveLetter>:} [/force] [/mbr]
reinstalled. Everything is fine now. My 1Tbs are now one partition, and the SSD is working flawlessly.
was freaking out because i thought i lost everything on my 1tb`s.
thanks everyone. Yeah had no idea about that command.
On a side note: Why was windows using that boot from the HDDs and not making one on the SSD? (now i dont have a pause before the boot screen )