similar to: CentOS 5.4 :: partitionable RAID1

I have some suggested tweaks and changes to http://wiki.centos.org/HowTos/Install_On_Partitionable_RAID1 1. The user should be instructed to start rescue mode with networking in order to be able to retrieve the patch for mkinitrd. 2. The command to create /etc/mdadm.conf will result in an extra line "spares=1" while the array is still syncing. Adding " | head -1 " to the

Environment: CentOS 6.2 amd64 (min. server install) 2 virtual hard disks of 10GB each Linux KVM Following the instructions on CentOS Wiki <http://wiki.centos.org/HowTos/Install_On_Partitionable_RAID1> I installed a min. server in Linux KVM setup (script shown below) <script> #!/bin/bash nic_mac_addr0=00:07:43:53:2b:bb kvm \ -vga std \ -m 1024 \ -cpu core2duo \ -smp 2,cores=2 \

Hi, After reading the tutorial at http://wiki.centos.org/HowTos/Install_On_Partitionable_RAID1 I have the following question: What should I put instead of splashimage=(hd0,0)/grub/splash.xpm.gz and root (hd0,0) on /etc/grub.conf? Should I leave those lines untouched? If so, how would grub know where to boot from if /dev/sda fails? Or I would need to swap the drives in order to boot

Hi. The following HowTo on the CentOS Wiki: http://wiki.centos.org/HowTos/Install_On_Partitionable_RAID1 valid for CentOS 5, has not been updated to CentOS 6, yet. I found it very useful during the glorious CentOS 5 days and now that I've successfully ported my RAID1 experience to CentOS 6, I'd like to share it with the Community. The title of the HowTo is currently: "How to

Hi. The following HowTo on the CentOS Wiki: http://wiki.centos.org/HowTos/Install_On_Partitionable_RAID1 valid for CentOS 5, has not been updated to CentOS 6, yet. I found it very useful during the glorious CentOS 5 days and now that I've successfully ported my RAID1 experience to CentOS 6, I'd like to share it with the Community. The title of the HowTo is currently: "How to

Hello all, I'm trying to install CentOS 6.3 to an mdadm partitionable array and not having any luck. The installer only allows me to create one file system per md device, or specify the md device as a LVM physical volume. I don't want to do either, I want to create one md device and create multiple partitions on top of the md device. I thought that perhaps the installer was preventing

On the wiki page for creating a mirrored root drive, at <https://wiki.centos.org/HowTos/Install_On_Partitionable_RAID1>, it first tells you, in the install, to chose manual partitioning, and to leave at least 1M at the end of the drive.... and then it tells you to create the RAID 1 using /dev/sda and /dev/sdb - the *whole* raw drives. mark, currently creating a RAID 1 using just

Hi, I've written two small howtos, and would like to contribute them to the CentOS Wiki. The first one is "How to install CentOS 5 on software partitionable mdadm RAID1", and the second one "How to repair a software mdadm RAID5 with two or more failed disks (if you know that information is still on the disks and readable)". I think that the first one should be somewhere

Hello Since linux 2.6, the md layer has a feature called partitionable arrays. So instead of having two disks, creating an identical partition table on both and then putting those partitions in RAID 1, you take those two disks and put them in one partitionable RAID 1 array (in mdadm terms, "mdp") and create a partition table on the new RAID device. The advantages are quite clear

OK sorry to hammer the list but one more question - having almost got the drives mirrored and happy - since I have created a custom initrd that has the raid1 drivers in it, do I now have to tell yum to ignore kernel updates? Will the stock kernel render me unbootable? Actually I am not 100% sure the initrd I created # mkinitrd -f --preload=raid1 /mnt/tmp/initrd-`uname -r`.img `uname -r` is

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

Hi! I have 2 identical hdd (1002FBYS) with the same firmware, etc .. really identical! when i try to add the second hdd to this raid1 array i have the message that /dev/sdb is not large enough to join array!! on the first hdd i have 100 mb unpartitioned at the end of disk (as i understood that mdadm put there some info...) Anyone, any idea what can be wrong? i already done this procees several

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

dear All, I'm spending the afternoon trying to build software raid using this ( excellent ) guide : http://wiki.centos.org/HowTos/Install_On_Partitionable_RAID1 I'm doing this not only because this machine has no raid controller - I could go out and buy one - but also because I hope software raid will provide easier monitoring. This is a newly installed, updated Centos6.4 standard

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

Mm, I have a big Quad-Opteron.. thing.. that I''m trying to get Xen onto. I''ve used the 3.0.2 binary-install mode, updated menu.lst as per the README, but I need an initrd which contains the HP cciss RAID driver, and no Xen initrd image was installed into /boot. Now I notice xen-3.0.2-2-install/install/lib/modules/2.6.16-xen/kernel/drivers /block/cciss.ko But I

Folks, Mercurial is selectable as an installation in OpenSUSE 10.3 YAST. I have done the following: hg clone http://xenbits.xensource.com/xen-unstable.hg hg clone http://xenbits.xensource.com/linux-2.6.18-xen.hg make dist sh ./install.sh I tried running the following to create the initrd but it failed: Depending on your config, you may need to use ''mkinitrd'' 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

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