After last update, automounted hard drive is getting hibernated after shutdown

Support System Updates
1

I have an internal hard drive disk set to automount using Gnome Disk utility. After this last update, every time I boot up my computer, the drive opens as read-only until I run this command:

sudo mount -t ntfs -o remove_hiberfile /dev/sda1 /mnt/668EB1FA8EB1C2BB

How do I stop this hibernation thing from happening? It’s really annoying to have to run this every time I boot up my computer.

And no, Windows is NOT involved, although my system is dual-booted. This happens when I shut down from linux and boot into linux.

System information:

System:
  Kernel: 6.18.26-1-MANJARO arch: x86_64 bits: 64 compiler: gcc v: 15.2.1
    clocksource: tsc avail: hpet,acpi_pm
    parameters: BOOT_IMAGE=/@/boot/vmlinuz-6.18-x86_64
    root=UUID=246a4db0-4152-46c2-94e0-79b1495fe607 rw rootflags=subvol=@
    quiet splash udev.log_priority=3
  Desktop: KDE Plasma v: 6.6.4 tk: Qt v: N/A info: frameworks v: 6.25.0
    wm: kwin_wayland vt: 1 dm: SDDM Distro: Manjaro base: Arch Linux
Machine:
  Type: Desktop System: ASUS product: N/A v: N/A serial: <superuser required>
  Mobo: ASUSTeK model: TUF GAMING B550M-PLUS WIFI II v: Rev X.0x
    serial: <superuser required> part-nu: SKU uuid: <superuser required>
    Firmware: UEFI vendor: American Megatrends v: 2806 date: 10/27/2022
Battery:
  Device-1: hidpp_battery_0 model: Logitech G305 Lightspeed Wireless Gaming
    Mouse serial: <filter> charge: 100% (should be ignored) rechargeable: yes
    status: discharging
Memory:
  System RAM: total: 16 GiB available: 15.52 GiB used: 7.19 GiB (46.3%)
  Message: For most reliable report, use superuser + dmidecode.
  Array-1: capacity: 128 GiB slots: 4 modules: 2 EC: None
    max-module-size: 32 GiB note: est.
  Device-1: DIMM_A1 type: DDR4 detail: synchronous unbuffered (unregistered)
    size: 8 GiB speed: 2133 MT/s volts: note: check curr: 1 min: 1 max: 1
    width (bits): data: 64 total: 64 manufacturer: G-Skill
    part-no: F4-3200C16-8GVKB serial: N/A
  Device-2: DIMM_A2 type: no module installed
  Device-3: DIMM_B1 type: DDR4 detail: synchronous unbuffered (unregistered)
    size: 8 GiB speed: 2133 MT/s volts: note: check curr: 1 min: 1 max: 1
    width (bits): data: 64 total: 64 manufacturer: G-Skill
    part-no: F4-3200C16-8GVKB serial: N/A
  Device-4: DIMM_B2 type: no module installed
PCI Slots:
  Permissions: Unable to run dmidecode. Root privileges required.
CPU:
  Info: model: AMD Ryzen 5 5600X bits: 64 type: MT MCP arch: Zen 3+ gen: 3
    level: v3 note: check built: 2022 process: TSMC n6 (7nm) family: 0x19 (25)
    model-id: 0x21 (33) stepping: 2 microcode: 0xA201211
  Topology: cpus: 1x dies: 1 clusters: 1 cores: 6 threads: 12 tpc: 2
    smt: enabled cache: L1: 384 KiB desc: d-6x32 KiB; i-6x32 KiB L2: 3 MiB
    desc: 6x512 KiB L3: 32 MiB desc: 1x32 MiB
  Speed (MHz): avg: 1738 min/max: 561/4654 boost: enabled scaling:
    driver: amd-pstate-epp governor: powersave cores: 1: 1738 2: 1738 3: 1738
    4: 1738 5: 1738 6: 1738 7: 1738 8: 1738 9: 1738 10: 1738 11: 1738 12: 1738
    bogomips: 88628

