My Raspberry Pi, on which I host a Minecraft server, suddenly froze. I cannot not SSH in, nor can I join the Minecraft server. I ran the Minecraft server in Docker, via itzg/docker-minecraft-server. I turned off the Raspberry Pi, took out its microsd and plugged it into my PC, to at least attempt to run the Minecraft server from my PC to see if I still have the data. I tried to copy it with cp, but I got an input-output error. Could this be the filesystem’s fault? And how can I fix this? If you need any additional info about this crash, please do not hesitate to ask.

    • schizo@forum.uncomfortable.businessEnglish
      11·
      2 months ago

      I’ll second that: every single issue I’ve had with any of the Pis that are around here have all been bad sd cards.

      They’re useful if you’re using an OS that doesn’t ever write to them, but as soon as you’re using a full Linux distro or running software that is writing logs or data, they’re going to fail and probably sooner than later and, of course, at the most annoying time possible because it’s a computer and that’s their thing.

  • Possibly linux@lemmy.zipEnglish
    7·
    2 months ago

    “He’s dead Jim”

    MicroSD cards aren’t designed for a lot of writes. Your card it probably dead. If you must use a RPI with a SD card you should get an enterprise grade MicroSD

  • the_crotch@sh.itjust.works
    71·
    2 months ago

    If you think it’s the filesystem try running fsck. It sounds like a failing storage device to me but there’s not nearly enough information to say for sure

    • Gregor@gregtech.euOP
      4·
      2 months ago

      Could this possibly result in the loss of data? If so, what’s a simple way to do a backup of an entire disk?

      • explore_broaden@midwest.social
        7·
        2 months ago

        fsck almost certainly isn’t going to cause loss of data, but it will likely inform you about a loss that already occurred if that is the issue you are having.

      • mvirts@lemmy.world
        4·
        2 months ago

        ddrescue is probably your best bet

        dd is the simplest: dd if=/path/to/disk/device of=/path/to/backup/file but it may fail with a broken device. ddrescue is similar but handles io errors appropriately and can retry bad reads.

      • the_crotch@sh.itjust.works
        2·
        2 months ago

        If the disk is failing anything you do that reads or writes it could cause data loss. Even having it plugged in and powered potentially could. It depends on what component of it is failing.

        That being said, fsck is pretty safe. It’s the equivalent of chkdsk in windows, it looks specifically at the filesystem for things that may have gotten screwy.

        ddrescue/gddrescue is your best bet for recovery. It can detect bad blocks and skip them, and it has some p robust resuming capabilities if your disk locks up while.its running. I usually use it to clone entire physical disks to another disk or an image file that can be mounted. I don’t know if it can be used to grab specific files, I’ve never tried.

        If it was me, I’d take the disk out and let it cool to room temperature. Then I’d ddrescue the whole thing, with resume turned on, to an image file. Then I’d run fsck. If fsck finds and recovers filesystem issues, I’d put it back in the pi, continue using it, and start doing regular backups of important files via a cron task.

  • BigDotNet@lemmy.mlEspañol
    31·
    2 months ago

    I believe your SD it’s fried, you should try using a variant of SBC with eMMC support. Like for example a Banana Pi M4 Berry or a Orange Pi 3B with eMMC module.