@Sebastian-Roth Your build instructions work! I am the proud owner of a freshly built bzImage! Thank you.

Setup is 16124 bytes (padded to 16384 bytes).
System is 8169 kB
CRC 8c40e932
Kernel: arch/x86/boot/bzImage is ready  (#1)
mike@VLIN-018987 11:57:46 0 :~/fos/fos[master] $ find . -name bzImage
./kernelsourcex64/arch/x86/boot/bzImage
./kernelsourcex64/arch/x86_64/boot/bzImage
./dist/bzImage
mike@VLIN-018987 11:58:18 0 :~/fos/fos[master] $

@Sebastian-Roth I completed the changes to the kernel build as you suggested. I copied over the new bzImage file. I booted the machine over iPXE and chose “Debug Mode”. I am able to verify that the newly compiled kernel is active as the print statement that was defined is being printed to the screen. Unfortunately, that is the only output I receive. The screen just hangs with the print statement displayed and never progresses past that statement. The station Model is a Lenovo ThinkPad L380, here is some information from Lenovo on the model. How can I further troubleshoot this issue? Thank you!

@Sebastian-Roth Your build instructions work! I am the proud owner of a freshly built bzImage! Thank you.

Setup is 16124 bytes (padded to 16384 bytes).
System is 8169 kB
CRC 8c40e932
Kernel: arch/x86/boot/bzImage is ready  (#1)
mike@VLIN-018987 11:57:46 0 :~/fos/fos[master] $ find . -name bzImage
./kernelsourcex64/arch/x86/boot/bzImage
./kernelsourcex64/arch/x86_64/boot/bzImage
./dist/bzImage
mike@VLIN-018987 11:58:18 0 :~/fos/fos[master] $

@george1421 Thanks so much for the bootable FOS image. I was able to boot to the debug option on the FOS stick and get an interactive shell in the FOS environment. Networking is working too. Which makes me wonder why the bootable USB is working on this drive but when I choose the debug option on the same model after PXE booting I see bzimage and init.xz download and then I just get a black screen. The only difference I noticed between the two environments is that my FOG installation lists the bzimage kernel as 4.19.1. When I run

uname -a

in the debug environment from your USB boot media it lists kernel version as 4.19.6. Do you have a recommendation on how I can further troubleshoot this issue? Are there changes to the kernel between 4.19.1 and 4.19.6 that contain items that might be making the difference for this host?
Thanks again for the bootable FOS image and all your help!

@Sebastian-Roth The issue with the link was by default my connection is not allowing traffic to Taiwan. I made an exception and was able to download from the link in the build process. The build is running now. Thank you.

@george1421 I think I would like to do both. If I could add the init.xz as a pxe boot option to boot to a live FOS install that would be pretty sweet. I would also like to make a bootable FOS USB stick for debug as well. If you already have a valid img for use with RUFUS I will happily take a download of that. I hope I am understanding the questions correctly. My current issue is related to video going black when I boot a Lenovo L380 but I am interested in the tools for various uses going forward. Thank you for your help.

@Sebastian-Roth Build appears to be running still but CPU has dropped off. When I look at the end of the log file the build seems to be stalled and showing the following output.

/bin/bash ../libtool --quiet --mode=install ../install-sh -o root -g root -m 755 xfs_db /usr/sbin
../install-sh -o root -g root -m 755 xfs_admin.sh /usr/sbin/xfs_admin
../install-sh -o root -g root -m 755 xfs_ncheck.sh /usr/sbin/xfs_ncheck
../install-sh -o root -g root -m 755 xfs_metadump.sh /usr/sbin/xfs_metadump
./install-sh -o root -g root -m 755 -d /usr/share/doc/xfsprogs
./install-sh -o root -g root -m 644 README /usr/share/doc/xfsprogs
>>> partclone 0.2.89 Downloading
--2019-03-08 09:46:43--  http://partclone.nchc.org.tw/download/stable/old/0.2.89/partclone_0.2.89.orig.tar.gz
Resolving partclone.nchc.org.tw (partclone.nchc.org.tw)... 140.110.240.54
Connecting to partclone.nchc.org.tw (partclone.nchc.org.tw)|140.110.240.54|:80... failed: Connection timed out.
Retrying.

--2019-03-08 09:48:53--  (try: 2)  http://partclone.nchc.org.tw/download/stable/old/0.2.89/partclone_0.2.89.orig.tar.gz
Connecting to partclone.nchc.org.tw (partclone.nchc.org.tw)|140.110.240.54|:80... failed: Connection timed out.
Retrying.

--2019-03-08 09:51:05--  (try: 3)  http://partclone.nchc.org.tw/download/stable/old/0.2.89/partclone_0.2.89.orig.tar.gz
Connecting to partclone.nchc.org.tw (partclone.nchc.org.tw)|140.110.240.54|:80... 

Thank you.

@Sebastian-Roth I omitted all the docker stuff and started the build on my Ubuntu station. It is off and running. I will check back on it in a number of hours. I am looking forward to testing it out. I will post back once the build is complete and I get the opportunity to try it. Thank you for your help.

I am trying to build a FOS USB boot disk for troubleshooting an issue I am having with a Lenovo L380. I am following the information I found at https://github.com/FOGProject/fos When I get to the build everything command and I run

docker run -v /path/to/fos/repo:/home/builder/fos:Z -u builder -it fogproject/fos-builder /home/builder/fos/build.sh -n

I get the error

Checking packages needed for building
No buildroot version, set environment BUILDROOT_VERSION

I am new to docker and also new to Buildroot. I know how to set an environment variable on my Linux station but not clear on what value to use for the variable. Any help is appreciated.

Thank you.

@george1421 I replicated my images using rsync and verified that all images are in both locations. I also have a backup of my images off of both of the nodes. I went in and I created a new Storage Group. I associated the Storage Node that is not the Master Server with the new Storage Group. I then associated a number of my images with that Storage Group. My goal is to have some images only reside on the node in the new Storage Group and some only reside on the other Storage Group. I set both servers to be the Master Node for their Storage Group. Based on the warning I read about setting a server to the Master Node I half-way expected for any images that were not associated with that Storage Group to be purged from the Master Node but that didn’t seem to happen, which is fine. Is it now safe to go back and purge images from servers via cli if they reside in an image store on a node that is not in the Storage Group that is associated with that image? Thank you!

@george1421 Got it. I am on a systemd based system. I am still getting used to systemd. Why would services that are listed in systemd not be listed under the output of the services command (not really asking, I can Google that on my own)? Just venting as I continue to relearn all that I thought I knew about Linux. Thanks again! Don’t think I ever would have got this sorted out without your help.