Can't format SD card with anything - ADVANCED

overkill22 · 2018-06-13 14:32:56

iMBeCil wrote:

Sorry it doesn't work.
At this point I'm out of ideas.
Except, possibly to change partition types of the existing partition to Linux partition.
Or, perhaps, press 'o', then 'w', then remove SD card ... and then reinsert card and then create partitions?
Maybe, the SD card really is damaged?
Sorry I couldn't help, perhaps someone more knowledgeable will step in ...

I don't think the card is damaged, I had access to all the data and then somehow formatted.
I think is something like permission or maybe MBR or stuff like that (but I don't know what I'm talking about)

With fdisk I tried to do the separate processed but it doesn't work.

It's like if the read-only permission set from Android is unbreakable.

iMBeCil · 2018-06-13 15:01:48

Just a general info ... sdtool. Unfortunaltely, works only for SD cards which connect as /dev/mmcblk* (not via USB).

Perhaps, try another computer with different card reader?

(Also, the first partition might be some read-only block, with certain software which enables 'peculiar' (custom/intended) behaviour like protecting SD card with read-only mode.)

EDIT: also sdlocker-tiny. I wasn't aware of those details on SD cards ... especially that the write-protect slider does nothing, i.e. it is up to application to honor (or not) this slider.

Last edited by iMBeCil (2018-06-13 15:10:05)

overkill22 · 2018-06-13 15:11:43

iMBeCil wrote:

Just a general info ... sdtool. Unfortunaltely, works only for SD cards which connect as /dev/mmcblk* (not via USB).
Perhaps, try another computer with different card reader?
(Also, the first partition might be some read-only block, with certain software which enables 'peculiar' (custom/intended) behaviour like protecting SD card with read-only mode.)
EDIT: also sdlocker-tiny. I wasn't aware of those details on SD cards ... especially that the write-protect slider does nothing, i.e. it is up to application to honor (or not) this switch.

I "like" this. I really think this is the issue. And I refuse to think it is unfixable.

Second link is really interesting. However I don't know from where to start. As hardware I have only laptops at my dispostal. One linux, one Windows 10, and another that probably is Vista or Windows 8 or some other crap.

any suggestion how to proceed with sdtool?

hhh · 2018-06-13 17:14:02

Moderator note... we've been trying to get on top of the forum organization with the release of Helium, unstickying threads, updating tutorials, etc...

This discussion has, IMO, moved past a "Basic Help" question, I'm moving the thread to "Kernel & Hardware". A redirect link will remain in the Help forum.

Thanks for your understanding!

overkill22 · 2018-06-13 17:16:30

hhh wrote:

Moderator note... we've been trying to get on top of the forum organization with the release of Helium, unstickying threads, updating tutorials, etc...
This discussion has, IMO, moved past a "Basic Help" question, I'm moving the thread to "Kernel & Hardware". A redirect link will remain in the Help forum.
Thanks for your understanding!

yes thank you!
I was unsure to open over there at the beginning, I knew already that was not a simple task ahaha...

Thank you so much

sleekmason · 2018-06-13 21:26:45

There is a program called testdisk in the repos. It is used for partition recovery, and may be of some use.

TestDisk checks the partition and boot sectors of your disks.
It is very useful in forensics, recovering lost partitions.
It works with :
* DOS/Windows FAT12, FAT16 and FAT32
* NTFS ( Windows NT/2K/XP )
* Linux Ext2 and Ext3
* BeFS ( BeOS )
* BSD disklabel ( FreeBSD/OpenBSD/NetBSD )
* CramFS (Compressed File System)
* HFS and HFS+, Hierarchical File System
* JFS, IBM's Journaled File System
* Linux Raid
* Linux Swap (versions 1 and 2)
* LVM and LVM2, Linux Logical Volume Manager
* Netware NSS
* ReiserFS 3.5 and 3.6
* Sun Solaris i386 disklabel
* UFS and UFS2 (Sun/BSD/...)
* XFS, SGI's Journaled File System

ohnonot · 2018-06-14 04:27:18

overkill22 wrote:

After inserting the sd car I got this

