Hdd mount problem

For some months the problem appeared first on my Lenovo laptop. I could not mount the HDD anymore ((after boot)).
I found out that with a previous snapshot the HDD was still mountable.
The problem is that I cannot update Garuda anymore because my external HDD won’t be mountable anymore.
I thouhgt it is an HW problem specific for the chinese AMD Laptop, but as I run the Garuda on an Intel-HP desktop as well, I found there I have the same problem now.
Any perspectives for the core team to find what is wrong with their updates?

It doesn’t look at all a problem specific to Garuda.
Just because you find it with garuda-update, it doesn’t necessarily mean that is the source of the problem.
It sounds like a kernel update, or maybe another package recently updated.
I’d tell you to try switching to the linux-lts kernel, but I don’t know your current kernel without the required garuda-inxi.

6 Likes

Hello. I’ve moved your thread to the Issues & Assistance category.
As filo mentioned, could we get a garuda-inxi of the snapshot you restored?
Also, could you list the output of the garuda-update command so we can see what it was trying to do? As filo mentioned, there was updates to kernels very recently.

6 Likes

I would test a bunch of different kernels. Be sure to test an alternate that uses a different I/O scheduler.

4 Likes

INXI of the system with old snapshot (let me know if this is good enough) thanks:

System:
  Kernel: 6.4.7-zen1-3-zen arch: x86_64 bits: 64 compiler: gcc v: 13.2.1
    parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen
    root=UUID=023ce1e3-fd7d-48a7-9fea-885bc9ac9a6a rw rootflags=subvol=@
    quiet quiet rd.udev.log_priority=3 vt.global_cursor_default=0 loglevel=3
    ibt=off
  Desktop: KDE Plasma v: 5.27.7 tk: Qt v: 5.15.10 wm: kwin_x11 vt: 2
    dm: SDDM Distro: Garuda Linux base: Arch Linux
Machine:
  Type: Laptop System: LENOVO product: 82RN v: IdeaPad 3 15ABA7
    serial: <superuser required> Chassis: type: 10 v: IdeaPad 3 15ABA7
    serial: <superuser required>
  Mobo: LENOVO model: LNVNB161216 v: NO DPK serial: <superuser required>
    UEFI: LENOVO v: JTCN42WW date: 01/10/2023
Battery:
  ID-1: BAT0 charge: 38.0 Wh (98.2%) condition: 38.7/38.0 Wh (101.9%)
    volts: 8.6 min: 7.7 model: LGC L20L2PF0 type: Li-poly serial: <filter>
    status: full cycles: 84
CPU:
  Info: model: AMD Ryzen 5 5625U with Radeon Graphics bits: 64 type: MT MCP
    arch: Zen 3 gen: 4 level: v3 note: check built: 2021-22
    process: TSMC n7 (7nm) family: 0x19 (25) model-id: 0x50 (80) stepping: 0
    microcode: 0xA50000C
  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: 16 MiB desc: 1x16 MiB
  Speed (MHz): avg: 3543 high: 3544 min/max: 1600/4387 boost: enabled
    scaling: driver: acpi-cpufreq governor: performance cores: 1: 3543 2: 3544
    3: 3544 4: 3544 5: 3543 6: 3544 7: 3544 8: 3543 9: 3543 10: 3543 11: 3543
    12: 3544 bogomips: 55098
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
  Vulnerabilities: <filter>
