Cannot mount, read, write, or format SD Card

Question

I can

• read from my micro-sd card when it is in "lock" position

but things get very weird when I try "unlock" it: there is no way I can

• fsck it, nor
• mount it, nor
• read it, nor..
• format it!

I need to format it, what can I do?

Here is my gparted output:

$ sudo gparted
Created symlink /run/systemd/system/-.mount → /dev/null.
Created symlink /run/systemd/system/boot-efi.mount → /dev/null.
Created symlink /run/systemd/system/home-iago\x2dlito-.docker-devicemapper.mount → /dev/null.
Created symlink /run/systemd/system/home.mount → /dev/null.
Created symlink /run/systemd/system/run-user-1000.mount → /dev/null.
Created symlink /run/systemd/system/run-user-117.mount → /dev/null.
Created symlink /run/systemd/system/tmp.mount → /dev/null.
Created symlink /run/systemd/system/var.mount → /dev/null.

======================
libparted : 3.2                                         # see screenshots
======================                                  #
Input/output error during write on /dev/mmcblk0         # first error
Error fsyncing/closing /dev/mmcblk0: Input/output error # second error
Input/output error during write on /dev/mmcblk0         # start looping
Error fsyncing/closing /dev/mmcblk0: Input/output error #
Input/output error during read on /dev/mmcblk0          #

Clicking Device -> Create partition table

choosing msdos, Apply, wait for a while then

Ignore

And then it starts looping between these two error messages until I finally Cancel.

After cancelling, the status bar displays

for a while, then

.. anyway there is no more mmcblk0 visible in the up-left box.

Any idea what may be wrong?
How can I format my SD card?
Is it just dead?

---

[EDIT] more info? When inserted in unlocked state:

$ dmesg
...
[ 1282.922022] mmc0: cannot verify signal voltage switch
[ 1283.097715] mmc0: new ultra high speed SDR104 SDHC card at address 0001
[ 1283.104727] mmcblk0: mmc0:0001 SD32G 29.0 GiB 
[ 1283.106469]  mmcblk0: p1 p2
[ 1284.996181] FAT-fs (mmcblk0p1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
[ 1285.018828] EXT4-fs (mmcblk0p2): warning: mounting unchecked fs, running e2fsck is recommended

Oh, okay..

$ sudo e2fsck /dev/mmcblk0
e2fsck 1.43.4 (31-Jan-2017)
e2fsck: Input/output error while trying to open mmcblk0

The superblock could not be read or does not describe a valid ext2/ext3/ext4
filesystem.  If the device is valid and it really contains an ext2/ext3/ext4
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
    e2fsck -b 8193 <device>
 or
    e2fsck -b 32768 <device>

.. suggested commands both yield the same output.

---

Playing around with f3 on malat advice:

# f3write /dev/mmcblk0p1
f3write: Can't open path /dev/mmcblk0p1: Not a directory

# f3write /dev/mmcblk0p2
f3write: Can't open path /dev/mmcblk0p2: Not a directory

# f3read /dev/mmcblk0p1
f3read: Can't open path /dev/mmcblk0p1: Not a directory

# f3read /dev/mmcblk0p2
f3read: Can't open path /dev/mmcblk0p1: Not a directory

Trying their mounting point instead:

# f3write /media/iago-lito/boot # /dev/mmcblk0p1
f3write: f3write.c:403: get_freespace: Assertion `!statvfs(path, &fs)' failed.
[1]    11908 abort      f3write /media/iago-lito/boot

# f3write /media/iago-lito/0aed834e-8c8f-412d-a276-a265dc676112 # /dev/mmcblk0p2
Free space: 24.50 GB
Creating file 1.h2w ...
f3write: Can't create file 0aed834e-8c8f-412d-a276-a265dc676112/1.h2w: Input/output error

# f3read /media/iago-lito/boot # /dev/mmcblk0p1
                  SECTORS      ok/corrupted/changed/overwritten

  Data OK: 0.00 Byte (0 sectors)
Data LOST: 0.00 Byte (0 sectors)
           Corrupted: 0.00 Byte (0 sectors)
    Slightly changed: 0.00 Byte (0 sectors)
         Overwritten: 0.00 Byte (0 sectors)
Average reading speed: 0.00 Byte/s

# f3read /media/iago-lito/0aed834e-8c8f-412d-a276-a265dc676112 # /dev/mmcblk0p2
                  SECTORS      ok/corrupted/changed/overwritten

  Data OK: 0.00 Byte (0 sectors)
Data LOST: 0.00 Byte (0 sectors)
           Corrupted: 0.00 Byte (0 sectors)
    Slightly changed: 0.00 Byte (0 sectors)
         Overwritten: 0.00 Byte (0 sectors)
Average reading speed: 0.00 Byte/s

.. `smells bad.

---

Now try playing gdisk with Alex Berry:

First try, both partitions were mounted:

$ sudo gdisk /dev/mmcblk0                                                                          20 ↵
GPT fdisk (gdisk) version 1.0.1

Partition table scan:
  MBR: MBR only
  BSD: not present
  APM: not present
  GPT: not present


***************************************************************
Found invalid GPT and valid MBR; converting MBR to GPT format
in memory. THIS OPERATION IS POTENTIALLY DESTRUCTIVE! Exit by
typing 'q' if you don't want to convert your MBR partitions
to GPT format!
***************************************************************


Warning! Secondary partition table overlaps the last partition by
33 blocks!
You will need to delete this partition or resize it in another utility.

Command (? for help): x

Expert command (? for help): z
About to wipe out GPT on /dev/mmcblk0. Proceed? (Y/N): Y
Warning! GPT main partition table not overwritten! Error is 0
Warning: The kernel is still using the old partition table.
The new table will be used at the next reboot or after you
run partprobe(8) or kpartx(8)
GPT data structures destroyed! You may now partition the disk using fdisk or
other utilities.

Expert command (? for help):

Second try after unmounting both partitions:

sudo gdisk /dev/mmcblk0                                                                                                      32 ↵
GPT fdisk (gdisk) version 1.0.1

Warning! Read error 5; strange behavior now likely!
Warning! Read error 5; strange behavior now likely!
Partition table scan:
  MBR: not present
  BSD: not present
  APM: not present
  GPT: not present

Creating new GPT entries.

Command (? for help): x

Expert command (? for help): z
About to wipe out GPT on /dev/mmcblk0. Proceed? (Y/N): Y
Warning! GPT main header not overwritten! Error is 5
Warning: The kernel is still using the old partition table.
The new table will be used at the next reboot or after you
run partprobe(8) or kpartx(8)
GPT data structures destroyed! You may now partition the disk using fdisk or
other utilities.

.. I am glad error messages (no5) at least are consistent with my deepest thoughts!
Yanking card and rebooting..

Now gparted does not list /dev/mmcblk0 at all after scanning devices:

Input/output error during read on /dev/mmcblk0

hard time for hardware -_-"