Hi.
Not sure where this error is coming from, is it from imaging or when
> you ran si_prepareclient to generate the UYOK kernel/initrd?
The error comes during imaging.
> At any rate, posting more of your log might help -- your current log
> gives me no context to troubleshoot. Also, it would help to provide
>
Here is more of the log:
sleep 0: This is to give your switch (if you're using one) time to
recognize your ethernet card before we try the network.
Tip: You can use <ctrl>+<c> to pass the time (pun intended).
dhclient
Internet Software Consortium DHCP Client 2.0pl5
Copyright 1995, 1996, 1997, 1998, 1999 The Internet Software Consortium.
All rights reserved.
Please contribute if you find this software useful.
For info, please visit http://www.isc.org/dhcp-contrib.html
sit0: unknown hardware address type 776
modprobe: module af_packet not found
modprobe: failed to load module af_packet
sit0: unknown hardware address type 776
Listening on LPF/sit0/<null>
Sending on LPF/sit0/<null>
Listening on LPF/lo/<null>
Sending on LPF/lo/<null>
Listening on LPF/eth2/00:e0:81:49:0a:e6
Sending on LPF/eth2/00:e0:81:49:0a:e6
Listening on LPF/eth1/00:e0:81:49:0b:0b
Sending on LPF/eth1/00:e0:81:49:0b:0b
Listening on LPF/eth0/00:e0:81:49:0b:0a
Sending on LPF/eth0/00:e0:81:49:0b:0a
Sending on Socket/fallback/fallback-net
DHCPDISCOVER on sit0 to 255.255.255.255 port 67 interval 7
DHCPDISCOVER on lo to 255.255.255.255 port 67 interval 5
DHCPDISCOVER on eth2 to 255.255.255.255 port 67 interval 5
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 7
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 5
DHCPOFFER from 192.168.253.32
DHCPDISCOVER on lo to 255.255.255.255 port 67 interval 8
DHCPDISCOVER on eth2 to 255.255.255.255 port 67 interval 9
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 13
DHCPDISCOVER on sit0 to 255.255.255.255 port 67 interval 9
DHCPREQUEST on eth1 to 255.255.255.255 port 67
DHCPACK from 192.168.253.32
Using option-140 as IMAGESERVER: 192.168.253.32
bound to 192.168.253.22 -- renewal in 43200 seconds.
Overriding any DHCP settings with pre-boot settings from kernel append
parameters.
read_kernel_append_parameters
ping_test
Pinging your SystemImager server to ensure we have network connectivity.
PING ATTEMPT 1:
PING 192.168.253.32 (192.168.253.32): 56 data bytes
64 bytes from 192.168.253.32: seq=0 ttl=64 time=1.266 ms
--- 192.168.253.32 ping statistics ---
1 packets transmitted, 1 packets received, 0% packet loss
round-trip min/avg/max = 1.266/1.266/1.266 ms
We have connectivity to your SystemImager server!
Monitoring initialized.
start_syslogd
Starting syslogd...
Successfully started syslogd!
get_boel_binaries_tarball
rsync -av 192.168.253.32::boot/x86_64/standard/boel_binaries.tar.gz
/tmp/boel_binaries
receiving file list ... done
boel_binaries.tar.gz
sent 134 bytes received 7012702 bytes 4675224.00 bytes/sec
total size is 7011717 speedup is 1.00
chown: /lib/modules/2.6.18-92.1.10.el5/weak-updates/gnbd/gnbd.ko: No such
file or directory
chown: /lib/modules/2.6.18-92.1.10.el5/weak-updates/gfs/gfs.ko: No such file
or directory
Killing off running processes.
> the log of when you generate the UYOK initrd -- perhaps something went
> wrong there and it wasn't caught.
How can I produce such log?
> Which version of SystemImager are
> you using?
>
The latest unstable.
By the way, is there any quick way to add another module to BOEL? It sees
that only the serverworks module is missing (sata_svw.ko), so perhaps I can
somehow add it to BOEL?
Regards.
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
sisuite-users mailing list
sisuite-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sisuite-users
