similar to: raid1 custom initrd and yum

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

I am trying to convert an existing IDE one-disk system to RAID1 using the general strategy found here: http://lists.centos.org/pipermail/centos/2005-March/003813.html But I am stuck on one thing - when I went to create the second md device with mdadm, # mdadm --create /dev/md1 --level=1 --raid-devices=2 /dev/hdb2 missing mdadm: error opening /dev/md1: No such file or directory And indeed,

I have an existing in-production LAMP server running Centos 5.1. It uses physical partitions on top of hardware RAID1, having / /home /var and /boot on separate partitions. We have a near-identical system I am thinking of bringing in as a DRBD/Heartbeat companion. One solution may be to use csync2 [http://oss.linbit.com/csync2/] on /etc and /usr/local (the only areas that will differ from

Hi everyone. Some body knows why my instalation always says Could Not mount root device (0,0), then reboots, i try to compile my own dom0 kernel, but always says the same thing. I''m seeking on create the initrd image, but nothings works. :( The currently hardware profile is this. Intel Server Board SE7230NH1-E (VT Enabled Motherboard) Intel Pentium D 830 CPU (3Ghz x 2 CPU) 2 GB

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

Hi! Did anyone tried this on 5.4? having a look on http://wiki.centos.org/HowTos/Install_On_Partitionable_RAID1 is would seem that that mkinitrd patch is no longer required. Can someone ack this? Thanks, Adrian -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 3110 bytes Desc: S/MIME Cryptographic Signature URL:

Has anyone had issues starting xen0 on a md? I have installed it a few times now w/ and w/o raid. Anytime I have a raid1 mirror, Xen panics on boot when trying to mount /. It gets past waiting for /dev/md0 to appear. John _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users

Has anyone had issues starting xen0 on a md? I have installed it a few times now w/ and w/o raid. Anytime I have a raid1 mirror, Xen panics on boot when trying to mount /. It gets past waiting for /dev/md0 to appear. John _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users

CentOS Community, I have a dedicated server with 4 hard drives in a RAID 10 software configuration running LVM. My OS is CentOS 6.2. Earlier today, I rebooted my system and my system did not come back online. I opened a ticket with my datacenter who informed me that one of my hard drives is no longer recognized by the bios and has failed. I was told that an OS reinstall was needed. I

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

As promised, here''s what I did to get iSCSI root running under XenU under Debian 3.1 (Sarge): Be running linux 2.6 under XenU. Build XenU with SCSI disk support (I did them as modules) Get linux-iscsi 4.0.1.8 from http://sourceforge.net/projects/linux-iscsi/ Build it according to the instructions there (i found it a bit tricky) and install under your XenU Get iscsi-init 4.0.1 from

I''m struggling to get Xen to boot on a FC4 Opteron box. I''ve included the tail of the boot log below [1]. I suspect that the problems relates to the software RAID 1 root and boot partitions, and how it relates to the initrd image. The RAID volumes fail to mount. I compiled the Xen snapshot from the 23rd September, and the only change I''ve made is to enable the

so, Just chroot to mountpoint: http://www.cyberciti.biz/faq/unix-linux-chroot-command-examples-usage-syntax/ chroot /mounted/path /bin/bash and then .. mkinitrd (see man page for documentation) 2016-10-30 22:57 GMT+02:00 Eero Volotinen <eero.volotinen at iki.fi>: > A bit hard to say. Try chrooting into environment and rebuilding initrd? > > -- > Eero > > 2016-10-30

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, I have a P4 2.4 GHz CPU (hyper threading) and have been using the 2.4.21-20.EL.c0smp kernel and it works perfectly. I installed the new kernel-smp (2.4.21-20.0.1.EL) kernel and it installed flawlessly. However, every time I boot I get a kernel panic and I must reboot to the older kernel. The error I am getting is: (it seems to be failing on jbd.o and ext3.o) Kernel

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 ?

I've managed to install CentOS 5.1 on S5000PAL with fakeraid Intel Embedded Raid Technology II Raid1 (LSI chipset) with some help of kickstart declaration 'driverdisk --source=http://.../driver.img' Then I've had some problems with yum update - new kernel didn't know about megasr.ko. I've solved it with commands: cd /lib/modules/ cp 2.6.18-53.el5PAE/updates/megasr.ko

Hi, Any one know how the Centos 5 kickstart initrd.img was built? I'll be very appreciated if any light can be shed on this topic. The basic problem to be solved here is: how to build a custom vmlinuz+initrd.img for Centos 5 kickstart with my own custom built kernel? I am not sure mkinitrd is the right tool for this purpose? If do, which are the modules I should include with

Dear All, I would like to get community's feedback with regard to RAID1 ( Software or Hardware) implementations with asterisk. This is my setup Motherboard with SATA RAID1 support CENT OS 4.4 Asterisk 1.2.19 Libpri/zaptel latest release 2.8 Ghz Intel processor 2 80 GB SATA Hard disks 256 MB RAM digium PRI/E1 card Following are the concerns I am having I'm planing to put this asterisk

Hi, anyone to point me URL on initrd.img creating? I have custom kernel and want to create initrd.img for install media. mkinitrd /tmp/initrd.img 2.6.18-8.1.14.el5.hrb -v -f create unusable file for install media. Thanks, David