Sign in with
Sign up | Sign in
Your question

WinXP NTFS Cross-Linked Files

Last response: in Windows XP
Share
October 12, 2004 4:30:34 PM

Archived from groups: microsoft.public.windowsxp.perform_maintain (More info?)

WinXP SP1 (NTFS).

Hard drive currently partitioned as following:

Linux (Main) - Linux (Home Dirs) - Linux Swap - Win98 - Free Space - WinXP -
Free Space

(BootMagic 8.0 is boot loader in MBR.)

I've been trying, for days, to move the WinXP partition down to end of the
Win98 partition in order to consolidate all the free space.

Using PartitionMagic 8.0, installed on both the Win98 and WinXP partitions.

PartitionMagic, whether attempted from Win98 or WinXP, reports that the
WinXP partition can't be moved because of cross-linked files.

I have defragged the WinXP partition and ran chkdsk several times. I ran
chkdsk with the proper attributes, both as startup options and from the
Recovery Console. Chkdsk reports finding the cross-linked file (seems to be
just one) and reports it has been fixed.

HDD Regenerator and Spinrite report no errors with the WinXP partition.
PartitionMagic reports no errors with the WinXP partition when "Check For
Errors" is run -- but every attempt to actually move it results in
"Cross-Linked Files Found" and it aborts.

I've ran chkdsk from within WinXP, (right clicking drive, properties, check
for errors, enable "Find and Fix" and "Find Bad Sectors") and I've ran it
from command prompt (chkdsk /f) -- allowing WinXP to reboot and run it as a
startup process. I've ran it from Recovery Console (chkdsk /r). All methods
report it has fixed the file and the volume is clean. HDD Regenerator and
Spinrite then report zero problems with the WinXP partition.
PartitionMagic, then reports zero problems with "Check For Errors".
Attempts to move the partition, however, keep resulting in this cross-linked
file.

Downloading PartitionMagic patch (8.0 to 8.01) right now. Don't know if
it's PM issue or not, but going install the patch.

Anyone using a better disk maintenance program than "chkdsk"? Doesn't seem
to work very well with WinXP NTFS. (I do have Norton Systemworks installed,
but Norton's disk checker just refers me to use WinXP's "chkdsk").

TIA
Anonymous
October 12, 2004 4:30:35 PM

Archived from groups: microsoft.public.windowsxp.perform_maintain (More info?)

Did you try running Disk Doctor from SystemWorks? I can't remember if it
will fix what you are asking...just a thought...



"Eric" <none@nospam.not> wrote in message
news:10mo1l7i7ajia26@corp.supernews.com...
> WinXP SP1 (NTFS).
>
> Hard drive currently partitioned as following:
>
> Linux (Main) - Linux (Home Dirs) - Linux Swap - Win98 - Free Space -
> WinXP -
> Free Space
>
> (BootMagic 8.0 is boot loader in MBR.)
>
> I've been trying, for days, to move the WinXP partition down to end of the
> Win98 partition in order to consolidate all the free space.
>
> Using PartitionMagic 8.0, installed on both the Win98 and WinXP
> partitions.
>
> PartitionMagic, whether attempted from Win98 or WinXP, reports that the
> WinXP partition can't be moved because of cross-linked files.
>
> I have defragged the WinXP partition and ran chkdsk several times. I ran
> chkdsk with the proper attributes, both as startup options and from the
> Recovery Console. Chkdsk reports finding the cross-linked file (seems to
> be
> just one) and reports it has been fixed.
>
> HDD Regenerator and Spinrite report no errors with the WinXP partition.
> PartitionMagic reports no errors with the WinXP partition when "Check For
> Errors" is run -- but every attempt to actually move it results in
> "Cross-Linked Files Found" and it aborts.
>
> I've ran chkdsk from within WinXP, (right clicking drive, properties,
> check
> for errors, enable "Find and Fix" and "Find Bad Sectors") and I've ran it
> from command prompt (chkdsk /f) -- allowing WinXP to reboot and run it as
> a
> startup process. I've ran it from Recovery Console (chkdsk /r). All
> methods
> report it has fixed the file and the volume is clean. HDD Regenerator and
> Spinrite then report zero problems with the WinXP partition.
> PartitionMagic, then reports zero problems with "Check For Errors".
> Attempts to move the partition, however, keep resulting in this
> cross-linked
> file.
>
> Downloading PartitionMagic patch (8.0 to 8.01) right now. Don't know if
> it's PM issue or not, but going install the patch.
>
> Anyone using a better disk maintenance program than "chkdsk"? Doesn't
> seem
> to work very well with WinXP NTFS. (I do have Norton Systemworks
> installed,
> but Norton's disk checker just refers me to use WinXP's "chkdsk").
>
> TIA
>
>
>
>
October 12, 2004 6:27:05 PM

