Help with problem diagnosis and data recovery

  • Thread starter Thread starter No-one
  • Start date Start date
N

No-one

A relative had a PC working correctly using XP Pro. Turned it off
one evening and when turned on the next day, it blue screened.

The HD is a Maxtor Diamond Plus 80GB IDE model. Only around six
months old, so still in warranty and only used for office
applications.

I tried it in other machines, same problem. The BIOS recognises the
drive (when placed as a slave in another PC) but the drive is not
accessible and doesn't show up in XP as being there in "My Computer"
or other file managers. (Strangely, IIRC it was identified in
System->Hardware devices, showing up as a SCSI drive !!)

HD s/w downloaded from Maxtor shows it passes the quick tests but
fails almost immediately on the full test, meaning the drive is
defective.

Any clues as to the cause - electronics? Any suggestions as to s/w
or other methods to recover the data ? (Almost the whole data had
been backed up a couple of days before this disaster but I would still
like to try and access the drive to grab back a couple of files)

Many thanks for any help.

Frank.
 
A relative had a PC working correctly using XP Pro. Turned it
off one evening and when turned on the next day, it blue screened.
Click to expand...
The HD is a Maxtor Diamond Plus 80GB IDE model. Only around six
months old, so still in warranty and only used for office applications.
Click to expand...
I tried it in other machines, same problem. The BIOS recognises
the drive (when placed as a slave in another PC) but the drive is
not accessible and doesn't show up in XP as being there in "My
Computer" or other file managers. (Strangely, IIRC it was identified
in System->Hardware devices, showing up as a SCSI drive !!)
Click to expand...

Thats certainly a bit odd, havent noticed a failing drive do that with XP.
HD s/w downloaded from Maxtor shows it passes the quick tests but
fails almost immediately on the full test, meaning the drive is defective.
Click to expand...

Exactly what does it say about the failure ?
Any clues as to the cause - electronics?
Click to expand...

Possibly, particularly with it listed as SCSI in XP.

Could also just be a failure to read off the platters successfully
tho, due to a non electornic failure, usualy mechanical.
Any suggestions as to s/w or other methods to recover the data ?
Click to expand...

You'd need to spell out how it fails the full test.
 
The drive shows up in Device Manager but not My Computer. That means the
partition table is gone, possible due to a bad MBR sector.

I would start with the Windows version of findpart and search for bad
sectors. If there are not too many at the beginning, you should be able to
recover.

http://inet.uni2.dk/~svolaf/utilities.htm
 
Exactly what does it say about the failure ?
Click to expand...

Nothing. Just a fail with an error message that means nothing except
to Maxtor. (A 6 place display of characters and numbers). It enables
the completion of an RMA return.

Regards,

Frank
 
Further info:-

Partinfo reports:

==========================================================================================================
Disk Geometry Information for Disk 2: 9964 Cylinders, 255 Heads,
63 Sectors/Track
System PartSect # Boot BCyl Head Sect FS ECyl Head
Sect StartSect NumSects
===========================================================================================================
0 0 80 0 1 1 07 1023 254
63 63 81,915,372
Info: End C,H,S values were large drive placeholders.
Actual values are:
0 0 80 0 1 1 07 5098 254 63 63
81915372
0 1 00 1023 0 1 0F 1023 254
63 81,915,435 78,140,160
Info: Begin C,H,S values were large drive placeholders.
Info: End C,H,S values were large drive placeholders.
Actual values are:
0 1 00 5099 0 1 0F 9962 254 63 81915435
78140160

=============================================================
Partition Information for Disk 2: 78,160.0 Megabytes
Volume PartType Status Size MB PartSect #
StartSect TotalSects
=========================================================================
NTFS Pri,Boot 39,997.7 0 0
63 81,915,372
ExtendedX Pri 38,154.4 0 1
81,915,435 78,140,160
EPBR Log 0.0 None --
81,915,435 63
Unallocated Log 38,154.3 None --
81,915,498 78,140,097
Unallocated Pri 7.8 None --
160,055,595 16,065


