Issues cloning MacOS drive into smaller one












0















I am trying to move my OS X install to a smaller disk because I plan to move to another OS, but this is taking much longer than planned so I hope someone can help me here.



The SSD that now holds OS X is divided into 4 partitions: EFI, Yosemite, Recovery HD (linked to Yosemite), El Capitan. I have shrinked each partition (except EFI of course) and moved it to the left, so now only the first ~120GB of the disk are used, the rest is unallocated. Also note that this is a Hackintosh so there are slight differences when it comes to the bootloader and the content of EFI (even though I have cloned this install in the past - from a HDD to this SSD with the same size, so I cannot explain the problems that I am having now). This SSD works flawlessly on all partitions and Disk Utility doesn't detect any problem.



The first thing I tried was creating partitions on the HDD that start and finish at the same sectors as the SSD (using gpt in terminal iirc) then using Disk Utility (later tried with Gparted) to clone the original partitions to the new ones and repairing the disk to fix the partition table. That did not work - the disk was not bootable.



I have read from this and other sites that people use Disk Utility to simply restore a bigger disk with enough free space into a smaller one and it just works. I have tried the same but I get a weird error (OSStatus error 6): the volume is not of type Apple_HFS or Apple_UFS. Except for EFI, this is not true. The destination disk had an empty partition formatted in HFS+, but anyway Disk Utility reported the error before it could check the destination. Note that I tried this from El Capitan, Recovery HD and a separate High Sierra installer USB stick.



I have tried creating an image of the entire disk. To do this I formatted another 500GB disk in GPT with a HFS+ partition and used it as the destination of the image file, but Disk Utility lamented that it needed a space as big as the source drive, even if the image was supposed to be compressed.



Using CloneZilla didn't bring me much further. Trying disk-to-disk clone gave me an instant error - even after selecting the option to not check the size of the destination disk against the source (I will try this again tomorrow with a new SATA-USB adapter that I got today). CloneZilla, like many Linux tools, reportedly have not optimal support for HFS+, but I read that people have successfully used it to clone MacOS disks. I have also tried making an image of the disk using Clonezilla. It seemed to run well, and it finished copying data from each partition, but right before the end it found an error and interrupted the operation, rendering the image unusable (I haven't recorded the actual error here, I can rerun it and report it if you think it can be relevant.). The image was going to the same 500GB drive used earlier with Disk Utility, only this time formatted as exFAT.



I then accepted trying commercial software. I tried Carbon Copy Cloner, which lets the user only clone single volumes at a time. I tried cloning all the contents but after this the drive was not bootable. I later tried to dd the EFI partition from the SSD, but it made no difference. Note that the single volumes on the newly cloned drive booted fine if I launched the bootloader (Clover in my case) from an other disk (the SSD or the install USB). Iirc the same happened after trying a few other methods mentioned above.



At this point I'm out of ideas, and this is getting a little frustrating. What am I overlooking? How can I clone this disk and just use it like if it was the original? Thank you for the help.










