Unable to write NTFS disk of Windows

FIrst of all thanks to garuda devs for creating such a nice and best arch-based distro. Finally I stopped distro-hopping after coming to Garuda. But I am new to Linux and facing a problem. I am unable to write on NTFS disk of Windows through nautilus as user or root. Also unable to modify permissions to make it writeable. It is Read-only. Please help me regarding this!

Kernel: 5.16.13-zen1-1-zen x86_64 bits: 64 compiler: gcc v: 11.2.0
parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen
root=UUID=5be83b56-8967-4471-a53c-29858d828b44 rw [email protected]
quiet splash rd.udev.log_priority=3 vt.global_cursor_default=0
resume=UUID=5539334e-1ca1-49c9-9bda-37b8aa0d15c9 loglevel=3
Desktop: GNOME 41.4 tk: GTK 3.24.33 wm: gnome-shell dm: GDM 41.3
Distro: Garuda Linux base: Arch Linux
Type: Laptop System: ASUSTeK product: VivoBook_ASUSLaptop X509DA v: 1.0
Mobo: ASUSTeK model: X509DA v: 1.0 serial:
UEFI: American Megatrends v: X509DA.306 date: 10/11/2019
ID-1: BAT0 charge: 23.7 Wh (97.1%) condition: 24.4/32.1 Wh (76.1%)
volts: 7.8 min: 7.8 model: ASUSTeK ASUS Battery type: Li-ion serial: N/A
status: Discharging cycles: 514
Info: model: AMD Ryzen 5 3500U with Radeon Vega Mobile Gfx socket: FP5
bits: 64 type: MT MCP arch: Zen/Zen+ note: check family: 0x17 (23)
model-id: 0x18 (24) stepping: 1 microcode: 0x8108109
Topology: cpus: 1x cores: 4 tpc: 2 threads: 8 smt: enabled cache:
L1: 384 KiB desc: d-4x32 KiB; i-4x64 KiB L2: 2 MiB desc: 4x512 KiB
L3: 4 MiB desc: 1x4 MiB
Speed (MHz): avg: 1400 min/max: 1400/2100 boost: enabled
base/boost: 2100/3700 scaling: driver: acpi-cpufreq governor: schedutil
volts: 1.2 V ext-clock: 100 MHz cores: 1: 1400 2: 1400 3: 1400 4: 1400
5: 1400 6: 1400 7: 1400 8: 1400 bogomips: 33535
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
Type: itlb_multihit status: Not affected
Type: l1tf status: Not affected
Type: mds status: Not affected
Type: meltdown status: Not affected
Type: spec_store_bypass
mitigation: Speculative Store Bypass disabled via prctl
Type: spectre_v1
mitigation: usercopy/swapgs barriers and __user pointer sanitization
Type: spectre_v2 mitigation: Full AMD retpoline, IBPB: conditional,
STIBP: disabled, RSB filling
Type: srbds status: Not affected
Type: tsx_async_abort status: Not affected
Device-1: AMD Picasso/Raven 2 [Radeon Vega Series / Radeon Mobile Series]
vendor: ASUSTeK driver: amdgpu v: kernel pcie: gen: 3 speed: 8 GT/s
lanes: 16 ports: active: eDP-1 empty: HDMI-A-1 bus-ID: 02:00.0
chip-ID: 1002:15d8 class-ID: 0300
Device-2: IMC Networks USB2.0 VGA UVC WebCam type: USB driver: uvcvideo
bus-ID: 3-2.2:5 chip-ID: 13d3:5a11 class-ID: 0e02
Display: server: [X.Org](http://X.Org) v: compositor: gnome-shell driver: X:
loaded: amdgpu,ati unloaded: modesetting,radeon alternate: fbdev,vesa
gpu: amdgpu display-ID: :1 screens: 1
Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x285mm (20.0x11.2")
s-diag: 582mm (22.9")
Monitor-1: eDP res: 1920x1080 hz: 60 dpi: 142 size: 344x193mm (13.5x7.6")
diag: 394mm (15.5")
Message: Unable to show GL data. Required tool glxinfo missing.
Device-1: AMD Raven/Raven2/Fenghuang HDMI/DP Audio driver: snd_hda_intel
v: kernel pcie: gen: 3 speed: 8 GT/s lanes: 16 bus-ID: 02:00.1
chip-ID: 1002:15de class-ID: 0403
Device-2: AMD ACP/ACP3X/ACP6x Audio Coprocessor driver: snd_pci_acp3x
v: kernel alternate: snd_rn_pci_acp3x,snd_pci_acp5x,snd_pci_acp6x pcie:
gen: 3 speed: 8 GT/s lanes: 16 bus-ID: 02:00.5 chip-ID: 1022:15e2
class-ID: 0480
Device-3: AMD Family 17h/19h HD Audio vendor: ASUSTeK
driver: snd_hda_intel v: kernel pcie: gen: 3 speed: 8 GT/s lanes: 16
bus-ID: 02:00.6 chip-ID: 1022:15e3 class-ID: 0403
Sound Server-1: ALSA v: k5.16.13-zen1-1-zen running: yes
Sound Server-2: PulseAudio v: 15.0 running: no
Sound Server-3: PipeWire v: 0.3.48 running: yes
Device-1: Intel Wireless 8265 / 8275 driver: iwlwifi v: kernel pcie: gen: 1
speed: 2.5 GT/s lanes: 1 bus-ID: 01:00.0 chip-ID: 8086:24fd class-ID: 0280
IF: wlp1s0 state: up mac:
Device-1: Intel Bluetooth wireless interface type: USB driver: btusb v: 0.8
bus-ID: 3-2.1:4 chip-ID: 8087:0a2b class-ID: e001
Report: bt-adapter ID: hci0 rfk-id: 3 state: up address:
Local Storage: total: 931.51 GiB used: 25.43 GiB (2.7%)
SMART Message: Required tool smartctl not installed. Check --recommends
ID-1: /dev/sda maj-min: 8:0 vendor: Seagate model: ST1000LM035-1RK172
size: 931.51 GiB block-size: physical: 4096 B logical: 512 B
speed: 6.0 Gb/s type: HDD rpm: 5400 serial: rev: 0001
scheme: GPT
ID-1: / raw-size: 200 GiB size: 200 GiB (100.00%) used: 25.1 GiB (12.6%)
fs: btrfs block-size: 4096 B dev: /dev/sda3 maj-min: 8:3
ID-2: /boot/efi raw-size: 616 MiB size: 614.8 MiB (99.80%)
used: 28 MiB (4.6%) fs: vfat block-size: 512 B dev: /dev/sda1 maj-min: 8:1
ID-3: /home raw-size: 200 GiB size: 200 GiB (100.00%)
used: 25.1 GiB (12.6%) fs: btrfs block-size: 4096 B dev: /dev/sda3
maj-min: 8:3
ID-4: /var/log raw-size: 200 GiB size: 200 GiB (100.00%)
used: 25.1 GiB (12.6%) fs: btrfs block-size: 4096 B dev: /dev/sda3
maj-min: 8:3
ID-5: /var/tmp raw-size: 200 GiB size: 200 GiB (100.00%)
used: 25.1 GiB (12.6%) fs: btrfs block-size: 4096 B dev: /dev/sda3
maj-min: 8:3
Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default)
ID-1: swap-1 type: zram size: 5.8 GiB used: 0 KiB (0.0%) priority: 100
dev: /dev/zram0
System Temperatures: cpu: 63.0 C mobo: N/A gpu: amdgpu temp: 63.0 C
Fan Speeds (RPM): cpu: 3200
Processes: 303 Uptime: 53m wakeups: 1 Memory: 5.8 GiB
used: 2.44 GiB (42.0%) Init: systemd v: 250 tool: systemctl Compilers:
gcc: 11.2.0 clang: 13.0.1 Packages: pacman: 1260 lib: 347
Shell: garuda-inxi (sudo) default: Bash v: 5.1.16
running-in: gnome-terminal inxi: 3.3.13
Garuda (2.5.5-1):
System install date: 2022-02-23
Last full system update: 2022-03-11
Is partially upgraded: No
Relevant software: NetworkManager
Windows dual boot: Yes
Snapshots: Snapper
Failed units:

If you include terminal outputs in your post please use the proper output format in your post.

Using "~" 3 times above and "~" 3 times below the text block will provide a readable, raw look.

Reboot to Windows, disable fast boot and hibernation on Windows, reboot to Linux and try again.


If the suggestion above doesn't help, maybe try to give a look at this recent thread.

It seems that this ntfsfix, provided by the ntfs-3g package, which should be installed appositely, since it will replace the standard package ntfsprogs-ntfs3, could help.


Sorry to be rude, but we don't offer Windows support for one simple reason. It adds a whole other level of complexity to using Linux.

While you can use ntfsfix, it will not necessarily correct all errors on a Windows file system. You often need to do this from Windows to correct serious file system errors.

If you want to prevent an NTFS drive from becoming corrupted regularly you need to mount it in your fstab with special flags. I suggest you research this topic thoroughly if you insist on using a Windows based file system in Linux.

This topic has been covered plenty of times on our forum, and countless times on other forums. The Arch Wiki also contains lots of information on mounting a drive properly.

If you must use a Windows filesystem, then I suggest you must do your research.

We don't support Windows here.


As per Archwiki, read/write is supported/embedded in the kernels. Check the article and if you still have problem, post bug report(s) to the applications that you are using and fail.

1 Like

Just boot into a windows machine, install AOMEI Partition Assistant, open the software, select your device by right click, then go to advance section then click check partition. Select the error fix option and voila it will fix your device without erasing your data. I have tried a dozen of ways but trust me this one is the best you'll find in the web right now.

No offense, but unless something has changed since my Windows days there is no need to install 3rd party software to scan and fix NTFS drives on Windows. Every Windows installallation has a utility included to do this to the best of my knowledge.

Also, this is not a Windows support site, so we're done here.

This stuff has been covered lots of times on our forum, and thousands of times on other sites. So, do your research.