I just found this in the cupboard.. with a note about 2005, so it is at least that old

Of course I decided to copy it using #ddrescue and my trusted external #cdrom drive

I had expected a lot of read issues, but one sector only failed and that was read on second pass.

Don't we expect cdrom 15+ years old to start failing?

#oldstuff

🧵 I now dismantled #LSC #MantraLite #DMX / #ArtNet console and took out the #raspberryPi 2.

While #ddRescue on #Linux is making a backup of the SSD card… looking at the boards and thinking of how to upgrade to the expensive “CPU board 3”. Which seems to be nothing but a RaspPi 3, I have one spare.

Turns out that this USB riser connector is soldered straight to the board of the Pi 2… (left in the image)

Uuuh. So it's like if you got this used piano and it's so great except for these 5 so and so strings and you try to tune it yourself. Either it works, or you have a non-usable used piano afterwards…

What would you guys do?

Re-create that little board somehow and solder wires to the Pi 3, so that I can at least go back to the old one if I fail?

Any RaspPi specialists out there? #fediHelp

EDIT: turns out the GPIO adapter is soldered, too.

So… basically spending ~300€ for the original part just to make sure I don't mess this up? Not so sure.

@azonenberg @taral I mean, it does make sense to DIY something 'lower level' and want or need that precision and lightweightness.

Personally I don't have that skillset and instead focus on a minimalist CLI/TUI-based #toybox+#musl / #Linux distro (aka. @OS1337 ), but that's simply due to different requirements and goals.

  • I want something reproducible, auditable, self-hosting capable and lightweight enough that it can run on an #i486SX and i.e. perform data recovery from 8" FDDs and QIC tapes using #ddrescue or reinstall a vintage setup by running #dd to restore a backup of it.

Granted shoving linux-6.6.6.-i486 and toybox-0.8.10 on a 3,5" 1440kB FDD and make it boot is a challenge on it's own.

But I can see why this is potentially seen as overkill and why one wants to do something bespoke with one's custom hardware architecture to leverage low-power ARM SoCs and the FPGAs flexibility for a specific application.

  • Like signal procession or avionics, where stuff needs to be blazing fast and errors are not acceptable!
Finally making progress on a gnarly data recovery project on someone else's damaged old hard drive where you can hear the metal crunching 😬
In spite of that, ddrescue and ddrescueview FTW. Amazed to get anything at all back👏
#DataRecovery #ddrescue

...And the tale goes on and on and on and on...

3 days, 5 passes, 67% rescued.
BashCoreX + ddrescue are still standing.
While GUIs weep, terminals work.

#BashCoreX #ForensicMode #IronMaiden #ddrescue #RAWdrive #LiveLinux #NoGUIJustResults

After a safe Ctrl+C on Saturday, I resumed the ddrescue recovery this Monday using the saved log and image. It's picking up exactly where it left off. 43% rescued so far, zero read errors on this pass. Hope lives. 🤞

#DataRecovery #ddrescue #LinuxTools #BashCore #Forensics

The adventures continue!

I run a number of computers at home, almost entirely GNU/Linux-based. As the hardware continues to age, data integrity had become more and more of a concern. I am particularly worried about sudden disk failures, and with a combination of ddrescue and timeshift I have been setting up whole-partition/whole-disk and incremental backups on critical systems.

I have also […]

https://steve.cooleysekula.net/blog/2025/07/06/adventures-in-microsd-and-raspberry-pi-disk-cloning/

My old 1TB Seagate external HDD turned RAW out of the blue after over a decade of loyal service...

I tried every well-known Windows recovery tool, with no success.

Now I'm giving it one last shot: using ddrescue on BashCore to create a raw image and extract whatever data I can on an Intenso 4TB drive.

Fingers crossed. 🧪💾

#DataRecovery #LinuxTools #ddrescue #RAWdrive #BashCore #DigitalForensics #Seagate #DisasterRecovery #Linux

@joahim
Same here recently
#handbrake (has a nice batch feature) and #K3b for the simple cases and #sh with #ddrescue and #ffmpeg et al. for the harder cases all on a #X61 on a #Debian distro

Problem ist behoben. Da es ein ganz schöner Ritt war, hier mal die Chronologie und ein paar Schlussfolgerungen:

Also, der #HomeAssistant bootete nicht mehr sauber. Das OS fuhr hoch, aber der Supervisor lief nicht, entsprechend die HA Container nicht.
Ursache war recht schnell ausgemacht: Die #SDKarte hatte eine Macke. Es waren am Ende ~50KB an kaputten Blöcken.

Das einzige Backup, das mir übrig blieb, war defekt. (unexpected end of file). Auch mit händisch repariertem Archiv konnte ich es nicht in eine neue Installation einspielen. (Ursache ist mir mittlerweile evtl. bekannt, dazu später mehr)

1. Schritt daher: Klonen der SD-Karte mit #ddrescue. (Im Vergleich zu dd macht ddrescue bei Fehlern weiter, und kann Blöcke auch x mal probieren. Damit kam ich nach mehreren Durchläufen auf nur