Western Digital drive, recognized but not accesible Topic is solved

Using TestDisk to repair the filesystem
Locked
Message
Author
Firedawn
Posts: 2
Joined: 17 May 2014, 19:58

Western Digital drive, recognized but not accesible

#1 Post by Firedawn » 17 May 2014, 22:53

So, this is the second time this HDD has stopped working (it's out of warranty unfortunately).
It's a 500 GB Caviar Blue (WD500AAKS)

I can see my files and partition with testdisk, but it's not accesible through Windows (the disk management says the partition is RAW).
A weird thing I noticed, is that my OS boot time (Windows 7) is much longer if this drive is plugged in.

So, I'm listening to suggestions. Desperate measures are welcome too, since I've backed up everything important.

This is testdisk's log:

Code: Select all


Sat May 17 18:43:57 2014
Command line: TestDisk

TestDisk 7.0-WIP, Data Recovery Utility, April 2014
Christophe GRENIER <grenier@cgsecurity.org>
http://www.cgsecurity.org
OS: Windows 7 (7601) SP1
Compiler: GCC 4.8, MinGW 3.11
Compilation date: May 12 2014 19:44:22
ext2fs lib: none, ntfs lib: 10:0:0, reiserfs lib: none, ewf lib: 20120504
disk_get_size_win32 IOCTL_DISK_GET_LENGTH_INFO(\\.\PhysicalDrive0)=2000398934016
disk_get_size_win32 IOCTL_DISK_GET_LENGTH_INFO(\\.\PhysicalDrive1)=40018599936
disk_get_size_win32 IOCTL_DISK_GET_LENGTH_INFO(\\.\PhysicalDrive2)=1000204886016
disk_get_size_win32 IOCTL_DISK_GET_LENGTH_INFO(\\.\PhysicalDrive3)=500107862016
disk_get_size_win32 IOCTL_DISK_GET_LENGTH_INFO(\\.\C:)=39910899712
disk_get_size_win32 IOCTL_DISK_GET_LENGTH_INFO(\\.\D:)=1000202241024
disk_get_size_win32 IOCTL_DISK_GET_LENGTH_INFO(\\.\E:)=500105217024
filewin32_getfilesize(\\.\F:) GetFileSize err Función incorrecta.


filewin32_setfilepointer(\\.\F:) SetFilePointer err Función incorrecta.


Warning: can't get size for \\.\F:
disk_get_size_win32 IOCTL_DISK_GET_LENGTH_INFO(\\.\G:)=2000263577600
Hard disk list
Disk \\.\PhysicalDrive0 - 2000 GB / 1863 GiB - CHS 243201 255 63, sector size=512
Disk \\.\PhysicalDrive1 - 40 GB / 37 GiB - CHS 4865 255 63, sector size=512
Disk \\.\PhysicalDrive2 - 1000 GB / 931 GiB - CHS 121601 255 63, sector size=512
Disk \\.\PhysicalDrive3 - 500 GB / 465 GiB - CHS 60801 255 63, sector size=512
Drive C: - 39 GB / 37 GiB - CHS 4852 255 63, sector size=512
Drive D: - 1000 GB / 931 GiB - CHS 121600 255 63, sector size=512
Drive E: - 500 GB / 465 GiB - CHS 60800 255 63, sector size=512
Drive G: - 2000 GB / 1862 GiB - CHS 243184 255 63, sector size=512

Partition table type (auto): Intel
Disk \\.\PhysicalDrive3 - 500 GB / 465 GiB
Partition table type: Intel

Analyse Disk \\.\PhysicalDrive3 - 500 GB / 465 GiB - CHS 60801 255 63
Geometry from i386 MBR: head=255 sector=63
NTFS at 0/1/1
get_geometry_from_list_part_aux head=255 nbr=2
get_geometry_from_list_part_aux head=8 nbr=1
get_geometry_from_list_part_aux head=16 nbr=1
get_geometry_from_list_part_aux head=32 nbr=1
get_geometry_from_list_part_aux head=64 nbr=1
get_geometry_from_list_part_aux head=128 nbr=1
get_geometry_from_list_part_aux head=240 nbr=1
get_geometry_from_list_part_aux head=255 nbr=2
Current partition structure:
 1 * HPFS - NTFS              0   1  1 60800 254 63  976768002

search_part()
Disk \\.\PhysicalDrive3 - 500 GB / 465 GiB - CHS 60801 255 63
file_win32_pread(100,16,buffer,2080(0/33/2)) read err: read after end of file
file_win32_pread(100,1,buffer,2080(0/33/2)) read err: read after end of file
file_win32_pread(100,2,buffer,2082(0/33/4)) read err: read after end of file
NTFS at 0/1/1
filesystem size           976768002
sectors_per_cluster       8
mft_lcn                   786432
mftmirr_lcn               16
clusters_per_mft_record   -10
clusters_per_index_record 1
     HPFS - NTFS              0   1  1 60800 254 63  976768002
     NTFS, blocksize=4096, 500 GB / 465 GiB
get_geometry_from_list_part_aux head=255 nbr=2
get_geometry_from_list_part_aux head=8 nbr=1
get_geometry_from_list_part_aux head=16 nbr=1
get_geometry_from_list_part_aux head=32 nbr=1
get_geometry_from_list_part_aux head=64 nbr=1
get_geometry_from_list_part_aux head=128 nbr=1
get_geometry_from_list_part_aux head=240 nbr=1
get_geometry_from_list_part_aux head=255 nbr=2

Results
   * HPFS - NTFS              0   1  1 60800 254 63  976768002
     NTFS, blocksize=4096, 500 GB / 465 GiB

interface_write()
 1 * HPFS - NTFS              0   1  1 60800 254 63  976768002
simulate write!

write_mbr_i386: starting...
write_all_log_i386: starting...
No extended partition

Interface Advanced
Geometry from i386 MBR: head=255 sector=63
NTFS at 0/1/1
get_geometry_from_list_part_aux head=255 nbr=2
get_geometry_from_list_part_aux head=8 nbr=1
get_geometry_from_list_part_aux head=16 nbr=1
get_geometry_from_list_part_aux head=32 nbr=1
get_geometry_from_list_part_aux head=64 nbr=1
get_geometry_from_list_part_aux head=128 nbr=1
get_geometry_from_list_part_aux head=240 nbr=1
get_geometry_from_list_part_aux head=255 nbr=2
 1 * HPFS - NTFS              0   1  1 60800 254 63  976768002
     NTFS, blocksize=4096, 500 GB / 465 GiB

TestDisk exited normally.

Sponsored links

User avatar
cgrenier
Site Admin
Posts: 3458
Joined: 18 Feb 2012, 15:08
Location: Le Perreux Sur Marne, France
Contact:

Re: Western Digital drive, recognized but not accesible

#2 Post by cgrenier » 28 May 2014, 07:35

Your disk contains bad sectors (read error listed in the log file), it's why the OS boot is longer when this disk is connected.
You need to clone this disk using gnu ddrescue to a new empty disk as described in
http://www.cgsecurity.org/wiki/Damaged_Hard_Disk
Once the copy is done, remove the original disk and try to access your data on the clone. Use TestDisk if necessary. It has been able to find your NTFS partition, so it should work.

Firedawn
Posts: 2
Joined: 17 May 2014, 19:58

Re: Western Digital drive, recognized but not accesible

#3 Post by Firedawn » 28 May 2014, 17:25

Thanks. I had backed up important stuff already with testdisk.

Is the Windows built in software good for attempting to fix bad sectors? Should I just format it? I want to keep using this disk, even if it is unreliable.

User avatar
cgrenier
Site Admin
Posts: 3458
Joined: 18 Feb 2012, 15:08
Location: Le Perreux Sur Marne, France
Contact:

Re: Western Digital drive, recognized but not accesible  Topic is solved

#4 Post by cgrenier » 31 May 2014, 08:13

You really should not continue to use a disk with bad sectors.
If you don't care about the futur data, activate the SMART monitoring for this disk (see BIOS settings and download a software to monitore the SMART status), use "chkdsk /r" to scan the disk

Locked

Who is online

Users browsing this forum: No registered users and 1 guest