Arch Linux

anxz

Member

Registered: 2023-09-14

Posts: 25

[solved]/boot became read only file system and cannot upgrade system

Hello I just had an upgrade of system.
And the logs showed the /boot becomes a ready-only file system.
I believe when rebooting the system, it will not work.

Would you help me out?
Thank you in advance.

More information:
1. fstab is checked.

sudo mount /dev/nvme0n1p1 /boot
mount: /boot: WARNING: source write-protected, mounted read-only.

[2024-08-14T16:38:42+0800] [ALPM-SCRIPTLET] install: cannot create regular file '/boot/vmlinuz-linux': Read-only file system
[2024-08-14T16:38:42+0800] [ALPM] running 'dbus-reload.hook'...
[2024-08-14T16:38:43+0800] [ALPM] running 'gdk-pixbuf-query-loaders.hook'...
[2024-08-14T16:38:43+0800] [ALPM] running 'gtk-update-icon-cache.hook'...
[2024-08-14T16:38:43+0800] [ALPM] running 'update-desktop-database.hook'...
[2024-08-14T16:41:55+0800] [PACMAN] Running 'pacman -Syu'
[2024-08-14T16:41:55+0800] [PACMAN] synchronizing package lists
[2024-08-14T16:41:58+0800] [PACMAN] starting full system upgrade
[2024-08-14T16:42:14+0800] [PACMAN] Running 'pacman -S linux-lts linux-lts-headers'
[2024-08-14T16:42:16+0800] [ALPM] running '70-dkms-upgrade.hook'...
[2024-08-14T16:42:16+0800] [ALPM] transaction started
[2024-08-14T16:42:16+0800] [ALPM] reinstalled linux-lts (6.6.45-1)
[2024-08-14T16:42:17+0800] [ALPM] reinstalled linux-lts-headers (6.6.45-1)
[2024-08-14T16:42:17+0800] [ALPM] transaction completed
[2024-08-14T16:42:17+0800] [ALPM] running '30-systemd-update.hook'...
[2024-08-14T16:42:17+0800] [ALPM] running '60-depmod.hook'...
[2024-08-14T16:42:18+0800] [ALPM] running '70-dkms-install.hook'...
[2024-08-14T16:42:18+0800] [ALPM] running '90-mkinitcpio-install.hook'...
[2024-08-14T16:42:18+0800] [ALPM-SCRIPTLET] install: cannot remove '/boot/vmlinuz-linux-lts': Read-only file system
[2024-08-14T16:45:41+0800] [PACMAN] Running 'pacman -Syu'
[2024-08-14T16:45:41+0800] [PACMAN] synchronizing package lists
[2024-08-14T16:46:00+0800] [PACMAN] Running 'pacman -S linux'
[2024-08-14T16:46:02+0800] [ALPM] transaction started
[2024-08-14T16:46:02+0800] [ALPM] reinstalled linux (6.10.4.arch2-1)
[2024-08-14T16:46:02+0800] [ALPM] transaction completed
[2024-08-14T16:46:02+0800] [ALPM] running '30-systemd-update.hook'...
[2024-08-14T16:46:02+0800] [ALPM] running '60-depmod.hook'...
[2024-08-14T16:46:03+0800] [ALPM] running '90-mkinitcpio-install.hook'...
[2024-08-14T16:46:03+0800] [ALPM-SCRIPTLET] install: cannot create regular file '/boot/vmlinuz-linux': Read-only file system
[2024-08-14T16:46:54+0800] [PACMAN] Running 'pacman -Syu'
[2024-08-14T16:46:54+0800] [PACMAN] synchronizing package lists
[2024-08-14T16:47:03+0800] [PACMAN] starting full system upgrade

Last edited by anxz (2024-08-14 13:51:10)

anxz

Member

Registered: 2023-09-14

Posts: 25

Re: [solved]/boot became read only file system and cannot upgrade system

ls shows it's readable.

ls -l /                        
total 24K
lrwxrwxrwx   1 root root    7 Apr  8 02:02 bin -> usr/bin/
drwxr-xr-x   8 root root 4.0K Jan  1  1970 boot/
drwxr-xr-x  22 root root 4.7K Aug 14 15:14 dev/
drwxr-xr-x   1 root root 3.2K Aug 14 16:46 etc/
drwxr-xr-x   1 anix anix    8 Jul 13 04:23 home/
lrwxrwxrwx   1 root root    7 Apr  8 02:02 lib -> usr/lib/
lrwxrwxrwx   1 root root    7 Apr  8 02:02 lib64 -> usr/lib/
drwxr-xr-x   1 root root   20 Aug 14 15:14 mnt/
drwxr-xr-x   1 root root  198 Aug  7 14:46 opt/
dr-xr-xr-x 546 root root    0 Aug 14 08:07 proc/
drwx------   1 root root  138 Aug  7 13:12 root/
drwxr-xr-x  24 root root  660 Aug 14 09:35 run/
lrwxrwxrwx   1 root root    7 Apr  8 02:02 sbin -> usr/bin/
drwxr-xr-x   1 root root   14 Jul 10 14:48 srv/
dr-xr-xr-x  13 root root    0 Aug 14 08:07 sys/
drwxr-xr-x   1 root root   18 Jul 27 01:27 timeshift-btrfs/
drwxrwxrwt  22 root root  860 Aug 14 16:57 tmp/
drwxr-xr-x   1 root root   80 Aug 14 16:46 usr/
drwxr-xr-x   1 root root  116 Aug 13 08:32 var/

