NTFS Partitons not avail to users after 13.2 update

English Install/Boot/Login
1

:sarcastic:Ok, here it is! I have a duel boot opensuse 13.2 and windowsXP:shame:yes winXP!rotfl! Before my update to 13.2 my users were able to gain access to the windows partitons.
Now the only way to access those partitions is in (<file manager of your choice> Superuser). I beleive I found the answer on the web, but I wanted to bring it to the forum to make sure.
I’ve read that the Fstab file needs to be updated with the NTFS UID info first. /var/run/media/root/winxp1, winxp2 partitons.
I Don’t believe the the permissions can be changed on NTFS partition in terminal.

ERROR when accessing those NTFS partitions in normal user file manager says “could not enter folder /var/run/media/root/winxp”

yes the partiton are mounted and the GRUB works. I can boot both Op systems.

Thanks,
man

2

How are you mounting it?
Via an entry in /etc/fstab, or by just clicking on it in your file manager?

Please post the output of “mount”.

ERROR when accessing those NTFS partitions in normal user file manager says “could not enter folder /var/run/media/root/winxp”

Of course.
It is mounted for root, and only root can access that.
You have to unmount it as root, and then you should be able to mount (and access) it as user.

3

4 users are on the computer. Its happening when I select <winxp partition> in file manager.

mycomputerinfo:/ # mount
sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
devtmpfs on /dev type devtmpfs (rw,nosuid,size=2019964k,nr_inodes=504991,mode=755)
securityfs on /sys/kernel/security type securityfs (rw,nosuid,nodev,noexec,relatime)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
tmpfs on /run type tmpfs (rw,nosuid,nodev,mode=755)
tmpfs on /sys/fs/cgroup type tmpfs (rw,nosuid,nodev,noexec,mode=755)
cgroup on /sys/fs/cgroup/systemd type cgroup (rw,nosuid,nodev,noexec,relatime,xattr,release_agent=/usr/lib/systemd/systemd-cgroups-agent,name=systemd)
pstore on /sys/fs/pstore type pstore (rw,nosuid,nodev,noexec,relatime)
cgroup on /sys/fs/cgroup/cpuset type cgroup (rw,nosuid,nodev,noexec,relatime,cpuset)
cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup (rw,nosuid,nodev,noexec,relatime,cpu,cpuacct)
cgroup on /sys/fs/cgroup/memory type cgroup (rw,nosuid,nodev,noexec,relatime,memory)
cgroup on /sys/fs/cgroup/devices type cgroup (rw,nosuid,nodev,noexec,relatime,devices)
cgroup on /sys/fs/cgroup/freezer type cgroup (rw,nosuid,nodev,noexec,relatime,freezer)
cgroup on /sys/fs/cgroup/net_cls,net_prio type cgroup (rw,nosuid,nodev,noexec,relatime,net_cls,net_prio)
cgroup on /sys/fs/cgroup/blkio type cgroup (rw,nosuid,nodev,noexec,relatime,blkio)
cgroup on /sys/fs/cgroup/perf_event type cgroup (rw,nosuid,nodev,noexec,relatime,perf_event)
cgroup on /sys/fs/cgroup/hugetlb type cgroup (rw,nosuid,nodev,noexec,relatime,hugetlb)
/dev/sda6 on / type ext4 (rw,relatime,data=ordered)
systemd-1 on /proc/sys/fs/binfmt_misc type autofs (rw,relatime,fd=28,pgrp=1,timeout=300,minproto=5,maxproto=5,direct)
hugetlbfs on /dev/hugepages type hugetlbfs (rw,relatime)
debugfs on /sys/kernel/debug type debugfs (rw,relatime)
mqueue on /dev/mqueue type mqueue (rw,relatime)
/dev/sdb5 on /usr/local type ext4 (rw,relatime,data=ordered)
/dev/sda7 on /home type ext4 (rw,relatime,data=ordered)
/dev/sda8 on /var type ext4 (rw,relatime,data=ordered)
tmpfs on /var/run type tmpfs (rw,nosuid,nodev,mode=755)
tmpfs on /var/lock type tmpfs (rw,nosuid,nodev,mode=755)
binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc (rw,relatime)
fusectl on /sys/fs/fuse/connections type fusectl (rw,relatime)
/dev/sdb1 on /run/media/root/TAXIWAY type fuseblk (rw,nosuid,nodev,relatime,user_id=0,group_id=0,default_permissions,allow_other,blksize=4096,uhelper=udisks2)
/dev/sdb1 on /var/run/media/root/TAXIWAY type fuseblk (rw,nosuid,nodev,relatime,user_id=0,group_id=0,default_permissions,allow_other,blksize=4096)
/dev/sda1 on /run/media/root/WINDOWSXP type fuseblk (rw,nosuid,nodev,relatime,user_id=0,group_id=0,default_permissions,allow_other,blksize=4096,uhelper=udisks2)
/dev/sda1 on /var/run/media/root/WINDOWSXP type fuseblk (rw,nosuid,nodev,relatime,user_id=0,group_id=0,default_permissions,allow_other,blksize=4096)

