What you mean by "wrong tool"? You mean the tool used to check the drive?Wrong tool?The superblock could not be read or does not describe a valid ext2/ext3/ext4
filesystem.I don't have recent Debian specific advice but have used hex editors that can force mount -ro to read the contents. When you are familiar with the structure it is possible to cut and paste your way to recovery. It's tricky, tedious, and possible. I used to descramble data loggers that would truncate on power loss and it happened on a regular basis, so I got familiar.$ sudo dmesg
[30369.874077] FAT-fs (sdb1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck
There is a thread here a few years old that I did detail this some. A few scoffed at the ability for a hex editor to open a multi GB disk in raw mode. It's what they do, they chunk in piece by piece and will scroll through just fine. Use a sector selection dialog to enter numbers, often +1. Don't try to mouse select highlight a multi-meg file, that's very clumsy. This is the last option after other methods have done what they can. In all cases, offload as much as possible, then reformat the device and reload the data.
That thread you mention, do you remember the title or part of it or something that I can use to search the forum?
Statistics: Posted by PsySc0rpi0n — 2024-01-31 21:05