Error during capture

[andreiv]

I’m getting the error in the attached picture while capturing:

https://photos.app.goo.gl/khaiFnJFut9R8bt29

However, it doesn’t seem to have any negative impact on the capture process.

[Sebastian Roth]

@andreiv Thanks for letting us know. As I am working on the inits I will look into fixing this as well.

[Sebastian Roth]

@andreiv Sorry but I can’t figure this out without having more information. Can you please schedule another capture task. But this time hit the checkbox for debug just before you actually schedule the task in the web UI. Boot up the client, hit enter twice to get to the console and then run parted -l /dev/nvme0n1 - take a picture and post here.

[andreiv]

@Sebastian-Roth
Sure. I’ll do it tomorrow and post the screenshot.

[Sebastian Roth]

@andreiv Spoke too soon. Playing a bit more with the code I figured what is causing this. You seem to have two partitions marked with the same flag. Definitely something we should have considered in the code. Will fix this soon!

@Quazz Mind having a look as well?

[Sebastian Roth]

@Quazz All good, found and (hopefully) fixed it.

@andreiv Will let you know when new init files are built and ready to test.

[Sebastian Roth]

@andreiv Unfortunately we only have a 32 bit build of the init file ready because the 64 bit build broke for a weird reason yesterday. I will check the build logs later on and go for another round. Will update here.

[Quazz]

@Sebastian-Roth Looks good! Don’t think we thoroughly tested Linux at the time, not surprised it needed to be improved.

[Sebastian Roth]

@andreiv Ok, build is done. Was just a download hickup on sourceforge. Not a major issue. Download init.xz and init_32.xz and put into /var/www/html/fog/service/ipxe. You might rename the original ones instead of overwriting the files just in case…

Please let us know if the error messages are gone.

EDIT: The fix is now in the current inits and the flag_fix versions above linked were removed from the webserver. Please use the current inits: init.xz and init_32.xz

[andreiv]

@Sebastian-Roth
Good. I’ll do the testing tomorrow and let you know.

[andreiv]

@Sebastian-Roth
Yes, problem solved. The error is gone (sorry for the bad photo):
https://photos.app.goo.gl/ZhWkYuHLTwndZBZPA

Thanks!