Установлен актуальный debain-stable. Некоторое время назад, я неверно оценил то сколько на самом деле освободил пространства на накопителе и запустил обновление. Из за этого потом пришлось чинить всю пакетную систему. Но тогда же, а может и раньше, не уверен, появилась проблема. В любой момент во время работы корневая файловая система переходила в режим ro.
dmesg
[ 22.571453] systemd-journald[307]: File /var/log/journal/443e4f41cf80faeb758a2a9d54d291ea/user-1000.journal corrupted or uncleanly shut down, renaming and replacing.
[ 24.779195] show_signal_msg: 26 callbacks suppressed
[ 24.779200] kdeconnectd[1778]: segfault at 3 ip 00007f5b323a0003 sp 00007ffe5b264b48 error 4 in libqca-qt5.so.2.3.5[7f5b323a0000+82000] likely on CPU 0 (core 0, socket 0)
[ 24.779212] Code: fb 8d 5d b1 b7 b2 04 33 17 93 9e 78 9e fd 1c 17 40 47 9b 93 02 61 40 5a da ec 1d ce ae 49 84 87 00 63 27 c8 ad b8 3b 6b df 73 <a6> 2c f9 22 4b 0d df 8d a9 c7 15 f2 b8 d4 b7 b4 39 bb e3 3d 78 0b
[ 25.384434] kdeconnectd[1937]: segfault at 1 ip 00007f25e3138003 sp 00007ffe9f53b658 error 4 in libqca-qt5.so.2.3.5[7f25e3138000+82000] likely on CPU 0 (core 0, socket 0)
[ 25.384450] Code: fb 8d 5d b1 b7 b2 04 33 17 93 9e 78 9e fd 1c 17 40 47 9b 93 02 61 40 5a da ec 1d ce ae 49 84 87 00 63 27 c8 ad b8 3b 6b df 73 <a6> 2c f9 22 4b 0d df 8d a9 c7 15 f2 b8 d4 b7 b4 39 bb e3 3d 78 0b
[ 58.945891] EXT4-fs error (device sda2): ext4_lookup:1851: inode #3299: comm plymouth: unexpected EA_INODE flag
[ 58.945900] Aborting journal on device sda2-8.
[ 58.949501] EXT4-fs error (device sda2): ext4_journal_check_start:83: comm systemd-journal: Detected aborted journal
[ 58.949503] EXT4-fs error (device sda2): ext4_journal_check_start:83: comm rs:main Q:Reg: Detected aborted journal
[ 58.962802] EXT4-fs (sda2): Remounting filesystem read-only
[ 280.938863] EXT4-fs error (device sda2): __ext4_remount:6422: comm mount: Abort forced by user
mount -no remount,rw /
mount: /: cannot remount /dev/sda2 read-write, is write-protected.
dmesg(1) may have more information after failed mount system call.
fsck -yf /dev/sda2
fsck из util-linux 2.38.1
e2fsck 1.47.0 (5-Feb-2023)
/dev/sda2: recovering journal
Pass 1: Checking inodes, blocks, and sizes
Inodes that were part of a corrupted orphan linked list found. Fix? yes
Inode 392834 was part of the orphaned inode list. FIXED.
Deleted inode 392924 has zero dtime. Fix? yes
Inode 394122 was part of the orphaned inode list. FIXED.
Inode 396034 was part of the orphaned inode list. FIXED.
Inode 397224 was part of the orphaned inode list. FIXED.
Inode 1056080, end of extent exceeds allowed value
(logical block 9, physical block 7930435, len 1)
Clear? yes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
Block bitmap differences: -(6917597--6917899) -(7654133--7654319) -(7876352--7876524) -(7929869--7929871)
Fix? yes
Free blocks count wrong for group #211 (7233, counted=7536).
Fix? yes
Free blocks count wrong for group #233 (4981, counted=5168).
Fix? yes
Free blocks count wrong for group #240 (2617, counted=2790).
Fix? yes
Free blocks count wrong for group #242 (4972, counted=4975).
Fix? yes
Free blocks count wrong (3746409, counted=3740090).
Fix? yes
Inode bitmap differences: -392834 -392924 -394122 -396034 -397224
Fix? yes
Free inodes count wrong for group #48 (777, counted=782).
Fix? yes
Free inodes count wrong (1900337, counted=1899065).
Fix? yes
/dev/sda2: ***** FILE SYSTEM WAS MODIFIED *****
/dev/sda2: ***** REBOOT SYSTEM *****
/dev/sda2: 475495/2374560 files (1.3% non-contiguous), 5786444/9526534 blocks
SSD накопитель недавно менял на новый, переносил данные с помощью dd. SATA кабель переткнул в другой порт. В чём состоит проблема не понимаю. Переустанавливать ОС не хотелось бы.