this is info from “mount”

can that be unmounted in Yast partition manager?

Thanks
man

4

Please but computer generated text in code tags.# in editor window

Show

cat /etc/fstab

Are all 4 on at the same time or just 4 people use the machine and have their own accounts

You can change the parameters of the mount to allow user access (see man mount for details of all the options)

5

Those are your NTFS partitions:

They are mounted by udisks2, i.e. your desktop/filemanager.

So udisks2 takes care of the permissions, you shouldn’t have to change anything.
But as mentioned, they are mounted by root, probably because you started your filemanager as root to mount them in the first place.

can that be unmounted in Yast partition manager?

No.
You mounted them with udisks2, so unmount them with udisks2 again.
IOW, start the filemanager in super-user mode, right-click on the partitions and select “Unmount”.

Then start the filemanager as user and mount them again.
Post the output of “mount” again afterwards (in CODE tags, as gogalthorp mentioned… :wink: ).

6

Sorry about that I will. It’s just four family members, we each have an individual accounts used at different times.

cat /etc/fstab
/dev/disk/by-id/ata-SAMSUNG_HD321KJ_S0ZEJ1KP810714-part5 swap                 swap       defaults              0 0
/dev/disk/by-id/ata-SAMSUNG_HD321KJ_S0ZEJ1KP810714-part6 /                    ext4       acl,user_xattr        1 1
/dev/disk/by-id/ata-SAMSUNG_HD321KJ_S0ZEJ1KP810714-part7 /home                ext4       acl,user_xattr        1 2
/dev/disk/by-id/ata-SAMSUNG_HD321KJ_S0ZEJ1KP810714-part8 /var                 ext4       acl,user_xattr        1 2
/dev/cdrom                                               /media/cdrom0       udf,iso9660 user,noauto           0 0
/dev/disk/by-id/ata-WDC_WD3200AAKS-75VYA0_WD-WCARW2608872-part5 /usr/local           ext4       acl,user_xattr        1 2

Ok thanks
man

7

Ok, unmouting the winxp partitions in Root file manager is getting me there, but not quite there yet. In 13.1 it asked for authorization when I wanted to access the partition which was fine.
Now It starts to show the authorization process window then it goes away. I get this message at the top of the file manager, “an error occured while accessing the <winxp> the system respnded: you are not autherized to perform this operation.”

Here’s the info from mount.

