Hello.
I have a Sandisk ExtremeA2 64Gb micro SD card that I have been using for a couple of years in my smartphone.
Yesterday I decided to use it with another device (ESP32-CAM) and at some point, while flashing this new device with an Arduino sketch, for some reason, the Arduino IDE got stcuk (froze) and I had to power down the laptop long-pressing the power button.
After the power cycle, when I tried to mount the SD card on my laptop, I got a message error saying something about the SuperBlock Magic number being wrong. Even though, after some attempts I was able to mount the SD card but when IAs this was my smartphone card, I asked a friend of mine that is using Windows on his latptop to use a software to see what could be recovered (recuva) and he recovered some stuff (I didn't check it what exactly was recovered).
This is what is shown when the SD card is inserted in my laptop:
This is what is shown inThis is what is shown in
At the beginning, when I couldn't mount the device, I got a suggestion to try to use:
So, I have been reading abit about this subject of SuperBlocks and how to fix the issue in some scenarios but I didn't want to mess with it without knowing exactly what I was doing, and probably making it worse that what it is already.
I found some things such like:
https://www.ibm.com/docs/ru/aix/7.2?top ... superblock
https://unix.stackexchange.com/question ... uper-block
https://www.linode.com/community/questi ... lock-error
https://raspberrypi.stackexchange.com/q ... superblock
I tried some of the commands there such as:and also
So, what else can I try?
I have a Sandisk ExtremeA2 64Gb micro SD card that I have been using for a couple of years in my smartphone.
Yesterday I decided to use it with another device (ESP32-CAM) and at some point, while flashing this new device with an Arduino sketch, for some reason, the Arduino IDE got stcuk (froze) and I had to power down the laptop long-pressing the power button.
After the power cycle, when I tried to mount the SD card on my laptop, I got a message error saying something about the SuperBlock Magic number being wrong. Even though, after some attempts I was able to mount the SD card but when I
ls -lahit, I got this:
Code:
$ ls -lah ~/mnt/usb1/ls: cannot access '/home/user/mnt/usb1/.αò'$'\f''╫#éc.⌠╬;': Input/output errorls: cannot access '''/home/user/mnt/usb1/┬'\''u√│pƒδ.ZL'$'\020': Input/output errorls: cannot access '''/home/user/mnt/usb1/Ñ*&╢║Dg'\''.ªw'$'\020': Input/output errorls: cannot access '/home/user/mnt/usb1/'\''°~₧"┤┤y.¼5m': Input/output errortotal 2.8Gdrwxr-xr-x 10 user user 1.0K Jan 1 1970 .drwxr-xr-x 4 user user 38 Jan 23 14:17 ..d????????? ? ? ? ? ? ''\''°~₧"┤┤y.¼5m'drwxr-xr-x 2 user user 3.0K Jan 1 1980 19700101drwxr-xr-x 2 user user 6.5K Jan 25 09:16 20240125-rwxr-xr-x 1 user user 0 Jan 1 1980 current.avidrwxr-xr-x 2 user user 512 Jan 1 1980 data-rwxr-xr-x 1 user user 448M Jun 26 2078 'î4-╬⌡g╬>.+°Ö'd????????? ? ? ? ? ? '''Ñ*&╢║Dg'\''.ªw'$'\020'drwxr-xr-x 2 user user 512 Jan 25 10:57 'System Volume Information'd????????? ? ? ? ? ? '''┬'\''u√│pƒδ.ZL'$'\020'd????????? ? ? ? ? ? '.αò'$'\f''╫#éc.⌠╬;'-rwxr-xr-x 1 user user 2.4G May 31 2042 'σo┌╙┼║'$'\a''è.5▌c'$This is what is shown when the SD card is inserted in my laptop:
Code:
$ sudo udevadm monitormonitor will print the received events for:UDEV - the event which udev sends out after rule processingKERNEL - the kernel ueventKERNEL[30225.046200] add /devices/pci0000:00/0000:00:14.0/usb1/1-5 (usb)KERNEL[30225.047477] add /devices/pci0000:00/0000:00:14.0/usb1/1-5/1-5:1.0 (usb)KERNEL[30225.047845] add /devices/virtual/workqueue/scsi_tmf_1 (workqueue)KERNEL[30225.048111] add /devices/pci0000:00/0000:00:14.0/usb1/1-5/1-5:1.0/host1 (scsi)KERNEL[30225.048155] add /devices/pci0000:00/0000:00:14.0/usb1/1-5/1-5:1.0/host1/scsi_host/host1 (scsi_host)KERNEL[30225.048248] bind /devices/pci0000:00/0000:00:14.0/usb1/1-5/1-5:1.0 (usb)KERNEL[30225.048380] bind /devices/pci0000:00/0000:00:14.0/usb1/1-5 (usb)UDEV [30225.052668] add /devices/virtual/workqueue/scsi_tmf_1 (workqueue)UDEV [30225.053143] add /devices/pci0000:00/0000:00:14.0/usb1/1-5 (usb)UDEV [30225.054190] add /devices/pci0000:00/0000:00:14.0/usb1/1-5/1-5:1.0 (usb)UDEV [30225.054932] add /devices/pci0000:00/0000:00:14.0/usb1/1-5/1-5:1.0/host1 (scsi)UDEV [30225.055589] add /devices/pci0000:00/0000:00:14.0/usb1/1-5/1-5:1.0/host1/scsi_host/host1 (scsi_host)UDEV [30225.056156] bind /devices/pci0000:00/0000:00:14.0/usb1/1-5/1-5:1.0 (usb)UDEV [30225.056960] bind /devices/pci0000:00/0000:00:14.0/usb1/1-5 (usb)KERNEL[30226.055365] add /devices/pci0000:00/0000:00:14.0/usb1/1-5/1-5:1.0/host1/target1:0:0 (scsi)KERNEL[30226.055650] add /devices/pci0000:00/0000:00:14.0/usb1/1-5/1-5:1.0/host1/target1:0:0/1:0:0:0 (scsi)KERNEL[30226.055702] add /devices/pci0000:00/0000:00:14.0/usb1/1-5/1-5:1.0/host1/target1:0:0/1:0:0:0/scsi_device/1:0:0:0 (scsi_device)KERNEL[30226.055750] add /devices/pci0000:00/0000:00:14.0/usb1/1-5/1-5:1.0/host1/target1:0:0/1:0:0:0/scsi_generic/sg1 (scsi_generic)KERNEL[30226.055780] add /devices/pci0000:00/0000:00:14.0/usb1/1-5/1-5:1.0/host1/target1:0:0/1:0:0:0/scsi_disk/1:0:0:0 (scsi_disk)KERNEL[30226.055813] add /devices/pci0000:00/0000:00:14.0/usb1/1-5/1-5:1.0/host1/target1:0:0/1:0:0:0/bsg/1:0:0:0 (bsg)UDEV [30226.057756] add /devices/pci0000:00/0000:00:14.0/usb1/1-5/1-5:1.0/host1/target1:0:0 (scsi)UDEV [30226.060199] add /devices/pci0000:00/0000:00:14.0/usb1/1-5/1-5:1.0/host1/target1:0:0/1:0:0:0 (scsi)UDEV [30226.062824] add /devices/pci0000:00/0000:00:14.0/usb1/1-5/1-5:1.0/host1/target1:0:0/1:0:0:0/scsi_device/1:0:0:0 (scsi_device)UDEV [30226.063749] add /devices/pci0000:00/0000:00:14.0/usb1/1-5/1-5:1.0/host1/target1:0:0/1:0:0:0/scsi_generic/sg1 (scsi_generic)UDEV [30226.064315] add /devices/pci0000:00/0000:00:14.0/usb1/1-5/1-5:1.0/host1/target1:0:0/1:0:0:0/scsi_disk/1:0:0:0 (scsi_disk)UDEV [30226.064549] add /devices/pci0000:00/0000:00:14.0/usb1/1-5/1-5:1.0/host1/target1:0:0/1:0:0:0/bsg/1:0:0:0 (bsg)KERNEL[30226.294697] add /devices/virtual/bdi/8:16 (bdi)UDEV [30226.295128] add /devices/virtual/bdi/8:16 (bdi)KERNEL[30226.707663] add /devices/pci0000:00/0000:00:14.0/usb1/1-5/1-5:1.0/host1/target1:0:0/1:0:0:0/block/sdb (block)KERNEL[30226.707764] add /devices/pci0000:00/0000:00:14.0/usb1/1-5/1-5:1.0/host1/target1:0:0/1:0:0:0/block/sdb/sdb1 (block)KERNEL[30226.707990] bind /devices/pci0000:00/0000:00:14.0/usb1/1-5/1-5:1.0/host1/target1:0:0/1:0:0:0 (scsi)UDEV [30226.858485] add /devices/pci0000:00/0000:00:14.0/usb1/1-5/1-5:1.0/host1/target1:0:0/1:0:0:0/block/sdb (block)UDEV [30227.006821] add /devices/pci0000:00/0000:00:14.0/usb1/1-5/1-5:1.0/host1/target1:0:0/1:0:0:0/block/sdb/sdb1 (block)UDEV [30227.008444] bind /devices/pci0000:00/0000:00:14.0/usb1/1-5/1-5:1.0/host1/target1:0:0/1:0:0:0 (scsi)This is what is shown in
dmesgwhen I plug the SD card in:
Code:
I/O error, dev sdb, sector 0 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2Buffer I/O error on dev sdb, logical block 0, async page readdmesgright after I mount the SD card whith:
Code:
sudo mount -o rw,uid=1000,gid=1000 /dev/sdb1 ~/mnt/usb1Code:
$ sudo dmesg[30369.874077] FAT-fs (sdb1): Volume was not properly unmounted. Some data may be corrupt. Please run fscksudo e2fsck -b 8193 /dev/sdborsudo e2fsck -b 32768 /dev/sdbwhich I tried but the same messages were popping up, about the Magic Number of SuperBlocks being wrong.
So, I have been reading abit about this subject of SuperBlocks and how to fix the issue in some scenarios but I didn't want to mess with it without knowing exactly what I was doing, and probably making it worse that what it is already.
I found some things such like:
https://www.ibm.com/docs/ru/aix/7.2?top ... superblock
https://unix.stackexchange.com/question ... uper-block
https://www.linode.com/community/questi ... lock-error
https://raspberrypi.stackexchange.com/q ... superblock
I tried some of the commands there such as:
Code:
$ sudo e2fsck -b 8193 /dev/sdbe2fsck 1.47.0 (5-Feb-2023)e2fsck: Bad magic number in super-block while trying to open /dev/sdbThe superblock could not be read or does not describe a valid ext2/ext3/ext4filesystem. If the device is valid and it really contains an ext2/ext3/ext4filesystem (and not swap or ufs or something else), then the superblockis corrupt, and you might try running e2fsck with an alternate superblock: e2fsck -b 8193 <device> or e2fsck -b 32768 <device>Found a dos partition table in /dev/sdbCode:
$ sudo e2fsck -b 32768 /dev/sdbe2fsck 1.47.0 (5-Feb-2023)e2fsck: Bad magic number in super-block while trying to open /dev/sdbThe superblock could not be read or does not describe a valid ext2/ext3/ext4filesystem. If the device is valid and it really contains an ext2/ext3/ext4filesystem (and not swap or ufs or something else), then the superblockis corrupt, and you might try running e2fsck with an alternate superblock: e2fsck -b 8193 <device> or e2fsck -b 32768 <device>Found a dos partition table in /dev/sdb$Code:
$ sudo dumpe2fs /dev/sdb1 | grep -i superblockdumpe2fs 1.47.0 (5-Feb-2023)dumpe2fs: Bad magic number in super-block while trying to open /dev/sdb1Couldn't find valid filesystem superblock.Statistics: Posted by PsySc0rpi0n — 2024-01-25 17:43