Originally Posted by juiceme

Jolla will automount it to /media/sdcard/{UUID}

Originally Posted by dameceno

Originally Posted by juiceme

Jolla will automount it to /media/sdcard/{UUID}

Well juiceme that is the thing, with my fat filesystem 32 GB SDcard it is mounted automatically but with this card it isn't, more over its uuid folder is missing from /media/sdcard so I need a way to force the system to mount it as well

Originally Posted by juiceme

OK, then there's something else. You coud try creating the directory there manually, maybe it would then be mounted?
You can find out the partition UUID's by command "blkid"
Then just do (as root) mkdir "/media/sdcard/your_UUID"

Originally Posted by dameceno

Thanks as I could mount it manually following your instructions, but it now has a permissions issue...

Originally Posted by juiceme

do "chown -R nemo.nemo /media/sdcard/{UUID}" as root.

Originally Posted by dameceno

Will do that when at home later on, I have to point out that the mount doesn't survive a reboot as jolla still doesn't automatically mount it, is there a way around that?

Originally Posted by dameceno

I am thinking on reformating the card, but that might be a setback avoidable with a workaround. in the steps on how to partition my sdcard you mentioned a step where I had to mount the card after formatting it with mkfs.ext4 what command would have been used to mount it?
Will mount -t /dev/mmcblk1p1 /media/sdcard/UUID do the trick, Thanks again for all your assistance without which my panic levels would have been up the roof by now.

Originally Posted by juiceme

Jolla should (and it not only should, it sure does) automount the card if set up correctly.
Without seeing any logs I cannot have a guess why your system does not automount

One way to force it to automount is to set an entry to /etc/fstab for it. However it should also work without. No idea why it does not work for you.




No difference, and no reason to repartition/remount it.

One thing comes to mind, I do not remember if you had another (smaller)SD card? if so, does that automount correctly?
If you have, and it does, you could take logs from each case and compare those for differences.

Originally Posted by Leinad

yes, i had the same thought, but could not notice any difference in speed the last day, using it.

This is, what df -h now puts out with my configuration:

Code:

[nemo@localhost ~]$ df -h
Filesystem            Size  Used Avail Use% Mounted on
rootfs                 14G  4.1G  9.2G  31% /
/dev/mmcblk0p28        14G  4.1G  9.2G  31% /
devtmpfs              406M   64K  406M   1% /dev
tmpfs                 407M  268K  406M   1% /dev/shm
tmpfs                 407M   23M  384M   6% /run
tmpfs                 407M     0  407M   0% /sys/fs/cgroup
tmpfs                 407M   24K  407M   1% /tmp
/dev/mmcblk0p25       8.0M  4.2M  3.8M  54% /persist
/dev/mmcblk0p19       8.0M  4.1M  3.9M  52% /drm
/dev/mmcblk0p18        64M   45M   20M  70% /firmware
/dev/mmcblk0p28        14G  4.1G  9.2G  31% /swap
/dev/mmcblk0p28        14G  4.1G  9.2G  31% /home
/dev/mmcblk0p9         48M  7.5M   40M  16% /var/systemlog
/dev/mmcblk1p1         60G  2.6G   54G   5% /mnt/sdcard2
/dev/mmcblk1p1         60G  2.6G   54G   5% /home/nemo
/dev/mmcblk1p1         60G  2.6G   54G   5% /data/sdcard
tmpfs                 407M     0  407M   0% /mnt/asec
tmpfs                 407M     0  407M   0% /mnt/obb
/dev/mmcblk1p1         60G  2.6G   54G   5% /run/user/100000/media/sdcard
/dev/mmcblk1p1         60G  2.6G   54G   5% /home/nemo
/dev/mmcblk1p1         60G  2.6G   54G   5% /data/sdcard

before encouraging other people to use it this way, i really would like to hear the opinion of at least one, who is more expert than me

edit: i don't understand, why /home/nemo and /data/sdcard are listed 2 times for example...

Originally Posted by Leinad

mount-sd.sh was overwritten by the update, so obviously you need to add the lines to mount your folders again (step 6 of first post)...

but the really bad part after the update is:
at first look, it seems that mount-sd.sh is now called for the first time later than before (now after the "ambiance-stuff"), which is really totally annoying.

the only workaround, i have for now:
copy the ambiance to the "traditional home-folder" (not on sdcard), so it can be accessed at bootup.

i hope, i or someone else finds a better solution (or this will be gone with the next update).