No access to drive D

Today I used my second disk normally. After some time, it stopped responding and the following message appears:

Error mounting system-managed device /dev/sdb1: Unknown error when mounting /mnt

I have no idea what happened

Summary

What’s the problem with not posting garuda-inxi?
It contains additional, useful information about the status of your system.

:warning: Missing information requested in the template may result in not receiving assistance

Make sure you have done the following before you post:

Issue still unresolved? Then:

  • ONE issue per topic.

  • Describe your issue in detail. The more we know, the better we can help

  • Show us the results of your searches, and what you’ve tried

  • After rebooting, post the FULL output of garuda-inxi in the body of the post (not linked externally, or collapsed with the “hide details” feature)

  • Format terminal output (including your garuda-inxi) as a code block by clicking the preformatted text button (</>) , or put three tildes (~) above and below the text

Without garuda-inxi this request will be moved to 412 Precondition Failed

2 Likes
System:
Kernel: 6.8.1-zen1-1-zen arch: x86_64 bits: 64 compiler: gcc v: 13.2.1
clocksource: tsc avail: acpi_pm
parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen
root=UUID=4425f8f3-d76c-423b-96d2-992528dca396 rw rootflags=subvol=@
quiet resume=UUID=33536e01-3c72-4fc8-8486-b580f74dcee0 loglevel=3 ibt=off
Desktop: KDE Plasma v: 6.0.2 tk: Qt v: N/A info: frameworks v: 6.0.0
wm: kwin_wayland with: krunner vt: 1 dm: SDDM Distro: Garuda
base: Arch Linux
Machine:
Type: Laptop System: Micro-Star product: GE72 6QF v: REV:1.0
serial: <superuser required> Chassis: type: 10 serial: <superuser required>
Mobo: Micro-Star model: MS-1794 v: REV:0.A serial: <superuser required>
uuid: <superuser required> UEFI-[Legacy]: American Megatrends
v: E1794IMS.117 date: 01/18/2018
Battery:
ID-1: BAT1 charge: 29.5 Wh (100.0%) condition: 29.5/53.4 Wh (55.2%)
volts: 12.2 min: 10.9 model: MSI BIF0_9 type: Li-ion serial: N/A
status: full
CPU:
Info: model: Intel Core i7-6700HQ bits: 64 type: MT MCP arch: Skylake-S
gen: core 6 level: v3 note: check built: 2015 process: Intel 14nm family: 6
model-id: 0x5E (94) stepping: 3 microcode: 0xF0
Topology: cpus: 1x cores: 4 tpc: 2 threads: 8 smt: enabled cache:
L1: 256 KiB desc: d-4x32 KiB; i-4x32 KiB L2: 1024 KiB desc: 4x256 KiB
L3: 6 MiB desc: 1x6 MiB
Speed (MHz): avg: 800 min/max: 800/3500 scaling: driver: intel_pstate
governor: powersave cores: 1: 800 2: 800 3: 800 4: 800 5: 800 6: 800 7: 800
8: 800 bogomips: 41599
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Vulnerabilities: <filter>
Graphics:
Device-1: Intel HD Graphics 530 vendor: Micro-Star MSI driver: i915
v: kernel arch: Gen-9 process: Intel 14n built: 2015-16 ports: active: eDP-1
empty: DP-1,HDMI-A-1,HDMI-A-2 bus-ID: 00:02.0 chip-ID: 8086:191b
class-ID: 0300
Device-2: NVIDIA GM204M [GeForce GTX 960 OEM / 970M]
vendor: Micro-Star MSI driver: nvidia v: 550.67
alternate: nouveau,nvidia_drm non-free: 545.xx+ status: current (as of
2024-02; EOL~2026-12-xx) arch: Maxwell code: GMxxx process: TSMC 28nm
built: 2014-2019 pcie: gen: 1 speed: 2.5 GT/s lanes: 16 link-max: gen: 3
speed: 8 GT/s bus-ID: 01:00.0 chip-ID: 10de:13d8 class-ID: 0302
Display: wayland server: X.org v: 1.21.1.11 with: Xwayland v: 23.2.4
compositor: kwin_wayland driver: X: loaded: modesetting,nvidia
unloaded: nouveau alternate: fbdev,intel,nv,vesa dri: iris
gpu: i915,nvidia display-ID: 0
Monitor-1: eDP-1 res: 1920x1080 size: N/A modes: N/A
API: EGL v: 1.5 hw: drv: intel iris drv: nvidia platforms: device: 0
drv: nvidia device: 2 drv: iris device: 3 drv: swrast gbm: drv: nvidia
surfaceless: drv: nvidia wayland: drv: iris x11: drv: iris
inactive: device-1
API: OpenGL v: 4.6.0 compat-v: 4.5 vendor: intel mesa v: 24.0.3-arch1.2
glx-v: 1.4 direct-render: yes renderer: Mesa Intel HD Graphics 530 (SKL GT2)
device-ID: 8086:191b memory: 7.46 GiB unified: yes display-ID: :1.0
API: Vulkan v: 1.3.279 layers: 4 device: 0 type: integrated-gpu name: Intel
HD Graphics 530 (SKL GT2) driver: mesa intel v: 24.0.3-arch1.2
device-ID: 8086:191b surfaces: xcb,xlib,wayland device: 1
type: discrete-gpu name: NVIDIA GeForce GTX 970M driver: nvidia v: 550.67
device-ID: 10de:13d8 surfaces: xcb,xlib,wayland device: 2 type: cpu
name: llvmpipe (LLVM 17.0.6 256 bits) driver: mesa llvmpipe
v: 24.0.3-arch1.2 (LLVM 17.0.6) device-ID: 10005:0000
surfaces: xcb,xlib,wayland
Audio:
Device-1: Intel 100 Series/C230 Series Family HD Audio
vendor: Micro-Star MSI driver: snd_hda_intel v: kernel
alternate: snd_soc_avs bus-ID: 00:1f.3 chip-ID: 8086:a170 class-ID: 0403
API: ALSA v: k6.8.1-zen1-1-zen status: kernel-api tools: N/A
Server-1: PipeWire v: 1.0.4 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
Network:
Device-1: Intel Wireless 3165 driver: iwlwifi v: kernel pcie: gen: 1
speed: 2.5 GT/s lanes: 1 bus-ID: 02:00.0 chip-ID: 8086:3165 class-ID: 0280
IF: wlp2s0 state: down mac: <filter>
Device-2: Qualcomm Atheros Killer E2400 Gigabit Ethernet
vendor: Micro-Star MSI driver: alx v: kernel pcie: gen: 1 speed: 2.5 GT/s
lanes: 1 port: d000 bus-ID: 03:00.0 chip-ID: 1969:e0a1 class-ID: 0200
IF: enp3s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Info: services: NetworkManager, systemd-timesyncd, wpa_supplicant
Bluetooth:
Device-1: Intel Bluetooth wireless interface driver: btusb v: 0.8 type: USB
rev: 2.0 speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 1-10:4 chip-ID: 8087:0a2a
class-ID: e001
Report: btmgmt ID: hci0 rfk-id: 0 state: up address: <filter> bt-v: 4.2
lmp-v: 8 status: discoverable: no pairing: no class-ID: 6c010c
Drives:
Local Storage: total: 1.2 TiB used: 84.86 GiB (6.9%)
ID-1: /dev/mmcblk0 maj-min: 179:0 vendor: Samsung model: EC2QT
size: 59.62 GiB block-size: physical: 512 B logical: 512 B type: USB
tech: SSD serial: <filter> scheme: MBR
SMART Message: Unknown smartctl error. Unable to generate data.
SMART Message: Unable to run smartctl. Root privileges required.
ID-2: /dev/sda maj-min: 8:0 vendor: A-Data model: SP900NS38
size: 238.47 GiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
tech: SSD serial: <filter> fw-rev: 3b scheme: MBR
ID-3: /dev/sdb maj-min: 8:16 vendor: HGST (Hitachi) model: HTS721010A9E630
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: A3J0 scheme: GPT
Partition:
ID-1: / raw-size: 229.67 GiB size: 229.67 GiB (100.00%)
used: 84.86 GiB (36.9%) fs: btrfs dev: /dev/sda1 maj-min: 8:1
ID-2: /home raw-size: 229.67 GiB size: 229.67 GiB (100.00%)
used: 84.86 GiB (36.9%) fs: btrfs dev: /dev/sda1 maj-min: 8:1
ID-3: /var/log raw-size: 229.67 GiB size: 229.67 GiB (100.00%)
used: 84.86 GiB (36.9%) fs: btrfs dev: /dev/sda1 maj-min: 8:1
ID-4: /var/tmp raw-size: 229.67 GiB size: 229.67 GiB (100.00%)
used: 84.86 GiB (36.9%) fs: btrfs dev: /dev/sda1 maj-min: 8:1
Swap:
Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default) zswap: no
ID-1: swap-1 type: zram size: 7.64 GiB used: 465.8 MiB (6.0%)
priority: 100 comp: zstd avail: lzo,lzo-rle,lz4,lz4hc,842 max-streams: 8
dev: /dev/zram0
ID-2: swap-2 type: partition size: 8.8 GiB used: 0 KiB (0.0%) priority: -2
dev: /dev/sda2 maj-min: 8:2
Sensors:
System Temperatures: cpu: 60.0 C pch: 59.5 C mobo: N/A
Fan Speeds (rpm): N/A
Info:
Memory: total: 8 GiB available: 7.64 GiB used: 4.03 GiB (52.8%)
Processes: 262 Power: uptime: 29m states: freeze,mem,disk suspend: deep
avail: s2idle wakeups: 0 hibernate: platform avail: shutdown, reboot,
suspend, test_resume image: 3.01 GiB services: org_kde_powerdevil,
power-profiles-daemon, upowerd Init: systemd v: 255 default: graphical
tool: systemctl
Packages: 1477 pm: pacman pkgs: 1468 libs: 419 tools: octopi,pamac,paru
pm: flatpak pkgs: 9 Compilers: gcc: 13.2.1 Shell: garuda-inxi default: fish
v: 3.7.0 running-in: konsole inxi: 3.3.33
Garuda (2.6.23-1):
System install date:     2024-02-03
Last full system update: 2024-03-24
Is partially upgraded:   No
Relevant software:       snapper NetworkManager dracut nvidia-dkms
Windows dual boot:       <superuser required>
Failed units:
$MFTMirr does not match $MFT (record 3).
Failed to mount '/dev/sdb1': Błąd wejścia/wyjścia
NTFS is inconsistent. Run chkdsk /f on Windows then reboot it TWICE!
The usage of the /f parameter is very IMPORTANT! No modification was
made to NTFS by this software.

