@george1421 So to translate what you have. kernel http://${fog-ip}/fog/gparted/vmlinuz initrd http://${fog-ip}/fog/gparted/initrd.img boot=live config components union=overlay username=user noswap noeject ip= vga=788 fetch=http://${fog-ip}/fog/gparted/filesystem.squashfs boot Into iPXE syntax kernel http://${fog-ip}/fog/gparted/vmlinuz initrd http://${fog-ip}/fog/gparted/initrd.img imgargs initrd=initrd.img boot=live config components union=overlay username=user noswap noeject vga=788 fetch=http://${fog-ip}/fog/gparted/filesystem.squashfs boot Also I would strongly suggest that you NOT use the path http://${fog-ip}/fog because of the url rewriting rules that fog does with apache. If you had to use http I would put it in directory off the web root directory and not under /fog.

@Sebastian-Roth said in Failed to Set Disk GUID (sgdisk -U) (restoreUUIDinformation): I just booted a client into FOS and see that we still have 4.7 MB of free space Didn’t we update this initfs to 256MB with this change to the build root config file? If I remember correctly the fog default was 100MB. BR2_TARGET_ROOTFS_EXT2_SIZE="256M" I’ll have to boot my last initrd file to see the free space, but 4MB sounds small. I might understand if its tempfs that is out of space. I think I remember that defaults to 4MB. That might be the space we are having issues with.

@quinniedid said in FOG 1.5.6.2 Issues with Resizable image: Sometimes the resize works and other times it doesn’t Do you mean the same image sometimes resizes and sometimes not? We’d need the exact same information from your image (best to open a new topic) to look into this.

@Jonathan-Cool They may be reserved accounts which is why it trips up, I don’t think there’s much to change in the settings there, going with the Samba credentials route seems the best way. If your Samba share is AD enabled then domain connected PCs will likely logon under their actual accounts when they try to connect to the share rather than Windows assuming you want to logon as ‘System’

