windows 7 raid boot issue

[xSauronx]

I wasn't thinking last week when I installed windows 7 onto a raid setup...it worked fine, but i left a 160gb sata drive plugged in when i did it

When i remove the 160gb drive...windows wont boot.

What's the proper way to fix this? I wanted to use the 160gb drive for something else, but i havent dealt with this specific boot issue before in wondws 7. Im pretty sure in xp it was the way boot.ini labeled the drives based on their order (0,1,2 etc) but Im not sure how that relates in windows 7

anyone care to point me in the right direction? Im not even exactly sure what to google for to get the right fix on this

 

[Absolution75]

You likely have the boot record on that hard drive. Boot into windows and check the windows disk management application. It will likely say "Boot" for that 160 GB hd.

What you can do is remove the HD, boot into windows recovery, and attempt an automatic repair of the boot sector. There is a much harder way of doing it via command prompt which I've done, but I'd try the automatic one first.

 

[Lorne]

Raid 0 or 1?,, Raid 0 your SOL if you dont put the 160 back in or have blanked it.

 

[xSauronx]

Raid 0 or 1?,, Raid 0 your SOL if you dont put the 160 back in or have blanked it.

raid 0...so, damn. oh well.

the 160 can stay in and just host random data or VMs, this just gives me an excuse to buy another drive i guess i didnt format it and am running the system now

thanks

/should probably find a wiki on the windows 7 boot process for future reference
//off to newegg