share|improve this question

























  • I'm voting to close this question as off-topic because the use of macOS on non-Apple hardware is a legal grey area and as a result "Hackintosh" questions have been deemed off-topic.

    – Tetsujin
    Feb 16 at 10:08











  • @Tetsujin I understand that Hackintosh can be a troubling topic on this site, but I think this is not the point here. My question is about cloning a drive with HFS+ formatted partitions onto a smaller drive. The fact that this is a Hackintosh doesn't make a big difference. Also, "legal grey area" does not mean illegal in this case, and many of the answers in your link are in favor of Hackintosh-related questions. There seems to not be a uniform decision to deem such questions as off-topic.

    – itsmeciao
    Feb 16 at 10:25













  • The decision, which applies right across Stack Exchange, comes from management, not from user opinion. Aside from the legalities, the variety of hardware makes it impossible to answer. Cloning a drive on a Mac is easy, I do it all the time. Doing the same without breaking whatever OSX86 hack you have in there to get it to boot is an entirely different matter.

    – Tetsujin
    Feb 16 at 10:29











  • For those looking into the same issue, it appears that reinstalling the Clover bootloader with its installer, and then re-copying all your personalized files in the new empty EFI (config.plist, kexts, DSDT/SSDT tables, etc; I haven't actually tried to just copy the entire CLOVER folder so try that first) solves all problems. Sorry for this question, as I said I had already done a clone before so I didn't expect this to be related to OSX86.

    – itsmeciao
    Feb 22 at 20:06
















0















I am trying to move my OS X install to a smaller disk because I plan to move to another OS, but this is taking much longer than planned so I hope someone can help me here.



The SSD that now holds OS X is divided into 4 partitions: EFI, Yosemite, Recovery HD (linked to Yosemite), El Capitan. I have shrinked each partition (except EFI of course) and moved it to the left, so now only the first ~120GB of the disk are used, the rest is unallocated. Also note that this is a Hackintosh so there are slight differences when it comes to the bootloader and the content of EFI (even though I have cloned this install in the past - from a HDD to this SSD with the same size, so I cannot explain the problems that I am having now). This SSD works flawlessly on all partitions and Disk Utility doesn't detect any problem.



The first thing I tried was creating partitions on the HDD that start and finish at the same sectors as the SSD (using gpt in terminal iirc) then using Disk Utility (later tried with Gparted) to clone the original partitions to the new ones and repairing the disk to fix the partition table. That did not work - the disk was not bootable.



I have read from this and other sites that people use Disk Utility to simply restore a bigger disk with enough free space into a smaller one and it just works. I have tried the same but I get a weird error (OSStatus error 6): the volume is not of type Apple_HFS or Apple_UFS. Except for EFI, this is not true. The destination disk had an empty partition formatted in HFS+, but anyway Disk Utility reported the error before it could check the destination. Note that I tried this from El Capitan, Recovery HD and a separate High Sierra installer USB stick.



I have tried creating an image of the entire disk. To do this I formatted another 500GB disk in GPT with a HFS+ partition and used it as the destination of the image file, but Disk Utility lamented that it needed a space as big as the source drive, even if the image was supposed to be compressed.



Using CloneZilla didn't bring me much further. Trying disk-to-disk clone gave me an instant error - even after selecting the option to not check the size of the destination disk against the source (I will try this again tomorrow with a new SATA-USB adapter that I got today). CloneZilla, like many Linux tools, reportedly have not optimal support for HFS+, but I read that people have successfully used it to clone MacOS disks. I have also tried making an image of the disk using Clonezilla. It seemed to run well, and it finished copying data from each partition, but right before the end it found an error and interrupted the operation, rendering the image unusable (I haven't recorded the actual error here, I can rerun it and report it if you think it can be relevant.). The image was going to the same 500GB drive used earlier with Disk Utility, only this time formatted as exFAT.



I then accepted trying commercial software. I tried Carbon Copy Cloner, which lets the user only clone single volumes at a time. I tried cloning all the contents but after this the drive was not bootable. I later tried to dd the EFI partition from the SSD, but it made no difference. Note that the single volumes on the newly cloned drive booted fine if I launched the bootloader (Clover in my case) from an other disk (the SSD or the install USB). Iirc the same happened after trying a few other methods mentioned above.



At this point I'm out of ideas, and this is getting a little frustrating. What am I overlooking? How can I clone this disk and just use it like if it was the original? Thank you for the help.