(...)
[58656.332344] sd 2:0:0:0: [sdb] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[58656.332358] sd 2:0:0:0: [sdb] tag#0 Sense Key : Not Ready [current] 
[58656.332386] sd 2:0:0:0: [sdb] tag#0 <<vendor>>ASC=0xff <<vendor>>ASCQ=0xff 
[58656.332400] sd 2:0:0:0: [sdb] tag#0 CDB: Read(10) 28 00 00 00 00 00 00 00 08 00
[58656.332407] print_req_error: I/O error, dev sdb, sector 0
[58656.332422] Buffer I/O error on dev sdb, logical block 0, async page read
[58656.333174] ldm_validate_partition_table(): Disk read failed.
[58656.333192] Dev sdb: unable to read RDB block 0
[58656.334063]  sdb: unable to read partition table

i think this points to a hardware error.

in any case, search for the error message:
https://www.startpage.com/do/dsearch?qu … %2Fo+error
please look at the top 2 results before reading on.

the error could be with your PCs card reader, but since the problem started inside the phone, i guess it's really the card itself.

is it fixable?
https://www.startpage.com/do/dsearch?qu … ard+repair

Last edited by ohnonot (2021-06-07 16:26:17)

iMBeCil · 2018-06-14 09:08:23

overkill22 wrote:

any suggestion how to proceed with sdtool?

I really don't know, sorry.

Perhaps, you should forget about this SC card, and buy a new one

Last question: how do you 'connect' your SD card to the computer/laptop? You have a slot in the computer/laptop and insert the SD card inside, or you have a separate device - the 'card reader' - which you connect to the computer/laptop via USB (and then insert your SD card into this separate 'card-reader')?

ohnonot wrote:

overkill22 wrote:
After inserting the sd car I got this
(...)
[58656.332344] sd 2:0:0:0: [sdb] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[58656.332358] sd 2:0:0:0: [sdb] tag#0 Sense Key : Not Ready [current] 
[58656.332386] sd 2:0:0:0: [sdb] tag#0 <<vendor>>ASC=0xff <<vendor>>ASCQ=0xff 
[58656.332400] sd 2:0:0:0: [sdb] tag#0 CDB: Read(10) 28 00 00 00 00 00 00 00 08 00
[58656.332407] print_req_error: I/O error, dev sdb, sector 0
[58656.332422] Buffer I/O error on dev sdb, logical block 0, async page read
[58656.333174] ldm_validate_partition_table(): Disk read failed.
[58656.333192] Dev sdb: unable to read RDB block 0
[58656.334063]  sdb: unable to read partition table
i think this points to a hardware error.
in any case, search for the error message:
https://www.startpage.com/do/dsearch?qu … %2Fo+error
please look at the top 2 results before reading on.
the error could be with your PCs card reader, but since the problem started inside the phone, i guess it's really the card itself.

Indeed, I have noticed this, and actually tried (too) to google "Dev unable to read RDB block" ... lots of links, but difficult to do anything without the OP's SD card at hand. And it might be defective SD card ...

overkill22 · 2018-06-14 13:33:28

sleekmason wrote:

There is a program called testdisk in the repos. It is used for partition recovery, and may be of some use.
TestDisk checks the partition and boot sectors of your disks.
It is very useful in forensics, recovering lost partitions.
It works with :
* DOS/Windows FAT12, FAT16 and FAT32
* NTFS ( Windows NT/2K/XP )
* Linux Ext2 and Ext3
* BeFS ( BeOS )
* BSD disklabel ( FreeBSD/OpenBSD/NetBSD )
* CramFS (Compressed File System)
* HFS and HFS+, Hierarchical File System
* JFS, IBM's Journaled File System
* Linux Raid
* Linux Swap (versions 1 and 2)
* LVM and LVM2, Linux Logical Volume Manager
* Netware NSS
* ReiserFS 3.5 and 3.6
* Sun Solaris i386 disklabel
* UFS and UFS2 (Sun/BSD/...)
* XFS, SGI's Journaled File System

Will take a look, thanks!

ohnonot wrote:

i think this points to a hardware error.
in any case, search for the error message:
https://www.startpage.com/do/dsearch?qu … %2Fo+error
please look at the top 2 results before reading on.
the error could be with your PCs card reader, but since the problem started inside the phone, i guess it's really the card itself.
is it fixable?
https://www.startpage.com/do/dsearch?qu … ard+repair
here's my personal log of hard drive (not sd card) maintenance:
http://dt.iki.fi/hard-drive-and-fs-health-checks