=============================================================
=============================================================
Boot Record for drive *: (Drive: 2, Starting sector: 63, Type: NTFS)
===========================================================================================================
1. Jump: EB 52 90
2. OEM Name: NTFS
3. Bytes per Sector: 512
4. Sectors per Cluster: 8
5. Reserved Sectors: 0
6. Number of FATs: 0
7. Root Dir Entries: 0
8. Total Sectors: 0
9. Media Descriptor: 0xF8
10. Sectors per FAT: 0
11. Sectors per Track: 63 (0x3F)
12. Number of Heads: 255 (0xFF)
13. Hidden Sectors: 63 (0x3F)
14. Total Sectors (>32MB): 0 (0x0)
15. Unused: 0x80008000
16. Total NTFS Sectors: 81915371
17. MFT Start Cluster: 4
18. MFT Mirror Start Clust: 5119710
19. Clusters per FRS: 246
20. Clusters per Index Blk: 1
21. Serial Number: 0xDE44243A442417B3
22. Checksum: 0 (0x0)
23. Boot Signature: 0xAA55

====================================================

Findpart reports:

Findpart, version 4.37 - for Windows 95/98/ME/NT/2000/XP.
Copyright Svend Olaf Mikkelsen, 2003.

Searches for partitions type 01, 04, 06, 07, 0B, 0C, 0E, 82, 83,
plus Fdisk F6 and Lilo sectors. Information based on bootsectors
is marked B. If the disk is larger than supported by BIOS, the
supported part of the disk is examined. Disks are numbered from 1.

OS: Windows 5.1

Disk: 2 Cylinders: 9964 Heads: 255 Sectors: 63 MB: 78160

-PCyl N ID -----Rel -----Num ---MB -Start CHS- --End CHS-- BS CHS
0 - 07 63 81915372 39997 0 1 1 5098 254 63 B OK
5099 - 07 63 61432497 29996 5099 1 1 8922 254 63 B OK
8923 1 07 63 16707537 8157 8923* 1 1 9962*254 63 OK OK
There were sectors, which could not be read.

No FATs found.
There were sectors, which could not be read.

Partitions according to partition tables on second harddisk:

-PCyl N ID -----Rel -----Num ---MB -Start CHS- --End CHS-- BS CHS
0 1*07 63 81915372 39997 0 1 1 5098*254 63 OK OK
0 2 0F 81915435 78140160 38154 5099* 0 1 9962*254 63 OK

Error reading CHS: 5099 0 1
 
Findpart reports:

Findpart, version 4.37 - for Windows 95/98/ME/NT/2000/XP.
Copyright Svend Olaf Mikkelsen, 2003.
Click to expand...
OS: Windows 5.1

Disk: 2 Cylinders: 9964 Heads: 255 Sectors: 63 MB: 78160

-PCyl N ID -----Rel -----Num ---MB -Start CHS- --End CHS-- BS CHS
0 - 07 63 81915372 39997 0 1 1 5098 254 63 B OK
5099 - 07 63 61432497 29996 5099 1 1 8922 254 63 B OK
8923 1 07 63 16707537 8157 8923* 1 1 9962*254 63 OK OK
There were sectors, which could not be read.

No FATs found.
There were sectors, which could not be read.

Partitions according to partition tables on second harddisk:

-PCyl N ID -----Rel -----Num ---MB -Start CHS- --End CHS-- BS CHS
0 1*07 63 81915372 39997 0 1 1 5098*254 63 OK OK
0 2 0F 81915435 78140160 38154 5099* 0 1 9962*254 63 OK

Error reading CHS: 5099 0 1
Click to expand...

There are one or more bad sectors. The only thing known is that the
extended partition table in CHS 5099/0/1 is in a bad sector. That can
be repaired, but alternatives could be considered.

The disk could initially be copied sector by sector to a new disk
using special software.

Data could be copied from the 3 NTFS partitions using recovery
software to partitions on other disks.

Further examination could be done. This could be from boot to a DOS
floppy using the Findbad program from my page:

findbad 2 firstlast fp.txt

assuming the disk is disk 2 in DOS too. That may take about an hour to
run on this disk. If very many cylinders with bad sectors are found,
the search can be stopped, and alternatives considered.