share|improve this question

























  • I'm voting to close this question as off-topic because the use of macOS on non-Apple hardware is a legal grey area and as a result "Hackintosh" questions have been deemed off-topic.

    – Tetsujin
    Feb 16 at 10:08











  • @Tetsujin I understand that Hackintosh can be a troubling topic on this site, but I think this is not the point here. My question is about cloning a drive with HFS+ formatted partitions onto a smaller drive. The fact that this is a Hackintosh doesn't make a big difference. Also, "legal grey area" does not mean illegal in this case, and many of the answers in your link are in favor of Hackintosh-related questions. There seems to not be a uniform decision to deem such questions as off-topic.

    – itsmeciao
    Feb 16 at 10:25













  • The decision, which applies right across Stack Exchange, comes from management, not from user opinion. Aside from the legalities, the variety of hardware makes it impossible to answer. Cloning a drive on a Mac is easy, I do it all the time. Doing the same without breaking whatever OSX86 hack you have in there to get it to boot is an entirely different matter.

    – Tetsujin
    Feb 16 at 10:29











  • For those looking into the same issue, it appears that reinstalling the Clover bootloader with its installer, and then re-copying all your personalized files in the new empty EFI (config.plist, kexts, DSDT/SSDT tables, etc; I haven't actually tried to just copy the entire CLOVER folder so try that first) solves all problems. Sorry for this question, as I said I had already done a clone before so I didn't expect this to be related to OSX86.

    – itsmeciao
    Feb 22 at 20:06














0












0








0








I am trying to move my OS X install to a smaller disk because I plan to move to another OS, but this is taking much longer than planned so I hope someone can help me here.



The SSD that now holds OS X is divided into 4 partitions: EFI, Yosemite, Recovery HD (linked to Yosemite), El Capitan. I have shrinked each partition (except EFI of course) and moved it to the left, so now only the first ~120GB of the disk are used, the rest is unallocated. Also note that this is a Hackintosh so there are slight differences when it comes to the bootloader and the content of EFI (even though I have cloned this install in the past - from a HDD to this SSD with the same size, so I cannot explain the problems that I am having now). This SSD works flawlessly on all partitions and Disk Utility doesn't detect any problem.



The first thing I tried was creating partitions on the HDD that start and finish at the same sectors as the SSD (using gpt in terminal iirc) then using Disk Utility (later tried with Gparted) to clone the original partitions to the new ones and repairing the disk to fix the partition table. That did not work - the disk was not bootable.



I have read from this and other sites that people use Disk Utility to simply restore a bigger disk with enough free space into a smaller one and it just works. I have tried the same but I get a weird error (OSStatus error 6): the volume is not of type Apple_HFS or Apple_UFS. Except for EFI, this is not true. The destination disk had an empty partition formatted in HFS+, but anyway Disk Utility reported the error before it could check the destination. Note that I tried this from El Capitan, Recovery HD and a separate High Sierra installer USB stick.



I have tried creating an image of the entire disk. To do this I formatted another 500GB disk in GPT with a HFS+ partition and used it as the destination of the image file, but Disk Utility lamented that it needed a space as big as the source drive, even if the image was supposed to be compressed.



Using CloneZilla didn't bring me much further. Trying disk-to-disk clone gave me an instant error - even after selecting the option to not check the size of the destination disk against the source (I will try this again tomorrow with a new SATA-USB adapter that I got today). CloneZilla, like many Linux tools, reportedly have not optimal support for HFS+, but I read that people have successfully used it to clone MacOS disks. I have also tried making an image of the disk using Clonezilla. It seemed to run well, and it finished copying data from each partition, but right before the end it found an error and interrupted the operation, rendering the image unusable (I haven't recorded the actual error here, I can rerun it and report it if you think it can be relevant.). The image was going to the same 500GB drive used earlier with Disk Utility, only this time formatted as exFAT.



I then accepted trying commercial software. I tried Carbon Copy Cloner, which lets the user only clone single volumes at a time. I tried cloning all the contents but after this the drive was not bootable. I later tried to dd the EFI partition from the SSD, but it made no difference. Note that the single volumes on the newly cloned drive booted fine if I launched the bootloader (Clover in my case) from an other disk (the SSD or the install USB). Iirc the same happened after trying a few other methods mentioned above.



At this point I'm out of ideas, and this is getting a little frustrating. What am I overlooking? How can I clone this disk and just use it like if it was the original? Thank you for the help.










share|improve this question
















I am trying to move my OS X install to a smaller disk because I plan to move to another OS, but this is taking much longer than planned so I hope someone can help me here.



The SSD that now holds OS X is divided into 4 partitions: EFI, Yosemite, Recovery HD (linked to Yosemite), El Capitan. I have shrinked each partition (except EFI of course) and moved it to the left, so now only the first ~120GB of the disk are used, the rest is unallocated. Also note that this is a Hackintosh so there are slight differences when it comes to the bootloader and the content of EFI (even though I have cloned this install in the past - from a HDD to this SSD with the same size, so I cannot explain the problems that I am having now). This SSD works flawlessly on all partitions and Disk Utility doesn't detect any problem.



The first thing I tried was creating partitions on the HDD that start and finish at the same sectors as the SSD (using gpt in terminal iirc) then using Disk Utility (later tried with Gparted) to clone the original partitions to the new ones and repairing the disk to fix the partition table. That did not work - the disk was not bootable.



I have read from this and other sites that people use Disk Utility to simply restore a bigger disk with enough free space into a smaller one and it just works. I have tried the same but I get a weird error (OSStatus error 6): the volume is not of type Apple_HFS or Apple_UFS. Except for EFI, this is not true. The destination disk had an empty partition formatted in HFS+, but anyway Disk Utility reported the error before it could check the destination. Note that I tried this from El Capitan, Recovery HD and a separate High Sierra installer USB stick.



I have tried creating an image of the entire disk. To do this I formatted another 500GB disk in GPT with a HFS+ partition and used it as the destination of the image file, but Disk Utility lamented that it needed a space as big as the source drive, even if the image was supposed to be compressed.



