Dell 3510 with USB-C

[Wayne Workman]

@george1421 FOS typically hangs at this spot when GPT remnants are present. Debug + fixparts /dev/nvme0n1 in this case will typically fix it.

[Tom Elliott]

@Wayne-Workman I didn’t see the full picture until now. I think you’re spot on.

This used to not happen with Non-resize disks (at least not that I’m aware of.)

[george1421]

@Wayne-Workman The concern with fixparts is if it is destructive to the current disk content(??). I get the impression that the OP wants to capture the image off storage, so we don’t want to disrupt the disk structure.

[Tom Elliott]

@george1421 I think @Wayne-Workman is right.

If we need to be 100% safe, maybe try uploading a separate image under “raw” type and then try fixparts?

[JBeene]

Recorded RAW image and then tried putting it on another laptop of exact specs.

Going to do a debug capture next.

Got the following message:

[JBeene]

@george1421 I have several for testing, until I get the image built.

[george1421]

@JBeene Then on the one that failed to image. Schedule another deployment, but on the task setup window select the check mark for debug deployment. Start to image the broken target. After a bunch of text on the screen it should drop you to a command prompt on the target computer. This is the debug console.

Now follow Wayne’s post about the fixparts command. https://forums.fogproject.org/topic/7808/dell-3510-with-usb-c/8 Test to see if this fixes the disk structure on the broken target computer. After running the fixpart command key in fog and press enter. You will have to press enter after each fog step, but see if you can get all the way through imaging. If not we’ll probably need you to boot into the debug console again to run some disk inspection commands.

[Tom Elliott]

@JBeene What does the file look like on your server?

Is it in /images/3510nosysprep or is simply a file named /images/3510nosysprep?

[JBeene]

3510nosysprep is the image name.

Ran the debug and did a fixpart. It said it found remnants from a prior partition, I removed that, and then selected A for MBR option. It seems to have not wrecked data on the drive and booted back into the Audit Mode for Windows 10.

Recorded image using Multiple Partition - Single Disk No resize. Since there was no errors with that, I then put that image on another machine. It also booted up into Audit mode. I’ll run my sysprep file then record the image again and see how it works. Thank you for the help so far.

[JBeene]

Image looks to be working now. Read up on the new Fog Client before I recorded my sysprep. I really appreciate all the help!

I’ve ran into dirty partition issues before. I should’ve known I should go over the initial Dell partitions with badger blood and napalm before I build my image.

[Sebastian Roth]

@JBeene said:

Got the following message:
…

In that picture I see Args passed: /dev/nvme0n while it should be nvme0n1 I guess?!? Bu you are saying things are working now?

[JBeene]

Could it be that was a RAW image deployment error vs a multiple partition image deployment? Yes, imaging is going well.
We had to downgrade the TPM from 2.0 to 1.2, since we are not doing UEFI.