Uploading Issue

  1. 2 months ago

    Hello !

    Here is the problem : I am trying to upload an image from a HP Proliant DL380 Gen9 server (12HDD). The server can boot on the PXE, load the initrd.xz image, but throw an error right after that : "could not boot: Error 0x7f048283 (http://ipxe.org/7f048283)"
    I've been to this link, but there was nothing helpful as description for this error.

    Nothing was visible on CloneDeploy's logs, but I found some further informations from tftpd :
    "Jun 16 12:02:03 clonedeploy in.tftpd[19428]: RRQ from 192.168.100.116 filename pxelinux.cfg/01-**-**-**-5f-e5-38.ipxe
    Jun 16 12:02:03 clonedeploy in.tftpd[19428]: sending NAK (1, File not found) to 192.168.100.116
    Jun 16 12:02:03 clonedeploy in.tftpd[19429]: RRQ from 192.168.100.116 filename pxelinux.cfg/01-**-**-**-5f-e5-39.ipxe
    Jun 16 12:02:03 clonedeploy in.tftpd[19429]: sending NAK (1, File not found) to 192.168.100.116"

    The first MAC Address is right, but I don't understand why it tries to reach the MAC Address from the second network interface.
    Anyway, I never had this kind of issue before, even when uploading images from servers using RAID, but despite everything I tried, nothing seems to work.

    Your first screenshot of the default menu does not actually represent current settings. Its just asking what kernel you want to use if you choose to update the boot menu.

    So your task boot menu is still using the x86 kernel. You need to cancel the task. Verify the image profile has the correct kernel set, then start a new task.

  2. clonedeploy

    Jun 16 Administrator

    What kernel is assigned to the image profile?

  3. Ipxe_efi64 - kernel : 4.9.8

  4. clonedeploy

    Jun 16 Administrator

    Change the kernel to a 64bit kernel

  5. Changing the kernel to a 64bit kernel allowed us to reach the PXE Menu (thing we couldn't do, until now, when a task was submitted), but nothing else happens, the uploading doesn't start.

    The computer configuration seems right, but the error log is slightly different now :
    "Jun 16 14:59:03 clonedeploy in.tftpd[19989]: RRQ from 192.168.100.116 filename pxelinux.cfg/default.ipxe
    Jun 16 14:59:03 clonedeploy in.tftpd[19990]: RRQ from 192.168.100.116 filename pxelinux.cfg/01-**-**-**-5f-e5-38.ipxe
    Jun 16 14:59:03 clonedeploy in.tftpd[19994]: RRQ from 192.168.100.116 filename pxelinux.cfg/01-**-**-**-5f-e5-39.ipxe
    Jun 16 14:59:03 clonedeploy in.tftpd[19994]: sending NAK (1, File not found) to 192.168.100.116"

  6. clonedeploy

    Jun 16 Administrator

    If I understand correctly. An upload task is started, when the computer pxe boots instead of starting the task it ends up at the menu where you can select on demand, add computer, etc?

    What happens if you try to load on demand?

  7. Yes, that's it !

    When trying to load on demand, the upload starts. So the problem appears to be with the upload from the computer task.

  8. clonedeploy

    Jun 16 Administrator

    What kernel is currently assigned to the global default menu?

  9. What do you mean by "Global default menu" ? Where do I find it ?

  10. clonedeploy

    Jun 16 Administrator

    Admin->Boot Menu

    That is the boot menu that loads when no task is scheduled or something goes wrong with the task boot menu.

  11. Edited 2 months ago by C_Ugloo

    Thanks for the informations

    Even though we switched the kernel to the x64 version, it still appears as a x86 kernel (see image_kernel-1).
    In the editor, we can see that the kernel used is the x64 (see image_kernel-2).
    But we noticed that in the boot menu of the active task created, the kernel used is still the x86 version (see image_kernel-3).

    Maybe there's a bug keeping the active tasks from gathering the right informations about the used kernel ?

  12. clonedeploy

    Jun 16 Administrator Answer

    Your first screenshot of the default menu does not actually represent current settings. Its just asking what kernel you want to use if you choose to update the boot menu.

    So your task boot menu is still using the x86 kernel. You need to cancel the task. Verify the image profile has the correct kernel set, then start a new task.

  13. Thank you so much for all these informations and explanations !

    Have a nice week-end

 

or Sign Up to reply!