My USB Drive isn't recognized by TestDisk

Using TestDisk to repair the filesystem
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
Locked
Message
Author
Echuta
Posts: 3
Joined: 22 Nov 2020, 11:56

My USB Drive isn't recognized by TestDisk

#1 Post by Echuta »

Hello Team.

I have a 32Gb USB drive that I was trying to repurpose but when I connected it to my Windows 10 machine, I got the following error:
"The Request could not be performed because of an I/O device error."
I then decided to use TestDisk to see if I can fix it but, when the application asks me to select the drive, I can't seem to find it. I then had a look at the logs and identified that for some reason, TestDisk is having issues getting the size of the drive. Here you have the log dump (I have highlighted in bold the error I'm referring to):
Sun Nov 22 21:54:01 2020
Command line: TestDisk

TestDisk 7.2-WIP, Data Recovery Utility, Novembre 2020
Christophe GRENIER <grenier@cgsecurity.org>
https://www.cgsecurity.org
OS: Windows 8 (9200)
Compiler: GCC 9.3, Cygwin 3001.4
ext2fs lib: 1.45.3, ntfs lib: 10:0:0, reiserfs lib: none, ewf lib: 20140608, curses lib: ncurses 6.1
disk_get_size_win32 IOCTL_DISK_GET_LENGTH_INFO(/dev/sda)=8001563222016
disk_get_size_win32 IOCTL_DISK_GET_LENGTH_INFO(/dev/sdb)=8001563222016
disk_get_size_win32 IOCTL_DISK_GET_LENGTH_INFO(/dev/sdc)=1000204886016
disk_get_size_win32 IOCTL_DISK_GET_LENGTH_INFO(/dev/sdd)=5000981078016
disk_get_size_win32 IOCTL_DISK_GET_LENGTH_INFO(/dev/sde)=5000981078016
disk_get_size_win32 IOCTL_DISK_GET_LENGTH_INFO(/dev/sdf)=5000981078016
disk_get_size_win32 IOCTL_DISK_GET_LENGTH_INFO(/dev/sdg)=38482906972160
disk_get_size_win32 IOCTL_DISK_GET_LENGTH_INFO(\\.\PhysicalDrive0)=8001563222016
disk_get_size_win32 IOCTL_DISK_GET_LENGTH_INFO(\\.\PhysicalDrive1)=8001563222016
disk_get_size_win32 IOCTL_DISK_GET_LENGTH_INFO(\\.\PhysicalDrive2)=1000204886016
disk_get_size_win32 IOCTL_DISK_GET_LENGTH_INFO(\\.\PhysicalDrive3)=5000981078016
disk_get_size_win32 IOCTL_DISK_GET_LENGTH_INFO(\\.\PhysicalDrive4)=5000981078016
disk_get_size_win32 IOCTL_DISK_GET_LENGTH_INFO(\\.\PhysicalDrive5)=5000981078016
disk_get_size_win32 IOCTL_DISK_GET_LENGTH_INFO(\\.\PhysicalDrive6)=38482906972160
filewin32_getfilesize(\\.\PhysicalDrive7) GetFileSize err Incorrect function.

filewin32_setfilepointer(\\.\PhysicalDrive7) SetFilePointer err Incorrect function.

Warning: can't get size for \\.\PhysicalDrive7
disk_get_size_win32 IOCTL_DISK_GET_LENGTH_INFO(\\.\C:)=999526760448
disk_get_size_win32 IOCTL_DISK_GET_LENGTH_INFO(\\.\D:)=38482771685376
filewin32_getfilesize(\\.\E:) GetFileSize err Incorrect function.

filewin32_setfilepointer(\\.\E:) SetFilePointer err Incorrect function.

Warning: can't get size for \\.\E:
disk_get_size_win32 IOCTL_DISK_GET_LENGTH_INFO(\\.\F:)=0
Warning: can't get size for \\.\F:
Hard disk list
Disk /dev/sda - 8001 GB / 7452 GiB - CHS 972801 255 63, sector size=512 - WDC WD80EFZX-68UW8N0, S/N:R6GVHEKY, FW:83.H0A83
Disk /dev/sdb - 8001 GB / 7452 GiB - CHS 972801 255 63, sector size=512 - WDC WD80EFZX-68UW8N0, S/N:R6GULXVY, FW:83.H0A83
Disk /dev/sdc - 1000 GB / 931 GiB - CHS 121601 255 63, sector size=512 - CT1000P1SSD8, S/N:1921E2065609 _00000001., FW:P3CR010
Disk /dev/sdd - 5000 GB / 4657 GiB - CHS 608001 255 63, sector size=512 - WDC WD50EFRX-68MYMN1, S/N:WD-WX81D65ASC26, FW:82.00A82
Disk /dev/sde - 5000 GB / 4657 GiB - CHS 608001 255 63, sector size=512 - WDC WD50EFRX-68MYMN1, S/N:WD-WX81D65D93N4, FW:82.00A82
Disk /dev/sdf - 5000 GB / 4657 GiB - CHS 608001 255 63, sector size=512 - WDC WD50EFRX-68MYMN1, S/N:WD-WX81D6550162, FW:82.00A82
Disk /dev/sdg - 38 TB / 35 TiB - CHS 584826 255 63, sector size=4096 - Msft Storage Space, S/N:{826238af-2b42-4ee5-913c-2825282c3f31}, FW:0.1
Disk \\.\PhysicalDrive6 - 38 TB / 35 TiB - CHS 584826 255 63, sector size=4096 - Msft Storage Space, S/N:{826238af-2b42-4ee5-913c-2825282c3f31}, FW:0.1
Drive D: - 38 TB / 34 TiB - CHS 584824 255 63, sector size=4096 - Msft Storage Space, S/N:{826238af-2b42-4ee5-913c-2825282c3f31}, FW:0.1


