Tommi ๐Ÿคฏ ๐Ÿ”œ DWeb Camp16h ago

I am experiencing this with #OpenZFS

โžœ ~ sudo zpool status -x
pool: ughetto
state: DEGRADED
status: One or more devices could not be used because the label is missing or
invalid. Sufficient replicas exist for the pool to continue
functioning in a degraded state.
action: Replace the device using 'zpool replace'.
see: https://openzfs.github.io/openzfs-docs/msg/ZFS-8000-4J
scan: scrub in progress since Sat Jun 27 18:44:31 2026
141G / 141G scanned, 11.8G / 141G issued at 184M/s
0B repaired, 8.39% done, 00:12:00 to go
config:

NAME STATE READ WRITE CKSUM
ughetto DEGRADED 0 0 0
mirror-0 DEGRADED 0 0 0
653332104939013944 UNAVAIL 0 0 0 was /dev/sdb1
sdc ONLINE 0 0 0
cache
sda FAULTED 0 0 0 corrupted data

errors: No known data errors

This has already happened, but at a point where I didnโ€™t mind losing the data, so I destroyed the pool and I recreated it from scratch, with no errors. Now, I would like to try to repair the corrupted dataโ€ฆ Any tips? I would hate it if I have to throw away the hard disk, itโ€™s less than one year old and I have been using it only for a couple of monthsโ€ฆ Is replacing the disk my only option?

#ZFS #systemAdministration #help #sysAd #techSupport #dataLoss #storage #partition #hardDisk #HDD #Linux #filesystem #data #storage

Jana Panke4d ago

Leute, macht ein Backup eurer Daten, wenn ihr das hier lest. Wirklich. Jetzt sofort.

Habe heute morgen stundenlang versucht, den Arbeitslaptop zum Laufen zu bringen.

Ich mache regelmรครŸig Backups und bin trotzdem fast verzweifelt, weil ich einen Teil eben noch nicht im Backup hatte und wusste, wie viel Arbeit reingeflossen ist.

Rechner lรคuft รผbrigens wieder ๐Ÿคž๐Ÿป, Backup auch. Werde nun meine Backup-Zyklen anpassen und noch hรคufiger machen. ๐Ÿค“

#backup #datenverlust #dataloss

seanpm2001 ๐Ÿ‡บ๐Ÿ‡ฆ๏ธ๐Ÿ‡ฌ๐Ÿ‡ฑJun 15
I am having very poor luck with files lately.
Last night, GNOME Text Editor froze up, and due to the way it crashed, it was impossible to interact with anything, so I closed it. Typically, I have to either restart the computer, or kill it with the terminal to make it bring everything back up through draft recovery. I messed up, and just pressed the X this time. It asked me to confirm saving files, and I began to panic, as I knew I just messed up. So I tried to correct it, pressed save all, and the program immediately terminated without any prompts.
Unlike every past crash since 2025, November, the documents did not recover this time, and I had my first genuine file losses for 2026. I have no idea what I lost, but it was not a good loss, as those documents are now lost media. I was able to recreate 7 of them, but there were at least 13 others, and they seem to be permanently gone. The cache folder for GNOME Text Editor shows nothing but empty files, except for a few, for much older documents that I have already saved. I was wrapping up for the day.
I am hoping the ideas I have come back to me. It is extremely rare for my operations to result in data loss. This was a worst case scenario, and I was already having a really hard day, dealing with lots of depression, and physical pain (floating rib injury, due to a torn ligament, alongside other issues)
#gnome #gnometexteditor #crash #data #dataloss #lostmedia #saving #backups #loss #status
Karel 'Clock' K.Jun 10

EU๐Ÿ‡ช๐Ÿ‡บ: We gonna decouple from USA๐Ÿ‡บ๐Ÿ‡ธ MS Excel and start using open source Libreoffice Calc and Gnumeric.

Libreoffice Calc and Gnumeric: hold our beers๐Ÿบ:

(This is the same file opened in both. A reality check.)

@european_alternatives

