Installed Win 8 on new drive after disconnecting drives of previous install. Now I can't get to the previous install.

Dennyd1

Honorable
May 21, 2013
20
0
10,510
Okay, so this is what I did. I have Windows 8 Pro, not 8.1 just 8, installed on four Velociraptor HDD's RAID'd with a 10 configuration using the built-in motherboard RAID controller.

I took an image of that installation using Win 8 backup image utility after updating windows and installing a few basic programs I always like to have so that when I return it back to that state, it's not as long and arduous a process.

Later on I bought a single 500GB SSD Samsung 840 EVO. I wanted to be sure I wasn't going to install over the previous installation of Win 8 located on my four RAID'd drives, so I manually disabled all of my drives by unplugging them from the system. I then proceeded to "restore" the Win 8 image to the new SSD drive. I used a windows repair boot disk that I created, also using the windows utility, after taking the image.

Somewhere along the way, I don't remember the exact order, but I booted up the SSD and reconnected my four RAID'd drives and decided to handle the different installations using the boot-order in the BIOS. However, I soon found out that I cannot boot to my previous installation of Windows, but only to the new installation on the SSD.

Then I disconnected the SSD and tried to boot up using only the RAID'd drives, but it just sent me to the repair and recovery utility. I tried to repair, but it didn't work. I also keep getting errors every time I try to boot to windows with both drives online, when the boot order is changed in order to attempt to control which one boots up.

My first thought, of course, is the Master Boot Record, but I'm not really sure how to handle that on Windows 8. Also, I'm not exactly sure how to know exactly which partition and disk my first installation is on.

Can anyone tell me what I did and how to fix it? I'm thinking MBR problem, and I'm hoping it's simple to fix by a simple edit of some Win 8 boot.ini-type of file, but I don't know. My motherboard is an MSI Big Bang Xpower II, in case that's important.


Less-important stuff:
Side note: I thought that the MBR was stored on the drives themselves, which I thought should mean that each drive, the RAID drive and the SSD, should each have their own individual MBR since they were entirely disconnected from each other when their installations took place, which I thought would mean that if I disabled one or perhaps changed the boot-order, the other would simply boot up. However, the only one that boots up is the installation on the SSD. I suppose it could also be competing C: designations, but when I boot up Win 8 on the SSD, J is the letter assigned to the RAID'd drives. So the SSD obviously has no problems reassigning a drive-letter. I would have assumed the same would be with the previous installation on the RAID'd drives.

The idea here is, for those that care to know, that I am not at a convenient situation in which I can just replace the first installation with the one on the SSD, so I was going to do it over time as I have free-time here and there, and then ultimately re-format the four RAID'd HDD's, and use them for gaming, and then use the SSD for the main OS and Virtualization of a couple or so other OS's such as Win 98SE and one or two of the free Linux distributions. Although, it appears that 500GB isn't quite so much with Win 8, not after all the updates, several basic programs, and the SSD supposedly life-extending, performance-enhancing partition is created by the Samsung SSD utility.


 

duken30

Distinguished
Sep 30, 2010
5
0
18,510
Dennyd1,

It sounds as if you have the same Bios as I do on my board. For one the Click II bios, from what I have seen on my AMD system has always been a little finicky. For one make sure your bios is up to date. I say this because they added features to mine not too long ago that gave a raid boot menu option on the UEFI bios. For two when you are trying to boot from the Raided drives there are a few caveats that need to be checked. Is the SATA Controller in RAID Mode or just AHCI? If it is in raid mode boot into the raid controller bios by hitting the button it prompts you to after the bios screen. I believe in my case this was F11. However, this is something that most people do not know if you are using a raid configuration like this and are prompted for a RAID Bios controller then you aren't using UEFI and should indeed have a MBR. If it is indeed a RAID 10 or 0+1. Then you should have two drives that are raid0 and then the other two are mirrored. The individual drives don't store the MBR as you stated. In fact it is on the logical volume of the raid. So, basically the two drives acting as one which are striping the data across have a piece of the MBR on both. If the Raid controller isn't seeing these drives as a logical disk then you are definitely going to not be able to boot. My suggestion is to check the raid bios editor where you originally would have configured the raid. Make sure it sees your Raid10 configuration there. If it does then you need to get into the bootini configuration and change the order. This is easier said than done because 1. It is windows 8 and there isn't an F8 boot option. 2. You are dealing with a raid so if the recovery environment doesn't have the raid driver loaded it won't see them as two separate drives. What worries me the most about your situation is that you used the windows auto recovery. If that recovery disk did not see them as two separate drives then it most likely did a write to only one independent drive trying to recreate your boot.ini. If this is the case it will make this process much harder because now the striped blocks on each drive do not match and most likely the raid controller does not see them as a logical drive. Make sure it is being seen as a raid 10, try to boot into a command line recovery tool from a windows 8 installation media, try editing and rebuilding the boot.ini from there. I hope this helps. Ultimately tho if you are looking to be able to boot faster than you do now you want to be in UEFI mode to really see boot time enhancements from your SSD setups. This is an entirely other task and would require a reinstallation in UEFI mode from your bios and launching the UEFI mode from your installation media. I just wanted to throw that out there as some day you may want to do this instead of a traditional MBR setup. It is far faster and the modern way of booting from a drive. Also, if you had UEFI already in place Windows8 is built around it and the bios as well. It would be an easier process to narrow down what is happening with the RAID and the single drive through the UEFI Shell interface from your bios. Anyways I hope this helps you figure out what exactly has happened.

Cheers,

Duken30
 

Dennyd1

Honorable
May 21, 2013
20
0
10,510
Thanks, but I found the solution here:
http://www.thewindowsclub.com/repair-master-boot-record-mbr-windows

It was a simple fix using the bootrec command.

I realize that you probably assumed that I had already tried that, but you must'nt assume such things.

I figured it must have been the MBR.

In fact, this will allow you to add your other windows installations to the boot record so that you can have a dual boot. Don't ask me what if you have Linux and want a dual boot because I don't know.

Oh, and automatic repair did not work.