RC19 : Capture message "Attempting to check in"

[Tom Elliott]

Already fixed and pushed out. Please update.

[Matthieu Jacquart]

I don’t have this message anymore but I launch capture task 1 hour ago on the computer and there’s just this into /dev folder…

I’m going to see directly on the computer in few minutes…

[Tom Elliott]

@Matthieu-Jacquart

You’re probably going to need to reupload as it doesn’t appear to have all of the data yet. Like the system is currently re-uploading, or in the process of uploading.

[Matthieu Jacquart]

I tried but this time I’ve got an error message about size disk (can’t be bigger than…)
fdisk -l give me 30GB for main partition on a 128GB SSD disk…
What is the command to revert to RC-18 ?

[Matthieu Jacquart]

Here is the problem each time I try to upload image…

[Tom Elliott]

@Matthieu-Jacquart Reverting will do you no good.

Essentially it’s not seeing how much size will be available. I’ll take a look to see if there’s anything I can do to fix this. It shouldn’t have a problem though.

[Matthieu Jacquart]

@Tom-Elliott Each time I’ve got error message at upload (New size won’t be bigger than the device size) I’ve got this next reboot

Even if I resize disk on windows this is always same problem…

[Tom Elliott]

@Matthieu-Jacquart I’ve found the issue. I added more liberalized error checking to the way ntfsresize handles things so as to hopefully prevent breaking upload disks. While they do appear to be working, the “order of operations” was not properly taken into account due to me being a total imbecile.

[Wayne Workman]

I think it’s this:

@Tom-Elliott said in PC unbootable after capture fails:

@dolf, @Wayne-Workman, @Sebastian-Roth

I’ve updated the base code for the inits.

In particular:

https://github.com/FOGProject/fogproject/commit/4caa4d679bd3a23a17e7923dd75b22ce4406c8e8

@dolf, I think we had the right approach, I just limited the calls for checks uninentionally.

If you look at the link I posted, you’ll see what I’ve added. Basically we had the "If target_size < device_size, and all the good suggestions you made.

We even had the elements that checked for success/fail etc…

However, I’ve added code in an attempt to more suitably test this. I will double check for more things just to ensure things are a bit better hashed out.

Please re-run the installer and the inits will have the modified code.

[Tom Elliott]

@Wayne-Workman I knew where about it was introduced. I just had bad order of operations.

I was checking error status before I introduced it to the case statement.

[Tom Elliott]

This issue is now more appropriately addressed in the latest and greatest. No, you don’t need to pull to get them, just re-run the installer and you will be fine.

[Matthieu Jacquart]

And no, this isn’t work… Maybe my image is broken, I’ll test on another one tomorrow…

[Matthieu Jacquart]

Ok it’s fine with last SVN

[x23piracy]

Hi,

same issue here with latest RC19, what can i do?

Regards X23

[Matthieu Jacquart]

@x23piracy You’ve made a git pull ? It works for me with svn 6002

[x23piracy]

@Matthieu-Jacquart yes did so just some seconds ago working again

Regards X23