SystemImager 2.0.x and earlier didn't maintain the bootable flag in the partition table. This worked fine in most cases, but in some cases this leads to an unbootable system. To confirm that this is the problem, boot your system from rescue media, and set the bootable flag on your boot partition using cfdisk or another partitioning tool. If this allows your system to boot, then you must upgrade SystemImager and regenerate your autoinstallscript(s). If for some reason you can't upgrade, then check the following:
Are you connected to a switch? Most switches will wait a period of time (usually 30 seconds) after a connected system's interface has come up before transmitting on that port. Newer versions of the autoinstalldiskette bring the ethernet interface up and wait 45 seconds or so before making a DHCP request. It will then wait 35 seconds or so to give the system time to receive an address. You could be using an autoinstalldiskette that does not wait the proper time for your switch and is giving up before it should.
Be sure that you are using the latest version of SystemImager and that you are using the autoinstalldiskette image that comes with that version. Note that the version numbers may not match. See the VERSION file.
Prev | Home | Next |
My client fails with the error: "chroot: cannot execute systemconfigurator: No such file or directory" My autoinstall client booted up and said "dhcp didn't work," but when I do an ifconfig eth0 it has an IP address. | Up | PXE installations work fine for a while, but eventually clients no longer boot the autoinstall kernel. |