Hello everybody,

I’m trying to read a (probably damaged) microSD card from my computer (tried with two different computers, both Arch Linux, which can read other card without any problems). There isn’t any singal of life (no /dev/sdX, nothing with GParted, testdisk, …); the only thing that I found was in dmesg. Here’s the output of sudo dmesg | rg "mmc0":

Any idea on how to resolve?

  • OsrsNeedsF2P@lemmy.ml
    link
    fedilink
    arrow-up
    7
    ·
    1 year ago

    Your output from dmesg didn’t paste.

    Does the card appear in lsblk? Also try cleaning any dirt off the microSD

    • djtech@lemmy.worldOP
      link
      fedilink
      arrow-up
      6
      ·
      1 year ago

      Sorry, this is the output: [ 8306.605559] mmc0: cannot verify signal voltage switch [ 8306.901332] mmc0: error -110 whilst initialising SD card [ 8307.544364] mmc0: cannot verify signal voltage switch [ 8307.837385] mmc0: error -110 whilst initialising SD card [ 8308.488564] mmc0: cannot verify signal voltage switch [ 8308.789314] mmc0: error -110 whilst initialising SD card [ 8582.217859] mmc0: error -123 whilst initialising SD card [ 8584.685053] mmc0: cannot verify signal voltage switch [ 8584.982799] mmc0: error -110 whilst initialising SD card [ 8585.628028] mmc0: cannot verify signal voltage switch [ 8585.926901] mmc0: error -110 whilst initialising SD card [ 8586.573009] mmc0: cannot verify signal voltage switch [ 8586.870849] mmc0: error -110 whilst initialising SD card

      The reader can’t initalizie the SD card, so no “/dev/sdb” (nothing on lsblk also, obvioulsy).

      I’ll try cleaning it better, but I already used a napkin.

      • OsrsNeedsF2P@lemmy.ml
        link
        fedilink
        arrow-up
        10
        ·
        edit-2
        1 year ago

        mmc0: cannot verify signal voltage switch suggests something is wrong with the hardware (either SD card or card reader). -110 is a timeout error, and -123 generally indicates a problem with media hardware.

        You’re not gonna fix this with software. Try a different card reader, or if you think it’s the SD card, put a bit of alcohol on a cotton swab and gently clean the contacts. Let the card fully dry, then try again.

        Obviously this is a hail-merry shot, but your card is likely physically done for

      • Hexarei
        link
        fedilink
        arrow-up
        1
        ·
        1 year ago

        You can edit your post to add these details