Menu

Cannot PXE boot to Clonezilla when imaging the same machine twice within a set time frame

Help
2015-04-21
2015-05-09
  • ThatClickingNoise

    Bit of a perplexing situation. We have a system setup (typical drbl/clonezilla setup) that we boot systems to and everything in the process is working more or less without incident. The primary problem that's occurring is that, once a system is imaged, it will not boot to Clonezilla again until after a significant period of time has passed (we don't have the exact time, but it's in the order of a few days). At first I thought it might have been an oddball DHCP lease time or something along those lines but that's set to 300 seconds currently. The system does see the server and will get the DRBL loader, but is defaulting to the local OS, and intervening on the bootup only gives you the option of local OS and the server itself. Everything else is working fine while this occurs, it just simply won't go back to clonezilla for that system, for several days. I'm a bit stumped as to to what I should be looking at that would cause this behavior to begin troubleshooting this. Possibly something with how it's handling mac addresses but we're not going off a preset mac list as the systems hitting the server are always unique.

     
  • Steven Shiau

    Steven Shiau - 2015-05-09

    Yes, very weird.
    You can enable the verbose mode of tftpd-hpa service, in Ubuntu/Debian, it's like:
    TFTP_OPTIONS="-v -v -v--secure --ipv4"
    in
    /etc/default/tftpd-hpa
    then restart tftp-hpa service.
    Boot your client, and you should be able to check your system logs about which files client machine is requesting.

    Steven.

     

Log in to post a comment.

Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.