I have three proxmox nodes in a cluster: A Lenovo, a Dell T5820, and a Mac Mini.
The installation for all was the same: Boot from usb key, install onto a single SSD.
The first one was the Lenovo.
After the installation I've added 3 SSDs for a ZFS pool, done all updates, shutdown down and boot clonezilla to create the image. At the end the Bronken partition error cames up.
I repeat the same steps for my Dell and no errors from clonezilla.
Created a cluster with the three nodes and tried today to use clonezilla to create the images with the same results: Lenovo errors out and Dell doesn't.
Again, only creating the image for the boot ssd.
Attached the logs for the Lenovo clonezilla run.
I can move all VMs to my Dell to run any tests you guy might want, so I can help solve this issue as I did see several posts with this same problem.
So tests continue, while I wait for some replies...
Built a new test server with a Supermicro X9, installed Proxmox VE on a SSD, created a LVM Thin for the VMs, joined my cluster and was able to create an image of my SSD boot with clonezilla.
So the question remains: Why didn't work on the Lenovo from fresh install 'til now?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
There are two issues about your proxmox and Clonezilla which you have to notice:
1. proxmox uses thin-provisioning LVM.
2. It also uses ZFS
Both these are not well supported by Clonezilla. Hence issues are expected.
Steven
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Since my last post, I've moved away from the Lenovo desktop and moved my proxmox to my dells T5820 (2 of them) and a Mac Mini - as a low wattage node to add to the cluster.
All with SSDs as boot that are been backed up with clinezilla no problem, so I do beliave the issue was a combination hardware/LVM with the Lenovo, as I'm using it for my linux desktop and clonezilla works fine.
Unfortunatelly I can no longer run any tests as I had to move on and get my setup working.
This issue is closed without resolution.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I have three proxmox nodes in a cluster: A Lenovo, a Dell T5820, and a Mac Mini.
The installation for all was the same: Boot from usb key, install onto a single SSD.
The first one was the Lenovo.
After the installation I've added 3 SSDs for a ZFS pool, done all updates, shutdown down and boot clonezilla to create the image. At the end the Bronken partition error cames up.
I repeat the same steps for my Dell and no errors from clonezilla.
Created a cluster with the three nodes and tried today to use clonezilla to create the images with the same results: Lenovo errors out and Dell doesn't.
Again, only creating the image for the boot ssd.
Attached the logs for the Lenovo clonezilla run.
I can move all VMs to my Dell to run any tests you guy might want, so I can help solve this issue as I did see several posts with this same problem.
Regards
So tests continue, while I wait for some replies...
Built a new test server with a Supermicro X9, installed Proxmox VE on a SSD, created a LVM Thin for the VMs, joined my cluster and was able to create an image of my SSD boot with clonezilla.
So the question remains: Why didn't work on the Lenovo from fresh install 'til now?
There are two issues about your proxmox and Clonezilla which you have to notice:
1. proxmox uses thin-provisioning LVM.
2. It also uses ZFS
Both these are not well supported by Clonezilla. Hence issues are expected.
Steven
Thank you for your reply.
Since my last post, I've moved away from the Lenovo desktop and moved my proxmox to my dells T5820 (2 of them) and a Mac Mini - as a low wattage node to add to the cluster.
All with SSDs as boot that are been backed up with clinezilla no problem, so I do beliave the issue was a combination hardware/LVM with the Lenovo, as I'm using it for my linux desktop and clonezilla works fine.
Unfortunatelly I can no longer run any tests as I had to move on and get my setup working.
This issue is closed without resolution.