@Tom-Elliott I am working on newer inits with the updated e2fsck
package to resolve this issue.
@VegaFlash I will update you when the new inits are available, for you to try it out.
@Tom-Elliott I am working on newer inits with the updated e2fsck
package to resolve this issue.
@VegaFlash I will update you when the new inits are available, for you to try it out.
@mrowand I just tried installing 1.5.10 on a fresh Rocky 8.9 VM. It went through and downloaded everything correctly.
Try running these commands on the server to see if you can manually download the files.
curl -kOL https://github.com/FOGProject/fos/releases/latest/download/bzImage
curl -kOL https://github.com/FOGProject/fos/releases/latest/download/bzImage32
curl -kOL https://github.com/FOGProject/fos/releases/latest/download/init.xz
curl -kOL https://github.com/FOGProject/fos/releases/latest/download/init_32.xz
curl -kOL https://github.com/FOGProject/fog-client/releases/download/0.13.0/FOGService.msi
curl -kOL https://github.com/FOGProject/fog-client/releases/download/0.13.0/SmartInstaller.exe
Let us know if this works.
Edit by Tom to ensure urls were accurate for fos files
@JackYwn You did not provide enough information on how/when you are getting this error.
I am assuming that the message you posted is from the installation script, meaning that it errors when trying to download the kernel during an install. If that is the case, please try re-running the installer using the newest dev-branch version, 1.5.10.17.
@iljared98 There is a way. The CSV will contain more information than just the Motherboard Product Name
, but that is easy to clean.
On FOG, go to the Reports
tab and select Inventory Report
from the left side menu. Don’t change anything there, just click on Search
. Download the CSV from the page using the excel sheet icon. When you open the CSV, column R
should be mbproductname
which is what you are looking for.
@sami-blackkite What filesystem are you using on your device?
@pauleb I use this powershell script for my M365 snappin. Hope it helps you.
$username = "DOMAIN\USERNAME"
$password = ConvertTo-SecureString "PASSWORD" -AsPlainText -Force
$creds = New-Object System.Management.Automation.PSCredential $username, $password
New-PSDrive -Persist -Name "Z" -PSProvider FileSystem -Root "\\SHARE\AppRepo" -Credential $creds
Start-Process -Wait -FilePath "Z:\Microsoft\Microsoft365_x64\setup.exe" -ArgumentList '/configure "Z:\Microsoft\Microsoft365_x64\configuration.xml"' -NoNewWindow
Remove-PSDrive -Name "Z"
@PCF24 Here is a quick and dirty script to reset all your hosts.
I tested it with two hosts and it is working for me. I don’t want to reset all my hosts.
You will have to paste your FOG server IP, FOG user api token, and FOG settings api token to the script.
You will also need to install jq
in your FOG server.
Debian base: sudo apt install jq
. RHEL based: sudo dnf install jq
#!/bin/bash
server_ip="http://10.10.10.10"
fog_user_token="PASTE_YOUR_USER_API_TOKEN_HERE"
fog_api_token="PASTE_YOUR_FOG_SETTINGS_API_TOKEN_HERE"
all_hosts=$(curl -S -s -X GET -H 'content-type: application/json' -H "fog-user-token: $fog_user_token" -H "fog-api-token: $fog_api_token" $server_ip/fog/host/ | jq '.hosts[]')
all_ids=$(echo "$all_hosts" | jq '.id')
all_ids=${all_ids//\"/}
for host_id in $all_ids
do
curl -S -s -o /dev/null -H "fog-user-token: $fog_user_token" -H "fog-api-token: $fog_api_token" -X PUT -d '{"pub_key":""}' $server_ip/fog/host/$host_id/edit
curl -S -s -o /dev/null -H "fog-user-token: $fog_user_token" -H "fog-api-token: $fog_api_token" -X PUT -d '{"sec_tok":""}' $server_ip/fog/host/$host_id/edit
curl -S -s -o /dev/null -H "fog-user-token: $fog_user_token" -H "fog-api-token: $fog_api_token" -X PUT -d '{"sec_time":"0000-00-00 00:00:00"}' $server_ip/fog/host/$host_id/edit
done
@sgilbe Okay, I did some changes and reuploaded dist_virt_1
& dist_virt_2
. Can you try them again?
@sgilbe I uploaded two more kernels with virtualization enabled (dist_virt_1
& dist_virt_2
). Let me know if this works for you.
https://drive.google.com/drive/folders/1sP6dfRymYaFTCr8iRiK64hN2pp2X836n
@SaturTP That’s an interesting find, I’ll check why this would be the problem.
@sgilbe If disabling virtualization makes it work for you too, I’ll add one more kernel to the drive share for you to try.
@sgilbe Hi, sorry for the delay.
I have 3 new kernels to try. I hope one of these works for you https://drive.google.com/drive/folders/1sP6dfRymYaFTCr8iRiK64hN2pp2X836n?usp=drive_link
If any one of these works, please let me know which one so I can document it.
@JJ-Fullmer I’m currently working on new kernels and inits. Having issues with building partclone for the inits, but I’ll hopefully have some time this weekend to get it done.
I will include the ufs changes for the kernels.
@bballmcoe I haven’t used CentOS 7 in a while so unless this is a CentOS quirk that I don’t remember, you are running the install script using shell
not bash
.
Try running the installer like this: ./installfog.sh
or bash installfog.sh
@Eliza Ese error pasa cuando el Kernel no encuentra ningún interfaz de red. Unas preguntas:
That error happens when the kernel doesn’t find any network interface. A few questions:
@Eliza Cual version de FOG y de Kernel esta usando? Puede poner una foto de la pantalla con el error de Kernel?
What version of FOG and Kernel are you using? Can you post a photo os the screen with the Kernel error?
@sgilbe I made a few changes to the kernel. Can you try the with the new one here? https://drive.google.com/drive/folders/1sP6dfRymYaFTCr8iRiK64hN2pp2X836n
@sgilbe Have you tried removing the QSFP card to see if it is still giving you that issue? I doubt that it’s the problem, but it wouldn’t hurt to try.
I’ll keep looking at the kernel config options to see if I find something else that could be missing. It may be a lot of back-and-forth trying different kernel options, since I don’t have any system with those CPUs.
@sgilbe Try this kernel out. https://drive.google.com/drive/folders/1sP6dfRymYaFTCr8iRiK64hN2pp2X836n?usp=sharing
This is kernel 6.5.6 with some config changes specific for gen 3/4 scalable Xeon CPUs. Please let us know if this works so I can document the changes.
Something else to look at… I had an issue like this with another Linux system last week. The issue turned out to be a Mellanox 40G PCIe card not playing nicely with the Kernel. Have you tried taking out non-essential PCIe cards from the host to test?
@sgilbe @george1421 I think I have an idea of what kernel modules need to be enabled for this type of CPU. I don’t have my dev laptop with me now, but I’ll work on it tonight/tomorrow so you can try it out.
@anwoke8204 Tom is right. I had that same issue when trying to use snapins the first time.
You would need to do something like this:
$username = "DOMAIN\USERNAME""
$password = ConvertTo-SecureString "PASSWORD!" -AsPlainText -Force
$creds = New-Object System.Management.Automation.PSCredential $username, $password
New-PSDrive -Persist -Name "Z" -PSProvider FileSystem -Root "\\SHARE\PATH" -Credential $creds
#
# RUN YOUR CODE REFERENCING THE "Z" DRIVE
#
Remove-PSDrive -Name "Z"