Posts made by jemerson93

@Junkhacker

Thank you for the assistance. This issue was resolved. I’m not sure how to mark this as resolved though.

@Junkhacker said in Issues with MBR images and disk guid:

@jemerson93 there was a bug that was in the initial 1.5.6 release. it has been fixed. if you rerun the installer it will update the init files and solve the problem, or you can update the init files manually to the new version.

I saw another post regarding this after I posted it. I downloaded the inits posted and moved them over. I also changed the KERNEL RAMDISK SIZE that I saw as well. Testing now but is that what you were mentioning?

Hello all,

So images that are created in MBR partitions (legacy) are receiving Unable to load Windows and please re-install Windows error. I found this to be common with Windows Server 2016, Windows 10 and Windows 7. Upon some further searching, I find “Inserting Extended Partitions” are failing and if I redeploy the failed image, I receive the following Disk Guid error. Any input would be appreciated.

FOG Version: 1.5.6
bzImage Version: 4.19.36
bzImage32 Version: 4.19.36

@Sebastian-Roth said in Partclone Upload Stalling:

@jemerson93 Please test the newly compiled 4.15.2 kernels you find here: https://fogproject.org/kernels/new/

Let us know if those help in speeding up the process and still don’t have the other rcu_sched stall issue.

Hi Sebastian,

It may take me a couple of days to get a response back to you. As soon as I can, I’ll do another upload and update you.

@Wayne-Workman said in Partclone Upload Stalling:

@Sebastian-Roth I don’t have access to their articles anymore - but when I did have access back at a previous job, I found if I google’d enough I could find the same stuff elsewhere.

Has a duplicate IP been looked for yet, for the fog server and for the VMs?

Hi Wayne,

I did verify there are no duplicate IP’s in use between the FOG server and VM’s nor are any in use on individual workstations on the LAN.

@Sebastian-Roth said in Partclone Upload Stalling:

@jemerson93 It’s very interesting we see this or similar issues on many different platforms - hardware as well as virtualized environments. There does not seem to be a general answer and those kind of things have been around for years - when you search for rcu_sched you find tons of messages in kernel related mailing lists and forums.

But still this got more and more lately in the FOG forums as well and we are not sure why yet. But moving back to 4.15.2 kernel helped most of the people. We have seen issues with the newer init files not being compatible with this kernel and so I might ask you to manually download those more compatible inits (64 bit and 32bit). Rename/backup the ones you have in /var/www/html/fog/service/ipxe and put those in place (names init.xz and init_32.xz). Then downgrade to the 4.15.2 kernel and see if you still get the ugly error you had before when trying to downgrade the kernel.

If that doesn’t work then I expect this particular issue to be a problem with Hyper-V and Linux kernel option PAGE_TABLE_ISOLATION - Meltdown patch (ref). But would be kind of strange as we have this option enabled in all later kernel version. Nevertheless you can try going back to even older versions of kernel and init. Find those used in FOG 1.5.0 here (kernel 4.13.4).

Beside that I have tried to find current information specific to Hyper-V. Not much I could find, really. https://access.redhat.com/solutions/3743631 (anyone who’s access to RedHat stuff? @Wayne-Workman?)

Hi Sebastian,

My apologies for the late response. I backed up the old inits and downloaded and moved the ones you requested. I then downgraded to 4.15.2 kernel. Did not receive the kernel panic and the legacy image successfully uploaded. It take much longer then usual (I think it took about 3 and a half hours opposed to the past 30 minutes) but no CPU stall or initial network stall.

@Sebastian-Roth said in Partclone Upload Stalling:

@jemerson93 I meant the stall from the initial post.

I also attempted 4.19.6 and got the same error. I’ll chalk it up as luck that I got it uploaded, but now I can’t re-upload.

@Sebastian-Roth said in Partclone Upload Stalling:

@jemerson93 I meant the stall from the initial post.

Hi Sebastian,

I did not see the stall from the initial post. Now I am just running into the self-detected stall.

@Sebastian-Roth said in Partclone Upload Stalling:

@jemerson93 Can you please do me a favor testing-wise? I just updated the 4.19.1 kernels to have the Hyper-V patch included as well. Can you please downgrade to that kernel version on your FOG server and test again? The hard stall shouldn’t be happing with this version anymore.

About the other issue: I am looking forward to hear what you guys find out testing this. Maybe we can report that to the kernel developers when we find out what version exactly is causing this.

Hi Sebastian,

Unfortunately, I still got the stall. As a notice, I did get the legacy image to upload on 4.19.6 yesterday. Was extremely slow but did upload. Trying again right now on 4.19.6.

I am still setting it up at my home to test as well.

@george1421 said in Partclone Upload Stalling:

@jemerson93 While it doesn’t help you at the moment, then can we say the issue of the cpu stall and other linux kernel strangeness is related to to hyper-v under windows 2016 server?

I have a hyper-v server running Windows 2016 Data Center in our backup hot site. This is for spinning up our Veeam images. The point is, I haven’t messed with hyper-v (ever sorry I’m a vmware guy) but I’m willing to see if I can create a VM and duplicate the same thing you see. The first step is to see if we have correlation between my server and your server. Then see if this is a common problem with linux OS running under hyper-v.

Hi George,

