Update: I was wrong about a couple things:
- I’m having issues with 2 different NTFS drives. The ext4 one is fine.
- The issue appears to be driver related. If the drive auto-mounts by udisks2.service, it shows up as “type ntfs3” with the output of mount, but if I mount it manually it shows up as “type fuseblk”. It seems that the fuse-based driver works but the ntfs3 one is broken.
I’m at my wits end with this one.
SSDs on my computer:
- a drive with a Windows 11 install
- a drive with an Ubuntu 22.04 install (the OS I use the most)
- a drive with an Ubuntu 20.04 install (for a piece of touchy software I needed that didn’t seem to like 22.04)
- an NTFS drive to share files across OSes
- an EXT4 drive to share files across OSes
These are all physically separate drives, not partitions of the same drive or something like that. They all SATA SSDs except the Windows one which is nvme.
Ubuntu 22.04 is acting up. It seems that it can write to the NTFS and EXT4 drives fine, but has difficulty reading from them. If I write a file e.g. echo “hello world” > test, the file appears but trying to read it, the file seems empty. I reboot and I can read the file.
When I first encountered this, I thought the NTFS drive was failing, so I did a large rsync (to back up the data) and got some read errors, and then ran a SMART test which came back clean.
Since then, with further testing, only 22.04 seems to have these issues. Both Windows and 20.04 can read and write fine. However, Windows caught some filesystem errors with the drive after the large rsync.
I’m about to reinstall Ubuntu but I’m worried about making things worse somehow. It would be nice to have an idea of what’s going on.
Any advice?
You could also try to switch the kernel version. Ubuntu 22.04 currently supports two different versions: 5.15 and 6.5, you could switch to the other one and see if the problem also occurs there.
I just read the update to the post saying that the issue has been narrowed down to the NTFS driver. I haven't used NTFS on linux since the NTFS fuse driver was brand new and still wonky as hell something like 15 years ago, so I don't know much about it.
However, it sounds like the in kernel driver was still pretty fresh in 5.15, so doing as you have suggested and trying out a 6.5 kernel instead is a pretty good call.
Yeah, NTFS being the problem actually makes a more sense.
OP could also just use the fuse driver then. I'm using it on 5.15 (Linux Mint) and it works quite well. I only had problems when I tried to use it for a Steam library.