On Mon, Apr 24, 2006 08:45:51, Bill wrote:

"Hoppy" wrote in message ...
On Sun, Apr 23, 2006 12:57:55, Bill wrote:

"Hoppy" wrote in message ...
Hello, All!

I used Partition Magic 8.02 to create a new 1GB partition (J, taking
the space from E:. At the end of operation, I received an error
that "...cross-linked files were found." There was no option other than
to continue. PM then called DriverMapper and it seemed to go smoothly.

On reboot, Windows Explorer shows E: and J: with no labels. When I click
on the drives, I get an error that says, "E:\ is not accessible. A device
attached to the system is not functioning."

In Device Manager on the Performance tab, it says "Drive E is using an
MS-DOS compatibility mode file system."

In DOS, ScanDisk says, "...cannot examine drive E:" I did not try J:

Also in DOS, FDisk shows E:'s size as it should (10000MB), but shows
System "Unknown" (-- it should be FAT32 --) with an 18% Usage -- which is
about right. FDisk does not show J: at all.

Partition Magic shows E: as it should -- FAT32; (new) Size: 10,001.4MB;
Used: 1150.5, set as Logical. Drive J: does not appear at all. What
does
show is 1004.1MB of Unallocated space after E:; this was supposed to be
the new J: partition.

Look in the Partition Magic directory tree for partinfo.exe. Open a DOS
prompt, CD to that dir, and run
partinfo partinfo.txt

Open partinfo.txt in notepad and Copy/Paste/Post to this thread.

Don't try to fix E: (or J until you find out what the problem is.

I'm getting too old for this. Here's the file. I'll try to attach it to
my post as well; I hope that's not breaking any rules.

No, that's fine. Actually better as attached.

The extended partition chain has a corrupt link in the chain for one.

Assuming all the start sectors LBA values are correct.

The first EMBR/second table entry contains an incorrect value for LBA "Num
sectors" (total sectors remaining in the extended partition).

The second EMBR/first table entry contains an incorrect value for LBA "Num
sectors" (total in "this" logical drive).

Again, that's assuming the start sector numbers are correct. If math
corrected the E: logical drive still may not show. The "E:" boot sector
doesn't show, so may also be corrupt, start elsewhere, or DOS/Windows has a
problem with those incorrect values.

You could try to correct the values yourself, and see what that does, or
probably safer use something like DiskPatch or MBRWork to scan the disk for
the missing partitions. I'd use DiskPatch first, as freeware MBRWork is a
"do or die" operation. The demo version of DiskPatch is read-only, so won't
do any damage. http://www.diydatarecovery.nl/DiskPatch.htm

Your existing partitions probably aren't at too much risk, but you never
know. Back up all important data before fixing anything.

================================================== ========================
Disk 0: 7476 Cylinders, 255 Heads, 63 Sectors/Track.
BiosExtensions: 0x100 Subsets (0x00000003): Access Lock/Eject
The BIOS supports INT 13h extensions for this drive.
========================== Partition Tables ==============================
Partition -----Begin---- ------End----- Start Num
Sector # Boot Cyl Head Sect FS Cyl Head Sect Sect Sects
---------- - ---- ---- ---- ---- -- ---- ---- ---- ----------
---------- 0 0 80 0 1 1 0B 305 254 63 63
4915827 0 1 00 [ 306 0 1] 0F [ 307 254 63] 4915890
115186050 [Large Drive Placeholders] 306 0 1
7475 254 63 Actual Values 4915890 0 00 306 1 1 0B 777
254 63 4915953 7582617 4915890 1 00 778 0 1 05 [1023
254 63] 12498570 20482875 [Large Drive Placeholders]
778 0 1 2052 254 63 Actual Values 12498570 0 00 778 1
1 0B [1023 254 63] 12498633 20482812 [Large Drive Placeholders]
778 1 1 2052 254 63 Actual Values 12498570 1 00 [ 133 0
1] 05 [ 307 254 63] 35037765 85064175 [Large Drive Placeholders]
2181 0 1 7475 254 63 Actual Values 35037765 0 00 [ 133
1 1] 0B [ 735 254 63] 35037828 9687132 [Large Drive
Placeholders] 2181 1 1 2783 254 63 Actual
Values 35037765 1 00 [ 736 0 1] 05 [ 307 254 63] 44724960
75376980 [Large Drive Placeholders] 2784 0 1
7475 254 63 Actual Values 44724960 0 00 [ 736 1 1] 0B [ 752
254 63] 44725023 16723602 [Large Drive Placeholders]
2784 1 1 3824 254 63 Actual Values 44724960 1 00 [ 753
0 1] 05 [ 307 254 63] 61448625 58653315 [Large Drive
Placeholders] 3825 0 1 7475 254 63 Actual
Values 61448625 0 00 [ 753 1 1] 0B [ 302 254 63] 61448688
25671807 [Large Drive Placeholders] 3825 1 1
5422 254 63 Actual Values 61448625 1 00 [ 303 0 1] 05 [ 307
254 63] 87120495 32981445 [Large Drive Placeholders]
5423 0 1 7475 254 63 Actual Values 87120495 0 00 [ 303
1 1] 0B [ 307 254 63] 87120558 32981382 [Large Drive
Placeholders] 5423 1 1 7475 254 63 Actual
Values

Disk[0], Part[44724960]: Warning #113: EPBR partition starting at 44724960
overlaps previous EPBR partition.

Disk[0], Part[61448625]: Warning #113: EPBR partition starting at 61448625
overlaps previous EPBR partition.

Disk[0], Part[87120495]: Warning #113: EPBR partition starting at 87120495
overlaps previous EPBR partition.

Thank you very much for responding, Bill (and PCR). I'm sorry for not
responding sooner, but your discussion with PCR has me reeling a bit. I
will probably take your suggestion about the trial version of DiskPatch --
especially since it read-only. At this point I am not willing to lose any
files on this HDD, and I'm not ready to commit to any procedure until I'm
1000% sure of its outcome. There used to be a second HDD in this machine,
and I've spent many hours hacking the registry to correct its addresses.
This box was destined for disassembly until I had a problem with my XP
machine. I'm wondering if the removal of the drive had something to do with
the misbehaviour of Partition Magic.

I will probably start working on this mess during the upcoming weekend.
Hopefully I can image and burn my drives to CD just in case I trash the HDD
while trying to fix it. Last night I remembered that I imaged these drives
and burned them to DVD on my XP machine -- which is currently down due a yet
undiagnosed hardware issue.

In the meantime, I'm hoping there may be a PowerQuest veteran at Symantec
who may be able to help. I've only used PQ tech support once before (with
Drive Image) and once I was sure they understood my problem, they quickly
solved it. Hopefully this time around, I can be so lucky.

It sounds like you have experience with PM, Bill. Do you think there's any
chance that reallocating the space on the J: drive might solve the problem?

Also, I'm thinking of snipping PartInfo from this post. Will that cause any
problem with future responses?

BTW, whatever you guys are doing with your quotes has made subsequent posts
pretty unreadable -- tons of breaks.
--
Hoppy
~~