A partition table repairer

[George Hester]

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. Thanks

 

[CBFalconer]

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. Thanks

fdisk /mbr. Otherwise boot up Knoppix and run gparted. In 25
years of using PCs I have never seen a fouled partition table. You
must have faulty drives, controllers, memory, or something. Fix
that first.

--
<http://www.cs.auckland.ac.nz/~pgut001/pubs/vista_cost.txt>

"A man who is right every time is not likely to do very much."
-- Francis Crick, co-discover of DNA
"There is nothing more amazing than stupidity in action."
-- Thomas Matthews

 

[Rod Speed]

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.

 

[George Hester]

Ok what do you suggest is the issue?

 

[George Hester]

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? If you know of a
partition table repairer even if it is not the issue I could at least try
it. Thanks.

 

[George Hester]

Hi Falconer. This is not a boot disk so mbr is not really the issue. It is
just a partition table I believe. Well it might be but when I had to do it
before I actually corrupted the partition table. I forget how I did it but
I did. On a different machine not the one where I am having this issue.
Remember the disk in question has two partitions on it. The second one is
not a problem Only the first. Anyway I know there is a free partition
table fixer out there but I just can't seem to find it again. Thought I'd
come here and ask but if you don't know of one that's OK.

 

[VWWall]

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. Thanks

Try here for TestDisk:

http://www.cgsecurity.org/wiki/TestDisk_Download

 

[Rod Speed]

Ok what do you suggest is the issue?

Most likely the file structures have got stomped on, not the partition table.

 

[Rod Speed]

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]

Ok Rod. Now what do you think of this assuming what you say is true? Do
you think I could hook up to that partition over a network to a movie that
is on that partition and play the movie entirely? I cannot copy it off but
I can play it. If the "file structure" was stomped do you think that would
be possible?

 

[George Hester]

Yes Rod I get a what do you call it a check sum error copying a file off the
partition. 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. 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
gpart I am going to try a suggestion from above first then gpart after..

 

[Rod Speed]

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.

 

[Rod Speed]

Ok Rod. Now what do you think of this assuming what you
say is true? Do you think I could hook up to that partition over
a network to a movie that is on that partition and play the movie
entirely? I cannot copy it off but I can play it. If the "file structure"
was stomped do you think that would be possible?

No, it looks more like a hardware problem.

 

[George Hester]

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:

--------[ EVEREST Home Edition (c) 2003-2005 Lavalys,
Inc. ]------------------------------------------------------------

Version EVEREST v2.20.405
Homepage
http://www.lavalys.com/
Report Type Quick Report
Computer HESTER95 (Gateway P1)
Generator Administrator
Operating System Microsoft Windows 2000
Professional 5.0.2195 (Win2000 Retail)
Date 2007-02-04
Time 22:53

Here I found the Smart Report:

--------[
SMART ]---------------------------------------------------------------------
----------------------------------

[ WDC AC31600H (WD-WT2895101913) ]

01 Raw Read Error Rate 51 200 200 0 OK:
Value is normal
04 Start/Stop Count 10 99 99 1677 OK:
Value is normal
0A Spin Retry Count 51 100 100 0 OK:
Value is normal
0B Calibration Retry Count 51 100 100 0 OK:
Value is normal

[ WDC WD600BB-00CAA1 (WD-WMA8F2753117) ]

01 Raw Read Error Rate 51 200 200 0 OK:
Value is normal
03 Spin Up Time 21 101 93 4008 OK:
Value is normal
04 Start/Stop Count 40 100 100 311 OK:
Value is normal
05 Reallocated Sector Count 140 200 200 0 OK:
Value is normal
07 Seek Error Rate 51 200 200 0 OK:
Value is normal
09 Power-On Time Count 0 67 67 24492 OK:
Always passing
0A Spin Retry Count 51 100 100 0 OK:
Value is normal
0B Calibration Retry Count 51 100 100 0 OK:
Value is normal
0C Power Cycle Count 0 100 100 308 OK:
Always passing
C4 Reallocation Event Count 0 200 200 0 OK:
Always passing
C5 Current Pending Sector Count 0 200 200 0 OK:
Always passing
C6 Off-Line Uncorrectable Sector Count 0 200 200 0 OK:
Always passing
C7 Ultra ATA CRC Error Rate 0 200 253 23 OK:
Always passing
C8 Write Error Rate 51 200 200 0 OK:
Value is normal
_______________________________________________________________

