You are not logged in.
I had some issues with my system upon reboot after updating (no network, mouse/external keyboard not working, etc.), and after some digging around, I narrowed the issue down to uname -r saying that the system version is 6.7.0-arch3-1 while my linux and linux-headers packages were 6.7.4-arch1-1 (from pacman -Q). After looking at previous posts with similar issues, most of them seem to revolve around /boot not being mounted, but it appears that /boot is part of my root filesystem, so I don't think it's that (unless it shouldn't be part of the root fs?). I was able to get my system back into a working state by reverting the linux/linux-headers packages back to 6.7.0-arch3-1, but I would like to be able to update my system. I have tried previously to update the system after getting it into a working state, but that just breaks it again.
Other random details I've found:
- When the linux package is 6.7.4-arch3-1, initramfs-linux.img and vmlinuz-linux in /boot are both version 6.7.4
- When the linux package is 6.7.4-arch3-1, /lib/modules/6.7.0-arch3-1 is missing (likely the cause of the non-working trackpad, as modprobe is unable to load the psmouse module)
- pacman -Syu does not produce any errors
Happy to provide any other info/output. System is a Dell XPS 13 7390.
Offline
Please post
$ lsblk -f... and the contents of /etc/fstab
Cheers,
"Before Enlightenment chop wood, carry water. After Enlightenment chop wood, carry water." -- Zen proverb
Offline
Sure,
lsblk -f:
{NAME FSTYPE FSVER LABEL UUID FSAVAIL FSUSE% MOUNTPOINTS
nvme0n1
├─nvme0n1p1
│ vfat FAT32 SYSTEM 00E6-1F3D
├─nvme0n1p2
│
├─nvme0n1p3
│ ntfs Windows 3030E6C130E68CE2
├─nvme0n1p4
│ ntfs Recovery 5A5EE6FF5EE6D335
├─nvme0n1p5
│ ext4 1.0 13efeb07-1491-4a49-8ae5-3c216f4be89a
├─nvme0n1p6
│ swap 1 d2821cc0-6969-45a2-99be-c664dc6df403
└─nvme0n1p7
ext4 1.0 e35513b5-dead-4f02-9717-fe8298fbc076 285.7G 12% /
}/etc/fstab:
{# UUID=e35513b5-dead-4f02-9717-fe8298fbc076
/dev/nvme0n1p7 / ext4 rw,relatime 0 1
portal /run/user/1000/doc fuse.portal rw,nosuid,nodev,user_id=1000,group_id=1000 0 0
}Offline
├─nvme0n1p1
│ vfat FAT32 SYSTEM 00E6-1F3DThe ESP is not being mounted as it is not in /etc/fstab. Please also consider using Persistent_block_device_naming.
Online
I mounted /efi, regenerated fstab, and then tried updating. When booting, I get this error.
[FAILED] Failed to mount /run/user/1000/doc.
[DEPEND] Dependency failed for Local File Systems.
[FAILED] Failed to mount /efi.I assume this is in some way related to the issue with modules I was discussing earlier - e.g. it can't mount these partitions because it can't find the module, I know that I couldn't mount /efi earlier as it was formatted as vfat, for instance.
Offline
Comment out the /efi entry in fstab and reboot if needed to downgrade linux/linux-headers. If you mount the ESP to /efi then you need to use EFI_system_partition#Using_bind_mount or some other method to ensure it is available at /boot when the kernel is updated. After ensuring the ESP is available at /boot upgrade linux/linux-headers.
Online
Comment out the /efi entry in fstab and reboot if needed to downgrade linux/linux-headers. If you mount the ESP to /efi then you need to use EFI_system_partition#Using_bind_mount or some other method to ensure it is available at /boot when the kernel is updated. After ensuring the ESP is available at /boot upgrade linux/linux-headers.
After rebooting, same error as before. However, there was an error in the upgrade, where my efi partition ran out of space while creating the fallback image. However, the builds for initramfs-linux.img and vmlinuz-linux succeeded, and I did verify that these were 6.7.4.
The error:
[2024-02-09T15:39:26-0600] [ALPM-SCRIPTLET] zstd: error 70 : Write error : cannot write block : No space left on device
[2024-02-09T15:39:26-0600] [ALPM-SCRIPTLET] bsdtar: Write error
[2024-02-09T15:39:26-0600] [ALPM-SCRIPTLET] bsdtar: Write error
[2024-02-09T15:39:26-0600] [ALPM-SCRIPTLET] ==> ERROR: Image generation FAILED: 'sort reported an error'Offline