In a remote session we figured out that the database schema version was kind of oddly set. Still not sure why that was. Fixed that and applied the last couple of schema changes. That fixed a couple of odd issues including the Storage Node setting changes that can be done now again.

@Sebastian-Roth It looks like these files fixed the issue. :)

@arnaudrigole said in Dell Optiplex 7060 - getHardDisk error: I used that trick to switch between “raid on” and “AHCI” during more than one year right now, and it worked well but… Now we got NVMe SSDs in our new DELL computers, which need to be configured in “Raid ON” as “Sata Operation” to boot on Windows. Do you think that “GetHardDisk” error will be fixed in next versions ? I think you have two different issues here. The first issue is the raid-on vs ahci mode. This is an age old issue between Intel, Linux, and uefi. With these three amigos working together linux can’t currently see any disks behind this configuration. If you change any of the three (really two) linux will see the disk. From what I understand the issue is related to intel not releasing the uefi raid drivers to the linux community. The second issue may be new Dell hardware with these NVMe disks. What version of FOG are you using? What version of FOS Linux kernel do you have installed? What is the model number of the computer with this issue?

@0juke If you did not make any changes to your dhcp server then that is the primary problem. PXE booting client relies on 2 settings in dhcp. They are dhcp option 66 {next-server} and dhcp option 67 {boot-file}. These options tell the pxe booting client how to boot. For dhcp option 66 that needs to be the IP address of the fog server. For dhcp option 67 needs to be undionly.kpxe for bios based computers and ipxe.efi for uefi based computers. Without these settings the client computer will not know how to boot.

@Sebastian-Roth I did it and it’s work ! thanks a lot for your reply ans the time you spent for me :)

I’m dumb. Thanks for pointing that out. Worked like a charm.

@SaxxAppeal Hi. I would love to get the Fog server Vm. Can you share a link to download the .Vdi? Thanks to all at this forum.

Thank you for the reply. I am all set now. Seeing the fogproject user had me confused. I wasn’t aware of the username change. Thanks again for the help.

@drumnj said in Deploying BIOS Boot Order to multiple computers (booting to network 1st): You said you return yours to “normal” boot (I take it hd 1st) What I was referring to here is with Dell and CCTK you can set a flag in the bios that basically says on the next reboot boot to the network. On reboot+1 boot what ever the default boot device is. So if you wanted to do an unattended imaging but your normal boot device was the hard drive you could push out a FOG snapin that called cctk on next boot-boot to the LAN, then schedule a fog deployment. If the fog client is installed it will reboot the target computer and then start imaging right away.

@george1421 Awesome! Thank you, George!

So this can get marked as resolved. Everything worked as expected except when you update the nodes the GUI did not show the new version until after we updated the Master. All the issues we had with 1.5.4 were resolved with 1.5.6. Very happy with this update. GUI is super fast! The freezing on formating MBR/GPT on start of imaging is back to only a few seconds. Replication seems to be acting normal again.

@Wayne-Workman said in FOG install overwrites /etc/exports with no warning: In what scenarios do you see having two? If you were to install fog side by side with another product that supports nfs. What is the likelihood of two installs creating an entry with fsid of 0 or 1? We see that issue today when someone wants to create a second nfs share on the fog server and clones what is currently there but updates the paths only.

Thanks for the help. At this point I’m not sure if we’ll have the opportunity to test this, as we may have identified some other issues with our specific setup, we’re looking into some possible changes into how we manage our printers. But I’m sure we’ll have a need to use this method in the future.

@Sebastian-Roth Gparted fixed it with the “check” command, running what appeared to be the same commands I entered at terminal. I’ll try to capture it again after I’m more confident the box is ok. thanks guys

@jconway1006 What do you mean by doesn’t halt?? Just take a picture with a camera the moment you see the message on screen.

@drumnj If you don’t give us your particular partition layout details we can’t fix the issue (if there is one in 1.5.6). It’s as simple as that!!

@bnorwood Sorry for my late reply… Please try the last command again exactly as I posted: ls -1 /sys/class/net/ | grep -v lo | xargs -n1 -I{} bash -c 'echo -n {} :" " ; basename `readlink -f /sys/class/net/{}/device/driver`' In the picture I see that the first quote before the echo a back tick was used instead of a single quote. Edit: I just saw the kernel version and I can imagine you still have one of the old kernels that had the Hyper-V slowness problem in it. Please update the kernel (FOG web UI -> FOG Configuration -> Kernel Update) and see if that makes a difference.

@Sebastian-Roth Yeah I would rather not re-build my DB from scratch if at all possible. I have fewer hosts now than when I started with FOG but it’s still a large number. I am in the process of setting up another FOG server to do a fresh install and go from there. I do need to clean some things up in there so it may be the time to do this. I did run through the Troubleshoot MySQL Database Maintenance Commands and didn’t get real far with it. I"ll look at that once more before I bite the bullet on starting over. I’ll post back to the other thread I started. Hopefully I can figure something out without having to re-do the entire DB… Thanks for all of your help! I know you guys put in a ton of time with FOG and it’s very appreciated!! Cheers! Joe

@phishphan Issue here is that you have a second recovery partition (type=DE94BBA4-06D1-4D40-A16A-BFD50179D6AC) as fifth partition. FOG is not able to move that partition around and therefore cannot actually shrink your layout to fit on the smaller disk. Let’s do the maths. sda5 starts at sector 974862336 and is at least 1908736 sectors in size: (974862336 sectors + 1908736 sectors) * 512 bytes sector size = 500106788864 bytes ~ 465.76 GBytes That’s about the size of disk you need to be able to deploy this particular disk layout to it. In case you would remove the fifth partition (not saying you should as I don’t know your setup enough) the maths would be: (1161216 + 330329656) * 512 ~ 158.07 GBytes

@tandersb If you want to debug the issue, the best advice on debugging I can provide is here: https://forums.fogproject.org/post/124470 This is a fog admin that is trying to use a qnap and is getting a similar result.