You are not logged in.

#1 2013-04-23 21:07:17

qr
Member
Registered: 2013-04-23
Posts: 7

[solved] unable to boot after "pacman -Syu",

Hey,
so I did an update today and everything was working fine, until I rebooted. There're 2 'failed' messages during the boot:

[FAILED] Failed to start Load Kernel Modules
See 'systemctl status systemd-modules.load.service' for details
[FAILED] Failed to mount /boot/efi
[DEPEND] Dependency failed for Local File Systems

The strange thing is, I can't even use my keyboard to login to the emergency mode. It looks like my keyboard modules (or better any module at all) wasn't loaded. Since I can't use my keyboard I can't give you much information with "systemctl ---failed".

I booted the install system and mounted the root drive to get some information from the log files. This is what I can get from journalctl:

systemd-modules-load.service: main process exited, code=exited, status=17FAILURE
Failed to start Load Kernel Modules.
MESSAGE=Unit systemd-modules-load.service entered failed state.
....

I don't know where I can get more information, I don't really see what the problem is... Is there a log file to see what packages were installed from pacman to get an idea what  caused the problem?

My hardware configuration:
-Intel i5-3470
-Gigabyte H77M-D3H
-Gigabyte Geforce GTX 660

Keyboard is a Aluminium Apple Keyboard.

Would be great if somebody could point me in the right direction. I'm still not used to Arch and it's been a long time since I used linux as my main OS.

Edit:
I found what I updated. Notably the linux, linux-headers,systemd,systemd-sysvcompat and  nvidia-304xx package.

Last edited by qr (2013-04-28 15:50:41)

Offline

#2 2013-04-23 21:20:02

Scimmia
Bug Wrangler
Registered: 2012-09-01
Posts: 5,126

Re: [solved] unable to boot after "pacman -Syu",

/var/log/pacman.log

something in the kernel upgrade probably failed.

Offline

#3 2013-04-23 21:24:16

qr
Member
Registered: 2013-04-23
Posts: 7

Re: [solved] unable to boot after "pacman -Syu",

Yep found the pacman.log. Here is the important part:

