Eruthon

Eruthon

@sebastian-roth
Changed the host properties:

Scheduled as debug task:

iPXE initializing:
IMG20210512150857 (Medium).jpg

Variable dump from FOG:
IMG20210512150930 (Medium).jpg

FOG prep:

Moving of nvme0n1p4; the partition 4 in the “after” table has corrected start address:

Partclone:

Also the d1.minimum.partitions looks correct:

label: gpt
label-id: D7496BEB-B8A7-4BDA-84D1-A924BDEB9789
device: /dev/nvme0n1
unit: sectors
first-lba: 34
last-lba: 1953525134
sector-size: 512

/dev/nvme0n1p1 : start=        2048, size=      204800, type=C12A7328-F81F-11D2-BA4B-00A0C93EC93B, uuid=25DAF354-4243-415E-9163-8AA61F158BBC, name="EFI system partition", attrs="GUID:63"
/dev/nvme0n1p2 : start=      206848, size=       32768, type=E3C9E316-0B5C-4DB8-817D-F92DF00215AE, uuid=3C51C90A-87D5-4C14-9D3E-378D17FF0882, name="Microsoft reserved partition", attrs="GUID:63"
/dev/nvme0n1p3 : start=      239616, size=    61985414, type=EBD0A0A2-B9E5-4433-87C0-68B6B72699C7, uuid=EE6CC19C-A52C-4909-B57D-E2915E54BB55, name="Basic data partition"
/dev/nvme0n1p4 : start=    62225408, size=      884224, type=DE94BBA4-06D1-4D40-A16A-BFD50179D6AC, uuid=17790088-AF7B-4D4B-B155-8C7E9DAFE516

Edit:
Now I’m triying to deploy it to the smaller SSD and it works so far… interesting that I didn’t change anything since when it wasn’t working.

Edit:
It succesfully deployed the image to the SSD and Windows booted without problems.

Eruthon

Great, it works sorry for the bother

Eruthon

Good day,

I would like to ask if it’s possible to change the way progress bar data are shown visually.
I imagine it being centered (and properly contrasted against background colors) within the whole progress bar, not just the green part.

Reason: e.g. if I create a task with WOL on remote PC, I’d like to see the required time for the task as soon as it begins, not 5 minutes after the numbers are more apart and readable.

Can it be somehow edited manually in an easy way by me? Or would it be better to wait for FOG 1.6 (in case it’s being polished in that version)?

Eruthon

@george1421 Great, thank you

Eruthon

Your guidance has been very helpful and spot on. It works exactly as I wanted: the grubx64.efi is now shown in rEFInd menu after “Booting…”

But if I understand correctly, wouldn’t editing only the original refind.conf file by adding Debian option solve the problem, too? Maybe it could be added to the next release of FOG out of the box, because Ubuntu is already there.

Eruthon

Re: IPXE exit not lauching BIOS UEFI next boot option

I have similar problems as the one above.

Is there a way to reconfigure settings for the EXIT method to boot Linux instead of Windows?

I want to boot grub as default, from there have grub configured to start Win10 (Windows Boot manager) as default (as Win10 doesn’t allow booting Linux from its Manager).
My UEFI boot order is:

UEFI IPv4 PXE
Debian grubx64.efi
Windows Boot Manager

If I choose:

REFIND-EFI Exit Type, the PC boots into Win10 automatically
EXIT Exit Type, the PXE boot says “Chainloading failed”

Eruthon

@sebastian-roth, it’s working! Managed to deploy the image from 1TB to 240GB, hopefully it will work for others, too. Thank you verymuch for your time! Should I post some files here for reference?

Eruthon

@sebastian-roth, thank you, files downloaded and ready, will report back with results tommorow!

Eruthon

@sebastian-roth In the heat of the moment I tried to edit the data partition size in that file to try it that way; I didn’t think it would work, but tried it as last resort. The issue persisted, also the log during deploying showed the same amount of blocks that were problematic because of smaller disk size.

Sadly I didn’t back up the original file, but before the change I saw that the d1.partitions had the same values as the d1.minimum.partitions, so I copied the values from d1.partitions back after trying the mentioned experiment.

d1.minimum.partition for the new 21H1 image:

label: gpt
label-id: D7496BEB-B8A7-4BDA-84D1-A924BDEB9789
device: /dev/nvme0n1
unit: sectors
first-lba: 34
last-lba: 1953525134
sector-size: 512

/dev/nvme0n1p1 : start=        2048, size=      204800, type=C12A7328-F81F-11D2-BA4B-00A0C93EC93B, uuid=25DAF354-4243-415E-9163-8AA61F158BBC, name="EFI system partition", attrs="GUID:63"
/dev/nvme0n1p2 : start=      206848, size=       32768, type=E3C9E316-0B5C-4DB8-817D-F92DF00215AE, uuid=3C51C90A-87D5-4C14-9D3E-378D17FF0882, name="Microsoft reserved partition", attrs="GUID:63"
/dev/nvme0n1p3 : start=      239616, size=    77211472, type=EBD0A0A2-B9E5-4433-87C0-68B6B72699C7, uuid=EE6CC19C-A52C-4909-B57D-E2915E54BB55, name="Basic data partition"
/dev/nvme0n1p4 : start=  1952640000, size=      884224, type=DE94BBA4-06D1-4D40-A16A-BFD50179D6AC, uuid=17790088-AF7B-4D4B-B155-8C7E9DAFE516

The starting lba of the partition 4 is the same as in the posts of the 20H2 image you can see in my earlier posts. My point is I don’t see any differences between the working 20H2 image and the new 21H1 image, except for the size of the data partitions which is, ofc, expected.

Also I wonder if the name of the issue here could be changed as it’s not longer a suitable name for the problem here. Could be changed to sth regarding the gpt partitions, so it wouldn’t sound like a problem with the PC model mentioned in the title.

Eruthon

After some time I tried to deploy new Win10 21H1 image with some pre-installed software again with UEFI and GPT… also using the new init… sadly it didn’t capture the partitions correctly again… lost my nerve, so didn’t try the debug mode, but will try next week

Eruthon

@sebastian-roth
Thank you for the appreciation!

Also maybe I just overlooked something, maybe edited wrong host, as I had multiple tabs and didn’t keep track of it. Otherwise I don’t see any other reason for it not working on the first try.

Eruthon