The Drive failed on a Fujitsu W380 with old BIOS.
Window 10 Prof reported something like: filesystems can not be solved in Dutch
First effort with TestDisk resulted in Harddisk too small, check jumpers
According the site of Intenso FAT32 was original.
tried to recreate FAT Boot sector
I have made a Dump
Lots of zero's
Tried too write the partial table:
write error: Can't write new FAT boot sector.
according Windows and CrystalDiskInfoPortable the HardDisk seems Okay
I have learned a lot trying this in these Corona times
Any suggestion will be welcomed
regards
Hans
trying to recover filesystem Intenso External USB 3T drive,
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
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
Re: trying to recover filesystem Intenso External USB 3T drive,
additional info: direct after neatly quiting TestDisk through its mainmenu my PC gave me the blue screen.
Stopcode: KMODE_EXCEPTION_NOT_HANDLED
problems with Ntfs.sys
bad disk was still connected
does this give an extra clue?
hans
Stopcode: KMODE_EXCEPTION_NOT_HANDLED
problems with Ntfs.sys
bad disk was still connected
does this give an extra clue?
hans
- cgrenier
- Site Admin
- Posts: 5432
- Joined: 18 Feb 2012, 15:08
- Location: Le Perreux Sur Marne, France
- Contact:
Re: trying to recover filesystem Intenso External USB 3T drive,
If you run PhotoRec, does it recover some files ?
Re: trying to recover filesystem Intenso External USB 3T drive,
Thanks for the response.
yes, have tried to use photorec_win for canon raw pictures (cr*) :no files recovered.
I hate the fact that EaseUS data Recovery wizard can find and show all files.
However the recovery button is greyed out untill i have paid, so the files are there.
The Windows command chkdisk /f /r does not repair the drive
Now studying the layout of FAT32.
greetings
hans
yes, have tried to use photorec_win for canon raw pictures (cr*) :no files recovered.
I hate the fact that EaseUS data Recovery wizard can find and show all files.
However the recovery button is greyed out untill i have paid, so the files are there.
The Windows command chkdisk /f /r does not repair the drive
Now studying the layout of FAT32.
greetings
hans
Re: trying to recover filesystem Intenso External USB 3T drive,
I think the BIOS parameter block is messed up.
Re: trying to recover filesystem Intenso External USB 3T drive,
Still struggling, I have made an a raw image using FTK.
When I tried to mount the raw image, FTK asked to format the chosen virtual disk
Then I exported the segmented dd4.001, 002, .... 1908 files to a single raw file still using FTK.
As bonus I got some info of the leftover file structure after MicroSoft's failed chkdsk action:
Filename Full Path Size (bytes) Created Modified Accessed Is Deleted
[root] Partition 1\NONAME [FAT32]\[root]\ 262144 no
VBR Partition 1\NONAME [FAT32]\VBR 4096 no
reserved sectors Partition 1\NONAME [FAT32]\reserved sectors 126976 no
[unallocated space] Partition 1\NONAME [FAT32]\[unallocated space]\ 0 no
file system slack Partition 1\NONAME [FAT32]\file system slack 188416 no
FAT1 Partition 1\NONAME [FAT32]\FAT1 45780992 no
FAT2 Partition 1\NONAME [FAT32]\FAT2 45780992 no
{ Partition 1\NONAME [FAT32]\[root]\{ 4194304 1980-Jan-20 00:01:32 1980-Jan-23 00:02:04 no
0 Partition 1\NONAME [FAT32]\[root]\0 5505024 1980-Jan-13 00:01:38 1980-Feb-02 00:02:06 no
2 Partition 1\NONAME [FAT32]\[root]\2 0 N/A N/A no
System Volume Information Partition 1\NONAME [FAT32]\[root]\System Volume Information\ 262144 2021-Mar-22 12:53:31.300000 2021-Mar-22 12:53:32 no
FOUND.000 Partition 1\NONAME [FAT32]\[root]\FOUND.000\ 524288 2021-Mar-22 14:13:10 2021-Mar-22 14:13:10 no
more in:
https://www.dropbox.com/s/ueyuea9j6bogj ... 1.csv?dl=0
Can I make use of this info?
Is it possible to change the raw image file so it wil work again?
In the mean time I will Study the TestDisk documentation for more clues
greetings
hans
When I tried to mount the raw image, FTK asked to format the chosen virtual disk
Then I exported the segmented dd4.001, 002, .... 1908 files to a single raw file still using FTK.
As bonus I got some info of the leftover file structure after MicroSoft's failed chkdsk action:
Filename Full Path Size (bytes) Created Modified Accessed Is Deleted
[root] Partition 1\NONAME [FAT32]\[root]\ 262144 no
VBR Partition 1\NONAME [FAT32]\VBR 4096 no
reserved sectors Partition 1\NONAME [FAT32]\reserved sectors 126976 no
[unallocated space] Partition 1\NONAME [FAT32]\[unallocated space]\ 0 no
file system slack Partition 1\NONAME [FAT32]\file system slack 188416 no
FAT1 Partition 1\NONAME [FAT32]\FAT1 45780992 no
FAT2 Partition 1\NONAME [FAT32]\FAT2 45780992 no
{ Partition 1\NONAME [FAT32]\[root]\{ 4194304 1980-Jan-20 00:01:32 1980-Jan-23 00:02:04 no
0 Partition 1\NONAME [FAT32]\[root]\0 5505024 1980-Jan-13 00:01:38 1980-Feb-02 00:02:06 no
2 Partition 1\NONAME [FAT32]\[root]\2 0 N/A N/A no
System Volume Information Partition 1\NONAME [FAT32]\[root]\System Volume Information\ 262144 2021-Mar-22 12:53:31.300000 2021-Mar-22 12:53:32 no
FOUND.000 Partition 1\NONAME [FAT32]\[root]\FOUND.000\ 524288 2021-Mar-22 14:13:10 2021-Mar-22 14:13:10 no
more in:
https://www.dropbox.com/s/ueyuea9j6bogj ... 1.csv?dl=0
Can I make use of this info?
Is it possible to change the raw image file so it wil work again?
In the mean time I will Study the TestDisk documentation for more clues
greetings
hans