Perfect, if you can let’s see if you get the same issue. I’m also going to spin up a VM at my home (I have Hyper-V and Proxmox on 2 servers at my house) and I’ll see if I can replicate the issue.

@george1421 said in Partclone Upload Stalling:

@jemerson93 That is very strange to see a kernel panic like that. I’ve only experienced that when I’ve mixed the inits arch with the kernel arch (i.e. booting bzImage (64 bit kernel) but having init_32.xz (32 bit inits) for the virtual disk).

I see you are running this on a hyper-v vm in bios mode. Are you getting the same results with a physical machine. Maybe its something in hyper-v land causing this cpu stall. Can you provide stats on your hypervisor version you are using (i.e. Windows 10 1803 with hyper-v loaded, etc).

Hi George,

The host running FOG (and our images) is Windows Server 2016 Standard 1607 with Hyper-V loaded. All that we are running on this server is a few VM’s (FOG, Win10-UEFI, Win10-Legacy, and our DHCP server).

To give another example, in another location, we run Proxmox as our hypervisor. FOG and all of our images (we house many more images there) are created in Proxmox and we are currently having no issues deploying or capturing images. That FOG is version 1.5.5 and the kernel version is 4.19.1.

This VM specifically is running in BIOS mode (as I am trying to upload a legacy only image for older workstations). We seem to be able to deploy to physical workstations (and virtual machines perfectly fine). Capturing seems to have no issue except on this VM running in Gen 1 (BIOS Mode).

@george1421 said in Partclone Upload Stalling:

@jemerson93 It would be interesting to know if you took the kernel the other direction and see if 4.15.2 has the same error. We’ve see quite a few cpu stalls recently. Maybe Sebastian’s patch took care of them. But downgrading the kernel also seems to mask the issue.

Hi George,

Just to give an update, I tried that kernel and it seems it goes into a Kernel Panic mode. I’ve also tried various other Kernel’s 4.19, 4.18, etc and I either go into the kernel panic or eventually the rcu_sched stall.

Stumped on what I could do to get this image captured.

Trying the 4.15.2 kernel’s, I get the following…

@Sebastian-Roth said in Partclone Upload Stalling:

@jemerson93 said in Partclone Upload Stalling:

I updated the kernel and I was able to capture the UEFI image.

So you are saying the speed issue and stall is gone with 4.19.6 kernels? If that is the case I should look into re-building the 4.19.1 kernels and make sure the patch is included as well.

About the rcu_sched message: Please search the forums for this and see what you can find out.

Hi Sebastian,

With the newest kernel, the issue and speed issue seemed resolved. This first upload took an extremely long time, but the 2nd upload took much, much faster.

I’ll try 4.15.2 and see if I can upload the legacy image.

@Sebastian-Roth said in Partclone Upload Stalling:

@jemerson93 I am wondering if this is related: https://forums.fogproject.org/topic/6695/performance-decrease-using-hyper-v-win10-clients

We should have that patch in all our kernels but there is a slight chance that I have missed adding the patch to 4.19.1 kernel. Can you please update to 4.19.6 and see if that makes a difference?

Hi Sebastian,

To give an update on this…

I updated the kernel and I was able to capture the UEFI image. Below is a copy of an error I am receiving when trying to capture the legacy image.

I verified I am not maxing out any resources on the host.

Running into a strange issue with a FOG deployment. Below is the information and issue.

FOG Version: 1.5.5
Kernel Version: 4.19.1

FOG is deployed via Hyper-V on Ubuntu 18.04.1 Desktop
2 separate VM’s are created for each image. 1 VM is a Gen 1 VM for the Legacy image. The other VM is a Gen 2 VM for the UEFI image. The DHCP server is Server 2016 and the scope options for Legacy (undionly.kpxe) and UEFI (ipxe.efi) are both configured and FOG boots fine. During the image capture, it completely stalls out shortly after starting the upload process to /images/dev. First the percentage bar stalls out and network traffic slowly drops, eventually the whole thing stalls out and time remaining and time elapsed are frozen. I’m stumped on what could be causing this as it was working a few weeks ago. The FOG server was re-created last night just to test that. This image is after it was completely frozen.

@Sebastian-Roth Let me test it with a machine and get a specific model. I will verify the UEFI firmware is up to date as well.

@Sebastian-Roth So sorry for the late reply.

It does not act like this on all workstations. Some are smooth and some have this issue.

This is an ongoing issue that never really bothered me until recently and I’m having some issues trying to resolve it. This issue does not appear if booting into FOG via Legacy boot.

The issue is when booting into FOG via UEFI boot, once selecting PXE boot before getting to the main FOG menu, we get a black screen. Only lasts for 2-3 seconds but with our settings set to boot to hard drive after 3 seconds, it’s a pain. We also have a delay when typing in the username/password or scrolling through the menu.

I was wondering if anyone has experienced this and has any insight on how I can resolve this.

FOG Version: 1.5.4
Kernel Version: 4.18.11 (happens with any kernel version)
Linux Server: Ubuntu 18.04.1 LTS (Bionic Beaver) 64-Bit

@tesparza said in Windows 10 clock is always off after imaging:

Is there a way to update the clock on windows 10 machine with FOG server remotely?

If it is the clock being off an hour, I had a similar issue which I fixed through my unattend script. It would automatically disable daylight savings time which would set it an hour back. Once I fixed that, my time is correct on each image.