NTFS partititon - Mount error - looking for some suggestions

Hi Team,

I’m using garuda linux more than 4years and satisfied with that.

Recent days, I’m facing issues (can’t mount ntfs partition)
so, i would like to know why this is happening, btw, I’m using new ssd

I’m using 1TB of ssd - 200GB for garuda (Btrfs) and 700GB for personal space (ntfs)

everytime i used to paste these command to mount

sudo ntfsfix /dev/nvme0n1p3

sudo mount -t ntfs /dev/nvme0n1p3 /mnt

any permanent solution for this?

i need to format my disk or i have to change to different partition?
like ext4 or btrfs
any suggestions regarding this?

just want to know how to fix it

for more info

Kernel: 6.5.4-zen2-1-zen arch: x86_64 bits: 64 compiler: gcc v: 13.2.1
clocksource: tsc available: hpet,acpi_pm
parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen
root=UUID=eddfc2bf-f824-464d-b001-d27ff9e017d0 rw rootflags=subvol=@
quiet quiet rd.udev.log_priority=3 vt.global_cursor_default=0 loglevel=3
Desktop: KDE Plasma v: 5.27.8 tk: Qt v: 5.15.10 wm: kwin_x11 vt: 2
dm: SDDM Distro: Garuda Linux base: Arch Linux
Type: Laptop System: Acer product: Aspire A715-42G v: V1.10
serial: <superuser required>
Mobo: LN model: Azalea_CAS v: V1.10 serial: <superuser required>
UEFI: Insyde v: 1.10 date: 07/28/2022
ID-1: BAT1 charge: 29.9 Wh (100.0%) condition: 29.9/47.8 Wh (62.5%)
volts: 12.3 min: 11.2 model: LGC AP18C8K type: Li-ion serial: <filter>
status: full
Info: model: AMD Ryzen 5 5500U with Radeon Graphics bits: 64 type: MT MCP
arch: Zen 2 gen: 3 level: v3 note: check built: 2020-22
process: TSMC n7 (7nm) family: 0x17 (23) model-id: 0x68 (104) stepping: 1
microcode: 0x8608103
Topology: cpus: 1x cores: 6 tpc: 2 threads: 12 smt: enabled cache:
L1: 384 KiB desc: d-6x32 KiB; i-6x32 KiB L2: 3 MiB desc: 6x512 KiB L3: 8 MiB
desc: 2x4 MiB
Speed (MHz): avg: 826 high: 1623 min/max: 400/4056 scaling:
driver: amd-pstate-epp governor: powersave cores: 1: 400 2: 400 3: 1421
4: 400 5: 400 6: 400 7: 1354 8: 1371 9: 400 10: 1623 11: 1354 12: 400
bogomips: 50304
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
Vulnerabilities: <filter>
Device-1: NVIDIA TU117M [GeForce GTX 1650 Mobile / Max-Q]
vendor: Acer Incorporated ALI driver: nvidia v: 535.104.05
alternate: nouveau,nvidia_drm non-free: 535.xx+
status: current (as of 2023-08) arch: Turing code: TUxxx
process: TSMC 12nm FF built: 2018-22 pcie: gen: 3 speed: 8 GT/s lanes: 8
link-max: gen: 4 speed: 16 GT/s lanes: 16 bus-ID: 01:00.0
chip-ID: 10de:1f9d class-ID: 0302
Device-2: AMD Lucienne vendor: Acer Incorporated ALI driver: amdgpu
v: kernel arch: GCN-5 code: Vega process: GF 14nm built: 2017-20 pcie:
gen: 3 speed: 8 GT/s lanes: 16 link-max: gen: 4 speed: 16 GT/s ports:
active: eDP-1 empty: HDMI-A-1 bus-ID: 05:00.0 chip-ID: 1002:164c
class-ID: 0300 temp: 46.0 C
Device-3: Quanta HD User Facing driver: uvcvideo type: USB rev: 2.0
speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 3-3:2 chip-ID: 0408:a061
class-ID: 0e02
Display: x11 server: X.Org v: 21.1.8 with: Xwayland v: 23.2.1
compositor: kwin_x11 driver: X: loaded: amdgpu,nvidia
unloaded: modesetting,nouveau alternate: fbdev,nv,vesa dri: radeonsi
gpu: amdgpu display-ID: :0 screens: 1
Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x285mm (20.00x11.22")
s-diag: 582mm (22.93")
Monitor-1: eDP-1 mapped: eDP model: AU Optronics 0xdf87 built: 2019
res: 1920x1080 hz: 60 dpi: 142 gamma: 1.2 size: 344x193mm (13.54x7.6")
diag: 394mm (15.5") ratio: 16:9 modes: max: 1920x1080 min: 640x480
API: OpenGL v: 4.6 Mesa 23.1.7-arch1.1 renderer: AMD Radeon Graphics
(renoir LLVM 16.0.6 DRM 3.54 6.5.4-zen2-1-zen) direct-render: Yes
Device-1: AMD Renoir Radeon High Definition Audio
vendor: Acer Incorporated ALI driver: snd_hda_intel v: kernel pcie: gen: 3
speed: 8 GT/s lanes: 16 link-max: gen: 4 speed: 16 GT/s bus-ID: 05:00.1
chip-ID: 1002:1637 class-ID: 0403
Device-2: AMD ACP/ACP3X/ACP6x Audio Coprocessor
vendor: Acer Incorporated ALI driver: N/A alternate: snd_pci_acp3x,
snd_rn_pci_acp3x, snd_pci_acp5x, snd_pci_acp6x, snd_acp_pci,
snd_rpl_pci_acp6x, snd_pci_ps, snd_sof_amd_renoir, snd_sof_amd_rembrandt
pcie: gen: 3 speed: 8 GT/s lanes: 16 link-max: gen: 4 speed: 16 GT/s
bus-ID: 05:00.5 chip-ID: 1022:15e2 class-ID: 0480
Device-3: AMD Family 17h/19h HD Audio vendor: Acer Incorporated ALI
driver: snd_hda_intel v: kernel pcie: gen: 3 speed: 8 GT/s lanes: 16
link-max: gen: 4 speed: 16 GT/s bus-ID: 05:00.6 chip-ID: 1022:15e3
class-ID: 0403
API: ALSA v: k6.5.4-zen2-1-zen status: kernel-api with: aoss
type: oss-emulator tools: N/A
Server-1: PipeWire v: 0.3.80 status: active with: 1: pipewire-pulse
status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin
4: pw-jack type: plugin tools: pactl,pw-cat,pw-cli,wpctl
Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
vendor: Acer Incorporated ALI driver: r8169 v: kernel pcie: gen: 1
speed: 2.5 GT/s lanes: 1 port: 2000 bus-ID: 03:00.0 chip-ID: 10ec:8168
class-ID: 0200
IF: enp3s0 state: down mac: <filter>
Device-2: Intel Wi-Fi 6 AX200 driver: iwlwifi v: kernel pcie: gen: 2
speed: 5 GT/s lanes: 1 bus-ID: 04:00.0 chip-ID: 8086:2723 class-ID: 0280
IF: wlp4s0 state: up mac: <filter>
IF-ID-1: virbr0 state: down mac: <filter>
Device-1: Intel AX200 Bluetooth driver: btusb v: 0.8 type: USB rev: 2.0
speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 1-4:2 chip-ID: 8087:0029
class-ID: e001
Report: btmgmt ID: hci0 rfk-id: 2 state: down bt-service: enabled,running
rfk-block: hardware: no software: yes address: <filter> bt-v: 5.2 lmp-v: 11
status: discoverable: no pairing: no
Local Storage: total: 931.51 GiB used: 364.74 GiB (39.2%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Crucial model: CT1000P3SSD8
size: 931.51 GiB block-size: physical: 512 B logical: 512 B speed: 31.6 Gb/s
lanes: 4 tech: SSD serial: <filter> fw-rev: P9CR30A temp: 39.9 C
scheme: GPT
ID-1: / raw-size: 180 GiB size: 180 GiB (100.00%) used: 68.03 GiB (37.8%)
fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%)
used: 580 KiB (0.2%) fs: vfat dev: /dev/nvme0n1p1 maj-min: 259:1
ID-3: /home raw-size: 180 GiB size: 180 GiB (100.00%)
used: 68.03 GiB (37.8%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
ID-4: /var/log raw-size: 180 GiB size: 180 GiB (100.00%)
used: 68.03 GiB (37.8%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
ID-5: /var/tmp raw-size: 180 GiB size: 180 GiB (100.00%)
used: 68.03 GiB (37.8%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default) zswap: no
ID-1: swap-1 type: zram size: 14.96 GiB used: 156 MiB (1.0%) priority: 100
comp: zstd avail: lzo,lzo-rle,lz4,lz4hc,842 max-streams: 12 dev: /dev/zram0
System Temperatures: cpu: 54.8 C mobo: N/A gpu: amdgpu temp: 48.0 C
Fan Speeds (rpm): N/A
Processes: 316 Uptime: 27m wakeups: 1 Memory: total: 16 GiB note: est.
available: 14.96 GiB used: 3.55 GiB (23.7%) Init: systemd v: 254
default: graphical tool: systemctl Compilers: gcc: 13.2.1 Packages:
pm: pacman pkgs: 1548 libs: 498 tools: octopi,paru Shell: fish v: 3.6.1
default: Bash v: 5.1.16 running-in: konsole inxi: 3.3.29
Garuda (2.6.16-1):
System install date:     2023-09-05
Last full system update: 2023-09-22
Is partially upgraded:   No
Relevant software:       snapper NetworkManager dracut nvidia-dkms
Windows dual boot:       No/Undetected
Failed units:
1 Like

I have seen a couple other places (here, here) where it has been mentioned running ntfsfix before mounting an NTFS drive has been needed. There must be a bug somewhere.

If you are not accessing these drives with a Windows system, you should change the filesystem. Some people (:wink:) still consider NTFS support on Linux experimental.

In general, switching to ext4 or Btrfs will give you better reliability, faster performance, and access to more features when accessing the disk from Linux.


Thanks for your suggestions sir :slight_smile:

which one you prefer mostly?
ext4 or btrfs

so ext4 can able access from windows?

I’m not good in these stuffs. so, i listen to the experts advice…

Why the hell are you mounting the windows partition like this I use ntfs for storage in 20 years never had a problem apart from when i did not close windows down properly and the file system was locked by windows.

i found these command helpful for me and solved issues.

i use Garuda as my primary and sometimes just want to access files from windows in emergency cases thats it.

There is a bug in the NTFS driver, which was mentioned in the thread. I even posted a couple links where other folks have the same issue. Try to keep up. :wink:

The main reason to choose Btrfs over ext4 would be to use Btrfs-specific features (filesystem snapshots, Btrfs send/receive, etc). If you don’t think you’ll be using those extra features I would just go with ext4.


But they are not solving issues only making issues worse

their is no bug in the ntfs-3g driver non at all i use it daily for the last 20 years the fault is users nothing more. the reason i use it is because i duel boot and mount the drives at start up. I suggest its you that needs to keep up use ntfs -3g driver not some alpha driver in the kernel


Technically I’m not good in stuffs.

anyway now i decided to move to btrfs…

Incase if you found any article regarding this, just share it
i really appreciate that :slight_smile:

My friend, I believe he is already using ntfs-3g driver. If he was using the new kernel driver, he would be mounting “ntfs3” not “ntfs”.

You can’t be sure of that, The only reason for mounting problems on ntfs drives is a corrupt drive caused by windows, or a locked drive again caused by windows locking the file system. User not shutting down correctly

you are saying that i dualboot windows & garuda and i didnt shutdown my windows correctly?


The mount type ntfs-3g does not need to be explicitly specified in Arch. The mount command by default will use /usr/bin/mount.ntfs which is symlinked to /usr/bin/ntfs-3g after the ntfs-3g package is installed.


I’m not arguing with you on what the cause of the problem is. I’m telling you that you’re wrong about him not using ntfs-3g.

What error message do you get if you don’t use the ntfsfix command before mounting?

Wrong fs type, bad option, bad superblock on a harddisk missing codepage or helper program, or other error

something like this

You are assuming i have never stated what driver is being used neither has the user. Either way he seems to have problems with the windows file system locking him out.
I would suggest if he must have a file system compatible with windows to use the Exfat file system

At this point perhaps one of the various CD/USB-based general repair applications, which includes repairing ntfs partitions, might be of use?

1 Like

Agree. As the user dual boots windows, perhaps just running a chkdsk next time u boot Windows will suffice

1 Like

I have not seen OP decisively say he has Windows installed.

But then OP says

Unless and until OP can be more decisive, the point of this topic seems moot.


I having this same issue.

It’s strange that my one WD 5TB NTFS partition mounts fine but my Toshiba 1TB NTFS gives the above error.

That is consistent with what we have seen so with this issue, that some hardware is affected and some not. Go ahead and try using ntfsfix as described in the OP and see if it restores you access to the drive. It may be necessary to do it every time until whatever bug gets fixed upstream.

1 Like