/ # mount
sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
devtmpfs on /dev type devtmpfs (rw,nosuid,size=2019964k,nr_inodes=504991,mode=755)
securityfs on /sys/kernel/security type securityfs (rw,nosuid,nodev,noexec,relatime)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
tmpfs on /run type tmpfs (rw,nosuid,nodev,mode=755)
tmpfs on /sys/fs/cgroup type tmpfs (rw,nosuid,nodev,noexec,mode=755)
cgroup on /sys/fs/cgroup/systemd type cgroup (rw,nosuid,nodev,noexec,relatime,xattr,release_agent=/usr/lib/systemd/systemd-cgroups-agent,name=systemd)
pstore on /sys/fs/pstore type pstore (rw,nosuid,nodev,noexec,relatime)
cgroup on /sys/fs/cgroup/cpuset type cgroup (rw,nosuid,nodev,noexec,relatime,cpuset)
cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup (rw,nosuid,nodev,noexec,relatime,cpu,cpuacct)
cgroup on /sys/fs/cgroup/memory type cgroup (rw,nosuid,nodev,noexec,relatime,memory)
cgroup on /sys/fs/cgroup/devices type cgroup (rw,nosuid,nodev,noexec,relatime,devices)
cgroup on /sys/fs/cgroup/freezer type cgroup (rw,nosuid,nodev,noexec,relatime,freezer)
cgroup on /sys/fs/cgroup/net_cls,net_prio type cgroup (rw,nosuid,nodev,noexec,relatime,net_cls,net_prio)
cgroup on /sys/fs/cgroup/blkio type cgroup (rw,nosuid,nodev,noexec,relatime,blkio)
cgroup on /sys/fs/cgroup/perf_event type cgroup (rw,nosuid,nodev,noexec,relatime,perf_event)
cgroup on /sys/fs/cgroup/hugetlb type cgroup (rw,nosuid,nodev,noexec,relatime,hugetlb)
/dev/sda6 on / type ext4 (rw,relatime,data=ordered)
systemd-1 on /proc/sys/fs/binfmt_misc type autofs (rw,relatime,fd=28,pgrp=1,timeout=300,minproto=5,maxproto=5,direct)                                                                                                         
hugetlbfs on /dev/hugepages type hugetlbfs (rw,relatime)                                                       
debugfs on /sys/kernel/debug type debugfs (rw,relatime)                                                        
mqueue on /dev/mqueue type mqueue (rw,relatime)                                                                
/dev/sdb5 on /usr/local type ext4 (rw,relatime,data=ordered)                                                   
/dev/sda7 on /home type ext4 (rw,relatime,data=ordered)
/dev/sda8 on /var type ext4 (rw,relatime,data=ordered)
tmpfs on /var/run type tmpfs (rw,nosuid,nodev,mode=755)
tmpfs on /var/lock type tmpfs (rw,nosuid,nodev,mode=755)
binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc (rw,relatime)
fusectl on /sys/fs/fuse/connections type fusectl (rw,relatime)

I’m almost there i can feel it!

thanks
guys
man

8

Actually the default should be to not ask for authorization.
Have you changed the security settings?

Now It starts to show the authorization process window then it goes away. I get this message at the top of the file manager, “an error occured while accessing the <winxp> the system respnded: you are not autherized to perform this operation.”

Then you have a different problem. Probably your user session is not registered with logind.
What does “loginctl” show?
Does it work if you logout and login again?

Here’s the info from mount.

That’s useless, as you didn’t mount anything.

You could add an entry to /etc/fstab to mount the partitions during boot and allowing all users access simultanously, if you want to.
For this open YaST->System->Partitioner, click on the arrow in front of “Hard Disks” on the left, select the hard disk (sda or sdb in your case), click on the partition (sda1, sdb1), and click on “Edit…” on the right. In the appearing window, make sure “Do not format partition” is selected (important! But that should be the default anyway), activate “Mount partition”, enter a Mount Point of your choice (do not choose one from the list, I would recommend to enter /windows/C and /windows/D or similar), click on “Fstab Options…” and empty the “Arbitrary Option Value” field if there’s text in it (otherwise you probably won’t have write access).
You can of course change other settings to your likings, but please ask first if you are unsure, otherwise you might cause data loss!
Click OK and Finish and the partitions should be mounted at boot, accessible by all users.

But if there’s a problem with registering your user session, you will other issues as well, not just the mounting.

9

Ok you are not mount any NTFS by default. That is where you want to put them. If you don’t want to edit the fstab then just do it in Yast - partitions module

Use the nofail option if the file system may not be attached at boot use the user option to allow all users. Note be sure the mount point (where every you intend it) permission is set to allow user group

10

“Then start the filemanager as user and mount them again.” there is no selection to mount, but i do remeber that before the upgrade there was a mount selection in the user file manager.

loginctl showed

mycomputerinfo:/ # loginctl
   SESSION        UID USER             SEAT            
         1       1000 userme           seat0           

1 sessions listed.

I have not changed any security setting since upgrade. Also in security settings you can select home, network workstation, network server, mine is custom settings
I looked at the mount points before posting error and they are mounted as NTFS_windows_myname_partitions.
It seems like what needs to happen is a authorization for users to access those winxp_partitions is needed.

thanks
man

11

Just click on the partition in the left pane to mount it.

loginctl showed

mycomputerinfo:/ # loginctl
   SESSION        UID USER             SEAT            
         1       1000 userme           seat0

1 sessions listed.

Ok, then it should actually work.

I have not changed any security setting since upgrade. Also in security settings you can select home, network workstation, network server, mine is custom settings

