You are not logged in.

#1 2013-06-10 13:25:02

SciePy
Member
Registered: 2013-01-15
Posts: 7

System unable to boot after kernel upgrade - mkinitcpio fails

Hi all,

after upgrading to linux 3.9.5-1 my system is unable to boot. Somehow mkinitcpio is unable to find the modules and fails generating the initrd. Then when booting I get "Unable to find root device". Probably because ext4 is not in the initrd, the UUID is correct.
I already tried reinstalling the kernel several times (from arch-chroot), I also compiled it myself and installed lts kernel, always same problem. Here is the output of mkinitcpio -p linux: http://pastie.org/8030073
The ext4.ko.gz (and the other modules) exists in /usr/lib/modules/3.9.5-1-ARCH/kernel/fs/ext4

I already saw this: https://bbs.archlinux.org/viewtopic.php?id=164888 but it doesn't really seem to be related, after all I didn't upgrade filesystem, just the kernel.

Any ideas?

Offline

#2 2013-06-10 13:30:20

karol
Archivist
Registered: 2009-05-06
Posts: 25,423

Re: System unable to boot after kernel upgrade - mkinitcpio fails

Is your system fully up to date?

Offline

#3 2013-06-10 13:42:55

SciePy
Member
Registered: 2013-01-15
Posts: 7

Re: System unable to boot after kernel upgrade - mkinitcpio fails

karol wrote:

Is your system fully up to date?

Well I'm holding back Xorg packages because I'm using the catalyst ATI driver:

:: Synchronizing package databases...
 core is up to date
 extra is up to date
 community is up to date
 multilib is up to date
:: Starting full system upgrade...
warning: xf86-input-acecad: ignoring package upgrade (1.5.0-5 => 1.5.0-6)
warning: xf86-input-aiptek: ignoring package upgrade (1.4.1-5 => 1.4.1-6)
warning: xf86-input-evdev: ignoring package upgrade (2.7.3-2 => 2.8.0-1)
warning: xf86-input-joystick: ignoring package upgrade (1.6.2-1 => 1.6.2-2)
warning: xf86-input-keyboard: ignoring package upgrade (1.6.2-2 => 1.7.0-1)
warning: xf86-input-mouse: ignoring package upgrade (1.8.1-2 => 1.9.0-1)
warning: xf86-input-synaptics: ignoring package upgrade (1.6.3-1 => 1.7.1-1)
warning: xf86-input-vmmouse: ignoring package upgrade (13.0.0-1 => 13.0.0-2)
warning: xf86-input-void: ignoring package upgrade (1.4.0-4 => 1.4.0-5)
warning: xf86-input-wacom: ignoring package upgrade (0.20.0-1 => 0.20.0-2)
warning: xf86-video-apm: ignoring package upgrade (1.2.5-2 => 1.2.5-3)
warning: xf86-video-ark: ignoring package upgrade (0.7.5-2 => 0.7.5-3)
warning: xf86-video-ast: ignoring package upgrade (0.97.0-2 => 0.97.0-3)
warning: xf86-video-chips: ignoring package upgrade (1.2.5-2 => 1.2.5-3)
warning: xf86-video-cirrus: ignoring package upgrade (1.5.2-1 => 1.5.2-2)
warning: xf86-video-dummy: ignoring package upgrade (0.3.6-2 => 0.3.6-3)
warning: xf86-video-fbdev: ignoring package upgrade (0.4.3-2 => 0.4.3-3)
warning: xf86-video-glint: ignoring package upgrade (1.2.8-2 => 1.2.8-3)
warning: xf86-video-i128: ignoring package upgrade (1.3.6-2 => 1.3.6-3)
warning: xf86-video-i740: ignoring package upgrade (1.3.4-2 => 1.3.4-3)
warning: xf86-video-mach64: ignoring package upgrade (6.9.4-1 => 6.9.4-2)
warning: xf86-video-mga: ignoring package upgrade (1.6.2-2 => 1.6.2-3)
warning: xf86-video-neomagic: ignoring package upgrade (1.2.7-4 => 1.2.7-5)
warning: xf86-video-nv: ignoring package upgrade (2.1.20-2 => 2.1.20-3)
warning: xf86-video-r128: ignoring package upgrade (6.9.1-2 => 6.9.1-3)
warning: xf86-video-rendition: ignoring package upgrade (4.2.5-2 => 4.2.5-3)
warning: xf86-video-s3: ignoring package upgrade (0.6.5-2 => 0.6.5-3)
warning: xf86-video-s3virge: ignoring package upgrade (1.10.6-2 => 1.10.6-3)
warning: xf86-video-savage: ignoring package upgrade (2.3.6-2 => 2.3.6-4)
warning: xf86-video-siliconmotion: ignoring package upgrade (1.7.7-2 => 1.7.7-3)
warning: xf86-video-sis: ignoring package upgrade (0.10.7-3 => 0.10.7-4)
warning: xf86-video-sisusb: ignoring package upgrade (0.9.6-2 => 0.9.6-3)
warning: xf86-video-tdfx: ignoring package upgrade (1.4.5-2 => 1.4.5-3)
warning: xf86-video-trident: ignoring package upgrade (1.3.6-3 => 1.3.6-4)
warning: xf86-video-tseng: ignoring package upgrade (1.2.5-2 => 1.2.5-3)
warning: xf86-video-v4l: ignoring package upgrade (0.2.0-11 => 0.2.0-12)
warning: xf86-video-vesa: ignoring package upgrade (2.3.2-2 => 2.3.2-3)
warning: xf86-video-vmware: ignoring package upgrade (13.0.0-1 => 13.0.1-1)
warning: xf86-video-voodoo: ignoring package upgrade (1.2.5-2 => 1.2.5-3)
warning: xorg-fonts-75dpi: ignoring package upgrade (1.0.1-4 => 1.0.3-1)
warning: xorg-server: ignoring package upgrade (1.13.3-1 => 1.14.1-1)
warning: xorg-xcursorgen: ignoring package upgrade (1.0.5-1 => 1.0.5-2)
warning: xorg-xdpyinfo: ignoring package upgrade (1.3.0-2 => 1.3.1-1)
warning: xorg-xrefresh: ignoring package upgrade (1.0.4-3 => 1.0.5-1)
warning: xorg-xwininfo: ignoring package upgrade (1.1.2-1 => 1.1.3-1)
 there is nothing to do

