jbullard wrote:Thinking about this a little more in detail also raised a few other concerns/questions. With Windows 7, the bootloader is installed on a hidden partition (100MB) which is only visible in Disk Management. This may be the reason you are having so many problems. Or, you also cloned the bootloader and it is also installed on the single drive resulting in locations associated with the RAID setup.
Have you tried to unplug the RAID drives and use the Windows 7 startup repair utility on the single drive?? This would recreate the bootloader within the single drive. Then, plug in the RAID drives and ensure the boot device is set for the single drive. Once in there, you could use DBP to add the RAID setup to the bootloader. Does that make sense??
Having read this it takes me in to a different angle on the situation.
My first thought was/is based in the ID assignment given by Windows 7. If I made the image from one drive and then shot it onto another drive and attempt to establish a dual boot it seems that what's happening is the second drive is containing the same ID of the one the image was made from. This would explain why the "collision" occurs. When I tried to use the Windows 7 installation disk to repair it Windows 7 recognized the bogus boot selection and deleted that, but when it tried to make the dual boot it saw the ID from the two drives being the same and left them. That causes the boot loader to point to the RAID drive since that's the drive ID contained in the image. Under Windows XP circumstances this isn't a problem because of the boot loader being contained in a boot.ini text document. Simply assign the proper disk and partition. With Windows 7 the OS creates the ID assignment. Manually changing the ID might work, but doing so is dangerous to the software and the hardware due to it's sourcing for the coding used, or so I've been told.
With your suggestion there is a different angle, but if I do use that method, and if it works, I end up with a problem with having to save two OS images, one from each of the OS's. I lose the universal functionality. If I later wanted to update the single drive by creating a new image of the striped drive and throwing it across I end up back at square one that I am today. I lose the ability to use the imaging capability to keep the single SATA drive up to date. It seems Symantec really needs to get their act together on this one.
Another problem is I'm not sure what will happen with your suggestion so I'm trying to think it through before I move on it. If I unplug the Striped drives and boot with just the single, if that drive is carrying the same ID of the stripe, it likely would recognize that and just boot as normal. When I plug the drives back in I'm back to the present problem. If I ran the Windows 7 install for a repair based on having only the single SATA plugged in then Windows 7 might not see anything wrong with the single SATA, but could unload the dual boot altogether since there's only one drive installed.
Any thoughts on this?
Edit: I forgot to mention that if I used the DBP to reestablish the dual boot it would be using the same ID for each drive which is originally from the stripe. Logically I'd be back to the current problem again. I'm thinking that, if I'm right, the ID of the drive assigned by way of the Windows 7 created ID must be changed on the single drive to make this work. Yes, I would loose functionality unless there was a fast and easy method to safely change the ID incorporated into the DBP or a manual method that's efficient enough to not make this into a nightmare each time I went to update the single SATA with a fresh image. Make sense?