Using CloneZilla didn't bring me much further. Trying disk-to-disk clone gave me an instant error - even after selecting the option to not check the size of the destination disk against the source (I will try this again tomorrow with a new SATA-USB adapter that I got today). CloneZilla, like many Linux tools, reportedly have not optimal support for HFS+, but I read that people have successfully used it to clone MacOS disks. I have also tried making an image of the disk using Clonezilla. It seemed to run well, and it finished copying data from each partition, but right before the end it found an error and interrupted the operation, rendering the image unusable (I haven't recorded the actual error here, I can rerun it and report it if you think it can be relevant.). The image was going to the same 500GB drive used earlier with Disk Utility, only this time formatted as exFAT.



I then accepted trying commercial software. I tried Carbon Copy Cloner, which lets the user only clone single volumes at a time. I tried cloning all the contents but after this the drive was not bootable. I later tried to dd the EFI partition from the SSD, but it made no difference. Note that the single volumes on the newly cloned drive booted fine if I launched the bootloader (Clover in my case) from an other disk (the SSD or the install USB). Iirc the same happened after trying a few other methods mentioned above.



At this point I'm out of ideas, and this is getting a little frustrating. What am I overlooking? How can I clone this disk and just use it like if it was the original? Thank you for the help.







macos hard-drive boot clonezilla disk-cloning






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Feb 16 at 9:18







itsmeciao

















asked Feb 16 at 9:04









itsmeciaoitsmeciao

14




