![]() ![]() I just guessed from there which were the packages that might be corrupt, and reinstalled them the same way as the linux/linux-headers/etc pacakges. The packages at the bottom are the ones that were installed last. If you have yaourt installed, you can show your installed packages, sorted by installation date with yaourt -Q -date. The last thing I needed to do is check which other packages might need to be reinstalled. Phew! Thank heavens for the live USB stick. After this was done and a reboot, my os was up and running again. It also re-built the initramfs and installed it. With me this was necessary since the same kernel and modules were already partially installed. The -force in there makes sure everything gets reinstalled even if files from the package already exist in the filesystem. I did pacman -S -force linux linux-headers mkinitcpio kmod. All I had to do now was reinstall the kernel and modules. Once I had network, I mounted my the partition with my OS’s root filesystem with mount /dev/sda8 /mnt and chrooted into it with arch-chroot /mnt /bin/bash. Once in the live cd, I setup the network with netctl. ![]() Fortunately I still had my custom persistent arch iso live USB stick. So there was clearly something wrong with my kernel modules, causing them not to load. Systemd: boot-efi.mount: Unit entered failed state. Systemd: local-fs.target: Triggering OnFailure = dependencies. Systemd: local-fs.target: Job local-fs.target/start failed with result 'dependency'. Systemd: Dependency failed for Local File Systems. Systemd: boot-efi.mount: Mount process exited, code =exited status =32 Mount: mount: unknown filesystem type 'vfat' Systemd-modules-load: Failed to lookup alias 'vboxnetflt': Function not implementedĪnd a little further down: systemd: Mounting /boot/efi. Systemd-modules-load: Failed to lookup alias 'vboxnetadp': Function not implemented Systemd-modules-load: Failed to lookup alias 'vboxpci': Function not implemented Systemd-modules-load: Failed to lookup alias 'vboxdrv': Function not implemented Systemd-modules-load: Failed to lookup alias 'loop': Function not implemented Systemd: rvice: Failed with result 'exit-code'. ![]() Systemd: rvice: Unit entered failed state. Systemd: Failed to start Load Kernel Modules. Systemd: rvice: Main process exited, code =exited, status =1 After looking at the logs with journalctl -xe and going almost all the way to the top of the logs, I found these error messages: systemd: Starting Load Kernel Modules. So when I started my laptop again, it dropped me into the emergency mode. And of course the kernel modules weren’t fully installed, and the initramfs wasn’t fully updated either. This isn’t the first time this happened, but unfortunately my computer was in the middle of a kernel upgrade…. ![]() While I was doing this though, I accidentally touched the power cord of my laptop, which then fell out of the wall socket. So as you can guess from the title of this blog post, yesterday I was working on my laptop and decided to install upgrades on my Arch Linux box. The power sockets in the Philippines aren’t great though, and Asus decided to integrate the plug into the transformer/regulator unit for my laptop charger, creating a big heavy plug that is really too heavy for vertical wall sockets. I am still trying to work with Asus to get a new one as it is still under warranty (but sending it in for repair will apparently take 2 months while I already know that a new battery will solve the problem). Since a few weeks my laptop battery is dead. Tags: ArchLinux live kernel upgrade modules Reinstalling the kernel on Arch Linux after a failed upgrade. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |