How is microSD error 123 felt like?

hd_scania · 06-02-2020, 02:08 AM

As for gdisk is gone against opening the card, which progs could be helpful to deal with the error ‘‘123’’?

Code:

[hd_scania@hd-scania ~]$ sudo gdisk /dev/sdb
GPT fdisk (gdisk) version 1.0.3
Problem opening /dev/sdb for reading! Error is 123.
[hd_scania@hd-scania ~]$ sudo cgdisk /dev/sdb
Could not load partitions from '/dev/sdb'! Aborting!
[hd_scania@hd-scania ~]$

pan64 · 06-02-2020, 02:15 AM

if you could not open that card for reading nobody can help you. You can simply try cat /dev/sdb > /dev/null to check if that card is readable.
Also you can check /var/log for a better error message.

fatmac · 06-02-2020, 03:24 AM

A possible solution (to reuse the card) - clear the first few MB,

Code:

sudo dd if=/dev/zero of=/dev/sdb bs=4M

then give it a new MBR, re partition, & put a file system on it.

hd_scania · 06-02-2020, 05:04 AM

Code:

[hd_scania@open ~]$ sudo dd if=/dev/zero of=/dev/da0 bs=13K
dd: /dev/da0: Device not configured
1+0 records in
0+0 records out
0 bytes transferred in 0.000178 secs (0 bytes/sec)
[hd_scania@open ~]$ sudo gdisk /dev/da0
Warning! Read error 6; strange behavior now likely!
Warning! Read error 6; strange behavior now likely!
Partition table scan:
  MBR: not present
  BSD: not present
  APM: not present
  GPT: not present

Creating new GPT entries in memory.

Command (? for help): p
Disk /dev/da0: 0 sectors, 0 bytes
Sector size (logical): 512 bytes
Disk identifier (GUID): E84F1D5F-58AB-421C-9C59-3A203F6FE5DC
Partition table holds up to 128 entries
Main partition table begins at sector 2 and ends at sector 33
First usable sector is 34, last usable sector is 18446744073709551582
Partitions will be aligned on 2048-sector boundaries
Total free space is 0 sectors (0 bytes)

Number  Start (sector)    End (sector)  Size       Code  Name

Command (? for help): q
[hd_scania@open ~]$ sudo cat /dev/da0 > /dev/null
cat: /dev/da0: Device not configured
[hd_scania@open ~]$ sudo fsck -ffyy -t msdosfs /dev/da0
** /dev/da0
could not read boot block
[hd_scania@open ~]$

pan64 · 06-02-2020, 05:06 AM

what is that of=/dev/da0 ??

hd_scania · 06-02-2020, 05:22 AM

/dev/da0 is how the same card is numbered on HBSD

Quote:

Originally Posted by pan64

what is that of=/dev/da0 ??

pan64 · 06-02-2020, 05:32 AM

that dd was not successful. It could not write anything onto /dev/da0.
Did you try the cat command I posted?

hd_scania · 06-02-2020, 06:06 AM

As given before, my cat result was Device not configured, and it gets perplexed how and why it reports not configured.
Given here, the card is NOT visible to sudo gpart.

Quote:

Originally Posted by pan64

that dd was not successful. It could not write anything onto /dev/da0.
Did you try the cat command I posted?

pan64 · 06-02-2020, 06:10 AM

ok, sorry, did not see that. So this card is not usable. Either the reader or the card itself is not ok (or both).
You can try another card, another reader (or probably another OS).

hd_scania · 06-02-2020, 06:18 AM

The same card with THREE readers was usually NOT visible to any disk managers, or seen outside but NOT readable inside
Now i still have an emptied card working fine, but 2x smaller than the dead one.

Quote:

Originally Posted by pan64

ok, sorry, did not see that. So this card is not usable. Either the reader or the card itself is not ok (or both).
You can try another card, another reader (or probably another OS).

hd_scania · 06-02-2020, 06:40 AM

And the SMART result has been out with my screenshots below,

Code:

smartctl 7.1 2019-12-30 r5022 [FreeBSD 13.0-CURRENT-HBSD amd64] (local build)
Copyright (C) 2002-19, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF INFORMATION SECTION ===
Vendor:               Generic-
Product:              SD/MMC
Revision:             1.00
Device type:          disk
Local Time is:        Tue Jun  2 19:54:02 2020 HKT
NO MEDIUM present in device
SMART support is:     Unavailable - device lacks SMART capability.
=== START OF READ SMART DATA SECTION ===

fatmac · 06-02-2020, 08:19 AM

Looking like it is dead/corrupted - I've come across other people with dead micro SD cards, they don't seem to be too reliable.

One of the reasons that I don't want to rely on them on my RPi computers, I prefer to USB boot them.

hd_scania · 06-02-2020, 07:26 PM

Dead/corrupted ... You mean the card was hard-bricked?
If not, how to recover those data for myself?

Quote:

Originally Posted by fatmac

Looking like it is dead/corrupted - I've come across other people with dead micro SD cards, they don't seem to be too reliable.
One of the reasons that I don't want to rely on them on my RPi computers, I prefer to USB boot them.

hd_scania · 06-02-2020, 07:43 PM

And the microSD was dead on an Android, but NOT a desktop, and i’ve put it onto a HBSD/Linux desktop as for data recovery.

pan64 · 06-03-2020, 12:37 AM

Quote:

Originally Posted by hd_scania

Dead/corrupted ... You mean the card was hard-bricked?
If not, how to recover those data for myself?

there is no way to recover anything if you get only errors when you try to read it.
you might try testdisk to recover some data.