Dual 2k drives imaged w/ Ghost 2nd drive won't boot
I really don't know just how to explain this. I have 2 bootable drives with 2k on each. The second is a image of the first done using Ghost. I've done this before, but this time the drives are hooked up to a Highpoint controller which, I assume is causing the problem.
I really don't know just how to explain this.
I have 2 bootable drives with 2k on each. The second is a image of the first done using Ghost.
I've done this before, but this time the drives are hooked up to a Highpoint controller which, I assume is causing the problem.
I disconnected the first drive since there is no way to disable it in the bios, then I booted using the 2nd drive, there was no page file and it was not created as I thought it was suppose to be after the image was made. I got the error message but it wouldn't load any further.
I reconnected the 2nd drive, booted using the first drive and created a page file for the other drive and then shutdown, disconnect the 1st drive and booted. I get a 'looping effect' with the dialog boxes for network connections etc. durning the msgina stage (for lack of a better term).
Another observation is the 2nd drive is ID'ed as 'D' not 'C' In other words the first drive is always 'C' and the 2nd drive is always 'D' no matter which is the boot drive, a problem I have seen before using 2k.
When the 2 drives are both on line the 2nd drive is using the pagefile from the first drive and probably associated itself with other files from the first drive. When I remove the 1st drive, I also assume the 2nd drive is confused by the missing 1st drive.
I have read all the stuff from M$ and Noton Ghost, but that only seems to confuse the issue more.
I haven't hooked the drives up to the IDE buss yet since the controller is ATA66 and the IDE is 33.
It is a Highpoint HPT366 on board controller.
I have 2 bootable drives with 2k on each. The second is a image of the first done using Ghost.
I've done this before, but this time the drives are hooked up to a Highpoint controller which, I assume is causing the problem.
I disconnected the first drive since there is no way to disable it in the bios, then I booted using the 2nd drive, there was no page file and it was not created as I thought it was suppose to be after the image was made. I got the error message but it wouldn't load any further.
I reconnected the 2nd drive, booted using the first drive and created a page file for the other drive and then shutdown, disconnect the 1st drive and booted. I get a 'looping effect' with the dialog boxes for network connections etc. durning the msgina stage (for lack of a better term).
Another observation is the 2nd drive is ID'ed as 'D' not 'C' In other words the first drive is always 'C' and the 2nd drive is always 'D' no matter which is the boot drive, a problem I have seen before using 2k.
When the 2 drives are both on line the 2nd drive is using the pagefile from the first drive and probably associated itself with other files from the first drive. When I remove the 1st drive, I also assume the 2nd drive is confused by the missing 1st drive.
I have read all the stuff from M$ and Noton Ghost, but that only seems to confuse the issue more.
I haven't hooked the drives up to the IDE buss yet since the controller is ATA66 and the IDE is 33.
It is a Highpoint HPT366 on board controller.
Participate on our website and join the conversation
This topic is archived. New comments cannot be posted and votes cannot be cast.
Responses to this topic
Quote:
I am interested in this MBR issue. If I understand you correctly, D.I. rewrites the MBR to load this virtual floppy (as they call it) into the root of 'C'(I assume) and writes a command line to point to this folder or file to load this program on the reboot?
Yep, thats pretty much how I've understood it. You can start your studies at http://www.powerquest.com/support/primus/id1811.html
there they describe the fix. I think I saw somewhere at PQ a description of how it works too.
H
I am interested in this MBR issue. If I understand you correctly, D.I. rewrites the MBR to load this virtual floppy (as they call it) into the root of 'C'(I assume) and writes a command line to point to this folder or file to load this program on the reboot?
Yep, thats pretty much how I've understood it. You can start your studies at http://www.powerquest.com/support/primus/id1811.html
there they describe the fix. I think I saw somewhere at PQ a description of how it works too.
H
I did see that article.
That seemed to be the problem with the Ghost image.
Couldn't find how it works though.
That seemed to be the problem with the Ghost image.
Couldn't find how it works though.