anxz

Member

Registered: 2023-09-14

Posts: 25

Re: [solved]/boot became read only file system and cannot upgrade system

dmesg info.. seems something abnormal found.
sda is my usd disk.
I used it and then poped it out.

and nvme0n1p1 is my disk partition.
[30649.609010] FAT-fs (nvme0n1p1): error, fat_free_clusters: deleting FAT entry beyond EOF
and then
[30649.609017] FAT-fs (nvme0n1p1): Filesystem has been set read-only

what shall I do...

[25536.933798] ses 0:0:0:1: Attached Enclosure device
[25539.651214] exFAT-fs (sda1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
[25568.939693] loop1: detected capacity change from 0 to 8388608
[25568.978836] FAT-fs (dm-1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
[25639.464868] sd 0:0:0:0: [sda] Synchronizing SCSI cache
[25639.708308] sd 0:0:0:0: [sda] Synchronize Cache(10) failed: Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
[25639.768994] usb 4-1: USB disconnect, device number 2
[27144.838365] wpscloudsvr[157149]: segfault at 17a ip 00007d8b2a4431a2 sp 00007ffda49d0350 error 6 in libqingbangong.so[c431a2,7d8b2a246000+1aef000] likely on CPU 7 (core 12, socket 0)
[27144.838374] Code: 00 74 27 44 0f b7 35 e5 01 a5 01 0f b7 05 e0 01 a5 01 41 0f b7 f6 66 89 44 24 36 0f b7 d0 bf 01 00 00 00 e8 50 93 8e 01 eb 00 <45> 88 af 7a 01 00 00 48 8b bc 24 90 00 00 00 e8 9a 7a 19 00 84 c0
[28955.654719] perf: interrupt took too long (3931 > 3923), lowering kernel.perf_event_max_sample_rate to 50700

[29023.339990] wpscloudsvr[168277]: segfault at 17a ip 0000700ae64431a2 sp 00007ffebd33e860 error 6 in libqingbangong.so[c431a2,700ae6246000+1aef000] likely on CPU 5 (core 8, socket 0)
[29023.339999] Code: 00 74 27 44 0f b7 35 e5 01 a5 01 0f b7 05 e0 01 a5 01 41 0f b7 f6 66 89 44 24 36 0f b7 d0 bf 01 00 00 00 e8 50 93 8e 01 eb 00 <45> 88 af 7a 01 00 00 48 8b bc 24 90 00 00 00 e8 9a 7a 19 00 84 c0

[30649.609010] FAT-fs (nvme0n1p1): error, fat_free_clusters: deleting FAT entry beyond EOF
[30649.609017] FAT-fs (nvme0n1p1): Filesystem has been set read-only

Last edited by anxz (2024-08-14 09:11:32)

seth

Member

Registered: 2012-09-03

Posts: 59,882

Re: [solved]/boot became read only file system and cannot upgrade system

Are there any device errors in dmesg, does it support https://wiki.archlinux.org/title/SMART ?
nvme's frequently run into this because of controller bugs, https://wiki.archlinux.org/title/Solid_ … leshooting
Did you repartition the device but not the filesystem?
Is it part of a raid?

Regardless of the cause and even if the problem is intermittent, you can most likely not recover from this without at least a reboot what's gonna be a problem because you'll boot an old kernel.
You'll have to fix the system offline, ie. boot an install iso, mount the partitions into place, arch-chroot and re-install the kernel.

---

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

anxz

Member

Registered: 2023-09-14

Posts: 25

Re: [solved]/boot became read only file system and cannot upgrade system

fstab: errors=remont-ro

# /dev/nvme0n1p1 LABEL=SYSTEM_DRV
UUID=3631-C911      	/boot     	vfat      	rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro	0 2

anxz

Member

Registered: 2023-09-14

Posts: 25

Re: [solved]/boot became read only file system and cannot upgrade system

it's just an ordinary laptop.
it is a part.

Are there any device errors in dmesg, does it support https://wiki.archlinux.org/title/SMART ?
nvme's frequently run into this because of controller bugs, https://wiki.archlinux.org/title/Solid_ … leshooting
Did you repartition the device but not the filesystem?
Is it part of a raid?

Regardless of the cause and even if the problem is intermittent, you can most likely not recover from this without at least a reboot what's gonna be a problem because you'll boot an old kernel.
You'll have to fix the system offline, ie. boot an install iso, mount the partitions into place, arch-chroot and re-install the kernel.

anxz

Member

Registered: 2023-09-14

Posts: 25

Re: [solved]/boot became read only file system and cannot upgrade system

hi dear all,
I have to boot with install media.
mount subvols and arch-chroot.
and then manually upgrade the kernels.
lastly, reboot.
Now I am back to the normal system.