don't think that should impact mkinitcpio though?

Offline

#4 2013-06-10 13:49:50

karol
Archivist
Registered: 2009-05-06
Posts: 25,423

Re: System unable to boot after kernel upgrade - mkinitcpio fails

Why did you install the whole xorg group? When / if you're done with the mkinitcpio issue, remove the xorg group and install only the applications and drivers that you need.

Unfortunately I have no idea what happened.

Offline

#5 2013-06-10 13:51:37

SciePy
Member
Registered: 2013-01-15
Posts: 7

Re: System unable to boot after kernel upgrade - mkinitcpio fails

karol wrote:

Why did you install the whole xorg group? When / if you're done with the mkinitcpio issue, remove the xorg group and install only the applications and drivers that you need.

Unfortunately I have no idea what happened.

Ok I'll do that, thanks anyway smile

Offline

#6 2013-06-10 14:44:29

Scimmia
Bug Wrangler
Registered: 2012-09-01
Posts: 4,789

Re: System unable to boot after kernel upgrade - mkinitcpio fails

In that chroot, try running "depmod 3.9.5-1-ARCH" then see if you can rebuild the initramfs.

Last edited by Scimmia (2013-06-10 14:50:02)

Offline

#7 2013-06-10 14:50:41

theodoreward
Member
Registered: 2013-04-05
Posts: 20

Re: System unable to boot after kernel upgrade - mkinitcpio fails

I'm getting the same issue today. My system is fully up to date, I'm getting a long list of modules preprended with "ERROR: module not found".

I've tried re-running mkinitcpio specifying the new kernel version "3.9.5-1-ARCH" with no change in output.
These modules only exist in "gz" form, is this normal? As a matter of fact, "find /usr/lib/modules/3.9.5-1-ARCH -name '*ko'" returns no results at all.

Offline

#8 2013-06-10 16:25:35

SciePy
Member
Registered: 2013-01-15
Posts: 7

Re: System unable to boot after kernel upgrade - mkinitcpio fails

Scimmia wrote:

In that chroot, try running "depmod 3.9.5-1-ARCH" then see if you can rebuild the initramfs.

I did that, but the modules are still not found sad

I also tried the mkinitcpio from here: https://projects.archlinux.org/mkinitcpio.git, same problem...

Last edited by SciePy (2013-06-10 16:29:24)

