Posts made by Doctrg

@george1421 We checked and all tables are ISAM.

We have moved our old server to a new server. We updated 1.5.5 to 1.5.9 on Ubuntu 18.04.6 and moved the database to the new server which is Ubuntu 20.04.3 and the MySQL process is getting hammered by our 1000+ clients checking in. There’s alot of changes from the old one to the new one and we are having issues tuning MySQL 8. Any suggestions where to look to start tuning MySQL 8?

We are about to migrate our Fog from one server to another. The current Fog is version 1.5.5. Are there any conflicts with moving from 1.5.5 to 1.5.9 directly or do we need to do an incremental update?

Thank you. This will help answering some questions on my end.

Will SnapIns run on a unregistered host using quick image or does the host need to be registered in FOG for SnapIns to run after imaging?

@Sebastian-Roth We are going from RHEL 6.8 to 7.5 and FOG 1.3.5 to 1.5.4. We were not sure if the database version would have an issue being backed up from 1.3.5 and dropped into a 1.5.4 install. Just trying to find out if it will be safe to do that large of gap upgrade or if we will have to babystep the upgrades to 1.5.4.

Good afternoon, we are going to be doing a fresh install of RHEL 7.5 and FOG. What version of mysql do you recommend or doing development on?

I just updated the kernel to 4.17.0 and it is working great now… actually seems like iPXE is much faster.

Has anyone recieved one of the new Dell Optiplex 7460 AIO computers and been able to boot to FOG? I am getting an issue failing to get an IP via DHCP. I know we are behind in versions, we are on 1.3.5. I’m assuming that our kernel is too old for the new chipset that Intel is using.

@Tom-Elliott Yep, that was my issue. I’ve updated to RC12 and from what testing that I have done, it seems that everything is working. I’m able to go from a 160GB to a 256GB and also 500GB drive and boot into Windows as well. The resizing seems to be correct as well.

@Tom-Elliott I’m trying to go through the installer this morning and it is failing on Backing up database.

@Tom-Elliott Not a problem. If you guys were here I’d buy y’all a round.

@Tom-Elliott On the 256GB drive it did not resize. It came up showing as a 40GB drive when running fdisk -l /dev/sda. The drive size showed correct on the 500GB drive due to it being the size it was created on originally. Neither could boot into Windows though.

@Tom-Elliott Sorry, the GPT image did not resize correctly.

@Tom-Elliott I’m glad it is not just me… I don’t have much hair on top of my head to pull out. I do thank you for your guidence on the bios image as recapturing it fixed that issue. I re-ran the FOG installer and my main server and storage nodes are now on 1.3.5 RC-10. I tried deploying the GPT image and it still did not expand the disk size. It did however it did not resize and it blew-up Windows. It is acting as if the Start-End of the partitions is not correct.

@Tom-Elliott I have the files uploaded to my Google Drive. I did find out that I was given some bad information the other day. The resize is also affecting our “BIOS” image. The reason we thought it was working was due to the HDD size being the same as the original drive. I was able to image a 500GB HDD, but when I tried an 80GB or 160GB I got the error “Target partition size (525MB) is smaller than source (670MB). Use option -C to disable size checking.”

I also booted into debug on the computer from the other day that I imaged which is showing only a 11GB drive. I ran ntfsresize -v /dev/sda4 and the output is as follows:

@Wayne-Workman I’m still working on getting the files uploaded. Who do I need to PM to send the link to the shared folder? Also, what program is being used for the resizing? My co-worker that has been the FOG administrator since the beginning is wondering if we can try to do a debug deploy and do a verbose on the resize.

@Wayne-Workman It would be helpful if I can send the image to one of you guys. I do not have control over our network so making DHCP changes would be out of my hands and we are in the middle of moving our offices so I do not have an offline environment setup yet to do testing. I’m downloading the image for the storage node now and will upload it to my Google drive once it is done.

@Wayne-Workman We were on 1.3.2 and we were having issues uploading so we updated to an RC of 1.3.4. As far as I know everything was working at that point, but once I saw there was a stable version of 1.3.4, I updated to that.

@Tom-Elliott I did some testing before your last post, but I’ve got some outputs for ya. What I did is installed Windows 10 barebone to both machines and created a totally new image entry in FOG.

This output is from the 500GB HDD to 256GB SSD:

And this output is from the 256GB SSD to 500GB HDD: