Posts made by Sebastian Roth

@AlkarimJ Which version of FOG is this? Login to the web UI and check at the bottom right corner (or maybe left?).

@Fog_Newb said in Backing up USB drive - blockdev --getsize64 then what?:

Have there been any updates in dealing with dual NVMe drives that are the same size?

Yes, you can use disk serial as well.

@admiralshaw @LLamaPie This sounds very much like the issue someone reported just a few weeks ago. Happens when you have more than two network interfaces in your device. Can’t find the topic right now.

What do you think @JJ-Fullmer ? Would you remember where we discussed this?

@Lemeunier Have you read through some of the other topics found in the forums? In a fair amount of cases people had to use domain\username in the username field but also specific the domain in it’s own field to make it work. I think no one got ever worked out why this is the case because the fog-client should actually do this by itself.

@Lemeunier The error code 1326 is specific to Microsoft domain joining, meaning “username and/or password are incorrect”. Double check you are using the correct credentials. Pretty sure this is not an issue with FOG being installed on different versions of Debian.

Search the forums for “1326” and you will find dozens of posts on this problem.

@Warsonix Great you figured out how to switch to a different iPXE binary. You are welcome. Feel free to ask whatever issue you run into in a new topic.

@Fog_Newb To get a list of the so called block devices you can use the command lsblk. If you are not sure which one is which you can get the partition table and also disk name/vendor by running fdisk -l /dev/... for each of the devices.

@Can-eh-dian11 said in Kernel Panic - Unable to mount root fs on unknown-block:

As suggested I gradually brought the FOG server and the clients closer together until eventually they were on the same switch/subnet and I’m still encountering the error.

Good work! Although we have not found the root cause of this we did rule out a very important factor.

We’ve also done some more deployments and have found that the issue isn’t as limited to a specific hardware vendor as we initially thought. There have been some recent Dell laptops where we are starting to see this pop up.

So from what we know so far I would guess this is a driver issue in iPXE. Do all the devices showing this issue have the same or a similar network chip (same vendor)?

Try using a different iPXE binary. Which one do you currently use? Are the devices set to UEFI or legacy BIOS mode?

@Warsonix Try using a different iPXE binary. The default for UEFI machines is snp.efi and you might want to try ipxe.efi or snponly.efi.

@cidy-long-0 You can setup FOG with firewall but really need to know what you are doing. E.g. kernel updates through the web UI and image capture can be a problem if you get the firewall rules wrong.

@hammerc807 For me github.com resolves to a totally different subnet. Could either be fine or a pointer to your provider doing transparent proxying?!

Try openssl s_client -showcerts -connect github.com:443 -server github.com to show the whole certificate chain.

@Fog_Newb Well, what’s the output of blockdev --getsize64 ... for the external drive?

Not sure I understand your question? You’d simply put that number into the Host Primary Disk field.

@terrigan You could try booting this particular model via USB key to get around the issue.

https://forums.fogproject.org/topic/7727/building-usb-booting-fos-image/21

Let us know if you need further information on this.

@cidy-long-0 said in Fog service is not accessible after reboot:

The site could be temporarily unavailable or too busy. Try again in a few moments.

This means the webserver is not running. Check with systemctl status httpd. Or maybe it’s a firewall that only was deactivated temporarily when installing FOG?

@aviel1540 Sure you are welcome to build your own UI. The best of documentation we have you can find here: https://news.fogproject.org/simplified-api-documentation/

@mronh Thanks for reporting. Probably a bug. Will take a look and get back to you.

@hummela Not sure if spacing in names could cause this. I have not had much time lately and couldn’t find the time to look into this. But it’s on the list. Will get back to you.

@cidy-long-0 In general FOG can be used for what you are trying to do BUT it’s not made for this. Personally I think you are way better of getting this done with Clonezilla or other imaging tools instead of making all the effort to get FOG up an running in your network. FOG heavily relies on PXE booting in the standard setup and that might even be a hassle with some server hardware.

Both FOG and Clonezilla use the same base - partclone. So technically you don’t miss out when you stick to Clonezilla.

@Can-eh-dian11 Are your clients PXE booting across subnets/routers or maybe even a VPN tunnel? If they do I may ask you to bring a machine to the local network to PXE boot and deploy there. See if you get the same error again. If it’s not across subnets I still suggest you try to move a client as close to the FOG server as possible (same switch) and try to reproduce the issue again.

@mardonis200 Please try other physical machines. As well increase the kernel log level to 7 in the FOG settings (web UI).