[Solved] "Cannot stat" messages when upgrading kernel to 3.3.3

Gumper · 2012-04-28 02:24:21

I just updated my system and the kernel was upgraded to 3.3.3-1. When the update runs mkinitcpio I have a bunch of messages as follows:

 -> Parsing hook: [base]
  -> Parsing hook: [udev]
  -> Parsing hook: [autodetect]
  -> Parsing hook: [pata]
  -> Parsing hook: [scsi]
  -> Parsing hook: [sata]
  -> Parsing hook: [filesystems]
  -> Parsing hook: [usbinput]
  -> Parsing hook: [fsck]
cp: cannot stat '/lib/modules/3.3.3-1-ARCH/kernel/drivers/ata/ata_generic.ko': No such file or directory
cp: cannot stat '/lib/modules/3.3.3-1-ARCH/kernel/drivers/ata/pata_acpi.ko': No such file or directory
cp: cannot stat '/lib/modules/3.3.3-1-ARCH/kernel/drivers/ata/pata_amd.ko': No such file or directory
cp: cannot stat '/lib/modules/3.3.3-1-ARCH/kernel/drivers/ata/sata_nv.ko': No such file or directory
cp: cannot stat '/lib/modules/3.3.3-1-ARCH/kernel/drivers/gpu/drm/nouveau/nouveau.ko': No such file or directory
cp: cannot stat '/lib/modules/3.3.3-1-ARCH/kernel/drivers/hid/hid-a4tech.ko': No such file or directory
cp: cannot stat '/lib/modules/3.3.3-1-ARCH/kernel/drivers/hid/hid-apple.ko': No such file or directory
cp: cannot stat '/lib/modules/3.3.3-1-ARCH/kernel/drivers/hid/hid-axff.ko': No such file or directory
cp: cannot stat '/lib/modules/3.3.3-1-ARCH/kernel/drivers/hid/hid-belkin.ko': No such file or directory
cp: cannot stat '/lib/modules/3.3.3-1-ARCH/kernel/drivers/hid/hid-cherry.ko': No such file or directory
cp: cannot stat '/lib/modules/3.3.3-1-ARCH/kernel/drivers/hid/hid-chicony.ko': No such file or directory
cp: cannot stat '/lib/modules/3.3.3-1-ARCH/kernel/drivers/hid/hid-cypress.ko': No such file or directory
cp: cannot stat '/lib/modules/3.3.3-1-ARCH/kernel/drivers/hid/hid-dr.ko': No such file or directory
cp: cannot stat '/lib/modules/3.3.3-1-ARCH/kernel/drivers/hid/hid-elecom.ko': No such file or directory

And then at the bottom of these message the following is displayed:

==> Generating module dependencies
==> Creating gzip initcpio image: /boot/initramfs-linux.img
==> WARNING: errors were encountered during the build. The image may not be complete.
==> Image generation successful

At this point I'm afraid to do a reboot for fear that the system won't boot properly.

Any suggestions on what to do next?

Last edited by Gumper (2012-04-28 21:47:11)

Gcool · 2012-04-28 08:39:37

I'm guessing depmod failed to run for whatever reason when installing the new kernel package. Try running "depmod -a" and afterwards regen your initramfs (mkinitcpio -p linux).

Gumper · 2012-04-28 11:31:43

If I try running "depmod -a" I get a command not found error.

I also see this in my pacman log.

[2012-04-27 22:01] /tmp/alpm_ZkiLot/.INSTALL: line 53: depmod: command not found
[2012-04-27 22:01] >>> Generating initial ramdisk, using mkinitcpio.  Please wait...
[2012-04-27 22:01] ==> Building image from preset: 'default'

Gcool · 2012-04-28 11:38:13

depmod is part of the kmod package. Make sure that's installed (although I can't see how it wouldn't be) and up to date.

Gumper · 2012-04-28 11:40:47

kmod is installed. I just ran a "pacman -S kmod" and then issued the "depmod -a" command.

I'm still getting the command not found error.

Gcool · 2012-04-28 11:45:02

depmod should be present under /sbin/depmod. Check if your path is messed up by any chance (/sbin not included for example).

# echo $PATH

Last edited by Gcool (2012-04-28 11:46:47)

Gumper · 2012-04-28 11:58:49

