You are not logged in.
Hi,
Thunar mounts my external disk correctly but it works for root and current user (the user who mounted the disk) while other users unable to read/write to the mounted disk.
How can I share mounted disk between users?
NOTE:
Thunar sets mount point to /media/<user>/<disk name> when I tried to change the owner of /media folder to 777 all users could see the mounted folder but can't read/write because Thunar sets the permissions to 644
I'm using: Linux Mint 17.2 x64 XFCE
Last edited by mbnoimi (2015-10-29 20:49:51)
Offline
I've same problem too and unfortunately I couldn’t find a permanent solution for it
Offline
Thunar uses gvfs for mounting and gvfs is a "userspace" tool - meaning its meant to be used within a user's profile (and not between or among users). What you are trying to do is going beyond its intent and design.
I think you'll need to look at something like fstab mounting or autofs to do the mounting. Maybe something like this.
Please remember to mark your thread [SOLVED] to make it easier for others to find
--- How To Ask For Help | FAQ | Developer Wiki | Community | Contribute ---
Offline
Maybe something like this.
jepp use umask=000 to share it with all users: eg my sdcard line
/dev/mmcblk0p1 /media/sdcard01 auto rw,user,auto,noatime,flush,umask=000 0 0
also pls keep in mind that systemd breaks fstab here, so you need to add "nofail" too or you will end up in a boot cycle!
Offline
Thunar uses gvfs for mounting and gvfs is a "userspace" tool - meaning its meant to be used within a user's profile (and not between or among users). What you are trying to do is going beyond its intent and design.
I think you'll need to look at something like fstab mounting or autofs to do the mounting. Maybe something like this.
Thanks for link but this is really exhausting procedure because whenever I mount an external disk I've to run the mentioned commands, don't forget that I'm using external disk not USB (I'm using ext4 disk format) and disk label always changes (/dev/sda1, /dev/dec2.. etc) so most practical solution is a GUI tool
Last edited by mbnoimi (2015-10-19 12:01:36)
Offline
and disk label always changes (/dev/sda1, /dev/dec2.. etc) so most practical solution is a GUI tool
then use uuids eg: http://linux.byexamples.com/archives/32 … with-uuid/
Offline
ToZ wrote:Maybe something like this.
jepp use umask=000 to share it with all users: eg my sdcard line
/dev/mmcblk0p1 /media/sdcard01 auto rw,user,auto,noatime,flush,umask=000 0 0
also pls keep in mind that systemd breaks fstab here, so you need to add "nofail" too or you will end up in a boot cycle!
I tried the following but the OS didn't boot well (it asked me for skip or manual mounting of my disk)... how can I fix this issue?
UUID=91b712b0-b5a7-4204-8d3c-3c1f2c23a82b /4TB auto rw,user,auto,noatime,flush,umask=000,nofail 0 0
I got the UUID using:
mbnoimi@mbnoimi-laptop ~ $ ls -l /dev/disk/by-uuid/
total 0
lrwxrwxrwx 1 root root 10 Oct 20 20:50 8382b8b4-0048-40b2-8185-042a80d3814e -> ../../sda3
lrwxrwxrwx 1 root root 10 Oct 20 20:52 91b712b0-b5a7-4204-8d3c-3c1f2c23a82b -> ../../sdb1
lrwxrwxrwx 1 root root 10 Oct 20 20:50 ba983c00-7453-41c3-8c43-f18024464a86 -> ../../sda6
mbnoimi@mbnoimi-laptop ~ $ cd /
mbnoimi@mbnoimi-laptop / $ ls -l
total 112
-rw-r--r-- 1 root root 0 Sep 20 11:40 0
drwxr-xr-x 2 root root 4096 Oct 20 20:39 4TB
drwxr-xr-x 10 mbnoimi mbnoimi 4096 Oct 13 10:15 Backup
drwxr-xr-x 2 root root 4096 Oct 19 22:29 bin
drwxr-xr-x 4 root root 4096 Oct 19 22:29 boot
drwxr-xr-x 2 root root 4096 May 28 09:50 cdrom
drwxr-xr-x 3 root root 4096 Jun 8 10:51 debian
drwxr-xr-x 18 root root 4700 Oct 20 20:52 dev
drwxr-xr-x 176 root root 12288 Oct 20 20:53 etc
drwxr-xr-x 6 root root 4096 Sep 11 16:44 home
lrwxrwxrwx 1 root root 33 May 29 10:41 initrd.img -> boot/initrd.img-3.19.0-18-generic
lrwxrwxrwx 1 root root 33 May 29 01:17 initrd.img.old -> boot/initrd.img-3.16.0-38-generic
drwxr-xr-x 26 root root 4096 Aug 4 03:58 lib
drwxr-xr-x 2 root root 4096 May 28 12:19 lib32
drwxr-xr-x 2 root root 4096 May 28 12:46 lib64
drwx------ 2 root root 16384 May 28 09:34 lost+found
drwxr-xr-x 4 root root 4096 Sep 19 19:49 media
drwxr-xr-x 3 root root 4096 Sep 22 10:20 mnt
drwxr-xr-x 9 root root 4096 Sep 20 11:40 opt
dr-xr-xr-x 239 root root 0 Oct 20 20:49 proc
drwx------ 15 root root 4096 Oct 10 18:46 root
drwxr-xr-x 33 root root 1040 Oct 20 20:54 run
drwxr-xr-x 2 root root 12288 Oct 19 22:28 sbin
drwxr-xr-x 2 root root 4096 Jan 7 2015 srv
dr-xr-xr-x 13 root root 0 Oct 20 20:49 sys
drwxrwxrwt 10 root root 4096 Oct 20 21:52 tmp
drwxr-xr-x 11 root root 4096 May 28 12:19 usr
drwxr-xr-x 12 root root 4096 Jul 6 15:39 var
lrwxrwxrwx 1 root root 30 May 29 10:41 vmlinuz -> boot/vmlinuz-3.19.0-18-generic
lrwxrwxrwx 1 root root 30 May 29 01:17 vmlinuz.old -> boot/vmlinuz-3.16.0-38-generic
mbnoimi@mbnoimi-laptop / $
Offline
May I get some help guys?
Thanks in advance
Offline
I'm using external disk not USB
eSATA?
Regards,
MDM
Offline
eSATA?
I use this external disk
Offline
don't forget that I'm using external disk not USB
I use
http://www.seagate.com/gb/en/external-hard-drives/desktop-hard-drives/backup-plus-desk/
Yeah... That's USB. It says so right there on the webpage you posted the link to.
BtW, wouldn't it be simple to just have whoever wants to use the thing plug it in themselves? It'll auto-mount when they do and they'll (presumably) be able to use it to their heart's content.
Regards,
MDM
Last edited by MountainDewManiac (2015-10-27 23:11:26)
Offline
BtW, wouldn't it be simple to just have whoever wants to use the thing plug it in themselves? It'll auto-mount when they do and they'll (presumably) be able to use it to their heart's content
I really didn't understand what did you mean!
I already know that Thunar auto mounts all plugged media but it mounts them inside user's profile. This is my issue
Offline
sorry I wasn't at home for a week
also your fstab line looks good, did you make the /4tb directory writeable for all user or users group?
>I tried the following but the OS didn't boot well (it asked me for skip or manual mounting of my disk)... how can I fix this issue?
hm thats new, could you pls describe it more eg exact message and when did it appear? eg fsck?
also how is your disk formated? ntfs? maybe then try to set it directly to ntfs-3g eg:
UUID=91b712b0-b5a7-4204-8d3c-3c1f2c23a82b /4TB ntfs-3g uid=$USERNAME,gid=users,umask=0022 0 0
also if this disk is formated with ntfs and if wasn't unmount correctly(safely remove) you might need to fix it with windows/chkdsk or use the ntfsfix linux utility.
PS tiny hint: you dont need to reboot after an fstab change you just need to run
mount -a
as root to test it!
Last edited by sixsixfive (2015-10-28 15:43:41)
Offline
did you make the /4tb directory writeable for all user or users group?
Yes, I set it to 777 as shown below
mbnoimi@mbnoimi-laptop ~ $ ls -l /
total 108
-rw-r--r-- 1 root root 0 Sep 20 11:40 0
drwxrwxrwx 2 mbnoimi mbnoimi 4096 Oct 20 20:39 4TB
hm thats new, could you pls describe it more eg exact message and when did it appear? eg fsck?
The error message appears on boot stage as shown in the following screenshot
After booting process (failed to mount the disk) I unable to mount it using Thunar so I tried to mount it using gnome-disk-utility but I got this error message
To fix this issue I modified mount option for this disk by enabling auto mount .. see the options before enable the option in the following screenshot:
Offline
hm seems to be an ubuntu specific issue but according to some forums it should go away if you add "nobootwait"
also could you pls post the output of "fdisk -l"
Offline
hm seems to be an ubuntu specific issue but according to some forums it should go away if you add "nobootwait"
also could you pls post the output of "fdisk -l"
Below the full log:
mbnoimi@mbnoimi-laptop ~ $ su
Password:
mbnoimi-laptop mbnoimi # cat /etc/fstab
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
# / was on /dev/sda6 during installation
UUID=ba983c00-7453-41c3-8c43-f18024464a86 / ext4 errors=remount-ro 0 1
# /home was on /dev/sda3 during installation
UUID=8382b8b4-0048-40b2-8185-042a80d3814e /home ext4 defaults 0 2
# swap was on /dev/sda5 during installation
#UUID=49634ec4-a711-4e69-bf50-2549c9a47104 none swap sw 0 0
/dev/mapper/cryptswap1 none swap sw 0 0
UUID=91b712b0-b5a7-4204-8d3c-3c1f2c23a82b /4TB auto rw,user,auto,noatime,flush,umask=000,nobootwait 0 0
mbnoimi-laptop mbnoimi # mount -a
mount: wrong fs type, bad option, bad superblock on /dev/sda1,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg | tail or so
mbnoimi-laptop mbnoimi # fdisk -l
Disk /dev/sdb: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders, total 976773168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk identifier: 0x9013285b
Device Boot Start End Blocks Id System
/dev/sdb1 * 2046 206723071 103360513 5 Extended
Partition 1 does not start on physical sector boundary.
/dev/sdb3 206723072 976771071 385024000 83 Linux
/dev/sdb5 2048 17268735 8633344 82 Linux swap / Solaris
/dev/sdb6 17270784 206723071 94726144 83 Linux
Note: sector size is 4096 (not 512)
Disk /dev/sda: 4000.8 GB, 4000787025920 bytes
255 heads, 63 sectors/track, 60800 cylinders, total 976754645 sectors
Units = sectors of 1 * 4096 = 4096 bytes
Sector size (logical/physical): 4096 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk identifier: 0x000c4020
Device Boot Start End Blocks Id System
/dev/sda1 256 976754431 3907016704 83 Linux
mbnoimi-laptop mbnoimi #
Offline
change the auto to ext4 and try again
also remove the flush and try adding defaults
if it still fails, check the disk/partition with fsck, parted, gparted etc.
Offline
change the auto to ext4 and try again
also remove the flush and try adding defaults
Did that, nothing changed. I got same error message:
mbnoimi-laptop mbnoimi # mount -a
mount: wrong fs type, bad option, bad superblock on /dev/sda1,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg | tail or so
mbnoimi-laptop mbnoimi #
if it still fails, check the disk/partition with fsck, parted, gparted etc.
The result of gparted:
GParted 0.18.0 --enable-libparted-dmraid --enable-online-resize
Libparted 2.3
Check and repair file system (ext4) on /dev/sda1 00:01:44 ( SUCCESS )
calibrate /dev/sda1 00:00:00 ( SUCCESS )
path: /dev/sda1
start: 256
end: 976754431
size: 976754176 (3.64 TiB)
check file system on /dev/sda1 for errors and (if possible) fix them 00:01:44 ( SUCCESS )
e2fsck -f -y -v -C 0 /dev/sda1
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
/lost+found not found. Create? yes
Pass 4: Checking reference counts
Pass 5: Checking group summary information
Media: ***** FILE SYSTEM WAS MODIFIED *****
745690 inodes used (0.31%, out of 244195328)
7229 non-contiguous files (1.0%)
106 non-contiguous directories (0.0%)
# of inodes with ind/dind/tind blocks: 0/0/0
Extent depth histogram: 742146/3525/10
524731488 blocks used (53.72%, out of 976754176)
0 bad blocks
102 large files
712046 regular files
33634 directories
0 character device files
0 block device files
0 fifos
0 links
0 symbolic links (0 fast symbolic links)
0 sockets
------------
745680 files
e2fsck 1.42.9 (4-Feb-2014)
grow file system to fill the partition 00:00:00 ( SUCCESS )
resize2fs -p /dev/sda1
resize2fs 1.42.9 (4-Feb-2014)
The filesystem is already 976754176 blocks long. Nothing to do!
========================================
As you can see above everything is OK but unfortunately fstab doesn't success
mbnoimi-laptop mbnoimi # cat /etc/fstab
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
# / was on /dev/sda6 during installation
UUID=ba983c00-7453-41c3-8c43-f18024464a86 / ext4 errors=remount-ro 0 1
# /home was on /dev/sda3 during installation
UUID=8382b8b4-0048-40b2-8185-042a80d3814e /home ext4 defaults 0 2
# swap was on /dev/sda5 during installation
#UUID=49634ec4-a711-4e69-bf50-2549c9a47104 none swap sw 0 0
/dev/mapper/cryptswap1 none swap sw 0 0
UUID=91b712b0-b5a7-4204-8d3c-3c1f2c23a82b /4TB ext4 rw,user,auto,noatime,umask=000,nobootwait 0 0
mbnoimi-laptop mbnoimi # mount -a
mount: wrong fs type, bad option, bad superblock on /dev/sda1,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg | tail or so
mbnoimi-laptop mbnoimi #
Offline
hm still strange also what displays " dmesg | tail" after "mount -a" fails?
Offline
hm still strange also what displays " dmesg | tail" after "mount -a" fails?
The full log:
mbnoimi@mbnoimi-laptop ~ $ su
Password:
mbnoimi-laptop mbnoimi # cat /etc/fstab
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
# / was on /dev/sda6 during installation
UUID=ba983c00-7453-41c3-8c43-f18024464a86 / ext4 errors=remount-ro 0 1
# /home was on /dev/sda3 during installation
UUID=8382b8b4-0048-40b2-8185-042a80d3814e /home ext4 defaults 0 2
# swap was on /dev/sda5 during installation
#UUID=49634ec4-a711-4e69-bf50-2549c9a47104 none swap sw 0 0
/dev/mapper/cryptswap1 none swap sw 0 0
UUID=91b712b0-b5a7-4204-8d3c-3c1f2c23a82b /4TB ext4 rw,user,auto,noatime,umask=000,nobootwait 0 0
mbnoimi-laptop mbnoimi # mount -a
mount: wrong fs type, bad option, bad superblock on /dev/sda1,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg | tail or so
mbnoimi-laptop mbnoimi # dmesg | tail
[80857.349316] [UFW ALLOW] IN= OUT=wlan0 SRC=192.168.1.4 DST=157.55.130.175 LEN=62 TOS=0x00 PREC=0x00 TTL=64 ID=31702 DF PROTO=UDP SPT=21918 DPT=40001 LEN=42
[80862.584199] [UFW AUDIT] IN= OUT=lo SRC=127.0.0.1 DST=127.0.0.1 LEN=60 TOS=0x00 PREC=0x00 TTL=64 ID=30826 DF PROTO=TCP SPT=49784 DPT=8123 WINDOW=43690 RES=0x00 SYN URGP=0
[80862.584211] [UFW AUDIT] IN=lo OUT= MAC=00:00:00:00:00:00:00:00:00:00:00:00:08:00 SRC=127.0.0.1 DST=127.0.0.1 LEN=60 TOS=0x00 PREC=0x00 TTL=64 ID=30826 DF PROTO=TCP SPT=49784 DPT=8123 WINDOW=43690 RES=0x00 SYN URGP=0
[80862.895796] [UFW ALLOW] IN= OUT=wlan0 SRC=192.168.1.4 DST=149.154.167.91 LEN=60 TOS=0x00 PREC=0x00 TTL=64 ID=4668 DF PROTO=TCP SPT=51885 DPT=443 WINDOW=29200 RES=0x00 SYN URGP=0
[80882.753777] [UFW AUDIT] IN= OUT=lo SRC=127.0.0.1 DST=127.0.0.1 LEN=60 TOS=0x00 PREC=0x00 TTL=64 ID=54652 DF PROTO=TCP SPT=49822 DPT=8123 WINDOW=43690 RES=0x00 SYN URGP=0
[80882.753812] [UFW AUDIT] IN=lo OUT= MAC=00:00:00:00:00:00:00:00:00:00:00:00:08:00 SRC=127.0.0.1 DST=127.0.0.1 LEN=60 TOS=0x00 PREC=0x00 TTL=64 ID=54652 DF PROTO=TCP SPT=49822 DPT=8123 WINDOW=43690 RES=0x00 SYN URGP=0
[80883.089556] [UFW ALLOW] IN= OUT=wlan0 SRC=192.168.1.4 DST=111.221.77.173 LEN=158 TOS=0x00 PREC=0x00 TTL=64 ID=16767 DF PROTO=UDP SPT=21918 DPT=40029 LEN=138
[80890.096993] EXT4-fs (sda1): Unrecognized mount option "umask=000" or missing value
[80902.553026] [UFW AUDIT] IN= OUT=lo SRC=127.0.0.1 DST=127.0.0.1 LEN=60 TOS=0x00 PREC=0x00 TTL=64 ID=13334 DF PROTO=TCP SPT=49872 DPT=8123 WINDOW=43690 RES=0x00 SYN URGP=0
[80902.553046] [UFW AUDIT] IN=lo OUT= MAC=00:00:00:00:00:00:00:00:00:00:00:00:08:00 SRC=127.0.0.1 DST=127.0.0.1 LEN=60 TOS=0x00 PREC=0x00 TTL=64 ID=13334 DF PROTO=TCP SPT=49872 DPT=8123 WINDOW=43690 RES=0x00 SYN URGP=0
mbnoimi-laptop mbnoimi # cat /etc/fstab
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
# / was on /dev/sda6 during installation
UUID=ba983c00-7453-41c3-8c43-f18024464a86 / ext4 errors=remount-ro 0 1
# /home was on /dev/sda3 during installation
UUID=8382b8b4-0048-40b2-8185-042a80d3814e /home ext4 defaults 0 2
# swap was on /dev/sda5 during installation
#UUID=49634ec4-a711-4e69-bf50-2549c9a47104 none swap sw 0 0
/dev/mapper/cryptswap1 none swap sw 0 0
UUID=91b712b0-b5a7-4204-8d3c-3c1f2c23a82b /4TB ext4 rw,user,auto,noatime,umask=0022,nobootwait 0 0
mbnoimi-laptop mbnoimi # mount -a
mount: wrong fs type, bad option, bad superblock on /dev/sda1,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg | tail or so
mbnoimi-laptop mbnoimi # dmesg | tail
[80922.536274] [UFW AUDIT] IN= OUT=lo SRC=127.0.0.1 DST=127.0.0.1 LEN=60 TOS=0x00 PREC=0x00 TTL=64 ID=20011 DF PROTO=TCP SPT=49904 DPT=8123 WINDOW=43690 RES=0x00 SYN URGP=0
[80922.536301] [UFW AUDIT] IN=lo OUT= MAC=00:00:00:00:00:00:00:00:00:00:00:00:08:00 SRC=127.0.0.1 DST=127.0.0.1 LEN=60 TOS=0x00 PREC=0x00 TTL=64 ID=20011 DF PROTO=TCP SPT=49904 DPT=8123 WINDOW=43690 RES=0x00 SYN URGP=0
[80922.636559] [UFW ALLOW] IN= OUT=wlan0 SRC=192.168.1.4 DST=157.56.52.27 LEN=62 TOS=0x00 PREC=0x00 TTL=64 ID=23332 DF PROTO=UDP SPT=21918 DPT=40016 LEN=42
[80943.232731] [UFW AUDIT] IN= OUT=lo SRC=127.0.0.1 DST=127.0.0.1 LEN=60 TOS=0x00 PREC=0x00 TTL=64 ID=29592 DF PROTO=TCP SPT=49932 DPT=8123 WINDOW=43690 RES=0x00 SYN URGP=0
[80943.232750] [UFW AUDIT] IN=lo OUT= MAC=00:00:00:00:00:00:00:00:00:00:00:00:08:00 SRC=127.0.0.1 DST=127.0.0.1 LEN=60 TOS=0x00 PREC=0x00 TTL=64 ID=29592 DF PROTO=TCP SPT=49932 DPT=8123 WINDOW=43690 RES=0x00 SYN URGP=0
[80963.760665] [UFW AUDIT] IN= OUT=lo SRC=127.0.0.1 DST=127.0.0.1 LEN=60 TOS=0x00 PREC=0x00 TTL=64 ID=5999 DF PROTO=TCP SPT=49961 DPT=8123 WINDOW=43690 RES=0x00 SYN URGP=0
[80963.760695] [UFW AUDIT] IN=lo OUT= MAC=00:00:00:00:00:00:00:00:00:00:00:00:08:00 SRC=127.0.0.1 DST=127.0.0.1 LEN=60 TOS=0x00 PREC=0x00 TTL=64 ID=5999 DF PROTO=TCP SPT=49961 DPT=8123 WINDOW=43690 RES=0x00 SYN URGP=0
[80982.595939] [UFW AUDIT] IN= OUT=lo SRC=127.0.0.1 DST=127.0.0.1 LEN=60 TOS=0x00 PREC=0x00 TTL=64 ID=2402 DF PROTO=TCP SPT=49993 DPT=8123 WINDOW=43690 RES=0x00 SYN URGP=0
[80982.595952] [UFW AUDIT] IN=lo OUT= MAC=00:00:00:00:00:00:00:00:00:00:00:00:08:00 SRC=127.0.0.1 DST=127.0.0.1 LEN=60 TOS=0x00 PREC=0x00 TTL=64 ID=2402 DF PROTO=TCP SPT=49993 DPT=8123 WINDOW=43690 RES=0x00 SYN URGP=0
[80992.646649] EXT4-fs (sda1): Unrecognized mount option "umask=0022" or missing value
mbnoimi-laptop mbnoimi #
Offline
>[80992.646649] EXT4-fs (sda1): Unrecognized mount option "umask=0022" or missing value
silly issue, umask is for fat/ntfs partitions, remove it and it should work
Offline
silly issue, umask is for fat/ntfs partitions, remove it and it should work
Thanks a lot the problem solved
Offline
[ Generated in 0.011 seconds, 7 queries executed - Memory usage: 688.35 KiB (Peak: 737.2 KiB) ]