Offline

#9 2013-06-10 16:31:59

Scimmia
Bug Wrangler
Registered: 2012-09-01
Posts: 4,789

Re: System unable to boot after kernel upgrade - mkinitcpio fails

Sanity check, what does "file /boot/vmlinuz-linux" give you?

Offline

#10 2013-06-10 16:34:41

SciePy
Member
Registered: 2013-01-15
Posts: 7

Re: System unable to boot after kernel upgrade - mkinitcpio fails

Scimmia wrote:

Sanity check, what does "file /boot/vmlinuz-linux" give you?

/boot/vmlinuz-linux: x86 boot sector

Machine is 64bit UEFI.

Offline

#11 2013-06-10 16:38:33

theodoreward
Member
Registered: 2013-04-05
Posts: 20

Re: System unable to boot after kernel upgrade - mkinitcpio fails

Here's mine, it's 64 bit, but not UEFI.

~ $ file /boot/*
/boot/initramfs-linux-fallback.img: gzip compressed data, from Unix, last modified: Mon Jun 10 11:32:13 2013
/boot/initramfs-linux.img:          gzip compressed data, from Unix, last modified: Mon Jun 10 11:32:09 2013
/boot/syslinux:                     directory 
/boot/vmlinuz-linux:                x86 boot sector

Last edited by theodoreward (2013-06-10 16:39:07)

Offline

#12 2013-06-10 17:11:23

Scimmia
Bug Wrangler
Registered: 2012-09-01
Posts: 4,789

Re: System unable to boot after kernel upgrade - mkinitcpio fails

ok, apparently they broke "file" for the kernel with the current version, try "file -k /boot/vmlinuz-linux" instead.

I'm just trying to make sure the kernel is 3.9.5-1-ARCH to go with the modules.

Offline

#13 2013-06-10 17:14:27

theodoreward
Member
Registered: 2013-04-05
Posts: 20

Re: System unable to boot after kernel upgrade - mkinitcpio fails

~ $ file -k /boot/vmlinuz-linux
/boot/vmlinuz-linux: x86 boot sector\012- Linux kernel x86 boot executable bzImage, version 3.9.5-1-ARCH (tobias@T-POWA-LX) #1 SMP PREEMPT Sat Jun 8 09:22:, RO-rootFS, swap_dev 0x3, Normal VGA PE32+ executable (EFI application) x86-64 (stripped to external PDB), for MS Windows

Offline

#14 2013-06-10 17:28:34

SciePy
Member
Registered: 2013-01-15
Posts: 7

Re: System unable to boot after kernel upgrade - mkinitcpio fails

> file -k /boot/vmlinuz-linux
/boot/vmlinuz-linux: x86 boot sector\012- Linux kernel x86 boot executable bzImage, version 3.9.5-1-ARCH (tobias@T-POWA-LX) #1 SMP PREEMPT Sat Jun 8 09:22:, RO-rootFS, swap_dev 0x3, Normal VGA PE32+ executable (EFI application) x86-64 (stripped to external PDB), for MS Windows

Last edited by SciePy (2013-06-10 17:50:53)

Offline

#15 2013-06-11 02:58:06

Scimmia
Bug Wrangler
Registered: 2012-09-01
Posts: 4,789

Re: System unable to boot after kernel upgrade - mkinitcpio fails

I wish I knew something else to try, guys. You need someone who knows more about mkinitcpio than I do.

Offline

#16 2013-06-11 04:04:53

camarao
Member
Registered: 2013-01-29
Posts: 26

Re: System unable to boot after kernel upgrade - mkinitcpio fails

Hi,

I had the same problem. Since I am not an IT expert I needed to downgrade the kernel, quite a ride, but eventually I got everything working again. If it could help solving the problem I can repeat all information posted above for my machine and any other information needed.

Last edited by camarao (2013-06-11 04:05:46)

Offline

#17 2013-06-11 05:44:42

theodoreward
Member
Registered: 2013-04-05
Posts: 20

Re: System unable to boot after kernel upgrade - mkinitcpio fails

I ended up creating the initramfs by booting a CD, installing to a USB drive and then copied the image to my /boot. So I can boot into the proper kernel version now

~ $ uname -a
Linux baloney 3.9.5-1-ARCH #1 SMP PREEMPT Sat Jun 8 09:22:45 CEST 2013 x86_64 GNU/Linux

Autodetection says it finds the modules:

~ $ mkinitcpio -M 
==> Modules autodetected
ac
acpi_cpufreq
aesni_intel
ahci
battery
btusb
button
coretemp
crc32c_intel
crc32_pclmul
dcdbas
dell_laptop
dell_wmi
e1000e
ehci_pci
evdev
ext4
firewire_ohci
ghash_clmulni_intel
hid_generic
i2c_i801
i915
intel_agp
intel_ips
intel_powerclamp
iTCO_wdt
iwlwifi
joydev
kvm_intel
lpc_ich
mei
microcode
parport_pc
pcspkr
processor
psmouse
sdhci_pci
sd_mod
serio_raw
shpchp
snd_hda_intel
sr_mod
usbcore
usbhid
uvcvideo
video
wmi
yenta_socket
~ $ 

But I still get the same error when trying to generate the initramfs, so the next kernel update will hose me again.

~ $ mkinitcpio 
==> Starting dry run: 3.9.5-1-ARCH
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [autodetect]
  -> Running build hook: [modconf]
  -> Running build hook: [block]
==> ERROR: module not found: `sr_mod'
==> ERROR: module not found: `sd_mod'
==> ERROR: module not found: `ahci'
==> ERROR: module not found: `ehci_pci'
==> ERROR: module not found: `firewire_ohci'
==> ERROR: module not found: `sdhci_pci'
==> ERROR: module not found: `sd_mod'
  -> Running build hook: [filesystems]
==> ERROR: module not found: `ext4'
  -> Running build hook: [keyboard]
==> ERROR: module not found: `ehci_pci'
==> ERROR: module not found: `hid_generic'
==> ERROR: module not found: `usbhid'
  -> Running build hook: [fsck]
==> WARNING: No modules were added to the image. This is probably not what you want.
==> Dry run complete, use -g IMAGE to generate a real image

Running with verbose output gives

~ $ mkinitcpio -v
==> Starting dry run: 3.9.5-1-ARCH
  -> Running build hook: [base]
    adding file: /bin/busybox
    adding symlink: /usr/lib/libc.so.6 -> libc-2.17.so
    adding file: /usr/lib/libc-2.17.so
    adding symlink: /lib/ld-linux-x86-64.so.2 -> ld-2.17.so
    adding file: /usr/lib/ld-2.17.so
    adding symlink: /usr/bin/[ -> busybox
    adding symlink: /usr/bin/[[ -> busybox
    adding symlink: /usr/bin/ash -> busybox
    adding symlink: /usr/bin/awk -> busybox
    adding symlink: /usr/bin/basename -> busybox
    adding symlink: /usr/bin/cat -> busybox
    adding symlink: /usr/bin/chgrp -> busybox
    adding symlink: /usr/bin/chmod -> busybox
    adding symlink: /usr/bin/chown -> busybox
    adding symlink: /usr/bin/chroot -> busybox
    adding symlink: /usr/bin/clear -> busybox
    adding symlink: /usr/bin/cp -> busybox
    adding symlink: /usr/bin/cttyhack -> busybox
    adding symlink: /usr/bin/cut -> busybox
    adding symlink: /usr/bin/dd -> busybox
    adding symlink: /usr/bin/df -> busybox
    adding symlink: /usr/bin/dirname -> busybox
    adding symlink: /usr/bin/dmesg -> busybox
    adding symlink: /usr/bin/du -> busybox
    adding symlink: /usr/bin/echo -> busybox
    adding symlink: /usr/bin/egrep -> busybox
    adding symlink: /usr/bin/env -> busybox
    adding symlink: /usr/bin/expr -> busybox
    adding symlink: /usr/bin/false -> busybox
    adding symlink: /usr/bin/free -> busybox
    adding symlink: /usr/bin/getopt -> busybox
    adding symlink: /usr/bin/grep -> busybox
    adding symlink: /usr/bin/halt -> busybox
    adding symlink: /usr/bin/head -> busybox
    adding symlink: /usr/bin/hexdump -> busybox
    adding symlink: /usr/bin/ifconfig -> busybox
    adding symlink: /usr/bin/init -> busybox
    adding symlink: /usr/bin/install -> busybox
    adding symlink: /usr/bin/ip -> busybox
    adding symlink: /usr/bin/ipaddr -> busybox
    adding symlink: /usr/bin/iplink -> busybox
    adding symlink: /usr/bin/iproute -> busybox
    adding symlink: /usr/bin/iprule -> busybox
    adding symlink: /usr/bin/iptunnel -> busybox
    adding symlink: /usr/bin/kbd_mode -> busybox
    adding symlink: /usr/bin/kill -> busybox
    adding symlink: /usr/bin/killall -> busybox
    adding symlink: /usr/bin/less -> busybox
    adding symlink: /usr/bin/ln -> busybox
    adding symlink: /usr/bin/loadfont -> busybox
    adding symlink: /usr/bin/loadkmap -> busybox
    adding symlink: /usr/bin/losetup -> busybox
    adding symlink: /usr/bin/ls -> busybox
    adding symlink: /usr/bin/md5sum -> busybox
    adding symlink: /usr/bin/mkdir -> busybox
    adding symlink: /usr/bin/mkfifo -> busybox
    adding symlink: /usr/bin/mknod -> busybox
    adding symlink: /usr/bin/mktemp -> busybox
    adding symlink: /usr/bin/mv -> busybox
    adding symlink: /usr/bin/nc -> busybox
    adding symlink: /usr/bin/netstat -> busybox
    adding symlink: /usr/bin/nslookup -> busybox
    adding symlink: /usr/bin/openvt -> busybox
    adding symlink: /usr/bin/pgrep -> busybox
    adding symlink: /usr/bin/pidof -> busybox
    adding symlink: /usr/bin/ping -> busybox
    adding symlink: /usr/bin/ping6 -> busybox
    adding symlink: /usr/bin/poweroff -> busybox
    adding symlink: /usr/bin/printf -> busybox
    adding symlink: /usr/bin/ps -> busybox
    adding symlink: /usr/bin/pwd -> busybox
    adding symlink: /usr/bin/readlink -> busybox
    adding symlink: /usr/bin/reboot -> busybox
    adding symlink: /usr/bin/rm -> busybox
    adding symlink: /usr/bin/rmdir -> busybox
    adding symlink: /usr/bin/route -> busybox
    adding symlink: /usr/bin/sed -> busybox
    adding symlink: /usr/bin/seq -> busybox
    adding symlink: /usr/bin/setfont -> busybox
    adding symlink: /usr/bin/sh -> busybox
    adding symlink: /usr/bin/sha1sum -> busybox
    adding symlink: /usr/bin/sha256sum -> busybox
    adding symlink: /usr/bin/sha512sum -> busybox
    adding symlink: /usr/bin/sleep -> busybox
    adding symlink: /usr/bin/sort -> busybox
    adding symlink: /usr/bin/stat -> busybox
    adding symlink: /usr/bin/strings -> busybox
    adding symlink: /usr/bin/tac -> busybox
    adding symlink: /usr/bin/tail -> busybox
    adding symlink: /usr/bin/telnet -> busybox
    adding symlink: /usr/bin/test -> busybox
    adding symlink: /usr/bin/tftp -> busybox
    adding symlink: /usr/bin/touch -> busybox
    adding symlink: /usr/bin/true -> busybox
    adding symlink: /usr/bin/umount -> busybox
    adding symlink: /usr/bin/uname -> busybox
    adding symlink: /usr/bin/uniq -> busybox
    adding symlink: /usr/bin/uptime -> busybox
    adding symlink: /usr/bin/vi -> busybox
    adding symlink: /usr/bin/wc -> busybox
    adding symlink: /usr/bin/wget -> busybox
    adding symlink: /usr/bin/yes -> busybox
    adding file: /usr/sbin/kmod
    adding symlink: /usr/lib/libkmod.so.2 -> libkmod.so.2.2.3
    adding file: /usr/lib/libkmod.so.2.2.3
    adding symlink: /usr/lib/libz.so.1 -> libz.so.1.2.8
    adding file: /usr/lib/libz.so.1.2.8
    adding symlink: /usr/bin/depmod -> kmod
    adding symlink: /usr/bin/insmod -> kmod
    adding symlink: /usr/bin/rmmod -> kmod
    adding symlink: /usr/bin/lsmod -> kmod
    adding symlink: /usr/bin/modprobe -> kmod
    adding symlink: /usr/bin/modinfo -> kmod
    adding file: /usr/sbin/blkid
    adding symlink: /usr/lib/libblkid.so.1 -> libblkid.so.1.1.0
    adding file: /usr/lib/libblkid.so.1.1.0
    adding symlink: /usr/lib/libuuid.so.1 -> libuuid.so.1.3.0
    adding file: /usr/lib/libuuid.so.1.3.0
    adding file: /usr/sbin/mount
    adding symlink: /usr/lib/libmount.so.1 -> libmount.so.1.1.0
    adding file: /usr/lib/libmount.so.1.1.0
    adding file: /usr/sbin/switch_root
    adding file: /init_functions
    adding file: /init
    adding file: /usr/lib/modprobe.d/usb-load-ehci-first.conf
  -> Running build hook: [udev]
    adding file: /etc/udev/udev.conf
    adding file: /usr/bin/udevd
    adding symlink: /usr/lib/libacl.so.1 -> libacl.so.1.1.0
    adding file: /usr/lib/libacl.so.1.1.0
    adding symlink: /usr/lib/librt.so.1 -> librt-2.17.so
    adding file: /usr/lib/librt-2.17.so
    adding symlink: /usr/lib/libattr.so.1 -> libattr.so.1.1.0
    adding file: /usr/lib/libattr.so.1.1.0
    adding symlink: /usr/lib/libpthread.so.0 -> libpthread-2.17.so
    adding file: /usr/lib/libpthread-2.17.so
    adding file: /usr/bin/udevadm
    adding file: /usr/lib/udev/rules.d/50-udev-default.rules
    adding file: /usr/lib/udev/rules.d/60-persistent-storage.rules
    adding file: /usr/lib/udev/rules.d/64-btrfs.rules
    adding file: /usr/lib/udev/rules.d/80-drivers.rules
    adding file: /usr/lib/udev/ata_id
    adding file: /usr/lib/udev/scsi_id
    adding file: /hooks/udev
  -> Running build hook: [autodetect]
    caching 48 modules
  -> Running build hook: [modconf]
    adding file: /etc/modprobe.d/modprobe.conf
    adding file: /etc/modprobe.d/nobeep.conf
    adding file: /etc/modprobe.d/vmware-fuse.conf
    overwriting file: /usr/lib/modprobe.d/usb-load-ehci-first.conf
  -> Running build hook: [block]
==> ERROR: module not found: `sr_mod'
==> ERROR: module not found: `sd_mod'
==> ERROR: module not found: `ahci'
==> ERROR: module not found: `ehci_pci'
==> ERROR: module not found: `firewire_ohci'
==> ERROR: module not found: `sdhci_pci'
==> ERROR: module not found: `sd_mod'
  -> Running build hook: [filesystems]
==> ERROR: module not found: `ext4'
  -> Running build hook: [keyboard]
==> ERROR: module not found: `ehci_pci'
==> ERROR: module not found: `hid_generic'
==> ERROR: module not found: `usbhid'
  -> Running build hook: [fsck]
    adding file: /usr/sbin/fsck.ext4
    adding symlink: /usr/lib/libext2fs.so.2 -> libext2fs.so.2.4
    adding file: /usr/lib/libext2fs.so.2.4
    adding symlink: /usr/lib/libcom_err.so.2 -> libcom_err.so.2.1
    adding file: /usr/lib/libcom_err.so.2.1
    adding symlink: /usr/lib/libe2p.so.2 -> libe2p.so.2.3
    adding file: /usr/lib/libe2p.so.2.3
    adding symlink: /usr/bin/fsck.ext2 -> fsck.ext4
    adding symlink: /usr/bin/fsck.ext3 -> fsck.ext4
    adding file: /usr/sbin/fsck
==> WARNING: No modules were added to the image. This is probably not what you want.
==> Dry run complete, use -g IMAGE to generate a real image

Last edited by theodoreward (2013-06-11 06:02:42)

Offline

#18 2013-06-11 13:22:39

alphaniner
Member
From: Ancapistan
Registered: 2010-07-12
Posts: 2,604

Re: System unable to boot after kernel upgrade - mkinitcpio fails

Someone else managed to 'solve' this by reinstalling all packages. Maybe it will help lead someone to a more reasonable solution.

I wonder if stracing or adding -x to the mkinitcpio shebang line would yield anything useful?

Edit: Holy crap, mkinitcpio with -x outputs over 10000 lines just for my default image. yikes

Last edited by alphaniner (2013-06-11 13:27:27)


But whether the Constitution really be one thing, or another, this much is certain - that it has either authorized such a government as we have had, or has been powerless to prevent it. In either case, it is unfit to exist.
-Lysander Spooner

Offline

#19 2013-06-11 14:59:33

falconindy
Developer
From: New York, USA
Registered: 2009-10-22
Posts: 4,092
Website

Re: System unable to boot after kernel upgrade - mkinitcpio fails

If mkinitcpio fails to find modules, then so will modinfo (or it won't, but the path modinfo provides won't exist). What's the output of:

$ modinfo -k 3.9.5-1-ARCH ext4
$ ls -l "$(modinfo -F filename -k 3.9.5-1-ARCH ext4)"

Offline

#20 2013-06-11 15:15:59

SciePy
Member
Registered: 2013-01-15
Posts: 7

Re: System unable to boot after kernel upgrade - mkinitcpio fails

falconindy wrote:

If mkinitcpio fails to find modules, then so will modinfo (or it won't, but the path modinfo provides won't exist). What's the output of:

$ modinfo -k 3.9.5-1-ARCH ext4
$ ls -l "$(modinfo -F filename -k 3.9.5-1-ARCH ext4)"

Hm well you fixed the problem for me...
Apparently modinfo was broken:

> modinfo
command not found: modinfo
> pacman -S kmod
... [reinstalling]
> pacman -S linux
... [reinstalling]
> reboot

Thanks! smile

Offline

#21 2013-06-11 15:17:20

u8sand
Member
Registered: 2012-08-15
Posts: 23

Re: System unable to boot after kernel upgrade - mkinitcpio fails

I had a similar issue which was fixed for me after running

# mkinitcpio -k 3.9.5-1-ARCH
# mkinitcpio -p linux

in a chroot environment (with a live usb)

Offline

#22 2013-06-11 18:13:29

theodoreward
Member
Registered: 2013-04-05
Posts: 20

Re: System unable to boot after kernel upgrade - mkinitcpio fails

Weird, same problem here although pacman says it was already installed, it either wasn't or was not in my path.

~ $ modinfo -k 3.9.5-1-ARCH ext4
bash: modinfo: command not found
~ $ sudo pacman -S kmod
[sudo] password for tward: 
warning: kmod-13-2 is up to date -- reinstalling
resolving dependencies...
looking for inter-conflicts...

Packages (1): kmod-13-2

Total Installed Size:   0.44 MiB
Net Upgrade Size:       0.00 MiB

:: Proceed with installation? [Y/n] 
(1/1) checking keys in keyring                                          [########################################] 100%
(1/1) checking package integrity                                        [########################################] 100%
(1/1) loading package files                                             [########################################] 100%
(1/1) checking for file conflicts                                       [########################################] 100%
(1/1) checking available disk space                                     [########################################] 100%
(1/1) reinstalling kmod     

Everything works great now.

Offline

#23 2013-06-11 18:27:44

falconindy
Developer
From: New York, USA
Registered: 2009-10-22
Posts: 4,092
Website

Re: System unable to boot after kernel upgrade - mkinitcpio fails

I suspect people wrongly decided to delete things when they did the recent filesystem upgrade, or else this makes absolutely no sense.

Offline

#24 2013-06-13 02:29:03

pyvlad
Member
Registered: 2011-12-31
Posts: 2

Re: System unable to boot after kernel upgrade - mkinitcpio fails

falconindy wrote:

I suspect people wrongly decided to delete things when they did the recent filesystem upgrade, or else this makes absolutely no sense.


The filesystem upgrade worked fine for me, and I'm currently running 3.9.4-1-ARCH. The only updates left are the kernel and headers. Upgrading to 3.9.5 breaks it in the way described by users above (modules no longer available).

Last edited by pyvlad (2013-06-13 02:29:38)

Offline

#25 2013-06-13 03:20:15

falconindy
Developer
From: New York, USA
Registered: 2009-10-22
Posts: 4,092
Website

Re: System unable to boot after kernel upgrade - mkinitcpio fails

pyvlad wrote:
falconindy wrote:

I suspect people wrongly decided to delete things when they did the recent filesystem upgrade, or else this makes absolutely no sense.


The filesystem upgrade worked fine for me, and I'm currently running 3.9.4-1-ARCH. The only updates left are the kernel and headers. Upgrading to 3.9.5 breaks it in the way described by users above (modules no longer available).

This sounds a lot like the latter contradicts the former.

Offline

Board footer

Powered by FluxBB