FOG fails to reboot target computer after imaging
-
@george1421
No success with this :
. Is that what you meant ? -
@jeromecandau yes that is the location.
Also thinking if the force doesn’t work then we can also try
acpi=off
Understand this is a unique issues, so we are making a new path here. -
I quickly scanned this thread and I didn’t see where I asked this question. Does this computer have the latest firmware installed? We have seen some pretty bad uefi firmware from this vendor, just saying…
-
@george1421 tried with acpi=off : nothing better… I’m looking after bios updates.
-
@jeromecandau Have you read through the other post yet? Try booting up a couple different Live Linux systems and see if those are able to reboot properly. Trying to gather more information here.
-
@sebastian-roth yes, with clonezilla CD and Gparted CD, last versions, all is OK…
-
@george1421 After flashing new bios version from Lenovo, nothing better else… I do not understand why the reboot is OK with a sata HDD and not with the M.2 one !
-
@jeromecandau I don’t know if I asked you this (sorry I’m in and out of too many threads), on your fog server, navigate to this directory
/var/www/html/fog/service/ipxe
In there, I want you to key in this command.
file bzImage
That will print out the version of the FOS kernel. What version is it? -
@george1421 FOS reboot calls busybox. The current version of busy box I have on FOS on my flash drive is 1.26.2.
-
@jeromecandau said in FOG fails to reboot target computer after imaging:
I do not understand why the reboot is OK with a sata HDD and not with the M.2 one !
This is strange indeed! Can you narrow it down to some specific kernel version within FOG? Have you tried different ones yet?
Can you give Ubuntu Live DVD a try too? As well you might want to try the
reboot=...
kernel parameters. -
@sebastian-roth Hi ! the initial kernel bzimage after fresh install was 4.11.0. I attempted to update from web interface but it was tricky because of rights on directories. Finally, I did it (command line via putty) but the pxe boot resulted in an error. I worked again on it and I succeeded : the current version is now 4.13.4 and all is working great ! I had to copy this new kernel in two places : /var/www/html/fog/service/ipxe and /var/www/fog/service/ipxe to overcome an error during the pxe boot process. That said, we configured another fog server for redundancy purpose and the upgrade from web interface 4.11.0 to 4.13.4 worked perfectly this time …(?) Thanks to every body for the reactivity. The Fog server is our very useful weekly tool to restore our classrooms… Best regards.