Archived from groups: microsoft.public.windowsxp.perform_maintain (More info?)

> > WinXP SP1 (NTFS).
> >
> > Hard drive currently partitioned as following:
> >
> > Linux (Main) - Linux (Home Dirs) - Linux Swap - Win98 - Free Space -
> > WinXP -
> > Free Space
> >
> > (BootMagic 8.0 is boot loader in MBR.)
> >
> > I've been trying, for days, to move the WinXP partition down to end of
the
> > Win98 partition in order to consolidate all the free space.
> >
> > Using PartitionMagic 8.0, installed on both the Win98 and WinXP
> > partitions.
> >
> > PartitionMagic, whether attempted from Win98 or WinXP, reports that the
> > WinXP partition can't be moved because of cross-linked files.
> >
> > I have defragged the WinXP partition and ran chkdsk several times. I
ran
> > chkdsk with the proper attributes, both as startup options and from the
> > Recovery Console. Chkdsk reports finding the cross-linked file (seems
to
> > be
> > just one) and reports it has been fixed.
> >
> > HDD Regenerator and Spinrite report no errors with the WinXP partition.
> > PartitionMagic reports no errors with the WinXP partition when "Check
For
> > Errors" is run -- but every attempt to actually move it results in
> > "Cross-Linked Files Found" and it aborts.
> >
> > I've ran chkdsk from within WinXP, (right clicking drive, properties,
> > check
> > for errors, enable "Find and Fix" and "Find Bad Sectors") and I've ran
it
> > from command prompt (chkdsk /f) -- allowing WinXP to reboot and run it
as
> > a
> > startup process. I've ran it from Recovery Console (chkdsk /r). All
> > methods
> > report it has fixed the file and the volume is clean. HDD Regenerator
and
> > Spinrite then report zero problems with the WinXP partition.
> > PartitionMagic, then reports zero problems with "Check For Errors".
> > Attempts to move the partition, however, keep resulting in this
> > cross-linked
> > file.
> >
> > Downloading PartitionMagic patch (8.0 to 8.01) right now. Don't know if
> > it's PM issue or not, but going install the patch.
> >
> > Anyone using a better disk maintenance program than "chkdsk"? Doesn't
> > seem
> > to work very well with WinXP NTFS. (I do have Norton Systemworks
> > installed,
> > but Norton's disk checker just refers me to use WinXP's "chkdsk").
> >
> > TIA
> >

> Did you try running Disk Doctor from SystemWorks? I can't remember if it
> will fix what you are asking...just a thought...

As I wrote, Norton (at least my older version, I don't know about Norton
2005) System Works' disk checker (Disk Doctor) can't work with NTFS. It
simply refers you to run WinXP's built-in checker (chkdsk) when you attempt
to run it.
October 12, 2004 7:03:33 PM

Archived from groups: microsoft.public.windowsxp.perform_maintain (More info?)

All the software that I've used to test the entire drive reports that the
sectors are all good. The SMART tests reports the drive as being 100%
healthly. Software reports there are still many available "reserve
sectors". This leads me to believe that I'm not dealing with a hardware
issue, but a file issue (that cross-linked file).

I made some progress today, I think. By looking into the logs of XP's Event
Viewer, I found what chkdsk had logged. NTFS, apparently, reports it as a
file number and not a file name though. I'm going to do a google later to
see how you can determine a particular file from a file number. I seem to
remember back in the DOS/Win3.11 days that repairing a cross-linked file was
very simple: simply copy the cross-linked file onto a new medium, delete
the original cross-linked file on the drive, and then copy it back from the
medium. I'll give that a try and see if it'll work for NTFS...

Thanks..
!