It seems your image was not saved successfully? When checking the image, did Clonezilla report which part is broken? I can not tell from the photo you shared. It looks like the image of some partition is broken?
Steven
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Sorry, late to the party... but hopefully this helps someone else.
"Broken partition images were found, or some of them are not checkable in this image"
I believe Clonezilla is just falsely reporting this as an error. Because I also got the same thing when I tried to back up my Proxmox (8.2) host too. You likely have Proxmox VM/CT "snapshots" like me which aren't technically filesystems. So when Clonezilla encounters these kinds of partitions (within the LVM), it can't identify the filesystem type so it just falls back to using the "dd' version of Partclone and does a full byte-level partition backup. If this happens, I believe this is what causes Clonezilla to freak out and display this message.
I hope this message gets clarified in the future, or at least restructured so that it knows the difference between a truly broken image versus ones that "are not checkable". Otherwise, this message is very misleading. If it's truly broken, then I believe it should remain a RED error message. But if none are "broken" and some are simply "not checkable", then it should only report these as YELLOW warning messages.
Because of this, maybe it would be better if Clonezilla would scan all partitions and attempt to identify them and report these kinds of "not checkable" warnings UP FRONT before it spends the majority of the processing time on the backup step? Or, perhaps Clonezilla/Partclone can be updated so that it could identify LVM snapshot-style partitions and then not worry about reporting these as "not checkable" in the first place?
Hopefully someone can correct me if I'm wrong on any of this, or propose a better workflow.
thanks,
Scott
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thanks for your feedback.
However, from the photo you have posted "ocs-live-error.png", I can not find which partition has issues. Could you please tell us which partition of the disk is falsely reported?
Steven
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thakns. Yes, after reading your 2nd post, I re-read your 1st post. Still I have no idea which partition has failure. By default Clonezilla won't check the unknown file system, as the photo in your 1st post. So I was wondering which partition Clonezilla failed to check.
Steven
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Sorry, I'm not the OP. I was just providing some feedback on how I think that the software's error messages or workflow should be changed to better inform users of real errors or not.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Sure, that's also what I meant.
Please let us know how to reproduce this issue in detail. In your description, we just can not identify which partition had the unknown file system and Clonezilla failed to detect that.
As I mentioned, by default Clonezilla won't check the file system integrity if it's unknown to Clonezilla. You can tell from the photo "ocs-live-error.png" in your 1st post, sdb1 won't be checked since it's dumped by dd. Clonezilla will just use dd to restore that.
Steven
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anytime Clonezilla has to end up using dd, does it always give this message at the end? "Broken partition images were found, or some of them are not checkable in this image"
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Well, "some of them are not checkable" does not include the dd case. So that's definitely different thing.
So we need your help to improve this. Please let us know how to reproduce this issue in detail.
I am wondering maybe it's related LVM thin provisioning, since you mentioned it's Proxmox.
Steven
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I did a full disk backup of my Proxmox drive and also got the same "Broken partition images were found, or some of them are not checkable in this image" message too. I didn't think to make copies of the log files as I thought Clonezilla might have copied them over to my image directory, but I don't have them any longer. However, I still have a 300+GB folder it created called "2024-08-17-17-img" in case there's anything I can attach here to help troubleshoot.
thanks,
Scott
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I think this should explain my Proxmox disk layout, sourced from my Clonezilla's image export blkdev.list file. Also uploaded to https://pastebin.com/CUx9Zwx6 . As you can tell, my Proxmox is on nvme0n1.
OK, thanks.
As I mentioned previously, Clonezilla does not support LVM thin provisioning at the moment.
We do not recommend use Clonezilla in such case.
Maybe in the future we will support it well when the required LVM tools have the functions we need.
Steven
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi All,
I create the proxmox image with some vm inside. When I clonning using Clonezilla its appear error "ocs-live-general"
It would be helpful if you all can give advices on this matter.
Please refer picture I attach.
Thanks
Ahmad
It seems your image was not saved successfully? When checking the image, did Clonezilla report which part is broken? I can not tell from the photo you shared. It looks like the image of some partition is broken?
Steven
Sorry, late to the party... but hopefully this helps someone else.
"Broken partition images were found, or some of them are not checkable in this image"
I believe Clonezilla is just falsely reporting this as an error. Because I also got the same thing when I tried to back up my Proxmox (8.2) host too. You likely have Proxmox VM/CT "snapshots" like me which aren't technically filesystems. So when Clonezilla encounters these kinds of partitions (within the LVM), it can't identify the filesystem type so it just falls back to using the "dd' version of Partclone and does a full byte-level partition backup. If this happens, I believe this is what causes Clonezilla to freak out and display this message.
I hope this message gets clarified in the future, or at least restructured so that it knows the difference between a truly broken image versus ones that "are not checkable". Otherwise, this message is very misleading. If it's truly broken, then I believe it should remain a RED error message. But if none are "broken" and some are simply "not checkable", then it should only report these as YELLOW warning messages.
Because of this, maybe it would be better if Clonezilla would scan all partitions and attempt to identify them and report these kinds of "not checkable" warnings UP FRONT before it spends the majority of the processing time on the backup step? Or, perhaps Clonezilla/Partclone can be updated so that it could identify LVM snapshot-style partitions and then not worry about reporting these as "not checkable" in the first place?
Hopefully someone can correct me if I'm wrong on any of this, or propose a better workflow.
thanks,
Scott
Thanks for your feedback.
However, from the photo you have posted "ocs-live-error.png", I can not find which partition has issues. Could you please tell us which partition of the disk is falsely reported?
Steven
Hi Steve,
I think you responded to the original question from months ago? My response was last week but I didn't post any pics.
thanks,
Scott
Thakns. Yes, after reading your 2nd post, I re-read your 1st post. Still I have no idea which partition has failure. By default Clonezilla won't check the unknown file system, as the photo in your 1st post. So I was wondering which partition Clonezilla failed to check.
Steven
Sorry, I'm not the OP. I was just providing some feedback on how I think that the software's error messages or workflow should be changed to better inform users of real errors or not.
OK, thanks.
If in the future you have more info from your OP, please share that.
Steven
What do you think about my previous suggestions to help improve Clonezilla? I think they would help reduce confusion.
thanks,
Scott
Sure, that's also what I meant.
Please let us know how to reproduce this issue in detail. In your description, we just can not identify which partition had the unknown file system and Clonezilla failed to detect that.
As I mentioned, by default Clonezilla won't check the file system integrity if it's unknown to Clonezilla. You can tell from the photo "ocs-live-error.png" in your 1st post, sdb1 won't be checked since it's dumped by dd. Clonezilla will just use dd to restore that.
Steven
Anytime Clonezilla has to end up using dd, does it always give this message at the end?
"Broken partition images were found, or some of them are not checkable in this image"
Of course not.
Steven
What is meant by "some of them are not checkable" ? Does this translate to a partition wasn't identifiable?
Well, "some of them are not checkable" does not include the dd case. So that's definitely different thing.
So we need your help to improve this. Please let us know how to reproduce this issue in detail.
I am wondering maybe it's related LVM thin provisioning, since you mentioned it's Proxmox.
Steven
I did a full disk backup of my Proxmox drive and also got the same "Broken partition images were found, or some of them are not checkable in this image" message too. I didn't think to make copies of the log files as I thought Clonezilla might have copied them over to my image directory, but I don't have them any longer. However, I still have a 300+GB folder it created called "2024-08-17-17-img" in case there's anything I can attach here to help troubleshoot.
thanks,
Scott
So how did you setup your Proxmox? We need that in detail so that we can reproduce this issue.
Steven
I think this should explain my Proxmox disk layout, sourced from my Clonezilla's image export
blkdev.list
file. Also uploaded to https://pastebin.com/CUx9Zwx6 . As you can tell, my Proxmox is onnvme0n1
.Last edit: Scott Copus 2024-08-26
OK, thanks.
As I mentioned previously, Clonezilla does not support LVM thin provisioning at the moment.
We do not recommend use Clonezilla in such case.
Maybe in the future we will support it well when the required LVM tools have the functions we need.
Steven