Graphics:
  Device-1: AMD Barcelo vendor: Lenovo 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: DP-1,HDMI-A-1 bus-ID: 04:00.0 chip-ID: 1002:15e7 class-ID: 0300
    temp: 56.0 C
  Device-2: IMC Networks Integrated Camera driver: uvcvideo type: USB
    rev: 2.0 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 1-3:3 chip-ID: 13d3:56ff
    class-ID: 0e02
  Display: x11 server: X.Org v: 21.1.8 with: Xwayland v: 23.1.2
    compositor: kwin_x11 driver: X: loaded: amdgpu unloaded: modesetting
    alternate: fbdev,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 0xe48d built: 2019
    res: 1920x1080 hz: 60 dpi: 142 gamma: 1.2 size: 344x194mm (13.54x7.64")
    diag: 395mm (15.5") ratio: 16:9 modes: max: 1920x1080 min: 640x480
  API: OpenGL v: 4.6 Mesa 23.1.4 renderer: AMD Radeon Graphics (renoir LLVM
    15.0.7 DRM 3.52 6.4.7-zen1-3-zen) direct-render: Yes
Audio:
  Device-1: AMD Renoir Radeon High Definition Audio vendor: Lenovo
    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: 04:00.1 chip-ID: 1002:1637
    class-ID: 0403
  Device-2: AMD ACP/ACP3X/ACP6x Audio Coprocessor vendor: Lenovo 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: 04:00.5 chip-ID: 1022:15e2 class-ID: 0480
  Device-3: AMD Family 17h/19h HD Audio vendor: Lenovo 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: 04:00.6 chip-ID: 1022:15e3 class-ID: 0403
  API: ALSA v: k6.4.7-zen1-3-zen status: kernel-api tools: N/A
  Server-1: PipeWire v: 0.3.76 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: Realtek RTL8822CE 802.11ac PCIe Wireless Network Adapter
    vendor: Lenovo driver: rtw_8822ce v: N/A modules: rtw88_8822ce pcie: gen: 1
    speed: 2.5 GT/s lanes: 1 port: 2000 bus-ID: 02:00.0 chip-ID: 10ec:c822
    class-ID: 0280
  IF: wlp2s0 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-4:2 chip-ID: 0bda:c123
    class-ID: e001 serial: <filter>
  Report: bt-adapter ID: hci0 rfk-id: 2 state: up address: <filter>
Drives:
  Local Storage: total: 942.7 GiB used: 396.93 GiB (42.1%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Samsung
    model: MZAL4512HBLU-00BL2 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: 7L1QHXC7 temp: 32.9 C scheme: GPT
  ID-2: /dev/sda maj-min: 8:0 vendor: Hitachi model: HTS727550A9E364
    size: 465.76 GiB block-size: physical: 4096 B logical: 512 B type: USB
    rev: 2.1 spd: 480 Mb/s lanes: 1 mode: 2.0 tech: HDD rpm: 7200
    serial: <filter> fw-rev: 0215 scheme: MBR
Partition:
  ID-1: / raw-size: 223.25 GiB size: 223.25 GiB (100.00%)
    used: 76.95 GiB (34.5%) fs: btrfs dev: /dev/nvme0n1p7 maj-min: 259:6
  ID-2: /boot/efi raw-size: 100 MiB size: 96 MiB (96.00%)
    used: 60.7 MiB (63.2%) fs: vfat dev: /dev/nvme0n1p1 maj-min: 259:1
  ID-3: /home raw-size: 223.25 GiB size: 223.25 GiB (100.00%)
    used: 76.95 GiB (34.5%) fs: btrfs dev: /dev/nvme0n1p7 maj-min: 259:6
  ID-4: /var/log raw-size: 223.25 GiB size: 223.25 GiB (100.00%)
    used: 76.95 GiB (34.5%) fs: btrfs dev: /dev/nvme0n1p7 maj-min: 259:6
  ID-5: /var/tmp raw-size: 223.25 GiB size: 223.25 GiB (100.00%)
    used: 76.95 GiB (34.5%) fs: btrfs dev: /dev/nvme0n1p7 maj-min: 259:6
Swap:
  Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default)
  ID-1: swap-1 type: zram size: 13.5 GiB used: 1024 KiB (0.0%) priority: 100
    dev: /dev/zram0
  ID-2: swap-2 type: partition size: 9.51 GiB used: 0 KiB (0.0%)
    priority: -2 dev: /dev/nvme0n1p9 maj-min: 259:7
Sensors:
  System Temperatures: cpu: 69.0 C mobo: N/A gpu: amdgpu temp: 57.0 C
  Fan Speeds (RPM): N/A
Info:
  Processes: 347 Uptime: 4m wakeups: 2 Memory: total: 16 GiB note: est.
  available: 13.5 GiB used: 4.33 GiB (32.0%) Init: systemd v: 254
  default: graphical tool: systemctl Compilers: gcc: 13.2.1 Packages:
  pm: pacman pkgs: 1317 libs: 376 tools: octopi,paru Shell: fish v: 3.6.1
  default: Bash v: 5.1.16 running-in: konsole inxi: 3.3.28
Garuda (2.6.16-1):
  System install date:     2023-02-24
  Last full system update: 2023-08-04
  Is partially upgraded:   Yes
  Relevant software:       snapper NetworkManager mkinitcpio
  Windows dual boot:       Probably (Run as root to verify)
  Failed units:

Chroot, mount, update, install LTS kernel, reboot. That’s what I’d do in Arch. Dunno about Garuda.

3 Likes

Since the system is bootable (only the external HDD cannot be mounted), I think it is enough to just update, install linux-lts, reboot and :crossed_fingers:

garuda-update
sudo pacman -S linux-lts linux-lts-headers
4 Likes

What filesystem is on the external drive?

What is the exact error you get when you attempt to mount it?

4 Likes

external HDD is NTFS.
It has been working before.

NTFS file systems are easily corrupted. You have 2 basic options.

  1. Repair it in Windows or with a Windows install disk.
  2. Apply ntfsfix and hope it works.NTFS - ArchWiki
5 Likes

Please never post error outputs as an image/pic. If possible, always try to post errors as terminal output. Try mounting the drive from the terminal and then post any error output as text.

Images cannot be searched online effectively, so you are always going to recieve less help if you post errors in this manner.

I suggested 4 days ago for you to test numerous alternate kernels. You have not reported on your efforts as yet.

5 Likes

looks too easy
will try it
not convinced

yep, the kernel looks a good idea to focus.
anyway, this means probably that Garuda team does not test enough though before launching updates.
good advises anyway
the tone is a little inpatient only
Merry and Christmas :wink:

I don’t care. Your drive, your data. Merry Christmas.

1 Like

grafik

Realy?

Works fine here.

lsblk -f
NAME        FSTYPE FSVER LABEL        UUID                                 FSAVAIL FSUSE% MOUNTPOINTS
zram0                                                                                     [SWAP]
nvme0n1                                                                                   
├─nvme0n1p1 vfat   FAT32 SYSTEM_DRV   94BA-ECE1                               205M    20% /boot/efi
├─nvme0n1p2                                                                               
├─nvme0n1p3 ntfs         Windows-SSD  A2A8BB95A8BB6707                       79,6G    38% /run/media/sgs/Windows-SSD
├─nvme0n1p4 ntfs         WINRE_DRV    B8F6BC25F6BBE234                                    
├─nvme0n1p5 btrfs        KDE          fc62cc44-07ab-497b-ac89-15704c290993                
├─nvme0n1p6 btrfs        Hyprland     4c17a9ec-6a7a-4114-8443-65c4d6e1d121                
├─nvme0n1p7 btrfs        i3wm         21e02e96-0ed6-4629-9a39-85ffee7a4359   64,3G    78% /var/tmp
│                                                                                         /var/cache
│                                                                                         /var/log
│                                                                                         /srv
│                                                                                         /root
│                                                                                         /home
│                                                                                         /
└─nvme0n1p8 btrfs        Hyprland-SGS b147dd48-f302-484d-80b0-661e7ff40a76   

Same with HDD on my desktop PC.

But Garuda Linux dos not support M$ or ntfs or M$ dual boot.

So, there must be something wrong on your side.

5 Likes

The Garuda team doesn’t do any kernel testing, nor does it hold back or otherwise interfere with any packages from the Arch repos. They become available immediately and are delivered as-is.

It sounds like you do not understand what Garuda Linux is, but just to clarify: if you want packages to be more thoroughly tested before they are made available to you, you should consider switching to a frozen pool distro like Debian stable or Ubuntu.

Your response of “looks too easy/ will try it/ not convinced” is more typing than just typing the actual command into your terminal to try it and be convinced.

sudo ntfsfix -d /dev/sdb1
7 Likes

sudo ntfsfix -d /dev/sdb1
fixed the issue (so unexpectedly! :D)

thanks guys!

no hard feelings pls
i don’t know what Garuda Linux is at all
I just like it

Anyway, just to give you more calm thoughts during the Holidays,
why the ntfs HDD suddenly has errors and cannot be mounted after garuda-update?
Actually two of my ntfs hdds behave the same way.

This is the reason:

NTFS is considerably more fragile when handled from Linux than it is from Windows. Basically anything can break it, although improperly unmounting the drives is probably the most common way to do it.

The NTFS drivers have a history of being inconsistently maintained as well. You get what you get, more or less.

If you are going to continue using NTFS drives on Linux, you had best get used to running ntfsfix. :wink:

7 Likes

The mess as usual.
Thanks again!

Just to give you fair warning, you better back up all your data on any NTFS drive used with Linux. There will eventually come a day when the drive will become so badly corrupted that it will not be able to be corrected by either Linux or Windows. When this happens your only alternative may be to use pricey Windows recovery utilities specifically designed for NTFS drives.

Running NTFS with Linux is like playing Russian Roulette. Eventually you will suffer data loss unless you take steps to reduce your chances of corruption.

I will not use NTFS on any computer that runs strictly Linux as it is just an accident waiting to happen IMO.

3 Likes