Title: PXE and CD issues
Hi Brad:
 
When replying, please hit "reply-all" so that the mail gets sent to the oscar-devel mailing-list and is archived, thanks!
 
Regarding your first issue, does node02 have the same hardware as your headnode (image server)?  Also, are you saying that that node imaged correctly but when it reboots it kernel panicked?  Can you boot that node into rescue mode and post the contents of /boot/grub/menu.lst?
 
Does node03 have different network card than node02?
 
Cheers,
 
Bernard


From: Brad Aisa [mailto:[EMAIL PROTECTED]
Sent: Sun 18/06/2006 02:25
To: oscar users; oscar devel
Cc: Bernard Li
Subject: PXE and CD issues

Fedora Core 5/Oscar 5

PXE Issues

node02: 172.16.0.2
using Use Your Own Kernel
PXE boots, loads image etc.
kernel panic at following step:

RAMDISK: Compressed image found at block 0
UDF-fs: No partition found (1)
Kernel panic - not syncing: VFS Unable to mount root fs on unknown-block(1,0)


node03: 172.16.0.3
gets the address from DHCP
TFTP server search just loops, never finds it

I can reliably reboot node02 and repeat the failed install, and just as reliably reboot node03, it gets its address, and loops forever looking for TFTP (node02 and node03 were previously created in the wizard)

Why can node02 fetch the kernel, but node03 cannot? I reiterate: node03 *does* get its IP address from DHCP, so all the connectivity is in place.


CD Issues
I though I would also try the CD boot method.

UYOK
gets to the rsync point, transcript:

get_boel_binaries_tarball
rsync -av 172.16.0.1:/boot/i386/standar/boel_binaries.tar.gz /tmp/boel_binaries
@ERROR: Unknown module 'boot'
rsync error: error startingclient-server prootocol

then it spits out the sysimager error message

Gee, this is really getting stressful!!! I hope I can get this working!!!

Brad Aisabaisa at brad-aisa dot com


_______________________________________________
Oscar-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/oscar-devel

Reply via email to