Is a random situation, I have tried to replicate the issue but was unsuccess. The problem is with the first time that the FOGservice runs, if you reboot the computer, in the second time the service runs well. But is necesary do it manually :(

@VijayBomble Any news on this?

@SPaceSkillz1 Did you solve this yet?

@Sebastian-Roth Do you see any risk to add this into FOS’s sysconfig? The question I would have is what is the default and what are the risks to shorten the latency to nvme_core.default_ps_max_latency_us=200 Searching the kernel paths I see the default set to this default_ps_max_latency_us = 100000; As set in drivers/nvme/host/core.c -OR- should this setting just be set as a host specific kernel parameter? I can make a case either way. I just don’t know if there are any negative impacts on systems where this isn’t a problem.

@DeRo93 said in Database connection unavailable - Login incorrect on FTP and Ubuntu: But maybe you can tell me if this happened because the Ubuntu Server did an Upgrade or something? Probably yes. But you may check the update log in /var/log/apt/history.log…

@Landy_Dan The FOG CA was introduced to secure the connection between fog-client software and the FOG server. We use certificate based state of the art encryption for that. But you need to know that it is a self signed CA and not derived from an official authority. Not sure if it’s wise (and even possible) to use that for your RADIUS project. Give it a try and see how far you get. Start by taking a look at all the certificate stuff in /opt/fog/snapins/ssl/ on your FOG server.

I didn’t update kernel. it still working for me. Thanks,

@pdit So it’s probably something that changed in the Linux kernel that is causing this issue. I’d like to track this down but I don’t think I’ll find the time to do so in the next months. You should be able to switch between different kernels to see which version first had the issue. Find all the different kernel versions in the FOG web UI or here: https://fogproject.org/kernels/

Make sure your firmware is up to date in this hardware. Its failing between the UEFI PXE rom hand off and iPXE starting. Typically when we’ve seen this in the past it was related to cruddy early generation firmware.

@tgidwani Looking at out code more closely I noticed that most of those ftp_... warnings are perfectly fine. FTP is not able to remove a directory that isn’t empty yet. So we do some kind of recursive delete which leads to print out all of the “ftp_delete” and “ftp_rmdir” messages which are not important. I’ll still remove those in the next release we get less confusion. But the “ftp_rename” and “ftp_put” warnings make me think there is something wrong with your NFS shares. Just guessing here but let’s give it a try. Please run exportfs -v as root on your FOG server and post output here. As well take a picture of the Storage Node setting in the web UI and post a picture here.

Hey Sebastian, thanks for the response. Some external vendors nuked our network over the weekend while performing some kind of maintenance in the data center, so I’m without access to the FOG server until the pieces can be mended. I’ll get back to you with the info once I can. They worked through the night and the network is 98% functional! Here’s what you asked for: #!ipxe set fog-ip 172.17.207.144 set fog-webroot fog set boot-url http://${fog-ip}/${fog-webroot} cpuid --ext 29 && set arch x86_64 || set arch i386 goto get_console :console_set colour --rgb 0x00567a 1 || colour --rgb 0x00567a 2 || colour --rgb 0x00567a 4 || cpair --foreground 7 --background 2 2 || goto MENU :alt_console cpair --background 0 1 || cpair --background 1 2 || goto MENU :get_console console --picture http://172.17.207.144/fog/service/ipxe/bg.png --left 100 --right 80 && goto console_set || goto alt_console :MENU menu colour --rgb 0x00567a 0 || cpair --foreground 1 1 || cpair --foreground 0 3 || cpair --foreground 4 4 || item --gap Host is registered as LNPC08CU55! item --gap -- ------------------------------------- item fog.local Boot from hard disk item fog.memtest Run Memtest86+ item fog.keyreg Update Product Key item fog.deployimage Deploy Image item fog.multijoin Join Multicast Session item fog.quickdel Quick Host Deletion item fog.sysinfo Client System Information (Compatibility) choose --default fog.reginput --timeout 3000 target && goto ${target} :fog.local sanboot --no-describe --drive 0x80 || goto MENU :fog.memtest kernel memdisk initrd=memtest.bin iso raw initrd memtest.bin boot || goto MENU :fog.keyreg login params param mac0 ${net0/mac} param arch ${arch} param username ${username} param password ${password} param keyreg 1 isset ${net1/mac} && param mac1 ${net1/mac} || goto bootme isset ${net2/mac} && param mac2 ${net2/mac} || goto bootme param sysuuid ${uuid} :fog.deployimage login params param mac0 ${net0/mac} param arch ${arch} param username ${username} param password ${password} param qihost 1 isset ${net1/mac} && param mac1 ${net1/mac} || goto bootme isset ${net2/mac} && param mac2 ${net2/mac} || goto bootme param sysuuid ${uuid} :fog.multijoin login params param mac0 ${net0/mac} param arch ${arch} param username ${username} param password ${password} param sessionJoin 1 isset ${net1/mac} && param mac1 ${net1/mac} || goto bootme isset ${net2/mac} && param mac2 ${net2/mac} || goto bootme param sysuuid ${uuid} :fog.quickdel login params param mac0 ${net0/mac} param arch ${arch} param username ${username} param password ${password} param delhost 1 isset ${net1/mac} && param mac1 ${net1/mac} || goto bootme isset ${net2/mac} && param mac2 ${net2/mac} || goto bootme param sysuuid ${uuid} :fog.sysinfo kernel bzImage32 loglevel=4 initrd=init_32.xz root=/dev/ram0 rw ramdisk_size=127000 web=http://172.17.207.144/fog/ consoleblank=0 rootfstype=ext4 storage=172.17.207.144:/images/ storageip=172.17.207.144 loglevel=4 mode=sysinfo imgfetch init_32.xz boot || goto MENU :bootme chain -ar http://172.17.207.144/fog/service/ipxe/boot.php##params || goto MENU autoboot

@jemerson93 Thanks for bumping this topic. Must have gone unseen in the last busy week, sorry. Is it one particular image that you see this “random” issue with? Please post the contents of the text files p1.partitions, p1.minimum.partitions and p1.fixed_size_partitions of that image here in the forums.

Weird, disregard. It just suddenly started working now. No idea what fixed it. Maybe it took a while for something to register.

@khalid Problem might be that the fog-client runs as System Service. Maybe installing updates like this is not allowed by MS security.