Access windows partition without entering the password every day? - Addition

This is an addition to the closed topic:
(Access windows partition without entering the password every day?)

Thank you for your help. The suggested way worked for me with one little change: I had to specifiy “ntfs” not “ntfs3” for the file system type. Apparently, ntfs3 is not existing/supported in Leap16.

When trying ntfs3 at first, the Laptop would not boot up anymore, which freaked me out for a moment. But after the error message concerning the failed mount a way for editing the fstab was explained that worked (editing the file in a minimized text based operating system).

Now, everything works fine.

Thank you.

1 Like

For Leap 16, the ntfs-3g package can be installed, as it provides the required FUSE NTFS support.

References:
man ntfs-3g
https://en.opensuse.org/SDB:NTFS
https://wiki.archlinux.org/title/NTFS-3G

@flo37 See https://en.opensuse.org/SDB:FilesystemBlacklisting just be aware ntfs and ntfs3 are unsupported.

@deano_ferrari the SDB you pointed to was last edited on 22 June 2019 :wink:

I know, but it was just another reference to the ntfs-3g fuse-based NTFS support that still exists for cases where where native ntfs3 isn’t available. The arch wiki reference is still good too. :wink:

Just a note for the casual user and a disclaimer: I am no filesystem expert, so please correct me if I’m wrong.

The original thread is about fstab and the “filesystem type” to be entered in fstab is “ntfs” (see man fs or man fstab) not ntfs3.
The openSUSE kernels do not ship a “ntfs” module (not even in Tumbleweed, even if a “new” ntfs module is available upstream for kernels 7.1.x and up).
The openSUSE kernels for Leap 16.0 (currently at 6.12.0-160000.38) do not ship a ntfs3 module and if it were it is blacklisted anyway (see the reference provided by Malcolm above).
The openSUSE kernels for Tumbleweed (currently 7.2.7) ship a ntfs3 module, but that module is blacklisted .

So I think that on a standard Leap 16.0 an ntfs filesystem is mounted in user space anyway.
[Sorry, I cannot check, no ntfs media nearby at the moment :wink: ]

That’s why I use ntfs-3g on my Leap install (as I have done with earlier openSUSE releases for several years) when the occasional need arises.

As the OP was able to mount it before he asked in the other post, it is easy enough to check the file system type used by that mounting. And then using the same in the fstab entry.

Not much research needed I would say.

1 Like

Thank you for these additional explanations.
Just to make it very clear to me: The mounting with “ntfs” in the fstab seems to work fine now. Should I await a problem, and therefore switch to “ntfs-3g”, or is “ntfs” fine?

The original mount via Dolphin only gives an entry in mtab, not in fstab. The entry in mtab reads:

/dev/nvme0n1p3 /run/media/<username>/<foldername> fuseblk rw,nosuid,nodev,relatime,user_id=0,group_id=0,default_permissions,allow_other,blksize=4096 0 0

So, ‘fuse’ covers the file system type.

The Dolphin entry you showed indicates that the filesystem was mounted through FUSE, which is consistent with ntfs-3g. The fact that it appears in /etc/mtab is expected for a mount performed dynamically by Dolphin.

mtab contains what is mounted at that moment in time (the same items as shown by mount command).

/etc/fstab is a configuration file (for mount and umount) what is in there should be mounted at boot (except when options tell not to mount this one at boot).

I have two NTFS partitions that I can accesss without having to put in a password. They mount from /etc/fstab. The mount options can be done in different ways, depending on your needs. This works for me as this is a single user PC. If needed, you could use a credentials file, but I don’t need that.

I use lsblk -ao uuid,label,fstype,size,path,owner,ro to show what I need to mount them in /etc/fstab. The ro column means read only and it will show as a 1 if it is mounted read only.

╔═⦗😀wilson@heisenberg⦘ Thu Oct 01, 04:50:18 [~]
╚═⦗<$> lsblk -ao uuid,label,fstype,size,path,owner,ro
UUID                                 LABEL    FSTYPE   SIZE PATH           OWNER RO
                                                       3.7T /dev/sda       root   0
39b03129-e367-435e-bd00-090522febc32 4TB-SSD1 ext4     3.7T /dev/sda1      root   0
                                                       3.7T /dev/sdb       root   0
f6dc5246-db2e-4ed7-a27c-edccf91c351d 4TB-SSD2 ext4     3.7T /dev/sdb1      root   0
                                                       3.6T /dev/sdc       root   0
