What is the recommended way to mount a microSD card so that I can use it as user furios?
(sudo chown ... after a sudo mount ... on the phone reports an error.)
SAFE TEMPORARY WORKAROUND:
1. create the folder "/home/furios/microSD" by using portfolio or the console
2. unmount the micro sd card by opening the console and running "sudo umount /dev/mmcblk0p1"
3. mount the micro sd card by opening the console and running "sudo mount -o uid=32011,gid=32011 /dev/mmcblk0p1 /home/furios/microSD"
steps 2 and 3 must be done after every boot.
MORE INFO:
furios does automatically mount the micro sd, but very incorrectly. first of all, furios mounts it as root, which makes it read-only to all apps. secondly, furios does not make it accessible to the user through portfolio.
the furios devs should make it automatically mount with full user read/write access, and show up in portfolio under devices. that would be the correct way it should work, as it does in kali for the pinephone pro.
there are rumors of people with ext4 formatted micro sd cards getting it to work using /etc/fstab, but this is a very dangerous method and you may lose all files on the phone (like if you don't use the nofail option). so far, using /etc/fstab is only reported working if the micro sd is formatted with an ext4 filesystem, regardless of what filesystem is configured in /etc/fstab or if the filesystem type is set to auto.
cubetronic 10/02/2026 12:34 pm
actually, vfat may also be working using "/etc/fstab", but my card is exfat, and i don't know if there is a valid type for that, and auto doesn't seem to work.
cubetronic 10/02/2026 1:24 pm
i got it to work with fstab, but it takes like 4 minutes after the system has booted up to kick in.
furios manual mount:
sudo mount -o uid=32011,gid=32011 /dev/mmcblk0p1 /home/furios/microSD
furios /etc/fstab mount:
/dev/mmcblk0p1 /home/furios/microSD auto nofail,uid=32011,gid=32011,umask=022,noatime 0 1
i believe specifying the uid is important for my exfat microsd, but seeing as how it takes 4 minutes to kick in, i dont consider it really solved, plus it should show up under devices, and should be fixed upstream
cubetronic 10/02/2026 1:49 pm
ALTERNATIVE ANSWER:
(this will mount the sd card automatically, and make it accessible in portfolio, but it takes a whopping 4 minutes after boot to kick in, on each boot)
1. create the folder "/home/furios/microSD" by using portfolio or the console
2. open console and run "sudo nano /etc/fstab"
3. add this line "/dev/mmcblk0p1 /home/furios/microSD auto nofail,uid=32011,gid=32011,umask=022,noatime 0 1"
4. press ctrl+o to save, and ctrl+x to exit, then reboot.
After plugging one in I was able to access it through /media/furios/sd card name (i think, writing from memory... it may be one more folder deep just follow down from /media) and copy using cli.
So I think it does mount it, it just doesn't expose it to portfolio
I had a similar problem with a VFAT SD card. I could read it but not to write to it as a non-root user. Since I don't know how to change the mount options for the card, I reformatted it as ext4 and then I could do sudo chown and use it normally.
It would be nice to have a FAQ entry for r/w SD card access.
Thanks for the hints. I had the same issue but with small differences. My SD card was taken from my Android phone so it was formatted with VFAT and had a partition table. I created an sdcard folder in my home folder, then mounted the card there using the /etc/fstab line:
/dev/mmcblk0p1 /home/furios/sdcard vfat user,auto,noatime 0 1
VFAT is more usable when swapping files with non-Linux devices and also doesn't have a journal so it will not do as much writing to the card.
garydale 04/01/2026 7:29 am
After a little further work, I noticed that the phone automatically mounts the card on boot. However, this is in a a less than ideal location, so creating a symbolic link to /media/furios/mmcblk0p1 in your folder provides easier access.
I'm not sure what happens if you change cards without rebooting, however I suggest that umounting the card before removing it is probably a good idea. It if doesn't automount when you put the new card in, you can always manually mount it now that the old card isn't still mounted.
cubetronic 10/02/2026 1:29 pm
@garydale WARNING!! this may make it not boot, requiring a factory reset, losing all user data, since you didnt give the nofail option.
Install Nautilus and it just works 😁.
Portfolio does not see sd cards but otherwise it is better because Nautilus has some annoying touch screen issues - nothing too big but you will notice when you try it
cubetronic 10/02/2026 1:38 pm
@alaraajavamma installing and using nautilus did not help at all. i got it by opening the console and running "sudo apt update", and "sudo apt install nautilus"
Thanks for the answers. Looking at the way that nautilus mounts it, I added the following line to /etc/fstab and now the sdcard is mounted on reboot as I need it:
/dev/mmcblk0 /media/furios/sdcard ext4 noatime 0 1
cubetronic 09/02/2026 7:32 pm
@sve WARNING!!! adding that line may make your system FAIL TO BOOT, requiring a FACTORY RESET (by holding power+volumeUp), not once but TWICE, and LOSING ALL FILES on the phone.
if your card is formatted as exfat, then your device WILL NOT BOOT, as described above, losing all files. you can check your filesystem type by using "lsblk -f"
perhaps try mounting the card manually before editing fstab.
Sven Topic starter
09/02/2026 8:57 pm
I am sorry that my answer caused trouble. The context in this forum software is hard to keep, so I should have repeated important information in my answer:
The answer assumes that the card is formatted with ext4.
Instead of noatime, one should always first try with noatime,noauto and mount it manually: mount /media/furios/sdcard. If all is ok, one can remove the noauto from the /etc/fstab line.
Sven Topic starter
09/02/2026 9:31 pm
Unfortunately, one cannot edit old answers. So, I must add it as a comment.
Add a line to /etc/fstab:
/dev/mmcblk0 /media/furios/sdcard auto noatime,noauto 0 1
The "auto" in column 3 should work for different filesystem types. The "noauto" in column 4 is important to not block booting if you mistyped this line, lost your SD card or similar.
