The gparted method caused I/O problems on my sdcard
First, thank you for describing with this detail the procedure to correctly partition the sd card. It is something that almost nobody cares or understands. So it is very useful for us newbies to get the maximum performance out of the sd card.
But in my case I had some problems. I bought at a respectable european store a Samsung plus MicroSDHC 32Gb UHS I class 10 (the ones with "32Gb" letters in orange). I used it on my tablet for 2 months without any problem. Then I decided to switch it to my phone to use it with a link2sd partition since the phone has low internal memory.
To prepare the sd card I booted with a Kali Live CD and launched gpart.
I inserted the micro sd card on the genuine adapter and I was always using the internal laptop reader.
Deleted the 32gb fat32 partition and I created 2 others
25,2Gb FAT32 1st and 4096mb ext4
Formatted both on linux.
Rebooted to Win7
Whenever I was sending 1,5Gb of files to the recently created FAT32 partition I was always getting "The request could not be performed because of an I/O device error". But choosing "Try again" would work and copy the files correctly. This would happen 3 or 4 times during that copy. Always using the sd card on the internal laptop reader.
I went to gpart again, deleted all the partitions and recreated them, this time allowing gpart to select different setttings like leaving 2 mb at the beginning.
Same error happened.
Formatted the sd card on the phone. It deleted everything and created a 32Gb partition. I changed the sd card to the adapter+internal reader, send 1,5Gb and it was copied without problems.
Gparted again. Recreate 26Gb FAT32 + 4Gb ext4.
When in Win7 the copy error was happening.
- So while in Win7 I decided to format the FAT32 partition via windows explorer. I notice that it changed the allocation unit size from 4k to 16k.
Next when I sent the 1,5Gb of files it went without problems.
I don't know what changed exactly because on my first attempt I noticed that the FAT32 partition created with gpart already had 16k allocation units. Strange...
First, thank you for describing with this detail the procedure to correctly partition the sd card. It is something that almost nobody cares or understands. So it is very useful for us newbies to get the maximum performance out of the sd card.
But in my case I had some problems. I bought at a respectable european store a Samsung plus MicroSDHC 32Gb UHS I class 10 (the ones with "32Gb" letters in orange). I used it on my tablet for 2 months without any problem. Then I decided to switch it to my phone to use it with a link2sd partition since the phone has low internal memory.
To prepare the sd card I booted with a Kali Live CD and launched gpart.
I inserted the micro sd card on the genuine adapter and I was always using the internal laptop reader.
Deleted the 32gb fat32 partition and I created 2 others
25,2Gb FAT32 1st and 4096mb ext4
Formatted both on linux.
Rebooted to Win7
Whenever I was sending 1,5Gb of files to the recently created FAT32 partition I was always getting "The request could not be performed because of an I/O device error". But choosing "Try again" would work and copy the files correctly. This would happen 3 or 4 times during that copy. Always using the sd card on the internal laptop reader.
I went to gpart again, deleted all the partitions and recreated them, this time allowing gpart to select different setttings like leaving 2 mb at the beginning.
Same error happened.
Formatted the sd card on the phone. It deleted everything and created a 32Gb partition. I changed the sd card to the adapter+internal reader, send 1,5Gb and it was copied without problems.
Gparted again. Recreate 26Gb FAT32 + 4Gb ext4.
When in Win7 the copy error was happening.
- So while in Win7 I decided to format the FAT32 partition via windows explorer. I notice that it changed the allocation unit size from 4k to 16k.
Next when I sent the 1,5Gb of files it went without problems.
I don't know what changed exactly because on my first attempt I noticed that the FAT32 partition created with gpart already had 16k allocation units. Strange...