#439 "Box" is an unknown partition device. Program terminated..

[Micha]

I'm really sorry, but this issue appears to keep cropping up. Is it really that hard to escape whatever strings are causing the problem? It is really difficult to trust this software for backup/restore if it keeps failing every couple of years over something as trivial as a space character..

I have used the latest versions of clonezilla from Kali linux (5.15.25-1) as well as the latest Clonezilla Live CD (clonezilla-live-3.3.1-35-amd64.iso).

I have gone through all the troubleshooting steps from previous tickets raising this issue, and cannot find any device or partition which has any spaces in any of its labels, strings, or other ids.

Attached log from "ocs-blk-dev-info".

Please let me know what else I can provide you with to try to track down the root cause.

[Micha]

FWIW, I confirm that Clonezilla Live CD 3.1.2.9 works fine.

[Steven Shiau]

Give me some time, since I am busy these days.
However, there are some ways you can avoid that, please check:
https://sourceforge.net/p/clonezilla/bugs/429/

[Steven Shiau]

For those using Ventoy 1.1.11 to create Clonezilla live USB stick, please update your Clonezilla live iso >= 3.3.2-22 or 20260418-*:
https://clonezilla.org/downloads.php
We have implemented a mechanism to avoid the issue.
Let us know the result. Thanks.

[Micha]

Thank you; I will try the new version when I'm back home (apologies for the slow reply, I'm now on a dive trip) which will be in a couple of weeks; sorry.

I -did- read the issue 429; as I said, there was not a single space anywhere in any of my partition or other labels, which seems to have been the root cause of that issue. Again, if spaces cause problems, simply replacing them with an underscore or a "%20;" html escape sequence or whatever would fix them causing problems in whiptail or other dependencies. Although the proper fix would be for those dependencies to be passed properly escaped strings or have bug-reports issued against them in turn as appropriate..

Anyway, much appreciated your prompt reply and workaround, I will try it as soon as I get home!