#dataloss #untrustworhy #treacherous #opensource #unreliable #contempt #unusable #failure #eu #us #usa #excel #localc #libreoffice #libreofficecalc #gnumeric #spreadsheet #corruption #naive

Karel 'Clock' K.Jun 2
Mastodon cuts off right side of text without breaking it onto the next line. Also cuts bottom of text and writes hashtags over it instead of under it:
แžŸแŸ’แžšแŸ’แžšแŸ’แžšแŸ’แžšแŸ’แž”แŸ’แž†แŸ’แž†แŸ’แž†แŸ’แž†แŸ’แž†แŸ’แž†แŸ’แž†แŸ’แž†แŸ’แž†แŸ’แž†แŸ’แž†แŸ’แž†แŸ’แž†แŸ’แž†แŸ’แž†แŸ’แž†แŸ’แž†แŸ’แž†แŸ’แž†แŸ’แž†แŸ’แž†แŸ’แž†แŸ’แž†แŸ’แž†แŸ’แž†แŸ’แž†แŸ’แž†แŸ’แž†แŸ’แž†แŸ’แž†แŸ’แž†แŸ’แž†แŸ’แž†แŸ’แž†แŸ’แž†แŸ’แž†แŸ’แž†แŸ’แž†แŸ’แž†แŸ’แž†แŸ’แž”แŸ’แž”แŸ’แž”แŸ’แž”แŸ’แž”แŸ’แž”แŸ’แž†แŸ’แž†แŸ’แž†แŸ’แž†แŸ’แž†แŸ’แž†แŸ’แž†แŸ’แž†แŸ’แž†แŸ’แž†แŸ’แž†แŸ’แž†แŸ’แž†แŸ’แž†แŸ’แž”แŸ’แž”แŸ’แž”แŸ’แž”แŸ’แž”แŸ’แž”แŸ’แž”แŸ’แž”แŸ’แž”แŸ’แž”แŸ’แž”แŸ’แž”แŸ’แž”แŸ’แž”แŸ’แž”แŸ’แž”แŸ’แž”แŸ’แž”แŸ’แž†แŸ’แž†แŸ’แž†แŸ’แž†แŸ’แž†แŸ’แž”แŸ’แž”แŸ’แž”แŸ’แž”แŸ’แž”แŸ’แž†แŸ’แž†แŸ’แž†แŸ’แž†แŸ’แž†แŸ’แž”แŸ’แž”แŸ’แž”แŸ’แž”แŸ’แž”แŸ’แž”แŸ’แž”แŸ’แž”แŸ’แž”แŸ’แž†แŸ’แž†แŸ’แž†แŸ’แž†แŸ’แž†แŸ’แž†แŸ’แž†แŸ’แž†แŸ’แž†แŸ’แž†แŸ’แž†แŸ’แž†แŸ’แž†แŸ’แž†แŸ’แž†แŸ’แž†แŸ’แž†แŸ’แž†แŸ’แž†แŸ’แž†แŸ’แž†แŸ’แž†แŸ’แž”แŸ’แž”แŸ’แž”แŸ’แž”แŸ’แž”แŸ’แž”แŸ’แž”แŸ’แž”แŸ’แž”แŸ’แž”แŸ’แž”แŸ’แž”แŸ’แž”แŸ’แž”แŸ’แž”แŸ’แž”แŸ’แž”แŸ’แž”แŸ’แž”แŸ’แž”แŸ’แž”แŸ’แž”แŸ’แž”แŸ’แž”แŸ’แž”แŸ’แž”แŸ’แž”แŸ’แž”แŸ’แž”แŸ’แž”แŸ’แž”แŸ’แž”แŸ’แž”แŸ’แž”แŸ’แž”แŸ’แž”แŸ’แž”แŸ’แž”แŸ’แž”แŸ’แž†แŸ’แž†แŸ’แž†แŸ’แž†แŸ’แž†แŸ’แž†แŸ’แž”แŸ’แž”แŸ’แž”แŸ’แž”แŸ’แž”แŸ’แž”แŸ’แž”แŸ’แž”แŸ’แž”แŸ’แž”แŸ’แž”แŸ’แž”แŸ’แž”แŸ’แž”แŸ’แž”แŸ’แž”แŸ’แž”แŸ’แž”แŸ’แž”แŸ’แž”แŸ’แž”แŸ’แž”แŸ’แž†แŸ’แž†แŸ’แž†แŸ’แž†แŸ’แž”แŸ’แž”แŸ’แž”แŸ’แž†แŸ’แž†แŸ’แž†แŸ’แž”แŸ’แž”แŸ’แž”แŸ’แž”แŸ’แž”แŸ’แž”แŸ’แž”แŸ’แž”แŸ’แž”แŸ’แž”แŸ’แž”แŸ’แž”แŸ’แž”แŸ’แž”แŸ’แž”แŸ’แž”แŸ’แž”แŸ’แž”แŸ’แž”แŸ’แž”แŸ’แž”แŸ’แž”แžฟ
#mastodon #dataloss #bug #buggy #internationalization #khmer #cambodia #cambodian #khmerlanguage
jonathan w. y. gray ๐ŸจMay 27
what is the datafied web? how to study it? and reimagine it? we chat in Internet Histories journal โœจ๐Ÿฐ๐Ÿฆ”๐Ÿจ๐Ÿข๐Ÿฆ‰๐Ÿฟ๏ธ๐Ÿฆ™๐Ÿฆ†๐Ÿ’ฌ https://jonathangray.org/2026/05/18/datafied-web
with @nthylstrup Miglฤ— Bareikytฤ—, Carolin Gerlitz, @sebgiessmann @annehelmond Ian Milligan & Valรฉrie Schafer.
come for the datafied web - stay for the AI #slop #adtech #deepfakes #bots #leaks #trolls #bubbles #linkrot #fintech #osint #dataloss #softwaredecay #venturecapital #platformlabour #webarchives #diywebsites #algorithms #surveillancecapitalism #poeticcomputation & more ๐Ÿ˜‹
article on โ€œthe datafied webโ€ in Internet Histories

