Buy Western Digital WD Blue Hard Drive WD10EZEX 1TB 7200 RPM 64MB Cache SATA 6.0Gb/s 3.5' Internal Hard Drive Bare Drive with fast shipping and top-rated customer service. AMD FX-8350 Black Edition Vishera 8-Core 4.0 GHz (4.2 GHz Turbo) Socket AM3+ 125W FD8350FRHKBOX Desktop Processor. With certified Class 10 ISO 4 Cleanroom technology and an extensive track record of success, Secure Data Recovery Services offers professional hard drive repair. WD Data Recovery. Western Digital. This page showcases our options for Western Digital hard drive owners. We maintain a partnership with Western Digital.

Friends please tell me which data? Software is the best in all? Anyone know of a good data? Program.preferably free?

Physically broken hard drive. Is there any way of recovering data? On a broken external hard drive? Are my documents gone after running what was supposed to be the non destructive hp recovery? Lenovo one key recovery? I had to do a recovery? On my computer because it crashed, is there any way to recover my data?

Unable to copy 2nd disc of recovery? Please help me? Which is the best and absolutely free dvd recovery? How can i recover data?

From hard disk make samsung - sp4002h, 40 gb, which is not detected by system? How to recover the data? From hidden drive?

Kenrivers, thanks for your reply. It does not show up as unallocated. Nothing shows up at all.

It shows the maximum disk size is 1.63TB. Fzabkar, thank you for your answer I have 64bit Windows 7 installed on my machine and have updated everything I can find to update! 144arana: I have read both those articles before positing and neither fixed my problem. Both those problems refer to having windows boot from the hard drive.

I just want to use it as a storage drive. Both also say it is there but unallocated. Mine doesn't show up at all. Thanks for your help! The specification sheet for WD's 4TB drives states that. User sectors per drive (WD4000FYYZ) = 7,814,037,168 Converting to hexadecimal.

7 814 037 168 = 0x1D1C0BEB0 sectors After stripping off the 33rd bit we have. 0xD1C0BEB0 = 3 519 069 872 sectors Converting this into a capacity in TiB.

0xD1C0BEB0 x 512 bytes = 1.639 terabytes Therefore it does appear that the 33rd bit is being ignored. Can you post the Identify Device information that is reported by CrystalDiskInfo? This will confirm that the drive is reporting its full capacity, and that it hasn't been truncated by a HPA. CrystalDiskInfo has a Text Copy feature. First go to Edit ->Copy Option and select Identify Device.

Then go to Edit ->Copy. This will copy the disk information to the clipboard. Then open up NotePad or whichever word processor ships with your version of Windows, and choose Edit ->Paste (or Ctrl-V) to input the clipboard data.

@wwasion, I suspect that you have created a time bomb. When you connect via eSATA, the SATA driver talks directly to the HDD. It appears that this driver is not affected by a 32-bit LBA limitation (it is probably 48-bit LBA aware), in which case it is able to see the full capacity of the drive. However, when you connect via USB, the OS uses a USB mass storage driver which communicates with the firmware on the USB-SATA bridge PCB inside the enclosure rather than with the HDD directly. It appears that the bridge firmware has a 32-bit LBA limitation. The end result is that the drive will appear to work fine up until the time you try to write data beyong the 2TiB point. Download Game Naruto Ultimate Ninja 5 For Pc Full Version on this page. When this happens, the LBAs wrap around to sector 0, trashing your file system.

@wwasion, I suspect that you have created a time bomb. When you connect via eSATA, the SATA driver talks directly to the HDD.

It appears that this driver is not affected by a 32-bit LBA limitation (it is probably 48-bit LBA aware), in which case it is able to see the full capacity of the drive. However, when you connect via USB, the OS uses a USB mass storage driver which communicates with the firmware on the USB-SATA bridge PCB inside the enclosure rather than with the HDD directly. It appears that the bridge firmware has a 32-bit LBA limitation.

The end result is that the drive will appear to work fine up until the time you try to write data beyong the 2TiB point. When this happens, the LBAs wrap around to sector 0, trashing your file system. USB-ATA bridges are absolute trash.

Some are better than others, but there are a huge number of limitations present in USB attached HDDs that are often glossed over. ESATA was designed for this! Try to see if this helps Thanks, but I've read those two already and neither are relevant.

My machine is brand new with very recent parts. The second one doesn't have a solution either. As an update, WD replied to me and asked that I write zeroes to the disk, which I have done and still have the same result. I read somewhere about deleting the registry entries for the drive letters that I allocated at the first initialisation, could this fix the issue?

I don't know anything about registry entries, so am a bit hesitant to mess with them. Try to see if this helps Thanks, but I've read those two already and neither are relevant.

My machine is brand new with very recent parts. The second one doesn't have a solution either. As an update, WD replied to me and asked that I write zeroes to the disk, which I have done and still have the same result.

I read somewhere about deleting the registry entries for the drive letters that I allocated at the first initialisation, could this fix the issue? I don't know anything about registry entries, so am a bit hesitant to mess with them. Titanium Backup Pro Ключ here.