Below is the drive that contains the problem partition

[ Maxtor 6L300R0 (L60GWA9H) ]

03 Spin Up Time 63 178 178 14465 OK:
Value is normal
04 Start/Stop Count 0 253 253 47 OK:
Always passing
05 Reallocated Sector Count 63 253 253 2 OK:
Value is normal
06 Read Channel Margin 100 253 253 0 OK:
Value is normal
07 Seek Error Rate 0 253 252 0 OK:
Always passing
08 Seek Time Performance 187 252 246 56415 OK:
Value is normal
09 Power-On Time Count 0 232 232 60075 OK:
Always passing
0A Spin Retry Count 157 253 252 0 OK:
Value is normal
0B Calibration Retry Count 223 253 252 0 OK:
Value is normal
0C Power Cycle Count 0 253 253 52 OK:
Always passing
C0 Power-Off Retract Count 0 253 253 0 OK:
Always passing
C1 Load/Unload Cycle Count 0 253 253 0 OK:
Always passing
C2 Temperature 0 50 253 50 OK:
Always passing
C3 Hardware ECC Recovered 0 253 252 12790 OK:
Always passing
C4 Reallocation Event Count 0 251 251 2 OK:
Always passing
C5 Current Pending Sector Count 0 253 253 2 OK:
Always passing
C6 Off-Line Uncorrectable Sector Count 0 245 245 8 OK:
Always passing
C7 Ultra ATA CRC Error Rate 0 253 253 0 OK:
Always passing
C8 Write Error Rate 0 253 252 0 OK:
Always passing
C9 <vendor-specific> 0 253 252 0 OK:
Always passing
CA <vendor-specific> 0 253 252 0 OK:
Always passing
CB <vendor-specific> 180 253 252 0 OK:
Value is normal
CC <vendor-specific> 0 253 252 0 OK:
Always passing
CD <vendor-specific> 0 253 252 0 OK:
Always passing
CF <vendor-specific> 0 253 252 0 OK:
Always passing
D0 <vendor-specific> 0 253 252 0 OK:
Always passing
D1 <vendor-specific> 0 241 241 152 OK:
Always passing
D2 <vendor-specific> 0 253 252 0 OK:
Always passing
D3 <vendor-specific> 0 253 252 0 OK:
Always passing
D4 <vendor-specific> 0 253 252 0 OK:
Always passing

[ WDC WD600BB-00CFC0 (WD-WMA9F1054075) ]

01 Raw Read Error Rate 51 200 200 0 OK:
Value is normal
03 Spin Up Time 21 106 94 5491 OK:
Value is normal
04 Start/Stop Count 40 99 99 1091 OK:
Value is normal
05 Reallocated Sector Count 112 195 195 18 OK:
Value is normal
07 Seek Error Rate 51 200 200 0 OK:
Value is normal
09 Power-On Time Count 0 79 79 16018 OK:
Always passing
0A Spin Retry Count 51 100 100 0 OK:
Value is normal
0B Calibration Retry Count 51 100 100 0 OK:
Value is normal
0C Power Cycle Count 0 99 99 1047 OK:
Always passing
C4 Reallocation Event Count 0 194 194 6 OK:
Always passing
C5 Current Pending Sector Count 0 200 200 0 OK:
Always passing
C6 Off-Line Uncorrectable Sector Count 0 200 200 0 OK:
Always passing
C7 Ultra ATA CRC Error Rate 0 200 253 0 OK:
Always passing
C8 Write Error Rate 51 200 200 0 OK:
Value is normal


--------[ Debug -
PCI ]-----------------------------------------------------------------------
--------------------------

B00 D00 F00: Intel 82437FX Triton System Controller - TSC [A-2]

Offset 00: 86 80 2D 12 06 00 00 22 02 00 00 06 00 40 00 00
Offset 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Offset 20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Offset 30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Offset 40: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Offset 50: 88 00 41 00 00 00 00 02 53 10 55 05 00 00 00 00
Offset 60: 08 08 10 10 10 00 00 00 0F 00 00 00 00 00 00 00
Offset 70: 00 00 0A 00 00 00 00 00 00 00 00 00 00 00 00 00
Offset 80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Offset 90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Offset A0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Offset B0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Offset C0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Offset D0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Offset E0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Offset F0: 00 00 00 00 00 00 00 00 00 00 00 00 00 F0 00 00