Failed to open '/dev/sdb1'.

$MFTMirr does not match $MFT (record 3).
Failed to mount '/dev/sdb1': Input/output error
NTFS is inconsistent. Run chkdsk /f on Windows then reboot it TWICE!
The usage of the /f parameter is very IMPORTANT! No modification was
made to NTFS by this software.

Please, use LANG=C in front of commands.

Post

lsblk -f

and fix M$ :slight_smile:

Always shutdown PC from M$, don’t reboot to Garuda.

I’m sorry, but the translation is poor. Can you explain what exactly I should do?

NAME FSTYPE FSVER LABEL      UUID                                 FSAVAIL FSUSE% MOUNTPOINTS
sda
├─sda1
│    btrfs                   4425f8f3-d76c-423b-96d2-992528dca396  142,7G    37% /var/tmp
│                                                                                /var/log
│                                                                                /var/cache
│                                                                                /srv
│                                                                                /home
│                                                                                /root
│                                                                                /
└─sda2
swap   1     swap       33536e01-3c72-4fc8-8486-b580f74dcee0                [SWAP]
sdb
└─sdb1
ntfs         multimedia BC1CE1391CE0EF78
sr0
mmcblk0
│
├─mmcblk0p1
│    ext4   1.0              e596c44d-8946-4452-9e2b-08e019257442
└─mmcblk0p2
swap   1     swap       de542637-81a7-45cd-8e0d-ea3423a62c4e
zram0
[SWAP]

