similar to: mkinitrd and xen w/lvm

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

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

Hi All, I am trying to create an initrd for a VM which uses LVM as its root partition. I am running the mkinitrd command a dom0 that also uses LVM - dom0''s volume group is "XenHost" while the VM''s volume group is "VG_VM10" (not sure if that matters). I issue the mkinitrd command from a chroot''d environment so I get the right /lib/modules &

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

> -----Original Message----- > From: centos-bounces at centos.org > [mailto:centos-bounces at centos.org] On Behalf Of Robert Heller > Sent: Sunday, March 08, 2009 15:46 > To: CentOS mailing list > Cc: CentOS mailing list > Subject: Re: [CentOS] Creating an alternitive install CD for CentOS > 5.2 (w/patched mkinitrd) > > At Sun, 8 Mar 2009 08:47:50 -0400 CentOS

Hi, I did a command-line upgrade of a RHL73 server to Centos 5. It was a bit rocky road, but in the end it was successful. There's one thing that bugged me. I'm using software RAID1 consisting of /dev/hd{a,c}. No LVM or anything fancy, a number of /dev/mdX partitions, including the root (+/boot). I'd have preferred to continue using lilo as it works more easily with RAID1

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

On Thu, Mar 29, 2007 at 03:39:01PM +0100, richard wrote: > bin/xapian-tcpsrv.cc,tests/harness/testsuite.cc: First of many > parts of a large patch from Mark Hammond working towards enabling > remote databases on windows. When displaying errors which might > be socket errors, display the error number as well as the output > of strerror - on windows, strerror doesn't display

Hi: I am installing Xen on Suse Linux Enterprise Server 10 SP2, when I try to make initrd img as README descirbed, but it tells me: #depmod 2.6.16.29-xen #mkinitrd -v -f --with=aacraid --with=sd_mod --with=scsi_mod initrd-2.6.16-xen.img 2.6.16-xen Unknown option: -v Try mkinitrd -h Then I added the "aacraid, sd_mod, scsi_mod" to "INITRD_MODULES" section in

Hi, I have a XEN machine booting nicely on regular partitions and using LVM for the guest domains. As Now I am looking to convert another machine (Debian) to XEN, on which all but a /boot partitions are on LVM. The Debian mkinitrd tool is geared toward Debian kernels and is not useful in this case. I have also tried http://www.poochiereds.net/svn/lvm2/lvm2create_initrd, but I am unsure as to

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.

Hi, my yum update freezed on the mkinitrd (second time it happens in 5.3): Running Transaction Updating : kernel-headers [ 1/22] Updating : viewvc [ 2/22] Updating : sos [ 3/22] Installing : kernel-devel [ 4/22]

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

Hello, I''ve installed XenExpress 3.2. Within a DomU (Debian) I want to recompile the kernel. I installed the kernel-source /kernel-xs-xen/kernel-2.6.16.38-xs3.2.0.531.3960.src.rpm from the XenServer-3.2.0-src1.iso. The kernel and modules build well. But: ---------------------------- IPCopHost:~# mkinitrd -o /boot/initrd-2.6.16.xen-38 2.6.16.xen-38 /usr/sbin/mkinitrd: /dev/xvda1: Unknown

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

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

Dear ALL, I have encountered an issue while installing xen4.1.2 from source. No problem encountered while xen installation.While booting towards XEN kernel, i encountered the folowing error ******************** setuproot: moving /dev failed : No such file or directory no fstab,sys mounting internal defaults setuproot: error mounting /proc setuproot: error mounting /sys Kernel

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

On Thu, March 24, 2016 11:56, g wrote: > > > On 03/24/16 09:29, Richard wrote: >>> Date: Thursday, March 24, 2016 14:10:41 +0000 >>> From: Always Learning <centos at u64.u22.net> >>> On Wed, 2016-03-23 at 22:29 -0700, Alice Wonder wrote: >>> >>>> What purpose does it serve? I don't object to it being there >>>> but I

I've added new volume group with single logical volume: pvcreate /dev/sdb1 vgcreate -s 32m xxx_vg /dev/sdb1 lvcreate -l 1234 -n yyy_lv xxx_vg and rebooted the server after it. When booting, the kernel panics with can't mount root file system. Looking at the console output, it seems all volume groups and all logical volumes on them were imported correctly. However, if I go to