Inode has an invalid extent note, fylesystem check failed, can't access tty

Здравствуйте, поставил систему на ssd, примерно с равной периодичностью сталкиваюсь со следующей ошибкой, объясните, пожалуйста, почему может возникать такая проблема?Дело в диске?А может в руках…?

It would be helpful (for others to help you)
if you included some basic system information
as well as the actual error message that you got.

You mention a problem, but do not describe the symptoms very well.

If you want help from people who can’t read russian - to increase your chances of a helpful response - you should post the messages in english
command output will be in english if you prepend the command with:
LANG=C
like:
LANG=C inxi -Fazy

Cheers!

Hello, put the system on an ssd, with about equal frequency I encounter the following error, can you please explain why this problem might be occurring? Is it the drive? Or maybe it’s the hands…?

Hi @us_u ,
This is the translation of the question you posted and the problem is in the drive.
Это перевод вопроса, который вы опубликовали, и проблема заключается в приводе.

I wonder whether you have and encrypted drive and in which partition the error is present. In the former, this requires another solution, they are many in the forum when you search with the words fsck inode. In the later you can solve this booting from an usb stick an run:

Интересно, есть ли у вас зашифрованный диск и в каком разделе возникает ошибка. В первом случае, это требует другого решения, их много на форуме, когда вы ищете со словами fsck inode. В последнем случае вы можете решить эту проблему, загрузившись с usb-флешки и запустив ее:

lsblk

Then, accordingly to the output you can execute, without mounting the drive:
Затем, в соответствии с выводом, вы можете выполнить, не монтируя диск:

fsck /dev/sda3/
``
I do not know which type of drive you are using. I use ext4 in my laptop and the output of the lsblk command is:
Я не знаю, какой тип диска вы используете. Я использую ext4 в своем ноутбуке, и вывод команды lsblk следующий:

``
lsblk
NAME         MAJ:MIN RM   SIZE RO TYPE MOUNTPOINTS
sda            8:0    0 223,6G  0 disk 
├─sda1         8:1    0   500M  0 part /boot/efi
├─sda2         8:2    0   3,9G  0 part [SWAP]
├─sda3         8:3    0  97,7G  0 part /
└─sda4         8:4    0 121,5G  0 part /home
mmcblk0      179:0    0  29,1G  0 disk 
├─mmcblk0p1  179:1    0   300M  0 part 
└─mmcblk0p2  179:2    0  28,8G  0 part 
mmcblk0boot0 179:8    0     4M  1 disk 
mmcblk0boot1 179:16   0     4M  1 disk 

Hope it help, regards

Надеюсь, это поможет, с уважением

DeepL Translate: The world's most accurate translator

Hello, thank you for your reply, am I correct in assuming that the problem is the lack of a mount point in the fstab?
/etc/fstab: static file system information.
Use ‘blkid’ to print the universally unique identifier for a device; this may
be used with UUID= as a more robust way to name devices that works even if
disks are added and removed. See fstab(5).

UUID=d8b06905-d5c5-49ce-8991-3401b4f1f6ca / ext4 defaults,noatime 0 1
tmpfs /tmp tmpfs defaults,noatime,mode=1777 0 0


NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
loop0
7:0 0 227,8M 1 loop /var/lib/snapd/snap/code/111
loop1
7:1 0 227,8M 1 loop /var/lib/snapd/snap/code/110
loop2
7:2 0 115M 1 loop /var/lib/snapd/snap/core/13886
sda 8:0 0 596,2G 0 disk
└─sda1
8:1 0 596,2G 0 part /run/media/ul/a56f8a08-7794-44ef-aaa0-12da76127404
sdb 8:16 0 111,8G 0 disk
└─sdb1
8:17 0 111,8G 0 part /

fsck /dev/sdb1

Reboot and hopefully there will be no futher inode errors.

Regards