Re: [Sisuite-users] rhel4 woes

[Daniel Crandall]

Title: Re: [Sisuite-users] rhel4 woes

Hi,
    I use Opterons and rhel4 with SIS, though I get there through
OSCAR.  For me, OSCAR eases many install pains.  I've used both the
"golden client" method as well as the systeminstaller method.  I usually
start by installing OSCAR and creating an image from rpms, then I push
the image out, work on the running configuration until I'm happy with
it, then suck it back in using si_prepareclient and si_getimage.
    I have had to nudge si_prepareclient to get it to work right before,
but my errors were different than the one you mentioned.
    I have seen similar partitioning weirdness when installing rhel4 in
general.
    Did you delete all of the default partitioning info and start from
scratch?  Or just the lvm partitions?  I find it helps to start with no
partitions - and if I remember correctly - I had to set real values to
my partition sizes and avoid the * "grow to fill" mechanism.

    FWIW, when I was having trouble getting off the ground with SIS, it
was suggested that I use OSCAR as a front end and that has worked well
for me.  If you don't install any optional packages, you'll get SIS and
c3 and a few other useful things but none of the message passing or
scheduling pieces.
    If you get way out in the weeds, you might consider that route.

-  dancran


Bernard Li wrote:

>Hi Mark:
>
> 
>
>>I've been struggling for a long time getting this to work on
>>an opteron
>>and it's not pretty.  I don't know if it's the processor or
>>rhel4 or a
>>combination, but here's what's going on.
>>   
>>
>
>Although I don't use SystemImager in the traditional sense (of taking
>golden image), I routinely push out RHEL4 images which are built by
>SystemInstaller and have no problems.
>
> 
>
>>I installed rhel4, which configures with lvm by default and I didn't
>>want it so I deleted and recreated my partition structure
>>before imaging
>>and I think that's a big part of the problem.  For example, at that
>>point parted lists the partitions out of order!  First 1, then 3 and
>>then 2.  When SI creates it's autoconfigurescript.conf it
>>also creates
>>it in that order, setting the second partition's size to *
>>and the 3rd
>>one to 4G (this is swap).  I manually changed the * to 65G and that
>>seems to work ok.   I consider this a bug in SystemImager!
>>   
>>
>
>Can you file this in SourceForge?
>
> 
>
>>rather than trying to dig through all the code more than I
>>have already
>>I was just wondering if anyone has had similar issues and
>>what they did
>>about them?
>>   
>>
>
>I suspect that SystemImager/SystemConfigurator currently do not support
>labels, this could be a feature request.  However, can you try again
>with physical mounts instead of labels?  Maybe that would work.
>
>Cheers,
>
>Bernard
>
>
>-------------------------------------------------------
>This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
>for problems?  Stop!  Download the new AJAX search engine that makes
>searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
>http://ads.osdn.com/?ad_idv37&alloc_id865&op=click
>_______________________________________________
>Sisuite-users mailing list
>Sisuite-users@lists.sourceforge.net
>https://lists.sourceforge.net/lists/listinfo/sisuite-users
>
> 
>