DRBL/CZ Live can't boot PXE-enabled laptop
A partition and disk imaging/cloning program
Brought to you by:
steven_shiau
Menu
▾
▴
I was asked to do this by my work and it's the first time I've ever done it.. I'm in a time crunch and any help provided would be fantastic! I will provide as much info as possible. Scenario: I am going to be cloning four laptops. I am running a test restore on just one laptop, connected to a workstation running the DRBL/Clonezilla live CD. They are directly connected with a crossover cable, and the desktop & laptop's bios has been set to boot to network/PXE.
SERVER: I started DRBL, mounted my external USB as /home/partimg, started up the DRBL modes with the command /opt/drbl/sbin/dcs. I selected clonezilla start, then "All select all the clients", Beginner mode, then "restore disk", "-p reboot", selected an image from my external drive, selected the drive, then selected "multicast" as the mode.
Laptop: I start the laptop. It immediately goes to network boot mode, sits there, waits, then it says "No boot device found. press any key to reboot the machine."
So nothing happens.. I'm not sure what to do. Here's a dump of my console.
user@debian:~$ sudo mount -bind '/media/kics-4 data' /home/partimag
user@debian:~$ sudo /opt/drbl/sbin/dcs
Now the clonezilla mode is: restore-disk
Setting client as clonezilla-restore-disk mode…Searching for images……………………
Setting the TERM as xterm
*****************************************************.
*****************************************************.
Clean all the previous saved config file if they exist…done!
Client OS type when doing Clonezilla job is: nfsroot
start_ocs_service -t multicast_restoredisk -o 2011-10-18-08-kics4-factory-img sda
clonezilla.lock dir: /var/lock/clonezilla
Warning!!! "range" option is found in dhcpd.conf, this is not a good way to operate Clonezilla… It is better to let your DRBL client acquire same IP address by setting MAC address in dhcpd.conf so that you will NOT overwrite the OS of some unknown machines.
Press "Enter" to continue……
Finding the multicast seed ethernet port… done.
Will use ethernet port eth0 for multicast seed in this clonezilla server.
You are using multicast Clonezilla, please make sure:
1. This ethernet port in server is up and connected: eth0
2. If you have more than one (>=2) network switches for the DRBL environment, make sure all the switches are connected to each other, otherwise the multicast packets will not be sent to every clients from the ethernet port mentioned above via all the switches, so the multicast clone might NOT start.
Press "Enter" to continue……
Starting the OCS service for node IP add. = 192.168.100.1
Starting the OCS service for node IP add. = 192.168.1.1
Starting the OCS service for node IP add. = 192.168.120.1
Starting the OCS service for node IP add. = 192.168.205.1
Set the single user password for client *, this will be safer…
/opt/drbl/sbin/drbl-functions: line 675: /tftpboot/nodes/*/etc/inittab: No such file or directory
Setting the PXE clients to DRBL mode with label "Clonezilla: multicast restore 2011-10-18-08-kics4-factory-img to disk sda"…
Turn off all MENU DEFAULT in /tftpboot/nbi_img/pxelinux.cfg/default…
Make "clonezilla" as default label in /tftpboot/nbi_img/pxelinux.cfg/default.
The MENU LABEL is "Clonezilla: multicast restore 2011-10-18-08-kics4-factory-img to disk sda"
Client jobs are logged in '/var/log/clonezilla/clonezilla-jobs.log',
The sfdisk log when running clonezilla is in client /var/log/clonezilla-restore-sfdisk.log
*****************************************************.
You are in clonezilla box mode!
*****************************************************.
*****************************************************.
Now set the client machines to boot from PXE or Etherboot (refer to http://drbl.sourceforge.net for more details). Then boot those clients, so that the template image can be cloned to them!
NOTE! (1) If Etherboot is used on client computers, version 5.4.0 or newer is required! (2) If the cloned OS is MS windows, and it fails to boot with an error message like "Missing Operating System" or "Invalid System Disk", then you can try to (1) change the IDE hard drive settings in the BIOS to use LBA mode instead of AUTO mode. (2) Or you can try to use parameter -t1 when restoring.
This is for all clients, so we remove other host-based PXE config files in /tftpboot/nbi_img/pxelinux.cfg/ and keep /tftpboot/nbi_img/pxelinux.cfg/default only.
Clean all the previous saved PXELINUX config file if they exist…done!
PS. Next time you can run this command directly:
/opt/drbl/sbin/drbl-ocs -b -g auto -e1 auto -e2 -r -x -j2 -p reboot -time-to-wait 1 -l en_US.UTF-8 startdisk multicast_restore 2011-10-18-08-kics4-factory-img sda
This command is also saved as this file name for later use if necessary: /tmp/ocs-2011-10-18-08-kics4-factory-img-2011-10-21-13-27
done!
user@debian:~$ ifup eth0
bash: ifup: command not found
""No boot device found. press any key to reboot the machine."" -> Did you enable PXE (LAN boot) in client machine's BIOS?
Steven.