Re: [sisuite-users] SI 4.1.6: <image>/boot directory empty in golden client image on the server

[Büchmann H. <en...@bu...>]

Hi Guy,

I met this issue recently. Probably, you have /boot on a separate 
partition AND /boot on a lower/earlier number than / (right?). This is 
quite normal setup, but the present version(s) of SI-suite seems to have 
problem with it.
What happens during installation (if I traced down and remember 
correctly) is that the disk is that each partition is created, formatted 
(with file system) and mounted on temporary mount point in turn. Thus, 
assume that sda1 is /boot and sda2 is /, as in my own first try.
What happens is:
  1. sda1 is created and mounted as /a/boot/.
  2. sda2 is created and mounted as /a/

Note that pnt 2 obscures the mount  point of sda1 (the boot partition). 
Thus, during subsequent rsync, all files for /boot/ ends in /a/boot/, 
which is really a directory on sda2(!)

My (ugly) solution is simply to get rid of the separate boot partition, 
and let sda1 be /, which contains /boot as a directory. I think most 
modern distributions should be happy with that choice.

Let me know, how it works out.

/Bjarne

On 26-06-2012 3:45, Guy Paulus wrote:
> Hello:
>
> Let me outline the configurations of the golden client and the SI (and PXE)
> server:
>
> Golden client
> -------------
> OS: Oracle Linux 6.2
> Kernel version: 2.6.32-300.3.1.el6uek.x86_64
> Disk layout: /dev/sda1 /boot ext4
>               /dev/sda2 / ext4
> Version of systemimager: 4.1.6
> Version of systemconfigurator: 2.2.11-1
>
> SI server
> ---------
> OS: Scientific Linux 6.2
> Kernel version: 2.6.32-220.7.1.el6.x86_64
> Disk layout: /boot (ext4) + LVM [LVM version: 2.02.87(2)-RHEL6 (2011-10-12);
> Library version: 1.02.66-RHEL6 (2011-10-12); Driver version: 4.22.6]
> Version of systemimager: 4.1.6
> Version of systemconfigurator: 2.2.11-1
> Using rsync to pull the golden client image
>
> Problem
> -------
> After performing si_getimage on the SI server, the <image>/boot directory is
> empty. As a result, when I PXE boot a client, the autoinstall fails because
> systemconfigurator complains that the kernel
> /boot/vmlinuz-2.6.32-300.3.1.el6uek.x86_64 does not exist.
> There is no explicit exclusion of /boot in /etc/systemimager/getimage.exclude.
>
> Did I miss something at the si_prepareclient stage ? I did
> si_prepareclient --server <ip address> --my-modules --yes
>
> The /etc/systemconfig/systemconfig.conf file reads
>
> [BOOT]
> ROOTDEV = /dev/sda2
> BOOTDEV = /dev/sda
> DEFAULTBOOT = systemimager
>
> [KERNEL0]
> LABEL = systemimager
> PATH = /boot/vmlinuz-2.6.32-300.3.1.el6uek.x86_64
> INITRD = /boot/initrd-2.6.32-300.3.1.el6uek.x86_64.img
> APPEND = KEYBOARDTYPE=pc KEYTABLE=us LANG=en_US.UTF-8 SYSFONT=latarcyrheb-sun16 quiet rd_NO_DM rd_NO_LUKS rd_NO_LVM rd_NO_MD rhgb ro
>
> Or did I miss something at the si_getimage stage ? I did
>
> sudo si_getimage --golden-client <ip address> --image blade0 --ip-assignment replicant --post-install reboot
>
> Thanks.
>
> Guy Paulus
>
>
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> sisuite-users mailing list
> sis...@li...
> https://lists.sourceforge.net/lists/listinfo/sisuite-users
>