Arghhh, Surface EFI partition. I got it copying over but that was a pain. Recovery partition next.
Posts
-
RE: Surface 4 Network boot and Imageposted in Hardware Compatibility
-
RE: Surface 4 Network boot and Imageposted in Hardware Compatibility
Testing capture and cloning now that I have most of the kinks worked out. Will report back.
-
RE: Surface 4 Network boot and Imageposted in Hardware Compatibility
Yep that worked, but what is that?
I am assuming it is just finding the boot partition on the hardware EFI
-
RE: Surface 4 Network boot and Imageposted in Hardware Compatibility
Excuse me I changed it to REFIND_EFI
-
RE: Surface 4 Network boot and Imageposted in Hardware Compatibility
@Tom-Elliott I changed it to SANBOOT and it worked. Testing again to verify
-
RE: Surface 4 Network boot and Imageposted in Hardware Compatibility
@Tom-Elliott Back to Chainloading failed
-
RE: Surface 4 Network boot and Imageposted in Hardware Compatibility
@Tom-Elliott OK that is causing it to loop on the menu over and over.
I am trying GRUB_FirstHDD
-
RE: Surface 4 Network boot and Imageposted in Hardware Compatibility
OK next snag, I was able to upload the image to the FOG server, no probems there, did all four partitions on a out of the box Surface 4.
Once it reboots and goes to teh FOG menu and I let it sit through the 3 second screen I get the following error:
Chainloading failed, hit ‘s’ for the iPXE shell
Any ideas?
-
RE: Surface 4 Network boot and Imageposted in Hardware Compatibility
OK little update here. This is the steps as I am taking them.
Hardware in use:
SP4 docking station
SP4 set to boot form network then USB then internal storage
Scope option for DHCP using ipxe.efiOnce the SP4 boot and downloads NBP file it goes to FOG menu without issue (Thank you Tom for seeing my stingy server habits)
Clicking Full Register Host
I am not able ot hit ? on image selection but if I know the number and enter it, it works jsut fine. I am not able ot use default options on some of the menus I have to enter Y/N or wit will just loop.
After entering all information I am able to see it registered in FOGSo DISCO. Now I need to figure out how to clean up the partitioning. But one thing at a time.
-
RE: Surface 4 Network boot and Imageposted in Hardware Compatibility
Server running very slow after upgrade top results below:
-
RE: Surface 4 Network boot and Imageposted in Hardware Compatibility
OK first test after upgrading is the following:

It doesn’t register the device but does dump some data and then drops me to a prompt.
-
RE: Surface 4 Network boot and Imageposted in Hardware Compatibility
OK this morning I am updating the FOG server to latest trunk off of SVN and replacing the .pxe files with the old ones. Lets see how this goes.
-
RE: Surface 4 Network boot and Image posted in Hardware Compatibility
-
RE: Surface 4 Network boot and Imageposted in Hardware Compatibility
@Tom-Elliott OK test two run, same result. I am seeing the USB nic but only after it gets into the Registration part. Now need ot find a way for FOG to see the HDD.
-
RE: Surface 4 Network boot and Imageposted in Hardware Compatibility
@Tom-Elliott said:
mode=manreg has_usb_nic=1
OK running the test again. I am gonna setup a live feed so I dont have to keep uploading LOL. Twitch FOG setup Screening
-
RE: Surface 4 Network boot and Imageposted in Hardware Compatibility
When I take that option out and boot from network to the docking station I am getting this:

So I am getting somewhere. I am thinking the ipxe.efi file is good with the the docking station and it gets through to the menu but maybe its the kernel that cant see the drive?