Hello,
I have a weird problem after adding new PV do LMV volume group.
It seems the error comes out only during boot time. Please read the story.
I have couple of 1U machines. They all have two, four or more Fujitsu-Siemens
SAS 2,5" disks, which are bounded in Raid1 pairs with Linux mdadm.
First p
I forgot to mention that after creation of md2 I've added a new line to
/etc/mdadm.conf:
# cat /etc/mdadm.conf
DEVICE partitions
MAILADDR root
ARRAY /dev/md0 level=raid1 num-devices=2
UUID=91518bd3:79953138:f203f159:f2795fde
ARRAY /dev/md1 level=raid1 num-devices=2
UUID=5b6722ca:b325344b:4ab40f
I solved this issue thanks to help on linux-lvm list from a guy from redhat.
Initrd image had to be recreated so that new raid devices could be seen
before root is mounted. Solution:
# mkinitrd /boot/initrd-$(uname -r).img $(uname -r)
--
Tomasz
___
Cen
Hello,
I successfuly run Centos 5.1 domU in Centos 5.1 dom0.
But I still have some minor issues/errors/warnings while
booting I'd like to fix and here are my questions:
1. How to disable loading usb host controler module:
[...from dmesg... ]
Loading uhci-hcd.ko module
USB Universal Host Contr
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
Hm... I've yum removed some old kernels in domU and...
they seem to dissappear also in dom0! :> Is that
possible?
--
Tomek
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos
Hello.
I can't install 5.3 domUs in 5.3 dom0 with the very same
/etc/xen/domU.cfg and remote domU.ks that I've used in
Centos 5.1. The only I've changed is Centos version
(including new 5.3 xen kernel and initrd images).
Results are that anaconda can't assing networki
configuration to network int
my previous install.cfg looked like this:
---
kernel = "/boot/vmlinuz-install"
ramdisk= "/boot/initrd-install.img"
extra = "ks=http://xx.yy.zz.xx/ks/domu.ks";
name = "domu"
vcpus = "4"
memory = "2048"
disk = [ 'phy:vg0/d
Ok, I've solved this issue by myself.
It turned out to be a MAC address conflict.
This is an Intel S5000PAL board with to NICs
LAN1 has MAC 00:15:17:77:4E:DE
LAN2 has MAC 00:15:17:77:4E:DF
So I assigned (see below) next MAC - 00:15:17:77:4E:E0
to first domU on that machine.
> ---
9 matches
Mail list logo