Drives:
  Local Storage: total: 2.73 TiB used: 683 GiB (24.4%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/nvme0n1 maj-min: 259:4 vendor: Western Digital
    model: WD BLACK SN750 SE 1TB size: 931.51 GiB block-size: physical: 512 B
    logical: 512 B speed: 63.2 Gb/s lanes: 4 tech: SSD serial: <filter>
    fw-rev: 711130WD temp: 39.9 C scheme: GPT
  ID-2: /dev/nvme1n1 maj-min: 259:0 vendor: Samsung
    model: SSD 970 EVO Plus 1TB 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: 4B2QEXM7 temp: 46.9 C scheme: GPT
  ID-3: /dev/sda maj-min: 8:0 vendor: Seagate model: ST1000DM010-2EP102
    size: 931.51 GiB block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s
    tech: HDD rpm: 7200 serial: <filter> fw-rev: CC46 scheme: MBR
  Message: No optical or floppy data found.

Partition:
  ID-1: / raw-size: 931.22 GiB size: 931.22 GiB (100.00%)
    used: 458.93 GiB (49.3%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:6
    label: N/A uuid: 246a4db0-4152-46c2-94e0-79b1495fe607
  ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%)
    used: 668 KiB (0.2%) fs: vfat dev: /dev/nvme0n1p1 maj-min: 259:5 label: N/A
    uuid: 9DA5-A68D
  ID-3: /home raw-size: 931.22 GiB size: 931.22 GiB (100.00%)
    used: 458.93 GiB (49.3%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:6
    label: N/A uuid: 246a4db0-4152-46c2-94e0-79b1495fe607
  ID-4: /mnt/668EB1FA8EB1C2BB raw-size: 931.51 GiB
    size: 931.51 GiB (100.00%) used: 224.07 GiB (24.1%) fs: ntfs dev: /dev/sda1
    maj-min: 8:1 label: ShareAndBackup uuid: 668EB1FA8EB1C2BB
  ID-5: /var/cache raw-size: 931.22 GiB size: 931.22 GiB (100.00%)
    used: 458.93 GiB (49.3%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:6
    label: N/A uuid: 246a4db0-4152-46c2-94e0-79b1495fe607
  ID-6: /var/log raw-size: 931.22 GiB size: 931.22 GiB (100.00%)
    used: 458.93 GiB (49.3%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:6
    label: N/A uuid: 246a4db0-4152-46c2-94e0-79b1495fe607
2

Maybe it is time to boot into winbose and do a checkdisk from there, just to be sure. That with the hibernation file is strange, but readonly mount usually means problem with filesystem.

2 Likes
3

I have already done this yesterday. Windows did in fact find an error and requested to reboot to fix it, which it did. Afterward I ran checkdesk again and no errors returned. The hard drive was still read-only on manjaro after this until I ran the remove hibernfile command, after which it became perfectly usable again… Until the next time I booted up my computer.

Just ran checkdisk again just to be safe, and it returned no errors. Drive is still read-only on boot in manjaro.

4

I’m wondering if the Windows “fast startup” (hibernation) feature is still active? (It might have been re-enabled during an update). I wouldn’t think it likely, but it may be possible some Windows service is still running in the background. I don’t know how modern Windows works.

Try running powercfg /h off in an elevated Windows command prompt. :wink:

5

If that were the case, would it still be happening even when I haven’t booted into windows? And my windows version is 10. There are no updates anymore lol.

6

It’s a bit of a guess on my part, but it does seem that when Windows hibernates, some background stuff (hardware related) stays in some sort of standby state, preventing Linux from having proper access (I’m thinking WiFi cards, etc.) as I’ve read about such issues on here.

It’s well worth running that command anyway.

7

Reboot into windows, ran the command, came back to linux. THOUGHT it was fixed but no, the drive is still read-only. (I might have been in the wrong folder the first time)

1 Like
8

Yes, it would. Windows Fast Startup — or Hybrid Sleep, however it is called — should be disabled.

1 Like
9

Does the disk in question contain the Windows installation or is the entire disk used purely for storage? I note that it uses a Master Boot Record (MBR) partitioning scheme, which is not ideal, but likely isn’t a factor if it’s only used for storage.

If, however, the disk is a Windows installation – the inference being that you are attempting to mount a Windows system partition during boot from Linux, which the use of the remove_hiberfil parameter suggests you are doing – this is potentially dangerous and not widely recommended.

I note that your inxi output is incomplete – please provide it in full, as requested:

[Mini-HowTo] Provide System Information

Basic details provided by *-fetch type apps might give enough information for someone wishing to buy a computer, however, for Support purposes it’s best to ask your system directly.

Output of the inxi command will generate more useful and detailed information for those who may wish to help:

Suggested inxi command (use either):
inxi -zv8 (short-form)
inxi --filter --verbosity=8 (long-form)

Command output should be presented as pre-formatted text in accordance with forum guidelines. :eyes:

Running inxi within a chroot environment

  • Add --color=0 to the long-form command, or…
  • Change the short-form command to inxi -zv8c0

Your privacy is respected

As @Aragorn has mentioned, if Fast Startup is enabled, it should be disabled when multi-booting with Linux;

The easiest way to do that is from an administrative command prompt in Windows:

powercfg.exe /h off

Once this action is performed, Fast Startup and all hibernation in Windows will be deactivated. There is no need for attempting to delete hiberfil.sys while mounting the disk in Linux.

Recommendation:

Create a secondary partition (a “D: drive”) on that disk, and mount that instead.

Regards.

2 Likes
10

It’s entirely for storage. It might have a MBR partitioning scheme because windows was ANNOYING and threw its boot partition on there even though it also installed one on its own SSD. I deleted the boot partition because windows was booting from the HDD instead of the SSD and it was taking forever as a result.

Hibernation and fast boot on windows is off. I turned it off long ago, and just ran the command again prior to your post for good measure. Even when it was on, the only time the drive got locked was after I had booted into windows. This isn’t the case here; I literally just restarted from manjaro into manjaro and the drive reset back to read-only.

And reminder–this ONLY started happening after the update to manjaro.

This inxi output was created before running the hiberfile command:

inxi output 
System:
  Kernel: 6.18.26-1-MANJARO arch: x86_64 bits: 64 compiler: gcc v: 15.2.1
    clocksource: tsc avail: hpet,acpi_pm
    parameters: BOOT_IMAGE=/@/boot/vmlinuz-6.18-x86_64
    root=UUID=246a4db0-4152-46c2-94e0-79b1495fe607 rw rootflags=subvol=@
    quiet splash udev.log_priority=3
  Desktop: KDE Plasma v: 6.6.4 tk: Qt v: N/A wm: kwin_wayland dm: SDDM
    Distro: Manjaro base: Arch Linux
Machine:
  Type: Desktop System: ASUS product: N/A v: N/A serial: N/A
  Mobo: ASUSTeK model: TUF GAMING B550M-PLUS WIFI II v: Rev X.0x
    serial: <filter> part-nu: SKU uuid: 9ce8974f-2a20-0dc5-9dbf-581122cd3cd0
    Firmware: UEFI vendor: American Megatrends v: 2806 date: 10/27/2022
Battery:
  Device-1: hidpp_battery_0 model: Logitech G305 Lightspeed Wireless Gaming
    Mouse serial: <filter> charge: 100% (should be ignored) rechargeable: yes
    status: discharging
Memory:
  System RAM: total: 16 GiB available: 15.52 GiB used: 3.26 GiB (21.0%)
  Array-1: capacity: 128 GiB slots: 4 modules: 2 EC: None
    max-module-size: 32 GiB note: est.
  Device-1: DIMM_A1 type: DDR4 detail: synchronous unbuffered (unregistered)
    size: 8 GiB speed: 2133 MT/s volts: curr: 1.2 min: 1.2 max: 1.2
    width (bits): data: 64 total: 64 manufacturer: G-Skill
    part-no: F4-3200C16-8GVKB serial: N/A
  Device-2: DIMM_A2 type: no module installed
  Device-3: DIMM_B1 type: DDR4 detail: synchronous unbuffered (unregistered)
    size: 8 GiB speed: 2133 MT/s volts: curr: 1.2 min: 1.2 max: 1.2
    width (bits): data: 64 total: 64 manufacturer: G-Skill
    part-no: F4-3200C16-8GVKB serial: N/A
  Device-4: DIMM_B2 type: no module installed
PCI Slots:
  Slot: 0 type: PCIe status: in use length: long volts: 3.3 bus-ID: 00:03.1
    children: 1: 08:00.0 class-ID: 0604 type: bridge children: 1: 09:00.0
    class-ID: 0604 type: bridge children: 1: 0a:00.0 class-ID: 0300
    type: display 2: 0a:00.1 class-ID: 0403 type: audio
  Slot: 1 type: PCIe status: available length: long volts: 3.3
    bus-ID: 00:1f.7
  Slot: 2 type: PCIe status: available length: short volts: 3.3
    bus-ID: 00:1f.7
CPU:
  Info: model: AMD Ryzen 5 5600X socket: AM4 bits: 64 type: MT MCP
    arch: Zen 3+ gen: 3 level: v3 note: check built: 2022 process: TSMC n6 (7nm)
    family: 0x19 (25) model-id: 0x21 (33) stepping: 2 microcode: 0xA201211
  Topology: cpus: 1x dies: 1 clusters: 1 cores: 6 threads: 12 tpc: 2
    smt: enabled cache: L1: 384 KiB desc: d-6x32 KiB; i-6x32 KiB L2: 3 MiB
    desc: 6x512 KiB L3: 32 MiB desc: 1x32 MiB
  Speed (MHz): avg: 1738 min/max: 561/4654 boost: enabled
    base/boost: 3700/4650 scaling: driver: amd-pstate-epp governor: powersave
    volts: 1.1 V ext-clock: 100 MHz cores: 1: 1738 2: 1738 3: 1738 4: 1738
    5: 1738 6: 1738 7: 1738 8: 1738 9: 1738 10: 1738 11: 1738 12: 1738
    bogomips: 88637
  Flags: 3dnowprefetch abm adx aes aperfmperf apic arat avic avx avx2 bmi1
    bmi2 bpext cat_l3 cdp_l3 clflush clflushopt clwb clzero cmov cmp_legacy
    constant_tsc cpb cpuid cqm cqm_llc cqm_mbm_local cqm_mbm_total
    cqm_occup_llc cr8_legacy cx16 cx8 de debug_swap decodeassists erms
    extapic extd_apicid f16c flushbyasid fma fpu fsgsbase fsrm fxsr fxsr_opt
    ht hw_pstate ibpb ibrs ibs invpcid irperf lahf_lm lbrv lm mba mca mce
    misalignsse mmx mmxext monitor movbe msr mtrr mwaitx nonstop_tsc nopl npt
    nrip_save nx ospke osvw overflow_recov pae pat pausefilter pclmulqdq
    pdpe1gb perfctr_core perfctr_llc perfctr_nb pfthreshold pge pku pni
    popcnt pse pse36 rapl rdpid rdpru rdrand rdseed rdt_a rdtscp rep_good sep
    sha_ni skinit smap smca smep ssbd sse sse2 sse4_1 sse4_2 sse4a ssse3
    stibp succor svm svm_lock syscall tce topoext tsc tsc_scale umip
    user_shstk v_spec_ctrl v_vmsave_vmload vaes vgif vmcb_clean vme vmmcall
    vpclmulqdq wbnoinvd wdt x2apic xgetbv1 xsave xsavec xsaveerptr xsaveopt
    xsaves xtopology
  Vulnerabilities:
  Type: gather_data_sampling status: Not affected
  Type: ghostwrite status: Not affected
  Type: indirect_target_selection status: Not affected
  Type: itlb_multihit status: Not affected
  Type: l1tf status: Not affected
  Type: mds status: Not affected
  Type: meltdown status: Not affected
  Type: mmio_stale_data status: Not affected
  Type: old_microcode status: Not affected
  Type: reg_file_data_sampling status: Not affected
  Type: retbleed status: Not affected
  Type: spec_rstack_overflow mitigation: Safe RET
  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: Retpolines; IBPB: conditional; IBRS_FW;
    STIBP: always-on; RSB filling; PBRSB-eIBRS: Not affected; BHI: Not
    affected
  Type: srbds status: Not affected
  Type: tsa mitigation: Clear CPU buffers
  Type: tsx_async_abort status: Not affected
  Type: vmscape mitigation: IBPB before exit to userspace
Graphics:
  Device-1: Advanced Micro Devices [AMD/ATI] Navi 44 [Radeon RX 9060 XT]
    vendor: Sapphire driver: amdgpu v: kernel arch: RDNA-4 code: Navi-4x
    process: TSMC n4 (4nm) built: 2025+ pcie: gen: 5 speed: 32 GT/s lanes: 16
    ports: active: HDMI-A-2 empty: DP-1,HDMI-A-1,Writeback-1 bus-ID: 0a:00.0
    chip-ID: 1002:7590 class-ID: 0300
  Display: unspecified server: X.Org v: 24.1.11 with: Xwayland v: 24.1.11
    compositor: kwin_wayland driver: X: loaded: amdgpu
    unloaded: modesetting,radeon alternate: fbdev,vesa dri: radeonsi
    gpu: amdgpu display-ID: :1 screens: 1
  Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x285mm (20.00x11.22")
    s-diag: 582mm (22.93")
  Monitor-1: HDMI-A-2 model: Acer V227Q serial: <filter> built: 2020 res:
    mode: 1920x1080 hz: 60 scale: 100% (1) dpi: 102 gamma: 1.2 chroma: red:
    x: 0.647 y: 0.333 green: x: 0.322 y: 0.627 blue: x: 0.153 y: 0.047 white:
    x: 0.314 y: 0.329 size: 476x268mm (18.74x10.55") diag: 546mm (21.5")
    ratio: 16:9 modes: 1920x1080, 1680x1050, 1280x1024, 1440x900, 1280x960,
    1280x800, 1152x864, 1280x720, 1024x768, 832x624, 800x600, 720x576,
    720x480, 640x480, 720x400
  API: EGL v: 1.5 hw: drv: amd radeonsi platforms: device: 0 drv: radeonsi
    device: 1 drv: swrast gbm: drv: radeonsi surfaceless: drv: radeonsi x11:
    drv: radeonsi inactive: wayland
  API: OpenGL v: 4.6 compat-v: 4.5 vendor: amd mesa v: 26.0.6-arch1.1
    glx-v: 1.4 direct-render: yes renderer: AMD Radeon RX 9060 XT (radeonsi
    gfx1200 ACO DRM 3.64 6.18.26-1-MANJARO) device-ID: 1002:7590
    memory: 15.62 GiB unified: no
  API: Vulkan v: 1.4.341 layers: 2 device: 0 type: discrete-gpu name: AMD
    Radeon RX 9060 XT (RADV GFX1200) driver: mesa radv v: 26.0.6-arch1.1
    device-ID: 1002:7590 surfaces: N/A
  Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo
    de: kscreen-console,kscreen-doctor wl: wayland-info
    x11: xdpyinfo, xprop, xrandr
Audio:
  Device-1: Advanced Micro Devices [AMD/ATI] Navi 48 HDMI/DP Audio
    driver: snd_hda_intel v: kernel pcie: gen: 5 speed: 32 GT/s lanes: 16
    bus-ID: 0a:00.1 chip-ID: 1002:ab40 class-ID: 0403
  Device-2: Advanced Micro Devices [AMD] Starship/Matisse HD Audio
    vendor: ASUSTeK driver: snd_hda_intel v: kernel pcie: gen: 4 speed: 16 GT/s
    lanes: 16 bus-ID: 0c:00.4 chip-ID: 1022:1487 class-ID: 0403
  API: ALSA v: k6.18.26-1-MANJARO status: kernel-api with: aoss
    type: oss-emulator tools: alsactl,alsamixer,amixer
  Server-1: sndiod v: N/A status: off tools: aucat,midicat,sndioctl
  Server-2: JACK v: 1.9.22 status: off tools: N/A
  Server-3: PipeWire v: 1.6.4 status: n/a (root, process) with:
    1: pipewire-pulse status: active 2: wireplumber status: active
    3: pipewire-alsa type: plugin tools: pactl,pw-cat,pw-cli,wpctl
Network:
  Device-1: MEDIATEK MT7921 802.11ax PCIe Wireless Network Adapter [Filogic
    330] vendor: AzureWave driver: mt7921e v: kernel pcie: gen: 2
    speed: 5 GT/s lanes: 1 bus-ID: 06:00.0 chip-ID: 14c3:7961 class-ID: 0280
  IF: wlp6s0 state: up mac: <filter>
  IP v4: <filter> type: dynamic noprefixroute scope: global
    broadcast: <filter>
  IP v6: <filter> type: dynamic noprefixroute scope: global
  IP v6: <filter> type: dynamic noprefixroute scope: global
  IP v6: <filter> type: noprefixroute scope: link
  Device-2: Realtek RTL8125 2.5GbE vendor: ASUSTeK driver: r8169 v: kernel
    pcie: gen: 2 speed: 5 GT/s lanes: 1 port: f000 bus-ID: 07:00.0
    chip-ID: 10ec:8125 class-ID: 0200
  IF: enp7s0 state: down mac: <filter>
  Info: services: NetworkManager, systemd-timesyncd, wpa_supplicant
  WAN IP: <filter>
Bluetooth:
  Device-1: IMC Networks Wireless_Device driver: btusb v: 0.8 type: USB
    rev: 2.1 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 1-5:3 chip-ID: 13d3:3563
    class-ID: e001 serial: <filter>
  Report: rfkill ID: hci0 rfk-id: 0 state: up address: see --recommends
Logical:
  Message: No logical block device data found.
RAID:
  Message: No RAID data found.
Drives:
  Local Storage: total: 2.73 TiB used: 686.77 GiB (24.6%)
  ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Samsung
    model: SSD 970 EVO Plus 1TB 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: 4B2QEXM7 temp: 38.9 C scheme: GPT
  SMART: yes health: PASSED on: 195d 17h cycles: 2,341
    read-units: 56,475,247 [28.9 TB] written-units: 27,670,334 [14.1 TB]
  ID-2: /dev/nvme1n1 maj-min: 259:4 vendor: Western Digital
    model: WD BLACK SN750 SE 1TB size: 931.51 GiB block-size: physical: 512 B
    logical: 512 B speed: 63.2 Gb/s lanes: 4 tech: SSD serial: <filter>
    fw-rev: 711130WD temp: 39.9 C scheme: GPT
  SMART: yes health: PASSED on: 104d 15h cycles: 3,019
    read-units: 80,877,756 [41.4 TB] written-units: 42,285,102 [21.6 TB]
  ID-3: /dev/sda maj-min: 8:0 vendor: Seagate model: ST1000DM010-2EP102
    family: BarraCuda 3.5 (CMR) size: 931.51 GiB block-size: physical: 4096 B
    logical: 512 B sata: 3.0 speed: 6.0 Gb/s tech: HDD rpm: 7200
    serial: <filter> fw-rev: CC46 temp: 32 C scheme: MBR
  SMART: yes state: enabled health: PASSED on: 2y 52d 19h cycles: 2775
    read: 4.51 TiB written: 1.94 TiB Pre-Fail: attribute: Spin_Retry_Count
    value: 100 worst: 100 threshold: 97
  Message: No optical or floppy data found.
Partition:
  ID-1: / raw-size: 931.22 GiB size: 931.22 GiB (100.00%)
    used: 462.7 GiB (49.7%) fs: btrfs block-size: 4096 B dev: /dev/nvme1n1p2
    maj-min: 259:6 label: N/A uuid: 246a4db0-4152-46c2-94e0-79b1495fe607
  ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%)
    used: 668 KiB (0.2%) fs: vfat block-size: 512 B dev: /dev/nvme1n1p1
    maj-min: 259:5 label: N/A uuid: 9DA5-A68D
  ID-3: /home raw-size: 931.22 GiB size: 931.22 GiB (100.00%)
    used: 462.7 GiB (49.7%) fs: btrfs block-size: 4096 B dev: /dev/nvme1n1p2
    maj-min: 259:6 label: N/A uuid: 246a4db0-4152-46c2-94e0-79b1495fe607
  ID-4: /mnt/668EB1FA8EB1C2BB raw-size: 931.51 GiB
    size: 931.51 GiB (100.00%) used: 224.07 GiB (24.1%) fs: ntfs
    block-size: 4096 B dev: /dev/sda1 maj-min: 8:1 label: ShareAndBackup
    uuid: 668EB1FA8EB1C2BB
  ID-5: /var/cache raw-size: 931.22 GiB size: 931.22 GiB (100.00%)
    used: 462.7 GiB (49.7%) fs: btrfs block-size: 4096 B dev: /dev/nvme1n1p2
    maj-min: 259:6 label: N/A uuid: 246a4db0-4152-46c2-94e0-79b1495fe607
  ID-6: /var/log raw-size: 931.22 GiB size: 931.22 GiB (100.00%)
    used: 462.7 GiB (49.7%) fs: btrfs block-size: 4096 B dev: /dev/nvme1n1p2
    maj-min: 259:6 label: N/A uuid: 246a4db0-4152-46c2-94e0-79b1495fe607
Swap:
  Alert: No swap data was found.
Unmounted:
  ID-1: /dev/nvme0n1p1 maj-min: 259:1 size: 16 MiB fs: N/A label: N/A
    uuid: N/A
  ID-2: /dev/nvme0n1p2 maj-min: 259:2 size: 900.25 GiB fs: ntfs label: N/A
    uuid: CAD8CA28D8CA129D
  ID-3: /dev/nvme0n1p3 maj-min: 259:3 size: 100 MiB fs: vfat label: N/A
    uuid: EE7B-F740
USB:
  Hub-1: 1-0:1 info: hi-speed hub with single TT ports: 10 rev: 2.0
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 chip-ID: 1d6b:0002
    class-ID: 0900
  Device-1: 1-3:2 info: QinHeng CH340 serial converter
    type: <vendor specific> driver: ch341,ch341-uart interfaces: 1 rev: 1.1
    speed: 12 Mb/s (1.4 MiB/s) lanes: 1 mode: 1.1 power: 104mA
    chip-ID: 1a86:7523 class-ID: ff00
  Device-2: 1-5:3 info: IMC Networks Wireless_Device type: bluetooth
    driver: btusb interfaces: 3 rev: 2.1 speed: 480 Mb/s (57.2 MiB/s) lanes: 1
    mode: 2.0 power: 100mA chip-ID: 13d3:3563 class-ID: e001 serial: <filter>
  Device-3: 1-6:4 info: ASUSTek AURA LED Controller type: HID
    driver: hid-generic,usbhid interfaces: 2 rev: 2.0 speed: 12 Mb/s (1.4 MiB/s)
    lanes: 1 mode: 1.1 power: 16mA chip-ID: 0b05:1939 class-ID: 0300
    serial: <filter>
  Hub-2: 1-7:5 info: Genesys Logic Hub ports: 4 rev: 2.0
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 power: 100mA
    chip-ID: 05e3:0608 class-ID: 0900
  Hub-3: 2-0:1 info: super-speed hub ports: 4 rev: 3.1
    speed: 10 Gb/s (1.16 GiB/s) lanes: 1 mode: 3.2 gen-2x1 chip-ID: 1d6b:0003
    class-ID: 0900
  Hub-4: 3-0:1 info: hi-speed hub with single TT ports: 4 rev: 2.0
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 chip-ID: 1d6b:0002
    class-ID: 0900
  Device-1: 3-2:2 info: Logitech USB Receiver type: keyboard,mouse,HID
    driver: logitech-djreceiver,usbhid interfaces: 3 rev: 2.0
    speed: 12 Mb/s (1.4 MiB/s) lanes: 1 mode: 1.1 power: 98mA
    chip-ID: 046d:c53f class-ID: 0300
  Device-2: 3-4:3 info: Ducky One 3 TKL RGB type: HID,keyboard,mouse
    driver: hid-generic,usbhid interfaces: 5 rev: 1.1 speed: 12 Mb/s (1.4 MiB/s)
    lanes: 1 mode: 1.1 power: 100mA chip-ID: 3233:8311 class-ID: 0300
    serial: <filter>
  Hub-5: 4-0:1 info: super-speed hub ports: 4 rev: 3.1
    speed: 10 Gb/s (1.16 GiB/s) lanes: 1 mode: 3.2 gen-2x1 chip-ID: 1d6b:0003
    class-ID: 0900
Sensors:
  System Temperatures: cpu: 56.2 C mobo: 38.0 C gpu: amdgpu temp: 39.0 C
    mem: 38.0 C
  Fan Speeds (rpm): N/A gpu: amdgpu fan: 35
Repos:
  Packages: 1613 pm: pacman pkgs: 1596 libs: 493 tools: pamac pm: flatpak
    pkgs: 17
  Active pacman repo servers in: /etc/pacman.d/mirrorlist
    1: https://forksystems.mm.fcix.net/manjaro/stable/$repo/$arch
    2: https://muug.ca/mirror/manjaro/stable/$repo/$arch
    3: https://mirror.fcix.net/manjaro/stable/$repo/$arch
    4: https://manjaro.mirrors.lavatech.top/stable/$repo/$arch
    5: https://mirrors.ft.uam.es/manjaro/stable/$repo/$arch
    6: https://manjaro.c3sl.ufpr.br/stable/$repo/$arch
    7: https://ftp.yz.yamagata-u.ac.jp/pub/linux/manjaro/stable/$repo/$arch
    8: https://mirrors.sjtug.sjtu.edu.cn/manjaro/stable/$repo/$arch
Processes:
  CPU top: 5 of 378
  1: cpu: 40.2% command: baloo_file pid: 788 mem: 53.1 MiB (0.3%)
  2: cpu: 34.9% command: firefox pid: 1684 mem: 528.8 MiB (3.3%)
  3: cpu: 32.5% command: exe pid: 1612 mem: 540.5 MiB (3.4%)
  4: cpu: 20.6% command: vesktop pid: 1485 mem: 333.3 MiB (2.0%)
  5: cpu: 11.8% command: firefox pid: 2173 mem: 289.4 MiB (1.8%)
  Memory top: 5 of 378
  1: mem: 540.5 MiB (3.4%) command: exe pid: 1612 cpu: 32.5%
  2: mem: 528.8 MiB (3.3%) command: firefox pid: 1684 cpu: 34.9%
  3: mem: 336.1 MiB (2.1%) command: plasmashell pid: 1011 cpu: 7.9%
  4: mem: 333.3 MiB (2.0%) command: vesktop pid: 1485 cpu: 20.6%
  5: mem: 289.4 MiB (1.8%) command: firefox pid: 2173 cpu: 11.8%
Info:
  Processes: 378 Power: uptime: 0m states: freeze,mem,disk suspend: deep
    avail: s2idle wakeups: 0 hibernate: platform avail: shutdown, reboot,
    suspend, test_resume image: 6.16 GiB services: org_kde_powerdevil,
    power-profiles-daemon, upowerd Init: systemd v: 260 default: graphical
    tool: systemctl
  Compilers: clang: 22.1.3 gcc: 15.2.1 Shell: Sudo (sudo) v: 1.9.17p2
    default: Bash v: 5.3.9 running-in: konsole inxi: 3.3.40
1 Like
11

Something to keep in mind for reference…

If you use GParted in Manjaro, you can firstly create a GPT partitioning scheme, and create a partition without creating an $ESP. I agree, it’s yet another Windows annoyance we could do without (it’s the same with macOS).

I wonder if you could remove your script to mount the volume, reboot and set it up again in the gnome-disk-utility (Disks) – and post a screenshot of the settings for that volume.

Incorrect permissions can be a contributor to an ntfs volume appearing “read only”, but whether it’s the case here is purely conjecture.

2 Likes
12

I am currently in the process of backing up all my files on said drive (which is taking a gazillion years due to the sheer volume) so I can’t really try it yet. However, I can give you Disks’ user session defaults page on the drive. This is how I set it to automount because I couldn’t figure out how to do it by editing settings files.

I will try re-automounting it first, and if that doesn’t work, create a new partition that hopefully isn’t a MBR.

Screenshot_20260505_085547
Screenshot_20260505_085547653×493 26.4 KB

13

Well, that looks fine, though specifying the filesystem type is generally advisable – replace auto with ntfs.

Preparing the disk with GParted as mentioned might make all the difference. Another option to consider (if you wish to maintain a partition for sharing) is to use format it as exfat instead – it’s not ideal for general or long term storage; not as robust as ntfs; but there should be no problem with permissions – it’s supported by Windows, Linux and macOS.

Incidentally, Disks lists these mounts dynamically in /etc/fstab – if you match the UUID in fstab, and copy/paste that line and change the syntax to resemble the format of the first entries near the top of the file, then the volume should mount permanently from there.

There should be someone lurking about to guide you with the correct syntax if you decide to try that later.

1 Like
14

The partition might have a dirty bit set.

From within Windows admin command prompt:

fsutil dirty query C: - substitute C: for whatever driver letter corresponds to the affected drive.

The chkdsk you ran should have cleared it, unless 1) you have fast startup enabled. 2) you didn’t run chkdsk in an admin command prompt.

If the dirty bit is set, preferably from a windows recovery media (Shift F10 from the Install screen to get a terminal) run chkdsk X: /F /R /X (replace X: with your drive). This should guarantee the disk is unmounted and chkdsk can therefore remove the dirty bit.

15

Some fun facts:

  • Under most circumstances, chkdsk will toggle the dirty bit off when – and only when – the filesystem repair has successfully completed.

  • If the dirty bit is toggled off by some program in a misguided attempt to magically fix an ntfs filesystem, this can impair the ability of chkdsk to correctly do it’s job. In that case, the bit should be toggled on to allow chkdsk to discover and correct existing errors.

  • Generally, chkdsk /f :X is sufficient for most scan/repair sessions.

  • Other parameters such as /f and /r may be used to search for and repair bad sectors, if necessary – warning: bad sector scans must not be interrupted and can take an extremely long time to complete.

  • Ensure you fully understand what each chkdsk command will do and the consequences of ignoring the documentation:

That is all.

2 Likes
16

This, along with setting the filesystem type to ntfs, worked. Glad I tried that before reformatting the drive…

2 Likes