I've got some good news. At least now the cloned system boots. There
was something related with the modules and therefore with the initrd file.
I was using UYOK and not BOEL, sorry, but I tried to add some extra
modules in the file /etc/sysconfig/kernel, line starting with
INITRD_MODULES, run mkinitrd and repeat the whole process again
(si_prepareclient, si_getclient, PXE-booting + autoinstall, reboot, ...)
Now I can clone the system and when rebooting it starts using Grub,
what I didn't force because finally I didn't add the PREFERED param
under the BOOT section of systemconfig.conf file.
I check the autoinstall logging and I saw several things:
1. The system tries to run lilo but it can't because kernel is too
big (at least is what it says):
Error: Cannot execute /sbin/lilo.
Fatal: Kernel /boot/vmlinux-2.6.22.5-31-default.gz is too big
at /usr/lib/systemconfig/Boot.pm line 112
2. After that it installs grub
3. At the end systemconfigurator says it has modified the following
files:
/etc/lilo.conf
/etc/modprobe.conf
/etc/modules.conf
/etc/sysconfig/network/ifcfg-eth0
There are some strange things:
1. The lilo.conf file created by systemconfigurator seems to be
wrong, it has an orphan parameter which has to do with the root disk
partition named by-id ('tor_6L080M0_L26FVVDG-part2'). Here you are both
/etc/lilo.conf files, the original of the golden node and the one that
generates systemconfigurator
----- /etc/lilo.conf of the golden node and the image
# Modified by YaST2. Last modification on Wed Feb 6 13:51:17 CET 2008
menu-scheme = Wb:kw:Wb:Wb
timeout = 80
lba32
change-rules
reset
read-only
prompt
message = /boot/message
boot = /dev/disk/by-id/scsi-SATA_Maxtor_6L080M0_L26FVVDG-part2
default = oS_10.3
image = /boot/vmlinuz-2.6.22.5-31-default
###Don't change this comment - YaST2 identifier: Original name: linux###
label = oS_10.3
append = "resume=/dev/sda1 splash=silent showopts"
vga = 0x314
initrd = /boot/initrd-2.6.22.5-31-default
root = /dev/disk/by-id/scsi-SATA_Maxtor_6L080M0_L26FVVDG-part2
image = /boot/vmlinuz-2.6.22.5-31-default
###Don't change this comment - YaST2 identifier: Original name: failsafe###
label = Failsafe
append = "showopts ide=nodma apm=off acpi=off noresume edd=off 3"
vga = normal
initrd = /boot/initrd-2.6.22.5-31-default
root = /dev/disk/by-id/scsi-SATA_Maxtor_6L080M0_L26FVVDG-part2
image = /boot/memtest.bin
###Don't change this comment - YaST2 identifier: Original name: memtest86###
label = Memory_Test
----- end
----- /etc/lilo.conf on the cloned machine (modified by systemconfigurator)
##################################################
# This file is generated by System Configurator. #
##################################################
# Do all the normal things lilo does
lba32
map=/boot/map
install=/boot/boot.b
vga=normal
# The number of deciseconds (0.1 seconds) to wait before booting
prompt
timeout=50
# The boot device where lilo installs the boot block
boot=/dev/sda
# the default label to boot
default=suse-10.3
# Device to be mounted as the root ('/')
root=/dev/sda2
#----- Options for KERNEL0 -----#
image=/boot/vmlinux-2.6.22.5-31-default.gz
label=suse-10.3
read-only
append="auto BOOT_IMAGE=oS_10.3 ro root=/dev/sda2
tor_6L080M0_L26FVVDG-part2 resume=/dev/sda1 splash=silent showopts"
initrd=/boot/initrd-2.6.22.5-31-default
----- end
2. The system boots using grub but the file menu.lst has not been
modified. At least the labels are the ones from the previous
installation of openSUSE 10.1 of the golden node. Obviously it works
because of the links of the /boot directory to the right versionof the
kernel and initrd.
----- /boot/grub/menu.lst on the golden node, the image and the clone system
# Modified by YaST2. Last modification on Wed Oct 18 16:28:13 CEST 2006
color white/blue black/light-gray
default 0
timeout 8
gfxmenu (hd0,1)/boot/message
###Don't change this comment - YaST2 identifier: Original name: linux###
title SUSE Linux 10.1
root (hd0,1)
kernel /boot/vmlinuz root=/dev/sda2 vga=0x314 resume=/dev/sda1
splash=silent showopts
initrd /boot/initrd
###Don't change this comment - YaST2 identifier: Original name: failsafe###
title Failsafe -- SUSE Linux 10.1
root (hd0,1)
kernel /boot/vmlinuz root=/dev/sda2 vga=normal showopts ide=nodma
apm=off acpi=off noresume edd=off 3
initrd /boot/initrd
###Don't change this comment - YaST2 identifier: Original name: memtest86###
title Memory Test
kernel (hd0,1)/boot/memtest.bin
----- end
----- /boot directory initrd and vmlinuz files
lrwxrwxrwx 1 root root 26 Feb 26 22:12 initrd ->
initrd-2.6.22.5-31-default
-rw-r--r-- 1 root root 4544722 Feb 26 17:45 initrd-2.6.22.5-31-default
-rwxr-xr-x 1 root root 1960389 Sep 24 21:09 vmlinux-2.6.22.5-31-default.gz
lrwxrwxrwx 1 root root 27 Feb 26 22:12 vmlinuz ->
vmlinuz-2.6.22.5-31-default
-rw-r--r-- 1 root root 1594088 Sep 24 21:02 vmlinuz-2.6.22.5-31-default
----- end
What should I do to be able to run /sbin/lilo? Trying using UYOK to
reduce the size of the kernel? Modifying manually the existing
/etc/lilo.conf on the image?
And regarding Grub, what is being used accidentally, does
systemconfigurator modify the menu.lst config file? Can I change the
labels of the file directly on the image?
Many thanks.
jesús .-
Andrea Righi wrote:
> Jesús Sánchez González wrote:
>> On 2/23/08, *Andrea Righi* <[EMAIL PROTECTED]
>> <mailto:[EMAIL PROTECTED]>> wrote:
>>
>> Jesús Sánchez González wrote:
>> > Hello.
>> >
>> > I am having problems cloning a recently upgraded golden client.
>> > I managed to generate the image and to clone a new node, after
>> rebooting
>> > I got lilo and I tried to start the system but it complained
>> saying that
>> > 'Could not find /dev/sda2'.
>>
>>
>> Ok, stupid question: is /dev/sda2 the correct device for / (could you
>> post also your autoinstallscript.conf)?
>>
>>
>> On every node, include the golden client we are trying to clone after
>> the upgrade we have /dev/sda2 mounted on /.
>> Here you are the autoinstallscript.conf (head comments omitted):
>>
>
> autoinstallscript.conf seems ok.
>
>> > I tried also to install grub through a post-install script and
>> although
>> > I didn't see any errors, the system keep on booting with lilo.
>>
>>
>> Could you try to add the PREFERED parameter under the BOOT section of
>> systemconfig.conf in your golden client?
>>
>> [BOOT]
>> PREFERED = Boot::Grub
>> ...
>>
>>
>> Do you mean keeping the post-install script to install grub, don't you?
>
> No, the PREFERED option should be enough.
>
>> And try to re-clone the image (si_prepareclient on golden client and
>> si_getimage on your image server).
>>
>> -Andrea
>>
>>
>>
>> I didn't point that the new nodes are slightly different than the
>> golden-node regarding to the hard disk type, which in the new nodes is a
>> SATA drive.
>
> mmmh... are you using the standard BOEL for imaging or UYOK? Have you
> already tried with both?
>
> -Andrea
--
--------------------------------------------------------------------------
Jesus Sanchez Phone: +34 934034770
Information Technology Services (ITS)
Institute for Research in Biomedicine (IRB) http://www.irbbarcelona.org
C/Baldiri Reixac 13 08028 Barcelona (Spain)
--------------------------------------------------------------------------
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
sisuite-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/sisuite-users
