Hi Allan:
Okay, figured it out -- I guess starting with 2.6.20, all HDs are treated as
'sdX', so if SystemImager thinks that your HD is 'hdX' then you will get the
kernel panic when the client boots.
The workaround for now, is to boot the imaged client into rescue mode,
modify
Installing a new cluster at SARA, I came across the following issue with
systemimager 3.8.0.
We have multiple network interfaces, which are all configured through
DHCP. Now a problem arises when the SystemImager initrd does a
start_network, which is that dhclient is called for _all_ ethernet
You are not alone :)
Here is a patch that I've been using for some time to address this problem. I
just ported it from 3.7.4 to 3.8.0 this morning, but it works in my limited
testing and has worked for some time with 3.7.4. I should note that we are
only using RHEL so I've not tested this on
On Wed, Mar 14, 2007 at 01:21:20AM -0700, Bernard Li wrote:
Hi Allan:
Okay, figured it out -- I guess starting with 2.6.20, all HDs are treated as
'sdX', so if SystemImager thinks that your HD is 'hdX' then you will get the
kernel panic when the client boots.
The workaround for now, is to
