I just wanted to confirm from our meeting just now, did you want me to (some crazy shit that could cause problems)?

  • 8 Posts
  • 58 Comments
Joined 6 months ago
cake
Cake day: January 9th, 2024

help-circle
  • mozz@mbin.grits.devtoSelfhosted@lemmy.worldHDD data recovery
    link
    fedilink
    arrow-up
    16
    arrow-down
    1
    ·
    2 days ago

    You’re going to think I am joking but I am not. Multiple people have sworn to me that this works for a common failure mode of HDD drives and I’ve literally never heard someone say they tried it and it failed. I’ve never tried it. Buyer beware. Don’t blame me if you fuck up your drive / your computer it’s connected to / anything else even worse by doing this:

    1. Stick it in the freezer for a short while.
    2. Take it out.
    3. Boot it up.
    4. If it works, get all the data off it as quick as you can.






  • Tor’s obfs4 protocol is pretty difficult to block, and it has some other transports that are options if obfs4 is unusable in a heavy censorship regime. This page is a good overview of how to start; with the right transport and bridge setup it’ll be extremely difficult for your ISP to prevent you having access.

    You could make your home server a securely-accessed onion site and connect to a remote-access-via-web service you’re running there. That part might be a little challenging (and this process overall may be overkill) but it’d be very challenging for them to block it, I think, so if you’ve tried some things and had no luck, that might be the way to do it.

    Be careful obviously














  • Federation in general seems like it’s been flaky as hell ever since a month or two ago… my guess (especially if you see it on some Lemmy servers and not others) is that it’s delayed and will show up eventually.

    It’s possible that there’s some unexpected behavior that leads it to federate some places and not others, but my expectation is that once your comment is on lemmy.ml’s server, it’s federation delay between the Lemmy servers and nothing to do with you specifically.


  • Hey, that’s wonderful! Good to hear. Yeah I would just throw away the memory and do a certain amount of double-checking of what’s on your disk, as some of it may have been corrupted during the time the broken memory was in there. But yeah if you can run and do stuff without errors after taking out the bad stick then that sounds like progress.



  • Sounds like serious hardware problems (bad memory sounds highly likely if that’s what memtest is telling you). Replace the faulty hardware before changing out any software, and before the badness “spreads”; you may already have corrupted a certain amount of the data / installed software on your disk by writing back data after the bad memory corrupted it, if you’ve been running on the broken hardware for that long.


  • I wish Debian had better support for software that wants to do its own package management.

    They do it a little bit with python, but for most things it’s either “stay within the wonderful Debian package management but then find out that the node thing you want to do is functionally impossible” or “abandon apt for a mismashed patchwork of randomly-placed and haphazardly-secured independently downloaded little mini-repos for Node, python, maybe some Docker containers, Composer, snap, some stuff that wants you to just wget a shell script and pipe it to sudo sh, and God help you, Nvidia drivers. At least libc6 is secure though.”

    I wish that there was a big multiarch-style push to acknowledge that lots of things want to do their own little package management now, and that’s okay, and somehow bring it into the fold (again their pyenv handling seems like a pretty good example of how it can be done in a mutually-working way) so it’s harmonious with the packaging system instead of existing as something of an opponent to it. Maybe this already exists and I’m not aware of it but if it exists I’m not aware of it.



  • All Linux systems will be very likely vulnerable to this if they’re not they’re patched with the fix. Patched systems will not be vulnerable. That’s true for Debian and Ubuntu, as it is for any Linux system. The commands I gave are determining whether or not you’re patched, on a Debian or Ubuntu system.

    What distro are you running? I can give you commands like that for any Linux system to determine whether or not you’re patched.