Related
hi,
i made partitions by using clockwork 3.0, i select 1 gb when it ask first, and 512 mb for swap. However, i dont know if this 1 gb partition is ext2 or ext3 or somehing else...
how can i see my sd card partitions...?
thanks....
polatkanfatih said:
hi,
i made partitions by using clockwork 3.0, i select 1 gb when it ask first, and 512 mb for swap. However, i dont know if this 1 gb partition is ext2 or ext3 or somehing else...
how can i see my sd card partitions...?
thanks....
Click to expand...
Click to collapse
Hi polatkanfatih,
You can't directly access the ext2 partition in Windows. Basically ext2 is a linux partiton. But still there are some 3rd party softwares available in the market which adds ext2 abilities to windows Operating System.
As per what you have written, i understood that you used Clockwork 3.0 for partitioning your SD card.Personally i don't know about clockwire.
Instead i'm using ''MiniTool Partition Wizard Home Edition 5.2'' which you can download for free from the MiniTool website.The software is pretty easy to use.With this software you can see the partitons you have created(including ext2).You can't access the files inside the partion, but you can format any partition using MiniTool.
Hope this helps........
that program doesnt make that work.
i need some adb code or somthing else to see how my sd card partitioned, how many partition are there and their sizes?
have you tried typing
Code:
mount
in terminal emulator or adb shell? That should give you a listing of all mounted partitions...
i made it with 'parted' adb command.
thanks..
i didn't undestand but still reading
A510+Link2sd+EXT3 2nd partition PROJECT
hi,
my project is to migrate all apps on a 2nd partition in my SDHC32GB-ultra sandisk
CWM recovery as the option to partition it but its not fully operational
i have a HTC HD2 on CM10 JB1.2 and 5.0.2.6 CWM, all apps are on the SD to free internal memory
my project is to view if the tablet is much more efficient with app on the SD wich is very quick and avoid space bugs...
this is beta project so i will add a tutorial and update it in time
1) create partition on SD for mine 1 swap 32mb 1 EXT3 2048Mb and all available in fat32 for storage
2) i used my HD2 for doing this perhaps another soft permit to do this as acronis disk director
3)insert my SD on the tablet, install link2sd with google play
4)create scripts with EXT3, not EXT4, it is buggy(searching why)
5)reboot
6)restoring apps with Titanium backup
7)enable link2sd auto link BUT DISABLE the dalvik file DEX to migrate on SD it seems buggy and apps are disabled if doing it(searching why)
8a)select multiple app and do mass processing to move them to create link
8b) you will see all apps installed linked to the EXT3 2nd partition
9) test it and report if table is quicker than previously state
not to blame me its a beta project never tested
regards
edit 7)enable link2sd auto link on all 3 settings
I get the hd2 too. Good luck for jour project
kiteman44 said:
I get the hd2 too. Good luck for jour project
Click to expand...
Click to collapse
thanx
it seems fully operationnal i tried all my apps and all runs as previously, much more efficient seems the tablet
no bad operations at this moment, i hope another mate will try it seems very good for the future
but i suppose performances are due to my SDHC class 10
Hi,
3 days of use, no buggs, more reactive tablet, it seems a good way to store apps on EXT3 SD partition for space in internal memory
and performances, but keep in mind to have a good quality SD card as class10
if you can do it i would recommend a this moment
Hi All
I'm looking to install this ROM: http://forum.xda-developers.com/showthread.php?t=2234221 on to my galaxy ace and have a question about formatting the SD card for it.
It talks about ext-4 partition and I was wondering what size to format the partition if using an 8gb card?
I was thinking - 1gb for the ext-4 and the rest for fat32?
halp please
What class is your sdcard? Are you planning to use int2sd?
Wysłane z mojego HTC Desire za pomocą Tapatalk 2
pamtayls said:
Hi All
I'm looking to install this ROM: http://forum.xda-developers.com/showthread.php?t=2234221 on to my galaxy ace and have a question about formatting the SD card for it.
It talks about ext-4 partition and I was wondering what size to format the partition if using an 8gb card?
I was thinking - 1gb for the ext-4 and the rest for fat32?
Click to expand...
Click to collapse
You must used the Fire Kernel because you don't have a 4Ext partition
and with Swap kernel and a Sdcard Class 6, you need a 4Ext partition.
So finally, it will depend of the choice of your kernel, and the better choice if you use the Swap kernel, it's to format all in 4Ext
And if you want an another answer, go to post here, you can do without problem
- Galaxy Ace S5830i Q&A, Help & Troubleshooting
or here: Galaxy Ace S5830 Q&A, Help & Troubleshooting
philos64 said:
You must used the Fire Kernel because you don't have a 4Ext partition
and with Swap kernel and a Sdcard Class 6, you need a 4Ext partition.
So finally, it will depend of the choice of your kernel, and the better choice if you use the Swap kernel, it's to format all in 4Ext
Click to expand...
Click to collapse
I am going to get a class 10 8gb card this weekend. the swap kernel is what I was going to use.
Why should I format the whole card in 4ext? If I do that, I won't be able to add files from my windows 7 PC will I??? I just don't know much about ext4. I do store some music and stuff on it.
Thanks so much for your help
pamtayls said:
I am going to get a class 10 8gb card this weekend. the swap kernel is what I was going to use.
Why should I format the whole card in 4ext? If I do that, I won't be able to add files from my windows 7 PC will I??? I just don't know much about ext4. I do store some music and stuff on it.
Thanks so much for your help
Click to expand...
Click to collapse
Which recovery do you use ?
I wrote a mistake about to format whole sdard to 4Ext
1 - You must have 1 Fat32 partition and 1 EXT4 partition on your sdcard
2 - If you rather use a computer for creating and formatting partitions keep in mind that both partitions must be primary partitions (not logical)
3 - The recommended size of your EXT4 partition is depending on how many roms and apps you are going to install.. 512M is the minimal size
Go to one of the links that I've wrote above and sent your question.
philos64 said:
Which recovery do you use ?
I wrote a mistake about to format whole sdard to 4Ext
1 - You must have 1 Fat32 partition and 1 EXT4 partition on your sdcard
2 - If you rather use a computer for creating and formatting partitions keep in mind that both partitions must be primary partitions (not logical)
3 - The recommended size of your EXT4 partition is depending on how many roms and apps you are going to install.. 512M is the minimal size
Go to one of the links that I've wrote above and sent your question.
Click to expand...
Click to collapse
Thanks, I didn't see your links in the first post. Will go check them out. at the moment I have the base CM7 ROM on the phone if that helps with which recovery I use.
again thanks heaps!!! and I will go to those links now
Hi my wonder is "can i use ext4 format for my SanDisk 64GB sdxc class 10 ?"to make it as a storage memory for miusc , images and videos. Or should i use the ntfs or exfat or fat32.
With thanks
Sent from my GT-N7100 using XDA Premium 4 mobile app
hi
deutsh said:
Hi my wonder is "can i use ext4 format for my SanDisk 64GB sdxc class 10 ?"to make it as a storage memory for miusc , images and videos. Or should i use the ntfs or exfat or fat32.
With thanks
Sent from my GT-N7100 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Hi,
Fat32 is universal partition for your music, ,video etc....
ext3 ext4 are used for android/unix/linux application storage...
be careful while partitioning you SD card...
read it before executing partiotion....
""forums.androidcentral.com/general-help-how/85809-tutorial-everything-you-wanted-know-about-app2sd-ext3-ext4-partitions.html[/url]"
-rkk
rkk253755 said:
Hi,
Fat32 is universal partition for your music, ,video etc....
ext3 ext4 are used for android/unix/linux application storage...
be careful while partitioning you SD card...
read it before executing partiotion....
""forums.androidcentral.com/general-help-how/85809-tutorial-everything-you-wanted-know-about-app2sd-ext3-ext4-partitions.html[/url]"
-rkk
Click to expand...
Click to collapse
Thanks for replying.
I don't want to partition the memory card i just want to format it as the best storage file system .
Sent from my GT-N7100 using XDA Premium 4 mobile app
hi
deutsh said:
Thanks for replying.
I don't want to partition the memory card i just want to format it as the best storage file system .
Sent from my GT-N7100 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
hi,
ok then use FAT32 is good enough for you...
-rkk
But think about the max. filesize with FAT32 (4 Gigabyte). If you don't want to use so large files, I would prefer FAT32 in all cases.
Good... But the question is : the ext4 working as fat32 as storage for files
Sent from my GT-N7100 using XDA Premium 4 mobile app
I think the best way is to try it, but I have read somewhere that ext should go, depending upon the android-version.
Accesing files via USB (in the phone) shouldn't be the Problem, but accesing via cardreader directly on windows did not (or rather not without special ext-drivers for windows).
Well, I think ext3 is the best option if you are going to have media files which are bigger that 4GBytes...
well... The other question is :what is the best for non-damage of microsd ?
I mean the card will minimize the ability to get a damage. What the file system type is best.?
Whith thanks
Sent from my GT-N7100 using XDA Premium 4 mobile app
hmmm, file system organization cannot damage your card, it is only a logic 1 or 0 on the electronics cells.
Maybe there is a difference between frequency of read/write operation. The more the bigger chance to damage a card... of course after a long, looooong time. I would recommend using ext3 as it's more scalable and stable than FAT32.
FAT32: File Allocation Table, 32-bit
Introduced: August 1996 (Windows 95 OSR2)
Directory contents: Table
File allocation: Linked list
Bad blocks: Cluster tagging
Maximum number of files: 268,435,437
Maximum file size: 4GB
Filenames: 8.3 or 255 characters, ASCII except for "'*/:<>?\|
Attributes: Read-only, hidden, system. volume label, subdir, archive
Ext3: Third extended file system
Introduced: November 2001 (Linux 2.4.15)
Directory contents: Table, tree
File allocation: Bitmap, table
Bad blocks: Table
Maximum number of files: number of bytes in volume/2^13.
Maximum file size: 16GB (1KB block) to 2TB (4KB block)
Filenames: 255 bytes long, all bytes except \0 and /.
Attributes: no access time logging, append-only, synchronous write, no-dump, h-tree, immutable, journal, secure-delete, top, allow-undelete.
Journal: metadata and file contents
There is no "best" filesystem, they are all optimized, to some extent, for different things.
Without lots more info, fat32 is relatively efficient and has far and away the best compatibility. For most users the compatibility makes it the winner.
Hi... I try the ntfs but.... But its incompatible with android.... So sad
Sent from my GT-N7100 using XDA Premium 4 mobile app
NTFS is an windows-filesystem, and is only write- and readable on windows. Yes. linux can read it, but needs secial drivers for that and isn't realy fast. It is the worst filesystem for android or linux.
Use fat32 and ready!
Its fast, its compatible, and can be used in/ with most devices. The only disadvantage for you will be the filesize-maximum (4 GB).
SaschaBr said:
NTFS is an windows-filesystem, and is only write- and readable on windows. Yes. linux can read it, but needs secial drivers for that and isn't realy fast. It is the worst filesystem for android or linux.
Use fat32 and ready!
Its fast, its compatible, and can be used in/ with most devices. The only disadvantage for you will be the filesize-maximum (4 GB).
Click to expand...
Click to collapse
O.K. I'll take your advice but I have a little question "how could I protect the micro sdcard from damage ? I suffered from a damge of micro sdcard several times.
Sent from my GT-N7100 using XDA Premium 4 mobile app
Until now I never had an damaged sd-card. And if it will happen, I have an backup of my important data. So I simply will buy a new one and play back this backup. Nothing is forever.
EDIT:
Ok, this 64 GB-SD-Cards are not realy cheap, but under normal conditions it won't faile for a long time, whatever filesystem you will use.
Thanks for everyone ....indeed
Sent from my GT-N7100 using XDA Premium 4 mobile app
rkk253755 said:
Hi,
Fat32 is universal partition for your music, ,video etc....
ext3 ext4 are used for android/unix/linux application storage...
be careful while partitioning you SD card...
read it before executing partiotion....
""forums.androidcentral.com/general-help-how/85809-tutorial-everything-you-wanted-know-about-app2sd-ext3-ext4-partitions.html[/url]"
-rkk
Click to expand...
Click to collapse
hey buddy,
can u tell me i going to partition of memory card for music nd video i'll use FAT32 but second partition what should i do..ext3 or ext4 i ma using motorola g3 stock android is supported ext4 partition on android 5.1.1 or not cz plz tell me .
thanks in advance
shailesh406 said:
hey buddy,
can u tell me i going to partition of memory card for music nd video i'll use FAT32 but second partition what should i do..ext3 or ext4 i ma using motorola g3 stock android is supported ext4 partition on android 5.1.1 or not cz plz tell me .
thanks in advance
Click to expand...
Click to collapse
Android supports Ext4 so I'd rather use Ext4 than Ext3
you can format it by Fat32
sharing and expecting to learn
Hi all,
I am wondering about the partitioning of my new external memory card manufactured by Samsung Electronics.
The very same manufacturer initially develop F2FS, the Flash Friendly File System for the Linux Kernel.
F2FS was expected to be the fastest F.S. for solid-state disks, eMMCs, and SD cards.
Initial tests confirmed it. Nevertheless posterior tests reveal that ext4 beats F2FS (...).
My guessing is that not enough research/test have been done in the matter.
Im going to set the following layout in order to test the speed for each partition:
1._ 34,7G EXT4 -> pictures, movies, backups, etc... AND/OR moved: APPs by hard/sym links; DATA by folder mount
2._ 65,0G FAT32 -> pictures, movies, backups, etc...
3._ 19,5G F2FS -> moved APPs by hard/sym links; moved DATA by folder mount
Depending on the results (specific for my phone and configuration) included in the reports from Antutu, A1SDBenmarch (possibly others too), I will most likely either:
1._ format whole microSD as F2FS -> roms,apps,data,pics,movies,etc; access using the phone (adb, usb, wifi)
2._ format whole microSD as EXT4 -> roms,apps,data,pics,movies,etc; access using any type of linux and many others
3._ format 32G as F2FS -> apps; format 64G as EXT4 -> roms,data,backups,movies; format 32G as FAT32 (any file smaller than 4G I want to be directly accessed from any device through any card reader using any OS)*
* I won't use fat32 as ext4 read/writes speeds are bit faster and i dont need to access the sd using any device
My goal is to format the external microSD card as F2FS and internal storage. F2FS is not only supposed to be better in performance but also it is supposed to expand it's lifespam
Note: Regarding partitioning the microSD in the computer, only linux will allow resizing F2FS filesystems; windows software doesnt recognize it yet, therefore it treats the partition as unformatted, neveertheless it's possible to move it.
Note2: there are programs that allow the user to mount linux partitions and read/write data on them.
Phone: Samsung Galaxy Note 3 SM-N9005, rooted, resurrection remix 5.6 (current,next5.8)
Card: Samsung EVO Plus 128Gb microSDXC UHS-I Class 10 U3 Card
ROM: Resurrection Remix v5.6 (Marshmallow)**
S.Soft: Apps2SDpro: Linked -hardlinks/symlinks- apps to F2FS partition on ext.SD. App data (TuneIn Radio recordings) moved -foldermount- to F2FS partition on ext.SD.
** I am currently designing the multiROM layout which will probably include the current ROM, plus Resurrection Remix v5.8 (Nougat) kali and some others
cheers
Alright, I'm having issues with Link2SD. Many others are as well, from the results that came up in a google search. Seems each "solution" is different for multiple people, and I'm getting a lot of contradictions.
I own a Huawei Ascend Mate 2 (Mt3L03 variant) on 4.3, rooted and running stock, kernel version 3.4.0-g1fcc1aa, bootloader unlocked via a code from Huawei themselves. I've tried AParted and Minitool Partition Wizard. Some people say "Use the Windows partitioning software!" and some people say "The chances of errors with Windows is higher, partition it on your Android!"
I've been at this for several hours, over and over, reading countless threads, trying various methods and settings. I tried creating the ext2 partition first a few times, just for funsies, but no luck there. So I've been mainly doing what I assume is correct, partitioning FAT32 first, then ext2. Or ext3. Or ext4. I've been through it all. I've partitioned ext2 (and others) as quite large, up to 48000mbs. I've partitioned it quite small, down to 800mbs. I've added swap. I've done it without swap. I've left empty space. I've filled the whole card. I've partitioned only FAT32 (or ext2, or others) and left the rest blank. I've created 2 FAT32/FAT16 partitions. I've used Link2SD as a user app. I've used Link2SD as a system app. I've rebooted again and again and again and again and AGAIN. I've selected the file system of my sd card's second partition as ext2, ext3, ext4, FAT32/FAT16, and f2fs (tested ALL on EVERY attempt, just to be certain). But after everything is said and done, no matter how certain I am that I finally got it right..... every stinking time it comes back with "Mount script error // Mount script cannot be created. mount: Invalid argument". Good lord I am ready to tear my hair out with this thing! What on earth am I doing wrong? Does it have anything to do with /dev/block/mmcblk1p2 ? I've also tried GL to SD, DS App2SD, and App2SD, but ultimately I'm not satisfied with any of those. I just tried this: http://techtriosonline.com/2014/11/p...-minitool.html Followed it EXACTLY. Still the same issue.
Also tried with AParted. Annnnd still the same issue. I should also note that in the configuration, I've attempted to changed /dev/block/mmcblk1 to dev/block/mmcblk1p2, and I get the warning "Detected internal device memory! To complish the new DDR of google, AParted can't work with internal partitions or gpt table types. One version with no limits will be maintained in the Aparted web site".
SonyXperiaz1s said:
Alright, I'm having issues with Link2SD. Many others are as well, from the results that came up in a google search. Seems each "solution" is different for multiple people, and I'm getting a lot of contradictions.
I own a Huawei Ascend Mate 2 (Mt3L03 variant) on 4.3, rooted and running stock, kernel version 3.4.0-g1fcc1aa, bootloader unlocked via a code from Huawei themselves. I've tried AParted and Minitool Partition Wizard. Some people say "Use the Windows partitioning software!" and some people say "The chances of errors with Windows is higher, partition it on your Android!"
I've been at this for several hours, over and over, reading countless threads, trying various methods and settings. I tried creating the ext2 partition first a few times, just for funsies, but no luck there. So I've been mainly doing what I assume is correct, partitioning FAT32 first, then ext2. Or ext3. Or ext4. I've been through it all. I've partitioned ext2 (and others) as quite large, up to 48000mbs. I've partitioned it quite small, down to 800mbs. I've added swap. I've done it without swap. I've left empty space. I've filled the whole card. I've partitioned only FAT32 (or ext2, or others) and left the rest blank. I've created 2 FAT32/FAT16 partitions. I've used Link2SD as a user app. I've used Link2SD as a system app. I've rebooted again and again and again and again and AGAIN. I've selected the file system of my sd card's second partition as ext2, ext3, ext4, FAT32/FAT16, and f2fs (tested ALL on EVERY attempt, just to be certain). But after everything is said and done, no matter how certain I am that I finally got it right..... every stinking time it comes back with "Mount script error // Mount script cannot be created. mount: Invalid argument". Good lord I am ready to tear my hair out with this thing! What on earth am I doing wrong? Does it have anything to do with /dev/block/mmcblk1p2 ? I've also tried GL to SD, DS App2SD, and App2SD, but ultimately I'm not satisfied with any of those. I just tried this: http://techtriosonline.com/2014/11/p...-minitool.html Followed it EXACTLY. Still the same issue.
Also tried with AParted. Annnnd still the same issue. I should also note that in the configuration, I've attempted to changed /dev/block/mmcblk1 to dev/block/mmcblk1p2, and I get the warning "Detected internal device memory! To complish the new DDR of google, AParted can't work with internal partitions or gpt table types. One version with no limits will be maintained in the Aparted web site".
Click to expand...
Click to collapse
Its pretty simple (at least I hope so):
Partition wizard is fine for preparing your sdcard. Put the sdcard into your cardreader (not the phone!) and delete all existing partitions from the card. Then create one "primary partition" formatted as "fat32". Once done resize the partition meant that you decrease it by the amount of space you need for your EXT4 partition. in the way that the unallocated space (e.g. 1024MB) is behind the Fat32 partition. Then create a "EXT4" partition in the empty space. This partition must also be a PRIMARY partition. or Link2SD will NOT work.
Put the sdcard into your phone and install Link2SD
LS.xD said:
Its pretty simple (at least I hope so):
Partition wizard is fine for preparing your sdcard. Put the sdcard into your cardreader (not the phone!) and delete all existing partitions from the card. Then create one "primary partition" formatted as "fat32". Once done resize the partition meant that you decrease it by the amount of space you need for your EXT4 partition. in the way that the unallocated space (e.g. 1024MB) is behind the Fat32 partition. Then create a "EXT4" partition in the empty space. This partition must also be a PRIMARY partition. or Link2SD will NOT work.
Put the sdcard into your phone and install Link2SD
Click to expand...
Click to collapse
Ah man, I can't tell you how happy I am that someone (you!) actually answered me about this, I've been going everywhere on XDA today. And no worries, I've been using a cardreader, leaving it in the phone just sounds like asking for trouble. And yup, tried that already. Just to repeat back: I made the card partitioned to FAT32 first. Then, after that, I resized it to free up 1024MB. For the first attempt with this method, I tried EXT2 because I wasn't certain if my kernel supported EXT4. And I made sure that the EXT2 partition was behind the FAT32 one. They were both made primary. I made sure my phone was off, and after Minitool did its magic and finished up I put the card into the phone, and rebooted. I launched Link2SD (after clearing its data first, so it would act as a fresh install), and got the onscreen prompt, and selected EXT2. And boom, once again was the annoying mount script error. I tried again, wiping the card and doing everything over identically, except trying it with EXT4 (because why not, eh?) and selecting EXT4 when Link2SD prompted. Same error. I would give it a go (with a smaller card) in my Sony Xperia Z1s, but I thought I read somewhere that Link2SD and Sony doesn't play nicely with each other..? Mainly, I would only want to try that to rule out that it's not user error, but rather an issue with the device. For that matter, I've also got an old Samsung Galaxy Proclaim on 2.3.6 that is also rooted. Perhaps if I'm feeling adventurous, I'll see if I can get it working there. Unrelated side note: How strange that my old Proclaim can read 64gig cards, but my Xperia freaks out with anything above 32! :laugh:
Alright, heres an update for this thread.
The mount script is successful for my Samsung Galaxy Proclaim, but is not on my Huawei Ascend Mate 2, even when the process is done identically.
Wondering why Link2SD seems to hate my HAM2 so much.
Bump
I've struggled with my cheap/no brand 64GB SD card now for days but I finally succeeded. Hopefully this works over the long haul. We will see.
I have an L34C with very limited internal memory which is why link2sd became essential. So I purchased a 64GB micro SD card through eBay for less than $8..00.
At first I tried to follow the various guides to partition the card using either Minitools/Easeus and even AParted on the phone. Every time the second partition (ext2/4) was added at the end, the partition table got corrupted and then showed file system "other" instead of ext2.
Finally I decided to try the GParted Live CD under Windows 8.1 using VirtualBox (32bit Linux) using the ISO as the boot device. Obviously booting the live CD directly via CDRom/USB works as well but I didn't want to always reboot.
Note that I used SDFormatter to initially low level format and verify that the card was good.
After many trials and errors I got it to work. The key seems to be that all partitions need to start in the first 32GB. This leads to the conclusion that the large fat32 partition needs to be last, before any desired SD card overprovisioning.
As link2sd insists that the ext2/ext4 partition is the second partition, I created a small 32MB Linux swap partition first. I then added a 6GB ext2 Apps partition directly followed by a 48GB fat32 Data partition.. The remainder is unallocated for overprovisioning.
I finally marked the fat32 partition "active" by setting the boot flag.
Before inserting the card, I cleared the link2sd cache and data and then turned the phone off.
Note that in my case link2sd, after the initial reboot, preferred the ext4 check mark for the ext2 partition.
I hope this helps somebody.
I dont understand what you did here. May you explain please.
regli said:
I've struggled with my cheap/no brand 64GB SD card now for days but I finally succeeded. Hopefully this works over the long haul. We will see.
I have an L34C with very limited internal memory which is why link2sd became essential. So I purchased a 64GB micro SD card through eBay for less than $8..00.
At first I tried to follow the various guides to partition the card using either Minitools/Easeus and even AParted on the phone. Every time the second partition (ext2/4) was added at the end, the partition table got corrupted and then showed file system "other" instead of ext2.
Finally I decided to try the GParted Live CD under Windows 8.1 using VirtualBox (32bit Linux) using the ISO as the boot device. Obviously booting the live CD directly via CDRom/USB works as well but I didn't want to always reboot.
Note that I used SDFormatter to initially low level format and verify that the card was good.
After many trials and errors I got it to work. The key seems to be that all partitions need to start in the first 32GB. This leads to the conclusion that the large fat32 partition needs to be last, before any desired SD card overprovisioning.
As link2sd insists that the ext2/ext4 partition is the second partition, I created a small 32MB Linux swap partition first. I then added a 6GB ext2 Apps partition directly followed by a 48GB fat32 Data partition.. The remainder is unallocated for overprovisioning.
I finally marked the fat32 partition "active" by setting the boot flag.
Before inserting the card, I cleared the link2sd cache and data and then turned the phone off.
Note that in my case link2sd, after the initial reboot, preferred the ext4 check mark for the ext2 partition.
I hope this helps somebody.
Click to expand...
Click to collapse
I didnt really get what the steps where to partition my sd card. Like you i have a cheap/no brand 64 Gb Micro Sd card and im unsuccessfull with partitioning it. May you please help me. And in advance Thank You :good:
First let me state that my initial SD card was a Chinese 64GB "fake". Check if yours is also one with RMPrepUSB. Fakes report themselves as having 32GB or 64GB capacity whereas, in reality, they only have a fraction of the reported capacity.
I then purchased Silicon Power SD cards with 32GB and 64GB capacity. I then followed the procedure mentioned above and everything works just fine.
You are brilliant!
I have been having the exact same problem and have spent hours pulling my hair out trying to overcome this issue. Your fix was brilliant as so far it seems to have solved the problem!
One note, I was trying many different methods of partitioning and formatting. This method WILL NOT work with the Aparted app. Mini Tool was the way to go.
Thank You!!!
OK - Here's the thing...
OK, I did this and even posted how it finally worked and got rid of the "mount script error." However, it now seems that because the fat32 partition is now third in line, it looks like Link2SD is now trying to save all the data on the ext4 partition and not the fat32 partition.
When I do the "Link to SD" operation, it seems like it's putting everything on the second partition which is the ext4, but I don't see a change in the space used on the fat32. Am I missing something...?
Maybe the device can't support ext2...
Hi, I got similar problem with you. I've also tried to do partition in reverse order, swap first, then ext2, then fat32. It didn't work. However, when I select repair for the ext2 in Aparted, it said
The super block cannot be read or does not describe the 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 super block is corrupt, and you might try running e2fsck with an alternate superblock: e2fsck -b8193 <device>
Click to expand...
Click to collapse
So now I'm looking for ext2.ko for Xiaomi Redmi Note but haven't found it anywhere.
regli said:
I've struggled with my cheap/no brand 64GB SD card now for days but I finally succeeded. Hopefully this works over the long haul. We will see.
I have an L34C with very limited internal memory which is why link2sd became essential. So I purchased a 64GB micro SD card through eBay for less than $8..00.
At first I tried to follow the various guides to partition the card using either Minitools/Easeus and even AParted on the phone. Every time the second partition (ext2/4) was added at the end, the partition table got corrupted and then showed file system "other" instead of ext2.
Finally I decided to try the GParted Live CD under Windows 8.1 using VirtualBox (32bit Linux) using the ISO as the boot device. Obviously booting the live CD directly via CDRom/USB works as well but I didn't want to always reboot.
Note that I used SDFormatter to initially low level format and verify that the card was good.
After many trials and errors I got it to work. The key seems to be that all partitions need to start in the first 32GB. This leads to the conclusion that the large fat32 partition needs to be last, before any desired SD card overprovisioning.
As link2sd insists that the ext2/ext4 partition is the second partition, I created a small 32MB Linux swap partition first. I then added a 6GB ext2 Apps partition directly followed by a 48GB fat32 Data partition.. The remainder is unallocated for overprovisioning.
I finally marked the fat32 partition "active" by setting the boot flag.
Before inserting the card, I cleared the link2sd cache and data and then turned the phone off.
Note that in my case link2sd, after the initial reboot, preferred the ext4 check mark for the ext2 partition.
I hope this helps somebody.
Click to expand...
Click to collapse
Will your method works on a 128gb sd card?
I was doing this in fact today, after reading this blog. I was having a helluva time because my Sophone i6 Plus has no regular Settings app, it's laid out like an iPhone Prefs app. The settings I needed are usually under "Storage" in a regular settings app. I was able to repartition my 32gb card on-device with aParted, but I could NOT get Links2SD to detect it, even after setting up the 2nd ext4 partition.
Mainly, after setting up the partitions in aParted, you have to switch your main write disk to internal before rebooting, else Link2SD will spit out whatever you have done. After the device reboots, the main write disk will be set to your first SD partition. After that you should be able to start Links2SD and it will prompt to set up your ext4. Then, Apps2SD will stop give you the message that it can't find the 2nd partition. Scroll down to the bottom of the blog and then the bottom where the comments start or use this link, my response should be visible. It's just a question of doing things in a specific order.
One thing that is mentioned in the tutorial is that for large cards, you should not use Fat32 for the main partition, but ext2 instead.
I've been trading a few emails with Vicki the creator of apps2SD. The best way to set this up is to link the user apps to the SD card but keep the data, the internal data on the internal partition. She said you can put the external data on the SD card but I kept both on internal and everything runs great now.
regli said:
I've struggled with my cheap/no brand 64GB SD card now for days but I finally succeeded. Hopefully this works over the long haul. We will see.
I have an L34C with very limited internal memory which is why link2sd became essential. So I purchased a 64GB micro SD card through eBay for less than $8..00.
At first I tried to follow the various guides to partition the card using either Minitools/Easeus and even AParted on the phone. Every time the second partition (ext2/4) was added at the end, the partition table got corrupted and then showed file system "other" instead of ext2.
Finally I decided to try the GParted Live CD under Windows 8.1 using VirtualBox (32bit Linux) using the ISO as the boot device. Obviously booting the live CD directly via CDRom/USB works as well but I didn't want to always reboot.
Note that I used SDFormatter to initially low level format and verify that the card was good.
After many trials and errors I got it to work. The key seems to be that all partitions need to start in the first 32GB. This leads to the conclusion that the large fat32 partition needs to be last, before any desired SD card overprovisioning.
As link2sd insists that the ext2/ext4 partition is the second partition, I created a small 32MB Linux swap partition first. I then added a 6GB ext2 Apps partition directly followed by a 48GB fat32 Data partition.. The remainder is unallocated for overprovisioning.
I finally marked the fat32 partition "active" by setting the boot flag.
Before inserting the card, I cleared the link2sd cache and data and then turned the phone off.
Note that in my case link2sd, after the initial reboot, preferred the ext4 check mark for the ext2 partition.
I hope this helps somebody.
Click to expand...
Click to collapse
Hi this is really the solution for creating the 2nd partition for app2sd or link2sd and also the solution for partitioning sdcards larger than 16gb i tried my 16gb with normal partition method and i was mounted at first time but my 32gb and 64gb they just wouldnt mount so this is the solution for it i tested it and it works tested on ICS 4.0.4 and marshmallow 6.0.1
thank you very much for this solution i had been hammering my head for the last 2 months
regli said:
I've struggled with my cheap/no brand 64GB SD card now for days but I finally succeeded. Hopefully this works over the long haul. We will see.
I have an L34C with very limited internal memory which is why link2sd became essential. So I purchased a 64GB micro SD card through eBay for less than $8..00.
At first I tried to follow the various guides to partition the card using either Minitools/Easeus and even AParted on the phone. Every time the second partition (ext2/4) was added at the end, the partition table got corrupted and then showed file system "other" instead of ext2.
Finally I decided to try the GParted Live CD under Windows 8.1 using VirtualBox (32bit Linux) using the ISO as the boot device. Obviously booting the live CD directly via CDRom/USB works as well but I didn't want to always reboot.
Note that I used SDFormatter to initially low level format and verify that the card was good.
After many trials and errors I got it to work. The key seems to be that all partitions need to start in the first 32GB. This leads to the conclusion that the large fat32 partition needs to be last, before any desired SD card overprovisioning.
As link2sd insists that the ext2/ext4 partition is the second partition, I created a small 32MB Linux swap partition first. I then added a 6GB ext2 Apps partition directly followed by a 48GB fat32 Data partition.. The remainder is unallocated for overprovisioning.
I finally marked the fat32 partition "active" by setting the boot flag.
Before inserting the card, I cleared the link2sd cache and data and then turned the phone off.
Note that in my case link2sd, after the initial reboot, preferred the ext4 check mark for the ext2 partition.
I hope this helps somebody.
Click to expand...
Click to collapse
You so totally saved my day!!! There is nothing in the FAQ of Link2SD about this ... OMG
I already tried for weeks ...
THX a lot
regli said:
I've struggled with my cheap/no brand 64GB SD card now for days but I finally succeeded. Hopefully this works over the long haul. We will see.
I have an L34C with very limited internal memory which is why link2sd became essential. So I purchased a 64GB micro SD card through eBay for less than $8..00.
At first I tried to follow the various guides to partition the card using either Minitools/Easeus and even AParted on the phone. Every time the second partition (ext2/4) was added at the end, the partition table got corrupted and then showed file system "other" instead of ext2.
Finally I decided to try the GParted Live CD under Windows 8.1 using VirtualBox (32bit Linux) using the ISO as the boot device. Obviously booting the live CD directly via CDRom/USB works as well but I didn't want to always reboot.
Note that I used SDFormatter to initially low level format and verify that the card was good.
After many trials and errors I got it to work. The key seems to be that all partitions need to start in the first 32GB. This leads to the conclusion that the large fat32 partition needs to be last, before any desired SD card overprovisioning.
As link2sd insists that the ext2/ext4 partition is the second partition, I created a small 32MB Linux swap partition first. I then added a 6GB ext2 Apps partition directly followed by a 48GB fat32 Data partition.. The remainder is unallocated for overprovisioning.
I finally marked the fat32 partition "active" by setting the boot flag.
Before inserting the card, I cleared the link2sd cache and data and then turned the phone off.
Note that in my case link2sd, after the initial reboot, preferred the ext4 check mark for the ext2 partition.
I hope this helps somebody.
Click to expand...
Click to collapse
it works for me as ive been getting the the partition ext2 showed file system "other" instead of ext2 as well, try many ways didnt work and finally got my sd card working now!!! thank you so much!!! :good: but instead of link2sd i used apps2sd as link2sd i still get the mount eror
Great!! This worked perfectly for Link2SD. But now the FAT32 3rd partition isn't showing up in any of the file explorer, backup, etc. apps. What did I miss or still need to do? Thx.
Still lost
Okay I might be a complete dummy but I'm still not understanding or maybe I know it's just not working for me if you could tell me I'll maybe put a picture of the partitioning using minitool from left to right size of the first primary partition size of the second primary partition size of swap file size of any damn thing for that matter it seems you guys tried to explain or try to help but you explain it in a matter that only makes sense to somebody who does nothing but this I'm a old slow and it's stupid truck driver but I would really like to get my SD card working so I can have more storage I do like to play on these things please help
zombunny said:
Alright, I'm having issues with Link2SD. Many others are as well, from the results that came up in a google search. Seems each "solution" is different for multiple people, and I'm getting a lot of contradictions.
I own a Huawei Ascend Mate 2 (Mt3L03 variant) on 4.3, rooted and running stock, kernel version 3.4.0-g1fcc1aa, bootloader unlocked via a code from Huawei themselves. I've tried AParted and Minitool Partition Wizard. Some people say "Use the Windows partitioning software!" and some people say "The chances of errors with Windows is higher, partition it on your Android!"
I've been at this for several hours, over and over, reading countless threads, trying various methods and settings. I tried creating the ext2 partition first a few times, just for funsies, but no luck there. So I've been mainly doing what I assume is correct, partitioning FAT32 first, then ext2. Or ext3. Or ext4. I've been through it all. I've partitioned ext2 (and others) as quite large, up to 48000mbs. I've partitioned it quite small, down to 800mbs. I've added swap. I've done it without swap. I've left empty space. I've filled the whole card. I've partitioned only FAT32 (or ext2, or others) and left the rest blank. I've created 2 FAT32/FAT16 partitions. I've used Link2SD as a user app. I've used Link2SD as a system app. I've rebooted again and again and again and again and AGAIN. I've selected the file system of my sd card's second partition as ext2, ext3, ext4, FAT32/FAT16, and f2fs (tested ALL on EVERY attempt, just to be certain). But after everything is said and done, no matter how certain I am that I finally got it right..... every stinking time it comes back with "Mount script error // Mount script cannot be created. mount: Invalid argument". Good lord I am ready to tear my hair out with this thing! What on earth am I doing wrong? Does it have anything to do with /dev/block/mmcblk1p2 ? I've also tried GL to SD, DS App2SD, and App2SD, but ultimately I'm not satisfied with any of those. I just tried this: http://techtriosonline.com/2014/11/p...-minitool.html Followed it EXACTLY. Still the same issue.
Also tried with AParted. Annnnd still the same issue. I should also note that in the configuration, I've attempted to changed /dev/block/mmcblk1 to dev/block/mmcblk1p2, and I get the warning "Detected internal device memory! To complish the new DDR of google, AParted can't work with internal partitions or gpt table types. One version with no limits will be maintained in the Aparted web site".
Click to expand...
Click to collapse
Hi sorry sorry would you mind doing a tutorial on YouTube please this would be most helpful. Thank you in advance.