similar to: mkinitrd integration strategy?

I''ve compiled xen without any problems. but now i have to create an initrd file. When i use the command mkinitrd (without any options) the i''ve got some errors: # mkinitrd Root device: /dev/sda3 (mounted on / as reiserfs) Module list: ata_piix mptbase mptscsih qla2300 reiserfs Kernel image: /boot/vmlinuz-2.6.11.12-xen0 Initrd image: /boot/initrd-2.6.11.12-xen0 Shared

While using mkinitrd on debian sarge, it gives the following error: mkinitrd -v -f --with=aacraid --with=sd_mod --with=scsi_mod initrd-2.6.16-xen.img 2.6.16-xen /usr/sbin/mkinitrd: illegal option -- v $Id: mkinitrd,v 1.201 2004/05/16 22:00:48 herbert Exp $ Usage: /usr/sbin/mkinitrd [OPTION]... <-o outfile> [version] Options: -d confdir Specify an alternative configuration directory.

RHEL 4's mkinitrd will fail to recognise that root is on LVM when running on a recent kernel/udev due to changes in naming. This patch detects LVM root for RHEL 4, and uses a dirty hack to frig mkinitrd if required. Fixes RHBZ#580461 --- lib/Sys/VirtV2V/GuestOS/RedHat.pm | 21 +++++++++++++++++++-- 1 files changed, 19 insertions(+), 2 deletions(-) diff --git

From: Pino Toscano <ptoscano at redhat.com> Complementary fix of commit 2d25872df3619a3077006ad0f91c029602db6780. On SLES 11 SP4 with kdump enabled mkinitrd calls mkdumprd which calls mkinitrd, but mkdumprd doesn't have any clue of the root device. Call mkinitrd with rootdev environment variable to tell them all what device to use as root. Tested-By: C?dric Bosdonnat <cbosdonnat at

I need to be able to install CentOS 5.2 on a machine with software RAID (and LVM) setup. I discovered (the hard way!) that there is a bug in the mkinitrd package that causes it to enter an endless loop when there are /dev/mapper/ devices present during the install process. There is a patch to mkinitrd, which I applied and created a new rpm for mkinitrd with this patch applied. I'd like to

Hey all, Just thought I'd give a quick shout out across the mailing list that it looks like Extlinux support got merged into Fedora's mkinitrd, which I believe is in time for Fedora 11. This apparently isn't my full patch series (which if anyone cares can be found at: http://git.kernel.org/?p=boot/warthog9/mkinitrd-syslinux.git;a=summary ) since it's missing the Extlinux

mkinitrd in SLE guests < 12 tries to get the root device by scanning the fstab: this will fail, since v2v already remapped the devices from hd*/sd* to vd* in the guest (including in its fstab). Since we know what is the root device in the appliance, pass it to mkinitrd directly, so it does not have to do guesswork. Thanks to: Cédric Bosdonnat, for reporting the issue, and testing the fix. ---

Hi all, I have a Opteron-machine with the MPT SCSI-controller (Symbios 53c1030). At least in i386-mode, mkinitrd does not seem to build a usable initrd for 2.6.13.x (.3 tested) with this kernel. With 2.6.12.6 it works fine. I have not tested this in x86_64 -mode yet. The symptom is that mptbase and mptscsih load, but mptscsih does not discover any controllers nor drives, and things like

mkinitrd needs to mount files using loop. loop might be a module, so try to load it first. --- lib/Sys/VirtV2V/GuestOS/RedHat.pm | 7 +++++++ 1 files changed, 7 insertions(+), 0 deletions(-) diff --git a/lib/Sys/VirtV2V/GuestOS/RedHat.pm b/lib/Sys/VirtV2V/GuestOS/RedHat.pm index 0e469f5..08027b6 100644 --- a/lib/Sys/VirtV2V/GuestOS/RedHat.pm +++ b/lib/Sys/VirtV2V/GuestOS/RedHat.pm @@ -1114,6

