similar to: Module error in mkinitrd

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

Hello, my problem is that after installing Xen and configuring menu.lst the new Xen-Kernel doesn''t start. I''m getting a message that the Kernel can''t find the root partition. I''m using the XenLinux 2.6.11 kernel my menu.lst entry looks like this tilte Xen 2.0 / XenLinux 2.6.11 kernel /boot/xen.gz dom0_mem=64000 module

Hi , I am ruuning Senmail with MailScanner on CentOS 4.4. It has updated to kernel 2.6.9-42.0.8.EL from its past kernel 2.6.9-42.0.3.EL. Now the Server can not boot up and gives the below error. mkrootdev: label / not found Mounting root filesystem mount: error 2 mouting ext3 switchroot: mount failed: 22 Kernel panic - not syncing: Attempted to kill init! But I can boot up from its

I''m a newbie. :) I followed the steps written by Jerone Young: http://sourceforge.net/mailarchive/message.php?msg_id=10562241 but i found an error at the 17th step: 17. mkinitrd /boot/initrd-2.6.10-xen0.img 2.6.10-xen0 it said:"No module ata_piix found for kernel 2.6.10-xen0, aborting." so I commented the line of "module /boot/initrd-2.6.10-xen0.img" in the

Posted a similar version of this to the RHEL4 list... I''m having trouble getting CentOS 4.2 installed on a DL140G2 with two SATA drives. I am doing a PXE install, so I do not have a CD-ROM drive in the system and this appears to have the side-effect that both SATA drives are caught by the Uniform Multi-Platform E-IDE driver before ata_piix can catch it. As soon as I hook an IDE CD-ROM

hello, just for a success story : After bad experience on fedeora core 6, I have tested a OpenSuse 10.2beta2. I have installed with success a Windows XP SP2. The hardware: A intel DQ965gf Intel Core 2 Duo 6700 USB DVD reader IDE disk (PATA) Set AHCI mode in BIOS and add all-generic-ide in boot option. The opensuse 10.2beta2 does not well configured the xen kernel, you should do a mkinitrd and

Hello All, I have a machine that crashed. Some part of the motherboard (power supply-related) went south. The motherboard, CPU and memory have been replaced with a much newer architecture. The OS and data are intact on two SATA drives that were RAID1 with LVM. I am going to use 'linux rescue' to recover the LVM backup so I can mount the RAIDs (there were two) in a new CentOS

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.

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

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

Hello, all. I'm afraid I've been dropped into the deep end even though I am an Asterisk novice. I've set up a few tiny, tiny systems in the past and have now been asked to pull together Asterisk, FreePBX, Kamailio, RTPProxy, and Fedora Directory Server into a VoIP service. After googling and reading for most of the last 24 hours, I finally have my head around the components and how

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

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

I have created a custom kernel as I needed to add floating point emulation to the kernel. I used the command below to create my initrd: mkinitrd --preload=ohci-hcd --preload=uhci-hcd --preload=ehci-hcd --preload=ext3 --preload=jbd --preload=scsi_mod --preload=sd_mod --preload=ata_piix --preload=libata /boot/initrd-2.6.9-67.ELmsgnet.img 2.6.9-67.ELmsgnet When I copy my vmlinuz and initrd to

How should mkinitrd integrate with the initramfs that comes with the kernel? At the moment, mkinitrd can simply provide an /init script and take over with the contents of its own cpio file available. /init then loads some modules, plays with mdadm, lvm, cryptsetup, creates some device nodes, mounts a filesystem, switch root, done. Integration is not an issue. That changes when more of the

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. ---

The iface:ide parameter (used in the libguestfs add_drive call) does not work with a libvirt backend. The error usually seen is: 'iface' parameter is not supported by the libvirt attach-method at /usr/share/perl5/vendor_perl/Sys/VirtConvert/GuestfsHandle.pm line 96. This issue was previously mentioned in this thread:

I have a question regarding the building of the unified xen kernel (linux-2.6-xen) and the use of initrd. In the past I built both xen0 and xenU kernels; the xen0 default configurations had SCSI and Fusion MPT support compiled into the kernel. Now, they are built as modules. The problem is that I am unable to boot the xen kernel built that way, even though I am building an initrd. I have

On Tue, Sep 03, 2013 at 11:30:07PM -0600, Mike Latimer wrote: > On Tuesday, September 03, 2013 06:09:26 PM Mike Latimer wrote: > > However, as mentioned in the bug, this parameter is likely no longer > > required. Unless there is a use-case where this setting is required, it > > seems like a good idea to remove it completely (which should work in > > either libvirt or