Archived from groups: microsoft.public.windowsxp.general (More info?)
I have a 2.0 GHz Gateway computer, with 512 Mb RAM, an 80 Gb Western Digital
Master HD 40 Gb free, & a 80 Gb Western Digital
Slave HD, & a 200 Gb Seagate Firewire HD, running Windows XP Pro SP-1.
I have been successfully cloning my Master HD (which boots & runs normal) to
my Slave HD for over two years every other week
(disconnecting the Slave HD from the computer at the completion of each
cloning) using Norton Ghost 3.0 that runs in DOS from
a floppy disk (part of Symantec System Works 2003). Before each cloning I
would defrag my Master HD using the Windows defrag
program with no problems. Then on 04/28/05 I defragged my Master HD using
the Symantec System Works 2003 defrag program.
After that defragging, I was unable to clone my Master Hd, receiving the
message;
"file system references disk sectors beyond the partition boundary" when
attempting to clone my Master HD.
Symantec Tech Support advised me to purchase Symantec System Works 2005
which has Ghost 9.0 that gets around this problem.
So I did. This new program does not have a cloning feature, but has HD
complete copy and backup/restore features. Symantec
Tech Support was right, I no longer get this message, however, I now have a
new problem. I copy my Master HD to my Slave HD
using Ghost 9.0, or backup using Ghost 9.0 or the Windows backup program to
my Firewire drive, then I restore to the Slave
HD, formatting it before each copy or restore. My new problem is the Slave
HD won't boot, when connected as the only HD on
the computer. In order to get it to boot I must run fdisk/mbr from a floppy
disk. Then the copied/restored HD boots & runs
normal.
Symantec Tech Support told me to run Windows defrag, CHKDSK, fdisk/mbr,
clean boot, disable/enable virtual memory, & delete
the page file on my Master HD. I did that several times with the same
results above. When Symantec Tech Support ran out of
ideas, they told me that some systems require the fdisk/mbr applied after
copy, backup/restore to get a HD to boot, nobody
knows why, not even Microsoft, but that it works. I don't accept this
explanation, because it seems to me that the Symantec
System Works 2003 defrag program somehow moved files outside the partition
boundary on my Master HD, resulting in the message
I received immediately after using it.
I have two questions after this history:
1. Except for the nightmare of formatting re-installing upgrading
everything & redoing settings on my Master HD, does anyone
have any ideas how I can restore my Master HD (which boots & runs OK) back
to a condition where copy backup/restore of it
works normally?
2. One Symantec Tech Support technician told me there is no problem having
Master Slave HD's both Windows bootable,
connected on the computer. Another Symantec Tech Support technician told me
that Master Slave HD's both Windows bootable,
connected on the computer is a disaster waiting to happen. As soon as the
copy or restore is made, that HD should
immediately be removed from the computer. Which is the correct advice?
Thanks.
Regards...Don
I have a 2.0 GHz Gateway computer, with 512 Mb RAM, an 80 Gb Western Digital
Master HD 40 Gb free, & a 80 Gb Western Digital
Slave HD, & a 200 Gb Seagate Firewire HD, running Windows XP Pro SP-1.
I have been successfully cloning my Master HD (which boots & runs normal) to
my Slave HD for over two years every other week
(disconnecting the Slave HD from the computer at the completion of each
cloning) using Norton Ghost 3.0 that runs in DOS from
a floppy disk (part of Symantec System Works 2003). Before each cloning I
would defrag my Master HD using the Windows defrag
program with no problems. Then on 04/28/05 I defragged my Master HD using
the Symantec System Works 2003 defrag program.
After that defragging, I was unable to clone my Master Hd, receiving the
message;
"file system references disk sectors beyond the partition boundary" when
attempting to clone my Master HD.
Symantec Tech Support advised me to purchase Symantec System Works 2005
which has Ghost 9.0 that gets around this problem.
So I did. This new program does not have a cloning feature, but has HD
complete copy and backup/restore features. Symantec
Tech Support was right, I no longer get this message, however, I now have a
new problem. I copy my Master HD to my Slave HD
using Ghost 9.0, or backup using Ghost 9.0 or the Windows backup program to
my Firewire drive, then I restore to the Slave
HD, formatting it before each copy or restore. My new problem is the Slave
HD won't boot, when connected as the only HD on
the computer. In order to get it to boot I must run fdisk/mbr from a floppy
disk. Then the copied/restored HD boots & runs
normal.
Symantec Tech Support told me to run Windows defrag, CHKDSK, fdisk/mbr,
clean boot, disable/enable virtual memory, & delete
the page file on my Master HD. I did that several times with the same
results above. When Symantec Tech Support ran out of
ideas, they told me that some systems require the fdisk/mbr applied after
copy, backup/restore to get a HD to boot, nobody
knows why, not even Microsoft, but that it works. I don't accept this
explanation, because it seems to me that the Symantec
System Works 2003 defrag program somehow moved files outside the partition
boundary on my Master HD, resulting in the message
I received immediately after using it.
I have two questions after this history:
1. Except for the nightmare of formatting re-installing upgrading
everything & redoing settings on my Master HD, does anyone
have any ideas how I can restore my Master HD (which boots & runs OK) back
to a condition where copy backup/restore of it
works normally?
2. One Symantec Tech Support technician told me there is no problem having
Master Slave HD's both Windows bootable,
connected on the computer. Another Symantec Tech Support technician told me
that Master Slave HD's both Windows bootable,
connected on the computer is a disaster waiting to happen. As soon as the
copy or restore is made, that HD should
immediately be removed from the computer. Which is the correct advice?
Thanks.
Regards...Don