We are happily running xen on a server which uses a SATA driver (thank you all you xenists for producing such a great product). However, we are creating a custom kernel for a domU. When we attempt to run mkinitrd we get: No module ata_piix found for kernel 2.6.11.12-xenUIPSec, aborting. This is the SATA driver. In the past (xen 2.0.5), we simply ran make ARCH=xen menuconfig and told it to

I've just updated one machine from 4.0 to 4.2. The trouble is, the new kernel doesn't want to boot (2.6.9-22.EL, also tested 2.6.9.22.0.2.EL). Usually, manually recreating initrd file solved this problem in the past for me. But not this time. Playing around, I also noticed that if I rebuild initrd for the old kernel, then it also fails to boot. The only way to boot it up is

Hi, The following set of patches is intended mostly to improve ipconfig and nfsmount compatibility with glibc. The context: I'm working on yaird, an alternative to mkinitrd, and currently implementing nfs root file systems. This is based on ipconfig and nfsmount from klibc, with a rewritten version of kinit. Users should be able to build the package with vanilla glibc, since klibc is not

--- appliance/init | 3 +++ 1 files changed, 3 insertions(+), 0 deletions(-) diff --git a/appliance/init b/appliance/init index fe135b4..053ef36 100755 --- a/appliance/init +++ b/appliance/init @@ -39,6 +39,9 @@ fi modprobe dm_mod ||: +# For mkinitrd on RHEL 3 +modprobe ext2 + ifconfig lo 127.0.0.1 ifconfig eth0 10.0.2.10 route add default gw 10.0.2.2 -- 1.6.2.5

Hopefully I should be up to date with all patches; haven't integrated the module-init-tools, and some of Erik's patches didn't make it for different reasons, which hopefully can be resolved soon. If you have sent another patch which I haven't applied, please do let me know. -hpa

Hello all, I posted the whole disk encryption instructions in the forum that has been briefly discussed on the list. I joined the list per Ned's post on the thread. http://www.centos.org/modules/newbb/viewtopic.php?viewmode=flat&topic_id=15923&forum=42 I have a couple of questions about the process of creating a wiki. 1. How does the peer-review process work? 2. Is there a place

Hello I have error virt-v2v: error: unable to rebuild initrd (/boot/initramfs-4.2.3-300.fc23.x86_64.img) because mkinitrd or dracut was not found in the guest My physical machine run on fedora23 Boot on usb made from virt-p2v-livecd-1.32.0.fc23.iso <http://oirase.annexia.org/virt-p2v/virt-p2v-livecd-1.32.0.fc23.iso> Log joined to this mail Do you have this problem ?

CentOS Errata and Bugfix Advisory 2013:0863 Upstream details at : https://rhn.redhat.com/errata/RHBA-2013-0863.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 01cf0a69042bfd510f083b8a37d0a716a32109d97c1363c5370ac8f2a5b8759f libbdevid-python-5.1.19.6-80.el5_9.i386.rpm

CentOS Errata and Bugfix Advisory 2013:1288 Upstream details at : https://rhn.redhat.com/errata/RHBA-2013-1288.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 83dc958013d4095db5c63ba7762e0aebf9897e1247190b7fa2ae370ec525ad97 libbdevid-python-5.1.19.6-81.el5_9.i386.rpm

CentOS Errata and Bugfix Advisory 2014:1224 Upstream details at : https://rhn.redhat.com/errata/RHBA-2014-1224.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 1559bd365056b02f9ce4b36c074d0fab4d6f35fc4f29fa4a1cd2db016a8aaf48 libbdevid-python-5.1.19.6-82.el5.i386.rpm

> -----Original Messages----- > From: "Steven Tardy" <sjt5atra at gmail.com> > Sent Time: 2018-02-26 10:48:48 (Monday) > To: "CentOS mailing list" <centos at centos.org> > Cc: > Subject: Re: [CentOS] How to update modules in iniramfs fastly > > On Sun, Feb 25, 2018 at 8:29 PM wuzhouhui <wuzhouhui14 at mails.ucas.ac.cn> > wrote: