I'll give this a shot but when i mkautoinstallcd it asked me which boot image and i picked the one i made from my goldenimage. If i use the standard none of my /dev/* are there. when i pick my boot image, it has the /dev/* to match my harddrives.
Also i had to modify the MAKEDEV portion because it did not work on suse 9. I ram maknod instead for sda etc.
![Inactive hide details for "Bernard Li" <[EMAIL PROTECTED]>](gifNdUkw8PosM.gif){kind=small}
"Bernard Li" <[EMAIL PROTECTED]>
Sent by: [EMAIL PROTECTED] 03/18/2006 09:49 PM
|
|
If you ran si_prepareclient, it should generate an initrd.img which you can use to boot your nodes. si_mkautoinstallcd in 3.6.x just grabs the files from the standard location, so make a backup copy of that and then overwrite it with the kernel/initrd.img which si_prepareclient generate for you. Hopefully that boot pair will be able to get your node booted up correctly.
Cheers,
Bernard
From: [EMAIL PROTECTED] on behalf of Scott Lepech
Sent: Sat 18/03/2006 16:42
To: [email protected]
Subject: [Sisuite-users] sit0: unknown hardware address type 776 on boot cd load
I'm running SLES 9 on dell hardware. I'm using systemimager 3.6.3. I've prepared the client and ran getimage etc, etc,. Now i have my boot cd on the box i would like to clone. I picked my os image as the basis for the boot kernel and ramdisk.
Everything appears to load fine from the boot cd but then i get this message when the host tries to get an IP via DHCP. I've verified that DHCP is up...
sit0: unknown hardware address type 776
socket: Address family not supported by protocol
Make sure to set CONFIG_PACKET=y and CONFIG_FILTER=y in your kernel config
I don't have sit0 on my original os. Any ideas on how to fix this?
Thanks
