Displaying 20 results from an estimated 4000 matches similar to: "mkinitrd trouble"
2006 Oct 03
3
/usr/sbin/mkinitrd: illegal option -- v
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.
2017 Jun 01
1
[PATCH] v2v: tell v2v the real root device to mkinitrd
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
2009 Mar 06
2
Creating an alternitive install CD for CentOS 5.2 (w/ patched mkinitrd)
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
2010 Aug 03
1
[PATCH] Fix mkinitrd detection of LVM root on RHEL 4
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
2005 Nov 05
4
Module error in mkinitrd
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
2009 Feb 04
1
Extlinux support makes Fedora's mkinitrd
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
2005 Oct 10
1
mkinitrd-4.2.1.3-1 unsuitable for 2.6.13+ kernels?
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
2005 May 28
1
mkinitrd integration strategy?
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
2017 May 15
1
[PATCH] v2v: linux: pass the root device when using SUSE's mkinitrd
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.
---
2005 Sep 07
1
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
2010 Apr 22
2
[PATCH 1/2] Try to load the loop module before running mkinitrd
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
2011 Aug 03
0
can't recover LVM volume: Please specify a *single* volume group to restore
Hi everyone,
I'm trying to recover a deleted LVM volume but can't see to get the
syntax right.
Running the following command gives me a list of backed up LVM volumes:
root at usaxen02:[~]$ vgcfgrestore -l fluidVG_125094317679
------- snip ---------
File: /etc/lvm/archive/fluidVG_125094317679_00126-1479850541.vg
VG name: fluidVG_125094317679
Description: Created
2015 Feb 28
0
Looking for a life-save LVM Guru
----- Original Message -----
| Dear All,
|
| I am in desperate need for LVM data rescue for my server.
| I have an VG call vg_hosting consisting of 4 PVs each contained in a
| separate hard drive (/dev/sda1, /dev/sdb1, /dev/sdc1, and /dev/sdd1).
| And this LV: lv_home was created to use all the space of the 4 PVs.
|
| Right now, the third hard drive is damaged; and therefore the third PV
|
2015 Feb 28
1
Looking for a life-save LVM Guru
Dear James,
Thank you for being quick to help.
Yes, I could see all of them:
# vgs
# lvs
# pvs
Regards,
Khem
On Sat, February 28, 2015 7:37 am, James A. Peltier wrote:
>
>
> ----- Original Message -----
> | Dear All,
> |
> | I am in desperate need for LVM data rescue for my server.
> | I have an VG call vg_hosting consisting of 4 PVs each contained in a
> | separate
2009 Aug 18
1
[PATCH] Load the ext2 module so mkinitrd works on RHEL 3
---
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
2015 Feb 28
9
Looking for a life-save LVM Guru
Dear All,
I am in desperate need for LVM data rescue for my server.
I have an VG call vg_hosting consisting of 4 PVs each contained in a
separate hard drive (/dev/sda1, /dev/sdb1, /dev/sdc1, and /dev/sdd1).
And this LV: lv_home was created to use all the space of the 4 PVs.
Right now, the third hard drive is damaged; and therefore the third PV
(/dev/sdc1) cannot be accessed anymore. I would like
2006 Sep 28
1
Installing CentOS 2.1 on ICH7R controller
I'm trying to install CentOS 2.1 on SATA drive that lives on ICH7R
controller. I have the controller setup in BIOS to "compatibility"
mode, which means it should look just like regular IDE controller to
the OS. In this mode, ide0 and ide1 are PATA controllers, and 4 SATA
ports are mapped to ide2 and ide3.
If I boot from the 2.1 installation CD, all the drives are detected
2012 Jan 19
1
Wrong PV UUID
Dear All,
I have one VG with one LV inside consist of four disk (and four PV) somehow
the UUID is changed. I try to restore with the last known good
configuration and use
pvcreate --uuid xxx --restorefile xxx
but I think when I first time do it I did use wrong UUID for two device.
but haven't only using command above and haven't used vgcfgrestore. After
carefully read the configuration,
2009 Mar 09
1
Creating an alternitive install CD for CentOS 5.2 (w/patched mkinitrd)
> -----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
2006 Nov 15
0
System crashed & LVM1
Hi all!
I'm new to this list. I wanted to have an opinion of the situation i'm
facing now (i'm no expert in LVM). Last week, i had to re-install a
system which had a system hard drive crash (it was clunking before it
definitely died!). It was running on SuSE 9.0 before. I just finished
to install a fresh copy of CentOS 4.4 on a new hard disk.
I want to know if it's possible