Error while accessing the windows partition

Support
1

whenever i want to access the windows partition it is showing me An error occurred while accessing 'Basic data partition', the system responded: The requested operation has failed: Error mounting /dev/nvme0n1p3 at /run/media/harsh/74FE122FFE11EA5E: wrong fs type, bad option, bad superblock on /dev/nvme0n1p3, missing codepage or helper program, or other error.

image
image1920Ă—1200 144 KB

System:
  Kernel: 6.6.8-2-MANJARO arch: x86_64 bits: 64 compiler: gcc v: 13.2.1
    clocksource: tsc available: acpi_pm
    parameters: BOOT_IMAGE=/boot/vmlinuz-6.6-x86_64
    root=UUID=ae935713-3636-423f-8804-43ca0faf5eb0 rw quiet splash
    udev.log_priority=3
  Desktop: KDE Plasma v: 5.27.10 tk: Qt v: 5.15.11 wm: kwin_x11 vt: 2
    dm: SDDM Distro: Manjaro Linux base: Arch Linux
Machine:
  Type: Laptop System: LENOVO product: 83BF v: IdeaPad Slim 5 14IAH8
    serial: <superuser required> Chassis: type: 10 v: IdeaPad Slim 5 14IAH8
    serial: <superuser required>
  Mobo: LENOVO model: LNVNB161216 v: SDK0T76485 WIN
    serial: <superuser required> UEFI: LENOVO v: LACN29WW date: 09/01/2023
Battery:
  ID-1: BAT1 charge: 31.6 Wh (55.2%) condition: 57.2/56.6 Wh (101.0%)
    power: 47.9 W volts: 12.3 min: 11.5 model: LGES L22L3PA4 type: Unknown
    serial: <filter> status: charging
  Device-1: hidpp_battery_0 model: Logitech Wireless Mouse serial: <filter>
    charge: 50% (should be ignored) rechargeable: yes status: N/A
CPU:
  Info: model: 12th Gen Intel Core i5-12450H bits: 64 type: MST AMCP
    arch: Alder Lake gen: core 12 level: v3 note: check built: 2021+
    process: Intel 7 (10nm ESF) family: 6 model-id: 0x9A (154) stepping: 3
    microcode: 0x430
  Topology: cpus: 1x cores: 8 mt: 4 tpc: 2 st: 4 threads: 12 smt: enabled
    cache: L1: 704 KiB desc: d-4x32 KiB, 4x48 KiB; i-4x32 KiB, 4x64 KiB L2: 7 MiB
    desc: 4x1.2 MiB, 1x2 MiB L3: 12 MiB desc: 1x12 MiB
  Speed (MHz): avg: 498 high: 879 min/max: 400/4400:3300 scaling:
    driver: intel_pstate governor: powersave cores: 1: 400 2: 400 3: 400 4: 400
    5: 656 6: 400 7: 850 8: 400 9: 879 10: 400 11: 400 12: 400 bogomips: 59916
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
  Vulnerabilities:
  Type: gather_data_sampling 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: retbleed status: Not affected
  Type: spec_rstack_overflow 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: Enhanced / Automatic IBRS, IBPB: conditional,
    RSB filling, PBRSB-eIBRS: SW sequence
  Type: srbds status: Not affected
  Type: tsx_async_abort status: Not affected
