Hi everybody!
I'm just trying to set up a new FAI server with the latest version from
koeln repository. It's a XenU (Version is 3.2 from BPO running on a DELL
PE2950 with Debian Etch amd64). fai-setup passed successfully without
errors besides the GPG warning for Thomas' and BPO repo. I checked
On Thu, 26 Jun 2008 10:58:05 +0200, Tobias Herziger [EMAIL PROTECTED]
said:
kernel= '/boot/vmlinuz-2.6.18-6-xen-amd64'
ramdisk = '/boot/initrd.img-2.6.18-6-xen-amd64'
You have to use the kernel and initrd that is generated by
make-fai-nfsroot. Only this initrd will include the
On Thu, 26 Jun 2008 10:58:05 +0200, Tobias Herziger [EMAIL PROTECTED]
said:
kernel = '/boot/vmlinuz-2.6.18-6-xen-amd64'
ramdisk = '/boot/initrd.img-2.6.18-6-xen-amd64'
You have to use the kernel and initrd that is generated by
make-fai-nfsroot. Only this initrd will include
Hi!
Today's not my most successful day ;)
I'm now discovering the following problem: I try to xm create
mysqlprx01 vminstall=1 -c a new XenU. I'm getting the busybox but
unionfs mount failed. Why? Does somebody know why ROOTPATH is empty?
Mr Google didn't gave me an appropriate answer :(
Hi!
Today's not my most successful day ;)
Well, then let's make it your most successful day :-))
I'm now discovering the following problem: I try to xm create
mysqlprx01 vminstall=1 -c a new XenU. I'm getting the busybox but
unionfs mount failed. Why? Does somebody know why ROOTPATH is
ok,
so apparently i was accidently using the older version of FAI that's why
it couldn't parse
i can choose to NOT USE SETUPSTORAGE and i can do an fai install fine
but now i'm having problems on the reboot with a setupstorage install
after FAI finishes the system hangs on boot
i need to get
I would like to partition a system that has plenty of free space left in
lvm volume group so I can do online backups of databases. I devised the
following configuration for that:
disk_config sda bootable:1
primary /boot 128 ext2rw
primary - 10240- - -
disk_config lvm
vg
[...]
By the way, for fai-client 3.2.8 is it normal that installation fails if
a target hard drive contains LVM volume? I'm just wondering is this a
bug or a feature. The same disk layout configuration works if I erase a
couple of megabytes in the beginning of the disk.
I haven't
ok so i tried not including /dev and it does the same thing
it halts on trying to mount root on startup when i reboot
i've attached the log
Oh yes ... please add
$ROOTCMD update-initramfs -k all -u
to one of your scripts, maybe LAST/50-misc or add some script named
SETUPSTORAGE; we'll add
