Clear block out of boundary
-
@saftkartoffel When you say stuck, do you mean the byte/sector count in the blue partclone screen did not move any further? For how long did you wait? Did the speed figure go down to zero?
-
@Sebastian-Roth said in Clear block out of boundary:
@saftkartoffel When you say stuck, do you mean the byte/sector count in the blue partclone screen did not move any further? For how long did you wait? Did the speed figure go down to zero?
Left it overnight, in the morning the speed is getting lower if I remembered correctly but not to zero
What i meant stuck is the progress bar
-
@Sebastian-Roth said in Clear block out of boundary:
@saftkartoffel Yes sure you can multicast a raw image.
Well I got Fatal: error unknown request type :: Null
Got a quick fix? need to do the imaging asap
-
@saftkartoffel As I see you are using the USB boot stuff. Not part of the official FOG code but I am sure we can help you! Please post the complete grub configuration you have in
boot/grub/grub.cfg
on your USB key. -
@saftkartoffel said in Clear block out of boundary:
Well I got Fatal: error unknown request type :: Null
Got a quick fix? need to do the imaging asapThis is one of the caveats of usb booting. You should reread the instructions for building the FOS Linux USB boot disk. It says that you MUST schedule the task first in the Web UI THEN select option 1 on the grub boot menu. If you don’t you will get the error about Unknown request type Null.
-
@george1421 said in Clear block out of boundary:
@saftkartoffel said in Clear block out of boundary:
Well I got Fatal: error unknown request type :: Null
Got a quick fix? need to do the imaging asapThis is one of the caveats of usb booting. You should reread the instructions for building the FOS Linux USB boot disk. It says that you MUST schedule the task first in the Web UI THEN select option 1 on the grub boot menu. If you don’t you will get the error about Unknown request type Null.
Did exactly like that, the unicast works flawlessly but the multicast task doesn’t seems to be recognized bye the hosts
-
@Sebastian-Roth said in Clear block out of boundary:
@saftkartoffel As I see you are using the USB boot stuff. Not part of the official FOG code but I am sure we can help you! Please post the complete grub configuration you have in
boot/grub/grub.cfg
on your USB key.I only changed the myfogip
set myfogip=10.35.148.134 set myimage=/boot/bzImage set myinits=/boot/init.xz set myloglevel=4 set timeout=-1 insmod all_video menuentry "1. FOG Image Deploy/Capture" { echo loading the kernel linux $myimage loglevel=$myloglevel initrd=init.xz root=/dev/ram0 rw ramdisk_size=275000 keymap= web=$myfogip/fog/ boottype=usb consoleblank=0 rootfstype=ext4 echo loading the virtual hard drive initrd $myinits echo booting kernel... } menuentry "2. Perform Full Host Registration and Inventory" { echo loading the kernel linux $myimage loglevel=$myloglevel initrd=init.xz root=/dev/ram0 rw ramdisk_size=275000 keymap= web=$myfogip/fog/ boottype=usb consoleblank=0 rootfstype=ext4 mode=manreg echo loading the virtual hard drive initrd $myinits echo booting kernel... } menuentry "3. Quick Registration and Inventory" { echo loading the kernel linux $myimage loglevel=$myloglevel initrd=init.xz root=/dev/ram0 rw ramdisk_size=275000 keymap= web=$myfogip/fog/ boottype=usb consoleblank=0 rootfstype=ext4 mode=autoreg echo loading the virtual hard drive initrd $myinits echo booting kernel... } menuentry "4. Client System Information (Compatibility)" { echo loading the kernel linux $myimage loglevel=$myloglevel initrd=init.xz root=/dev/ram0 rw ramdisk_size=275000 keymap= web=$myfogip/fog/ boottype=usb consoleblank=0 rootfstype=ext4 mode=sysinfo echo loading the virtual hard drive initrd $myinits echo booting kernel... } menuentry "5. Run Memtest86+" { linux /boot/memdisk iso raw initrd /boot/memtest.bin } menuentry "6. FOG Debug Kernel" { echo loading the kernel linux $myimage loglevel=7 init=/sbin/init root=/dev/ram0 rw ramdisk_size=275000 keymap= boottype=usb consoleblank=0 rootfstype=ext4 isdebug=yes echo loading the virtual hard drive initrd $myinits echo booting kernel... } menuentry "7. FOG iPXE Jumpstart BIOS" { echo loading the kernel linux16 /boot/ipxe.krn echo booting iPXE... } menuentry "8. FOG iPXE Jumpstart EFI" { echo chain loading the kernel insmod chain chainloader /boot/ipxe.efi echo booting iPXE-efi... }
-
@saftkartoffel said in Clear block out of boundary:
but the multicast task doesn’t seems to be recognized bye the hosts
At the current time you can not use multicast with the USB boot environment. In theory it should be possible but we will need to get GRUB to prompt for the multicast task name. So “today” only unicast is supported when booting via usb.
I do have to ask why are you booting via USB? Is PXE booting not supported by your hardware?
-
@george1421 said in Clear block out of boundary:
@saftkartoffel said in Clear block out of boundary:
but the multicast task doesn’t seems to be recognized bye the hosts
At the current time you can not use multicast with the USB boot environment. In theory it should be possible but we will need to get GRUB to prompt for the multicast task name. So “today” only unicast is supported when booting via usb.
I do have to ask why are you booting via USB? Is PXE booting not supported by your hardware?
Unfortunately no, is there a way for imac to boot directly from network though? And more notes for further research. The unicast now does 100% on other identical machine as the golden master, the previous stuck percentage at partclone is done on an older machine but with the same size of hdd. And the final result is a hfs+ formated partitions. So I guess the raw capture doesn’t capture the image as APFS. luckily a time machine backup will fix the format back to apfs
-
@george1421 said in Clear block out of boundary:
At the current time you can not use multicast with the USB boot environment…
I keep forgetting the drawbacks of the USB boot stuff. Now that the latest release is out I might have a bit more time to look into this and maybe make it work. Though this won’t be today.
@saftkartoffel said:
And the final result is a hfs+ formated partitions. So I guess the raw capture doesn’t capture the image as APFS. luckily a time machine backup will fix the format back to apfs.
I can’t imagine RAW capture will convert a partition formated with APFS to HFS+ or anything like that unless APFS has parts of the filesystem stored in NVRAM - which would be really strange.
-
@saftkartoffel Are you willing to try something different to see if we can jump into iPXE via USB? If we can get the iPXE menu loaded then multicasting is an option.
Follow these instructions. https://forums.fogproject.org/topic/6350/usb-boot-uefi-client-into-fog-menu-easy-way
Understand this is an idea and have no understanding if it will work under mac hardware. But the idea is to load iPXE much like we load GRUB from the usb stick.
-
@Sebastian-Roth said in Clear block out of boundary:
I keep forgetting the drawbacks of the USB boot stuff. Now that the latest release is out I might have a bit more time to look into this and maybe make it work. Though this won’t be today.
I looked into this and grub does have a readline (or similar) that we can grab the task name with. I simply haven’t had time my self to script this up yet. In theory it should work.
-
@saftkartoffel going by your photo i am experiencing a very similar if not identical issue, attempting to capture an image from a 2020 MBA using usb key booting with bzImage.T2 (renamed to bzImage)
-
@saftkartoffel @kudlab While I can’t test USB booting here in my VM setup quickly I would ask you guys to try out using the last menu point from your USB key GRUB menu
8. FOG iPXE Jumpstart EFI
after you’ve scheduled a multicast task.