I looked at the mount points before posting error and they are mounted as NTFS_windows_myname_partitions.
It seems like what needs to happen is a authorization for users to access those winxp_partitions is needed.

Ah I see, sorry. This is an internal disk, right?
Then yes, you normally would need the root password to mount it.

In that case, it might be more convinient to add it to the fstab, as described.
Or you can also turn off the need for the root password if you want to.

12

You said
“Ok you are not mount any NTFS by default. That is where you want to put them. If you don’t want to edit the fstab then just do it in Yast - partitions module”

I was very careful to head all warnings. I named the mount point/windows/C or D and fstab option made it mountable by users. without formatting. I recieved this error.

Failure occurred during the folowing action
Mounting/dev/sdb1 to /windows/D

System error code was -3003

/bin/mount -t ntfs-3g -o user,user,gid=users,fmask=133,dmask=022,locale-=en_us.utf-8 '/dev/sdb1 ' ' /windows/D:
mount: failed to parse mount options

continue despite the error.

I aborted the command! until I posted it here.

thanks
man

13

Where in the world did you get those options LOL

I don’t have ntfs here to test so I’ll let other explain your errors

14

Hm. Is this a bug in YaST? Or maybe you entered some things into the wrong text field…

I’d suggest to open /etc/fstab in a text editor then:

kdesu kwrite /etc/fstab

You should see a line like this in there:

/dev/sdb1            /windows/D           ntfs-3g    user,user,gid=users,fmask=133,dmask=022,locale-=en_us.utf-8         0 0

Change the line to:

/dev/sdb1            /windows/D           ntfs-3g    defaults              0 0

(if the line does not exist, add one like I posted)

If in doubt, post the /etc/fstab and I’ll tell you what to change.

15

:sarcastic:Ok wow! Something is wrong somewhere I tried to run <kdesu> this is what I got. Oh yeah I was SU when performing this request in terminal.

/ # kdesu kwrite /etc/fstab
kdesu(2315)/kdeui (kdelibs): Session bus not found 
To circumvent this problem try the following command (with Linux and bash) 
export $(dbus-launch) 
KCrash: Application 'kdesu' crashing...
KCrash: Attempting to start /usr/lib64/kde4/libexec/drkonqi from kdeinit
KCrash: Connect sock_file=/root/.kde4/socket-aldierihomestead/kdeinit4__0

[1]+  Stopped                 kdesu kwrite /etc/fstab

And if i just open the fstab file in KWrite in file manager this is the info there

/dev/disk/by-id/ata-SAMSUNG_HD321KJ_S0ZEJ1KP810714-part5 swap                 swap       defaults              0 0
/dev/disk/by-id/ata-SAMSUNG_HD321KJ_S0ZEJ1KP810714-part6 /                    ext4       acl,user_xattr        1 1
/dev/disk/by-id/ata-SAMSUNG_HD321KJ_S0ZEJ1KP810714-part7 /home                ext4       acl,user_xattr        1 2
/dev/disk/by-id/ata-SAMSUNG_HD321KJ_S0ZEJ1KP810714-part8 /var                 ext4       acl,user_xattr        1 2
/dev/cdrom                                               /media/cdrom0       udf,iso9660 user,noauto           0 0
/dev/disk/by-id/ata-WDC_WD3200AAKS-75VYA0_WD-WCARW2608872-part5 /usr/local           ext4       acl,user_xattr        1 2

I’m going to step out for awhile, let all of us give this some thought. I’ll be back later. I’m central time US.:\

16

Yep that is not right something borked somewhere. Try using a command line text editor. I think nano is default installed maybe or joe or vi if you can deal with it

17

You have to run “kdesu kwrite /etc/fstab” as user!
The point of kdesu is to get root permissions. No sense in running it as root, and it won’t work when you switch to root via su before anyway.

And if i just open the fstab file in KWrite in file manager this is the info there

So the entry is not added yet.
Then add exactly those lines:

/dev/sda1            /windows/C           ntfs-3g    defaults,nofail              0 0
/dev/sdb1            /windows/D           ntfs-3g    defaults,nofail              0 0
18

Did not notice he was root for the call LOL

19

Alright I updated the entries to fstab to no avail. The authorization request still shows up for a breif second then it goes away. If it would stay that would be fine. I’m ok with entering in my info.

thanks
man

20

Maybe show us the new fstab.