It can be a hardware error, but not for physical damage in case. I contacted Sandisk and this is their official answer:

Sandisk wrote:

I just wanted to mention something that may be useful, since you were saying that you used the card as an internal memory in your phone device with Android OS, I don’t know the version of the Android you are using but in case is Android 6 or higher, please bear in mind that the microSD support implemented into Android 6 or higher is called Adoptable Storage Devices. It allows smartphones to use an external microSD card as if it were the internal storage built into a smartphone.
Once a user installs a microSD card into their device and selects the internal format method the card is formatted and encrypted, locking it to that mobile device.
Once formatted the microSD card cannot be used in any other device. For further information we suggest reviewing the user manual of your mobile device or contacting the manufacturer
We inform you about this because we have seen several cases where this usage damage the card in a very short period of time and we don’t recommend the card to be used like this, you may use it but you may have again the same issue.

I had 2 cards and both "damaged" after an application crash.

OT: what's the deal with startpage? what's the difference with google?

iMBeCil wrote:

overkill22 wrote:
any suggestion how to proceed with sdtool?
I really don't know, sorry.
Perhaps, you should forget about this SC card, and buy a new one
Last question: how do you 'connect' your SD card to the computer/laptop? You have a slot in the computer/laptop and insert the SD card inside, or you have a separate device - the 'card reader' - which you connect to the computer/laptop via USB (and then insert your SD card into this separate 'card-reader')?
ohnonot wrote:
overkill22 wrote:
After inserting the sd car I got this
(...)
[58656.332344] sd 2:0:0:0: [sdb] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[58656.332358] sd 2:0:0:0: [sdb] tag#0 Sense Key : Not Ready [current] 
[58656.332386] sd 2:0:0:0: [sdb] tag#0 <<vendor>>ASC=0xff <<vendor>>ASCQ=0xff 
[58656.332400] sd 2:0:0:0: [sdb] tag#0 CDB: Read(10) 28 00 00 00 00 00 00 00 08 00
[58656.332407] print_req_error: I/O error, dev sdb, sector 0
[58656.332422] Buffer I/O error on dev sdb, logical block 0, async page read
[58656.333174] ldm_validate_partition_table(): Disk read failed.
[58656.333192] Dev sdb: unable to read RDB block 0
[58656.334063]  sdb: unable to read partition table
i think this points to a hardware error.
in any case, search for the error message:
https://www.startpage.com/do/dsearch?qu … %2Fo+error
please look at the top 2 results before reading on.
the error could be with your PCs card reader, but since the problem started inside the phone, i guess it's really the card itself.
Indeed, I have noticed this, and actually tried (too) to google "Dev unable to read RDB block" ... lots of links, but difficult to do anything without the OP's SD card at hand. And it might be defective SD card ...

