Reusing a master HDD with corrupt OS as a slave...couple questions!

bigmck said:

whs said:

This is hard to tell. The OS could be living off either 100MB active partition. I suggest you transfer the bootmgr to C. Then you should not have any problems without the second HDD. Bootmgr - Move to C:\ with EasyBCD

WHS -- I don't understand what you did. C: already had a System Reserved. When the F: System Reserved was moved, did it overwrite the C: or were there two? Thanks,

Jim, the situation here was the folllowing:

There were 2 disks with 2 system partitions and 1 disk had the C partition. When they removed the disk without the C partition, the system did not boot. That suggested that the bootmgr that was used did not reside in the system partition of the disk with the C partition but on the other disk.

I recommended to move (which is actually a copy) the bootmgr from the system partition to the C partition. EasyBCD finds the right system partition from where to copy it and now the C partition is self contained and does not need any system partition any more. Thus it is irrelevant on which disk's system partition the bootmgr originally resided.

And the best part is that it worked, LOL.

whs said:

Jim, the situation here was the folllowing:

There were 2 disks with 2 system partitions and 1 disk had the C partition. When they removed the disk without the C partition, the system did not boot. That suggested that the bootmgr that was used did not reside in the system partition of the disk with the C partition but on the other disk.

I recommended to move (which is actually a copy) the bootmgr from the system partition to the C partition. EasyBCD finds the right system partition from where to copy it and now the C partition is self contained and does not need any system partition any more. Thus it is irrelevant on which disk's system partition the bootmgr originally resided.

And the best part is that it worked, LOL.

Thanks very much for the explanation.