开启电脑 30 分钟后，我安装的一些额外应用程序在需要时无法启动。默认安装的应用程序运行正常。
- 无法启动应用程序
- 无法安装软件包。输出显示只读文件系统。
当尝试重新启动电脑时，屏幕变黑并显示类似
systemd-journald: Failed to rotate /var/log/journal/f29f59... system journal: read only file system
systemd-journald: Failed to write entry (22 items, 738 bytes) despite vacuuming, ignoring: Bad message
系统：
Operating System: Kubuntu 21.04
KDE Plasma Version: 5.22.4
KDE Frameworks Version: 5.85.0
Qt Version: 5.15.2
Kernel Version: 5.11.0-31-generic (64-bit)
Graphics Platform: X11
Processors: 4 × Intel® Core™ i5-4430 CPU @ 3.00GHz
Memory: 15,4 GiB of RAM
Graphics Processor: GeForce GT 610/PCIe/SSE2
根分区有 btrfs 文件系统。但是ext4 文件系统也是如此
chris@k2104:~$ lsblk -f
NAME FSTYPE FSVER LABEL UUID FSAVAIL FSUSE% MOUNTPOINT
sda
├─sda1 ntfs New Volume A254DEF854DECDE3
├─sda2 crypto_LUKS 1 d687b472-083a-401b-9405-fa4e336440ca
└─sda3 LVM2_member LVM2 001 2M2yQS-1ckT-Sb7c-m8nm-KKzo-Pbgl-17rYou
└─vg2-vms ext4 1.0 a85ffc5e-484c-4629-925d-3b65f6546e8d
sdb
├─sdb1 btrfs 9e82231c-74c4-4bb2-907b-1f3e0e7713a7 68,8G 31% /
├─sdb2 LVM2_member LVM2 001 kFAIla-HKFN-TKfb-2dTR-9Y3u-4kCR-ZxiJeD
│ └─vg1-home ext4 1.0 d27ee1f7-d35e-4ad8-9722-d36958eb8a1f 78,3G 15% /home
└─sdb3 swap 1 a191a4aa-78bc-464d-ae44-41ee9bb21a36 [SWAP]
sdc
├─sdc1 vfat FAT32 5670-9433 50,4M 47% /boot/efi
├─sdc2
├─sdc3 ntfs 00EE92CBEE92B87C
└─sdc4 ntfs 68E2BA7EE2BA4FD4
sr0
chris@k2104:~$
在网上找到本论坛并在此处运行了这些命令
dmesg |grep systemd
[ 9286.742113] systemd-journald[363]: Failed to write entry (22 items, 749 bytes), ignoring: Read-only file system
[ 9286.742162] systemd-journald[363]: Failed to write entry (22 items, 738 bytes), ignoring: Read-only file system
[ 9286.742211] systemd-journald[363]: Failed to write entry (22 items, 749 bytes), ignoring: Read-only file system
[ 9286.742261] systemd-journald[363]: Failed to write entry (22 items, 738 bytes), ignoring: Read-only file system
[ 9286.742312] systemd-journald[363]: Failed to write entry (22 items, 749 bytes), ignoring: Read-only file system
dmesg |grep systemd
[ 1457.129448] systemd-journald[363]: Failed to write entry (22 items, 749 bytes) despite vacuuming, ignoring: Bad message
[ 1457.129527] systemd-journald[363]: /var/log/journal/f29f59c285a64491bbb7ce03db252823/system.journal: Journal file corrupted, rotating.
[ 1457.129535] systemd-journald[363]: Failed to rotate /var/log/journal/f29f59c285a64491bbb7ce03db252823/system.journal: Read-only file system
[ 1457.129550] systemd-journald[363]: Failed to rotate /var/log/journal/f29f59c285a64491bbb7ce03db252823/user-1000.journal: Read-only file system
[ 1457.129916] systemd-journald[363]: Failed to write entry (22 items, 738 bytes) despite vacuuming, ignoring: Bad message
[ 1457.129995] systemd-journald[363]: /var/log/journal/f29f59c285a64491bbb7ce03db252823/system.journal: Journal file corrupted, rotating.
[ 1457.130003] systemd-journald[363]: Failed to rotate /var/log/journal/f29f59c285a64491bbb7ce03db252823/system.journal: Read-only file system
[ 1457.130009] systemd-journald[363]: Failed to rotate /var/log/journal/f29f59c285a64491bbb7ce03db252823/user-1000.journal: Read-only file system
[ 1457.130395] systemd-journald[363]: Failed to write entry (22 items, 749 bytes) despite vacuuming, ignoring: Bad message
sudo journalctl --verify
FAIL: /var/log/journal/f29f59c285a64491bbb7ce03db252823/system@7f05e06386df48d180db2effce0cfec4-00000000000033ec-0005cb6812012c54.journal (Read-only file system)
Failed to create data file: Read-only file system
File corruption detected at /var/log/journal/f29f59c285a64491bbb7ce03db252823/system.journal:000000 (of 8388608 bytes, 0%).
FAIL: /var/log/journal/f29f59c285a64491bbb7ce03db252823/system.journal (Read-only file system)
Failed to create data file: Read-only file system
File corruption detected at /var/log/journal/f29f59c285a64491bbb7ce03db252823/user-1000@e901582910854e349958c8651e322494-0000000000001e80-0005cb5fa4d330fe.journal:000000 (of 8388608 bytes, 0%).
FAIL: /var/log/journal/f29f59c285a64491bbb7ce03db252823/user-1000@e901582910854e349958c8651e322494-0000000000001e80-0005cb5fa4d330fe.journal (Read-only file system)
Failed to create data file: Read-only file system
File corruption detected at /var/log/journal/f29f59c285a64491bbb7ce03db252823/user-1000.journal:000000 (of 8388608 bytes, 0%).
FAIL: /var/log/journal/f29f59c285a64491bbb7ce03db252823/user-1000.journal (Read-only file system)
chris@k2104:~$
chris@k2104:~$ sudo journalctl --disk-usage
Archived and active journals take up 280.0M in the file system.
chris@k2104:~$
我必须重新启动系统才能解决问题，但大约 30 分钟后，电脑再次出现问题。
我们如何检查 SSD 问题？我们如何知道问题所在？我们如何修复它？提前致谢。
答案1
该脚本将卸载 var 挂载点，然后将其重新挂载为读写。
sudo umount /var
sudo mount -o remount,rw /var
这可能是硬件问题，所以请记住这一点。
答案2
不知道问题是否与 btrfs 有关，问题一直存在，导致我无法正常使用计算机。我已在根分区中重新安装了 kubuntu 21.04，现在使用的是 ext4 文件格式。我尝试安装 kde neon，但它无法识别那里存在的 /efi/boot 分区，并且始终向我显示消息“系统需要带有 fat32 文件系统的 efi/boot 分区，请创建一个”
今天问题已经解决，但如果有人遇到同样的问题并且知道问题的根源，请随时写下任何见解。
命令sudo smartctl -t short -a /dev/sda说我的SSD有SSD_Life_left，004这确实令人担心。
chris@k21:~/Documents/web/logindo$ sudo smartctl -t short -a /dev/sda |grep SSD_Life_Left
231 SSD_Life_Left 0x0000 004 004 000 Old_age Offline - 96
chris@k21:~/Documents/web/logindo$
Gnome 磁盘（gnome-disk-utility）
