Data Hoarder

439 readers

57 active

1 user here now

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 (tm) ). Along the way we have sought out like-minded individuals to exchange strategies, war stories, and cautionary tales of failures.

founded 2 years ago

moderators

communick@selfhosted.forum

Checksum for original files came out unreadable (alien.top)

submitted 2 years ago by slaiyfer@alien.top [B] to c/datahoarder@selfhosted.forum

9 comments fedilink hide all child comments

Does that mean there was bitrot ready in the original file? Something else? How is the checksum even generated successfully if it's corrupted or undreadable in the first place.

Any way to fix?

you are viewing a single comment's thread
view the rest of the comments

[–] Ubermidget2@alien.top [B] 1 point 2 years ago

Why are you using third party tools for this?

An "unreadable" result sounds like a failure from HashCheck - What does your OS Native tools give you?

permalink

fedilink

source

parent

lemmy:	0.19.20
mlmym (mschae):	26.3.4