Clonezilla / Bugs / #356 kernel of 2.7.0-10 doesn't immediately recognize changes to a partition table

#356 kernel of 2.7.0-10 doesn't immediately recognize changes to a partition table

Milestone: testing_clonezilla

Status: open

Owner: nobody

Labels: None

Priority: 5

Updated: 2021-04-14

Created: 2021-02-11

Creator: mauricevo

Private: No

On a Parallels virtual machine, the kernel in Clonezilla 2.7.0-10 is unable to recognize changes to the partition table and thus Clonezilla doesn't recognize changes it had just made to a disk for restoration. Further details are at https://sourceforge.net/p/clonezilla/discussion/Help/thread/3689db58df/

Discussion

Steven Shiau - 2021-02-12

Thanks for reporting this. Is this issue reproducible for the latest stable Clonezilla live 2.7.1-22?
https://clonezilla.org/downloads.php

Steven

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Steven Shiau - 2021-02-12

OK, I found you mentioned you actually use 2.7.1-22:
https://sourceforge.net/p/clonezilla/discussion/Help/thread/3689db58df/?limit=25#e38b

However, I can not reproduce this issue. All my tests on VM or physical machines work, and you are the only one so far reporting this issue. Hence I am not sure where went wrong. Maybe you can give Ubuntu-based Clonezilla live a try:
https://clonezilla.org/downloads.php

Steven

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Jack G - 2021-04-13

Hey Steven, I also get this same issue for my standard Sata Drives and NVME ones.

Screenshot 2021-04-13 at 20.45.06.png

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Jack G - 2021-04-13

Do you know if there's any way to rename the target partitions? Here is another screenshot for the NVME drive.

Screenshot 2021-04-13 at 22.51.54.png

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
- Steven Shiau - 2021-04-14
  
  You choose the option "-k", which means no need to create the partition table on the destination disk. That's why you have /dev/nvme0n1, but no partition /dev/nvme0n1p1. You should remove the option "-k", or you have to manually create the partition on the destination disk.
  
  Steven
  
  If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Jack G - 2021-04-13

Not sure if this is useful information, but I'm using an image to put onto a virtual machine using VMWare, some reason the images of my Lenovo ThinkPad laptops work fine when doing this, but this error only appears when imaging the Dell XPS 9310 devices. Is there any additional files or logs I can send to help you find this issue?

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Jack G - 2021-04-13

Interesting - lenovo laptop images where using a different version of CloneZilla when they were cloned.

Lenovo Laptop Images that works when imaging VM

Image was saved by these Clonezilla-related packages: drbl-2.32.9-drbl1 clonezilla-3.39.14-drbl1 partclone-0.3.14-drbl1 util-linux-2.35.2-6 gdisk-1.0.5-1 Saved by clonezilla-live-2.6.7-28-amd64.

Dell Laptop Image that fails when imaging VM

Image was saved by these Clonezilla-related packages: drbl-4.2.16-drbl1 clonezilla-4.2.30-drbl1 partclone-0.3.17-drbl1 util-linux-2.36.1-6 gdisk-1.0.6-1 Saved by clonezilla-live-2.7.1-22-amd64.

Note: no VM hardware configurations were changed during the testing of each VM image

Last edit: Jack G 2021-04-13
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Steven Shiau - 2021-04-14

Maybe you can try the testing Clonezilla live, e.g., >= 2.7.2-19 or 20210406-hirsute:
https://clonezilla.org/downloads.php

Steven

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Log in to post a comment.