• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

RAID 0 No bootup

E

elite_prodigy

n00b
Joined
Mar 28, 2013
Messages
4
Ok guys I have a weird problem on my hands right now.

I have 2 ssds in RAID 0 and 2 HDDs in non raid.

I wanted to take out one of the HDDs because its a piece of crap and i need to put it into another build i have. When i take out the one HDD windows won't boot anymore, It does all of the bios boot screens and shows the raid settings and disks, but it just says that I need to put the right boot media in and restart. I have already checked to see if the boot order is right and it has the raid setup as the main boot. Also my sata controller is set to raid as well.

Please help
 
Plug the drive back in, then try each different drive as the first drive to boot off of into the BIOS.

I believe this has to do with that 100mb partition win7 makes being on the "wrong" disk at time of installation. I've run into it before.
 
something like this happened to me, as well, if I understand you correctly.

last month I upgraded my system, and tried to clone my hard drive. Norton ghost and... easeUS? both. They both created a cloned hard drive that would not boot on its own.

Same thing as you-- if the original hard drive was also plugged in, I could boot from the new one still.
But if I removed the old hard drive and booted from the new one alone, it could not.
And if I tried to boot from the old drive alone, it would boot... and then fail to go past the login screen.

Some critical few files of windows, remained on the old drive.

I tried doing a disk repair. For me, it did not work.
From the repair screen, you can find more detailed error codes. I looked all of these up too, following different repair suggestions, and it still failed to work. But that was just my personal situation. I did a fresh install of windows and my favorite programs rather than mess with it further (ended up faster).

But, get a windows boot disk and try a repair. Sounds like some boot files ended up on the old hard drive?
 
The problem is that for non-UEFI install Windows will ask the BIOS which drive the boot drive is and install the bootloader and boot partition on that drive regardless of which drive you selected for the install. You have to make sure that the right drive is selected before you install. In the past I usually just disconnected all drives that I did not want to install to and proceeded from there. That way you can select the right drive after the install.

If you have now split boot partition and system partition to different drives, it is possible to "repair" this but it is complicated unless some tool I do not know of just provides this function. I would say it is much easier to just reinstall. I'm not completely sure if the boot loader and boot partition go to the boot drive or only the boot loader. I only run into this problem pre-Windows 7 and there was no boot partition before.

A first step would be to post a screenshot of the windows partition manager.
 
it is habit for me to do windows installs with ONLY the OS drive plugged in, then plug in storage drives after the OS is installed. for as long as windows has been owned by MS (that means forever) it has had issues with popping MBR or boot/system files in weird places if more the one drive is installed in the machine during the windows install. like everyone says, when you get the locations figured out and set correctly running a repair and doing a MBR repair may fix it. (fdisk MBR is not available anymore but the bootsect command can do similar things to what is now the current windows implementation)
 
Ok, so general consensus says to unplug all the other drives except the raid 0 array, then do a windows repair. Right?
 
DiskManagerpic_zps79f6200c.jpg
[/URL][/IMG]

There's the pic guys
 
Well, that is a little bit of a mess. It seems that the disk with drive E: is the boot disk and drive E: contains the bootmanager (it is marked as "System"). Normally the bootmanager goes to the 100 MB partition, but you can live without that partition.

You should be able to solve that with a repair (backup data first). You may need a driver disk for then Intel RAID, though.
 
You must log in or register to reply here.
Back
Top