Bug 765715 - kernel-3.1.4-1.fc16.x86_64 does not install initramfs-3.1.4-1.fc16.x86_64.img
Summary: kernel-3.1.4-1.fc16.x86_64 does not install initramfs-3.1.4-1.fc16.x86_64.img
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: rawhide
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-12-09 08:12 UTC by agrigo2001
Modified: 2012-01-23 19:33 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-01-23 19:33:32 UTC
Type: ---


Attachments (Terms of Use)

Description agrigo2001 2011-12-09 08:12:00 UTC
Description of problem:
Upgrading the kernel to 3.1.4 fails to install the initramfs-3.1.4-1.fc16.x86_64.img

Version-Release number of selected component (if applicable): 3.1.4-1.fc16.x86_64

How reproducible:

Steps to Reproduce:
1. $ sudo yum upgrade
2. ls /boot
  
Actual results:
config-3.1.2-1.fc16.x86_64         lost+found
config-3.1.4-1.fc16.x86_64         memtest86+-4.20
efi                                System.map-3.1.2-1.fc16.x86_64
elf-memtest86+-4.20                System.map-3.1.4-1.fc16.x86_64
grub                               vmlinuz-3.1.2-1.fc16.x86_64
grub2                              vmlinuz-3.1.4-1.fc16.x86_64
initramfs-3.1.2-1.fc16.x86_64.img

Expected results:
initramfs-3.1.4-1.fc16.x86_64.img should be included in the list.

Additional info:

The file is listed by
$ rpm -ql kernel-3.1.4 
/boot/System.map-3.1.4-1.fc16.x86_64
/boot/config-3.1.4-1.fc16.x86_64
/boot/initramfs-3.1.4-1.fc16.x86_64.img
/boot/vmlinuz-3.1.4-1.fc16.x86_64
/etc/ld.so.conf.d/kernel-3.1.4-1.fc16.x86_64.conf
/lib/modules/3.1.4-1.fc16.x86_64
...

I then downloaded http://ftp.jaist.ac.jp/pub/Linux/Fedora/updates/16/x86_64/kernel-3.1.4-1.fc16.x86_64.rpm
and ran 
$ rpm2cpio kernel-3.1.4-1.fc16.x86_64.rpm | cpio -idmv

This extracted all the files from the kernel except the initramfs.
$ ls boot
config-3.1.4-1.fc16.x86_64      vmlinuz-3.1.4-1.fc16.x86_64
System.map-3.1.4-1.fc16.x86_64

Is it possible that the initramfs file is not included in the rpm?

Comment 1 Josh Boyer 2011-12-09 12:11:42 UTC
(In reply to comment #0)
> Description of problem:
> Upgrading the kernel to 3.1.4 fails to install the
> initramfs-3.1.4-1.fc16.x86_64.img

Do you have any errors in your yum.log or dracut.log or messages pertaining to this update?

> I then downloaded
> http://ftp.jaist.ac.jp/pub/Linux/Fedora/updates/16/x86_64/kernel-3.1.4-1.fc16.x86_64.rpm
> and ran 
> $ rpm2cpio kernel-3.1.4-1.fc16.x86_64.rpm | cpio -idmv
> 
> This extracted all the files from the kernel except the initramfs.
> $ ls boot
> config-3.1.4-1.fc16.x86_64      vmlinuz-3.1.4-1.fc16.x86_64
> System.map-3.1.4-1.fc16.x86_64
> 
> Is it possible that the initramfs file is not included in the rpm?

It's entirely expected that the initramfs is not in the RPM itself.  The initramfs is created after the kernel RPM is installed in a %posttrans scriptlet that runs the 'new-kernel-pkg' binary, which runs depmod and creates the initramfs.

It's likely something went amiss running this scriptlet an left you without the initramfs.  If you reinstall the kernel via RPM itself, it will probably work this time.

Note: none of this is really a kernel problem, but unless you have an error message that points to either dracut or new-kernel-pkg I don't know which package to move this to.

Comment 2 agrigo2001 2011-12-23 09:07:54 UTC
Do you have any errors in your yum.log or dracut.log or messages pertaining to this update?

No errors in the logs.

> It's entirely expected that the initramfs is not in the RPM itself.  The
> initramfs is created after the kernel RPM is installed in a %posttrans
> scriptlet that runs the 'new-kernel-pkg' binary, which runs depmod and creates
> the initramfs.

Thanks for the clue.

> It's likely something went amiss running this scriptlet an left you without the
> initramfs.  If you reinstall the kernel via RPM itself, it will probably work
> this time.

I reinstalled from the RPM itself, and initially it failed stating that I was running out of disk space in /var/tmp. Now I have increased the size of the /var/tmp partition and can now install from the RPM. I can also install kernel-3.1.5 via yum, so I think that this has solved the problem.

> Note: none of this is really a kernel problem, but unless you have an error
> message that points to either dracut or new-kernel-pkg I don't know which
> package to move this to.

Comment 3 Josh Boyer 2012-01-23 19:33:32 UTC
Closing per comment #2.


Note You need to log in before you can comment on or make changes to this bug.