Hi everyone,
I have 16GB ADATA microSD card. After reformating through the recovery image to ext2,swapm and fat 14GB i used apps2sd for a while now. Today i wanted to wip my phone and all data on the microsd, so booted up recovery image and used Part SD to only fat32. I wanted to use the whole 16GB as a Fat32 drive again. But then I only got 14GB recognized in windows.
So i Tried to reformat again to swap,ext2 and Fat 12GB. But after trying to format back to 16GB FAT32 i lost another 2GB. I cant get the card to work in Windows anymore the only way i can access is through ADB.
Can someone help me to get my 16GB back?
j_love
update: i get the following when using parted
/dev/block # parted mmcblk0 print
parted mmcblk0 print
Model: SD SD (sd/mmc)
Disk /dev/block/mmcblk0: 12.0GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Number Start End Size Type File system Flags
1 32.3kB 12.0GB 12.0GB primary fat32 lba
What is the output of
Code:
parted -l
parted -l doesnt give me any output.
/ # parted -l
parted -l
/ #
Sounds like you have a corrupt partition table on your card. It's probably best to delete all the partitions on this card and start over BUT you should use a decent partitioning tool. Without meaning to be rude, it sounds like you are using Windows' built in (i.e. very basic) drive formatting tools and that you probably aren't that familiar with using parted on the command line. I would recommend using gparted, a graphical tool. You can use this either from a USB key http://gparted.sourceforge.net/liveusb.php or an Ubuntu live cd (appears as 'partition editor'). I find that disc partitioning is a great deal easier with graphics, i.e. in this case you can see what you are doing.
Thanks but I already used the liveCD of gparted. The main problem here is that my SDCARD is not recognized in Windows or in Linux. Also tryed Ubuntu and knoppix. I am not very familiar with linux but have some experience with command line tools.
The only way i can access the SDCARD is via adb on my Hero. Do you know any commands i could test? I already wiped the partition table and tried to make new partitions. But im stuck at 12GB.
The thing is that in Linux, you don't mount a device, you mount a file system. In this case that would translate to partitions (there are other cases but they are not relevant here). I would ask: if you cannot 'see' the card in windows or in linux and parted -l gives no output, where is this 12GB figure coming from?
Windows typically won't show a drive in 'my computer' if it doesn't recognise the partition format so you won't see any ext2 or ext3 partitions. You won't get any pop-ups on your desktop for unformatted space in Ubuntu either. Please could you confirm that you have tried the following:
In Ubuntu connect phone via USB to PC via (on phone) 'USB/ USB connected/ mount'. This won't affect adb.
Bring up Gparted and do 'gparted/refresh devices'
Select '/dev/sdb' or whatever your memory card appears as there- your main hard drive will be shown by default.
Tell us what you see now
I am attaching a screenshot of my SD card in my phone seen like this. It shows as sdc because I have two hard drives on my PC
ok done that. I got the following
/dev/sdf1 11.21GiB
/dev/sdf1 fat32 /media/disk 11.21GiB 11.26MiB 11.20GiB lba
/dev/sdf1 11.21GiB
/dev/sdf1 fat32 /media/disk 11.21GiB 11.26MiB 11.20GiB lba
Click to expand...
Click to collapse
If I understand correctly the above appears to show a single FAT32 partition on this device of 11.21GiB with 11.26MiB used. My suggestion is to use Gparted to delete all the partitions on this card (don't forget to hit 'apply') and then see how much unformatted space you have. Bear in mind that you must unmount your filesystem (mounting/unmounting can be done within gparted) before playing around with any of the partitions on it. You can then create new partitions on the card (again, don't forget to 'apply changes'). You will likely have to reboot your phone to seem them there.
Does this work?
ok. I can delete create resize partitions but the diskspace is still 11.21GiB
If you delete all the partitions on the device, how much 'unallocated space do you have after 'apply changes'? when you unmount and the remount the card?
unallocated space is 11.21GiB
okay try creating a single new partition on the card and then using the 'check' option in gparted. What happens then?
Created a ext2 partition and checked it. Check was fine without errors but space is still 11.21GiB
Okay, assuming your card is still on /dev/sdf1 please try the following:
Code:
sudo fdisk /dev/sdf
This enters the fdisk shell. Then type
Code:
p
and paste the output here. You can exit fdisk with the command
Code:
quit
Got the following output
[email protected]:~$ sudo fdisk /dev/sdf
The number of cylinders for this disk is set to 1463.
There is nothing wrong with that, but this is larger than 1024,
and could in certain setups cause problems with:
1) software that runs at boot time (e.g., old versions of LILO)
2) booting and partitioning software from other OSs
(e.g., DOS FDISK, OS/2 FDISK)
Command (m for help): p
Disk /dev/sdf: 12.0 GB, 12035555328 bytes
255 heads, 63 sectors/track, 1463 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x00065e4e
Device Boot Start End Blocks Id System
/dev/sdf1 1 1463 11751516 83 Linux
Command (m for help): quit
does anyone have the output of fdisk->p of there ADATA 16GB microSD CARD???
I tried to change the clyinders but need the correct value
Code:
Disk /dev/sdf: 12.0 GB, 12035555328 bytes
255 heads, 63 sectors/track, 1463 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x00065e4e
Device Boot Start End Blocks Id System
/dev/sdf1 1 1463 11751516 83 Linux
Click to expand...
Click to collapse
Well that's interesting. This appears to show a single ext3 partition toward the end of the card (unless I've got this completely wrong). What do you get for
Code:
parted
print
with the same partion(s)?
for reference on my 8GB card I get (on laptop):
Code:
sudo fdisk
p
gives
Code:
Disk /dev/sdb: 7948 MB, 7948206080 bytes
255 heads, 63 sectors/track, 966 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x000beb03
Device Boot Start End Blocks Id System
/dev/sdb1 * 1 902 7245283+ c W95 FAT32 (LBA)
/dev/sdb2 903 966 514080 83 Linux
and
Code:
sudo parted /dev/sdb
print
gives
Code:
Model: HTC Android Phone (scsi)
Disk /dev/sdb: 7948MB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Number Start End Size Type File system Flags
1 32.3kB 7419MB 7419MB primary fat32 boot, lba
2 7419MB 7946MB 526MB primary ext2
Im Not at home right now but will post the Output tomorrow.
But I think you got it wrong. The start cylinder is 1 and the end is at 1463.
I can use fdisk to manipulate the cylinders but the size stays the same. This is really a big problem. There ar3 more users on the net with similar problems but without a solution. Hope we can get this back to normal.
I get the following for :
[email protected]:/# parted /dev/sdf
GNU Parted 1.8.8
Using /dev/sdf
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) print
Model: SD/MMC Card Reader (scsi)
Disk /dev/sdf: 12.0GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Number Start End Size Type File system Flags
1 32.3kB 12.0GB 12.0GB primary fat32 lba
(parted)
(parted) quit
and the following for
[email protected]:/# fdisk /dev/sdf
The number of cylinders for this disk is set to 1463.
There is nothing wrong with that, but this is larger than 1024,
and could in certain setups cause problems with:
1) software that runs at boot time (e.g., old versions of LILO)
2) booting and partitioning software from other OSs
(e.g., DOS FDISK, OS/2 FDISK)
Command (m for help): p
Disk /dev/sdf: 12.0 GB, 12035555328 bytes
255 heads, 63 sectors/track, 1463 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x0005c05a
Device Boot Start End Blocks Id System
/dev/sdf1 1 1464 11753440 c W95 FAT32 (LBA)
Cheers, any chance of posting that again and using the 'code' tags in the message editor? It's a bit hard to read in the body of your post like this
thanks
Figured I would post this for information sharing purpose.
I have been doing some device read timings on internal memory / sdcard file systems.
My setup:
- internal flash -> standard
- SD card with 1 VFAT partition
- SD card with 1 ext4 partition
Below measured read timings (measured with "hdparm -t"):
1) internal flash
bash-3.2# /data/hdparm -t /dev/block/mmcblk0p25
/dev/block/mmcblk0p25:
Timing buffered disk reads: 90 MB in 3.01 seconds = 29.87 MB/sec
2) VFAT on sdcard partition
bash-3.2# /data/hdparm -t /dev/block/mmcblk1p1
/dev/block/mmcblk1p1:
Timing buffered disk reads: 22 MB in 3.07 seconds = 7.17 MB/sec
3) ext4 on sdcard partition
bash-3.2# /data/hdparm -t /dev/block/mmcblk1p2
/dev/block/mmcblk1p2:
Timing buffered disk reads: 28 MB in 3.03 seconds = 9.24 MB/sec
Clear where you have to store your data if you want high read throughput (and not surprising of course).
Note: "hdparm" compiled for arm from original source code.
Readahead = 8192 in all cases.
There is an issue with my SDcard, I don't know how it happened, I did nothing special on it.
It appears as unformatted BUT, I know that the data is still there because the CWM manages to browse files if I get into the menu "install zip from /sdcard1", but it can't see anything if I try a "restore from sdcard1"...
Weird huh ?
So I have an ubuntu build and I'd like to try to repair the "masterboot" with your help
I never did this before so I don't really know what I need, SDCard is 32 GB class 10.
When I plug my phone from CWM and enable the mount the SDcard on usb I got this error message :
Error mounting: mount: /dev/sdb1: can't read superblock
Here is the result of the "fdisk -l" command :
Code:
Disk /dev/sdb: 32.0 GB, 32018268160 bytes
32 heads, 63 sectors/track, 31019 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: 0x4d544f4f
Device Boot Start End Blocks Id System
/dev/sdb1 2048 62535679 31266816 b W95 FAT32
Which actually looks weird, I thought that my sdcard were ext4 formated, well but I am not 100% sure about that...
Here the result of the command "fsck -y /dev/sdb1"
Code:
fsck from util-linux 2.20.1
dosfsck 3.0.12, 29 Oct 2011, FAT32, LFN
/
Contains a free cluster (2). Assuming EOF.
FAT32 root dir starts with a bad cluster!
What else can I do ?
Ok great...
Thanks anyway...
For information, I managed to backup data from the SDcard using testdisk, then using again testdisk I tried a repair, and it actually rewrote the superblock and the card is alive again without wiping
When trying to push new files to my LG G3 to fix the issue outlined here:
http://forum.xda-developers.com/showthread.php?t=2582142&page=178
Basically, can't get to recovery, or download and won't boot.
Terminal returns this instead of list of .img files:
ls /dev/sd *
TERMINAL RESPONSE: / dev / sda / dev / sda1 / dev / sda2 / dev / sda3
Partition table scan:
MBR: MBR only
BSD: not present
APM: not present
GPT: not present
************************************************** *****************************************
Found invalid GPT and MBR valid; Converting MBR to GPT format in memory.
************************************************** *****************************************
Disk /dev/sda: 625142448 sectors, 298.1 GiB
Logical sector size: 512 bytes
Disk identifier (GUID): 4746570D-B91E-4A91-917C-D94BCEBD34F3
Partitions table holds up to 128 entries
First usable sector in 34, last usable sector is 625142414
Partitions will be aligned on 2048-sector boundaries
Total free space is 310512237 sectors (148.1 GiB)
Number Start (sector) End (sector) Size Code Name
1 2048 52430847 25.0 GiB 0700 Linux data
2 52430848 314632191 125.0 GiB 0700 Linux data
^^^^ here is where the list of img files and their respective locations should be according to the guide. However, it does not show.
Any ideas?
Howdy. Just a question: if I select "use as internal memory" for my 128 GB SD card I inserted in my Nokia 1, does that mean I won't be able to access the said SD card if I try to plug the Nokia 1 to a PC?
Jem2291 said:
Howdy. Just a question: if I select "use as internal memory" for my 128 GB SD card I inserted in my Nokia 1, does that mean I won't be able to access the said SD card if I try to plug the Nokia 1 to a PC?
Click to expand...
Click to collapse
Hi,
I've used an 8 Gig SanDisk MicroSD card as internal memory on my Nokia 1.
The short answer to your question is no, probably not. at least not without a bit of effort.
I just plugged the SD card into a Linux box, which give me the below data
Code:
[[email protected] ~]$ sudo fdisk -l /dev/sdc
Disk /dev/sdc: 7.4 GiB, 7948206080 bytes, 15523840 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: gpt
Disk identifier: 98FA1F61-0482-4F31-A074-73550CC9B369
Device Start End Sectors Size Type
/dev/sdc1 2048 34815 32768 16M unknown
/dev/sdc2 34816 15523806 15488991 7.4G unknown
[[email protected] ~]$
[[email protected] ~]$
[[email protected] ~]$
[[email protected] ~]$ sudo gdisk -l /dev/sdc
GPT fdisk (gdisk) version 1.0.3
Partition table scan:
MBR: protective
BSD: not present
APM: not present
GPT: present
Found valid GPT with protective MBR; using GPT.
Disk /dev/sdc: 15523840 sectors, 7.4 GiB
Model: USB3.0 CRW -SD
Sector size (logical/physical): 512/512 bytes
Disk identifier (GUID): 98FA1F61-0482-4F31-A074-73550CC9B369
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 15523806
Partitions will be aligned on 2048-sector boundaries
Total free space is 2014 sectors (1007.0 KiB)
Number Start (sector) End (sector) Size Code Name
1 2048 34815 16.0 MiB FFFF android_meta
2 34816 15523806 7.4 GiB FFFF android_expand
When I plugged it into one of my Win10 boxes and it just offered to format it for me.
I'm not sure what file system is in use as it was reported as unknown. You'll need to figure out what file system is in use and install whatever tools your PC OS needs to work with that file system.