Depois um desligamento forçado (no botão) do meu desktop, meu sistema CachyOS só boota no Emergency Mode,
[ OK ] Finished Create Static Device Nodes in /dev.
[ OK ] Reached target Preparation for Local File Systems.
[ OK ] Reached target Local File Systems.
Starting Rule-based Manager for Device Events and Files...
[ OK ] Finished Virtual Console Setup.
[ OK ] Started Rule-based Manager for Device Events and Files.
[ OK ] Started Journal Service.
Starting Create System Files and Directories...
[ OK ] Finished Create System Files and Directories.
[ 1.978393]
[ OK ] Finished Coldplug All udev Devices.
Starting Show Plymouth Boot Screen...
You are in emergency mode. After logging in, type "journalctl -xb" to view system logs, "systemctl reboot" to reboot, or "exit" to continue bootup.
Cannot open access to console, the root account is locked. See sulogin(8) man page for more details.
Press Enter to continue.
Eu pesquisei sobre e vi vários casos parecidos, mas não consegui utilizar as mesmas soluções para o meu, eu bootei um Live USB do CachyOS nessa máquina, copiei o output do “journalctl -xb“ e tentei usar a ferramenta de chroot do próprio CachyOS, que teoricamente, resolveria o meu problema, mas ela dá erro,
[root@CachyOS liveuser]# cachy-chroot
Info: Found 4 block devices
Info: Found partition: Partition: /dev/sda1: FS: exfat UUID: 4E21-0000
Info: Found partition: Partition: /dev/sda2: FS: vfat UUID: 223C-F3F8
Info: Found partition: Partition: /dev/nvme0n1p1: FS: vfat UUID: 463E-2D73
Info: Found partition: Partition: /dev/nvme0n1p2: FS: btrfs UUID: d0218780-0ae3-434e-8532-0e72a37c67a2
✔ Select the block device for the root partition (use arrow keys): · Partition: /dev/nvme0n1p2: FS: btrfs UUID: d0218780-0ae3-434e-8532-0e72a37c67a2
Info: Selected BTRFS partition, mounting and listing subvolumes...
Info: Mounting partition /dev/nvme0n1p2 at /tmp/cachyos-chroot-temp-mount-d0218780-0ae3-434e-8532-0e72a37c67a2-QpwVU2 with options: []
mount: /tmp/cachyos-chroot-temp-mount-d0218780-0ae3-434e-8532-0e72a37c67a2-QpwVU2: fsconfig() failed: File exists.
dmesg(1) may have more information after failed mount system call.
Error: Failed to mount partition /dev/nvme0n1p2 at /tmp/cachyos-chroot-temp-mount-d0218780-0ae3-434e-8532-0e72a37c67a2-QpwVU2
[root@CachyOS liveuser]#
Pelo que eu vi, o problema todo parece ter algo a ver com fstab, algo que eu sou bem leigo.
O sistema é um processador Ryzen 5 5500, GPU RTX 4060, 16GB de RAM, instalado em um SSD NVME de 1TB, só esse sistema no SSD e não tenho outros discos instalados.
Não consegui postar a saída como pública nesse site, eu coloquei nesse link como um quebra galho Dontpad .
“Pastebin’s SMART filters have detected potentially offensive or questionable content in your Paste.
The content you are trying to publish has been deemed potentially offensive or questionable by our filters, because of this you’re receiving this warning.
This Paste can only be published with the visibility set to “Private”.”
sudo btrfs check /dev/nvme0n1p2
Opening filesystem to check…
Checking filesystem on /dev/nvme0n1p2
UUID: d0218780-0ae3-434e-8532-0e72a37c67a2
[1/7] checking root items
[2/7] checking extents
[3/7] checking free space tree
[4/7] checking fs roots
[5/7] checking only csums items (without verifying data)
[6/7] checking root refs
[7/7] checking quota groups skipped (not enabled on this FS)
found 736168554496 bytes used, no error found
total csum bytes: 716918192
total tree bytes: 1890058240
total fs tree bytes: 949157888
total extent tree bytes: 156581888
btree space waste bytes: 242946146
file data blocks allocated: 1639896793088
referenced 792720752640
sudo mount -o recovery /dev/nvme0n1p2 /mnt/btrfs
mount: /mnt/btrfs: fsconfig() failed: btrfs: Unknown parameter 'recovery'.
dmesg(1) may have more information after failed mount system call.
