Posts made by jakevirginia

@theopenem_admin when I enable efi on the virtual machine setting in virtual box. I no longer have to ability to f12 into pxe boot. And the vm will not boot. And I also don’t understand because the laptops are dual legacy and uefi. I’ve never had to click enable efi before and it imaged the drives just fine.

@theopenem_admin

enregdeploylogstheo.txt

here is the requested log

Hello all. I’m having some issues currently with deploying an image to a drive. The image loads onto theopenem just fine. When I put a drive into the laptop I boot ipv4 pxe and it takes me to the theopenem option. I select my image and it deploys just fine or so it seems. After it finishes It doesn’t boot to the image and it doesn’t see the drive or image in the boot priorities. It’s as if it didn’t actually put anything on. I’ve tried 3 different known good laptops and 7 different known good images. And uploaded from 2 different servers. The only explanation I can come up with is there’s something wrong with theopenem as that’s the only common denominator. Has anyone seen a similar issue ? Any ideas on what to do next? attatched are the logs from the process

enregdeploylogstheo.txt

@theopenem_admin the only error I can find is a warning. “Secondary partition table overlaps the last partition by 33 blocks”

@theopenem_admin I found the application logs. How do I find the deploy logs?

@theopenem_admin
I have not been able to find any option for logs in the theopenem desktop application on my server

Hello all. I’m having some issues currently with deploying an image to a drive. The image loads onto theopenem just fine. When I put a drive into the laptop I boot ipv4 pxe and it takes me to the theopenem option. I select my image and it deploys just fine or so it seems. After it finishes It doesn’t boot to the image and it doesn’t see the drive or image in the boot priorities. It’s as if it didn’t actually put anything on. I’ve tried 3 different known good laptops and 7 different known good images. And uploaded from 2 different servers. The only explanation I can come up with is there’s something wrong with theopenem as that’s the only common denominator. Has anyone seen a similar issue ? Any ideas on what to do next?