Apologies if this is a FAQ. If it is please point me in the right direction.
I have a dual boot (Win 10 and Linux Mint 20) system disk that I wish to clone to a larger disk.
I followed the directions in this doc. https://clonezilla.org/fine-print-live-doc.php?path=./clonezilla-live/doc/03_Disk_to_disk_clone/09-starting-cloning.doc#09-starting-cloning.doc
The operation aborts with "This disk contains mismatched GPT & MBR partitions: /dev/sda"
There are tips such as using sgdik -z or mbr2gpt to correct this BUT can I safely do this and not
destroy the dual boot system on /dev/sda?
Any help appreciated.
Peter.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Dual boot does mean it has MBR and GPT table co-existing. Hence you still have to keep only one of them.
Normally if you know which one is the correct one you need, then you can delete the other one.
It's recommended to backup important data before you do that. Just in case.
Steven
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thanks Steven. I set up the dual boot system sometime ago and can't remember having to select either MBR or GPT tables when doing so. When you say they co-exist does that mean Win 10 uses one and LM uses the other? If yes, won't deleting one destroy the dual boot?
Or, when you say "if you know the one you need, you can delete the other one" Will this still retain the dual boot? If yes, how do I determine which is the correct table MRB or GPT?
Sorry if these are newby questions but I am <g> Thanks again.</g>
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
"does that mean Win 10 uses one and LM uses the other?" -> I do not think so. Normally this is due to the hard drive was used for legacy booting, but later it is used in GPT format. Somehow the legacy MBR was not removed.
So please boot Clonezilla live, enter command line prompt, then run:
1. sudo parted -s /dev/sda print
2. sudo blkid
(Replace /dev/sda with your device name)
Please post the results of 1 and 2.
Thanks.
Steven
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Apologies for the delay but after reading the links I chickened out, I didn't want to risk breaking my working system disk by doing the wrong thing. In another forum when I explained my problem it was suggested I put Linux Mint on a USB stick, booted in off of it and then use the "dd" command. "dd if=/dev/sda of=/dev/sdg" in my case. It worked! No problem with "mismatched partitions" etc. The new disk is in place and works perfectly.
Thanks for all the help.
Peter.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Sounds like you would have copied the mismatch state too. If you went from one disk to another with dd, and both disks are the same sector size, you now have a byte for byte exact copy. Disconnect the old drive and you can try to repair/convert/etc. the new disk to a more sane state. If your hardware+software supports booting GPT, I'd recommend converting to that for future compatibility, Make sure you then make a backup once you are happy with it in a working state.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Apologies if this is a FAQ. If it is please point me in the right direction.
I have a dual boot (Win 10 and Linux Mint 20) system disk that I wish to clone to a larger disk.
I followed the directions in this doc.
https://clonezilla.org/fine-print-live-doc.php?path=./clonezilla-live/doc/03_Disk_to_disk_clone/09-starting-cloning.doc#09-starting-cloning.doc
The operation aborts with "This disk contains mismatched GPT & MBR partitions: /dev/sda"
There are tips such as using sgdik -z or mbr2gpt to correct this BUT can I safely do this and not
destroy the dual boot system on /dev/sda?
Any help appreciated.
Peter.
Dual boot does mean it has MBR and GPT table co-existing. Hence you still have to keep only one of them.
Normally if you know which one is the correct one you need, then you can delete the other one.
It's recommended to backup important data before you do that. Just in case.
Steven
Thanks Steven. I set up the dual boot system sometime ago and can't remember having to select either MBR or GPT tables when doing so. When you say they co-exist does that mean Win 10 uses one and LM uses the other? If yes, won't deleting one destroy the dual boot?
Or, when you say "if you know the one you need, you can delete the other one" Will this still retain the dual boot? If yes, how do I determine which is the correct table MRB or GPT?
Sorry if these are newby questions but I am <g> Thanks again.</g>
"does that mean Win 10 uses one and LM uses the other?" -> I do not think so. Normally this is due to the hard drive was used for legacy booting, but later it is used in GPT format. Somehow the legacy MBR was not removed.
So please boot Clonezilla live, enter command line prompt, then run:
1. sudo parted -s /dev/sda print
2. sudo blkid
(Replace /dev/sda with your device name)
Please post the results of 1 and 2.
Thanks.
Steven
I've attached, hopefully successfully, the results to this message Steven.
Thanks again for you help.
Peter.
Your partition table of /dev/sda is legacy mode, i.e., MBR format.
You can run:
sudo sgdisk -v /dev/sda
to check that.
So look like you can remove the GPT one...
Ref: https://community.spiceworks.com/topic/2199605-clonezilla-mbr-gpt-mismatch-on-two-mbr-drives
https://superuser.com/questions/884608/clonezilla-fails-at-cloning-with-mismatched-gpt-and-mbr-partition
//NOTE// Backup important data before you fix it. Just in case.
Steven
Thanks. I'll make time over the weekend to try again.
I'll let you know how I get on.
Peter
Apologies for the delay but after reading the links I chickened out, I didn't want to risk breaking my working system disk by doing the wrong thing. In another forum when I explained my problem it was suggested I put Linux Mint on a USB stick, booted in off of it and then use the "dd" command. "dd if=/dev/sda of=/dev/sdg" in my case. It worked! No problem with "mismatched partitions" etc. The new disk is in place and works perfectly.
Thanks for all the help.
Peter.
Sure. You have found a good solution. Cool.
Steven
Sounds like you would have copied the mismatch state too. If you went from one disk to another with dd, and both disks are the same sector size, you now have a byte for byte exact copy. Disconnect the old drive and you can try to repair/convert/etc. the new disk to a more sane state. If your hardware+software supports booting GPT, I'd recommend converting to that for future compatibility, Make sure you then make a backup once you are happy with it in a working state.