this post was submitted on 04 Feb 2026
6 points (100.0% liked)

datahoarder

10021 readers
177 users here now

Who are we?

We are digital librarians. Among us are represented the various reasons to keep data -- legal requirements, competitive requirements, uncertainty of permanence of cloud services, distaste for transmitting your data externally (e.g. government or corporate espionage), cultural and familial archivists, internet collapse preppers, and people who do it themselves so they're sure it's done right. Everyone has their reasons for curating the data they have decided to keep (either forever or For A Damn Long Time). Along the way we have sought out like-minded individuals to exchange strategies, war stories, and cautionary tales of failures.

We are one. We are legion. And we're trying really hard not to forget.

-- 5-4-3-2-1-bang from this thread

founded 6 years ago
MODERATORS
 

Sorry if this is not the place to ask I also tried on a different instance as well

I bought an adapter to retrieve old files from ancient hard drives and I didn't save the stuff from one I had looked at. Now though when I plug it in it will only read as an android file system? It has 2 disk images now, one is labeled Presario D: which shows up as an android backup or something but all folders are empty. The other is Local Disk E: and if I click it it literally just locks up my file explorer to the point I have to restart the PC.

Any thoughts or ideas?

I may have plugged it into an android phone at some point? Not sure though.

you are viewing a single comment's thread
view the rest of the comments
[–] clb92@feddit.dk 3 points 1 day ago

Does windows call it "Android file system"? Because as far as I know, Android usually uses EXT4, which is also what many Linux systems use by default. But it could also be corrupted filesystem or dying drive.

Try booting into a Linux USB. Linux in general can in some cases be more forgiving with failing hard drives, whereas Explorer in Windows sometimes just freezes until it gets a response from the drive.

If you can't see and mount the filesystem (preferably as read-only), take a look at tools like ddrescue (better than plain old dd with dying drives) and testdisk (to recover data from corrupted partitions). The "proper" procedure is to make a full disk image (or as much as it can read) and then try to recover the data from that disk image, so the potentially failing drive is used as little as possible.