Posts made by Chris Whiteley

@Sebastian-Roth I am sorry that I didn’t post anything or submit my feedback. As a SysAdmin it is hard sometimes to find the time to start trying to dig into issues when you are busy and you know that going back to the version you had fixes the issue and you can move on. You guys have always been incredible and you have a team of people here that truly wants to help. I so appreciate the time and energy you guys spend tirelessly making this into a product I recommend to anyone that will listen to me.

@Sebastian-Roth Thanks for the heads up! I have not done any imaging since upgrading. I held off on doing 1.5.7.X since I had that issue with speed. I was hoping that 1.5.8 was going to be different. Luckily I have it as a VM and I just reverted my snapshot so I could do some testing with you guys.

@Sebastian-Roth I have done some testing and the version of partclone is v0.3.13. I have mostly NVMe machines which will make it difficult to want to update to 1.5.8. 1.5.7 did not have the same issues with NVMe drives. I also tested it on one of my machines that I put a normal SSD in and that machine was also very slow. It is my imaging machine that I make my golden image on and it is usually around 14 GB/min download and now it is 9.50 GB/min. So it looks like in both scenarios that it is slow. The only other thing is the same is that they are all Dell machines, optiplex and latitudes.

Thanks for reaching out!

I am having significant speed differences during imaging from 1.5.7 to 1.5.8. I noticed this when I tried some of the 1.5.7.X revisions and so I went back to 1.5.7. I tried the update and here was the speed difference:

1.5.7 - 10.54 GB/min
1.5.8 - 7.23 GB/min

Is there a reason why there is such a drastic change in speed?

Just curious.

Thanks,

Truth table:

bzImage version	init version	partclone	buildroot	speed	tested by SR
4.19.101	1.5.8	0.3.13	2019.02.9	1.4.4	slow
4.19.65	1.5.7	0.2.89	2019.02.1	1.3.5	fast
4.19.101	1.5.8+pc0.2.89	0.2.89	2019.02.9	1.4.4	slow
4.19.101	1.5.7	0.2.89	2019.02.1	1.3.5	fast
4.19.101	1.5.7+pc0.3.13	0.3.13	2019.02.1	1.3.5	fast
4.19.101	1.5.7+zstd1.4.4	0.2.89	2019.02.1	1.4.4	fast
4.19.101	1.5.9	0.3.13	2020.02.6	1.4.5	slow
…	…	…	…	…	…

Full test logs…

@george1421 Thanks for the response. I think I might’ve actually figured it out. If you Legacy PXE boot, it errors out on a UEFI based machine. However, if you use the Network Stack PXE boot (UEFI), it will correctly boot. The DVD does work for both UEFI and Legacy. I don’t know why I didn’t think to try that first.

Thanks for the help!

Hey All,

I don’t know if this has been documented anywhere, but I have searched around the forums and have been unable to find something that resembles what I am looking for. I would like to use the UEFI boot option in the FOG menu for Hiren’s Boot CD (PE Environment). The one I am using only works for BIOS machines and most of the ones I have now are not that way. Here is what my current menu says:

set tftp-path tftp://${fog-ip}
set pe-path ${tftp-path}/os/winpe
kernel ${tftp-path}/wimboot gui
imgfetch --name BCD ${pe-path}/BCD BCD
imgfetch --name boot.sdi ${pe-path}/boot.sdi boot.sdi
imgfetch --name boot.wim ${pe-path}/boot.wim boot.wim
boot || goto MENU

What can I change to make this work for UEFI? Is it just the memdisk iso raw?

Thanks!

@Sebastian-Roth That worked! Thanks so much! It did the resize and it looks good from within Windows.

@Sebastian-Roth I got this error this morning from the new file:

@Sebastian-Roth Thanks for the update. I will look for this tomorrow and wait to hear word from you. Thanks again,

@Sebastian-Roth Thanks for working on it! I am just glad that it wasn’t me doing something wrong I tried everything to make it work. I really appreciate everything you guys do to make an amazing product!

@Sebastian-Roth

Sorry it took so long to get back to you. Here are the updated pictures with the kernel args:

@Sebastian-Roth

Yes I messed up. Here is the right image:

d1.fixed_size_partitions:

:1:1

d1.minimum.partitions:

label: dos
label-id: 0xbb1896a4
device: /dev/nvme0n1
unit: sectors

/dev/nvme0n1p1 : start=        2048, size=     1124352, type=7, bootable
/dev/nvme0n1p2 : start=     1126400, size=    77984264, type=7

