George Hester <hesterloli@hotmail.com> wrote:
> Ok got it the report is very big. But what I will do is just
> post the parts that have to do with the drive in question:

Whoops, managed to snip the later question, lets have another go.

> What do you think man? Doesn't look like anything????

Yes, looks like the Maxtor has a problem with pending sectors
that are likely the problem with the chkdsk freezing.

And you appear to be running the drives much too hot too.

> Now the application that VWWall provided from up top,
> TestDisk said the partition could not be recovered.

Likely due to those two pending sectors.

> Then said it may be recovered if I change the geometry of the drive.

That is mad. Presumably you are using an AUTO drive type ?

> I am a little hesitant to do that for how could the
> Geometry change from whatever it was to wrong?

Indeed. It likely would have suggested that even if you had run it initially tho.

> It may always have been wrong and worked fine.

Yep, bet that's it.

> It wants to reduce the number of cylinders.

Tell it to get stuffed.


> "Rod Speed" <rod.speed.aaa@gmail.com> wrote in message
> news:52ncv1F1pblcnU1@mid.individual.net...
>> George Hester <hesterloli@hotmail.com> wrote
>>
>>> Yes Rod I get a what do you call it a check
>>> sum error copying a file off the partition.
>>
>> That wont be due to a partition table that needs repair.
>>
>>> Not every file but at least one file. It gets about 25%
>>> completely copied to another drive then just hangs for
>>> a bit then errors with a checksum error.
>>
>> Thats much more likely to be a hard drive hardware problem.
>> Post the Everest SMART report for the drive.
>> http://www.majorgeeks.com/download.php?det=4181
>>
>>> But I can open the file normally while it is on that partition.
>>
>>> Yes it is NTFS Windows 2000.
>>
>>> Manually repair. Yes I know believe me when I did it before
>>> I looked long and hard at it before I made the plunge to DO IT
>>
>> Unlikely that it was the same problem then.
>>
>>> gpart I am going to try a suggestion from above first then gpart
>>> after..
>>
>>
>>> Rod Speed <rod.speed.aaa@gmail.com> wrote
>>>> George Hester <hesterloli@hotmail.com> wrote
>>
>>>>> Just to let you know there are 2 partitions on the disk. The
>>>>> first and the secong. The secong has no issue at all. The first
>>>>> must be messed up. Obviously this is not the disk. So what else
>>>>> could it be?
>>>>
>>>> Do you get any other symptoms of a problem except that chkdsk hang
>>>> ?
>>>>
>>>> If not, you can see a situation where the file structures get into
>>>> a state that chkdsk cant handle, even tho access to the files is
>>>> still fine, particularly with an NTFS formatted partition. NTFS is
>>>> quite complex and even chkdsk can get confused at times.
>>>>
>>>>> If you know of a partition table repairer even
>>>>> if it is not the issue I could at least try it.
>>>>
>>>> Not clear if you mean an automatic repairer or one that you
>>>> can use manually to manipulate the partition table entry.
>>>>
>>>> gparted is certainly worth trying, but be careful, it isnt hard
>>>> to wreck a perfectly good partition table with it, at least image
>>>> the entire physical drive before molesting the partition table.
>>>>
>>>>
>>>>> "George Hester" <hesterloli@hotmail.com> wrote in message
>>>>> news:45c62b72$0$4927$4c368faf@roadrunner.com...
>>>>>> Ok what do you suggest is the issue?
>>>>>>
>>>>>> --
>>>>>>
>>>>>> George Hester
>>>>>> _________________________________
>>>>>> "Rod Speed" <rod.speed.aaa@gmail.com> wrote in message
>>>>>> news:52mmenF1on4mfU1@mid.individual.net...
>>>>>>> George Hester <hesterloli@hotmail.com> wrote:
>>>>>>>
>>>>>>>> I located a free partition table fixer on the Net a couple
>>>>>>>> months ago and used it successfully. I need it again and was
>>>>>>>> wondering if anyone knew of a free one on the Net because I
>>>>>>>> can't find it. For some reason it looks like the first
>>>>>>>> partition on one of my drives got hosed. I tried to run
>>>>>>>> chkdsk on it but when it got to the last part checking data it
>>>>>>>> just stopped at 0% complete and went no further.
>>>>>>>
>>>>>>> That is unlikely to be due to a partition table problem.