Hi John:
Which version of SystemImager
are you using?
Once you're back to the
console during imaging, can you do a "dmesg | grep eth0" and see if anything
shows up?
I have a feeling perhaps your
network adapter was not recognized, but the error logs you have posted is not
sufficient to determine that.
Cheers,
Bernard
From: [EMAIL PROTECTED] on behalf of [EMAIL PROTECTED]
Sent: Fri 14/04/2006 06:21
To: [email protected]
Subject: [Sisuite-users] floppy boot problem
Hi,
I'm running into the problem described in the attached e-mail while attempting to install a Dell2850. I didn't see anything in the archives indicating a fix. Any ideas on how to resolve this?
SIOCSIFADDR: no such device
NETMASK: no such device
BRDADDR: no such device
-John
List: sisuite-users
Subject: [Sisuite-users] floppy boot problem
From: "Irvine, Doug - Resources - ICT Services"
Date: 2004-07-13 15:50:52
Message-ID: EA43A8949BD2D411ACFF00D0B706E923042A3D63 () chexch2 ! oxfordshire ! gov ! uk
[Download message RAW]
[Attachment #2 (multipart/alternative)]
Hi,
I hope you can help me. I am trying to use SystemImager to provide a backup
solution for a network of 13 Redhat ES 2.1 servers.
All the servers are HP DL360-G3
I have built an image server and taken an image from one of the other
servers.
I built a boot floppy with mkautoinstalldiskette and configured the
local.cfg as follows:
----------------------------------------------------------------------------
--
HOSTNAME=client
DOMAINNAME=oxfordshire.gov.uk
DEVICE=eth0
IPADDR=xx.yy.zz.8
NETWORK=xx.yy.zz.0
NETMASK=255.255.254.0
BROADCAST=xx.yy.zz.255
GATEWAY=xx.yy.zz.254
GATEWAYDEV=eth0
IMAGESERVER=xx.yy.zz.12
IMAGENAME=client
----------------------------------------------------------------------------
-
When I try to boot the server, the kernel loads but I'm unable to start the
rebuild as I get the following errors:
SIOCSIFADDR: no such device
NETMASK: no such device
BRDADDR: no such device
The interesting part is once the boot sequence has stopped I can set an ip
address on eth0 with:
ifconfig eth0 xx.yy.zz.8
and then ping the image server.
I am thinking this may have something to do with the gigabyte interface not
being ready from the module load. The next thing I'm going to try is adding:
ETHER_SLEEP=35
to the local.cfg file. Does anybody have any ideas or experiences with this
problem?
Thanks for your help.
Regards,
Doug Irvine
Oxfordshire County Council
Doug Irvine
Websphere Support
01865 815888
Mobile 0777 616 3426
