[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]
missing /initrd-2.4.20-30.7.legacy.img after kernel upgrade
- From: Ivan Teliatnikov <ivan geosci usyd edu au>
- To: fedora-legacy-list redhat com
- Subject: missing /initrd-2.4.20-30.7.legacy.img after kernel upgrade
- Date: Thu, 11 Mar 2004 23:33:49 +1100 (EST)
I have upgraded a number of RH8 and RH7.3 boxes (all running from IDE
disks) to a new kernel using apt-get without any hustle. So far no
problems. I wanted to start upgrading servers running of SCSI disks,
but I noticed an unexpected feature.
Namely, file /initrd-2.4.20-30.7.legacy.img file was not
created during the upgrade.
The initrd is typically used for temporarily booting the hardware into a
state, that the real kernel vmlinuz can than take over and continue the
booting. For example - you can't read the kernel off the scsi hard disk
until you have a scsi driver loaded in the kernel.
My /etc/grub.conf points to non-existing image. Is this correct?
title Red Hat Linux (2.4.20-30.7.legacy)
root (hd0,0)
kernel /vmlinuz-2.4.20-30.7.legacy ro root=/dev/hda9
initrd /initrd-2.4.20-30.7.legacy.img
I can manually create this image running command
mkinitrd /initrd-2.4.20-30.7.legacy.img 2.4.20-30.7.legacy
Thank you in advance.
--
================================================================================
Ivan Teliatnikov
phone: +61 2 9351 2031
fax: +61 2 9351 0184
mobile_phone: +61 402 173 179
email: ivan es usyd edu au
School of Geosciences
F05 - Edgeworth David Building
The University of Sydney
NSW 2006 Australia
===============================================================================
[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]