Assuming space is present for copying files, the Findpart commands to
copy the files from the 3 NTFS partitions to current directory and
below would be:

findpart findntfs 2 0 1 1 copy
findpart findntfs 2 5099 1 1 copy
findpart findntfs 2 8923 1 1 copy
 
There are one or more bad sectors. The only thing known is that the
extended partition table in CHS 5099/0/1 is in a bad sector. That can
be repaired, but alternatives could be considered.
Click to expand...

I am afraid I am a total novice. How does one repair such a thing ?
The disk could initially be copied sector by sector to a new disk
using special software.

Data could be copied from the 3 NTFS partitions using recovery
software to partitions on other disks.
Click to expand...

I have used your FindNTFS software and copied files to a good disk.
There was only really one file needed that had not been previously
backed up to CD. THis file was recovered :-)) Many thanks to you.
Further examination could be done. This could be from boot to a DOS
floppy using the Findbad program from my page:

findbad 2 firstlast fp.txt

assuming the disk is disk 2 in DOS too. That may take about an hour to
run on this disk. If very many cylinders with bad sectors are found,
the search can be stopped, and alternatives considered.
Click to expand...

I have put the disk back into the original PC and am using FindBad on
it now.
Svend Olaf
Click to expand...

Many thanks Svend.

Best regards,

Frank
 
Further examination could be done. This could be from boot to a DOS
floppy using the Findbad program from my page:
Click to expand...

Here is the response:-


FindBad, version 1.5. Copyright Svend Olaf Mikkelsen, 2003.

Searches for bad sectors.

OS: DOS 6.00

Disk: 1 Cylinders: 9964 Heads: 255 Sectors: 63 MB: 78160

Start cylinder: 0 End cylinder: 9963 Firstlast

Only the first and last bad sector in each cylinder
will be shown.

-------- CHS ----- LBA Code Difference
0 22 62 1447 10
0 112 40 7095 10 5648
36 146 30 587567 10
Current cylinder: 100
Current cylinder: 200
Current cylinder: 300
Current cylinder: 400
Current cylinder: 500
Current cylinder: 600
Current cylinder: 700
Current cylinder: 800
Current cylinder: 900
Current cylinder: 1000
Current cylinder: 1100
Current cylinder: 1200
Current cylinder: 1300
Current cylinder: 1400
Current cylinder: 1500
Current cylinder: 1600
Current cylinder: 1700
Current cylinder: 1800
Current cylinder: 1900
Current cylinder: 2000
Current cylinder: 2100
Current cylinder: 2200
Current cylinder: 2300
Current cylinder: 2400
Current cylinder: 2500
2549 128 43 40957791 10
2549 130 33 40957907 10 116
2558 6 13 41094660 10
2558 6 21 41094668 10 8
2564 34 34 41192835 10
2568 42 50 41257615 10
2568 42 57 41257622 10 7
2571 84 49 41308455 10
2571 84 52 41308458 10 3
2589 252 5 41608165 10
2589 252 13 41608173 10 8
2590 144 10 41617431 10
2590 144 17 41617438 10 7
2598 11 13 41737575 10
Current cylinder: 2600
2623 18 19 42139647 10
2623 18 22 42139650 10 3
2627 134 51 42211247 10
2627 134 58 42211254 10 7
2630 113 59 42258127 10
2630 114 3 42258134 10 7
2632 22 46 42284511 10
2632 22 53 42284518 10 7
2635 74 63 42335999 10
2635 75 7 42336006 10 7
2659 69 10 42721191 10
2659 69 17 42721198 10 7
2693 219 60 43276901 10
2693 225 41 43277260 10 359
2695 47 48 43298183 10
2695 49 29 43298290 10 107
Current cylinder: 2700
2704 70 8 43444177 10
2704 74 8 43444429 10 252
2707 236 48 43502870 10
2755 31 52 44261079 10
2755 31 59 44261086 10 7
Current cylinder: 2800
2823 146 55 45360747 10
2823 153 43 45361176 10 429
Current cylinder: 2900
Current cylinder: 3000
Current cylinder: 3100
Current cylinder: 3200
Current cylinder: 3300
Current cylinder: 3400
Current cylinder: 3500
Current cylinder: 3600
Current cylinder: 3700
Current cylinder: 3800
Current cylinder: 3900
Current cylinder: 4000
Current cylinder: 4100
Current cylinder: 4200
Current cylinder: 4300
Current cylinder: 4400
Current cylinder: 4500
Current cylinder: 4600
Current cylinder: 4700
Current cylinder: 4800
Current cylinder: 4900
Current cylinder: 5000
5099 0 1 81915435 10
Current cylinder: 5100
Current cylinder: 5200
Current cylinder: 5300
Current cylinder: 5400
Current cylinder: 5500
Current cylinder: 5600
Current cylinder: 5700
Current cylinder: 5800
Current cylinder: 5900
Current cylinder: 6000
Current cylinder: 6100
Current cylinder: 6200
Current cylinder: 6300
Current cylinder: 6400
Current cylinder: 6500
Current cylinder: 6600
Current cylinder: 6700
Current cylinder: 6800
Current cylinder: 6900
Current cylinder: 7000
Current cylinder: 7100
Current cylinder: 7200
Current cylinder: 7300
Current cylinder: 7400
Current cylinder: 7500
Current cylinder: 7600
Current cylinder: 7700
Current cylinder: 7800
Current cylinder: 7900
Current cylinder: 8000
Current cylinder: 8100
Current cylinder: 8200
Current cylinder: 8300
Current cylinder: 8400
Current cylinder: 8500
Current cylinder: 8600
Current cylinder: 8700
Current cylinder: 8800
Current cylinder: 8900
Current cylinder: 9000
Current cylinder: 9100
Current cylinder: 9200
Current cylinder: 9300
Current cylinder: 9400
Current cylinder: 9500
Current cylinder: 9600
Current cylinder: 9700
Current cylinder: 9800
Current cylinder: 9900
 
