partition unreadable after running drive image

[Joe]

I used drive image to create an image of my c drive on my e drive. it
completed without errors, but i can not longer read my e drive. i'm
running w98se. i have attached the output of findpart
hoping that someone can provide some insight into what has happened.

Findpart, version 4.41 - for Windows 95/98/ME/NT/2000/XP.
Copyright Svend Olaf Mikkelsen, 1999-2004.

OS: Windows 4.10.2222 All

Disk: 1 Cylinders: 2494 Heads: 255 Sectors: 63 MB: 19564

-PCyl N ID -----Rel -----Num ---MB -Start CHS- --End CHS-- BS CHS
0 - 0B 63 8000307 3906 0 1 1 497 254 63 B OK
498 1 0B 63 23711877 11578 498 1 1 1973*254 63 R0 OK
498 2 05 23711940 8353800 4079 1974* 0 1 2493*254 63 498 OK
0 - 0B 8000433 23711877 11578 498 1 1 1973 254 63 B OK
1974 1 0B 63 8353737 4078 1974 1 1 2493 254 63 NB OK
0 - 0B 31712373 8353708 4078 1974 1 1 2493 254 34 B OK
No jump 1974 1 1

-----FAT CHS -Size Cl --Root -Good -Rep. Maybe --Bad YYMMDD DataMB
0 1 33 7798 4 2 7798 0 0 0 040206 666
498 1 33 11573 8 2 11573 0 0 0 040207 4112
1974 1 33 8142 4 2 8142 0 0 0 040206 510

Partitions according to partition tables on first harddisk:

-PCyl N ID -----Rel -----Num ---MB -Start CHS- --End CHS-- BS CHS
0 1*0B 63 8000307 3906 0 1 1 497 254 63 OK OK
0 2 0F 8000370 32065740 15657 498 0 1 2493 254 63 OK

498 1 0B 63 23711877 11578 498 1 1 1973*254 63 R0 OK
498 2 05 23711940 8353800 4079 1974* 0 1 2493*254 63 OK

1974 1 0B 63 8353737 4078 1974 1 1 2493 254 63 NB OK

thanks
joe

 

[Svend Olaf Mikkelsen]

I used drive image to create an image of my c drive on my e drive. it
completed without errors, but i can not longer read my e drive. i'm
running w98se. i have attached the output of findpart
hoping that someone can provide some insight into what has happened.

Findpart, version 4.41 - for Windows 95/98/ME/NT/2000/XP.
Copyright Svend Olaf Mikkelsen, 1999-2004.

OS: Windows 4.10.2222 All

Disk: 1 Cylinders: 2494 Heads: 255 Sectors: 63 MB: 19564

-PCyl N ID -----Rel -----Num ---MB -Start CHS- --End CHS-- BS CHS
0 - 0B 63 8000307 3906 0 1 1 497 254 63 B OK
498 1 0B 63 23711877 11578 498 1 1 1973*254 63 R0 OK
498 2 05 23711940 8353800 4079 1974* 0 1 2493*254 63 498 OK
0 - 0B 8000433 23711877 11578 498 1 1 1973 254 63 B OK
1974 1 0B 63 8353737 4078 1974 1 1 2493 254 63 NB OK
0 - 0B 31712373 8353708 4078 1974 1 1 2493 254 34 B OK
No jump 1974 1 1

-----FAT CHS -Size Cl --Root -Good -Rep. Maybe --Bad YYMMDD DataMB
0 1 33 7798 4 2 7798 0 0 0 040206 666
498 1 33 11573 8 2 11573 0 0 0 040207 4112
1974 1 33 8142 4 2 8142 0 0 0 040206 510

Partitions according to partition tables on first harddisk:

-PCyl N ID -----Rel -----Num ---MB -Start CHS- --End CHS-- BS CHS
0 1*0B 63 8000307 3906 0 1 1 497 254 63 OK OK
0 2 0F 8000370 32065740 15657 498 0 1 2493 254 63 OK

498 1 0B 63 23711877 11578 498 1 1 1973*254 63 R0 OK
498 2 05 23711940 8353800 4079 1974* 0 1 2493*254 63 OK

1974 1 0B 63 8353737 4078 1974 1 1 2493 254 63 NB OK

thanks
joe

The boot sector of the cylinder 1974 partition contains no jump
instruction in the first bytes, which is required for Windows to
consider the partition valid.

You can create a new directory in the root of the 11578 MB partition,
copy the findpart exe and library files to the new directory, and in
the directory run this command:

findpart chsdir 1 1974 1 33 8142 4 2 copy

This should copy all files from the damaged partition.

 

[Joe]

thanks for the quick response. any idea what would cause the jump
instruction to be removed ? this is the second time this has happened on
two different computers.

joe

 

[Svend Olaf Mikkelsen]

thanks for the quick response. any idea what would cause the jump
instruction to be removed ? this is the second time this has happened on
two different computers.

joe

Did you use Drive Image on both computers?

I do not know, and do not remember previous occasions without
checking.

Disk: 1 Cylinders: 2494 Heads: 255 Sectors: 63 MB: 19564
0 - 0B 31712373 8353708 4078 1974 1 1 2493 254 34 B OK


You can do this:

findpart getsect 1 1974 1 8 fp-a.bin

and mail me the file fp-a.bin so I have it for reference. It contains
the boot sector and the backup boot sector.

Principally before sending the file you can do:

edit /64 fp-a.bin

and check that the location is correct, and that the file does not
look as it can contain private information.

 

[Svend Olaf Mikkelsen]

Did you use Drive Image on both computers?

I do not know, and do not remember previous occasions without
checking.

Disk: 1 Cylinders: 2494 Heads: 255 Sectors: 63 MB: 19564
0 - 0B 31712373 8353708 4078 1974 1 1 2493 254 34 B OK


You can do this:

findpart getsect 1 1974 1 8 fp-a.bin

and mail me the file fp-a.bin so I have it for reference. It contains
the boot sector and the backup boot sector.

Principally before sending the file you can do:

edit /64 fp-a.bin

and check that the location is correct, and that the file does not
look as it can contain private information.

The correct command was, as guessed by Joe:

findpart getsect 1 1974 1 1 8 fp-a.bin

I received the file.

The first four bytes of both the FAT32 boot sector in CHS 1974/1/1 and
the backup boot sector in CHS 1974/1/7 contain the string "RRaA",
which belong in the first four bytes of the following sector, the
"FSInfo" sector. I do not know the details, but as far as I remember
all cases I have seen have been related to Partition Magic. If Drive
Image uses the procedures, it can be the same error.

 

[Joe]

Svend Olaf,

thanks again for the quick reply. I have done a bit more poking around and have
isolated the problem. both of these disk were originally partitioned and
formatted with western digital data lifeguard 11.0. The fs info sector field in
the boot sector is set to 0. on my other drives, partitioned and formatted
with an earlier version of the data lifeguard utility, the fs info sector field
is set to 1. on these disks, drive image works properly. i'm guessing that
drive image is using this values as an offset when it updates the fs info
sector.

thanks for all of the help.

joe

 

[Svend Olaf Mikkelsen]

Svend Olaf,

thanks again for the quick reply. I have done a bit more poking around and have
isolated the problem. both of these disk were originally partitioned and
formatted with western digital data lifeguard 11.0. The fs info sector field in
the boot sector is set to 0. on my other drives, partitioned and formatted
with an earlier version of the data lifeguard utility, the fs info sector field
is set to 1. on these disks, drive image works properly. i'm guessing that
drive image is using this values as an offset when it updates the fs info
sector.

thanks for all of the help.

joe

Nice that you figured that out.

You are welcome.