I believe the error message is self explanatory. Please follow it.

3 Likes

Try garuda-inxi command again prefaced by sudo

There is no-such-thing as a Drive D in Linux. So you are apparently referring to a Windows drive D formatted in NTFS? That would fit with your error msg.

First, NTFS is a very fragile file system and its best not to access Windows NTFS drives while in Linux. That’s best practice.
Second, it’s easiest to fix in Windows. Use their tools. But if you don’t choose that route, you can probably repair it in Linux using ntfsfix.
Third, if you don’t use Windows anymore, consider converting that drive to a Linux format.

Best luck! :smiley:

4 Likes

windows have not been used for many months. I only have Garuda Linux

What about?

No Windows? Do this. Lookup the command. :slight_smile:

2 Likes

there are very important documents on the disk, files from my work. Very important is an understatement

Lookup! NTFSFIX

4 Likes
ERROR: You must specify a device.
ntfsfix v2022.10.3 (libntfs-3g)

Usage: ntfsfix [options] device
Attempt to fix an NTFS partition.

-b, --clear-bad-sectors Clear the bad sector list
-d, --clear-dirty       Clear the volume dirty flag
-h, --help              Display this help
-n, --no-action         Do not write anything
-V, --version           Display version information

For example: ntfsfix /dev/hda6

Developers' email address: [email protected]
News, support and information:  https://github.com/tuxera/ntfs-3g/

https://wiki.archlinux.org/title/NTFS#unknown_filesystem_type_‘ntfs’

This is not a chat room. Show some incentive.

https://wiki.archlinux.org/title/NTFS-3G

https://wiki.archlinux.org/title/NTFS-3G#Troubleshooting

https://wiki.archlinux.org/title/NTFS-3G#Damaged_NTFS_filesystems

4 Likes

6 Likes

maybe I’ll thank you for not helping.

You’re going to need to spend time reading and learning. No one here is going to take responsibility for doing your work for you. They’re your files.

This is a topic rehashed multiple times in this forum. Search

3 Likes

Unfortunately there is no emoji for, users in “panic mode”.

Good luck. :wave:

3 Likes

https://forum.garudalinux.org/search?context=topic&context_id=35725&q=ntfsfix%20%20status%3Asolved%20order%3Alatest&skip_context=true

4 Likes

the solution to the problem is here.