Title: Re: [Sisuite-users] Cloned clients won't boot from harddisk (Redhat RHEL 4.0)
Hey Ole:
I'm curious why you say that
/boot/grub/stage1 is corrupted because it is 512 bytes. I've looked at a
few Red Hat installations and they're all 512 bytes.
I'm still
uite-users] Cloned clients won't boot from harddisk (Redhat
RHEL 4.0)
> Yes, that is my conclution so far with RHEL 4.0 as well as Centos 4.0
> golden clients installed onto a cleanly wiped harddisk and
> then cloned onto another client with a similarly wiped harddisk,
> and using Sys
> Yes, that is my conclution so far with RHEL 4.0 as well as Centos 4.0
> golden clients installed onto a cleanly wiped harddisk and
> then cloned onto another client with a similarly wiped harddisk,
> and using Systemimager 3.5.2.
Okay cool - I'll give it a shot tonight and report back.
> Wiping
Bernard Li wrote:
I appreciate your help ! After a lot of experimentation, and working
interactively on the cloned client at the end of the SI installation,
I'm now firmly convinced that Systemimager v3.4.1 as delivered by the
RPM packages on http://sourceforge.net/projects/systemimager/
*does n
Hey Ole:
> I appreciate your help ! After a lot of experimentation, and working
> interactively on the cloned client at the end of the SI installation,
> I'm now firmly convinced that Systemimager v3.4.1 as delivered by the
> RPM packages on http://sourceforge.net/projects/systemimager/
> *does
Bernard Li wrote:
I'm now looking into this issue more closely and I was wondering if you
can post your /boot/grub/device.map (from the imaged node after running
SystemConfigurator)?
I appreciate your help ! After a lot of experimentation, and working
interactively on the cloned client at the
Title: Re: [Sisuite-users] Cloned clients won't boot from harddisk (Redhat RHEL 4.0)
Hey Ole:
I'm now looking into this
issue more closely and I was wondering if you can post your
/boot/grub/device.map (from the imaged node after running
SystemConfigurator)?
Thanks,
Bern
; Of Bernard Li
> Sent: Monday, May 30, 2005 10:02
> To: Ole Holm Nielsen
> Cc: sisuite-users@lists.sourceforge.net
> Subject: RE: [Sisuite-users] Cloned clients won't boot from
> harddisk (Redhat RHEL 4.0)
>
> Hi Ole:
>
> I would try using lilo and see if it g
ists.sourceforge.net
> Subject: Re: [Sisuite-users] Cloned clients won't boot from
> harddisk (Redhat RHEL 4.0)
>
> Hi Bernard,
>
> That's a nice observation, since FC3 and RHEL 4.0 ought to be rather
> similar ! When SI 3.4.1 installs my RHEL 4.0 client, the
Hi Bernard,
That's a nice observation, since FC3 and RHEL 4.0 ought to be rather
similar ! When SI 3.4.1 installs my RHEL 4.0 client, the master
script executes "systemconfigurator" which gives this error message
twice:
df: Warning: Cannot read table of mounted filesystems
This is caused by /
Title: Re: [Sisuite-users] Cloned clients won't boot from harddisk (Redhat RHEL 4.0)
Hi Ole:
RHEL4 doesn't use devfs, it
uses udev, however, using this method, I was able to use SystemImager with
Fedora Core 3, which uses udev.
Perhaps you can post the
error messages assoc
"Bernard Li" <[EMAIL PROTECTED]> wrote:
Do you use SystemConfigurator along side SystemImager? One thing you can try
is modify
autoinstallscript.conf and add:
right before the config block ends (right before ).
Then re-run mkautoinstallscript for the image and try to re-image a new cli
Title: [Sisuite-users] Cloned clients won't boot from harddisk (Redhat RHEL 4.0)
Hi Ole:
Do you use SystemConfigurator
along side SystemImager? One thing you can try is modify
autoinstallscript.conf and add:
right before the config block ends (right before
).
Then re-run
mkautoins
13 matches
Mail list logo
