Harddisk seems too small

How to use TestDisk to recover lost partition
Forum rules
When asking for technical support:
- Search for posts on the same topic before posting a new question.
- Give clear, specific information in the title of your post.
- Include as many details as you can, MOST POSTS WILL GET ONLY ONE OR TWO ANSWERS.
- Post a follow up with a "Thank you" or "This worked!"
- When you learn something, use that knowledge to HELP ANOTHER USER LATER.
Before posting, please read https://www.cgsecurity.org/testdisk.pdf
Message
Author
pulledporkpoutine
Posts: 7
Joined: 16 Feb 2021, 23:27

Harddisk seems too small

#1 Post by pulledporkpoutine »

Hello, I have an old external Iomega 1TB HDD that I have been attempting to recover data from on Windows 10. Years ago I split it into three partitions: two ~450GB drives (E and F), and one ~10GB drive G. One of the large drives, E, has been problematic. When I first plugged in the drive I was able to see the files present, but after trying to copy the whole drive and running into an error I haven't been able to see them since.

If I try to access E: in Windows, I get a "not accessible... access denied" message even though I have made sure there are no user control problems (opened as admin, set to full control, etc).

I have run chkdsk, used recuva, tried photorec, to no avail. I have run testdisk analyse and deep search. The files don't show up after I use Boot > Rebuild BS > List.

At first there were boot sector errors but now there don't appear to be any. However, I got this message: https://imgur.com/XwySybm -- The harddisk seems too small!

Any suggestions?

Partition structure: https://imgur.com/tU9wV7f

Boot sector: https://imgur.com/KVSAfHa
recuperation
Posts: 3036
Joined: 04 Jan 2019, 09:48
Location: Hannover, Deutschland (Germany, Allemagne)

Re: Harddisk seems too small

#2 Post by recuperation »

Use smartmontools to extract a health log file of your drive. Search the forum how to do that.

Code: Select all

Post the content of your log file within code markers
.
pulledporkpoutine
Posts: 7
Joined: 16 Feb 2021, 23:27

Re: Harddisk seems too small

#3 Post by pulledporkpoutine »

Short test results:

Code: Select all

=== START OF READ SMART DATA SECTION ===
SMART Self-test log structure revision number 1
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Short offline       Completed: read failure       90%     42796         983216191

Will post long test results.
pulledporkpoutine
Posts: 7
Joined: 16 Feb 2021, 23:27

Re: Harddisk seems too small

#4 Post by pulledporkpoutine »

Same results from long test as short test, it seems.
recuperation
Posts: 3036
Joined: 04 Jan 2019, 09:48
Location: Hannover, Deutschland (Germany, Allemagne)

Re: Harddisk seems too small

#5 Post by recuperation »

Do not run self-tests. Look here:

viewtopic.php?p=31986#p31986
pulledporkpoutine
Posts: 7
Joined: 16 Feb 2021, 23:27

Re: Harddisk seems too small

#6 Post by pulledporkpoutine »

I'm sorry, I haven't been able to get anything other than this.

Code: Select all

smartctl 7.2 2020-12-30 r5155 [x86_64-w64-mingw32-w10-1909] (sf-7.2-1)
Copyright (C) 2002-20, Bruce Allen, Christian Franke, www.smartmontools.org

/dev/sdE: Unknown device type ',sat'
=======> VALID ARGUMENTS ARE: ata, scsi[+TYPE], nvme[,NSID], sat[,auto][,N][+TYPE], usbcypress[,X], usbjmicron[,p][,x][,N], usbprolific, usbsunplus, sntjmicron[,NSID], sntrealtek, intelliprop,N[+TYPE], jmb39x[-q],N[,sLBA][,force][+TYPE], jms56x,N[,sLBA][,force][+TYPE], aacraid,H,L,ID, areca,N[/E], auto, test <=======

Use smartctl -h to get a usage summary
I tried smartctl -a /dev/sdE > C:\mylog.txt and smartctl -a -d /dev/sdE > C:\mylog.txt, including -d,sat[,auto] and so on. I don't know which of the -d commands listed on the following link I should use: https://www.smartmontools.org/wiki/USB
recuperation
Posts: 3036
Joined: 04 Jan 2019, 09:48
Location: Hannover, Deutschland (Germany, Allemagne)

Re: Harddisk seems too small

#7 Post by recuperation »

Write sde instead of sdE.

The bix "X" in my example was only supposed to be a visible placeholder symbol.
pulledporkpoutine
Posts: 7
Joined: 16 Feb 2021, 23:27

Re: Harddisk seems too small

#8 Post by pulledporkpoutine »

That doesn't seem to change the output. How can I figure out which device type to use for the -d command?

Code: Select all

smartctl 7.2 2020-12-30 r5155 [x86_64-w64-mingw32-w10-1909] (sf-7.2-1)
Copyright (C) 2002-20, Bruce Allen, Christian Franke, www.smartmontools.org

/dev/sde: Unknown device type ',sat'
=======> VALID ARGUMENTS ARE: ata, scsi[+TYPE], nvme[,NSID], sat[,auto][,N][+TYPE], usbcypress[,X], usbjmicron[,p][,x][,N], usbprolific, usbsunplus, sntjmicron[,NSID], sntrealtek, intelliprop,N[+TYPE], jmb39x[-q],N[,sLBA][,force][+TYPE], jms56x,N[,sLBA][,force][+TYPE], aacraid,H,L,ID, areca,N[/E], auto, test <=======

Use smartctl -h to get a usage summary
recuperation
Posts: 3036
Joined: 04 Jan 2019, 09:48
Location: Hannover, Deutschland (Germany, Allemagne)

Re: Harddisk seems too small

#9 Post by recuperation »

pulledporkpoutine wrote: 03 Mar 2021, 21:39 That doesn't seem to change the output. How can I figure out which device type to use for the -d command?
Google for how to find the usb device id.
Post your findings. You can then compare it to the variations of the "-"-parameter.
pulledporkpoutine
Posts: 7
Joined: 16 Feb 2021, 23:27

Re: Harddisk seems too small

#10 Post by pulledporkpoutine »

This is what is listed under the Device Instance Path:

Code: Select all

SWD\WPDBUSENUM\{0F0048B3-59C6-11EB-ACEB-10C37BDCA9FB}#0000000000007E00
Hardware ids:

Code: Select all

USB\VID_059B&PID_0370&REV_010?

Code: Select all

USB\VID_059B&PID_0370
Locked