![hard drive showing wrong capacity hard drive showing wrong capacity](https://www.diskpart.com/articles/images/cloned-hard-drive-shows-wrong-size-3125/create.jpg)
#HARD DRIVE SHOWING WRONG CAPACITY INSTALL#
making a bitstream copy (aka image file) of the failing driveįirst of all, install the ddrescue tool through the gddrescue package (the g is not a typo), which is used to make accurate copies of failing drives, cloning as much information as possible.stopping any write on the drive (you already stopped attempting to re-write the partition table with testdisk, which is good).The things you must absolutely do in this case are: ) However, I am sorry to inform you that your drive looks physically damaged or at least is reaching failure:ĭoes instantly give the same output if I run the command again without unplugging the drive Luckily, hard drives do not have feelings.
![hard drive showing wrong capacity hard drive showing wrong capacity](https://www.partitionwizard.com/images/uploads/articles/2019/09/wrong-hard-disk-free-space/wrong-hard-disk-free-space-1.png)
Thanks to everyone who gave it's thoughts and especially to Andrea Lazzarotto. I'm marking this question as solved, since the process given to solve the error would mostly work if the drive wasn't "dead". Did I do anything wrong? I just followed the instructions given. Does this means that there's no data being copied or that there's no sucessful data to recover?Īfter a long process and wait, with a lot of replugging the drive to keep the process going, looks like ddrescue finished, but the. the drive has a real capacity of 500GB, and some of the numbers shown are bigger than that.Īlso, the size of the copy.img file is 0 bytes.
![hard drive showing wrong capacity hard drive showing wrong capacity](https://www.minitool.com/images/uploads/articles/2018/08/hard-drive-only-shows-half-capacity/hard-drive-only-shows-half-capacity-11.jpg)
I'm not sure if the values presented in the rescued, ipos, and opos are wrong or not, so I ask someone to tell me if should be like this. Second, the command output can be seen here: # Command line: ddrescue /dev/sdc /media/sidious/Supply/dotk/bkpHD/copy.img /media/sidious/Supply/dotk/bkpHD/status.log One thing to notice, the grep command after the first output taking around 20 seconds, does instantly give the same output if I run the command again without unplugging the drive.ĭdrescue has been running for some hours by now, but I'm finding some points weird in the behavior of the outputs, as follow:įirst, a sample of some lines of the status.log file: # Rescue Logfile. The sudo grep -abiro "NTFS " /dev/sdb command output gave me, after some time of running: grep: /dev/sdb: Input/output errorĬorrecting the print, looks like the sdb unmounted before I did the parted command, the image above is the real output. The command parted -l /dev/sdb output goes as below: Should I try to tweak the number so they show the true disk capacity or there's a recovery option? The drive doesn't look psychically damaged. WD Lifeguard Diagnostic isn't proofing useful either, since it doesn't show the drive on it's table. R-Studio demo was useless in my test, if I try to open it with the drive pluged the program just doesn't work/doesn't respond. I hope someone can help, and I know that a lot of people have this problem too. It's very important for me to recover that data because it evolves college and master's degree material, and my last backup is from 1 month ago(I can't do it everyday due the space avaliable in my backup External USB Drive). If I use smartmontools or gsmartcontrol to see the hard drive status I get this as result: I can confirm that the drive isn't dead because the LEDs light up and I can feel the disk running. Actually the amount of disk space ocuppied in my HD is 110GB. One thing to note is that the disk space ocupied in the list by sda(my hard drive) is the disk space occupied by the hard drive I want to recover. You can see my personal hard drive(sda) and the drive I want to recover(sdb) both should list as 500GiB. The output of testdisk in recognizing the drive.
#HARD DRIVE SHOWING WRONG CAPACITY WINDOWS#
I tried to see the drive in the Windows Disk Manager, but it takes a really long time to show up, and still showing as raw, with no info about its size. Trying to mount the drive for read only to an attempt to recover data isn't working either, I get the message that the "NTFS is inconsistent". The hard disk is now sowing in testdisk as a 2199GB drive, and if I plug it directly into the SATA port, as recommended in the testdisk FAQ, even my BIOS can't recognize it properly, and I can't run testdisk again since it doesn't recognize the drive with it's normal size (that's 500GB). So, now I think I got an even bigger problem. I did all good, did the quick search, the deeper seach, and then, after confirming that my files had been found by testdisk, I wrote the partition table. I'm trying to recover the data of a damaged hard drive using testdisk.