An article on โ€œthe datafied webโ€ that I co-authored has just been published in the Internet Histories journal.

Jonathan W. Y. Gray
Hacker NewsMay 8

My first in-prod corrupted hard drive problem

https://blog.pavementlink.ch/2026/05/07/my-first-corrupted-hard-drive-problem/

#HackerNews #Tech #DataLoss

My first corrupted hard drive problem

How I had to deal with a corrupted hard drive on a production server.

Richard's Blog
Hacker NewsMay 8

My first in-prod corrupted hard drive problem

https://blog.pavementlink.ch/2026/05/07/my-first-corrupted-hard-drive-problem/

#HackerNews #corruptedharddrive #dataloss #techstories #harddriverecovery #hackernews

My first corrupted hard drive problem

How I had to deal with a corrupted hard drive on a production server.

Richard's Blog
erikMay 2

IDrive.com lost all of my backup data. No user error. No support assistance.

https://thespecter.net/blog/technology/how-idrive-lost-all-of-my-backup-data/ #backup #backupServiceReview #backups #cloudBackup #cloudStorage #dataLoss #dataRecovery #idrive #idriveReview #IDriveCom #idriveComReview #lostData #selfHosting #selfhosting
ResearchBuzz: FirehoseMay 1

Mashable: New ransomware wipes every file larger than 128 KB. โ€œThe ransomware contains a critical coding flaw that permanently destroys any file larger than 128 kilobytes rather than encrypting it. That threshold is smaller than a typical email attachment, meaning virtually every file that would matter to a victim โ€” databases, backups, virtual machine disks, documents, spreadsheets โ€” is [โ€ฆ]

https://rbfirehose.com/2026/05/01/mashable-new-ransomware-wipes-every-file-larger-than-128-kb/
Mashable: New ransomware wipes every file larger than 128 KB

Mashable: New ransomware wipes every file larger than 128 KB. โ€œThe ransomware contains a critical coding flaw that permanently destroys any file larger than 128 kilobytes rather than encryptiโ€ฆ

ResearchBuzz: Firehose