Can't mount BTRFS partition

My /home partition won’t mount anymore. I reinstalled the system, so I now have /home on the same partition as /, but I can’t access any of the files on my old /home. When I try to mount it, I get this error:

mount: /run/media/zedmost/myhome: mount(2) system call failed: No such file or directory.
dmesg(1) may have more information after failed mount system call.

When I run dmesg, I get this.

Here’s my garuda-inxi:

Kernel: 6.7.0-zen3-1-zen arch: x86_64 bits: 64 compiler: gcc v: 13.2.1
clocksource: hpet available: acpi_pm
parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen
root=UUID=55d59fa2-02fd-42ce-9ed8-f00efdb9061b rw rootflags=subvol=@
quiet loglevel=3 ibt=off
Desktop: KDE Plasma v: 5.27.10 tk: Qt v: 5.15.12 wm: kwin_wayland vt: 1
dm: SDDM Distro: Garuda Linux base: Arch Linux
Type: Desktop System: ASUS product: N/A v: N/A serial: <superuser required>
Mobo: ASUSTeK model: ROG STRIX B550-A GAMING v: Rev X.0x
serial: <superuser required> UEFI: American Megatrends v: 2604
date: 02/25/2022
Info: model: AMD Ryzen 5 5600G 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: 614 high: 2977 min/max: 400/4464 scaling:
driver: amd-pstate-epp governor: powersave cores: 1: 400 2: 400 3: 400
4: 400 5: 400 6: 2977 7: 400 8: 400 9: 400 10: 400 11: 400 12: 400
bogomips: 93420
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
Vulnerabilities: <filter>
Device-1: AMD Cezanne [Radeon Vega Series / Radeon Mobile Series]
vendor: ASUSTeK 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: HDMI-A-1 empty: DP-1
bus-ID: 0a:00.0 chip-ID: 1002:1638 class-ID: 0300 temp: 32.0 C
Display: wayland server: v: with: Xwayland v: 23.2.4
compositor: kwin_wayland driver: X: loaded: amdgpu unloaded: modesetting
alternate: fbdev,vesa dri: radeonsi gpu: amdgpu display-ID: 0
Monitor-1: HDMI-A-1 res: 1920x1080 size: N/A modes: N/A
API: EGL v: 1.5 hw: drv: amd radeonsi platforms: device: 0 drv: radeonsi
device: 1 drv: swrast surfaceless: drv: radeonsi wayland: drv: radeonsi x11:
drv: radeonsi inactive: gbm
API: OpenGL v: 4.6 compat-v: 4.5 vendor: amd mesa v: 23.3.3-arch1.1
glx-v: 1.4 direct-render: yes renderer: AMD Radeon Graphics (radeonsi
renoir LLVM 16.0.6 DRM 3.56 6.7.0-zen3-1-zen) device-ID: 1002:1638
memory: 500 MiB unified: no display-ID: :1.0
API: Vulkan v: 1.3.274 layers: 3 device: 0 type: integrated-gpu name: AMD
Radeon Graphics (RADV RENOIR) driver: mesa radv v: 23.3.3-arch1.1
device-ID: 1002:1638 surfaces: xcb,xlib,wayland device: 1 type: cpu
name: llvmpipe (LLVM 16.0.6 256 bits) driver: mesa llvmpipe
v: 23.3.3-arch1.1 (LLVM 16.0.6) device-ID: 10005:0000
surfaces: xcb,xlib,wayland
Device-1: AMD Renoir Radeon High Definition Audio vendor: ASUSTeK
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: 0a:00.1 chip-ID: 1002:1637
class-ID: 0403
Device-2: AMD Family 17h/19h HD Audio vendor: ASUSTeK
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: 0a:00.6 chip-ID: 1022:15e3
class-ID: 0403
API: ALSA v: k6.7.0-zen3-1-zen status: kernel-api tools: N/A
Server-1: PipeWire v: 1.0.1 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
Device-1: Intel Wi-Fi 6 AX200 driver: iwlwifi v: kernel pcie: gen: 2
speed: 5 GT/s lanes: 1 bus-ID: 06:00.0 chip-ID: 8086:2723 class-ID: 0280
IF: wlp6s0 state: up mac: <filter>
Device-2: Intel Ethernet I225-V vendor: ASUSTeK driver: igc v: kernel
pcie: gen: 2 speed: 5 GT/s lanes: 1 port: N/A bus-ID: 08:00.0
chip-ID: 8086:15f3 class-ID: 0200
IF: enp8s0 state: down mac: <filter>
Device-1: Intel AX200 Bluetooth driver: btusb v: 0.8 type: USB rev: 2.0
speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 1-7.2:8 chip-ID: 8087:0029
class-ID: e001
Report: btmgmt ID: hci0 rfk-id: 3 state: up address: <filter> bt-v: 5.2
lmp-v: 11 status: discoverable: no pairing: no class-ID: 6c0104
Local Storage: total: 3.23 TiB used: 793.61 GiB (24.0%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Kingston model: SKC3000D2048G
size: 1.86 TiB block-size: physical: 512 B logical: 512 B speed: 63.2 Gb/s
lanes: 4 tech: SSD serial: <filter> fw-rev: EIFK31.6 temp: 20.9 C
scheme: GPT
ID-2: /dev/sda maj-min: 8:0 vendor: Seagate model: ST3500630NS
size: 465.76 GiB block-size: physical: 512 B logical: 512 B speed: 3.0 Gb/s
tech: N/A serial: <filter> fw-rev: 3CNR scheme: GPT
ID-3: /dev/sdb maj-min: 8:16 vendor: Seagate model: ST1000DM003-1CH162
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: CC47 scheme: GPT
ID-4: /dev/sdc maj-min: 8:32 vendor: Kingston model: DataTraveler 2.0
size: 3.84 GiB block-size: physical: 512 B logical: 512 B type: USB rev: 2.0
spd: 480 Mb/s lanes: 1 mode: 2.0 tech: N/A serial: <filter> fw-rev: PMAP
SMART Message: Unknown USB bridge. Flash drive/Unsupported enclosure?
ID-1: / raw-size: 100 GiB size: 100 GiB (100.00%) used: 10.09 GiB (10.1%)
fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%)
used: 584 KiB (0.2%) fs: vfat dev: /dev/nvme0n1p1 maj-min: 259:1
ID-3: /home raw-size: 100 GiB size: 100 GiB (100.00%)
used: 10.09 GiB (10.1%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
ID-4: /var/log raw-size: 100 GiB size: 100 GiB (100.00%)
used: 10.09 GiB (10.1%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
ID-5: /var/tmp raw-size: 100 GiB size: 100 GiB (100.00%)
used: 10.09 GiB (10.1%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default) zswap: no
ID-1: swap-1 type: zram size: 14.91 GiB used: 0 KiB (0.0%) priority: 100
comp: zstd avail: lzo,lzo-rle,lz4,lz4hc,842 max-streams: 12 dev: /dev/zram0
System Temperatures: cpu: 36.6 C mobo: N/A gpu: amdgpu temp: 33.0 C
Fan Speeds (rpm): N/A
Processes: 335 Uptime: 4h 39m wakeups: 1 Memory: total: 16 GiB note: est.
available: 14.91 GiB used: 5.29 GiB (35.5%) Init: systemd v: 255
default: graphical tool: systemctl Compilers: gcc: 13.2.1 Packages:
pm: pacman pkgs: 1208 libs: 356 tools: octopi,paru Shell: fish v: 3.7.0
running-in: yakuake inxi: 3.3.31
Garuda (2.6.22-1):
System install date:     2024-01-20
Last full system update: 2024-01-23
Is partially upgraded:   No
Relevant software:       snapper NetworkManager dracut
Windows dual boot:       No/Undetected
Failed units:

I’d like to get my files back, if possible. What’s the best path I can take? This is the first time I’ve ever had to deal with this on Linux, and I’m pretty new to btrfs as well. I tried running btrfs restore with the --dry-run option to see if there were any files I could recover that way, but there was no response. I’m guessing the options I have left are btrfs check and btrfs rescue?

First try is to restore a snapshot from grub.


lsblk -f

Use live ISO chroot, if you install new I think ~/ is empty, try testdisk if you can restore youre files, do not use the new system.

1 Like

I tried a couple of snapshots from when the system was working, but it still wouldn’t mount. I guess my old snapshots are gone now that I re-installed? I thought that it only made snapshots for the system partition, though, and this is a separate partition.

What is your method for mounting it? Post the exact command into the thread.

:point_up_2: Let’s take a look.

1 Like

As @SGS already mentioned, if you need to recover files from an inaccessible partition it is best to never use that drive at all.

Use testdisk to try and recover your files from the inaccessible drive/partition. Copy any recovered files to a completely separate drive, (not a different partition). Continuing to use a drive you need to recover files from is only going to make it harder (or impossible) to recover the files you want.

1 Like

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