I had an issue with some hosts not releasing the cue on the dashboard and also was noticing some lag on the different pages on the FOG dash. I got this link Database Maintenance Commands from @Sebastian-Roth and it helps out with the Dashboard. Not sure if this would help with your issue but it’s worth a try.
Hope this helps.
@pascald73 I followed the guide on the FOG wiki and I was able to get it going.
Some screenshots of the error would help us to get an idea of how to troubleshoot.
Hope the link helps.
@george1421 Thanks for the information on this. Also, what is the process for updating the kernel? I know it is on the GUI side of FOG but not sure if the is a specific process to avoid any unexpected errors. I have 2 storage servers and not sure if this would affect the connection or settings.
Another thing is that I have already set up Windows 10 on this Dell 3410 laptop using the RAID settings on the BIOS. So how can I fix Windows 10 since when changing to AHCI I get a blue screen?
Any tips or suggestions would be greatly appreciated.
Thanks
I get an error when trying to capture an image for a Dell Latitude 3410. So I performed a compatibility test on it and it failed on the hard drive.
It suggested to update the kernel and use the valuable information below to post on the forums
02:00.0 Ethernet controller [0200]: Realtek Semiconductor Co. Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 15)
FOG ver Version 1.5.9-RC2
OS Ubuntu Server 18.4
1 FOG master, 2 FOG storage servers
If I switch on the BIOS to AHCI it works but if I leave it on the default BIOS setting with RAID I get errors.
Thanks in advance for your help.
@sebastian-roth So if I have an image that is replicated on the storage servers deleting the image from the fog master server by using “Option 2” (Clicking on the Image and then delete) should delete the image definition and data file on the rest of the storage servers?
If I have an image that is replicated and I used the delete option under the image list view (Option 1) will I then have to manually delete the image data file from each storage server it is on?
Thanks for your help.
@george1421 The command work for me. Thanks for the help.
@fognerval is the BIOS on UEFI or Legacy boot? You might need to change your files on the DHCP server. Also, are both the Device and DHCP servers on the same network? If not, then you might need some IP helper configuration or proxy. More information on setup is needed I think to figure it out.
I started this to have some references for future use. I was not aware of the process on how to delete images and I intuitively used the FOG delete options on the image list view. This did not delete the image data file so I reached out and posted on the forum for a dashboard issue but included the storage issue along with it and by asking for one I got help for both (Thanks to FOG community and to @Sebastian-Roth)
So @Sebastian-Roth provided the steps below:
Steps for Option 1:
How to quickly delete definitions but NOT data:
Web Interface -> Image Management -> List All Images -> Click the checkboxes to the left of the image definitions -> Click “Delete All Selected Images?” at bottom of page -> Click “Are you sure you wish to delete these items?” -> Authenticate to confirm
Steps for Option 2:
How to delete a single image definition AND it’s data too:
Web Interface -> Image Management -> List All Images -> Click the name of the image you want to delete -> Click “Delete” tab at the top -> Check the box labeled “Delete file data” -> Click “Remove” -> Authenticate to confirm
Steps if Option 1 was done but wanted Option 2:
If you want to delete image data after you deleted the image definition (but not the data) through the web interface you can manually delete the folder /images/IMAGENAME/ on your FOG server. Make sure you delete the correct folder as there is no backup of the image data if you purge the wrong one.
Here is the question for this topic:
If I have replication on my images does Option 2 deletes them from the rest of the storage servers?
If I have replication on my images and I did Option 1 do I then have to manually delete the image folder from all the other storage servers?
Thanks for your help in advance.
@sebastian-roth The database maintenance commands on the wiki link you provided worked for me on the dashboard issue.
Thank you for your help.
@sebastian-roth I think I did exactly what you explained. I did not check on the process of deleting images from FOG. My mistake, now I would like to delete the image from the server but what is the path to the image folder?
Thanks for the help
I do not see the updates for Storage Group Activity and Storage Node Disk Usage on the FOG Dashboard. I do not have any sessions Queued but I keep seeing 12 Queued on the storage group activity section. On the storage node disk usage section, I do not see the recent space increase due to an image I deleted.
I have restarted all the server storage nodes and master node and still keep getting the same stats shown on the FOG dashboard.
Currently running FOG 1.5.9-RC2 on Ubuntu Server 18.04.3 LTS (GNU/Linux 4.15.0-128-generic x86_64)
All other sections System Overview, Imaging Over the last 30 days, and Bandwidth are displaying correctly.
Any help is greatly appreciated.
Thanks in advance.
@sebastian-roth FOG ver 1.5.9-RC2 and we do not use PowerShell modules
Thanks for the reply
I usually get this when there is a system pending or currently waiting for an image. I then would go to the task section and cancel all tasks to release the queued computers. I’m not sure why all of a sudden this does not work. I have also tried restarting all of the FOG servers in an effort to clear the queued computers. I can still image but since I have a limit of 30 and 12 are queued I can only image 18.
How do I release the queued systems?
Any help is greatly appreciated.
Thanks
@george1421 Sounds like something that will be okay with the rest of the IT team here. So then how to start on the ipxe menu stuff for FOG is the next step. Any ideas on this
Thanks for the reply
Hello,
I would like to have both FOG and MDT/WDS on the same network but don’t know how to start. Below is what I have currently set up in my environment.
Network:
Cisco router
Multicast is enabled
VLAN 10 interface:
ip address 10.253.0.1 255.255.252.0
ip helper-address 10.254.0.110 [Windows DHCP]
ip helper-address 10.254.0.160 [PC management server WOL]
ip helper-address 10.254.0.250 [FOG main server I change it to .155 when I need MDT/WDS]
no ip redirects
no ip unreachables
ip directed-broadcast 101
ip pim sparse-dense-mode
Windows DHCP information:
FOG info:
Installed on Ubuntu server 18.04.3 LTS bionic
You are currently running version: 1.5.9-RC2
Latest stable version is 1.5.9
Latest dev-branch version is 1.5.9.49
Latest alpha-branch version is 1.6.0-alpha.1049
The goal is to have both running at the same time without having to make changes to DHCP or on the VLAN ip-helper address.
Any help on this would be greatly appreciated.
Thanks
I had the same issue. I made some changes to the wait time for multicast sessions under the settings menu for FOG. I think the default is 10 min so I dropped it down to 2 just to give me enough time to set up the other systems on the session. This wait time setting will take place if you don’t join the computers to the multicast. So it will start the session before you get the rest of the PCs joined. Use with caution.
FOG configuration>FOG settings>Multicast Settings>UDPCAST MAXWAIT
Hope this helps
Thanks, @george1421 I was able to get it going. Did not need to capture since I have a Windows image that I use to set up the image template for the CPU. Thanks for the info on this @Tom-Elliott I did have to change to AHCI in order for it to work. The secure boot and PXE should be standard now for FOG deployments. I do appreciate the reminders for BIOS setups cuz sometimes they do get overlooked no matter how much experience one might have using FOG.
Hopefully, in the future, the FOG team will develop something to remedy this issue with RAID BIOS configs.
Thanks for the help and quick replies.
Thanks for the quick reply I will try it and post my results.
I got an error on a dell 3310 latitude laptop.
Init Version: 20200906
Cannot find disk on system (getHardDisk)
Args Passed:
Kernel variables and settings:
bzImage loglevel=4 initrd=init.xz root=/dev/ram0 rw ramdisk_size275000 web=http://192.168.1.250/fog/ consoleblank=0 rootfstype=ext4 storage=192.168.1.250:/images/ storageip=192.168.1.250 nvme_core.default_ps_max_latency_us=0 loglevel=4 mode=manreg
have been using fog on several laptops different brands and have not had this error.
Any ideas on where to start fixing?
Thanks in advance
@Sebastian-Roth Thanks for the TIP. I did make the change on the storage nodes as well. The time on the reports is now correct.
Thanks for the reply.