[2013-04-23 18:01] [PACMAN] Running 'pacman -Syu'
[2013-04-23 18:01] [PACMAN] synchronizing package lists
[2013-04-23 18:01] [PACMAN] starting full system upgrade
[2013-04-23 18:03] [PACMAN] upgraded glib2 (2.34.3-1 -> 2.36.1-1)
[2013-04-23 18:03] [PACMAN] upgraded atk (2.6.0-1 -> 2.8.0-1)
[2013-04-23 18:03] [PACMAN] upgraded libgcrypt (1.5.1-1 -> 1.5.2-1)
[2013-04-23 18:03] [PACMAN] upgraded libksba (1.2.0-3 -> 1.3.0-1)
[2013-04-23 18:03] [PACMAN] upgraded dirmngr (1.1.0-4 -> 1.1.0-5)
[2013-04-23 18:03] [ALPM-SCRIPTLET] updating font cache... done.
[2013-04-23 18:03] [PACMAN] upgraded fontconfig (2.10.2-1 -> 2.10.92-4)
[2013-04-23 18:03] [PACMAN] upgraded gdk-pixbuf2 (2.26.5-2 -> 2.28.1-1)
[2013-04-23 18:03] [PACMAN] upgraded gnome-icon-theme-symbolic (3.6.2-1 -> 3.8.0.1-1)
[2013-04-23 18:03] [PACMAN] upgraded gnome-icon-theme (3.6.2-1 -> 3.8.0-1)
[2013-04-23 18:03] [PACMAN] upgraded gnupg (2.0.19-6 -> 2.0.19-7)
[2013-04-23 18:03] [PACMAN] upgraded gpgme (1.3.2-1 -> 1.4.0-1)
[2013-04-23 18:03] [PACMAN] upgraded harfbuzz (0.9.15-1 -> 0.9.16-1)
[2013-04-23 18:03] [PACMAN] upgraded libdrm (2.4.43-1 -> 2.4.44-1)
[2013-04-23 18:03] [PACMAN] upgraded libusbx (1.0.14-1 -> 1.0.15-1)
[2013-04-23 18:03] [ALPM-SCRIPTLET] >>> Updating module dependencies. Please wait ...
[2013-04-23 18:03] [ALPM-SCRIPTLET] >>> Generating initial ramdisk, using mkinitcpio.  Please wait...
[2013-04-23 18:03] [ALPM-SCRIPTLET] ==> Building image from preset: 'default'
[2013-04-23 18:03] [ALPM-SCRIPTLET]   -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux.img
[2013-04-23 18:03] [ALPM-SCRIPTLET] ==> Starting build: 3.8.8-1-ARCH
[2013-04-23 18:03] [ALPM-SCRIPTLET]   -> Running build hook: [base]
[2013-04-23 18:03] [ALPM-SCRIPTLET]   -> Running build hook: [udev]
[2013-04-23 18:03] [ALPM-SCRIPTLET]   -> Running build hook: [autodetect]
[2013-04-23 18:03] [ALPM-SCRIPTLET]   -> Running build hook: [modconf]
[2013-04-23 18:03] [ALPM-SCRIPTLET]   -> Running build hook: [block]
[2013-04-23 18:03] [ALPM-SCRIPTLET]   -> Running build hook: [filesystems]
[2013-04-23 18:03] [ALPM-SCRIPTLET]   -> Running build hook: [keyboard]
[2013-04-23 18:03] [ALPM-SCRIPTLET]   -> Running build hook: [fsck]
[2013-04-23 18:03] [ALPM-SCRIPTLET] ==> Generating module dependencies
[2013-04-23 18:03] [ALPM-SCRIPTLET] ==> Creating gzip initcpio image: /boot/initramfs-linux.img
[2013-04-23 18:03] [ALPM-SCRIPTLET] ==> Image generation successful
[2013-04-23 18:03] [ALPM-SCRIPTLET] ==> Building image from preset: 'fallback'
[2013-04-23 18:03] [ALPM-SCRIPTLET]   -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-fallback.img -S autodetect
[2013-04-23 18:03] [ALPM-SCRIPTLET] ==> Starting build: 3.8.8-1-ARCH
[2013-04-23 18:03] [ALPM-SCRIPTLET]   -> Running build hook: [base]
[2013-04-23 18:03] [ALPM-SCRIPTLET]   -> Running build hook: [udev]
[2013-04-23 18:03] [ALPM-SCRIPTLET]   -> Running build hook: [modconf]
[2013-04-23 18:03] [ALPM-SCRIPTLET]   -> Running build hook: [block]
[2013-04-23 18:03] [ALPM-SCRIPTLET]   -> Running build hook: [filesystems]
[2013-04-23 18:03] [ALPM-SCRIPTLET]   -> Running build hook: [keyboard]
[2013-04-23 18:03] [ALPM-SCRIPTLET]   -> Running build hook: [fsck]
[2013-04-23 18:03] [ALPM-SCRIPTLET] ==> Generating module dependencies
[2013-04-23 18:03] [ALPM-SCRIPTLET] ==> Creating gzip initcpio image: /boot/initramfs-linux-fallback.img
[2013-04-23 18:03] [ALPM-SCRIPTLET] ==> Image generation successful
[2013-04-23 18:03] [PACMAN] upgraded linux (3.8.7-1 -> 3.8.8-1)
[2013-04-23 18:03] [PACMAN] upgraded linux-headers (3.8.7-1 -> 3.8.8-1)
[2013-04-23 18:03] [PACMAN] upgraded lirc-utils (1:0.9.0-41 -> 1:0.9.0-42)
[2013-04-23 18:03] [PACMAN] upgraded man-pages (3.50-1 -> 3.51-1)
[2013-04-23 18:03] [PACMAN] upgraded mplayer2 (20130126-1 -> 20130309-1)
[2013-04-23 18:03] [PACMAN] upgraded netcfg (3.0-1 -> 3.0-2)
[2013-04-23 18:03] [PACMAN] upgraded nvidia-304xx (304.88-2 -> 304.88-3)
[2013-04-23 18:03] [PACMAN] upgraded p11-kit (0.13-1 -> 0.18.1-1)
[2013-04-23 18:03] [PACMAN] upgraded pango (1.32.5-1 -> 1.34.0-1)
[2013-04-23 18:03] [PACMAN] upgraded perl (5.16.3-2 -> 5.16.3-3)
[2013-04-23 18:03] [PACMAN] installed lcms2 (2.4-1)
[2013-04-23 18:03] [PACMAN] upgraded poppler (0.22.2-1 -> 0.22.3-2)
[2013-04-23 18:03] [PACMAN] upgraded systemd (201-2 -> 202-2)
[2013-04-23 18:03] [PACMAN] upgraded qtwebkit (2.3.0-1 -> 2.3.1-1)
[2013-04-23 18:03] [PACMAN] upgraded systemd-sysvcompat (201-2 -> 202-2)
[2013-04-23 18:03] [ALPM-SCRIPTLET] >>> texlive: updating the filename database...
[2013-04-23 18:03] [ALPM-SCRIPTLET] mktexlsr: Updating /etc/texmf/ls-R... 
[2013-04-23 18:03] [ALPM-SCRIPTLET] mktexlsr: Updating /usr/share/texmf/ls-R... 
[2013-04-23 18:03] [ALPM-SCRIPTLET] mktexlsr: Updating /usr/share/texmf-dist/ls-R... 
[2013-04-23 18:03] [ALPM-SCRIPTLET] mktexlsr: Updating /var/lib/texmf/ls-R... 
[2013-04-23 18:03] [ALPM-SCRIPTLET] mktexlsr: Done.
[2013-04-23 18:04] [ALPM-SCRIPTLET] recreating all formats... done.
[2013-04-23 18:04] [ALPM-SCRIPTLET]  (logs are under /var/lib/texmf/web2c/<engine>/<formatname>.log)
[2013-04-23 18:04] [PACMAN] upgraded texlive-bin (2012.0-8 -> 2012.0-10)
[2013-04-23 18:04] [ALPM-SCRIPTLET] >>> texlive: saving updmap.cfg as /tmp/tmp.l3n4mI9Y0P...
[2013-04-23 18:04] [ALPM-SCRIPTLET] >>> texlive: regenerating updmap.cfg (custom additions should go
[2013-04-23 18:04] [ALPM-SCRIPTLET]              into /etc/texmf/web2c/updmap-local.cfg
[2013-04-23 18:04] [ALPM-SCRIPTLET] >>> texlive: updating the filename database...
[2013-04-23 18:04] [ALPM-SCRIPTLET] mktexlsr: Updating /etc/texmf/ls-R... 
[2013-04-23 18:04] [ALPM-SCRIPTLET] mktexlsr: Updating /usr/share/texmf/ls-R... 
[2013-04-23 18:04] [ALPM-SCRIPTLET] mktexlsr: Updating /usr/share/texmf-dist/ls-R... 
[2013-04-23 18:04] [ALPM-SCRIPTLET] mktexlsr: Updating /var/lib/texmf/ls-R... 
[2013-04-23 18:04] [ALPM-SCRIPTLET] mktexlsr: Done.
[2013-04-23 18:04] [ALPM-SCRIPTLET] >>> texlive: updating the fontmap files with updmap...
[2013-04-23 18:04] [ALPM-SCRIPTLET]  done.
[2013-04-23 18:04] [ALPM-SCRIPTLET] >>> texlive: recreating all formats...
[2013-04-23 18:04] [ALPM-SCRIPTLET]  done.
[2013-04-23 18:04] [ALPM-SCRIPTLET]  (logs are under /var/lib/texmf/web2c/<engine>/<formatname>.log)
[2013-04-23 18:04] [ALPM-SCRIPTLET] NB: To setup ConTeXt and the lua(la)tex font db,
[2013-04-23 18:04] [ALPM-SCRIPTLET]     see http://wiki.archlinux.org/index.php/TeX_Live
[2013-04-23 18:04] [PACMAN] upgraded texlive-core (2012.28273-1 -> 2012.29661-1)
[2013-04-23 18:04] [ALPM-SCRIPTLET] >>> texlive: updating the filename database...
[2013-04-23 18:04] [ALPM-SCRIPTLET] mktexlsr: Updating /etc/texmf/ls-R... 
[2013-04-23 18:04] [ALPM-SCRIPTLET] mktexlsr: Updating /usr/share/texmf/ls-R... 
[2013-04-23 18:04] [ALPM-SCRIPTLET] mktexlsr: Updating /usr/share/texmf-dist/ls-R... 
[2013-04-23 18:04] [ALPM-SCRIPTLET] mktexlsr: Updating /var/lib/texmf/ls-R... 
[2013-04-23 18:04] [ALPM-SCRIPTLET] mktexlsr: Done.
[2013-04-23 18:04] [PACMAN] upgraded texlive-bibtexextra (2012.28244-1 -> 2012.29663-1)
[2013-04-23 18:04] [ALPM-SCRIPTLET] In order to use the new version, reload all virtualbox modules manually.
[2013-04-23 18:04] [PACMAN] upgraded virtualbox-host-modules (4.2.12-1 -> 4.2.12-2)

Edit: I downgraded the linux and linux-headers packages manually. It's working now. Still, it would be nice if somebody could help me figure out what went wrong so I can upgrade to the new kernel.

Last edited by qr (2013-04-23 21:39:00)

Offline

#4 2013-04-23 21:58:24

ewaller
Administrator
From: Pasadena, CA
Registered: 2009-07-13
Posts: 13,431

Re: [solved] unable to boot after "pacman -Syu",

Was your boot partition mounted at /boot when you updated?  It is not in your /etc/fstab, it won't be.  The effect is that the kernel modules get updated in /lib, the new kernel gets put in the root partition's /boot directory, but the root partition (which was supposed to be grafted to the file system tree at /boot, but wasn't) never gets updated.  When you reboot, you get the stale kernel that does not match the fresh modules.

Last edited by ewaller (2013-04-23 21:58:40)


Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
You assume people are rational and influenced by evidence.  You must not work with the public much. -- Trilby
----
How to Ask Questions the Smart Way

Offline

#5 2013-04-24 00:23:51

andyc
Member
Registered: 2013-04-16
Posts: 2

Re: [solved] unable to boot after "pacman -Syu",

This also happend to me. I downgraded back to 3.8.6, and it is ok. looking at the /boot/efi/EFI/arch dir, it appears that the new kernel files are not copied to the arch dir there. Is this supposed to happen on update, or do the kernel files need to be copied manually before reboot?

Offline

#6 2013-04-24 10:57:21

Vilius
Member
From: Dushanbe, Tajikistan
Registered: 2012-01-05
Posts: 26
Website

Re: [solved] unable to boot after "pacman -Syu",

andyc wrote:

This also happend to me.

And me either. Downgrading the linux package to 3.8.6 didn't help.

Offline

#7 2013-04-24 15:24:37

ewaller
Administrator
From: Pasadena, CA
Registered: 2009-07-13
Posts: 13,431

Re: [solved] unable to boot after "pacman -Syu",

Guys,

When this happens, compare the version numbers from the output of uname -a and of pacman -Qi linux

andyc wrote:

looking at the /boot/efi/EFI/arch dir, it appears that the new kernel files are not copied to the arch dir there. Is this supposed to happen on update, or do the kernel files need to be copied manually before reboot?

None of my machines use EFI, so I cannot speak authoritatively.  The wiki seems to imply one might have to do this.


Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
You assume people are rational and influenced by evidence.  You must not work with the public much. -- Trilby
----
How to Ask Questions the Smart Way

Offline

#8 2013-04-28 15:50:23

qr
Member
Registered: 2013-04-23
Posts: 7

Re: [solved] unable to boot after "pacman -Syu",

Hey!
Sorry, forgot to post about the solution.  Andyc was right, the kernel files weren't copied to the efi system partition, only to /boot, you have to do that yourself (see  here (point 2). Would be great if pacman could warn about it after the upgrade.
Thank you for the fast help.

Offline

#9 2013-04-28 15:54:00

WonderWoofy
Member
From: Los Gatos, CA
Registered: 2012-05-19
Posts: 8,412

Re: [solved] unable to boot after "pacman -Syu",

qr wrote:

Hey!
Sorry, forgot to post about the solution.  Andyc was right, the kernel files weren't copied to the efi system partition, only to /boot, you have to do that yourself (see  here (point 2). Would be great if pacman could warn about it after the upgrade.
Thank you for the fast help.

If you aren't reading the extensive output that occurs when a kernel is updated, I kind of doubt that you would actually read any warnings that would be trown out by pacman ether.

In any case, there is information on the wiki about how to use a systemd.path and systemd.service (oneshot) to have you kernels automagically moved to the correct place on updates (or copied).  I think it is on the UEFI wiki page.  If not there, certainly a link or two away.

Offline

Board footer

Powered by FluxBB