I definitely have to buy a new one (actually I'll get a replacement from SanDisk), but that's not the point. I can't buy a new SD card every time an app crash and the SD card get spoiled because of some software protections.

It is not my laptop hardware fault, I used both the SD card reader on the laptop and an extenal card reader. And also different phones can't format the card.

Anyway, here's the dmsg of another sd card (Samsung, from my father) with which I'm experiencing the same formatting problem, I just tried to format with dd but then content is still there. I don't know if it was used as internal memory or external memory.
The second code is the dmsg of my SD card, again.

My father SD Samsung:

[ 3663.631324] usb 1-8: new high-speed USB device number 9 using xhci_hcd
[ 3663.774290] usb 1-8: New USB device found, idVendor=058f, idProduct=6366
[ 3663.774303] usb 1-8: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 3663.774312] usb 1-8: Product: Flash Card Reader/Writer
[ 3663.774321] usb 1-8: Manufacturer: Generic
[ 3663.774330] usb 1-8: SerialNumber: 058F63666485
[ 3663.776092] usb-storage 1-8:1.0: USB Mass Storage device detected
[ 3663.777149] scsi host2: usb-storage 1-8:1.0
[ 3664.800263] scsi 2:0:0:0: Direct-Access     Multiple Card  Reader     1.00 PQ: 0 ANSI: 4
[ 3664.800933] sd 2:0:0:0: Attached scsi generic sg1 type 0
[ 3665.271188] sd 2:0:0:0: [sdb] 15448064 512-byte logical blocks: (7.91 GB/7.37 GiB)
[ 3665.273209] sd 2:0:0:0: [sdb] Write Protect is off
[ 3665.273221] sd 2:0:0:0: [sdb] Mode Sense: 23 00 00 00
[ 3665.275369] sd 2:0:0:0: [sdb] Write cache: disabled, read cache: disabled, doesn't support DPO or FUA
[ 3665.281893]  sdb: sdb1
[ 3665.287106] sd 2:0:0:0: [sdb] Attached SCSI removable disk
[ 3665.477414] FAT-fs (sdb1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.

My SD Sandisk:

[ 3714.947075] usb 1-8: new high-speed USB device number 10 using xhci_hcd
[ 3715.089689] usb 1-8: New USB device found, idVendor=058f, idProduct=6366
[ 3715.089702] usb 1-8: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 3715.089711] usb 1-8: Product: Flash Card Reader/Writer
[ 3715.089720] usb 1-8: Manufacturer: Generic
[ 3715.089729] usb 1-8: SerialNumber: 058F63666485
[ 3715.091139] usb-storage 1-8:1.0: USB Mass Storage device detected
[ 3715.092060] scsi host2: usb-storage 1-8:1.0
[ 3716.100600] scsi 2:0:0:0: Direct-Access     Multiple Card  Reader     1.00 PQ: 0 ANSI: 4
[ 3716.102396] sd 2:0:0:0: Attached scsi generic sg1 type 0
[ 3716.562378] sd 2:0:0:0: [sdb] 124735488 512-byte logical blocks: (63.9 GB/59.5 GiB)
[ 3716.564379] sd 2:0:0:0: [sdb] Write Protect is off
[ 3716.564390] sd 2:0:0:0: [sdb] Mode Sense: 23 00 00 00
[ 3716.566466] sd 2:0:0:0: [sdb] Write cache: disabled, read cache: disabled, doesn't support DPO or FUA
[ 3716.610675] sd 2:0:0:0: [sdb] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[ 3716.610686] sd 2:0:0:0: [sdb] tag#0 Sense Key : Not Ready [current] 
[ 3716.610706] sd 2:0:0:0: [sdb] tag#0 <<vendor>>ASC=0xff <<vendor>>ASCQ=0xff 
[ 3716.610716] sd 2:0:0:0: [sdb] tag#0 CDB: Read(10) 28 00 00 00 00 00 00 00 08 00
[ 3716.610721] print_req_error: I/O error, dev sdb, sector 0
[ 3716.610737] Buffer I/O error on dev sdb, logical block 0, async page read
[ 3716.611605] sd 2:0:0:0: [sdb] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[ 3716.611616] sd 2:0:0:0: [sdb] tag#0 Sense Key : Not Ready [current] 
[ 3716.611635] sd 2:0:0:0: [sdb] tag#0 <<vendor>>ASC=0xff <<vendor>>ASCQ=0xff 
[ 3716.611644] sd 2:0:0:0: [sdb] tag#0 CDB: Read(10) 28 00 00 00 00 00 00 00 08 00
[ 3716.611649] print_req_error: I/O error, dev sdb, sector 0
[ 3716.611659] Buffer I/O error on dev sdb, logical block 0, async page read
[ 3717.073412] sd 2:0:0:0: [sdb] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[ 3717.073427] sd 2:0:0:0: [sdb] tag#0 Sense Key : Unit Attention [current] 
[ 3717.073445] sd 2:0:0:0: [sdb] tag#0 Add. Sense: Not ready to ready change, medium may have changed
[ 3717.073458] sd 2:0:0:0: [sdb] tag#0 CDB: Read(10) 28 00 00 00 00 00 00 00 08 00
[ 3717.073466] print_req_error: I/O error, dev sdb, sector 0
[ 3717.073481] Buffer I/O error on dev sdb, logical block 0, async page read
[ 3717.073517] ldm_validate_partition_table(): Disk read failed.
[ 3717.073626] Dev sdb: unable to read RDB block 0
[ 3717.073742]  sdb: unable to read partition table
[ 3717.080857] sd 2:0:0:0: [sdb] Attached SCSI removable disk
[ 3717.100178]  sdb: sdb1 sdb2
[ 3717.149151] sd 2:0:0:0: [sdb] Unaligned partial completion (resid=64, sector_sz=512)
[ 3717.149165] sd 2:0:0:0: [sdb] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[ 3717.149175] sd 2:0:0:0: [sdb] tag#0 Sense Key : Not Ready [current] 
[ 3717.149193] sd 2:0:0:0: [sdb] tag#0 <<vendor>>ASC=0xff <<vendor>>ASCQ=0xff 
[ 3717.149203] sd 2:0:0:0: [sdb] tag#0 CDB: Read(10) 28 00 07 6f 43 f0 00 00 08 00
[ 3717.149208] print_req_error: I/O error, dev sdb, sector 124732400

