findpart "Fdisk F6 sector"

  • Thread starter Thread starter MartyEgan
  • Start date Start date
M

MartyEgan

Hello again! This time I'm at work and someone's PC crashed. They
were using it normally, it began to perform slowly. They rebooted and
it never came up successfully again. After POST, they got an error in
text mode. I'll find out the error tomorrow. Drive is a Maxtor 160G
SATA.

I've mounted the drive as a secondary drive in a working XP SP2 system,
and run findpart (see below). I also installed a S.M.A.R.T utility
called "HDD Health" from http://www.panterasoft.com. Ever since I
installed the drive as a secondary on this working system, it is very
slow in explorer. The HDD Health utility popped up two errors a few
minutes after I ran it. One said "Attribute Raw Read Error Rate
changes from 70 to 69". The other says "Attribute TA Counter Increased
changes from 252 to 253."

Taking a clue from my previous post on a different drive, I ran the
command below, with the output shown also. It has run a long time
without generating any files in the c:\temp folder. I'll let it run
overnight.

C:\temp\findpart>findpart findntfs 2 5 0 1 backupboot 268333695 copy

FindNTFS, version FP 4.67 - for Windows 95/98/ME/NT/2000/XP.
Copyright Svend Olaf Mikkelsen, 2005.

OS: Windows 5.1.2600 Service Pack 2

Disk: 2 Cylinders: 19452 Heads: 255 Sectors: 63 MB: 152586

CHS 5/0/1 LBA: 80325

Options: Backupboot: 268333695

Searching ... ..








OS: Windows 5.1.2600 Service Pack 2

Disk: 2 Cylinders: 19452 Heads: 255 Sectors: 63 MB: 152586

--PCyl N ID -----Rel -----Num ---MB --Start CHS- ---End CHS-- BS CHS
0 - 06 63 80262 39 0 1 1 4 254 63 B OK
0 - 07 80325268333695131022 5 0 1 16707 254 63 B OK
Fdisk F6 sector 2547 0 1
Fdisk F6 sector 2547 1 1
0 - 07 80325312416055152546 5 0 1 19451 254 63 BU OK

------FAT CHS -Size Cl --Root -Good -Rep. Maybe --Bad YY-MM-DD DataMB
0 1 2 79 2 512 79 0 0 0 04-11-17 7

Partitions according to partition tables on second harddisk:

--PCyl N ID -----Rel -----Num ---MB --Start CHS- ---End CHS-- BS CHS
0 1 DE 63 80262 39 0 1 1 4 254 63 OK
0 2*07 80325 268333695 131022 5 0 1 16707*254 63 OK OK


Any ideas? Am I on the right track? I'm wondering if the drive is
failing, based on the SMART errors.
 
MartyEgan said:
Hello again! This time I'm at work and someone's PC crashed. They
were using it normally, it began to perform slowly. They rebooted and
it never came up successfully again. After POST, they got an error in
text mode. I'll find out the error tomorrow. Drive is a Maxtor 160G
SATA.

I've mounted the drive as a secondary drive in a working XP SP2
system, and run findpart (see below). I also installed a S.M.A.R.T
utility called "HDD Health" from http://www.panterasoft.com. Ever
since I installed the drive as a secondary on this working system, it
is very slow in explorer. The HDD Health utility popped up two
errors a few minutes after I ran it. One said "Attribute Raw Read
Error Rate changes from 70 to 69". The other says "Attribute TA
Counter Increased changes from 252 to 253."

Taking a clue from my previous post on a different drive, I ran the
command below, with the output shown also. It has run a long time
without generating any files in the c:\temp folder. I'll let it run
overnight.

C:\temp\findpart>findpart findntfs 2 5 0 1 backupboot 268333695 copy

FindNTFS, version FP 4.67 - for Windows 95/98/ME/NT/2000/XP.
Copyright Svend Olaf Mikkelsen, 2005.

OS: Windows 5.1.2600 Service Pack 2

Disk: 2 Cylinders: 19452 Heads: 255 Sectors: 63 MB: 152586

CHS 5/0/1 LBA: 80325

Options: Backupboot: 268333695