B00 D07 F00: Intel 82371FB PCI ISA IDE Xcelerator - PIIX [A-1]

Offset 00: 86 80 2E 12 0F 00 80 02 02 00 01 06 00 00 00 00
Offset 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Offset 20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Offset 30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Offset 40: 00 00 00 00 00 00 00 00 00 00 00 00 4D 00 60 00
Offset 50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Offset 60: 80 80 0A 80 00 00 00 00 00 F2 00 00 00 00 00 00
Offset 70: 0F 80 00 00 00 00 04 04 02 00 00 00 00 00 00 00
Offset 80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Offset 90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Offset A0: 03 00 E0 00 02 D0 00 A0 11 00 00 00 00 00 00 00
Offset B0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Offset C0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Offset D0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Offset E0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Offset F0: 00 00 00 00 00 00 00 00 10 0F 00 00 00 00 00 00

B00 D07 F01: Intel 82338FB IDE Controller

Offset 00: 86 80 30 12 05 00 80 02 02 80 01 01 00 40 00 00
Offset 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Offset 20: A1 FF 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Offset 30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Offset 40: 77 A3 77 A3 00 00 00 00 00 00 00 00 00 00 00 00
Offset 50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Offset 60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Offset 70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Offset 80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Offset 90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Offset A0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Offset B0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Offset C0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Offset D0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Offset E0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Offset F0: 00 00 00 00 00 00 00 00 10 0F 00 00 00 00 00 00

B00 D0F F00: Intel(R) PRO/1000 GT Desktop Adapter [NoDB]

Offset 00: 86 80 7C 10 07 01 30 02 05 00 00 02 08 40 00 00
Offset 10: 00 00 EE FF 00 00 EC FF 81 FE 00 00 00 00 00 00
Offset 20: 00 00 00 00 00 00 00 00 00 00 00 00 86 80 76 13
Offset 30: 00 00 00 00 DC 00 00 00 00 00 00 00 0A 01 FF 00
Offset 40: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Offset 50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Offset 60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Offset 70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Offset 80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Offset 90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Offset A0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Offset B0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Offset C0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Offset D0: 00 00 00 00 00 00 00 00 00 00 00 00 01 E4 22 C8
Offset E0: 00 20 00 28 07 00 02 00 00 00 40 00 00 00 00 00
Offset F0: 05 00 80 00 00 00 00 00 00 00 00 00 00 00 00 00

B00 D10 F00: S3 Trio64 V+ Video Adapter

Offset 00: 33 53 11 88 03 00 00 02 40 00 00 03 00 00 00 00
Offset 10: 00 00 00 F8 00 00 00 00 00 00 00 00 00 00 00 00
Offset 20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Offset 30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Offset 40: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Offset 50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Offset 60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Offset 70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Offset 80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Offset 90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Offset A0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Offset B0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Offset C0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Offset D0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Offset E0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Offset F0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00


--------[ Debug - Video
BIOS ]----------------------------------------------------------------------
--------------------

