Hi everyone, I hope my message will be clear enough because it’s the first time I’m writing here ! Also english is not my native language. Anyway, I’m on Manjaro KDE Stable, Kernel 6.18, nVidia GPU.
The update went well as far as I did not had a warning as the end. I’m not sure how to read the full update log for the moment.
The system boots without any issue, but there is something special : I have suddenly troubles to mount a NTFS disk that usually is mounted on boot.
Here are the issues : As I could not launch a game that was installed on this drive, I opened Dolphin to check in /mnt if I could access it. The folder was empty.
I use “Gnome disk” to check if the disk is mounted or not, but when I try to mount it, I have the following message :
It’s surprising because “hide_hidden_files” was working in my fstab since my first Manjaro install one year ago more or less. When deleting this parameter in the fstab line, I can access the disk in Dolphin but in read-only mode, So I’m not able to use the softwares on it as usual, nor my Windows 10 VHD in Virtualbox.
I’m sure that the issue went during or just after the update because I was able to use this disk everyday the days before.
Is anyone encountering this issue ? And sorry if it’s not the correct place for this message, but as it seems linked to the update…
Note that if I don’t find a solution I will use TimeShift to go back and apply the update later
Thank you for the suggestion, you are correct, I wrote “hidden” but the setting seems to be “hide_hid_files” because I can find it on two trustworthy sources (Fstab/fr - Manjaro) and (ntfs-3g(8) — ntfs-3g — Debian bookworm — Debian Manpages). But It don’t seems to work, I always have the same message…
Apart of that, I can easily delete this optional setting and this is what I have on fstab for this specific NTFS disk :
/dev/disk/by-uuid/80A6D052A6D049F4 /mnt/80A6D052A6D049F4 auto defaults,windows_names,relatime,nosuid,nodev,nofail,x-gvfs-show 0 0
I tried with another NTFS disk on external USB that I use sometimes, mainly for backups : exactly the same result, I have to delete “hide_hid_files” and then I’m on read only…
It’s not that important for me to hide the Windows hidden file as I’m not browsing a lot in this disk. So let’s forget about this setting and now I have to find why I’m suddenly in read only …
I found the command needed to know the privileges of each folders and file, this is the result below :
The reason for keeping the old line but commenting it out, rather than just replacing it, is that this makes it much easier to revert if there are any issues (and for any experimentation).
Remount (easiest just to reboot) and re-check. Hopefully this will have the desired result.
I thought the windows_names might still be needed; not dealt with that side of things for years. I know it used to be an issue. I didn’t spot the relatime though. Guess that had been auto-generated by a GUI partition manager.
For my external USB spiining disk NTFS partitions, which are 2 I had to change how I mount them. First, Auto filesystem would not work. I got this error in Doplhin IIRC: “filesystem type null not configured in kernel”. So I changed auto to ntfs-3g. I have blacklisted the other NTFS driver. I don’t trust it. ntfs-3g has not been a problem ever, in the past 15 years. Ntfs3 had a rough time around kernel 5.15. Dataloss etc.
The last part in /etc/fstab looks like this for me:
ntfs-3g nosuid,nodev,nofail,x-gvfs-show 0 0
I used Gnome Disk Utility to mount the partitions. GDU added noauto to the options, which prevented automounting of the partitions, so I removed that. 2 changes I made, specify exactly which filesystem to use and removed noauto.
To note: I compiled Zen 7.0.3 and it is what I am running. Maybe I forgot to enable something in kernel config. If I did, I would not expect it to work at all. But yeah, this started with Kernel 7.
Thanks a lot everyone for your suggestions, I’m too new to discuss anything in fstab ;).
I just saw something unusual but maybe my preference for GUI instead of command line has a limit : I wrote the line below as suggested by @Molski :
I wrote in fstab and check it afterwards.
Then I used Gnome Disk to unmount and checked a last time the settings : the tool did changed them automatically to
So maybe GDU is making some jokes ? I came back to the first line in fstab and tried directly in Konsole :
sudo systemctl daemon-reload
sudo mount /mnt/80A6D052A6D049F4
mount: /mnt/80A6D052A6D049F4: type de système de fichiers « ntfs3g » inconnu.
dmesg(1) peut avoir plus d'informations après un échec de l'appel système du montage.
I will try only rebooting as suggested and I come back here with the result.
I cannot understand what did change so much for my NTFS drives before and after the last update, without changing any settings
But as @Aragorn suggested, and as far I understand his answer, the “link” between these rights and the NTFS filesystem will not be made. So with or without these settings I should have the same result.
Thanks again, I selected your answer as the solution if someone needs it later. I tried it also successfully on the external HDD Have a nice Sunday everyone.
Glad you solved it. Which kernel do you run? Since it is the second such topic, with the solution to go back to ntfs-3g driver. But the kernel driver is changed at the 7 series, this shouldn’t happen on 6.18.
NTFS is not POSIX compliant, but the driver can present synthesized POSIX permissions across the entire filesystem.
With the umask this way, you can’t accidentally execute anything. But more importantly, only your user (plus group), and elevated privileges, can access this filesystem.
Even on a single-user system, it’s just a best-practice way of setting it up.
Give each part of the system only the access it actually needs.
I’m running 6.18.26-1. And the troubles came only yesterday after the last Manjaro Stable kernel update … It’s maybe not limited to 7.0 kernels ? Again, I’m not skilled enough to have a position on this issue
Have a nice Sunday everyone.
