I’m going to attempt to create a new fresh image using AHCI instead of RAID. If this works, I have no problem using AHCI instead of RAID.
Best posts made by matt.lowrey
Latest posts made by matt.lowrey
RE: FOG and UEFI/M.2 SSD
No, the system doesn’t boot if I leave it on AHCI. It bluescreens with an “Inaccessible boot device” error. I did re-image the machine with my pre-sysprep version of the image I made, and I was able to boot after setting the option to RAID on. I’m going to try to sysprep again and capture the image again to see if it works.
As far as my DHCP server, it’s a Windows DHCP server. I have found the document showing how to create filters in DHCP for UEFI systems, but I couldn’t figure out how to determine what the UEFI architectures we have are. I wasn’t too worried about this since I can just change the option in DHCP whenever imaging a UEFI system.
FOG and UEFI/M.2 SSD
I have recently created a new FOG server for our imaging solution, and have been running into some issues. At first, I was using legacy boot for pxebooting, since we still have some systems that do not support uefi, but then I discovered the I cannot boot to my m.2 ssd while using legacy boot. So I changed DHCP option 67 to point to ipxe.efi for this uefi system I’m trying to capture an image on. If I turn legacy boot on temporarily to capture the image, and then change back to uefi boot, my base image computer will no longer boot, just going to a bluescreen that tells me inaccessible boot device.
My next problem is: when I try to uefi pxeboot with RAID On for capturing my image, I get an error message that says: cannot find disk on system (get hard disk). I thought I could just change my UEFI settings to AHCI, capture the image, and then change back to RAID on. When doing this, I again receive bluescreens saying inaccessible boot device.