@abulhol Any news on this?

@abulhol Thanks for looking into the error and fixing the issue via the github PR. Merge is done.

@abulhol Should be back up and running.

Thanks for letting us know.

@Tom-Elliott Yes, this might work, but I didn’t want to spend too much time experimenting. If somebody wants to follow up on this, that’s fine, but I won’t. 🙂

@abulhol said in Does FOG check free disk space before starting capture?:

That’s nice - but as far as I understand, it still doesn’t protect against the new image needing 10GB, but there are only 9GB left.
Right?

Yes, right, it doesn’t protect from that. We discussed different “solutions” and thought we should better keep it simple. If you are keen you can still jump in and add a more thorough check - estimating how much size the new image will need. While it is possible to do it’s not that easy because images are being compressed and other variables can vary as well.

Final update:
Replacing the hardware solved the issue.
So it was either a hardware defect, or a bug in the firmware.

@abulhol This issue should be fixed in latest dev-branch.

@abulhol Fixed in working branch, will be in the next release. Let’s see if we are able to get this out in time so people upgrading their servers from 16.04 to 18.04 won’t run into the same issue as you did.

@abulhol Fixed in working branch.

@Sebastian-Roth thanks I figured it out .