Changing from RAID on in BIOS to AHCI fixed this issue for me. Thanks so much for the tip @FoSTerCyber !!

I get that, Wayne, and I don’t think that’s harsh. I should have commented on your suggestion. Better late than never: The weird thing I saw was when I did a download with debug, and then ran fdisk was I only saw one partition. I didn’t really understand that and still getting my feet wet with FOG decided to revert back to a snapshot before going any further. I really do appreciate the help and knowledge you guys have, I would be sunk without your help!! Thanks again. I’m going to try upgrading to the latest Trunk version and see what happens. Thanks!

@george1421 Yes. I downloaded and installed FOG trunk on a separate server. Copied the bzImage, bzImage32, init.xz, init_32.xz to the /var/www/html/service/ipxe folder. Kernels do work on regular computer, yes.

@Sebastian-Roth I am in the process of making a live debug fog usb stick now. I’ll let you guys know of the status when I get there. Thanks for all the help so far!

Cool. I’m ready to run some command-fu on this thing and provide output as needed.

@Sebastian-Roth I’ve done the manual registration and pushed the bzImage_epk to the host with the kernel arguments and it did give a lot of text printing before the kernel panic. Video coming soon…

@Tom-Elliott Sure. Thanks for keeping on this one, Tom!

@Tom-Elliott Updated and uploading an image now from the Surface Pro 4 on the amazon basics usb 2.0 Ethernet adapter. I’ll let you know what it does in 10 minutes or so. Thanks for all your help, Tom and FOG team, you guys rock!!

@Tom-Elliott It did this time. And I was able to set up 2 different locations on 2 different storage groups.

You can mark this is as solved. This was a case of good old SE linux set to enforce. Can’t believe it. Thanks @Tom-Elliott!!

@george1421 Sweet, doing the initial install now via git.

@george1421 So, I’m doing a brand new install to start afresh. I’ll need to do some work I assume to get on 1.5.2?

@george1421 Ok… how does one install to a certain version? I’d used git on the last one to update to current, but I’m not sure how to get 1.5.2 installed and then switch to the working branch? I’ll look on the forums but if you can point me in the right direction to get this installed, then 1.5.3 will be a simple upgrade.

@george1421 Any idea when 1.5.3 will be released?

Would it be a good idea to update FOG? I know you all have made TONS of improvements from the version I’m on. However, it doesn’t like a FOG issue per se but a UEFI issue. So, the process I would take to image is as follows:

Machine comes in RAID ON
Prep machine as I want it
Start a Capture task for the host
sysprep, then on reboot change to AHCI, Legacy mode and capture
After that, capture image
Deploy or just reboot
Before booting up, change back to RAID ON

?? Does that sound like the right process?

@george1421 I should be able to use any .efi file, correct? OR should it be a specific efi file? Right now I think I’m using a hacked together one from @Tom ages ago so I will most likely be upgrading FOG shortly.

@george1421 That is the process I was looking for. I’ll attempt that and let you know. Thanks @george1421 !!

Switched to RAID on and got an “inaccessible boot device” interestingly enough. This is a latitude 7490 from factory with a few tweaks and then me trying to upload to be able to deploy. I’m fine if I have to update FOG, that’s not a problem but wondering if this can be avoided in the future or what process I should take to capture and deploy with this UEFI/linux issue?

So,

Windows just booted up and I got the famous “windows cannot complete the installation, please reinstall” or some such. Thoughts? Would switching back to Raid On fix this issue and allow windows to boot properly?

@george1421 Very interesting. I just switched to legacy and captured the “master sysprepd” image as it were. BEFORE booting into the os, I changed from RAID-ON to AHCI. I’ll let you know what happens in a few minutes as I suspected the RAID-on vs AHCI deal. Thanks.