SliTaz Forum
You are not logged in.
Hi,
Using 5.0-RC2 I'm unable to mount an NTFS partition as a user:
[c]> mount /win/D
Unprivileged user can not mount NTFS block devices using the external FUSE
library. Either mount the volume as root, or rebuild NTFS-3G with integrated
FUSE support and make it setuid root. Please see more information at
http://tuxera.com/community/ntfs-3g-faq/#unprivileged[/c]
(The fstab entry is:
[c]/dev/sda2 /win/D ntfs-3g defaults,noauto,user 0 2[/c]
and access rights of /win/D are 777.)
May a dev do this ("rebuild...")?
Thanks.
PS: should I post RFEs to the bug tracker instead?
Offline
Post requests here.
http://hg.slitaz.org/wok/rev/b0977e588407
http://cook.slitaz.org/packages/ntfs-3g-2014.2.15.tazpkg
Offline
@mojo
/bin/ntfs-3g: 44k -> 112k
/bin/lowntfs-3g 47k -> 83k
Does a 'chmod 4755 /bin/ntfs-3g /bin/lowntfs-3g' do the job ?
Offline
Thanks mojo.
@Bellard: no, it doesn't. I tried before posting my RFE!
If you set the setuid bit the message changes into something like "mount is disabled because ntfs-3g is setuid root but wasn't compiled with FUSE support" ;-)
Indeed it is a big change in size. I don't know if this prevents mounting NTFS flash drives in pcmanfm, I'll try and report. (What I tried was mounting said partition from a terminal.)
Offline
this seams to be pcmanfm related - I am still on spacefm + udevil and I can mount my ntfs files without any problems.
Maybe you just need to install ntfsprogs - I have to install ntfsprogs, when I want to use partimage with ntfs files - also gparted needs ntfsprogs to handle ntfs partitions correctly.
Offline
So, I tried to plug in a NTFS-partitioned flash drive. Results:
- if it is not listed in fstab, it doesn't show up at all in pcmanfm's left panel! (dmesg does report a device on sdb with one partition)
- if it is listed in fstab, it shows up as usual (not mounted) in the left panel, and a click on it pops up an error window with the same message as obtained in a terminal ("Unprivileged user...").
@kultex: the problem I reported in my first post is independant of the file manager. Maybe your setup works around it by automounting, so you don't need to manually mount in the first place. Do you unmount without problems also?
I also have a problem with pcmanfm and mounting: removable media don't automount (although the relevant boxes are checked in Prefs). I prefer not to post a new thread about it because solving it might tamper the need for user-mounting of NTFS, as kultex suggested.
BTW I do have ntfsprogs installed.
Offline
@Bellard
Mounting as regular user works with ntfs-3g and lowntfs-3g using integrated driver
Auto-mount of ntfs flash drive by udisks2/gvfs-fuse in pcmanfm works in full install and booting into core iso built with ntfs-3g with integrated fuse.
If size is a problem a ntfs-3g-fuse tazpkg with integrated driver could be added to the repo as a user option and the isos built with a smaller ntfs-3g tazpkg with fuse external.
Offline
!! PLEASE !! dont mess up things....
1) RC2 is "shi." and really needs to be replaced - !!! urgent!!! - because there was troubles with polkit roules. This was corrected in first rolling after RC2 - it was working in all rollings after RC" - also automount!!
see: http://forum.slitaz.org/topic/pcmanfm-mount-devices-as-user
Offline
Hi kultex,
What do you mean by "first rolling"? I thought that rolling meant just that: something that rolls, not something that steps! So that each commit would correspond to a "new rolling". Am I wrong?
Also, isn't installing RC2 then doing tazpkg recharge+tazpkg up equivalent to the rolling ISO?
As regards what you call "sh*t", the end of the thread you cite seems to show automounting works in RC2. Doesn't it?
Offline
Hi llev,
isn't installing RC2 then doing tazpkg recharge+tazpkg up equivalent to the rolling ISO?
Not always, to be more exact. TazPkg preserves original configuration files. So you may finished to have newest packages installed with old RC2 configs. Yes, it's a pain.
Offline
@llev
you can see, when a new rolling is cooked here
http://cook.slitaz.org/cookiso.cgi
so you see, that it is cooked at the moment evry week
release date of RC2 was 19 May 2014 - so first rolling after RC2 was done about 20. - 27. May
Offline
Hi all,
Thanks @ Aleksej & kultex for explanations. I guess I'll find the latest config files in the rolling rootfs. But which ones are relevant to my current problem? I've adjusted many config files to have Slitaz work on my PC, so I don't want to scratch everything.
Yesterday I discovered udisksctl. It manages to mount NTFS partitions, taking into account the mountpoint and options specified in fstab. So, all in all, I see two seemingly distinct problems:
- pcmanfm obviously doesn't rely on udisks to mount devices;
- "someone" (pcmanfm or the kernel or ?) should try to automount new devices but doesn't.
Any help is appreciated.
Offline
you have to check all the things from here:
http://forum.slitaz.org/topic/pcmanfm-mount-devices-as-user/page/2
Offline
@kultex: checked the cited topic, everything was OK.
Then I did a recursive diff between my /etc and the last rolling /etc. Didn't find anything relevant, except in tazlito/distro-packages.list which gave me the good hint: gvfs-udisks2 was not installed.
Now that gvfs-udisks2 is installed, automounting works (at least for fat and squashfs, couldn't test NTFS yet).
But now pcmanfm doesn't show my fstab entries in its left panel anymore! Please help (again)!
Offline
Hi llev,
PCManFM not shows entries from /etc/fstab by design. It shows only removable media.
If you need it, you can add bookmarks to your mount points to the left panel.
Offline
Hi Aleksej,
Yes, it did it in Slitaz 4 and it still did in 5RC2 before installation of gvfs-udisks2.
Adding the mount point to bookmarks doesn't do the trick, because it simply adds the empty mount folder, and clicking on it doesn't mount the relevant device.
(I'll try to revert back to the old behaviour and take screenshots.)
Offline
Here you are: first, without gvfs-udisks2, two screenshots to show the old, wanted behaviour(*); the third screenshot shows what pcmanfm displays when gvfs-udisks2 is installed.
(*) What's wanted is that pcmanfm shows fstab entries.
[attachment=35911,1848] [attachment=35911,1849] [attachment=35911,1850]
Offline
Hi Lucas,
Oh sorry, I forgot about "noauto" option. So, I mistakenly decide that partition should mounts on booting, if you add entry into your /etc/fstab file.
Currently, my SliTaz is semi-broken. Internal HDD partitions mounts well on boot, but mounting of external USB Flash works in half of times. Seems it not works in present week 
Sorry, I don't know even is it works in our upstream, Rolling release, or not.
Searching the net for "PCManFM /etc/fstab" I not found something relevant dated not too old. Maybe this topic will be helpful:
http://forum.slitaz.org/topic/pcmanfm-mount-devices-as-user
Or not. So sorry, I can not help you with this problem.
Offline
Connected drives should appear in left pane of pcmanfm.
If they are mounted by either clicking on the drive icon or auto-mounted by /etc/fstab there is an up arrow umount/eject icon.
There are no drives showing with_gvfs-udisks2.png
[c]tazpkg -gi udisks2 --forced[/c]
These 2 threads have more possible solutions if needed:
http://forum.slitaz.org/topic/rc2-usb-wont-automount
http://forum.slitaz.org/topic/automountinternal-drive-icons-doesnt-work-anymore-in-pcmanfm
Offline
Hi mojo,
Thanks for the hints. Alas, still no luck. I purged cache and reinstalled all installed gvfs-*, udisks2, and pcmanfm.
[c]~> tazpkg list|grep gvfs
gvfs 1.22.1 system-tools
gvfs-dev 1.22.1 development
gvfs-fuse 1.22.1 system-tools
gvfs-udisks2 1.22.1 system-tools[/c]
Is it enough?
I have no message when launching pcmanfm form a terminal.
Offline
I experienced the bug on one of my slitaz full installs after a recent update. When I installed udisks2 --forced from the package cache and rebooted my attached drives appeared again in pcmanfm.
Maybe some error messages when starting pcmanfm in terminal?
Open a terminal
Type
pcmanfm
Hit enter
Post any error messages.
Offline
Just after reinstalling packages, and before rebooting, I got a warning like "missing modules" or "unable to find modules", but now that I have rebooted I get no message anymore (so I think the warning was a transient effect).
What's the date of your kernel?
Offline
To be complete, I also reinstalled slim and slitaz-configs-base, as suggested in one of the thread you cite. I also reinstalled again udisks2. Rebooted after all that. Still no joy, and no error message when launching pcmanfm from a terminal.
But there's still some hope: when I launch pcmanfm as root it works as expected, with the following warning:
[c]root@slitaz:/home/tux # pcmanfm
Error creating proxy: La connexion est fermée (g-io-error-quark, 18)
** (pcmanfm:1300): WARNING **: modules directory is not accessible
match profile: viewnior_on_folder
match profile: viewnior_on_images
match profile: gpicview_on_folder
match profile: image_wallpaper
match profile: on_archive
match profile: root_on_folder
match profile: gvfs-info
match profile: any
match profile: file_root_edit[/c]
I can't see why it works as root and not as tux.
[c]~> groups
users tty disk floppy video cdrom audio plugdev dialout scanner camera[/c]
The only groups tux is not a member of are: root, daemon, bin, sys, adm, lp, kmem, wheel, tape, www, nogroup, messagebus, haldaemon.
Offline
as nobody answers I try to continue, but I have no idea about pcmanfm, because I hate pcmanfm
first can you post the output of: $ df - as an example my output:
tux@slitaz:~ $ df
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 646360 280 646080 0% /run
tmpfs 1163452 462672 700780 40% /
devtmpfs 427892 0 427892 0% /dev
tmpfs 646360 0 646360 0% /dev/shm
/dev/sdb2 21212392 13920532 6214308 69% /home
/dev/sdb1 2030928 35792 1891968 2% /media/slitaz-root
/dev/sdb3 7529084 147872 6998748 2% /media/save
/dev/sdc1 7827424 7166388 661036 92% /media/BOOTCD_USB
/dev/sda3 15217664 168816 14275832 1% /media/sda3-ata-PHOTOFAST18CF_32
/dev/sda2 5477920 1341056 4136864 24% /media/sda2-ata-PHOTOFAST18CF_32
/dev/sda1 9438156 6288377 3149779 67% /media/sda1-ata-PHOTOFAST18CF_32
second the output of: ls -l /folder of your fstab disk
as an exemple - spacefm und udevil mounts evrything in /meda - it should be something like this
tux@slitaz:~ $ ls -l /media
total 28
drwxr-xr-x 29 tux users 8192 Jan 1 1970 BOOTCD_USB
drwxr-xr-x 2 root root 40 Jan 17 2013 cdrom
drwxr-xr-x 2 root root 40 Jan 17 2013 flash
drwxr-xr-x 3 root root 4096 Dec 4 2013 save
drwxrwxrwx 1 tux users 4096 Jan 25 13:02 sda1-ata-PHOTOFAST18CF_32
drwxr-xr-x 9 tux users 4096 Jan 1 1970 sda2-ata-PHOTOFAST18CF_32
drwxr-xr-x 3 root root 4096 Aug 16 2013 sda3-ata-PHOTOFAST18CF_32
drwxr-xr-x 3 root root 4096 Dec 4 2013 slitaz-root
drwxr-xr-x 2 root root 40 Jan 17 2013 usbdisk
and third output as root of #fdisk -l
root@slitaz:/home/tux1 fdisk -l
Disk /dev/sda: 32.0 GB, 32019316736 bytes
255 heads, 63 sectors/track, 3892 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/sda1 * 1 1285 10319836+ 7 HPFS/NTFS
/dev/sda2 1285 1969 5488640 c Win95 FAT32 (LBA)
/dev/sda3 1969 3893 15460352 83 Linux
Disk /dev/sdb: 32.0 GB, 32015679488 bytes
64 heads, 32 sectors/track, 30532 cylinders
Units = cylinders of 2048 * 512 = 1048576 bytes
Device Boot Start End Blocks Id System
/dev/sdb1 2 2016 2063360 83 Linux
Partition 1 does not end on cylinder boundary
/dev/sdb2 2017 23062 21551104 83 Linux
Partition 2 does not end on cylinder boundary
/dev/sdb3 23063 30532 7649280 83 Linux
Partition 3 does not end on cylinder boundary
Disk /dev/sdc: 8032 MB, 8032092160 bytes
255 heads, 63 sectors/track, 976 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/sdc1 * 1 977 7843808+ c Win95 FAT32 (LBA)
Partition 1 has different physical/logical endings:
phys=(975, 254, 63) logical=(976, 130, 50)
this would help to check, if there is something wrong with permission
and lst but not least can you install spacefm and tell if you have the same problems there....
Offline
Thanks kultex for your help. Here's my report with respect to spacefm.
Spacefm can be set up to show the internal devices, but it fails to mount them with the message "udevil: denied 88: device /dev/sda1 is an internal device and you're not root", although sda1 has option "user" in fstab.
When hotplugging a NTFS USB key, I get:
"Error mounting system-managed device /dev/sdb1: Command-line `mount "/media/NTFS_part"' exited with non-zero exit status 18: Failed to write lock '/dev/sdb1': Resource temporarily unavailable
Error opening '/dev/sdb1': Resource temporarily unavailable
Failed to mount '/dev/sdb1': Resource temporarily unavailable",
but the key ends up mounted RW! However the masks specified in fstab are ignored.
When hotplugging a two partition USB key (FAT+squashfs), I get errors saying the partitions are already mounted, but they are correctly mounted (masks are applied to the FAT partition).
EDIT : about hotplugged devices, forget it, there must have been severe interference with pcmanfm!
Offline
[ Generated in 0.019 seconds, 7 queries executed - Memory usage: 1.6 MiB (Peak: 1.77 MiB) ]