Sudden XP Pro boot problem after imaging partitions

  • Thread starter Thread starter Bob
  • Start date Start date
B

Bob

Environment:

OS: XP Pro

Primary boot drive: 160 GB IBM (partitioned into C: (~10GB), D:
(~10GB), E: (~20GB), F: (~20GB), G: (~80GB)...OS is on C:, programs on
D: and data on E,F, and G partitions...all NTFS partitions; booted and
worked fine until now)

Data drive: 60 GB IBM (partitioned into H: (1GB), I: (29GB) and J: (30GB)..NTFS...never had
any problems)

Last night I did the following:

1) Using Drive Image 2002, I created an image file (*.PQI) of the I: and J: drives
on drive G: on the 160GB IBM. G: had ~65GB of free space left at the
time. After setting it all up in DI, the system rebooted and the
imaging process started.

2) About 75 minutes later, the image process was complete (no errors),
HOWEVER when the system automatically rebooted, the system would not
boot back into XP. After POST, all I get is a blinking cursor....no
messages of any kind. The system boots fine from an XP boot floppy disk and the
BIOS sees the IBM 160GB drive just fine.

3) I had an extra 30GB drive laying around, so I thought I might be
able to image the C: drive onto it. So, I booted using the XP boot
floppy disk, and then ran DI 2002, which I also had on floppy disk.
When I tried to do a disk-to-disk copy, I got error #1507 (Bad file
record signature). PowerQuest's solution to that is to run CHKDSK /F.

At this point, I have not done anything other than the above. I think
my first step will be to boot from the XP Pro CD, go into recovery mode
and go from there. I'm thinking that something is wrong in the MBR or
something like that.

Any suggestions or ideas would be most welcome. I am going to be
severely bummed if I lose all the stuff on that IBM 160GB drive.

Thanks very much!
Bob
 
DOS based, NTFS writie capable DOS versions of DriveImage sometimes acted
weird when writing TO NTFS drives. Since DOS does not support NTFS
DriveImage itself takes care of all file system I/O for the destination
drive.

To avoid problems I'd use a FAT32 drive for writing images to or upgrade to
DriveImage 7 (as it run from Windows and doesn't have to access the NTFS
destination drive itself).
 
Well, it appears that DI 2002 has really screwed up the drive because
after booting from the XP Pro CD and going into recovery mode, running
a 'chkdsk /r' yields "The volume appears to contain one or more
unrecoverable problems".

Anything else I can do?


:DOS based, NTFS writie capable DOS versions of DriveImage sometimes acted
:weird when writing TO NTFS drives. Since DOS does not support NTFS
:DriveImage itself takes care of all file system I/O for the destination
:drive.
:
:To avoid problems I'd use a FAT32 drive for writing images to or upgrade to
:DriveImage 7 (as it run from Windows and doesn't have to access the NTFS
:destination drive itself).
:
:--
:Joep
:
:
::> Environment:
:>
:> OS: XP Pro
:>
:> Primary boot drive: 160 GB IBM (partitioned into C: (~10GB), D:
:> (~10GB), E: (~20GB), F: (~20GB), G: (~80GB)...OS is on C:, programs on
:> D: and data on E,F, and G partitions...all NTFS partitions; booted and
:> worked fine until now)
:>
:> Data drive: 60 GB IBM (partitioned into H: (1GB), I: (29GB) and J:
:(30GB)..NTFS...never had
:> any problems)
:>
:> Last night I did the following:
:>
:> 1) Using Drive Image 2002, I created an image file (*.PQI) of the I: and
:J: drives
:> on drive G: on the 160GB IBM. G: had ~65GB of free space left at the
:> time. After setting it all up in DI, the system rebooted and the
:> imaging process started.
:>
:> 2) About 75 minutes later, the image process was complete (no errors),
:> HOWEVER when the system automatically rebooted, the system would not
:> boot back into XP. After POST, all I get is a blinking cursor....no
:> messages of any kind. The system boots fine from an XP boot floppy disk
:and the
:> BIOS sees the IBM 160GB drive just fine.
:>
:> 3) I had an extra 30GB drive laying around, so I thought I might be
:> able to image the C: drive onto it. So, I booted using the XP boot
:> floppy disk, and then ran DI 2002, which I also had on floppy disk.
:> When I tried to do a disk-to-disk copy, I got error #1507 (Bad file
:> record signature). PowerQuest's solution to that is to run CHKDSK /F.
:>
:> At this point, I have not done anything other than the above. I think
:> my first step will be to boot from the XP Pro CD, go into recovery mode
:> and go from there. I'm thinking that something is wrong in the MBR or
:> something like that.
:>
:> Any suggestions or ideas would be most welcome. I am going to be
:> severely bummed if I lose all the stuff on that IBM 160GB drive.
:>
:> Thanks very much!
:> Bob
:
:
 
Back
Top