Here is the response:-


FindBad, version 1.5. Copyright Svend Olaf Mikkelsen, 2003.

Searches for bad sectors.

OS: DOS 6.00

Disk: 1 Cylinders: 9964 Heads: 255 Sectors: 63 MB: 78160

Start cylinder: 0 End cylinder: 9963 Firstlast

Only the first and last bad sector in each cylinder
will be shown.

-------- CHS ----- LBA Code Difference
0 22 62 1447 10
0 112 40 7095 10 5648
36 146 30 587567 10
Click to expand...
Current cylinder: 5000
5099 0 1 81915435 10
Current cylinder: 5100
Click to expand...

All bad sectors are in the primary partition, except the one in the
extended partition table.

The partition tables could be edited to hide the primary partition,
and make the two logical partitions visible. If needed, I can make a
batch file for that.

My suggestion is that you keep the problem disk unchanged for a while
as kind of a backup. After that the disk could be zeroed using the
manufacturer tool for that. It is not known if this should be
considered as a disk problem, a system problem or a Windows problem.
 
My suggestion is that you keep the problem disk unchanged for a while
as kind of a backup. After that the disk could be zeroed using the
manufacturer tool for that. It is not known if this should be
considered as a disk problem, a system problem or a Windows problem.
Click to expand...

Thank you for your help. I have purchased a replacement drive and
will deal with its installation this afternoon. Would I be right in
thinking that the low-level format tool on the Maxtor utility disk
will let me wipe the faulty drive, isolate the bad sectors and let me
re-format and use it? (All needed data has been salvaged and my
relative does not wish to send back the disk since it has
commercial/private information on it)

Bes regards,

Frank
 
Thank you for your help. I have purchased a replacement drive and
will deal with its installation this afternoon. Would I be right in
thinking that the low-level format tool on the Maxtor utility disk
will let me wipe the faulty drive, isolate the bad sectors and let me
re-format and use it? (All needed data has been salvaged and my
relative does not wish to send back the disk since it has
commercial/private information on it)

Bes regards,

Frank
Click to expand...

Yes.
 
Back
Top