@engineerfranko said in Boot from Hard Disk from Fog Server PXE doesn’t work:
Is this something you can configure via the web gui?
Well you can switch between the chainloading options you mentioned, like SANBOOT and so on.
On top of that some options have special settings like REFIND can be tuned in a config file /var/www/html/fog/service/ipxe/refind.conf.
Once again I may ask if you have legacy BIOS machines or UEFI? There are two different settings in the web UI for those?
@pastorn said in help with multi-cast deploy:
the DHCP is on windows server 2022
Can you please post pictures of the settings?
@Lementchow said in Can not find hard disk(s) (getHardDisk):
No, It’s still can not get harddisk, in fog deploy. Something strange.
Ahh, now I see. Somehow got the PE part wrong in your earlier posts.
Have you updated the FOS kernel as suggested? Please boot into a debug session and run uname -a to make sure it’s running the 6.x kernel.
@Numa09 said in Stuck on "running post init scripts:
They are in the same network 172.16.0.0/27
According to what I know about subnet masks this is a pretty narrow one separating the server from the clients and making it necessary to have a router/gateway in between. You need to look at those to see if network traffic is being filtered.
@Lementchow So everything is working now as it should?
@Numa09 I am not sure how this is related to post init scripts. Can you please give some more context and also post this contents of the scripts if you have those in place?
The error on mount points to an issue with NFS not being possible to connect in your network. Are the client machine and the FOG server on the same subnet? Can’t be sure from the IPs seen in the screenshot because we are missing the subnet mask used.
@glequeau Which version of FOG do you use?
I ask because there was a bug in that part for quite some time but we fixed that in 1.5.10. See details here: https://github.com/FOGProject/fogproject/issues/371
@danieln Thanks for reporting. This is a known issue and will be fixed when someone finds enough time to do it right. See here: https://forums.fogproject.org/topic/16796/log-viewer-blank
@mronh I had a bit of time today and started looking at it. This is a bigger issue, code security involved and I wasn’t able to fix this in the time given.
I have got it on my list of things to fix when I find some more time.
@engineerfranko Welcome to the forums.
However the automated boot to hard disk doesn’t appear to work, it just loops.
The so called chainloading process depends on hardware, BIOS mode (legacy or UEFI) and OS installed on disk and can be a it tricky. From what you wrote I get you have Windows installed, right? Is this machine legacy BIOS or UEFI? Have you tried other hardware to see if those can chainload into Windows?
so added it to host primary disk, alas no joy.
This setting does not play a role when chainloading the OS from disk. It’s only important when you have several drives in a machine and want to image/deploy the secondary one
@lebrun78 said in FOG 1.5.10 officially released:
The installation instructions in https://news.fogproject.org/fog-1-5-10-officially-released/ link seams not good.
The link changed over time as we are working on the docs as well. This should be fixed now.
@JJ-Fullmer Will the links change again in the future you reckon?
@smazzola We need more information to be able to help. Please provide what has been asked or we’ll close this topic.
@plegrand In the first months of 2023 I did some testing with Debian 12 Alpha. Installed fine if I remember correctly. Looks like @Lee-Rowlett does confirm.
Though as always I suggest you take a backup (snapshot) before going ahead and then give it a go. You have good chances of going without much of an issue.
@Lee-Rowlett said:
only issues so far i’ve come across is with the ldap plugin
Would you be so kind and open an issue report about this on github? This is not a specific issue with Debian 12 but probably due to a newer PHP version as you said.
@JJ-Fullmer Pretty sure you have used SSL with the FogAPI modules?!
@Tom-Elliott said in Isolated Network Setup (Stuck in Start PXE over IPv4):
/etc/dhcpd.conf
I might be wrong here but from the top of my head I wouldn’t think that’s the right config file. Guess it is /etc/dhcp/dhcpd.conf though.
@pastorn That screen you posted a picture of is not pointing to a multicast issue, well not yet. This is a PXE booting problem which you will see on unicast deploys just as well. What kind of DHCP server do you use?
@alexamore90 Definitely look into using multicast if you want to image many in little time!!
@Lementchow I suggest you update your kernels to the latest available 6.1.x and try again: https://github.com/FOGProject/fos/releases/tag/20230331
@Lementchow Which kernel do you use (command uname -a in FOS debug session)?