Last edited by overkill22 (2018-06-14 13:34:25)

ohnonot · 2018-06-15 05:55:26

^ it looks like your father's card is OK, but your's is still getting the same i/o errors, doesn't it.

personally i think it's a load of BS, what sandisk wrote, just a very elaborate explanation for "our products break when you move them around too much between devices".

a general advice with formatting problems is to dd the device's first few MBs, a.k.a "nuke", then try again whatever didn't work.

overkill22 wrote:

OT: what's the deal with startpage? what's the difference with google?

proxied. no user specific data transmitted, no search bubble.

overkill22 · 2018-06-15 10:14:10

ohnonot wrote:

^ it looks like your father's card is OK, but your's is still getting the same i/o errors, doesn't it.
personally i think it's a load of BS, what sandisk wrote, just a very elaborate explanation for "our products break when you move them around too much between devices".
a general advice with formatting problems is to dd the device's first few MBs, a.k.a "nuke", then try again whatever didn't work.
overkill22 wrote:
OT: what's the deal with startpage? what's the difference with google?
proxied. no user specific data transmitted, no search bubble.

Father's SD card: yes should be ok, but I can't format even with dd or fdisk or tesdisk or gparted. What should I do? I used the command

sudo dd if=/dev/zero of=/dev/sdb bs=1M status=progress

but didn't work even fo my father's card. Is there another command to just target the first few MBs?

Sandisk explanations: I don't know, I start thinking the Android way to manage internal memory kind of sucks. Mine were Sandisk, but my father Samsung. And we didn't switch them at all, bought > inserted in the phone > formatted as internal memory. Maybe the fact that is encrypted stress too much the SD, in this case it could be a general problem that SD sucks in handling lots of I/O.

Startpage: I'll look into it, looks cool.

ohnonot · 2018-06-15 17:26:02

please explain "didn't work".
actual commands & their output.

overkill22 · 2018-06-25 21:12:25

ohnonot wrote:

please explain "didn't work".
actual commands & their output.

I wish I had an error message but I had nothing. The process completes successfully as if the SD card was formatted correctly. However, everything is still in the SD card, photos, documents, etc.

#21 2018-06-13 14:32:56

Re: Can't format SD card with anything - ADVANCED

#22 2018-06-13 15:01:48

Re: Can't format SD card with anything - ADVANCED

#23 2018-06-13 15:11:43

Re: Can't format SD card with anything - ADVANCED

#24 2018-06-13 17:14:02

Re: Can't format SD card with anything - ADVANCED

#25 2018-06-13 17:16:30

Re: Can't format SD card with anything - ADVANCED

#26 2018-06-13 21:26:45

Re: Can't format SD card with anything - ADVANCED

#27 2018-06-14 04:27:18

Re: Can't format SD card with anything - ADVANCED

#28 2018-06-14 09:08:23

Re: Can't format SD card with anything - ADVANCED

#29 2018-06-14 13:33:28

Re: Can't format SD card with anything - ADVANCED

#30 2018-06-15 05:55:26

Re: Can't format SD card with anything - ADVANCED

#31 2018-06-15 10:14:10

Re: Can't format SD card with anything - ADVANCED

#32 2018-06-15 17:26:02

Re: Can't format SD card with anything - ADVANCED

#33 2018-06-25 21:12:25

Re: Can't format SD card with anything - ADVANCED

Board footer