Graphics:
  Device-1: Intel Alder Lake-P GT1 [UHD Graphics] vendor: Lenovo driver: i915
    v: kernel arch: Gen-12.2 process: Intel 10nm built: 2021-22+ ports:
    active: eDP-1 empty: DP-1,DP-2,HDMI-A-1 bus-ID: 00:02.0 chip-ID: 8086:46a3
    class-ID: 0300
  Device-2: Chicony Integrated Camera driver: uvcvideo type: USB rev: 2.0
    speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 3-5:3 chip-ID: 04f2:b7b9
    class-ID: fe01 serial: <filter>
  Display: x11 server: X.Org v: 21.1.10 compositor: kwin_x11 driver: X:
    loaded: modesetting alternate: fbdev,vesa dri: iris gpu: i915 display-ID: :0
    screens: 1
  Screen-1: 0 s-res: 1920x1200 s-dpi: 96 s-size: 508x317mm (20.00x12.48")
    s-diag: 599mm (23.57") monitors: <missing: xrandr>
  Monitor-1: eDP-1 model: ChiMei InnoLux 0x1457 built: 2022 res: 1920x1200
    dpi: 162 gamma: 1.2 size: 301x188mm (11.85x7.4") diag: 355mm (14")
    ratio: 16:10 modes: 1920x1200
  API: EGL v: 1.5 hw: drv: intel iris platforms: device: 0 drv: iris
    device: 1 drv: swrast surfaceless: drv: iris x11: drv: iris
    inactive: gbm,wayland
  API: OpenGL v: 4.6 compat-v: 4.5 vendor: intel mesa v: 23.1.9-manjaro1.1
    glx-v: 1.4 direct-render: yes renderer: Mesa Intel Graphics (ADL GT2)
    device-ID: 8086:46a3 memory: 14.99 GiB unified: yes
  API: Vulkan v: 1.3.274 layers: N/A device: 0 type: integrated-gpu
    name: Intel Graphics (ADL GT2) driver: mesa intel v: 23.1.9-manjaro1.1
    device-ID: 8086:46a3 surfaces: xcb,xlib
Audio:
  Device-1: Intel Alder Lake PCH-P High Definition Audio vendor: Lenovo
    driver: snd_hda_intel v: kernel alternate: snd_sof_pci_intel_tgl
    bus-ID: 00:1f.3 chip-ID: 8086:51c8 class-ID: 0403
  API: ALSA v: k6.6.8-2-MANJARO status: kernel-api with: aoss
    type: oss-emulator tools: alsactl,alsamixer,amixer
  Server-1: JACK v: 1.9.22 status: off tools: N/A
  Server-2: PipeWire v: 1.0.0 status: active 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: Realtek RTL8852BE PCIe 802.11ax Wireless Network vendor: Lenovo
    driver: rtw89_8852be v: kernel pcie: gen: 1 speed: 2.5 GT/s lanes: 1
    port: 3000 bus-ID: 03:00.0 chip-ID: 10ec:b852 class-ID: 0280
  IF: wlp3s0 state: up mac: <filter>
Bluetooth:
  Device-1: Realtek Bluetooth Radio driver: btusb v: 0.8 type: USB rev: 1.0
    speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 3-10:4 chip-ID: 0bda:4853
    class-ID: e001 serial: <filter>
  Report: rfkill ID: hci0 rfk-id: 2 state: up address: see --recommends
Drives:
  Local Storage: total: 476.94 GiB used: 95.5 GiB (20.0%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Western Digital model: WD PC
    SN740 SDDPMQD-512G-1101 size: 476.94 GiB block-size: physical: 512 B
    logical: 512 B speed: 63.2 Gb/s lanes: 4 tech: SSD serial: <filter>
    fw-rev: 73110001 temp: 37.9 C scheme: GPT
Partition:
  ID-1: / raw-size: 160 GiB size: 156.43 GiB (97.77%) used: 16 GiB (10.2%)
    fs: ext4 dev: /dev/nvme0n1p5 maj-min: 259:5
  ID-2: /boot/efi raw-size: 100 MiB size: 96 MiB (96.00%)
    used: 35.7 MiB (37.2%) fs: vfat dev: /dev/nvme0n1p1 maj-min: 259:1
Swap:
  Alert: No swap data was found.
Sensors:
  System Temperatures: cpu: 39.0 C mobo: N/A
  Fan Speeds (rpm): N/A
Info:
  Processes: 278 Uptime: 9m wakeups: 0 Memory: total: 16 GiB note: est.
  available: 15.35 GiB used: 3.21 GiB (20.9%) Init: systemd v: 254
  default: graphical tool: systemctl Compilers: gcc: 13.2.1 clang: 16.0.6
  Packages: pm: pacman pkgs: 1181 libs: 347 tools: pamac,yay pm: flatpak
  pkgs: 0 Shell: Zsh v: 5.9 default: Bash v: 5.2.21 running-in: konsole
  inxi: 3.3.31
2

Error mounting NTFS HDD: [Wrong fs type, bad option, bad superblock]

The Linux NTFS filesystem driver – ntfs3 – returns a mount failure error when damage, or rather, an indicator of damage to an NTFS filesystem is found. This indicator is commonly referred to as a dirty bit.

When a dirty bit is detected, ntfs3 prevents an NTFS filesystem from being mounted. This is by design, and is a safety feature of ntfs3 intended to prevent further damage through continued use of the NTFS filesystem. Any damage must be properly repaired, and the dirty bit cleared, before the partition is allowed to mount.

Though a dirty bit can be cleared within Linux, this action does not repair any damage to a filesystem. A tool specifically designed to correct Windows filesystem errors, such as ChkDsk, should be used to diagnose and repair NTFS.

A note on Windows utilities for NTFS

Each of these utilites must be run from an administrative command prompt in Windows.

chkdsk can clear a dirty bit if one of these conditions are met:

  • A check/repair is successfully performed on the NTFS filesystem
  • No damage to the NTFS filesystem is found after a successful check/repair

fsutil can also check for or set a dirty bit:

  • Check for a dirty bit: fsutil dirty query x:
  • Set the dirty bit: fsutil dirty set x:
  • A dirty bit cannot be cleared using fsutil

Fix NTFS errors using Windows ChkDsk

If damage is indicated on an NTFS filesystem this should be checked/repaired from within a Windows environment, by launching the Windows chkdsk utility from an administrative command prompt.

ChkDsk will check/repair any damage to an NTFS filesystem, clear the dirty bit, and allow the partition to be mounted in Linux using ntfs3.

chkdsk /f x:
  • x: denotes the drive letter of the disk as it appears in Windows.

What if I don’t have Windows installed?:

ChkDsk may also be run from a bootable:

Note: An OEM Windows Recovery Disc of any kind is not suitable.

ChkDisk fixed my NTFS drive and now it mounts with no errors:

No further action is needed. Continue using your NTFS filesystem as before.

What if my NTFS filesystem still doesn’t mount?:

If ntfs3 still refuses to mount your NTFS drive, then ChkDsk was unsuccessful, and deeper issues with your NTFS volume, or the disk itself, may be indicated. Other recovery methods exist, but they are outside the scope of this document.

It is possible, however, to substitute the ntfs3 kernel driver for the FUSE-based ntfs-3g driver package. Doing so will allow the NTFS volume to mount, but at great risk.

See Blacklist the ntfs3 kernel module (Optional).

Blacklist the ntfs3 kernel module (Optional)

A note on blacklisting ntfs3 in favour of ntfs-3g

ntfs3 will not mount an NTFS filesystem if it is marked dirty.

Important to note is that ntfs-3g works around this by virtue of ignoring the dirty bit. Any damage to the volume therefore is also ignored. Continued use of the volume risks even greater accumulated damage to the NTFS filesystem.

It is said that “Ignorance is bliss”

Blacklisting ntfs3 and opting to use ntfs-3g allows the NTFS volume to be mounted – but that’s all it does – If the NTFS volume is damaged, it remains damaged, while you remain blissfully unaware that any problem exists.

What does this mean?:

A check/repair using ChkDsk is recommended regardless of which NTFS driver is used.

Because ntfs-3g ignores the dirty bit, you won’t know if the volume is damaged, until it’s too late. Data loss is possible!

Procedure to blacklist ntfs3 and use ntfs-3g:

Install ntfs-3g:

# Check whether the `ntfs-3g` package is installed
pacman -Qi ntfs-3g

# Install the `ntfs-3g` package, if needed
sudo pacman -S ntfs-3g

Blacklist ntfs3:

echo 'blacklist ntfs3' | sudo tee /etc/modprobe.d/blacklist-ntfs3.conf

To reverse this decision at any time, delete blacklist-ntfs3.conf:

sudo rm /etc/modprobe.d/blacklist-ntfs3.conf

Note: The ntfs-3g package can remain installed, if desired, as ntfs3 will take precedence if no longer blacklisted. ntfs-3g might optionally be used to manually mount a volume, for example, in preference to ntfs3.

I think that just about covers it.

1 Like
3

Hi @Nobita,

That inxi seems woefully incomplete. It should be something like this:

$ inxi --full --admin --filter --width

System:
  Kernel: 6.1.69-1-MANJARO arch: x86_64 bits: 64 compiler: gcc v: 13.2.1
    clocksource: tsc available: acpi_pm
    parameters: BOOT_IMAGE=/boot/vmlinuz-6.1-x86_64
    root=UUID=9a26c8d0-43f4-44ad-a7d3-861d6f6cdbfa rw quiet
    udev.log_priority=3 modprobe.blacklist=iTCO_wdt
  Desktop: KDE Plasma v: 5.27.10 tk: Qt v: 5.15.11 info: cairo-dock
    wm: kwin_x11 dm: SDDM Distro: Manjaro Linux base: Arch Linux
Machine:
  Type: Desktop System: Gigabyte product: Z370 HD3 v: N/A serial: N/A
  Mobo: Gigabyte model: Z370 HD3-CF serial: N/A UEFI: American Megatrends
    v: F14 date: 11/13/2021
CPU:
  Info: model: Intel Core i7-8700 socket: LGA1151 (U3E1) note: check bits: 64
    type: MT MCP arch: Coffee Lake gen: core 8 level: v3 note: check built: 2018
    process: Intel 14nm family: 6 model-id: 0x9E (158) stepping: 0xA (10)
    microcode: 0xF4
  Topology: cpus: 1x cores: 6 tpc: 2 threads: 12 smt: enabled cache:
    L1: 384 KiB desc: d-6x32 KiB; i-6x32 KiB L2: 1.5 MiB desc: 6x256 KiB
    L3: 12 MiB desc: 1x12 MiB
  Speed (MHz): avg: 1722 high: 4501 min/max: 800/4600 base/boost: 4300/8300
    scaling: driver: intel_pstate governor: performance volts: 1.1 V
    ext-clock: 100 MHz cores: 1: 4474 2: 800 3: 4501 4: 800 5: 800 6: 800
    7: 800 8: 800 9: 4500 10: 800 11: 800 12: 800 bogomips: 76831
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
  Vulnerabilities:
  Type: gather_data_sampling mitigation: Microcode
  Type: itlb_multihit status: KVM: VMX disabled
  Type: l1tf mitigation: PTE Inversion; VMX: conditional cache flushes, SMT
    vulnerable
  Type: mds mitigation: Clear CPU buffers; SMT vulnerable
  Type: meltdown mitigation: PTI
  Type: mmio_stale_data mitigation: Clear CPU buffers; SMT vulnerable
  Type: retbleed mitigation: IBRS
  Type: spec_rstack_overflow 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: IBRS, IBPB: conditional, STIBP: conditional,
    RSB filling, PBRSB-eIBRS: Not affected
  Type: srbds mitigation: Microcode
  Type: tsx_async_abort mitigation: TSX disabled
Graphics:
  Device-1: NVIDIA GM206 [GeForce GTX 960] vendor: Gigabyte driver: nvidia
    v: 545.29.06 alternate: nouveau,nvidia_drm non-free: 545.xx+ status: current
    (as of 2023-11; EOL~2026-12-xx) arch: Maxwell code: GMxxx
    process: TSMC 28nm built: 2014-2019 pcie: gen: 3 speed: 8 GT/s lanes: 16
    bus-ID: 01:00.0 chip-ID: 10de:1401 class-ID: 0300
  Display: server: X.Org v: 21.1.10 compositor: kwin_x11 driver: X:
    loaded: nvidia gpu: nvidia display-ID: :0 screens: 1
  Screen-1: 0 s-res: 5120x1080 s-dpi: 97 s-size: 1341x283mm (52.80x11.14")
    s-diag: 1371mm (53.96")
  Monitor-1: DVI-I-1 pos: right res: 2560x1080 hz: 60 dpi: 97
    size: 673x284mm (26.5x11.18") diag: 730mm (28.76") modes: N/A
  Monitor-2: HDMI-0 pos: primary,left res: 2560x1080 hz: 60 dpi: 97
    size: 673x284mm (26.5x11.18") diag: 730mm (28.76") modes: N/A
  API: EGL v: 1.5 hw: drv: nvidia platforms: device: 0 drv: nvidia device: 2
    drv: swrast gbm: drv: nvidia surfaceless: drv: nvidia x11: drv: nvidia
    inactive: wayland,device-1
  API: OpenGL v: 4.6.0 compat-v: 4.5 vendor: nvidia mesa v: 545.29.06
    glx-v: 1.4 direct-render: yes renderer: NVIDIA GeForce GTX 960/PCIe/SSE2
    memory: 1.95 GiB
  API: Vulkan v: 1.3.274 layers: 1 device: 0 type: discrete-gpu
    name: NVIDIA GeForce GTX 960 driver: nvidia v: 545.29.06 device-ID: 10de:1401
    surfaces: xcb,xlib
Audio:
  Device-1: Intel 200 Series PCH HD Audio vendor: Gigabyte
    driver: snd_hda_intel v: kernel bus-ID: 00:1f.3 chip-ID: 8086:a2f0
    class-ID: 0403
  Device-2: NVIDIA GM206 High Definition Audio vendor: Gigabyte
    driver: snd_hda_intel v: kernel pcie: gen: 3 speed: 8 GT/s lanes: 16
    bus-ID: 01:00.1 chip-ID: 10de:0fba class-ID: 0403
  API: ALSA v: k6.1.69-1-MANJARO status: kernel-api with: aoss
    type: oss-emulator tools: alsactl,alsamixer,amixer
  Server-1: JACK v: 1.9.22 status: off tools: N/A
  Server-2: PipeWire v: 1.0.0 status: n/a (root, process)
    with: pipewire-media-session status: active tools: pw-cli
  Server-3: PulseAudio v: 16.1 status: active (root, process) with:
    1: pulseaudio-alsa type: plugin 2: pulseaudio-jack type: module
    tools: pacat,pactl
Network:
  Device-1: Intel Ethernet I219-V vendor: Gigabyte driver: e1000e v: kernel
    port: N/A bus-ID: 00:1f.6 chip-ID: 8086:15b8 class-ID: 0200
  IF: eno1 state: up speed: 1000 Mbps duplex: full mac: <filter>
Drives:
  Local Storage: total: 8.41 TiB used: 2.97 TiB (35.3%)
  ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Samsung model: SSD 960 EVO 250GB
    size: 232.89 GiB block-size: physical: 512 B logical: 512 B speed: 31.6 Gb/s
    lanes: 4 tech: SSD serial: <filter> fw-rev: 3B7QCXE7 temp: 29.9 C
    scheme: GPT
  SMART: yes health: PASSED on: 192d 14h cycles: 3,215
    read-units: 54,388,830 [27.8 TB] written-units: 42,235,987 [21.6 TB]
  ID-2: /dev/sda maj-min: 8:0 vendor: Seagate model: ST4000DM000-1F2168
    family: Desktop HDD.15 size: 3.64 TiB block-size: physical: 4096 B
    logical: 512 B sata: 3.1 speed: 6.0 Gb/s tech: HDD rpm: 5900
    serial: <filter> fw-rev: CC54 temp: 30 C scheme: GPT
  SMART: yes state: enabled health: PASSED on: 3y 144d 2h cycles: 3525
    read: 123.22 TiB written: 62.78 TiB Old-Age: UDMA CRC errors: 13567
    alert: Bad cable/connection? Pre-Fail: end-to-end: 99 threshold: 99
    alert: FAILING_NOW attribute: Spin_Retry_Count value: 100 worst: 100
    threshold: 97
  ID-3: /dev/sdb maj-min: 8:16 vendor: Seagate model: ST5000VX0011-1T317X
    family: Surveillance size: 4.55 TiB block-size: physical: 4096 B
    logical: 512 B sata: 3.1 speed: 6.0 Gb/s tech: HDD rpm: 7200
    serial: <filter> fw-rev: VN02 temp: 33 C scheme: GPT
  SMART: yes state: enabled health: PASSED on: 1y 233d 17h cycles: 2592
    read: 77.92 TiB written: 17.08 TiB Pre-Fail: attribute: Spin_Retry_Count
    value: 100 worst: 100 threshold: 97
Partition:
  ID-1: / raw-size: 224.58 GiB size: 220 GiB (97.96%) used: 84.84 GiB (38.6%)
    fs: ext4 block-size: 4096 B dev: /dev/nvme0n1p3 maj-min: 259:3
  ID-2: /boot/efi raw-size: 500 MiB size: 499 MiB (99.80%)
    used: 296 KiB (0.1%) fs: vfat block-size: 512 B dev: /dev/nvme0n1p1
    maj-min: 259:1
Swap:
  Kernel: swappiness: 10 (default 60) cache-pressure: 75 (default 100)
    zswap: yes compressor: zstd max-pool: 20%
  ID-1: swap-1 type: partition size: 7.81 GiB used: 0 KiB (0.0%) priority: -2
    dev: /dev/nvme0n1p2 maj-min: 259:2
Sensors:
  System Temperatures: cpu: 30.0 C mobo: N/A gpu: nvidia temp: 31 C
  Fan Speeds (rpm): N/A gpu: nvidia fan: 65%
Info:
  Processes: 305 Uptime: 3h 48m wakeups: 1 Memory: total: 16 GiB
  available: 15.55 GiB used: 4.79 GiB (30.8%) Init: systemd v: 254
  default: graphical tool: systemctl Compilers: gcc: 13.2.1 clang: 16.0.6
  Packages: pm: pacman pkgs: 1972 libs: 472 tools: pamac pm: appimage pkgs: 0
  Shell: Sudo (sudo) v: 1.9.15p4 default: Zsh v: 5.9 running-in: yakuake
  inxi: 3.3.31

Anyway, If it’s a NTFS partition like you said, it might simply that Windows wasn’t shut down properly. Or that fast boot/startup is enabled. So, check your BIOS/UEFI for that and make sure Fast startup/boot is disabled, as well as Secure boot.

Also check in Windows itself that Fast startup/boot is disabled, and make absolutely 100% that it’s not hibernated, but properly shut down.

4

secure boot and fast startup is disabled

5

echo 'blacklist ntfs3' | sudo tee /etc/modprobe.d/blacklist-ntfs3.conf
using this command my problem has been fixed.
Thanks all for helping

6

No. Your problem has not been fixed.

Please read the entire post in context, and understand that blacklisting ntfs3 ONLY allows the Windows drive to mount. It DOES NOT fix damage to the NTFS filesystem.

Or, ignore this completely, and enjoy potential data loss.

Cheers.

1 Like
7

but now that partition is showing . All the files are also showing
if anything wrong please help me

8

It’s all there in the post, please read it fully.

Are you multibooting with Windows?

9

yes i have dual boot with windows

10

OK, then that makes it a lot easier for you to follow the instructions, and use chkdsk in Windows. It’s a good idea to run chkdsk regularly on the shared NTFS drive. Linux has no tools to safely fix NTFS drives. Windows chkdsk is the best option.

As @Mirdarthos mentioned, Fast Startup in Windows should be disabled, as it seriously messes with Linux. Fast Startup is a variant of hibernation; when it’s activated, Windows hibernates instead of shutting down, or restarting.

powercfg /h off

…from an administrative command prompt in Windows, will disable it.

11

Translation: He said you should first repair your NTFS Partition with Windows Tools,
to blacklist NTFS3 and mount it with the dangerous option NTFS-3G should be the last option on earth… atleast mount it in READ Only, if you have too… if you can’t repair it.

12

This topic was automatically closed 36 hours after the last reply. New replies are no longer allowed.