Searching ... ..








OS: Windows 5.1.2600 Service Pack 2

Disk: 2 Cylinders: 19452 Heads: 255 Sectors: 63 MB: 152586

--PCyl N ID -----Rel -----Num ---MB --Start CHS- ---End CHS-- BS CHS
0 - 06 63 80262 39 0 1 1 4 254 63 B OK
0 - 07 80325268333695131022 5 0 1 16707 254 63 B OK
Fdisk F6 sector 2547 0 1
Fdisk F6 sector 2547 1 1
0 - 07 80325312416055152546 5 0 1 19451 254 63 BU OK

------FAT CHS -Size Cl --Root -Good -Rep. Maybe --Bad YY-MM-DD DataMB
0 1 2 79 2 512 79 0 0 0 04-11-17 7

Partitions according to partition tables on second harddisk:

--PCyl N ID -----Rel -----Num ---MB --Start CHS- ---End CHS-- BS CHS
0 1 DE 63 80262 39 0 1 1 4 254 63 OK
0 2*07 80325 268333695 131022 5 0 1 16707*254 63 OK OK


Any ideas? Am I on the right track? I'm wondering if the drive is
failing, based on the SMART errors.
Click to expand...

I prefer the Everest display of SMART data myself. What does that say ?
 
Taking a clue from my previous post on a different drive, I ran the
command below, with the output shown also. It has run a long time
without generating any files in the c:\temp folder. I'll let it run
overnight.

C:\temp\findpart>findpart findntfs 2 5 0 1 backupboot 268333695 copy

FindNTFS, version FP 4.67 - for Windows 95/98/ME/NT/2000/XP.
Copyright Svend Olaf Mikkelsen, 2005.

OS: Windows 5.1.2600 Service Pack 2

Disk: 2 Cylinders: 19452 Heads: 255 Sectors: 63 MB: 152586

CHS 5/0/1 LBA: 80325

Options: Backupboot: 268333695

Searching ... ..
Click to expand...
OS: Windows 5.1.2600 Service Pack 2

Disk: 2 Cylinders: 19452 Heads: 255 Sectors: 63 MB: 152586

--PCyl N ID -----Rel -----Num ---MB --Start CHS- ---End CHS-- BS CHS
0 - 06 63 80262 39 0 1 1 4 254 63 B OK
0 - 07 80325268333695131022 5 0 1 16707 254 63 B OK
Fdisk F6 sector 2547 0 1
Fdisk F6 sector 2547 1 1
0 - 07 80325312416055152546 5 0 1 19451 254 63 BU OK

------FAT CHS -Size Cl --Root -Good -Rep. Maybe --Bad YY-MM-DD DataMB
0 1 2 79 2 512 79 0 0 0 04-11-17 7

Partitions according to partition tables on second harddisk:

--PCyl N ID -----Rel -----Num ---MB --Start CHS- ---End CHS-- BS CHS
0 1 DE 63 80262 39 0 1 1 4 254 63 OK
0 2*07 80325 268333695 131022 5 0 1 16707*254 63 OK OK


Any ideas? Am I on the right track? I'm wondering if the drive is
failing, based on the SMART errors.
Click to expand...

My advice generally is that if nothing at all happens on the Findpart
FindNTFS search screen for 5 minutes searching a partition with bad
sectors, the search should be stopped, and other methods used.

On the other hand I had a user who ignored that, and 90 per cent of
the files were copied, which may have been all files that could be
copied.

At least it can be said that the Findpart FindNTFS command does not
automatically fully minimize the number of read attempts to bad
sectors.

In this case there is a boot sector for the 131022 MB partition, but
since the backupboot sector must be assumed to be equal, it does not
matter that the backup boot sector was used.

I am not aware of an automated optimal recovery process for an NTFS
partition with bad sectors, but I can do something in mail for that.

In order to protect the partition, and prevent Windows from slowing
down due to the read attempts to bad sectors, the problem partition
should be made hidden in the partition tables.

The Fdisk F6 sectors just shows that at some time a partition was made
using DOS/Windows 95/98/ME Fdisk.
 
Back
Top