Hello, Andrea.
Thanks for your assistance.
I have new info as well, but I appreciate that changing the line numbers
may have been necessary also.
The problem though, is that the mount order dependency was not noticed
by SI, though it does work correctly in other cases.
For example, I have just been busy creating a golden image for the same
hardware but a different OS (RedHat 8). we have the almost the same
partitioning scheme but on that platform si_prepareclient/si_getimage
correctly notices the mount dependency.
e.g.
[EMAIL PROTECTED] root]# fdisk -l /dev/hda
Disk /dev/hda: 255 heads, 63 sectors, 4863 cylinders
Units = cylinders of 16065 * 512 bytes
Device Boot Start End Blocks Id System
/dev/hda1 * 1 13 104391 83 Linux
/dev/hda2 14 274 2096482+ 82 Linux swap
/dev/hda3 275 4862 36853110 83 Linux
[EMAIL PROTECTED] root]# df -l
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/hda3 35698972 3509900 30346420 11% /
/dev/hda1 101089 19673 76197 21% /boot
none 515000 0 515000 0% /dev/shm
Note 2 differences between the partitioning scheme between my CentOS4.2
golden image and my RH8 image. They are:
1) there is only 1 swap partition on RH8 (hda2) whereas COS has 2 (hda2
and hda3) and
2) the root partition is hda3 on RH8 and hda4 on COS.
There are numerous differences between RH8 and COS4 so perhaps some
regression has found its way into the sorting and searching functions.
More likely is that the code is confused by 2 swap partitions, but this
is just a guess as I havn't looked at it.
thanks again,
p
Paul Newman wrote:
Bernard Li wrote:
can do but how do I regenerate my autoinstall script? do I redo the
si_getimage? I notice there is also something called
si_mkautoinstallscript on the server. sounds promising but it is not
installed on the client. do i copy this over to the client and use it?
Yes you run si_mkautoinstallscript to regenerate the script (make sure
you make a backup copy before you run it).
The script is executed on the image server, which should contain a copy
of your golden image.
Hi, Bernard.
I changed <the image>/etc/systemimager/autoinstallscript.conf per your
suggestion and ran si_mkautoinstallscript. it generated a new
/var/lib/systemimager/scripts/<the image>.master
this is enclosed. note the order is still the same, i.e. wrong and will
result in an image that mounts root on top of /boot.
Paul,
you have to switch the 2 lines and modify the line number to have the
right mount order. Attached your autoinstallscript.conf correctly modified.
Anyway, the strange thing is that si_prepareclient should generate this
file properly, respecting the right order... in particular the order
should be the same of the `mount` command. What's the output of this
command in your golden client?
Regards,
-Andrea
------------------------------------------------------------------------
--
I'm afraid of commitment and will never submit
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
Sisuite-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/sisuite-users
