|
| If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|||||||
|
|
|
Thread Tools | Display Modes |
|
#1
December 8th 03, 06:48 PM
|
|||
|
|||
Help with problem diagnosis and data recovery
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. 
|
|
#2
December 8th 03, 07:54 PM
|
|||
|
|||
|
No-one wrote in message news 
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 !!) 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. Exactly what does it say about the failure ? Any clues as to the cause - electronics? 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 ? You'd need to spell out how it fails the full test. (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)
|
|
#3
December 8th 03, 10:21 PM
|
|||
|
|||
|
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/%7Esvolaf/utilities.htm "No-one" wrote in message news 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)
|
|
#4
December 8th 03, 11:20 PM
|
|||
|
|||
|
On Tue, 9 Dec 2003 06:54:52 +1100, "Rod Speed"
wrote: 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. Exactly what does it say about the failure ? 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
|
|
#5
December 9th 03, 08:56 AM
|
|||
|
|||
|
On Mon, 08 Dec 2003 18:48:48 +0000, No-one
wrote: 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 a 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 a 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 Signatu 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
|
|
#6
December 9th 03, 10:14 AM
|
|||
|
|||
|
On Tue, 09 Dec 2003 08:56:13 +0000, No-one
wrote: Findpart reports: Findpart, version 4.37 - for Windows 95/98/ME/NT/2000/XP. Copyright Svend Olaf Mikkelsen, 2003. 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 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 -- Svend Olaf http://www.partitionsupport.com/utilities.htm
|
|
#7
December 9th 03, 10:39 AM
|
|||
|
|||
|
|
|
#8
December 9th 03, 01:08 PM
|
|||
|
|||
|
|
|
#9
December 9th 03, 01:18 PM
|
|||
|
|||
|
On Tue, 09 Dec 2003 13:08:14 +0000, No-one
wrote: On Tue, 09 Dec 2003 10:14:39 GMT, (Svend Olaf Mikkelsen) wrote: Further examination could be done. This could be from boot to a DOS floppy using the Findbad program from my page: 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: 5000 5099 0 1 81915435 10 Current cylinder: 5100 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. -- Svend Olaf
|
|
#10
December 9th 03, 01:25 PM
|
|||
|
|||
|
|
|
| Thread Tools | |
| Display Modes | |
|
|
Similar Threads
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| [ICSEng'05] Final CFP - due date March 10, 2005 | avinash | General | 0 | March 6th 05 12:11 AM |
| Reading from FPGA Issue | Isaac | General Hardware | 4 | September 30th 03 02:01 PM |
Linear Mode