14













  • I'm voting to close this question as off-topic because the use of macOS on non-Apple hardware is a legal grey area and as a result "Hackintosh" questions have been deemed off-topic.

    – Tetsujin
    Feb 16 at 10:08











  • @Tetsujin I understand that Hackintosh can be a troubling topic on this site, but I think this is not the point here. My question is about cloning a drive with HFS+ formatted partitions onto a smaller drive. The fact that this is a Hackintosh doesn't make a big difference. Also, "legal grey area" does not mean illegal in this case, and many of the answers in your link are in favor of Hackintosh-related questions. There seems to not be a uniform decision to deem such questions as off-topic.

    – itsmeciao
    Feb 16 at 10:25













  • The decision, which applies right across Stack Exchange, comes from management, not from user opinion. Aside from the legalities, the variety of hardware makes it impossible to answer. Cloning a drive on a Mac is easy, I do it all the time. Doing the same without breaking whatever OSX86 hack you have in there to get it to boot is an entirely different matter.

    – Tetsujin
    Feb 16 at 10:29











  • For those looking into the same issue, it appears that reinstalling the Clover bootloader with its installer, and then re-copying all your personalized files in the new empty EFI (config.plist, kexts, DSDT/SSDT tables, etc; I haven't actually tried to just copy the entire CLOVER folder so try that first) solves all problems. Sorry for this question, as I said I had already done a clone before so I didn't expect this to be related to OSX86.

    – itsmeciao
    Feb 22 at 20:06



















  • I'm voting to close this question as off-topic because the use of macOS on non-Apple hardware is a legal grey area and as a result "Hackintosh" questions have been deemed off-topic.

    – Tetsujin
    Feb 16 at 10:08











  • @Tetsujin I understand that Hackintosh can be a troubling topic on this site, but I think this is not the point here. My question is about cloning a drive with HFS+ formatted partitions onto a smaller drive. The fact that this is a Hackintosh doesn't make a big difference. Also, "legal grey area" does not mean illegal in this case, and many of the answers in your link are in favor of Hackintosh-related questions. There seems to not be a uniform decision to deem such questions as off-topic.

    – itsmeciao
    Feb 16 at 10:25













  • The decision, which applies right across Stack Exchange, comes from management, not from user opinion. Aside from the legalities, the variety of hardware makes it impossible to answer. Cloning a drive on a Mac is easy, I do it all the time. Doing the same without breaking whatever OSX86 hack you have in there to get it to boot is an entirely different matter.

    – Tetsujin
    Feb 16 at 10:29











  • For those looking into the same issue, it appears that reinstalling the Clover bootloader with its installer, and then re-copying all your personalized files in the new empty EFI (config.plist, kexts, DSDT/SSDT tables, etc; I haven't actually tried to just copy the entire CLOVER folder so try that first) solves all problems. Sorry for this question, as I said I had already done a clone before so I didn't expect this to be related to OSX86.

    – itsmeciao
    Feb 22 at 20:06

















I'm voting to close this question as off-topic because the use of macOS on non-Apple hardware is a legal grey area and as a result "Hackintosh" questions have been deemed off-topic.

– Tetsujin
Feb 16 at 10:08





I'm voting to close this question as off-topic because the use of macOS on non-Apple hardware is a legal grey area and as a result "Hackintosh" questions have been deemed off-topic.

– Tetsujin
Feb 16 at 10:08













@Tetsujin I understand that Hackintosh can be a troubling topic on this site, but I think this is not the point here. My question is about cloning a drive with HFS+ formatted partitions onto a smaller drive. The fact that this is a Hackintosh doesn't make a big difference. Also, "legal grey area" does not mean illegal in this case, and many of the answers in your link are in favor of Hackintosh-related questions. There seems to not be a uniform decision to deem such questions as off-topic.

– itsmeciao
Feb 16 at 10:25







@Tetsujin I understand that Hackintosh can be a troubling topic on this site, but I think this is not the point here. My question is about cloning a drive with HFS+ formatted partitions onto a smaller drive. The fact that this is a Hackintosh doesn't make a big difference. Also, "legal grey area" does not mean illegal in this case, and many of the answers in your link are in favor of Hackintosh-related questions. There seems to not be a uniform decision to deem such questions as off-topic.

– itsmeciao
Feb 16 at 10:25















The decision, which applies right across Stack Exchange, comes from management, not from user opinion. Aside from the legalities, the variety of hardware makes it impossible to answer. Cloning a drive on a Mac is easy, I do it all the time. Doing the same without breaking whatever OSX86 hack you have in there to get it to boot is an entirely different matter.

– Tetsujin
Feb 16 at 10:29





The decision, which applies right across Stack Exchange, comes from management, not from user opinion. Aside from the legalities, the variety of hardware makes it impossible to answer. Cloning a drive on a Mac is easy, I do it all the time. Doing the same without breaking whatever OSX86 hack you have in there to get it to boot is an entirely different matter.

– Tetsujin
Feb 16 at 10:29













For those looking into the same issue, it appears that reinstalling the Clover bootloader with its installer, and then re-copying all your personalized files in the new empty EFI (config.plist, kexts, DSDT/SSDT tables, etc; I haven't actually tried to just copy the entire CLOVER folder so try that first) solves all problems. Sorry for this question, as I said I had already done a clone before so I didn't expect this to be related to OSX86.

– itsmeciao
Feb 22 at 20:06





For those looking into the same issue, it appears that reinstalling the Clover bootloader with its installer, and then re-copying all your personalized files in the new empty EFI (config.plist, kexts, DSDT/SSDT tables, etc; I haven't actually tried to just copy the entire CLOVER folder so try that first) solves all problems. Sorry for this question, as I said I had already done a clone before so I didn't expect this to be related to OSX86.

– itsmeciao
Feb 22 at 20:06










0






active

oldest

votes












Your Answer








StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});














draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1406405%2fissues-cloning-macos-drive-into-smaller-one%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown

























0






active

oldest

votes








0






active

oldest

votes









active

oldest

votes






active

oldest

votes
















draft saved

draft discarded




















































Thanks for contributing an answer to Super User!


  • Please be sure to answer the question. Provide details and share your research!

But avoid



  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.


To learn more, see our tips on writing great answers.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1406405%2fissues-cloning-macos-drive-into-smaller-one%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown





















































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown

































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown







Popular posts from this blog

flock() on closed filehandle LOCK_FILE at /usr/bin/apt-mirror

Mangá

 ⁒  ․,‪⁊‑⁙ ⁖, ⁇‒※‌, †,⁖‗‌⁝    ‾‸⁘,‖⁔⁣,⁂‾
”‑,‥–,‬ ,⁀‹⁋‴⁑ ‒ ,‴⁋”‼ ⁨,‷⁔„ ‰′,‐‚ ‥‡‎“‷⁃⁨⁅⁣,⁔
⁇‘⁔⁡⁏⁌⁡‿‶‏⁨ ⁣⁕⁖⁨⁩⁥‽⁀  ‴‬⁜‟ ⁃‣‧⁕‮ …‍⁨‴ ⁩,⁚⁖‫ ,‵ ⁀,‮⁝‣‣ ⁑  ⁂– ․, ‾‽ ‏⁁“⁗‸ ‾… ‹‡⁌⁎‸‘ ‡⁏⁌‪ ‵⁛ ‎⁨ ―⁦⁤⁄⁕