C000:0000 [email protected] VGA Compatible BIOS.
...f..a...
C000:0040 ....STB PowerGraph 64 Video (TRIO64V+) Enhanced VGA BIOS.
Versio
C000:0080 n 1.5..Copyright 1987-1992 Phoenix Technologies
Ltd.............
C000:00C0 ....................................Copyright 1992-1995 S3
Incor
C000:0100 porated..Copyright 1995 STB Systems, Inc...All Rights
Reserved..
C000:0140
.................................................................
C000:0180 ....10/27/9510/27/95...... 0.b.
...D.DDD...........T..D.........
C000:01C0
[email protected].:.;Z<.C.E.P.Q.S.T0U.X.].^.`.g.i.j....
C000:0200
[email protected]..........@..............<Uu...?..7.....Z..7..R...
C000:0240
......p......i.Z......f...^.....X..6.y<......t.f..0......)..f....
C000:0280
.......Y.U<...f.....k...R........Z.\...o.5<......u......RS......2
C000:02C0
<[Z.........R.............Z....;.............=.J=....3..E.u....
C000:0300
..=.t-....5.t.......+.u.....#.u..................3..3.3.3........
C000:0340
S3.2........c....3......t.3....u.......[.*.[.P..R......f;.....er
C000:0380
....gw.....Z...w..f.J;.......2.?;......Qu..C...k.-;.Y.2....X..@..
C000:03C0
;....W...I....6...FN.t..\..|..u................Q....:..|..}.....


--------[ Debug -
Unknown ]-------------------------------------------------------------------
--------------------------

Monitor AST2C58: Plug and Play Monitor [NoDB]
PCI/AGP 8086-107C: Intel(R) PRO/1000 GT Desktop Adapter [NoDB]
PnP PNPFFFF: Unsupported Device [NoDB]


----------------------------------------------------------------------------
--------------------------------------------

The names of actual companies and products mentioned herein may be the
trademarks of their respective owners.

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

Now the application that VWWall provided from up top, TestDisk said the
partition could not be recovered. Then said it may be recovered if I change
the geometry of the drive. I am a little hesitant to do that for how could
the Geometry change from whatever it was to wrong? It may always have been
wrong and worked fine.
It wants to reduce the number of cylinders.

 

[VWWall]

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:

--------[ EVEREST Home Edition (c) 2003-2005 Lavalys, [big snip of report]
--------[ Debug - Video
BIOS ]----------------------------------------------------------------------
--------------------

C000:0000 [email protected] VGA Compatible BIOS.
..f..a...
C000:0040 ....STB PowerGraph 64 Video (TRIO64V+) Enhanced VGA BIOS.
Versio
C000:0080 n 1.5..Copyright 1987-1992 Phoenix Technologies
Ltd.............

This looks like a very old BIOS. Is it? What date do you see on boot-up?

What size are the disks in question? What size are the partitions?
Looks like the WD is 60GB and the Maxtor 320GB.

A BIOS that old must be LBA28. I'm wondering if the problem came from
overwriting one of the partitions. This can happen if you attempt to
use a drive >137GB, (128GiB), on an old LBA28 BIOS, by making smaller
partitions.

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

Now the application that VWWall provided from up top, TestDisk said the
partition could not be recovered. Then said it may be recovered if I change
the geometry of the drive. I am a little hesitant to do that for how could
the Geometry change from whatever it was to wrong? It may always have been
wrong and worked fine.
It wants to reduce the number of cylinders.

I haven't used TestDisk in awhile. I've heard only good reports about
it. What kind of data is on the drive in question? You may be forced
to re-format after saving as much as you can get off.

Generally, when a drive starts to go bad it doesn't get better by
itself. If it's a file/partition problem the drive may be OK, but the
data's in danger.

Let us know if you do have a 320GB drive and the BIOS is an older one.
(Before about 2002, when LBA48 became common.)

 

[Rod Speed]

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:

Fine, comments interleaved below.

Below is the drive that contains the problem partition

[ Maxtor 6L300R0 (L60GWA9H) ]

03 Spin Up Time 63 178 178 14465
OK: Value is normal
04 Start/Stop Count 0 253 253 47
OK: Always passing
05 Reallocated Sector Count 63 253 253 2
OK: Value is normal
06 Read Channel Margin 100 253 253 0
OK: Value is normal
07 Seek Error Rate 0 253 252 0
OK: Always passing
08 Seek Time Performance 187 252 246 56415
OK: Value is normal
09 Power-On Time Count 0 232 232 60075
OK: Always passing
0A Spin Retry Count 157 253 252 0
OK: Value is normal
0B Calibration Retry Count 223 253 252 0
OK: Value is normal
0C Power Cycle Count 0 253 253 52
OK: Always passing
C0 Power-Off Retract Count 0 253 253 0
OK: Always passing
C1 Load/Unload Cycle Count 0 253 253 0
OK: Always passing
C2 Temperature 0 50 253 50

Urk, that is much too high given that you are presumably in winter currently.

OK: Always passing
C3 Hardware ECC Recovered 0 253 252 12790
OK: Always passing
C4 Reallocation Event Count 0 251 251 2
OK: Always passing
C5 Current Pending Sector Count 0 253 253 2
OK: Always passing

That is likely the problem, those two sectors.

C6 Off-Line Uncorrectable Sector Count 0 245 245 8
OK: Always passing
C7 Ultra ATA CRC Error Rate 0 253 253 0
OK: Always passing
C8 Write Error Rate 0 253 252 0
OK: Always passing
C9 <vendor-specific> 0 253 252 0
OK: Always passing
CA <vendor-specific> 0 253 252 0
OK: Always passing
CB <vendor-specific> 180 253 252 0
OK: Value is normal
CC <vendor-specific> 0 253 252 0
OK: Always passing
CD <vendor-specific> 0 253 252 0
OK: Always passing
CF <vendor-specific> 0 253 252 0
OK: Always passing
D0 <vendor-specific> 0 253 252 0
OK: Always passing
D1 <vendor-specific> 0 241 241 152
OK: Always passing
D2 <vendor-specific> 0 253 252 0
OK: Always passing
D3 <vendor-specific> 0 253 252 0
OK: Always passing
D4 <vendor-specific> 0 253 252 0
OK: Always passing

[ WDC WD600BB-00CFC0 (WD-WMA9F1054075) ]

01 Raw Read Error Rate 51 200 200 0
OK: Value is normal
03 Spin Up Time 21 106 94 5491
OK: Value is normal
04 Start/Stop Count 40 99 99 1091
OK: Value is normal
05 Reallocated Sector Count 112 195 195 18

That is a very high value too.

OK: Value is normal
07 Seek Error Rate 51 200 200 0
OK: Value is normal
09 Power-On Time Count 0 79 79 16018
OK: Always passing
0A Spin Retry Count 51 100 100 0
OK: Value is normal
0B Calibration Retry Count 51 100 100 0
OK: Value is normal
0C Power Cycle Count 0 99 99 1047
OK: Always passing
C4 Reallocation Event Count 0 194 194 6
OK: Always passing
C5 Current Pending Sector Count 0 200 200 0
OK: Always passing
C6 Off-Line Uncorrectable Sector Count 0 200 200 0
OK: Always passing
C7 Ultra ATA CRC Error Rate 0 200 253 0
OK: Always passing
C8 Write Error Rate 51 200 200 0
OK: Value is normal

The temperature is likely too high too, but this was
before those WDs had a SMART temperature sensor.

The rest wasnt the SMART report.

 

[Rod Speed]

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:

--------[ EVEREST Home Edition (c) 2003-2005 Lavalys, [big snip of report]
--------[ Debug - Video
BIOS
]----------------------------------------------------------------------
--------------------

C000:0000 [email protected] VGA Compatible BIOS.
..f..a...
C000:0040 ....STB PowerGraph 64 Video (TRIO64V+) Enhanced VGA
BIOS. Versio
C000:0080 n 1.5..Copyright 1987-1992 Phoenix Technologies
Ltd.............

This looks like a very old BIOS. Is it?

That is the video bios. Not relevant to LBA48

What date do you see on boot-up?

What size are the disks in question? What size are the partitions?
Looks like the WD is 60GB and the Maxtor 320GB.

A BIOS that old must be LBA28.

Nope, not when its the video bios.

I'm wondering if the problem came from overwriting one of the partitions. This can happen if you
attempt to use a drive >137GB, (128GiB), on an old LBA28 BIOS, by making smaller partitions.

What matters is whether he has LBA48 from the 2K service pack or not.

 

[Rod Speed]

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.

 

[George Hester]

Ugh I am at a loss here. I run chkdsk while Windows is runnig on it and it
completes and says everything is fine. It will not let me xcopy /c a file
off of it. Not all just one in particular. There is nothing on it very
important but important enough that I will probably never delete the
partition unless I can get most off of it. Remember everything on it is
available just not able to be copied or moved. I will probably retire the
disk if I can't do anything with it. Maybe I could Ghost it ???

Yes I have a 320 GB drive. Do you think I should try to Ghost the drive in
question onto that? That will probably fail. The app you suggested said I
should change the Geometry of the drive. What do you think about doing
that? What happens is after I try to copy this file elsewhere the drive
just seems to stop. No activity on the indicator lights. But the other
partition doesn't exhibit this behavior.

One other thing about this partition. Some time ago I noticed that I was
not able to put a file on it that was less than 100MB of the available
space. In other words if there was 200MB of available space any file I put
on it had to be smaller than about 75MB. And even that might have been too
much. A 5MB file would have gone on it.

I think in the meantime I will try to put it in a different machine. One a
little more advanced then P1.

--

George Hester
_________________________________

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:

--------[ EVEREST Home Edition (c) 2003-2005 Lavalys, [big snip of report]
--------[ Debug - Video
BIOS ]----------------------------------------------------------------------
--------------------

C000:0000 [email protected] VGA Compatible BIOS.
..f..a...
C000:0040 ....STB PowerGraph 64 Video (TRIO64V+) Enhanced VGA BIOS.
Versio
C000:0080 n 1.5..Copyright 1987-1992 Phoenix Technologies
Ltd.............

This looks like a very old BIOS. Is it? What date do you see on boot-up?

What size are the disks in question? What size are the partitions?
Looks like the WD is 60GB and the Maxtor 320GB.

A BIOS that old must be LBA28. I'm wondering if the problem came from
overwriting one of the partitions. This can happen if you attempt to
use a drive >137GB, (128GiB), on an old LBA28 BIOS, by making smaller
partitions.

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

Now the application that VWWall provided from up top, TestDisk said the
partition could not be recovered. Then said it may be recovered if I change
the geometry of the drive. I am a little hesitant to do that for how could
the Geometry change from whatever it was to wrong? It may always have been
wrong and worked fine.
It wants to reduce the number of cylinders.

I haven't used TestDisk in awhile. I've heard only good reports about
it. What kind of data is on the drive in question? You may be forced
to re-format after saving as much as you can get off.

Generally, when a drive starts to go bad it doesn't get better by
itself. If it's a file/partition problem the drive may be OK, but the
data's in danger.

Let us know if you do have a 320GB drive and the BIOS is an older one.
(Before about 2002, when LBA48 became common.)

 

[Rod Speed]

Ugh I am at a loss here. I run chkdsk while Windows is runnig
on it and it completes and says everything is fine. It will not let
me xcopy /c a file off of it. Not all just one in particular. There
is nothing on it very important but important enough that I will
probably never delete the partition unless I can get most off of it.

Remember everything on it is available just not able to be copied or moved.

You say above that its just one particular file that cant be copied.
What exactly is that file content wise ? You appeared to say
previously that its a video file.

I will probably retire the disk if I can't do anything with it.

You may be able to fix it by doing something about the temperature and then
getting PowerMax to fix the pending sectors by 'low level formatting' it.

Maybe I could Ghost it ???

Might be viable but it depends on that file, what it actually is.

Yes I have a 320 GB drive. Do you think I should
try to Ghost the drive in question onto that?

Depends on what that file actually is.

That will probably fail.

You should be able to ghost it by telling Ghost to ignore bad sectors.

The app you suggested said I should change the Geometry
of the drive. What do you think about doing that?

No evidence of a geometry problem.

What happens is after I try to copy this file elsewhere the drive just seems to stop.
No activity on the indicator lights. But the other partition doesn't exhibit this behavior.

Almost certainly that particular file has the pending sectors in it.

One other thing about this partition. Some time ago I noticed that
I was not able to put a file on it that was less than 100MB of the
available space. In other words if there was 200MB of available
space any file I put on it had to be smaller than about 75MB. And
even that might have been too much. A 5MB file would have gone on it.

What exactly happened when that failed ?

I think in the meantime I will try to put it in a different
machine. One a little more advanced then P1.

I doubt it will help. Just make sure you keep using an AUTO drive type.

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:

--------[ EVEREST Home Edition (c) 2003-2005 Lavalys, [big snip of report]
--------[ Debug - Video

BIOS
]----------------------------------------------------------------------

--------------------

C000:0000 [email protected] VGA Compatible
BIOS. ..f..a...
C000:0040 ....STB PowerGraph 64 Video (TRIO64V+) Enhanced VGA
BIOS. Versio
C000:0080 n 1.5..Copyright 1987-1992 Phoenix Technologies
Ltd.............

This looks like a very old BIOS. Is it? What date do you see on
boot-up?

What size are the disks in question? What size are the partitions?
Looks like the WD is 60GB and the Maxtor 320GB.

A BIOS that old must be LBA28. I'm wondering if the problem came
from overwriting one of the partitions. This can happen if you
attempt to
use a drive >137GB, (128GiB), on an old LBA28 BIOS, by making smaller
partitions.

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

Now the application that VWWall provided from up top, TestDisk said
the partition could not be recovered. Then said it may be
recovered if I change the geometry of the drive. I am a little
hesitant to do that for how could the Geometry change from whatever
it was to wrong? It may always have been wrong and worked fine.
It wants to reduce the number of cylinders.

I haven't used TestDisk in awhile. I've heard only good reports about
it. What kind of data is on the drive in question? You may be
forced
to re-format after saving as much as you can get off.

Generally, when a drive starts to go bad it doesn't get better by
itself. If it's a file/partition problem the drive may be OK, but
the data's in danger.

Let us know if you do have a 320GB drive and the BIOS is an older
one. (Before about 2002, when LBA48 became common.)