• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Unable to mount, micro SD memory card

eosfour

Lurker
Hello,
i just remove my sdcard from my android phone (lollipop), iput another sd card inside to format, i make the format,
then i put back the original sd card ( samsung 16G ), but the phone refuse to mount it, and use it as internal memory, except if i format it .

the point is that i canot mount my sdcard not my pc (linux debian 8), so to get my data. the reason is an I/O error, and fdisk, dd, refuse to work with the sdcard. My OS cant report any partitions in card, and any try to read is an IO Error.

here is a snaphost of hdparm :

⟰ ohost3 ⚇ root
pts/0:0 ~ ➫ hdparm /dev/sdb

/dev/sdb:
SG_IO: bad/missing sense data, sb[]: 70 00 05 00 00 00 00 0a 00 00 00 00 20 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
multcount = 0 (off)
readonly = 0 (off)
readahead = 256 (on)
geometry = 15193/64/32, sectors = 31116288, start = 0


⟰ ohost3 ⚇ root
pts/0:0 ~ ➫ hdparm -I /dev/sdb
/dev/sdb:
SG_IO: bad/missing sense data, sb[]: 70 00 05 00 00 00 00 0a 00 00 00 00 20 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

ATA device, with non-removable media
Standards:
Likely used: 1
Configuration:
soft sectored
head switch time > 15us
fixed drive
disk xfer rate <= 5Mbs
disk xfer rate > 5Mbs, <= 10Mbs
data strobe offset option
format speed tolerance gap reqd
Logical max current
cylinders 21314 0
heads 0 0
sectors/track 1 0
--
bytes/track: 512 bytes/sector: 0
Logical/Physical Sector size: 512 bytes
device size with M = 1024*1024: 0 MBytes
device size with M = 1000*1000: 0 MBytes
cache/buffer size = unknown
Capabilities:
IORDY not likely
Cannot perform double-word IO
R/W multiple sector transfer: not supported
DMA: not supported
PIO: pio0

any sugestion ?
 
Hello,
i just remove my sdcard from my android phone (lollipop), iput another sd card inside to format, i make the format,
then i put back the original sd card ( samsung 16G ), but the phone refuse to mount it, and use it as internal memory, except if i format it .

the point is that i canot mount my sdcard not my pc (linux debian 8), .....

I'm a little confused on what could be a minor contradiction. You refer to your phone running Lollipop and wanting to use your microSD card as 'internal', but adoptable storage wasn't implemented until Marshmallow. So either your phone is running a newer version than Lollipop or your card cannot currently be formatted as 'internal' (only as 'portable').
If it is running Marshmallow or newer, and if you had formatted that original card to be 'internal', than you won't be able to access the contents of the card no matter what OS your computer is running, as when formatted as 'internal' the card gets changed from FAT to ext4 with the added factor being it's also encrypted (the encryption key itself tying the card to your phone specifically).

Also, did you use hdparm with any other flags besides -I ? If so that could be why that original card isn't recognized properly by your phone when you put it back in.
 
..., So either your phone is running a newer version than Lollipop or your card cannot currently be formatted as 'internal' (only as 'portable').
..., with the added factor being it's also encrypted (the encryption key itself tying the card to your phone specifically).

i think your right about the version of the android, its newer, cause i have 2 options
Internal
Portable

so is ext4 encrypted, right ?
plus when it was the other card ( i wanted to format,) i press forget, and i think the forget is refer to encryption keys, so,
i suicide i think,
right ?


and why i cant format with linux ?
and from windows, only windows 10, accept to format the disk ?


Also, did you use hdparm with any other flags besides -I ?
an example ?
 
Last edited:
so is ext4 encrypted, right ?
As is, no ext4 is not. Like any typical file system, encryption is something that is either left out or implemented.

