Windows 11 | 65x HP Z2 Tower G1i | UPDATE -
-
This post is deleted! -
@Tom-Elliott
clonzilla started
Gained “root” privileges using sudo su
Ran lsblk -pdno => BNE7N774610407R40 identified as the system disk.
Entered into the FOG GUI
An attempt to clone the device results in the following error
Even deleting the PC from the database and adding it again did not solve the problem.
I’m not in the office right now or tomorrow, so I won’t be able to check the debug mode until Monday.
So far, this has happened with exactly one PC (I haven’t tried cloning the other 38 PCs yet). I followed the exact same procedure for the 23 devices I’ve already cloned, and everything works fine on those. This error has only occurred with PC115CAD so far. -
@kratkale the last 0 is an O (ohhhhh) not a 0 (zero)
-
yes - you are right …
-
@kratkale Did changing the serial on the host in question get it imaging to the right drive?
-
@Tom-Elliott
I was for a coffy - when I came back …
-
@kratkale If you update the the latest verison of working-1.6, does this error go away?
-
@Tom-Elliott
This bar is missing in multicast Task
-
@Tom-Elliott
it works the single Cast with PC115CAD - it was tho old 0O problem thanksNo errors with database and so on - like it was in multicast - reported …
fog client will now be installed after cloning - first try -
I’m using a simulation but I’m still seeing percent for mutlicast tasks.
-
Now there is the bar …
Error after multicast session:
Installation of fog client worked
Here the used script:
Still Problem with security token
Reset Encryption Data for PC111CAD
workingTomorrow I’ll reset Encryption Data during the cloning process …
-
@kratkale So, just to make sure:
Things are working (though you are getting a visual error saying something failed when it really didn’t?)
Otherwise things are functioning mostly correctly now, right?
-
@kratkale Also just pushed code I hope should address the issue with Multicast Task race condition which I think is the problem you’re seeing.
Basically when the multicast task starts to clear out it updates the reliant tasks to complete, but it’s doing this before your machine gets to do it’s checkout process which makes it show as “complete” but then when it tries to clear itself out, it’s already clear causing it to say there is no task available to complete causing the message you’re seeing.
I’ve added code to hopefully get around that if you’re willing to test?
Also the latest working-1.6 has the Sun/Moon now and you can have dark mode (if you’re one - like me - who doesn’t want burned cornea’s
)
