Score:0

A particular microSD adapter failing to be recognized

mx flag

So I have a 4GB SD card with a disk image written on it and I have two microSD adapters: one is native to the card, the other is an old one.

Inserting the card with the older adapter yields no problems and the card is recognized as expected:

microSD with the older adapter

It is the native adapter, however, that won't work:

microSD with its native adapter

Now it's not a big deal as I can still access the data through the other adapter but I'm just curious as to why this particular adapter won't just work. Do you have any ideas? Has anyone else ever faced with a similar issue?

journalctl outputs:

Aug 17 18:48:32 kernel: mmc0: card 59b4 removed
Aug 17 18:48:57 kernel: mmc0: new high speed SDHC card at address 59b4
Aug 17 18:48:57 kernel: mmcblk0: mmc0:59b4 USD   3.73 GiB 
Aug 17 18:48:57 kernel: print_req_error: 4 callbacks suppressed
Aug 17 18:48:57 kernel: blk_update_request: I/O error, dev mmcblk0, sector 0 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
Aug 17 18:48:57 kernel: buffer_io_error: 3 callbacks suppressed
Aug 17 18:48:57 kernel: Buffer I/O error on dev mmcblk0, logical block 0, async page read
Aug 17 18:48:57 kernel: blk_update_request: I/O error, dev mmcblk0, sector 0 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
Aug 17 18:48:57 kernel: Buffer I/O error on dev mmcblk0, logical block 0, async page read
Aug 17 18:48:57 kernel: blk_update_request: I/O error, dev mmcblk0, sector 0 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
Aug 17 18:48:57 kernel: Buffer I/O error on dev mmcblk0, logical block 0, async page read
Aug 17 18:48:57 kernel: ldm_validate_partition_table(): Disk read failed.
Aug 17 18:48:57 kernel: blk_update_request: I/O error, dev mmcblk0, sector 0 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
Aug 17 18:48:57 kernel: Buffer I/O error on dev mmcblk0, logical block 0, async page read
Aug 17 18:48:57 kernel: blk_update_request: I/O error, dev mmcblk0, sector 0 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
Aug 17 18:48:57 kernel: Buffer I/O error on dev mmcblk0, logical block 0, async page read
Aug 17 18:48:57 kernel: blk_update_request: I/O error, dev mmcblk0, sector 0 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
Aug 17 18:48:57 kernel: Buffer I/O error on dev mmcblk0, logical block 0, async page read
Aug 17 18:48:57 kernel: blk_update_request: I/O error, dev mmcblk0, sector 0 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
Aug 17 18:48:57 kernel: Buffer I/O error on dev mmcblk0, logical block 0, async page read
Aug 17 18:48:57 kernel: Dev mmcblk0: unable to read RDB block 0
Aug 17 18:48:57 kernel: blk_update_request: I/O error, dev mmcblk0, sector 0 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
Aug 17 18:48:57 kernel: Buffer I/O error on dev mmcblk0, logical block 0, async page read
Aug 17 18:48:57 kernel: blk_update_request: I/O error, dev mmcblk0, sector 0 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
Aug 17 18:48:57 kernel: Buffer I/O error on dev mmcblk0, logical block 0, async page read
Aug 17 18:48:57 kernel: blk_update_request: I/O error, dev mmcblk0, sector 24 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
Aug 17 18:48:57 kernel: Buffer I/O error on dev mmcblk0, logical block 3, async page read
Aug 17 18:48:57 kernel:  mmcblk0: unable to read partition table

mount output:

mount: /mnt/sd: can't read superblock on /dev/mmcblk0.

fsck output:

fsck.ext2: Input/output error while trying to open /dev/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>

fdisk output:

fdisk: cannot open /dev/mmcblk0: Input/output error

The card can be mounted flawlessly using the older adapter. Here are the journalctl outputs:

Aug 17 18:56:21 kernel: mmc0: new high speed SDHC card at address 59b4
Aug 17 18:56:21 kernel: mmcblk0: mmc0:59b4 USD   3.73 GiB (ro)
Aug 17 18:56:21 kernel: GPT:Primary header thinks Alt. header is not at the end of the disk.
Aug 17 18:56:21 kernel: GPT:5744931 != 7821311
Aug 17 18:56:21 kernel: GPT:Alternate GPT header not at the end of the disk.
Aug 17 18:56:21 kernel: GPT:5744931 != 7821311
Aug 17 18:56:21 kernel: GPT: Use GNU Parted to correct GPT errors.
Aug 17 18:56:21 kernel:  mmcblk0: p1 p2 p3 p4
Aug 17 18:56:32 kernel: hfsplus: Filesystem is marked locked, mounting read-only.
Aug 17 18:56:32 systemd[1]: Finished Clean the /media/USER/ISOIMAGE mount point.
Aug 17 18:56:32 udisksd[710]: Mounted /dev/mmcblk0p3 at /media/USER/ISOIMAGE on behalf of uid 1000
mangohost

Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.