d1.partitons:

label: dos
label-id: 0xbb1896a4
device: /dev/nvme0n1
unit: sectors

/dev/nvme0n1p1 : start=        2048, size=     1124352, type=7, bootable
/dev/nvme0n1p2 : start=     1126400, size=    87136208, type=7

@Sebastian-Roth

Here are the outputs and what was seen at the end:

@Sebastian-Roth

d1.minimum.partitions:

label: gpt
label-id: 0EF8BFB0-8547-11E8-BD1D-1866DA4A79D9
device: /dev/sda
unit: sectors
first-lba: 34
last-lba: 500118158

/dev/sda1 : start=        2048, size=     1021952, type=DE94BBA4-06D1-4D40-A16A-BFD50179D6AC, uuid=B09CBC62-337C-4F76-AB41-5CC15BC19BCE, name="Basic data partition", attrs="RequiredPartition GUID:63"
/dev/sda2 : start=     1024000, size=      204800, type=C12A7328-F81F-11D2-BA4B-00A0C93EC93B, uuid=5125EE82-07EE-400C-B923-455E1DF89F0A, name="EFI system partition", attrs="GUID:63"
/dev/sda3 : start=     1228800, size=       32768, type=E3C9E316-0B5C-4DB8-817D-F92DF00215AE, uuid=8F38AD90-28EA-433F-B566-7CFF947E5A42, name="Microsoft reserved partition", attrs="GUID:63"
/dev/sda4 : start=     1261568, size=    70461368, type=EBD0A0A2-B9E5-4433-87C0-68B6B72699C7, uuid=C7A3FCC5-4446-4D7D-80DA-8A6A37FC797B, name="Basic data partition"

d1.fixed_size_partitions:

:2:3:1

d1.partitions:

label: gpt
label-id: 0EF8BFB0-8547-11E8-BD1D-1866DA4A79D9
device: /dev/sda
unit: sectors
first-lba: 34
last-lba: 500118158

/dev/sda1 : start=        2048, size=     1021952, type=DE94BBA4-06D1-4D40-A16A-BFD50179D6AC, uuid=B09CBC62-337C-4F76-AB41-5CC15BC19BCE, name="Basic data partition", attrs="RequiredPartition GUID:63"
/dev/sda2 : start=     1024000, size=      204800, type=C12A7328-F81F-11D2-BA4B-00A0C93EC93B, uuid=5125EE82-07EE-400C-B923-455E1DF89F0A, name="EFI system partition", attrs="GUID:63"
/dev/sda3 : start=     1228800, size=       32768, type=E3C9E316-0B5C-4DB8-817D-F92DF00215AE, uuid=8F38AD90-28EA-433F-B566-7CFF947E5A42, name="Microsoft reserved partition", attrs="GUID:63"
/dev/sda4 : start=     1261568, size=   498856448, type=EBD0A0A2-B9E5-4433-87C0-68B6B72699C7, uuid=C7A3FCC5-4446-4D7D-80DA-8A6A37FC797B, name="Basic data partition"

I am having an issue where after imaging the machine with a Windows 10 resizable image, it is not making the image fill back out to the size of the drive. It is just staying the same as the image size. This is how I have always done it. Has something changed? I have tried both iterations of 1.5.6 and 1.5.6.2.

Process:
-> Create Pristine Windows 10 Image
-> Sysprep and reboot for upload and image is chosen as Windows 10 and resizable
-> Deploy image and the disk size doesn’t expand

Thanks,

@george1421 You are the man! That was it! I made the changes and the menu came up. It was the - before the Windows 10 1809 - Office 2013 image

#!ipxe
set fog-ip <ip address>
set fog-webroot fog
set boot-url http://${fog-ip}/${fog-webroot}
goto MENU
:MENU
menu
item Windows101809b - Windows 10 1809 (208)
item -Windows101809-Office2013 - Windows 10 1809 - Office 2013 (209)
item return Return to menu
choose --default Windows101809b --timeout 10000 target && goto ${target}
:Windows101809b
set imageID 208
params
param mac0 ${net0/mac}
param arch ${arch}
param imageID ${imageID}
param qihost 1
param username ${username}
param password ${password}
isset ${net1/mac} && param mac1 ${net1/mac} || goto bootme
isset ${net2/mac} && param mac2 ${net2/mac} || goto bootme
:-Windows101809-Office2013
set imageID 209
params
param mac0 ${net0/mac}
param arch ${arch}
param imageID ${imageID}
param qihost 1
param username ${username}
param password ${password}
isset ${net1/mac} && param mac1 ${net1/mac} || goto bootme
isset ${net2/mac} && param mac2 ${net2/mac} || goto bootme
:return
params
param mac0 ${net0/mac}
param arch ${arch}
isset ${net1/mac} && param mac1 ${net1/mac} || goto bootme
isset ${net2/mac} && param mac2 ${net2/mac} || goto bootme
:bootme
chain -ar http://<ip address>/fog/service/ipxe/boot.php##params
goto MENU

