Upgraded to FOG 1.5.10.1629 but now can't capture image #99
Comments
|
Can you check what version of the kernel and init you're running. |
|
This is the only info I could find.
[image: image.png]
…On Mon, Dec 23, 2024 at 11:15 AM JJ Fullmer ***@***.***> wrote:
Can you check what version of the kernel and init you're running.
I believe this should show in the FOG web gui under fog configuration,
should show the versions of each as I recall
—
Reply to this email directly, view it on GitHub
<#99>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ARI47S2IJTFS3ONXX7ZT2SD2HBHMVAVCNFSM6AAAAABUDOYMJ6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNRQGEZDEMJWGE>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
|
looks like the image didn't attach |
|
That's weird. Hopefully it is there now.
…On Mon, Dec 23, 2024 at 11:33 AM JJ Fullmer ***@***.***> wrote:
looks like the image didn't attach
—
Reply to this email directly, view it on GitHub
<#99>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ARI47S24TOQFMFP25HYXAQD2HBJRNAVCNFSM6AAAAABUDOYMJ6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNRQGE2DEMRUGU>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
|
I think I got it attached this time. |
|
There's a upgrade kernel and an upgrade init section in the config. Maybe try the previous version of both, looks like you're on the latest. Seems like you've loaded the kernel and init and then getting stuck. If a previous version works then maybe something in proxmox has an issue with that Linux kernel |
|
Thanks, I'll give it a try.
…On Fri, Dec 27, 2024 at 3:13 PM JJ Fullmer ***@***.***> wrote:
There's a upgrade kernel and an upgrade init section in the config. Maybe
try the previous version of both, looks like you're on the latest. Seems
like you've loaded the kernel and init and then getting stuck. If a
previous version works then maybe something in proxmox has an issue with
that Linux kernel
—
Reply to this email directly, view it on GitHub
<#99>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ARI47SYLBTUTSMVWGGTAAWD2HXGHFAVCNFSM6AAAAABUDOYMJ6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNRUGA3DEOBUHA>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
|
Found a post of someone that was having the same problem but with Hyper-v. They downgraded the Kernel to 6.1.89 to make it work. https://forums.fogproject.org/topic/17663/capture-uefi-image-on-hyper-v-vm/2 We run Proxmox 8.3.2 if that helps. |
|
Ah, I didn't know that the hyper v issue affected prox mox too. Iirc this is a Linux kernel issue with the hypervisors not the fog implementation but I'm not 100%. A fix is on our radar but everyone is on vacation at the moment
…________________________________
From: laurwls ***@***.***>
Sent: Monday, December 30, 2024 3:23:10 PM
To: FOGProject/fogproject ***@***.***>
Cc: JJ Fullmer ***@***.***>; Comment ***@***.***>
Subject: [External]Re: [FOGProject/fogproject] Upgraded to FOG 1.5.10.1629 but now can't capture image (Issue FOGProject/fos#99)
Found a post of someone that was having the same problem but with Hyper-v. They downgraded the Kernel to 6.1.89 to make it work. https://forums.fogproject.org/topic/17663/capture-uefi-image-on-hyper-v-vm/2
Downgrading the Kernel to 6.1.89 also worked for me. None of the newer Kernels (6.6.xx) worked. Will there be a true fix? Downgrading doesn't seem like a fix to me.
We run Proxmox 8.3.2 if that helps.
—
Reply to this email directly, view it on GitHub<#99>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AB3CO3AFCBMFLIO3M2E2WFT2IHBU5AVCNFSM6AAAAABUDOYMJ6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNRVHE3DQNBYGY>.
You are receiving this because you commented.Message ID: ***@***.***>
|
|
Thank you for taking the time to try and help me. Should I post to a Linux
group about this issue?
…On Mon, Dec 30, 2024 at 3:36 PM JJ Fullmer ***@***.***> wrote:
Ah, I didn't know that the hyper v issue affected prox mox too. Iirc this
is a Linux kernel issue with the hypervisors not the fog implementation but
I'm not 100%. A fix is on our radar but everyone is on vacation at the
moment
________________________________
From: laurwls ***@***.***>
Sent: Monday, December 30, 2024 3:23:10 PM
To: FOGProject/fogproject ***@***.***>
Cc: JJ Fullmer ***@***.***>; Comment ***@***.***>
Subject: [External]Re: [FOGProject/fogproject] Upgraded to FOG 1.5.10.1629
but now can't capture image (Issue FOGProject/fos#99)
Found a post of someone that was having the same problem but with Hyper-v.
They downgraded the Kernel to 6.1.89 to make it work.
https://forums.fogproject.org/topic/17663/capture-uefi-image-on-hyper-v-vm/2
Downgrading the Kernel to 6.1.89 also worked for me. None of the newer
Kernels (6.6.xx) worked. Will there be a true fix? Downgrading doesn't seem
like a fix to me.
We run Proxmox 8.3.2 if that helps.
—
Reply to this email directly, view it on GitHub<
#99>,
or unsubscribe<
https://github.com/notifications/unsubscribe-auth/AB3CO3AFCBMFLIO3M2E2WFT2IHBU5AVCNFSM6AAAAABUDOYMJ6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNRVHE3DQNBYGY>.
You are receiving this because you commented.Message ID: ***@***.***>
—
Reply to this email directly, view it on GitHub
<#99>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ARI47S7NP5B3VQ42AD6KK3L2IHDFTAVCNFSM6AAAAABUDOYMJ6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNRVHE3TMMZRHA>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
|
@laurwls This is more of a Linux issue that's specific to FOS. That being said, I don't believe that posting anything on a Linux group would help in this case. I figured out what the issue is for this and have a solution tested on Proxmox. I am testing it today with Hyper-V and ESXi but I should have a full kernel release later this week. Also moving this issue to the FOS repo. |
|
Thank you @rluzuriaga @darksidemilk @laurwls for tracking this and glad this is in the right area now. |
|
@laurwls Please try using the newest experimental release of kernel 6.6.69. This release should have fixed your issue, let us know if it is still giving you problems. |
|
Tested and the experimental release of kernel 6.6.69 has fixed the issue.
I can now capture and deploy images with that kernel.
Thank you
…On Wed, Jan 8, 2025 at 12:57 PM Rodrigo Luzuriaga ***@***.***> wrote:
@laurwls <https://github.com/laurwls> Please try using the newest
experimental release of kernel 6.6.69. This release should have fixed your
issue, let us know if it is still giving you problems.
—
Reply to this email directly, view it on GitHub
<#99 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/ARI47SYTYAAIXOL627NUUYD2JV7IZAVCNFSM6AAAAABUWJ6YDOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNZYGUYTMMRUGQ>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
How can we help you?
Upgraded to FOG 1.5.10.1629 but now can’t capture image. The capture process gets stuck at EFI Stub measured.
Can anyone help?
The text was updated successfully, but these errors were encountered: