Chainloading failure: Toshiba Tecra C40-C UEFI & Samsung SSD MZNLF128HCHP-000

[mabarton]

I am attempting to image 100 new Toshiba Tecra C40-C computers running Windows 10.

They have UEFI based systems and SSDs. The SSD is an M.2 Samsung MZNLF128HCHP-00.

I am able to iPXE and get to the Fog menu and register the computers. However, they will not boot back to the SSD but says “chainloading failure.”

Also, I am able to schedule a task and begin uploading an image but that fails at the end, too.

I began using Fog in September and have successfully imaged many machines in legacy mode or BIOS with no trouble but this is a real problem.

I need to figure this out because we need all of these computers by August 1st.

Thank you for your help,
Melissa

[george1421]

I guess the first question is what version of fog are you using? (hint: look about the cloud on the FOG management page).

Are these traditional ssd (sata) drives or M.2 drives?

Will the images machines boot if you take PXE out of the boot order?

[edit] Slightly off topic, since you now have a mix of uefi and bios (legacy) systems if your dhcp server is linux or Windows 2012 you can make the dhcp server issue the right boot file depending on the target system.

[mabarton]

This post is deleted!

[george1421]

A quick look up of the MZNLF128HCHP-00 drive, its a M.2 device. You will need to be on the trunk build post (git) r6500 (I think).

[mabarton]

@george1421 1.2.0 upgraded to trunk on Ubuntu 14.04

[george1421]

@mabarton said in Chainloading failure: Toshiba Tecra C40-C UEFI & Samsung SSD MZNLF128HCHP-000:

@george1421 1.2.0 upgraded to trunk on Ubuntu 14.04

OK, what release? (numbers by cloud on web gui page)

In regards to the chain load failure, you may need to update the host record for these specific computers. You will need to change the uefi exit mode field. You will have to test each of the uefi exit modes until you find the one that works for you.

[mabarton]

@george1421

They are M.2

The machine boots fine when not in PXE

[mabarton]

@george1421 I have tested each mode some give me the chainloading issue and some give me no valid OS.

Running Version 8291
bzImage Version 4.6.2
bzImage32 4.6.2

[george1421]

@mabarton Just for clarity these are uefi systems, so you adjusted the uefi exit mode in the host record? The bios exit modes won’t apply here.

[mabarton]

This post is deleted!

[mabarton]

The PXE, Fog Menu (FOS?), and Chainloading failure.

[george1421]

@Developers I had a lengthy chat session with the OP. To summarize the situation here is where it is.

The OP has a 100 (first in the environment) uefi system, with gpt disk structure on a M.2 ssd drive. The OP is trying to capture a Windows 10 reference image using a current release of the FOG trunk. The uefi target system boots into FOS and begins to copy the image off the ssd drive, but it fails near the end of the image capture (the OP has agreed to snap a picture of the actual error with a mobile phone and post the image to this thread). The reference image the OP is trying to capture is a Factory installed image that has been customized for the OPs environment. FWIW this image also contains a factory installed restore partition.

Another part of the puzzle here is that FOG menu will not exit properly and boot the system. If the OP changes the firmware so that the target boots directly to the hard drive the device boots OK. The OP has tested all FOG UEFI exit modes with no success. None yield a system that boots.

At this point the OP has already tried most things before I suggested them. When I exited the chat the OP was attempting to clone the disk with clonezilla to see if its a partclone issue or something else with fog.

At this point I’m out of ideas on how to verify the disk structure without damaging the content of the reference image. I’m suspecting there is a corrupted partition table or that factory restore partition is gumming up the capture (wouldn’t be the first time I saw that issue).

[mabarton]

@george1421
I use DHCP from the fog setup. I have an isolated network.

[george1421]

@mabarton Just for clarity, the picture you posted appears to be a pxe boot issue, where did that come from? We’d like to see a screen shot of the image capture error.

[mabarton]

@george1421
The three pics are the order in which it fails.

1. PXE booting
   2)FOG menu
   3)Chainloading failure (when leaving the Fog menu after the 3 sec.)

The other picture with mostly a black screen is the Raw image failure at the end of the cloning process.

I will submit more pics of the different exits and what they do.

[george1421]

@mabarton Lets not focus on the exit modes right now. I think they are all related. But lets focus on image capture. Because if you can’t capture the image, the exit mode issue is a moot point. A clear image of the capture error will give the devs something to reference.

[Tom Elliott]

@george1421 the pic shows ftp issues for image capture

[Tom Elliott]

@george1421 uefi exit should be handled by rEFInd type but it needs a Config file for it as well.

[mabarton]

This is when I attempted a Raw image. At the end this came up

[Wayne Workman]

Looking at the picture that has FTP related messages, the upload script can authenticate but cannot enter into the ftp root directory - which is /home/fog. This is exactly what the error says in fact.

Troubleshooting should focus on this directory. Does it exist? What are the permissions?

Please post the output of this command:
ls -lahRt /home/fog