[sisuite-users] RE : Which version ?

[LAHAYE O. <oli...@ce...>]

Hi,

You can try the 4.3.0-0.1svn version, it worked for me. You'll need pre and post-install scripts available here: http://olivier.lahaye1.free.fr/RPMS/extra/

Cheers,


--
   Olivier LAHAYE
   CEA DRT/LIST/DCSI/DIR
________________________________
De : dav...@cn... [dav...@cn...]
Date d'envoi : mercredi 19 décembre 2012 00:09
À : sis...@li...
Objet : [sisuite-users] Which version ?


I have been using a modified version of  4.1.99.svn4556_bli-1 to load my i386 rhel6.x servers as
described below. I am now looking at imaging similar machines but now with the x86_64 version
of rhel6.3 so I need like initrd_template( and boot_standard if it works) packages.

What  versions should I be trying ?  http://olivier.lahaye1.free.fr/RPMS/noarch/   ??

Thanks



David K Livingstone
CN Signals and Communications
10229 127 Avenue floor 2
Walker Operations East Building
Edmonton, AB, T5E 0B9
Ph  : 780 472-3959 Fax : 780 472-3046
Email: Dav...@cn...
----- Forwarded by David Livingstone/LIVING03/CNR/CA on 2012/12/18 16:00 -----
From:   David Livingstone/LIVING03/CNR/CA
To:     sis...@li...
Date:   2012/03/29 09:41
Subject:        Loading RHEL 6.2 using 4.1.99.svn4556_bli-1

________________________________


Using  systemimager  4.1.99.svn4556_bli-1(ext4 enabled version) I have successfully imaged a
RHEL 6.2 image to HP DL380G7 hardware(p410 array controllers). I was considering using SALI
however for RHEL6.x grub2 is not an issue and ext4 support is included in  4.1.99.svn4556_bli-1.

The setup I was imaging is a Proliant DL380G7 server with two p410 controllers(p401i and p410)
with raid1 for root/boot/swap on the p410i and raid5 for /data on the p410. The system is running
the latest RHEL 6.2.

The attempted to image the system in two ways:
1. standard kernel
2. uyok

1. standard kernel
    I eventually got this to work but only after major modifications to the install script and manually
    setting up grub.  The major issue here is that the default kernel uses the cciss driver and
    device naming(ex /dev/cciss/c0d0p2) and the RHEL6.x uses the hpsa driver(scsi naming ex /dev/sda).
    See http://h20000.www2.hp.com/bc/docs/support/SupportManual/c02677069/c02677069.pdf  .
    In general RHEL 5.x and before uses the cciss driver and RHEL6.x uses the hpsa when possible.
    I presume the standard kernel could be built with the hpsa module and some version logic
    applied to resolve this.

2. uyok
    This worked successfully after making some changes to address :
     - Needed modules(ie hpsa) as symbolic links  under /lib/modules/(uname -r)
       ex
[root@scdev ~]# ls -al /lib/modules/2.6.32-220.4.2.el6.i686/weak-updates/hpsa/hpsa.ko
0 lrwxrwxrwx 1 root root 50 Mar  5 04:05 /lib/modules/2.6.32-220.4.2.el6.i686/weak-updates/hpsa/hpsa.ko -> /lib/modules/2.6.32-71.el6.i686/extra/hpsa/hpsa.ko
[root@scdev ~]#
        This results in the modules not being copied correctly in the generated initrd.
         I resolved this by modifying the UseYourOwnKernel.pm rsync invocations
         to copy the resultant files(the L rather then the l option. I include the diff
         below.

    - Numerous /lib/firmware files were missing in the initrd. By default the
      bnx2 nic driver(driver for the four nic's on the motherboard) as well as
      others in the RHEL6.2 kernel request firmware which is missing in the
      uyok initrd. I got this to work by :
       - modifying UseYourOwnKernel.pm to copy /lib/firmware to the initrd.
         Unfortunately this copies all of firmware as I couldn't figure out how to
         dynamically copy what was needed.
       - modified rcS under the std template to start udev BEFORE the modules
         are inserted.
    - rcS : start udev before loading modules.
       - under the std template :
         /usr/share/systemimager/boot/i386/standard/initrd_template/etc/init.d/rcS
    - The ramdisk_size must be set high enough to accept the larger initrd.
    -  I had to si_cpimage as part of testing and noted that for yuok the
       kernel and initrd.img files are not copied. They had to be copied manually.


Notes :
 When creating the image initially  I also had to change si_prepareclient to use parted rather then sfdisk. I believe a bug
 was submitted on this a long time ago which was never applied. parted supports gpt
 partitions and sfdisk does not.

[root@nasmtl sbin]# diff si_prepareclient si_prepareclient.orig.4.1.99.svn4556_bli
969,971c969,971
< #        if($arch eq "i386") {
< #                $preferred_tool = 'sfdisk';
< #        }
---
>         if($arch eq "i386") {
>                 $preferred_tool = 'sfdisk';
>         }

- Diff for UseYourOwnKernel.pm
[root@nasmtl SystemImager]# diff UseYourOwnKernel.pm UseYourOwnKernel.pm.orig
152c152
<                 $cmd = qq(rsync -aL --exclude=build --exclude=source ) .
---
>                 $cmd = qq(rsync -a --exclude=build --exclude=source ) .
159c159
<                     $cmd = qq(rsync -aLR $module $staging_dir);
---
>                     $cmd = qq(rsync -aR $module $staging_dir);
223,225d222
<         #
<         # Copy /lib/firmware file to initrd
<         #
227,233d223
<         if (-d "/lib/firmware") {
<            # copy entire firmware tree to new initrd.
<            $cmd = qq(rsync -aLR /lib/firmware $staging_dir);
<            !system( $cmd ) or die( "Couldn't $cmd." );
<
<         }
<

- Diff for rcS :
[root@nasmtl init.d]# diff rcS rcS.orig
45,47d44
< # Start udev BEFORE load_my_modules so the modules can load firmware if needed.
< start_udevd
<
49a47,48
> start_udevd
>







David K Livingstone
CN Signals and Communications
10229 127 Avenue floor 2
Walker Operations East Building
Edmonton, AB, T5E 0B9
Ph  : 780 472-3959 Fax : 780 472-3046
Email: Dav...@cn...