I have a HTC Desire Z Model A7272 with the microSD microSDHC SanDisk 8 GB Class 4.
CyanogenMod 7.0.3
After rooting and installing CyanogenMod 7.0.3, I went to Settings -> Storage -> Erase SD Card. Doing that showed two confirmation screens Erase SD Card -> Erase everything and then the notification bar said:
Code:
SD card safe to remove
Blank SD card
Opening the notification bar sais:
Code:
Blank SD card
SD Card blank or has unsupported file system
with the option Format SD card. Doing that, enters the circle again, displaying one after another:
Code:
SD card safe to remove
Blank SD card
SD Card blank or has unsupported file system
Same with Settings -> Storage -> Mount SD Card and Erase SD Card.
After Googling and Reading I booted ClockworkMod Recovery:
ClockworkMod Recovery 3.0.2.4
There I did mounts and storage -> mount /sdcard, which resulted in:
Code:
Error mounting /sdcard!
Same with mounts and storage -> format /sdcard:
Code:
Formatting /sdcard...
Error mounting /sdcard!
Skipping format...
The option advanced -> Partition SD Card only displays ext sizes until 4 GB, my card is 8 GB.
So I enter the shell:
Android Debug Bridge version 1.0.26 shell
VBusyBox v1.16.2androidfull
Boot Log sais:
Code:
# [I]dmesg[/I]
<6>[ 4.893951] mmc2: new high speed SDHC card at address e624
<6>[ 4.894866] mmcblk1: mmc2:e624 SU08G 7.40 GiB
<6>[ 4.895202] mmcblk1: p1
List the partition table:
Code:
# [I]fdisk -l /dev/block/mmcblk1[/I]
Disk /dev/block/mmcblk1: 7948 MB, 7948206080 bytes
256 heads, 63 sectors/track, 962 cylinders
Units = cylinders of 16128 * 512 = 8257536 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk1p1 * 1 963 7760896 c Win95 FAT32 (LBA)
Partition 1 has different physical/logical beginnings (non-Linux?):
phys=(1023, 255, 63) logical=(0, 32, 33)
Partition 1 has different physical/logical endings:
phys=(1023, 255, 63) logical=(962, 138, 10)
Trying to mount it by hand:
Code:
# [I]mount -v -t vfat /dev/block/mmcblk1p1 /mnt/sdcard[/I]
mount: mounting /dev/block/mmcblk1p1 on /mnt/sdcard failed: Invalid argument
System call trace of that:
Code:
# [I]strace mount -v -t vfat /dev/block/mmcblk1p1 /mnt/sdcard[/I]
stat64("/dev/block/mmcblk1p1", {st_mode=S_IFBLK|0600, st_rdev=makedev(179, 33), ...}) = 0
mount("/dev/block/mmcblk1p1", "/mnt/sdcard", "vfat", MS_VERBOSE, ""...) = -1 EINVAL (Invalid argument)
write(2, "mount: mounting /dev/block/mmcbl"..., 77mount: mounting /dev/block/mmcblk1p1 on /mnt/sdcard failed: Invalid argument
) = 77
mprotect(0x40008000, 4096, PROT_READ|PROT_WRITE) = 0
mprotect(0x40008000, 4096, PROT_READ) = 0
munmap(0x40008000, 4096) = 0
SYS_248(0xffffffff, 0x1000, 0xafd46300, 0xafd46300, 0xffffffff <unfinished ... exit status 255>
Unfortunately, the following programs I am used to by Linux are not available on my phone: blkid, fsck, mkfs.
I tried creating a new partition table with one primary partition over the entire size. Neither ClockworkMod Recovery nor CyanogenMod wanted to format or mount this. However, one of them changed the partition table back to what can be seen above.
Unfortunately, I can not currently put the card into another device to debug/format/mount it there.
Any idea how I can debug this further on my phone?
from the formating going on your phone, it seems to say skipped the format. i suggest to format the sd card on your computer to fat32. also if your computer detects errors on the sd card, you can debug them on your computer then reformat it. just remeber to back up your stuff
I didn't have another device. That was my problem.
So I dug one up (some Samsung, non-Android), put it in there, formatted it, put it back in mine and it worked!
Cool for problem solved, but I am still wondering what the cause of this was and how to fix it.
The partition table is still looking exactly the same:
Code:
# [I]fdisk -l /dev/block/mmcblk1[I]
Disk /dev/block/mmcblk1: 7948 MB, 7948206080 bytes
256 heads, 63 sectors/track, 962 cylinders
Units = cylinders of 16128 * 512 = 8257536 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk1p1 * 1 963 7760896 c Win95 FAT32 (LBA)
Partition 1 has different physical/logical beginnings (non-Linux?):
phys=(1023, 255, 63) logical=(0, 32, 33)
Partition 1 has different physical/logical endings:
phys=(1023, 255, 63) logical=(962, 138, 10)
So my questions remain:
1. Why were both CyanogenMod 7.0.3 and ClockworkMod Recovery 3.0.2.4 unable to format and/or mount the card? Where is the exact bug?
2. How to fix this software so we don't need another device?
ilf_ said:
I didn't have another device. That was my problem.
So I dug one up (some Samsung, non-Android), put it in there, formatted it, put it back in mine and it worked!
Cool for problem solved, but I am still wondering what the cause of this was and how to fix it.
The partition table is still looking exactly the same:
Code:
# [I]fdisk -l /dev/block/mmcblk1[I]
Disk /dev/block/mmcblk1: 7948 MB, 7948206080 bytes
256 heads, 63 sectors/track, 962 cylinders
Units = cylinders of 16128 * 512 = 8257536 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk1p1 * 1 963 7760896 c Win95 FAT32 (LBA)
Partition 1 has different physical/logical beginnings (non-Linux?):
phys=(1023, 255, 63) logical=(0, 32, 33)
Partition 1 has different physical/logical endings:
phys=(1023, 255, 63) logical=(962, 138, 10)
So my questions remain:
1. Why were both CyanogenMod 7.0.3 and ClockworkMod Recovery 3.0.2.4 unable to format and/or mount the card? Where is the exact bug?
2. How to fix this software so we don't need another device?
Click to expand...
Click to collapse
Did you try
#parted /dev/block/mmcblk1p1
in clockwork recovery?
I suggest getting a new card. Either of the cards in my signature are good, and PNY's 8GB Class 4 card is a good backup card.
Im having the same problem. I have an atrix. WHAT DO I DO
I'm having the same issue and have tried formatting through clockwork, the current rom i'm using, and windows. The sdcard still cannot be mounted. I've tried searching throught the forums and haven't found anything that helped. Hoping someone might have some suggestions other than buying a new sdcard...thanks
also, how do u type in commands while in recovery?
Related
I have a 32GB uSD Card Class 6. I partition in Recovery (RA) with 512 Swap, 1920 ext2 (or 3 or 4 tried all) and remaining FAT32. If I use the old 8GB Class 4 card with 100MB Swap, 512MB EXT4 and remainder FAT32, it works fine.
I get the error "Bad magic number in super-block while trying to open /dev/block/mmcblk0p2" when I try to upgrade from EXT2 to 4 and when I wipe DALVIK Cache. I tried mini partition with the same results. I have formatted card with NTFS and copied a 17GB movie file and it plays ok. Reformat it as above and back to same old error. Can copy files into FAT32 partition (<2gb files that is) and see them. Here is a RECOVERY.log of the partition, upgrade and then Dalvik cache wipe. Please help
- RECOVERY.log------------------------------
Model: SD 33333 (sd/mmc)
Disk /dev/block/mmcblk0: 32.7GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Number Start End Size Type File system Flags
1 512B 30.3GB 30.3GB primary fat32 lba
2 30.3GB 32.2GB 1920MB primary
3 32.2GB 32.7GB 512MB primary
script log is located @ /data/sdparted.log
Partitioning complete!
I:Set boot command ""
Upgrade ext2 to ext3
Press Trackball to confirm,
any other key to abort.
Upgrading ext2 to ext3 : .e2fsck 1.41.6 (30-May-2009)
e2fsck: Superblock invalid, trying backup blocks...
e2fsck: Bad magic number in super-block while trying to open /dev/block/mmcblk0p2
The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
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>
tune2fs: Bad magic number in super-block while trying to open /dev/block/mmcblk0p2
Couldn't find valid filesystem superblock.
tune2fs 1.41.6 (30-May-2009)
Ext upgrade complete!
I:Set boot command ""
Upgrade ext3 to ext4
Press Trackball to confirm,
any other key to abort.
Upgrading ext3 to ext4 : .tune2fs: Bad magic number in super-block while trying to open /dev/block/mmcblk0p2
Couldn't find valid filesystem superblock.
tune2fs 1.41.6 (30-May-2009)
e2fsck: Bad magic number in super-block while trying to open /dev/block/mmcblk0p2
/dev/block/mmcblk0p2:
The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
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>
Ext upgrade complete!
I:Set boot command ""
I:Set boot command ""
I:Set boot command ""
Wipe Dalvik-cache
Press Trackball to confirm,
any other key to abort.
Formatting DATA:dalvik-cache...
Formatting CACHE:dalvik-cache...
Formatting SDEXT:dalvik-cache...
E:Can't mount /dev/block/mmcblk0p2 (or /dev/block/mmcblk0)
(Invalid argument)
Error mounting /sd-ext/dalvik-cache!
Skipping format...
Dalvik-cache wipe complete!
-end-----------------------------------------------
when i run this command
/ # e2fsck -p /dev/block/mmcblk0p2
e2fsck -p /dev/block/mmcblk0p2
e2fsck: Bad magic number in super-block while trying to open /dev/block/mmcb
2
/dev/block/mmcblk0p2:
The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
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>
What does this all mean. I had a dream of a 32 GB storage with plenty of songs and media on my HTC Desire
__________________
HTC Desire PVT4
SD Card: 32GB Class 6
Espresso Sense HD RCS Touch v2.1 A2SD+
Recovery: RA AMON Recovery 2.0.0
Radio: 32.54.00.32U_5.14.05.17
HBOOT : 0.93.0001 S-OFF
Try formatting it with no swap. Set it to 0.
Ok, tried that same error. 0MB Swap, 512MB Ext2 and remainder FAT32. Partition FAT32 is first (viewable and RW in Windows) followed by 512MB EXT2.
I guess the question should be asked, does anyone run a HTC Desire GSM with a 32GB microSD Card, and if so what/how did the partitions set up. I suspect that the HTC Desire does not support 32GB cards. (I put the card in a HTC Desire HD and formatted under Clockworks 3.0.0.5). Formats ok, but get same error. Put a 16 GB card in CLASS 10 and get same errors. Put an 8GB microSD CLASS 4 and everything works fine.
-thanks anyway for the suggetion !
I have an Epic4G running
Code:
Marcusant Revival v1 ROM
Samurai 3.0.1 Kernel
ClockworkMod 5.0.2.7
ROM Manager Premium v4.8.0.6
I've installed
Code:
Titanium Backup Pro v4.6.5.1
App 2 SD Pro v2.42 (http://android.a0soft.com)
I've moved all movable apps to the /sdcard, except for "ROM Manager".
I've backed up "all apps & data" with TitaniumBackup.
This is all 'on' the current /sdcard, which is the stock, out-of-the-box 8GB card:
Code:
adb devices
List of devices attached
393071F74C1D00EC device
adb shell
#
# busybox df -h
Filesystem Size Used Available Use% Mounted on
tmpfs 181.4M 32.0K 181.3M 0% /dev
tmpfs 181.4M 0 181.4M 0% /mnt/asec
tmpfs 181.4M 0 181.4M 0% /mnt/obb
/dev/block/stl9 251.8M 211.9M 40.0M 84% /system
/dev/block/stl10 484.8M 332.8M 152.0M 69% /data
/dev/block/stl11 163.2M 112.0K 163.1M 0% /cache
df: /mnt/.lfs: Function not implemented
/dev/block/vold/179:1
14.7G 13.3G 1.4G 91% /mnt/sdcard
/dev/block/vold/179:1
14.7G 13.3G 1.4G 91% /mnt/secure/asec
/dev/block/dm-1 4.1M 2.6M 1.5M 64% /mnt/asec/com.hcom.android-1
/dev/block/dm-2 2.0M 108.0K 1.9M 5% /mnt/asec/com.HexPlus-1
...
/dev/block/dm-88 5.1M 3.2M 1.8M 64% /mnt/asec/com.amazon.kindle-1
# ls -a /mnt
.lfs
obb
asec
secure
sdcard
I've purchased a new 32GB Class10 sdcard.
I've formatted it @linux desktop to a map of:
Code:
/dev/sde1 -> 29.25 GB FAT23
/dev/sde2 -> 1.5 GB ext4
/dev/sde3 -> * (~62 MB) swap
checking,
Code:
fdisk -l /dev/sde
Disk /dev/sde: 32.0 GB, 32018268160 bytes
255 heads, 63 sectors/track, 3892 cylinders, total 62535680 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x000d58e8
Device Boot Start End Blocks Id System
/dev/sde1 2048 59248639 29623296 c W95 FAT32 (LBA)
/dev/sde2 59248640 62396415 1573888 83 Linux
/dev/sde3 62396416 62535679 69632 82 Linux swap / Solaris
I clearly need to move data from the 'old' sdcard to the 'new' one.
I've read a bunch of sources online, and they mention "/system/sd" directory, which I do *NOT* seem to have, and they fail to make any mention of "/mnt/asec", which I *DO* have ...
Since there's a different partition map, and I'm guessing a different directory structure that'll be used (?), what -- exactly -- needs to get copied to what?
The goal is to copy correctly/completely, swap in the new card, and boot successfully.
Better safe than sorry ...
Honestly, I just did an sdcard swap...and all I did; make a folder on my PC desktop, drag all files to folder from phone, unmount and insert new SD in phone, drag and drop files on new SD. No problems.
sent from my EPICally transmogrified EI22: Thunderhawk III- adrenaline injected, SUPERCHARGED
and how did you partition your new sdcard? single partition, FAT32?
[email protected] said:
and how did you partition your new sdcard? single partition, FAT32?
Click to expand...
Click to collapse
I didn't- just moved the files. However, it was just a couple of days before I Odined- went to EC05, rerooted, and then to EI22- so it may have been buggy and I never even had time to notice
- I considered repartition, but wanted to see what would happen if I just dropped the files. Everything seemed to have run smoothly for a couple of days, but like I said, I rerooted and moved to EI22 shortly after
> I didn't
Then that's likely a different case altogether. I'm specifically asking about what-goes-where? in the multiple-partition case.
Does anyone know what Android is doing to check the external SD card before producing the error that the SD card is damaged? I get that error after every reboot the card card is then fully functional (camera can write to it, file browsers can access it). I have reformatted the card in the phone and in Windows 7. Here is the output from fsck from a linux box:
[email protected]:/media$ sudo fsck -v /dev/sdb1
fsck from util-linux 2.19.1
dosfsck 3.0.9 (31 Jan 2010)
dosfsck 3.0.9, 31 Jan 2010, FAT32, LFN
Checking we can access the last sector of the filesystem
Boot sector contents:
System ID "MSDOS5.0"
Media byte 0xf8 (hard disk)
512 bytes per logical sector
32768 bytes per cluster
596 reserved sectors
First FAT starts at byte 305152 (sector 596)
2 FATs, 32 bit entries
1944576 bytes per FAT (= 3798 sectors)
Root directory start at cluster 2 (arbitrary size)
Data area starts at byte 4194304 (sector 8192)
486032 data clusters (15926296576 bytes)
63 sectors/track, 255 heads
2048 hidden sectors
31114240 sectors total
Checking for unused clusters.
Checking free cluster summary.
/dev/sdb1: 1 files, 2/486032 clusters
Time to reflash the ROM maybe? (Diet ICS) I'd just like to know what command is being run to trigger the error. It is a 16GB card formated as fat32
ok, while I was spinning my wheels someone else had posted in the Diet ICS thread that this is apparently a known issue with the toggles being used.
I had to make sure my card was formatted to FAT32 for it to recognize my card. try that.
MentalDragon said:
I had to make sure my card was formatted to FAT32 for it to recognize my card. try that.
Click to expand...
Click to collapse
In this case it was specific to the ROM and reflashing the theme fixed it. While I was trying to figure out what was going on and ended up posting this question, someone else was already posting the fix.
Hi everybody..
I have a strange and boring issue with my micro SD card that I use with my smartphone.. Today, while I was reading a PDF book the phone freezes it self: the only solution was to reboot it!
But.. WOW; 'till that moment the phone doesn't recognize my micro-SD any more!! It doesn't give warnings or messages.. nothing.. the only problem is that my SD card is inserted but the phone won't read it..
I mount the micro sd into my Slackware laptop and it still have partitions but they are all read-only! Every thing I try to do (copy files, move, delete etc) fails with a read-only warning!
So I try to format all from the scratch.. but it is not possible!! It doesn't let me format my SD for the same reason: read-only file system!!
WOW!! It's absurd!!
What can I do? is there a solution for that?
I tried to use fsck, badblocks, mkfs but nothing helped!
fdisk -l output
Code:
Disk /dev/sdb: 15.9 GB, 15918432256 bytes
255 heads, 63 sectors/track, 1935 cylinders, total 31090688 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00031a4f
Device Boot Start End Blocks Id System
/dev/sdb1 1 29027343 14513671+ c W95 FAT32 (LBA)
/dev/sdb2 29027344 31027343 1000000 83 Linux
/dev/sdb3 31027344 31090687 31672 82 Linux swap
I have a FAT partition for data, a ext2 one used with Link2sd and a swap one.
This is the result I got when trying to format the second partition..
Code:
# mkfs.ext2 /dev/sdb2
mke2fs 1.41.14 (22-Dec-2010)
/dev/sdb2: Read-only file system while setting up superblock
The same to me. Wish a help!! Thanks
The SD card was removed while the device was running.
The device is running CM 7.2 and the SD card was partitioned to extend the internal memory.
Now, everything is out of whack.
The call log is gone, the texts are gone, I have no contacts, I have no favorites.
The widgets are gone, the home screen icons are gone.
Actually it'd be better to say what's still there: The apps themselves and some file content (pictures, videos, downloads) are there.
How do I rectify this and safe my data. I wouldn't mind migrating it to a new device as I have a new device.
Please advice if you can
what method did you use to partition your card ? some leave user data on internal memory some move that too on to external. i don't know if there's any PC software that can see your 2nd partition if you put your SDcard into a card reader on a PC for backing up.
3mel said:
what method did you use to partition your card ? some leave user data on internal memory some move that too on to external.
Click to expand...
Click to collapse
I don't know for sure but I think it was Data2SD from the package Data2sdV2withA2sdremover_by_jikantaru.zip
It is a 2 GB SD card and the phone shows an internal storage of 473 MB and 1,39 GB on the SD card.
3mel said:
i don't know if there's any PC software that can see your 2nd partition if you put your SDcard into a card reader on a PC for backing up.
Click to expand...
Click to collapse
I inserted it in a Ubuntu computer and got some output.
This is the relevant output from Ubuntu
Code:
[email protected]:~$ df -h
Filesystem Size Used Avail Use% Mounted on
/dev/mmcblk0p1 1.4G 1.4G 21M 99% /media/ubuntu/F031-5199
/dev/mmcblk0p2 465M 393M 73M 85% /media/ubuntu/userdata
Code:
[email protected]:~$ sudo fdisk -l
Disk /dev/mmcblk0: 1.9 GiB, 2002780160 bytes, 3911680 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x000ccb88
Device Boot Start End Sectors Size Id Type
/dev/mmcblk0p1 1 2912109 2912109 1.4G c W95 FAT32 (LBA)
/dev/mmcblk0p2 2912256 3911679 999424 488M 83 Linux
Code:
[email protected]:~$ sudo ls /media/ubuntu/F031-5199
AI Factory Stats LOST.DIR Safety Guide
Android media ScanToPDF_Free
aScreenshot miniclipId.txt SmsContactsBackup
busybox-stericson My Documents svox
clockworkmod My files System Volume Information
data Notifications TitaniumBackup
data2whateverlog.txt Pictures tmp
DCIM Quick Start Guide toolbox-stericson
download reboot-stericson User Manual
ezPDFReader Ringtones
kindle rosie_scroll
[email protected]:~$ sudo tail /media/ubuntu/F031-5199/data
Code:
[email protected]:~$ sudo lsblk -f
NAME FSTYPE LABEL UUID MOUNTPOINT
mmcblk0
├─mmcblk0p1 vfat F031-5199 /media/ubu
└─mmcblk0p2 ext3 userdata 6f6684d8-78c2-40b6-ae72-d9b089f623a1
Both partitions are still there and accessible. I did run fsck but it did not help with the lost thing (texts, etc.)
somebody else had trouble with that method a cm10.1 thread. I would have said try flashing it again but I don't know that method...