@george1421

#!ipxe
set fog-ip <ipaddress>
set fog-webroot fog
set boot-url http://${fog-ip}/${fog-webroot}
echo Invalid login!
clear username
clear password
sleep 3
cpuid --ext 29 && set arch x86_64 || set arch i386
params
param mac0 ${net0/mac}
param arch ${arch}
param platform ${platform}
param menuAccess 1
param debug
isset ${net1/mac} && param mac1 ${net1/mac} || goto bootme
isset ${net2/mac} && param mac2 ${net2/mac} || goto bootme
:bootme
chain -ar http://<ipaddress>/fog/service/ipxe/boot.php##params```

@george1421 I will clarify…This only happens from the fog menu if I choose “Deploy Image”. It won’t do it if I kick a task off from the web, or choose the image now option from the “Full Host Reg”. Does that change where you want to go with this?

@george1421 Here is the code:

#!ipxe
set fog-ip ipaddress
set fog-webroot fog
set boot-url http://${fog-ip}/${fog-webroot}
cpuid --ext 29 && set arch x86_64 || set arch i386
goto get_console
:console_set
colour --rgb 0x00567a 1 ||
colour --rgb 0x00567a 2 ||
colour --rgb 0x00567a 4 ||
cpair --foreground 7 --background 2 2 ||
goto MENU
:alt_console
cpair --background 0 1 ||
cpair --background 1 2 ||
goto MENU
:get_console
console --picture http://ipaddress/fog/service/ipxe/bg.png --left 100 --right 80 && goto console_set || goto alt_console
:MENU
menu
colour --rgb 0x00567a 0 ||
cpair --foreground 1 1 ||
cpair --foreground 0 3 ||
cpair --foreground 4 4 ||
item --gap Host is registered as FOG-test!
item --gap -- -------------------------------------
item fog.local Boot from hard disk
item fog.memtest Run Memtest86+
item fog.keyreg Update Product Key
item fog.deployimage Deploy Image
item fog.multijoin Join Multicast Session
item fog.quickdel Quick Host Deletion
item fog.sysinfo Client System Information (Compatibility)
choose --default fog.local --timeout 10000 target && goto ${target}
:fog.local
exit || goto MENU
:fog.memtest
kernel memdisk initrd=memtest.bin iso raw
initrd memtest.bin
boot || goto MENU
:fog.keyreg
login
params
param mac0 ${net0/mac}
param arch ${arch}
param username ${username}
param password ${password}
param keyreg 1
isset ${net1/mac} && param mac1 ${net1/mac} || goto bootme
isset ${net2/mac} && param mac2 ${net2/mac} || goto bootme
:fog.deployimage
login
params
param mac0 ${net0/mac}
param arch ${arch}
param username ${username}
param password ${password}
param qihost 1
isset ${net1/mac} && param mac1 ${net1/mac} || goto bootme
isset ${net2/mac} && param mac2 ${net2/mac} || goto bootme
:fog.multijoin
login
params
param mac0 ${net0/mac}
param arch ${arch}
param username ${username}
param password ${password}
param sessionJoin 1
isset ${net1/mac} && param mac1 ${net1/mac} || goto bootme
isset ${net2/mac} && param mac2 ${net2/mac} || goto bootme
:fog.quickdel
login
params
param mac0 ${net0/mac}
param arch ${arch}
param username ${username}
param password ${password}
param delhost 1
isset ${net1/mac} && param mac1 ${net1/mac} || goto bootme
isset ${net2/mac} && param mac2 ${net2/mac} || goto bootme
:fog.sysinfo
kernel bzImage32 loglevel=4 initrd=init_32.xz root=/dev/ram0 rw ramdisk_size=127000 web=ipaddress/fog/ consoleblank=0 rootfstype=ext4 storage=ipaddress:/images/ storageip=ipaddress loglevel=4 mode=sysinfo
imgfetch init_32.xz
boot || goto MENU
:bootme
chain -ar http://ipaddress/fog/service/ipxe/boot.php##params ||
goto MENU
autoboot```