After updating from version 6.17 to 6.18, I can no longer access the SD card and have to reformat it. Of course, I’d like to avoid doing that so I don’t lose the data on it.
New Issue
(enter here…)
When I insert the SD card into my computer, all the data is there and readable. So it really does seem to be a problem with iodé. Is there any way to get my Fairphone to recognize the card again without having to format it first?
Have the sane multiple Times!
Sometimes “resolved” the Reboot the Access. Or the Format of the SD on the Phone and Transfer the Data Back.
It seems to be a problem with the latest update after all.
I have the same issue with my Fairphone 5 after updating from 7.7 to 7.8.
If requested, I raise another issue for the Fairphone 5 and 7.8.
I checked the exFAT filesystem on another device without finding errors.
The SD is a SanDisk Ultra 512 GB A1.
While writing, I am running a backup of the relevant files under Linux with rsync.
I will later format the SD and restart the phone to check if the issue reappears.
Was there a change in the exFAT drivers with a brick in the downward compatibility?
In case anyone is interested in which parameters I use:
rsync --human-readable --progress -av
//EDIT: The English error is:
Issue with SDCard Tap to fix
Thank you very much for your responses. Since I’m apparently not the only one with this problem, it must indeed be a bug in the update process.
You’re welcome.
I hope we get a reaction soon.
BTW:
While waiting for my file backup, I did some searching on the internet.
As LineageOS is upstream to iodéOS, this closed issue of a 23.2.x nightly build troubles me a bit:
By now I did’nt have found the time to connect my phone to a computer to capture some logs.
If I understand the issue right, we both could have just bad luck, so that the file system check takes too long for the mounting process to wait. Therefore, I won’t format my SD card by now.
I hope I find the time to dive in there. Because this situation bugs me like hell. On the SD I have audiobooks and many offline maps.
Hello again,
I checked my logcat now.
The system seems to find the device, but after this I cannot find anything else that is linked to the SD (mmcblk1).
I vold : Found disk at /devices/platform/soc/8804000.sdhci/mmc_host/mmc1/mmc1:aaaa/block/mmcblk1 but delaying scan due to secure keyguard
I know some things about Linux systems to troubleshoot most issues you can face in a server or desktop environment, but Android is something else. Right now I will write a support e-mail because I don’t like the idea right now of formatting my SD card for nothing.
@atasingorneq
Can you verify this wording on your device
Issue with SDCard Tap to fix
Yes, that’s the error message.
Yes there have been multiple reports of this, I notified our lead developer.
Hello,
Is there a news update available?
In which position in the queue are we?
From our developer, it seems related to filesystem checks (fsck in Linux) performed on the SD card:
“It seems that there is a change in the exfat fsck which make it take much longer. For big / full sd cards, it takes too much time, and a timeout is triggered. It seems there is nothing to do, except format the sd card with another file system (e.g. ext4). I have no problem with a small card, I can read, format it, …”
What I am not certain about is if this is only Fairphone related or not, but I think so? As a reformatting workaround, what other systems do you use? (Windows or Linux?) If Windows, you could try formatting as FAT32 but this would not store single files larger than 4GB. With Linux, you could go to ext4 (default for many Linux distros) and be fine. There is also “F2FS” (“Flash Friendly”) that I think can be used by Android.
I have asked on our Telegram / Matrix beta channel if people can test with the new 7.9 beta to see if anything has changed, but no feedback yet.
No, the Shiftphone 8 is also affected. The SD card vanished after installing the last system update.
I bought a Motorola G 5G 2024 from Openmobile.us, it does the same issue with SD card.
I’ll repartition my sd card since beta tester don’t answer yet. My guess is that the bug will be fixed faster like this, than waiting for 7.9.
Thanks!
I have also heard from some that copying your data out and reformatting it within iodéOS (presumably this would remain exfat) has been successful.
But yes, I don’t see any definitive feedback from testers yet. One person noted that the issue only occurs every other boot meaning when they start the phone and get the error message that it can’t be used, they then restart and after that it works until the next reboot. I do think this behavior is related to the triggering of the filesystem checks: maybe they are only done every 2nd boot in their case. But I don’t know the underlying logic of how Android initiates filesystem checks.
Hm,
I was afraid of this kind of response.
So this is a bug/feature/situation/issue iodeOS actually inherited from LineageOS.
See my post above #6.
If I understand the GitHub issue for LineageOS right, the timeout will not be adjusted.
And because there appears to be no binary fsck for exFAT, EXT4, or FAT32 on the shell (EDIT:// or at least you cannot see/ use it without rooting), if this problem should reoccur with another file system, we will be screwed all over again. 
Or did I miss something here? - Is the fsck and mounting not done by the kernel itself?
I hope there will be at least for the future a native support to format the SD card with all possible filesystems. As a Linux power user, it is a piece of cake, but for others, I don’t know.
I’ve managed to copy my SD Card on my computer, format my SD Card with my iodéOS phone, and bring back my data on my SD Card.
It only took several hours to have my back up done and back, the rest was pretty quick and simple.
Thanks!
Has this bug actually been fixed in version 6.19, and can I update to this version without any problems?
I updated my Fairphone 4 from 7.7 to 7.9 and now it won’t mount my exFAT formatted MicroSD card
I have it rooted though, so I’m wondering if I can mount it manually using a terminal app
[edit]
So, you can check the block devices using the blkid command
And I found the microsd partition is /dev/block/mmcblk0p1, and it’s supposed to get mounted to /mnt/media_rw/partition_name
Your microsd card’s partition name might be different.
And you can unmount and mount the partition using
umount /mnt/media_rw/partition_name
mount -t exfat /dev/block/mmcblk0p1 /mnt/media_rw/partition_name
And this sort of works if I manually navigate to /mnt/media_rw/partition_name in FX file explorer. But it doesn’t show up the way it normally should, and most apps still don’t see it.
I think it needs to be linked to somewhere in /storage