Suddenly problems accessing ntfs-HDDs und USB3

Issues & Assistance
1

Hey there,

after one of the last updates I’m experiencing some problems with ntfs3-HDDs and USB3 connected sticks or NVMEs.

Last problems were:

  • USB 3 stick with ventoy on it. I want to copy an iso-file from an ntfs formated 4TB HDD to the stick. The data rate goes down to 8MiB/s.
  • I added my Nextcloud Server via network in Dolphin and wanted to transfer 300GB+ to the nextcloud-Server, the transfer rate goes down to 500KB/s.

Some days before there was no problem. And it is not a hardware problem, with a parallel installation of LM22 I can copy the iso from the NTFS-HDD to the ventoy Stick with stable 140MB/s.

Any ideas where to examine?

2

It’s getting more crazy. Because of no idea after 4h of waiting and needing the functionality on the machine I decided to do a reinstallation - and crazy enough the problem persists…

I have to say that I use different partitions for / and /home. So I can leave my home partition staying and only give /boot/efi and / a fresh formatted partition.

So the question is if anything on the /home partition can cause this strange behavior… But as far as I understand, the system can’t use any of the .dot files before any software is installed. And I verified the behavior right after the reinstallation.

But I didn’t install any weird packages that I didn’t install before…

I think the only way to verify is a new reinstallation with no separate /home partition and verify again.

Can this be a driver problem?

3

Folks,

I can’t figure it out… Other Debian and Ubuntu based DEs give me the full transfer rate from the btrfs formatted /home partition to USB 3 at about 140MB/s.

This is a game changer for me and if I can’t find a solution my arch experiment will end here…

4

Ok, I have had the time and did some further testing:

  • An iso of the up to date EndeavourOS with KDE plasma went on my 2TB USB-NVME drive. To my biggest surprise EndeavourOS works without any problems… I installed NVIDIA 565.57.01 drivers.
  • Then I remembered a YT Video which told about installing the CachyOS Repo on every Arch Linux, like told in the wiki Optimized Repositories. I tried the script, and it installed without any problems. Then I installed the CachyOS Kernel manager and tried linux-cachyos-eevdf-lto Kernel. That failed, I think because dracut did not integrate the NVIDIA drivers?
    So I did another try and installed linux-cachyos-nvidia-open. This installed Kernel 6.11.6-2

And what should I say, everything is working any smoother than before… In addition, some problems with stuttering of my Microsoft mouse and keyboard, which I didn’t mention before, are also gone.

So I’m very pleased by this system by now. I only have to do the same installation on my build in NVME.

So is there no one of the package builders beyond you, who has any idea what was going on with my CachyOS installation? I don’t know anything about Kernel building. But I thought that such drivers like for USB ports are only matched together, and the Kernel is compiled. You won’t investigate the wheel again… So I thought the drivers are the same in the CachyOS Kernel and the EndeavourOS Kernel. But, it seems, that this is not the case.

It would be nice to have any suggestion.

5

Bump for our friend here.

6

I’m also experiencing issues with mounting NTFS Windows 11 drives for a couple days now, that were not present before.

Here’s the error I get while trying to mount a NTFS formatted drive:

LC_ALL=C sudo mount -t ntfs3 /dev/nvme0n1p3 /mnt/windows_c
mount: /mnt/windows_c: wrong fs type, bad option, bad superblock on /dev/nvme0n1p3, missing codepage or helper program, or other error.
       dmesg(1) may have more information after failed mount system call.


(...)
[  861.283214] [UFW BLOCK] IN=wlan0 OUT= MAC=70:d8:23:1d:5a:e7:58:11:22:63:29:f0:08:00 SRC=192.168.50.1 DST=224.0.0.1 LEN=36 TOS=0x00 PREC=0x00 TTL=1 ID=50180 DF PROTO=2 
[  861.832713] ntfs3: nvme0n1p3: It is recommened to use chkdsk.
[  861.834759] ntfs3: nvme0n1p3: volume is dirty and "force" flag is not set!
[  863.944028] kauditd_printk_skb: 16 callbacks suppressed
[  863.944030] audit: type=1130 audit(1730983731.213:430): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=unconfined msg='unit=man-db comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[  863.944032] audit: audit_lost=1170 audit_rate_limit=0 audit_backlog_limit=64
[  863.944033] audit: kauditd hold queue overflow
[  863.944035] audit: type=1131 audit(1730983731.213:431): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=unconfined msg='unit=man-db comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[  863.944036] audit: audit_lost=1171 audit_rate_limit=0 audit_backlog_limit=64
[  863.944036] audit: kauditd hold queue overflow
[  863.958275] audit: type=1334 audit(1730983731.227:432): prog-id=58 op=UNLOAD
[  863.958285] audit: audit_lost=1172 audit_rate_limit=0 audit_backlog_limit=64
[  863.958290] audit: kauditd hold queue overflow
[  868.200209] audit: type=1101 audit(1730983735.469:433): pid=4520 uid=1000 auid=1000 ses=3 subj=unconfined msg='op=PAM:accounting grantors=pam_unix,pam_permit,pam_time acct="cardiozibi" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/0 res=success'

Any hints what “nvme0n1p3: volume is dirty and “force” flag is not set!” could mean?
Don’t know what could be wrong here, maybe new kernel version broke something.

7

It means the drive has errors and/or wasn’t cleanly dismounted (likely the last).
For safety’s sake, I recommend booting into Windows and performing a filesystem check/fix/repair.

8

You were right, it worked. Thanks.