TestDisk exited normally.
As you can see in the log, I'm using TestDisk 7.2. Windows Disk Management tool shows the drive mounted as Disk 7 (Unit F:) but I can't seem to do anything with it...

Any ideas as to what I can do to get this USB drive detected by TestDisk so that I can bring it back to life?

THANKS in advance!
Top
recuperation
Posts: 2729
Joined: 04 Jan 2019, 09:48
Location: Hannover, Deutschland (Germany, Allemagne)

Re: My USB Drive isn't recognized by TestDisk

#2 Post by recuperation »

Sounds like a hardware error, a case for a professional lab.

The first thing is always to check the SMART parameters.

Sarch for "smartctl" in this forum to get detailed instructions.

Here is an example:
viewtopic.php?p=31992#p31992
Use the -d parameter in case of problems with external drives.
Top
Echuta
Posts: 3
Joined: 22 Nov 2020, 11:56

Re: My USB Drive isn't recognized by TestDisk

#3 Post by Echuta »

Hello mate.

Thanks a lot for your response!

I tried what you mentioned but I get the following all the time:
smartctl 7.1 2019-12-30 r5022 [x86_64-w64-mingw32-w10-1909] (sf-7.1-1)
Copyright (C) 2002-19, Bruce Allen, Christian Franke, www.smartmontools.org

Smartctl open device: /dev/sdF failed: Invalid argument
I tired using all the available option with the -d command and had the same result with all of them... :(

I remember doing something with this USB drive and my Nintendo Wii where I had to modify the sector information of the drive... but I can't remember exactly what it was... Maybe that's what cause the drive to fail now? If that is the case, is it possible to restore it to it s original state?
Top
recuperation
Posts: 2729
Joined: 04 Jan 2019, 09:48
Location: Hannover, Deutschland (Germany, Allemagne)

Re: My USB Drive isn't recognized by TestDisk

#4 Post by recuperation »

Linux is case-sensitive.

use sdf instead of sdF please.
Top
Echuta
Posts: 3
Joined: 22 Nov 2020, 11:56

Re: My USB Drive isn't recognized by TestDisk

#5 Post by Echuta »

Such a rookie mistake!

Sorry for that...

It looks like we are getting somewhere now:

On my 1st try, I got this:
smartctl 7.1 2019-12-30 r5022 [x86_64-w64-mingw32-w10-1909] (sf-7.1-1)
Copyright (C) 2002-19, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Vendor: GENERIC
Product: USB Mass Storage
Revision: 1.00
Compliance: SPC-2
scsiModePageOffset: response length too short, resp_len=4 offset=4 bd_len=0
scsiModePageOffset: response length too short, resp_len=4 offset=4 bd_len=0
>> Terminate command early due to bad response to IEC mode page
A mandatory SMART command failed: exiting. To continue, add one or more '-T permissive' options.

Then I tried again with the " -T permissive" parameter and got this:
smartctl 7.1 2019-12-30 r5022 [x86_64-w64-mingw32-w10-1909] (sf-7.1-1)
Copyright (C) 2002-19, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Vendor: GENERIC
Product: USB Mass Storage
Revision: 1.00
Compliance: SPC-2
scsiModePageOffset: response length too short, resp_len=4 offset=4 bd_len=0
scsiModePageOffset: response length too short, resp_len=4 offset=4 bd_len=0
>> Terminate command early due to bad response to IEC mode page

=== START OF READ SMART DATA SECTION ===
Current Drive Temperature: 0 C
Drive Trip Temperature: 0 C

Error Counter logging not supported

scsiModePageOffset: response length too short, resp_len=4 offset=4 bd_len=0
Device does not support Self Test logging
Does this give you any more insights?
Top
Locked

Return to “Filesystem repair”