I’m having the same problem 64gb sd card that is not mountable… has anyone been able to get a 64gb sd card working in a fp2?
Yes, my 64 GB SanDisk Ultra works perfectly, after formatting it with the phone.
2 Likes
I’ve got a Samsung EVO 128GB card in my FP2 and so far, it has behaved perfectly. I was able to erase and format from the phone, then mount and copy my music from PC using Windows Explorer.
1 Like
Samsung 64GB card. The last three times I have to restart the phone, I was able to use the card by taking it out of the phone and back into it. Didn’t need to mount, but that is not very ideal.
I have the same problem with my Samsung 64GB SD Card. It is not being detected after a reboot. Should this be on the known bugs list?
I´m using a fresh Samsung Micro SD PRO+ 128GB Memory Card which is performing flawless and smooth in my FP2.
One thing I could experience shortly: it worked perfect from the beginning and was formatted with fat32 by the phone.
I guess there is not much choice in fs selection when fresh out the pack.
Partition size isn´t a problem for the fs, but rather file size.
So recently I tested some new apps and experienced later not being able to access my card. No replacing the card, rebooting or taking out the accumulator changed this condition.
My filemanager simply couldn´t see it any longer.
So I took it out once more and checked the filesystem with windows, there were errors found.
After fixing the fs all went well again and I could access it again with my filemanager on FP2.
Also don´t miss to unmount/mount it if you plan to remove it to prevent damaging the fs.
I have a similar experience with my 64 GB Samsung SD card. When I have to reboot my phone, the SD card is no longer visible. When I insert the card into my PC I need to run CHKDSK and then my FP2 recognizes it again until the next reboot. Today my FP2 was no longer able to read the SD card, so I inserted it into my tablet which immediately recognized the card. So I ejected it from the tablet and could read it fine in my FP2 after that.
So I highly suspect that something marks the card dirty and does not close this status when powering off the phone. So on reboot it’s also not able to fix the chkdsk required status and then the card is gone.
Sounds like a recreateable and fixable scenario to me.
Thanks for looking into this.
Christian
Just for the records, my samsung 64GB SDcard is working well in the FP2. No problems after reboots.
Next update (23.04.2016):
With the new update it got a little bit worse. Before the update I used the tip, that you just have to reboot the phone a multiple times until it recognized the SDcard. Now I can reboot it 15 times and nothing changes. Now back to start. Open the case after every reboot (includes spontaneous reboots) and put the card out and in again and again until it works…
I also have the same problem with my new Samsung 64GB evo card. Only solution that works consistently is to take off the back and remove and reinsert.
Hopefully fixable with a software update.
I also had this problem with my SanDisk 64GB card with the FP Open OS.
I was able to fix this by formatting the card to EXT4 with my computer and formatting it again with my FP2 in the storage-settings. Since that, everything is working fine. 
Hopefully, this helps you and also works under other circumstances too. 
1 Like
Meanwhile I have tried several options and believe it is some kind of timing problem when (auto) mounting the card on reboot.
Usually I do the following with my Samsung 128GB pro+ which in most cases brings back my sdcard after boot.
I don´t reboot my phone but only power it off, rebooting usually don´t manage to get my card mounted again but rather spends my fresh accumulator while doing several runs.
So I have to wait some time after power off, it could take 60 secs or more. After powering on and booting the phone I patiently unlock my sim card(s) without any rush waiting a moment for it (them) being unlocked.
After this I unlock my phone and go to settings/storage to see if the card is available again.
When doing this procedure in most cases I only need one attempt to get back my sdcard.
Anything else that I have tried in the past like rebooting, (re)formating, unmounting before rebooting or what others had also sugested didn´t solve this issue for good.
But with this procedure I have very good chances to get my card mounted quicker than with all other approaches I took.
Have you checked if your SD card might be defective?
I had similar issues with multiple SD cards. The phone did not detect them. Sometimes “Erase SD card” on the phone helped, sometimes not, sometimes it lead to reboots.
In most cases I could see error messages from Vold in the log (with “adb logcat” from a USB-connected computer).
The example log messages below shows that the card was not accessble, then formatted and the filesystems check durign mounting was ok. But creating a directory (LOST.DIR) on the card failed, so it was never mounted.
Note that this example also shows that one of the relevant services crashed due ot the check leading to a reboot.
D/Vold ( 234): Volume sdcard1 state changing 1 (Idle-Unmounted) → 6 (Formatting)
E/Vold ( 234): Failed to apply disk configuration (-1)
E/Vold ( 234): Failed to initialize MBR (I/O error)
D/Vold ( 234): Volume sdcard1 state changing 6 (Formatting) → 1 (Idle-Unmounted)
W/Vold ( 234): Returning OperationFailed - no handler for errno 0
I/Vold ( 234): /dev/block/vold/179:65 being considered for volume sdcard1
D/Vold ( 234): Volume sdcard1 state changing 1 (Idle-Unmounted) → 3 (Checking)
I/fsck_msdos( 234): ** /dev/block/vold/179:65
D/fsck_msdos( 6654): sectors Per cluster :16
D/fsck_msdos( 6654): boot->ClusterOffset :30356
I/fsck_msdos( 6654): FAT32 Filesystem
D/fsck_msdos( 6654): Using cluster_chain_descriptor
I/fsck_msdos( 6654): Total clusters 1942742
I/fsck_msdos( 234): ** Phase 1 - Read FAT (compare skipped)
I/fsck_msdos( 234): Attempting to allocate 7589 KB for FAT
I/fsck_msdos( 6654): ** Phase 2 - Check Cluster Chains
I/fsck_msdos( 6654): Begin to handle the cluster chain
D/fsck_msdos( 6654): rootDir->head :2
I/fsck_msdos( 234): ** Phase 3 - Checking Directories
D/fsck_msdos( 6654): Verify Filesystem information
W/fsck_msdos( 6654): 1 files, 2959000 free (1942739 clusters)
I/fsck_msdos( 6654): free_rb_tree
I/fsck_msdos( 6654): free_fragment_tree
I/fsck_msdos( 6654): free_fragment_tree
I/fsck_msdos( 6654): free_fragment_tree: rb_tree is empty
I/fsck_msdos( 234): ** Phase 4 - Checking for Lost Files
I/Vold ( 234): Filesystem check completed OK
E/Vold ( 234): Unable to create LOST.DIR (I/O error)
D/Vold ( 234): blkid identified as /dev/block/vold/179:65: LABEL=“android” UUID=“EE3E-9E59” TYPE=“vfat”
E/VoldConnector( 1141): timed-out waiting for response to 14 volume mount /storage/sdcard1
--------- beginning of crash
E/AndroidRuntime( 1141): *** FATAL EXCEPTION IN SYSTEM PROCESS: Thread-299
E/AndroidRuntime( 1141): java.lang.NullPointerException: Attempt to invoke virtual method ‘int com.android.server.NativeDaemonEvent.getCode()’ on a null object reference
E/AndroidRuntime( 1141): at com.android.server.MountService.doMountVolume(MountService.java:1154)
E/AndroidRuntime( 1141): at com.android.server.MountService.mountVolume(MountService.java:1794)
E/AndroidRuntime( 1141): at com.android.internal.os.storage.ExternalStorageFormatter$2.run(ExternalStorageFormatter.java:295)
D/AndroidRuntime( 6725): >>>>>> START com.android.internal.os.ZygoteInit uid 0 <<<<<<
D/AndroidRuntime( 6725): CheckJNI is OFF
W/Vold ( 234): fs_prepare_dir failed: I/O error
E/Vold ( 234): Failed to mount secure area (I/O error)
In the end what I did was to thoroughly test all SD cards on a computer:
- Format the whole card with fat32 or ext4
- Create some directories
- Write big files to it to fill the whole card
- Umount / detach
- Attach / mount
- Try to read files
- Repeat the procedure ten times
All three SD cards I had showed errors and failed during this process, while a new card survived the test and is now working fine in my phone.
I have the same problem with a new FP2: A “Samsung Pro MicroSDXC 64GB UHS-I (Class 10) 90 MB/s” card does not get mounted after a reboot (sometimes).
My finding: The “card not mounted” problem occurs very often if the phone is warm/hot and you reboot it. If its cold, the sdcard seems to work fine. If I shut down the warm phone and wait a little moment (1-2min), power up -> all fine too.
So, could it be temperature related?
I reported the same issue with my Samsung card earlier, but a two weeks ago I ditched the Samsung card and put in a Lexar 64 GB card and I haven’t seen the problem so far. Very strange though, there must be a very tiny electrical margin where the Samsung card seems to have a problem.
Hi folks,
my fairphone 2 functions very well with a Lexar 633x 64 GB micro SDXC and with a Samsung 64 GB Eco. At every time I switch the phone on, the sd-cards are well recognized. I had the same problems as other users here with a Sandisk Ultra 64 GB. The problem was, that the sandisk was never recognized after shutting down and switching on the FP. The Lexar was first not recognized after putting it in the FP. In had to format it with the FP and then it functiones now.
These are my experiences with sd-cards in th FP2.
This post was posted wrong page . sorry
Hi
I also have the same problem as all above … The problem is random, but in most cases, I loose the SD card when I reboot my FP2.
My SD card is also a 64 Go SAMSUNG EVO Plus.
Dis anybody find a solution that does not need extra computer ?
A new finding on this: I installed Fairphone Open OS 16.07.1 and since then no problems mounting the SD-card, even if the phone is warm/hot. But lets see how it goes the next couple of days …