This replaces /usr/sbin/mount-sd.sh with a experimental version including these commits:
Adding support for swap space on SD card
Wait for the tracker after we mounted, not before.
Correctly unmount
Remove duplicated code
Enable TRIM on ext4 and btrfs
Remove useless indexing
Add TRIM support for f2fs.
fschk before mounting.
Try to fix exfat support.
Don't flush on exfat.
Mount by label.
Remove swap support if SailfishOS handles it native (>=2.0.2.45)
Installation failed, why?
To correctly install it you have to uninstall first, then install (see comment #13836 and comment #9665 for more information).
My card won't mount anymore after a update of SailfishOS, what to do?
Reinstall bleeding edge sd-utils (see comment #9665 for more information).
Use at your own risk!
Like what you see? Feel free to
Attachment | Size | Date |
---|---|---|
sd-utils-0.0.18.1-1.noarch.rpm | 3.77 KB | 28/06/2015 - 13:28 |
sd-utils-0.0.18.1-2.noarch.rpm | 3.99 KB | 04/07/2015 - 13:40 |
sd-utils-0.0.18.3-0.noarch.rpm | 4.08 KB | 08/07/2015 - 19:25 |
sd-utils-0.0.18.3-1.noarch.rpm | 4.15 KB | 08/07/2015 - 19:37 |
sd-utils-0.0.18.4-0.noarch.rpm | 4.23 KB | 26/09/2015 - 14:55 |
sd-utils-0.0.18.4-1.noarch.rpm | 4.31 KB | 13/10/2015 - 08:47 |
sd-utils-0.3.0.1-0.noarch.rpm | 4.49 KB | 08/05/2016 - 19:49 |
sd-utils-0.3.0.1-1.noarch.rpm | 4.58 KB | 08/05/2016 - 20:26 |
sd-utils-0.3.0.1-2.noarch.rpm | 4.9 KB | 20/06/2016 - 12:19 |
- Remove swap support if SailfishOS handles it native (>=2.0.2.45)
Comments
SebMa
Tue, 2019/11/05 - 22:01
Permalink
@V10lator I'd to fork from the latest version (0.3.0.1-2) of your mount-sd.sh script, bit I cannot find on github. It's not at https://github.com/V10lator/bleeding-sd-utils/releases. Can you help me find it ?
olf
Wed, 2019/11/06 - 02:38
Permalink
It is inside the archive files there, take a look in @V10lator's sd-utils source code repository.
But all the various forks of and patches to the sd-utils were derived from MER's / Jolla's original sd-utils, which were obsoleted and not used anymore since SailfishOS 2.2.0 and ultimately removed in SailfishOS 3.2.0. Consequently its source code repository was archived by moving it into mer-core-attic.
Hence the mechanisms employed by all sd-utils variations are not supported anymore.
SebMa
Wed, 2019/11/06 - 03:12
Permalink
@olf The latest release in archive files there is 0.0.18 not 0.3.0.1-2
olf
Sat, 2019/11/09 - 18:52
Permalink
The repo is newer (who cares about some old, tagged archive files), but (as said) follows an (now) obsolete approach anyway.
P.S.: May I suggest to support TJC #212628 and to use FAT (as vFAT32) or EXT4 meanwhile.
SebMa
Thu, 2019/11/07 - 17:41
Permalink
What repo are you talking about : the V10lator on github or the V10lator on openrepos ?
rfa
Sat, 2017/10/21 - 09:21
Permalink
I'm trying to follow these instruinstructions :
download warehouse
find bleeding edge sd utils
install
uninstall
reinstall
& then my sd permission should work. I think I missed something, my sd appears, but no permission to access /media/sdcard... is still returned
TMavica
Mon, 2016/06/20 - 19:26
Permalink
after update, it wont work again
V10lator
Tue, 2016/06/21 - 00:45
Permalink
Point 2 of the FAQ:
My card won't mount anymore after a update of SailfishOS, what to do?
Reinstall bleeding edge sd-utils (see comment #9665 for more information).
TMavica
Tue, 2016/06/21 - 00:56
Permalink
of course I know, bit still same
Reinstall previous version fixed
V10lator
Tue, 2016/06/21 - 00:59
Permalink
Wait, are you talking about an update of SFOS or this package here?
TMavica
Tue, 2016/06/21 - 01:09
Permalink
this package here
V10lator
Tue, 2016/06/21 - 02:31
Permalink
That's strange and it I can't reproduce it.
Is there any output if you execute
/usr/sbin/mount-sd.sh add /dev/mmcblk1p1
(change /dev/mmcblk1p1 if needed: /dev/mmcblk is your SD card, p1 is the first partition) with the newest version of this script? Also do you have the file /etc/sailfish-release on your device and does it contain the line
VERSION_ID=2.0.2.45
?
TMavica
Tue, 2016/06/21 - 02:47
Permalink
1. Nothing show in first command
2. I got this line
TMavica
Sat, 2016/06/18 - 01:35
Permalink
It seem it cant mount my exfat sdcard now in 2.0.2
uninstall and reinstall nil help, it said unknown filesystem
V10lator
Sat, 2016/06/18 - 10:40
Permalink
My Jolla 1 is still on 2.0.1.11, how did you get access to 2.0.2 (do you own a Jolla C) ?
So as our OS versions differ the following is just guessed:
Most likely this package is working as it should but you also need exfat-nofuse and exfat-utils installed. If that doesn't fix your issue exfat-nofuse might need a update. You could check that by enabling developer mode on your SailfishOS device and executing
uname -r
it should show 3.4.108.20150901.1. If it shows a higher number either contact me to give me the new number and test a pre-release for me or wait till 2.0.2 is available to early access users so I can test for myself.
//EDIT: If you try to mount exfat manually please try to add
-t exfat
to your mount command.
TMavica
Sat, 2016/06/18 - 11:29
Permalink
If I manually mount , it said filesystem not support
Mine is 3.4.108.20160401.1
I update to 2.0.2.45 by using ssu re 2.0.2.45 , version --dup
I have tried install exfat fuse , it works only after I create its filesystem
after reboot, it wont mount again, I have labelled it
V10lator
Sat, 2016/06/18 - 11:46
Permalink
Thanks, investigating.
TMavica
Sat, 2016/06/18 - 11:55
Permalink
Find me if u want me to test new version
V10lator
Sat, 2016/06/18 - 19:14
Permalink
Fixed. Please update exfat-nofuse to 1.2.11.
Skillmon
Sat, 2016/05/21 - 22:42
Permalink
Installation failed for me (from within Wareshouse) due to:
Status: dep-resolution-failed
Extra details:
There is no update candidate for sd-utils-0.1.0-1.13.1.noarch
V10lator
Sun, 2016/05/22 - 09:25
Permalink
You might have noticed that it showed as installed while it wasn't (0.1.0-1.13.1 is the version Jolla uses, 0.3-1 is the newest upstream ( https://git.merproject.org/mer-core/sd-utils/blob/master/rpm/sdcard-util... ) and 0.3.0.1-1 is the newest bleeding edge you want to install, see also https://openrepos.net/comment/10064#comment-10064 ). So I guess you tried to "update" which won't always work. To correctly install it you have to uninstall first, then install.
Skillmon
Sun, 2016/05/22 - 09:51
Permalink
Thank you for the fast reply. Now installation worked just fine!
eatdirt
Sun, 2016/05/08 - 23:20
Permalink
If I may, are you the V10lator of Q3arena and QuakeLive?
sorry if you're not!
If you are, I guess we shared a few hundred of frags together :D
cheers.
V10lator
Sun, 2016/05/22 - 09:12
Permalink
No, that's not me, sorry.
Just for reference, that's me on Steam: http://steamcommunity.com/id/V10lator
MoritzJT
Fri, 2015/10/23 - 13:56
Permalink
Does this need updating for SailfishOS 2.0.0.10?
Currently my f2fs partition won't mount, only my SWAP partition.
I have uninstalled the original utils and installed these instead but it won't mount my f2fs one.
BR
V10lator
Fri, 2015/10/23 - 14:27
Permalink
This doesn't need updating, but f2fs does (read on the description: "Compiled for kernel 3.4.106.20150416.1 (SailfishOS 1.1.6.27 - 1.1.9.28)").
Sorry to say but at the time of writing I can't update f2fs to 2.0.0.10 (kernel 3.4.108.20150901.1) as Jolla didn't release the kernel sources yet.
//EDIT: Yes, that means I also can't access my SD card atm. :(
MoritzJT
Fri, 2015/10/23 - 16:17
Permalink
Carsten (stskeeps on irc & elsewhere) offered to pull the kernel sources out if it is urgent, but he also said it might have to be done again then upon the final release. As I have no experience with this I didn't ask him to. Maybe you can be a better judge on the situation and get back to him on IRC
Thanks for the clarification though!
V10lator
Sat, 2015/10/24 - 15:52
Permalink
Updated f2fs. Have a nice day. :)
MoritzJT
Wed, 2016/07/20 - 23:34
Permalink
Hey, do you know whether we f2fs needs an update for Jolla C on 2.0.2.45? I can't seem to mount my SD card :-(
uname -r shows:
3.10.49+0.0.52.2
V10lator
Thu, 2016/07/21 - 10:55
Permalink
As the description of f2fs says it's compiled for kernel 3.4.108.20150901.1 and 3.4.108.20160401.1 so yes, it would need an update. But even if I would update it for the Jolla C I couldn't test it at all as I don't own the hardware, so I won't make a version for the Jolla C. Sorry about that. :(
Pages