Here's what I get from echo

/bin:/usr/bin:/usr/local/bin

and if I run "/sbin/depmod -a" I'm getting this:

[root@archlinux gumper]# /sbin/depmod -a
ERROR: could not open directory /lib/modules/3.3.2-1-ARCH: No such file or directory
FATAL: could not search modules: No such file or directory

Gumper · 2012-04-28 12:12:40

I need to step out for a couple of hours. Any other suggestions that I could try when I get back would be appreciated.

Gcool · 2012-04-28 13:29:43

Ok, something seems to be messing with your path there. But you can figure that one out later (check the files in /etc/profile.d). For the issue at hand, try the following:

# export PATH=/usr/local/bin:/usr/bin:/bin:/usr/local/sbin:/usr/sbin:/sbin
# pacman -Syu linux

Gumper · 2012-04-28 18:26:52

I believe that worked.

( 1/17) upgrading linux                                       [#################################] 100%
>>> Updating module dependencies. Please wait ...
>>> Generating initial ramdisk, using mkinitcpio.  Please wait...
==> Building image from preset: 'default'
  -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux.img
==> Starting build: 3.3.3-1-ARCH
  -> Parsing hook: [base]
  -> Parsing hook: [udev]
  -> Parsing hook: [autodetect]
  -> Parsing hook: [pata]
  -> Parsing hook: [scsi]
  -> Parsing hook: [sata]
  -> Parsing hook: [filesystems]
  -> Parsing hook: [usbinput]
  -> Parsing hook: [fsck]
==> Generating module dependencies
==> Creating gzip initcpio image: /boot/initramfs-linux.img
==> Image generation successful
==> Building image from preset: 'fallback'
  -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-fallback.img -S autodetect
==> Starting build: 3.3.3-1-ARCH
  -> Parsing hook: [base]
  -> Parsing hook: [udev]
  -> Parsing hook: [pata]
  -> Parsing hook: [scsi]
  -> Parsing hook: [sata]
  -> Parsing hook: [filesystems]
  -> Parsing hook: [usbinput]
  -> Parsing hook: [fsck]
==> Generating module dependencies
==> Creating gzip initcpio image: /boot/initramfs-linux-fallback.img
==> Image generation successful

Would you say that it's safe to do a reboot now? Also, anything else that I would need to do to correct my path issues?

Thanks for the help! It's greatly appreciated!

Gcool · 2012-04-28 20:47:38

That looks pretty decent to me. You should be safe to reboot.

As for your path issues, have a look at the "PATH=" value in /etc/profile (should be set to what I said in my previous post).

Gumper · 2012-04-28 21:46:48

Rebooted and everything is fine.

I also check /etc/profile and the path is correct there.

Thanks again for the help!

Arch Linux

#1 2012-04-28 02:24:21

[Solved] "Cannot stat" messages when upgrading kernel to 3.3.3

#2 2012-04-28 08:39:37

Re: [Solved] "Cannot stat" messages when upgrading kernel to 3.3.3

#3 2012-04-28 11:31:43

Re: [Solved] "Cannot stat" messages when upgrading kernel to 3.3.3

#4 2012-04-28 11:38:13

Re: [Solved] "Cannot stat" messages when upgrading kernel to 3.3.3

#5 2012-04-28 11:40:47

Re: [Solved] "Cannot stat" messages when upgrading kernel to 3.3.3

#6 2012-04-28 11:45:02

Re: [Solved] "Cannot stat" messages when upgrading kernel to 3.3.3

#7 2012-04-28 11:58:49

Re: [Solved] "Cannot stat" messages when upgrading kernel to 3.3.3

#8 2012-04-28 12:12:40

Re: [Solved] "Cannot stat" messages when upgrading kernel to 3.3.3

#9 2012-04-28 13:29:43

Re: [Solved] "Cannot stat" messages when upgrading kernel to 3.3.3

#10 2012-04-28 18:26:52

Re: [Solved] "Cannot stat" messages when upgrading kernel to 3.3.3

#11 2012-04-28 20:47:38

Re: [Solved] "Cannot stat" messages when upgrading kernel to 3.3.3

#12 2012-04-28 21:46:48

Re: [Solved] "Cannot stat" messages when upgrading kernel to 3.3.3

Board footer