and why i cant format with linux ?
and from windows, only windows 10, accept to format the disk ?
Not knowing just how you were attempting to use to format the card it's hard to determine just what was the problem, but utilities such as gparted are capable of manipulating a number of different file system types:
https://en.wikipedia.org/wiki/GParted
As for Windows, out of the box it will be limited only to media set up using NTFS and FAT variants. The default file system on a microSD card is FAT-based so cards are typically handled as is, but once it involves any other file system (such as. ext, or Apple's HFS+/APFS) than you need to install a third-party utility to use it. Again, on your Note a microSD card formatted as 'portable' will remain using FAT, but if formatted as 'internal' will be using ext.
Using hdparm does need to be done with care, if you use one of its flags incorrectly that can change things. ('man hdparm' is your friend)
 
svim, first of all thank you for your answers and your interest. there 're very help full to me

i didnt got it
1. the fs in the card is an linux ext filesytem ?
2. is this filesystem encrypted ?


Is the 'Internal Storage' format somewhere documented by google?


ABOUT FORMAT:
---------------------------------
i have tried allready theese programs but not,
so i reach dd, o a low level util of linux , it fails,
so i reach hdparm,

here what i did, (/dev/sdc is my SD card):
-----------------------------------------
pts/0:0 ~ ➫ mount /dev/sdc x
-----------------------------------------
Code:
mount: wrong fs type, bad option, bad superblock on /dev/sdc,
       missing codepage or helper program, or other error
-----------------------------------------
pts/0:0 ~ ➫ dmesg | tail
-----------------------------------------
Code:
[146160.373662] sd 2:0:0:0: [sdc] tag#0 CDB: Read(10) 28 00 00 00 00 02 00 00 02 00
[146160.373664] blk_update_request: critical medium error, dev sdc, sector 2
[146160.373717] EXT4-fs (sdc): unable to read superblock
[146160.382662] sd 2:0:0:0: [sdc] Unaligned partial completion (resid=640, sector_sz=512)
[146160.382677] sd 2:0:0:0: [sdc] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[146160.382680] sd 2:0:0:0: [sdc] tag#0 Sense Key : Medium Error [current]
[146160.382683] sd 2:0:0:0: [sdc] tag#0 Add. Sense: Unrecovered read error
[146160.382687] sd 2:0:0:0: [sdc] tag#0 CDB: Read(10) 28 00 00 00 00 02 00 00 02 00
[146160.382690] blk_update_request: critical medium error, dev sdc, sector 2
[146160.382724] EXT4-fs (sdc): unable to read superblock
-----------------------------------------
pts/0:0 ~ ➫ dd if=/dev/sdc
-----------------------------------------
Code:
dd: error reading ‘/dev/sdc’: Input/output error
0+0 records in
0+0 records out
0 bytes (0 B) copied, 0.0150425 s, 0.0 kB/s
-----------------------------------------
pts/0:0 ~ ➫ fdisk -l /dev/sdc
-----------------------------------------
Code:
fdisk: cannot open /dev/sdc: Input/output error
-----------------------------------------
pts/0:0 ~ ➫ hdparm /dev/sdc
-----------------------------------------
Code:
/dev/sdc:
SG_IO: bad/missing sense data, sb[]:  70 00 05 00 00 00 00 0a 00 00 00 00 20 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
 multcount     =  0 (off)
 readonly      =  0 (off)
 readahead     = 256 (on)
 geometry      = 15193/64/32, sectors = 31116288, start = 0

that means that a reading error happen

https://superuser.com/questions/1213715/hdparm-error-sg-io-bad-missing-sense-data

Code:
The sense data given reads:
70  response code=Current information (about the error etc.)
00
05  sense code=Illegal Request
00 00 00 00 (not valid)
0a  additional 10 bytes
04 51 60 00  (command specific)
21 04 additional sense code=Unaligned Write Command
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

So the error is "Illegal Request, Unaligned Write Command".
,
(for read realy strange ;) )

so anyway in an android phone, or windows pc, i can format the drive,
but i cannot read, even access the card, beyond any filesystem or data it is
This is strange, i have a debian 8 OS, fully updated, in year 2018 (happy new year),
this make no sense.
The sd card, is 100% ,undamage and valid
 
Last edited:
Back
Top Bottom