36A2F6336AC254FB                     4TB-HDD  ntfs     3.6T /dev/sdc1      root   0  # This is one of them
a61c1088-653f-4851-b7f9-3b8d4f373c71          swap    30.5G /dev/zram0     root   0
                                                     953.9G /dev/nvme0n1   root   0
F95A-5ABC                                     vfat       1G /dev/nvme0n1p1 root   0
a272aac9-323b-408d-a761-7f537ba376e5 System   btrfs  952.9G /dev/nvme0n1p2 root   0
                                                     931.5G /dev/nvme1n1   root   0
                                                        16M /dev/nvme1n1p1 root   0
5CDEF0D6DEF0AA02                     Windows  ntfs   930.7G /dev/nvme1n1p2 root   0  # This is one of them.
5C92341F9233FFD6                              ntfs     815M /dev/nvme1n1p3 root   0  # This is a hidden restore partition and I don't mount it.
# /etc/fstab: static file system information.
#
# <file system>                           <mount point>  <type>     <options>                           <dump> <pass>
UUID=a272aac9-323b-408d-a761-7f537ba376e5   /             btrfs     defaults                                 0 0 
UUID=a272aac9-323b-408d-a761-7f537ba376e5   /var          btrfs     subvol=/@/var                            0 0 
UUID=a272aac9-323b-408d-a761-7f537ba376e5   /usr/local    btrfs     subvol=/@/usr/local                      0 0 
UUID=a272aac9-323b-408d-a761-7f537ba376e5   /srv          btrfs     subvol=/@/srv                            0 0 
UUID=a272aac9-323b-408d-a761-7f537ba376e5   /root         btrfs     subvol=/@/root                           0 0 
UUID=a272aac9-323b-408d-a761-7f537ba376e5   /opt          btrfs     subvol=/@/opt                            0 0 
UUID=a272aac9-323b-408d-a761-7f537ba376e5   /home         btrfs     subvol=/@/home                           0 0 
UUID=a272aac9-323b-408d-a761-7f537ba376e5   /.snapshots   btrfs     subvol=/@/.snapshots                     0 0 
UUID=F95A-5ABC                              /boot/efi     vfat      utf8,dmask=0077                          0 2 
#
#
UUID=39b03129-e367-435e-bd00-090522febc32   /4TB-SSD1     ext4      nofail,users,rw                          0 0 
UUID=f6dc5246-db2e-4ed7-a27c-edccf91c351d   /4TB-SSD2     ext4      nofail,users,rw                          0 0 
UUID=36A2F6336AC254FB                       /4TB-HDD      ntfs-3g   nofail,uid=1000,gid=1000,windows_names   0 0    # This is one of them
UUID=5CDEF0D6DEF0AA02					    /Windows      ntfs-3g   nofail,uid=1000,gid=1000,windows_names   0 0    # This is one of them

If you look at the mount point /Windows and the mount point /4TB-HDD, those must have folders/directories existing. You will have to create them.

I cannot edit the post after 15 minutes, but as far as type, I mount them as ntfs-3g so I can write to them. ntfs will mount them, but they will be read only.

I may be wrong, but I thought ntfs was aliased to ntfs-3g on openSUSE?

I don’t know. I was using ntfs-3g on other distros. I will have to remove it and test it.

Yes, on openSUSE, ntfs can be handled by the mount.ntfs helper.

You can run update-alternatives --display mount.ntfsand will show what it points to.

For example I currently have

~> /usr/sbin/update-alternatives --display mount.ntfs
mount.ntfs - auto mode
  link best version is /usr/sbin/mount.ntfs-3g
  link currently absent
  link mount.ntfs is /usr/sbin/mount.ntfs
  slave mount.ntfs.8.gz is /usr/share/man/man8/mount.ntfs.8.gz
/usr/sbin/mount.ntfs-3g - priority 10
  slave mount.ntfs.8.gz: /usr/share/man/man8/mount.ntfs-3g.8.gz
~>

As far as I know NTFS was refactored in Kernel 7.1 but it’s still blacklisted on openSUSE for some reason, I’m not sure why.

Apparently it does indeed work with just ntfs. That was the first time I had heard of it being aliased.

Read:

I just login to my window partition when I need to. If you wish to be always logged in to windows partition, I’d think you need to set that up in windows password/login administration somewhere. I don’t think linux can just login to windows w/o permission.

tom kosvic

> > update-alternatives --display mount.ntfs
update-alternatives: error: no alternatives for mount.ntfs

Still, mounting with just “ntfs” works for me - including write permission.