After kernel upgrade "file not found"

Koven · 2011-08-07 21:30:59

I upgraded to kernel version 3 and I rebooted but I didn't do anything in menu.lst, because I thought symlinks would work, so I rebooted but it didn't work. I tried to boot changing names in grub menu but I'm always getting same error "file not found" and I don't know what else to do. I can see the vmlinuz-linux but I can't see initramfs-linux file in /boot from a Live CD. Can you share your menu.lst to try them please.

brain0 · 2011-08-07 21:35:30

It seems your initramfs wasn't generated at all. Without looking at your pacman.log, I have no idea what happened. Fix it by chrooting to your system and running 'mkinitcpio -p linux'. And to satisfy my curiosity, paste the output of 'ls -lF /boot' here.

Trisatr · 2011-08-07 22:08:30

maybe https://bbs.archlinux.org/viewtopic.php … 60#p972060 ?

edit: oops, sorry, bad reply

Last edited by Trisatr (2011-08-07 22:10:10)

misc · 2011-08-07 22:09:41

I had the symlinks as well, but grub(1) would also fail with FNF, so I manually edited menu.lst (as I'd have done anyway). The relevant lines read:

# (1) Arch Linux
title  Arch Linux
root   (hd0,3)
kernel /boot/vmlinuz-linux root=/dev/disk/by-uuid/bla resume=/dev/sda3 ro vga=775 init=/bin/systemd systemd.unit=multi-user.target quiet
initrd /boot/initramfs-linux.img

NB: The symlinks on my /boot were created with 777 permissions, for whatever reason.

Last edited by misc (2011-08-07 22:14:37)

Koven · 2011-08-07 23:49:11

It's right I had not initramfs-linux file. Now I try to boot but there are errors and it can't boot, I only can get an ramfs shell, so there is some error. Unfortunately I can't send you output errors when I run mkinitcpio -p linux in chroot environment, but these are some "module not found error" and it tells me there is a succesful file creation but when I boot as I told you I can't boot in my arch linux box.

BTW I'm posting from Windows in the same laptop.

Last edited by Koven (2011-08-08 00:00:19)

mwave · 2011-08-08 00:35:39

Hi,
I also got the "file not found" error.

Turned out that while editing the menu.list.pacnew, I accidentally changed the path from

/boot/vmlinuz-linux
to
/vmlinuz-linux

same thing for next line
/boot/initramfs-linux.img
to
/initramfs-linux.img

When I rebooted I got the "file not found" error. I used the "edit" (e) command and changed the paths back to the full (/boot/vmlinuz-linux and /boot/initramfs-linux.img). Invoked boot, and bingo.
......
Not a fun error to be faced with. The pacnew version of the grub.lst file simply had a different path than my installation. I didn't catch it at first.
.....
Hope that helps.

Koven · 2011-08-08 01:09:56

Ok I've tried so many different configurations in grub edit option but nothing works, not because I edited wrong anythingm there was nothing relate to initramfs-linux in /boot folder, now everytime I try to run mkinitcpio -p linux I get a lot of differente errors related with module not found. I'll try a downgrade and reinstall linux kernel 3 version.

I get this error trying to boot with my new kernel.

Root device '/dev/sda5'  doesn't exist. Attemp to create it.
Unable to determine major/minor number of root device '/dev/sda5'

So I don't know what else I can do, because I really can't downgrade, or I don't know how I can downgrade. Chroot works ok but mkinitcpio as I told you gives me a lot of errors.

BR

Last edited by Koven (2011-08-08 01:33:31)

brain0 · 2011-08-08 06:12:17

"Module not found" errors mean something went really wrong during kernel installation. You might give 'fallback' a try, but I don't think it'll help in these cases.

Reinstalling the 'linux' package is worth a try, but I would really like to see some output of the 'mkinitcpio -p linux' command (first few lines could suffice to identify the problem, you could write the first three lines down using a pen, or make a digital photo).

Himari · 2011-08-08 08:15:47

mwave wrote:

Hi,
I also got the "file not found" error.
Turned out that while editing the menu.list.pacnew, I accidentally changed the path from
/boot/vmlinuz-linux
to
/vmlinuz-linux
same thing for next line
/boot/initramfs-linux.img
to
/initramfs-linux.img

When I rebooted I got the "file not found" error. I used the "edit" (e) command and changed the paths back to the full (/boot/vmlinuz-linux and /boot/initramfs-linux.img). Invoked boot, and bingo.
......
Not a fun error to be faced with. The pacnew version of the grub.lst file simply had a different path than my installation. I didn't catch it at first.
.....
Hope that helps.

Thanks a lot! I also come across the same error, this helped me to do the trick

However, I have several partitions on my laptop, and Arch is on extended partition, for some reasons that I don't know, the new menu.lst created by pacman point to /dev/sda3 (which is where the extended partition starts) whilst my Arch (/) is actually on /dev/sda5 and I had to edit manually in order to boot in Arch. Other than that, you will need to edit /vmlinuz-linux to /boot/vmlinuz-linux and /initramfs-linux.img to /boot/initramfs-linux.img

P.S : Sorry for my bad English

karol · 2011-08-08 08:18:35

Himari wrote:

However, I have several partitions on my laptop, and Arch is on extended partition, for some reasons that I don't know, the new menu.lst created by pacman point to /dev/sda3 (which is where the extended partition starts) whilst my Arch (/) is actually on /dev/sda5 and I had to edit manually in order to boot in Arch. Other than that, you will need to edit /vmlinuz-linux to /boot/vmlinuz-linux and /initramfs-linux.img to /boot/initramfs-linux.img
P.S : Sorry for my bad English

/dev/sda3 is just an example, a placeholder.
If you have /boot on a separate partition, /vmlinuz-linux (w/o 'boot') is the correct configuration.

pressh · 2011-08-08 08:52:03

karol wrote:

Himari wrote:
However, I have several partitions on my laptop, and Arch is on extended partition, for some reasons that I don't know, the new menu.lst created by pacman point to /dev/sda3 (which is where the extended partition starts) whilst my Arch (/) is actually on /dev/sda5 and I had to edit manually in order to boot in Arch. Other than that, you will need to edit /vmlinuz-linux to /boot/vmlinuz-linux and /initramfs-linux.img to /boot/initramfs-linux.img
P.S : Sorry for my bad English
/dev/sda3 is just an example, a placeholder.

Yes it is. If you want the package to attempt to create a menu.lst for you, you need to use the install-grub script included in the package:

install-grub /dev/sda

or similar.

Koven · 2011-08-09 01:03:37

Hi this is the output of "mkinitcpio -p linux"

http://imageshack.us/photo/my-images/68 … 0034ss.jpg

http://imageshack.us/photo/my-images/26/photo0035tb.jpg

I guess I'll have to reinstall Arch linux, first time in two years, it's a shame...

BR

Last edited by Koven (2011-08-09 01:04:14)

Griemak · 2011-08-09 01:43:07

Something is wrong with your kernel install. Can you re-install the 'linux' package or install kernel26-lts to get back to a working boot and then re-install the 'linux' package?

Koven · 2011-08-09 13:29:40

There is no way I can enter into my linux box, so I think I will have to reinstall arch.

Inxsible · 2011-08-09 13:30:33

Why not just chroot into it? use the pacman -r option to install whatever packages you need.

Koven · 2011-08-10 18:50:40

I don't know about chroot procedures so I reinstall, I upgraded kernel and everything worked fine. I didn't see anything about chroot procedures in wiki, only downgrade but I can't see /var/spool/pkg folder in chroot environment.

jazz452 · 2011-08-10 18:50:57

I have same problem even a fresh netinstall gave me the same error.Had to install ubuntu for now -.0.

Mr.Elendig · 2011-08-11 18:00:49

Koven wrote:

I don't know about chroot procedures so I reinstall, I upgraded kernel and everything worked fine. I didn't see anything about chroot procedures in wiki, only downgrade but I can't see /var/spool/pkg folder in chroot environment.

https://wiki.archlinux.org/index.php/Change_Root

Not that you actually need to chroot, you can boot a up to date install cd, mount your partions to /mnt and use 'pacman -r /mnt -Syu whatever you need' in most cases.

Last edited by Mr.Elendig (2011-08-11 18:01:12)

skanky · 2011-08-13 20:07:51

mwave wrote:

Hi,
I also got the "file not found" error.
Turned out that while editing the menu.list.pacnew, I accidentally changed the path from
/boot/vmlinuz-linux
to
/vmlinuz-linux
same thing for next line
/boot/initramfs-linux.img
to
/initramfs-linux.img

When I rebooted I got the "file not found" error. I used the "edit" (e) command and changed the paths back to the full (/boot/vmlinuz-linux and /boot/initramfs-linux.img). Invoked boot, and bingo.
......
Not a fun error to be faced with. The pacnew version of the grub.lst file simply had a different path than my installation. I didn't catch it at first.
.....
Hope that helps.

I don't think you introduced that error, my pacnew file had that path in it, too.

tbuitenh · 2011-08-15 10:59:49

I ran into the same problem. I bookmarked this thread earlier, sorry if the problem has been solved in another one and I didn't notice it.

After putting back the kernel and ramdisk from a backup (using different filenames) and downgrading the kernel (mkinitcpio doesn't work, that's why I had to take the ramdisk from a backup), I was able to get back into my system.

I found a mkinitcpio.conf.pacnew, but no significant changes in there. Applied them anyway.

So let's try that again...

sudo pacman -Syu

(3/5) installing linux                             [######################] 100%
>>> Updating module dependencies. Please wait ...
/tmp/alpm_kwQ6VA/.INSTALL: line 10: depmod: command not found
>>> Generating initial ramdisk, using mkinitcpio.  Please wait...
/tmp/alpm_kwQ6VA/.INSTALL: line 12: mkinitcpio: command not found
Optional dependencies for linux
    crda: to set the correct wireless channels of your country

That doesn't look healthy. Perhaps a path problem?

[tb@progress ~]$ su -
Password:
[root@progress ~]# pacman -S linux
warning: linux-3.0.1-1 is up to date -- reinstalling
resolving dependencies...
looking for inter-conflicts...

Targets (1): linux-3.0.1-1

Total Download Size:    0.00 MB
Total Installed Size:   54.55 MB

Proceed with installation? [Y/n] 
(1/1) checking package integrity                   [######################] 100%
(1/1) checking for file conflicts                  [######################] 100%
(1/1) 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.0-ARCH
  -> Parsing hook: [base]
  -> Parsing hook: [udev]
  -> Parsing hook: [autodetect]
  -> Parsing hook: [sata]
  -> Parsing hook: [resume]
  -> Parsing hook: [filesystems]
  -> Parsing hook: [consolefont]
==> Generating module dependencies
==> Creating xz initcpio image: /boot/initramfs-linux.img
6472 blocks
==> 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.0-ARCH
  -> Parsing hook: [base]
  -> Parsing hook: [udev]
  -> Parsing hook: [sata]
  -> Parsing hook: [resume]
  -> Parsing hook: [filesystems]
  -> Parsing hook: [consolefont]
==> Generating module dependencies
==> Creating xz initcpio image: /boot/initramfs-linux-fallback.img
13946 blocks
==> Image generation successful
[root@progress ~]# ls -l /boot
total 12484
drwxr-xr-x 2 root root    4096 Aug 15 12:18 grub
-rw-r--r-- 1 root root 5216044 Aug 15 12:41 initramfs-linux-fallback.img
-rw-r--r-- 1 root root 1460104 Aug 15 12:41 initramfs-linux.img
drwxr-xr-x 2 root root    4096 Jan 26  2011 memtest86+
-rw-r--r-- 1 root root 1453292 Jul 11 19:22 offmylawn.img
-rw-r--r-- 1 root root 2333056 Aug  6 16:22 vmlinuz-linux
-rw-r--r-- 1 root root 2305152 Jul  9 15:00 vmlinuz-offmylawn

That's better. I'll reboot now and see what happens.

tbuitenh · 2011-08-15 11:04:43

It worked. I hope this helps. (note the difference between sudo and su)

Tetsumaki · 2011-09-01 21:11:11

Hello.
Boot with LiveCD : eq: archlinux-2010.05-netinstall-x86_64.iso

For my mdadm raid6-lvm2-luks :

modprobe dm-mod
modprobe md-mod
cryptsetup luksOpen /dev/md1 cryptvol -d /tmp/luks.key
vgscan
vgchange -ay

mount partition with /arch/setup, exit and :

mount -o bind /dev /mnt/dev
mount -t proc none /mnt/proc
mount -t sysfs none /mnt/sys
chroot /mnt /bin/bash
pacman -Sy linux
exit
reboot

Sorry for my english, i'm french.

dhave · 2011-09-22 23:00:04

tbuitenh wrote:

I ran into the same problem. I bookmarked this thread earlier, sorry if the problem has been solved in another one and I didn't notice it.

After putting back the kernel and ramdisk from a backup (using different filenames) and downgrading the kernel (mkinitcpio doesn't work, that's why I had to take the ramdisk from a backup), I was able to get back into my system.

I found a mkinitcpio.conf.pacnew, but no significant changes in there. Applied them anyway.

So let's try that again...

sudo pacman -Syu

(3/5) installing linux                             [######################] 100%
>>> Updating module dependencies. Please wait ...
/tmp/alpm_kwQ6VA/.INSTALL: line 10: depmod: command not found
>>> Generating initial ramdisk, using mkinitcpio.  Please wait...
/tmp/alpm_kwQ6VA/.INSTALL: line 12: mkinitcpio: command not found
Optional dependencies for linux
    crda: to set the correct wireless channels of your country

That doesn't look healthy. Perhaps a path problem?

[tb@progress ~]$ su -
Password:
[root@progress ~]# pacman -S linux
warning: linux-3.0.1-1 is up to date -- reinstalling
resolving dependencies...
looking for inter-conflicts...

Targets (1): linux-3.0.1-1

Total Download Size:    0.00 MB
Total Installed Size:   54.55 MB

Proceed with installation? [Y/n] 
(1/1) checking package integrity                   [######################] 100%
(1/1) checking for file conflicts                  [######################] 100%
(1/1) 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.0-ARCH
  -> Parsing hook: [base]
  -> Parsing hook: [udev]
  -> Parsing hook: [autodetect]
  -> Parsing hook: [sata]
  -> Parsing hook: [resume]
  -> Parsing hook: [filesystems]
  -> Parsing hook: [consolefont]
==> Generating module dependencies
==> Creating xz initcpio image: /boot/initramfs-linux.img
6472 blocks
==> 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.0-ARCH
  -> Parsing hook: [base]
  -> Parsing hook: [udev]
  -> Parsing hook: [sata]
  -> Parsing hook: [resume]
  -> Parsing hook: [filesystems]
  -> Parsing hook: [consolefont]
==> Generating module dependencies
==> Creating xz initcpio image: /boot/initramfs-linux-fallback.img
13946 blocks
==> Image generation successful
[root@progress ~]# ls -l /boot
total 12484
drwxr-xr-x 2 root root    4096 Aug 15 12:18 grub
-rw-r--r-- 1 root root 5216044 Aug 15 12:41 initramfs-linux-fallback.img
-rw-r--r-- 1 root root 1460104 Aug 15 12:41 initramfs-linux.img
drwxr-xr-x 2 root root    4096 Jan 26  2011 memtest86+
-rw-r--r-- 1 root root 1453292 Jul 11 19:22 offmylawn.img
-rw-r--r-- 1 root root 2333056 Aug  6 16:22 vmlinuz-linux
-rw-r--r-- 1 root root 2305152 Jul  9 15:00 vmlinuz-offmylawn

That's better. I'll reboot now and see what happens.

@tbuitenh: I encountered this same situation today when I tried to update linux-ck-corei7 from 3.0.4-1 to 3.0.4-2. Like you, running pacman after "su -" (instead of "su") permitted me to complete the update.

I figure this has to do with default login path, right? What exactly is going on here, and how can I fix it? I don't normally run pacman this way.

Last edited by dhave (2011-09-22 23:07:53)

jseg44 · 2011-10-09 16:45:07

I had exactly the same problem, I just upgraded
pacman -Syu
about 6 hours ago from the ftp.archlinux.org/$repo/os/i686 server,
and could not reboot because of a non-existent initramfs-linux.img file.
Managed to fix it by following brain0's advice of chrooting and running mkinicpio -p linux
however I had to follow the chroot instructions given here

https://bugs.archlinux.org/task/26344?project=6

as the instructions given here

https://wiki.archlinux.org/index.php/Change_Root

cause mkinitcpio to segfault and fail.

jseg44 · 2011-10-09 17:05:35

and here's an excerpt from the pacman.log
which might explain why the initramfs-linux
wasn't there:

[2011-10-09 19:32] upgraded mkinitcpio-busybox (1.16.1-3 -> 1.18.5-1)
[2011-10-09 19:32] warning: /etc/mkinitcpio.conf installed as /etc/mkinitcpio.conf.pacnew
[2011-10-09 19:32] upgraded mkinitcpio (0.6.4-1 -> 0.7.3-1)
[2011-10-09 19:33] >>> Updating module dependencies. Please wait ...
[2011-10-09 19:33] >>> Generating initial ramdisk, using mkinitcpio. Please wait...
[2011-10-09 19:33] /sbin/mkinitcpio: line 160: 11483 Segmentation fault mountpoint -q /proc
[2011-10-09 19:33] ==> ERROR: /proc must be mounted!
[2011-10-09 19:33] installed linux (3.0.6-2)
[2011-10-09 19:33] installed linux-headers (3.0.6-2)
[2011-10-09 19:33] >>>
[2011-10-09 19:33] >>> If you use the LILO bootloader, you should run 'lilo' before rebooting.
[2011-10-09 19:33] >>>
[2011-10-09 19:33] >>> Updating module dependencies. Please wait ...
[2011-10-09 19:33] >>> MKINITCPIO SETUP
[2011-10-09 19:33] >>> ----------------
[2011-10-09 19:33] >>> If you use LVM2, Encrypted root or software RAID,
[2011-10-09 19:33] >>> Ensure you enable support in /etc/mkinitcpio.conf .
[2011-10-09 19:33] >>> More information about mkinitcpio setup can be found here:
[2011-10-09 19:33] >>> http://wiki.archlinux.org/index.php/Mkinitcpio
[2011-10-09 19:33]
[2011-10-09 19:33] >>> Generating initial ramdisk, using mkinitcpio. Please wait...
[2011-10-09 19:33] /sbin/mkinitcpio: line 160: 11531 Segmentation fault mountpoint -q /proc
[2011-10-09 19:33] ==> ERROR: /proc must be mounted!
[2011-10-09 19:33] upgraded kernel26-lts (2.6.27.46-1 -> 2.6.32.46-1)
[2011-10-09 19:33] upgraded kernel26-lts-headers (2.6.27.46-1 -> 2.6.32.46-1)
[2011-10-09 19:33] upgraded krb5 (1.9.1-3 -> 1.9.1-4)
[2011-10-09 19:33] upgraded less (436-1 -> 444-1)
[2011-10-09 19:33] installed elfutils (0.152-1)
[2011-10-09 19:33] upgraded libpcap (1.1.1-1 -> 1.1.1-2)
[2011-10-09 19:33] upgraded librpcsecgss (0.19-3 -> 0.19-5)

Arch Linux

#1 2011-08-07 21:30:59

After kernel upgrade "file not found"

#2 2011-08-07 21:35:30

Re: After kernel upgrade "file not found"

#3 2011-08-07 22:08:30

Re: After kernel upgrade "file not found"

#4 2011-08-07 22:09:41

Re: After kernel upgrade "file not found"

#5 2011-08-07 23:49:11

Re: After kernel upgrade "file not found"

#6 2011-08-08 00:35:39

Re: After kernel upgrade "file not found"

#7 2011-08-08 01:09:56

Re: After kernel upgrade "file not found"

#8 2011-08-08 06:12:17

Re: After kernel upgrade "file not found"

#9 2011-08-08 08:15:47

Re: After kernel upgrade "file not found"

#10 2011-08-08 08:18:35

Re: After kernel upgrade "file not found"

#11 2011-08-08 08:52:03

Re: After kernel upgrade "file not found"

#12 2011-08-09 01:03:37

Re: After kernel upgrade "file not found"

#13 2011-08-09 01:43:07

Re: After kernel upgrade "file not found"

#14 2011-08-09 13:29:40

Re: After kernel upgrade "file not found"

#15 2011-08-09 13:30:33

Re: After kernel upgrade "file not found"

#16 2011-08-10 18:50:40

Re: After kernel upgrade "file not found"

#17 2011-08-10 18:50:57

Re: After kernel upgrade "file not found"

#18 2011-08-11 18:00:49

Re: After kernel upgrade "file not found"

#19 2011-08-13 20:07:51

Re: After kernel upgrade "file not found"

#20 2011-08-15 10:59:49

Re: After kernel upgrade "file not found"

#21 2011-08-15 11:04:43

Re: After kernel upgrade "file not found"

#22 2011-09-01 21:11:11

Re: After kernel upgrade "file not found"

#23 2011-09-22 23:00:04

Re: After kernel upgrade "file not found"

#24 2011-10-09 16:45:07

Re: After kernel upgrade "file not found"

#25 2011-10-09 17:05:35

Re: After kernel upgrade "file not found"

Board footer