@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.
Latest posts made by jeromecandau
-
RE: FOG fails to reboot target computer after imaging
-
RE: FOG fails to reboot target computer after imaging
@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 !
-
RE: FOG fails to reboot target computer after imaging
@sebastian-roth yes, with clonezilla CD and Gparted CD, last versions, all is OK…
-
RE: FOG fails to reboot target computer after imaging
@george1421 tried with acpi=off : nothing better… I’m looking after bios updates.
-
RE: FOG fails to reboot target computer after imaging
@george1421
No success with this :
. Is that what you meant ?
-
RE: FOG fails to reboot target computer after imaging
@sebastian-roth
the SSD M.2 drive is connected to slot 9…
-
RE: FOG fails to reboot target computer after imaging
@sebastian-roth
Hi ! These desktop are Thinkcentre M710t from Lenovo with 16GB RAM (DDR4-2400 (1200 MHz) - Part Number M378A1K43BB2-CRC).
The user manual is avalaible at :
https://content.etilize.com/User-Manual/1038658110.pdfMotherboard : Manufacturer LENOVO Model 3102 (U3E1)
Version SDK0L22692 WIN 3306006364178
CPU Intel Core i3 6100
Cores 2, Threads 4, Name Intel Core i3 6100
Code Name Skylake, Package Socket 1151 LGA, Technology 14nm
Specification Intel Core i3-6100 CPU @ 3.70GHzDISK : SSD m.2
NVMe INTEL SSDPEKKF25 SCSI Disk Device
Interface Unknown Capacity 238 GB
This models come from central administration and will be numerous in high schools. Il would be great that we can use fog server as we did for a long time with no trouble… Anywhere, great thanks for developping a such usefull imaging server.
-
RE: FOG fails to reboot target computer after imaging
Yes, and I wonder why the Fog main OS (bzimage+init.xz) isn’t able to reboot the PC’s as the first iPXE boot menu is… Isn’t known the right reboot command by Fog since he can reboot ?
-
FOG fails to reboot target computer after imaging
Hi everybody,
we work in a high school in France and we also have somme difficulties with the new PC’s we installed recently. They are Lenovo Thincentre M710t with Windows7Pro64 installed on a m.2 SSD drives. We installed a new Fog server (the old one was a 1.2) : 1.4.4 on a debian 9-stretch server to deploy over about 40 hosts. This fog server is also the DHCP and TFTP server on an isolated network. We can make inventories, upload and download images (single and multicast) but the Fog server can’t reboot the hosts after these actions. The PC’s fall in a “dreaming state” : led power on, fan running but no boot for ever. The issue is the same as we boot in LEGACY MODE or in UEFI mode. The only way is to manually power down and then reboot after what the only fog service we installed (renaming hosts) works perfectly. We tried all the “Host Bios Exit Type” but without any success ! We also tried some of the advices in this post (scanfor, refind, …) with no results.
The only time when the boot occurs is in case whe just make a network boot until the fog menu appears and then select boot to hard drive (first item) (or do nothing : then the boot occurs after timeout). We tried replacing the m.2 SSD with more “classical” drives HDD on SATA ports : the reboot by the fog server occurs normally and all is fine. So we suppose that the fog OS (bzimage, init.xz ???) is not able to send comprehensive command to boot the M.2 SSD drive but is OK with SATA drives… Is there anyone encountering a similar issue ? In this case, have a solution been tuned ? Thanks… J CANDAU (apologies for my nearly bad english)