Firstly thank you for such a wonderful and empowering tool. I have used this for adding a Linux Minut installation to my Macbook Air and its been wonderful. Of course now that I am really using my computer for what it should have been used for ages ago, I now would like more storage space. I'm wanting to purchase a 960GB SSD drive for this machine, and re-partition the installation OS on them with larger storage volumes however I have to work out how to copy the entire SSD I already have to a larger SSD.
What is the best way to do this? Are there any FOSS or commercial products that will do a full, raw SSD copy that respect rEFInd and its way to book multiple OS on the SSD?
Thanks in advance for any help.
K
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Personally, I'd do a file-by-file copy with tar or something similar. This will avoid problems with a low-level byte-for-byte copy, which might cause problems with the SSD's TRIM options. This approach will require updating boot loader entries, though, since the GUIDs on the disk won't match. (Likewise for /etc/fstab entries in Linux.)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Firstly thank you for such a wonderful and empowering tool. I have used this for adding a Linux Minut installation to my Macbook Air and its been wonderful. Of course now that I am really using my computer for what it should have been used for ages ago, I now would like more storage space. I'm wanting to purchase a 960GB SSD drive for this machine, and re-partition the installation OS on them with larger storage volumes however I have to work out how to copy the entire SSD I already have to a larger SSD.
What is the best way to do this? Are there any FOSS or commercial products that will do a full, raw SSD copy that respect rEFInd and its way to book multiple OS on the SSD?
Thanks in advance for any help.
K
Personally, I'd do a file-by-file copy with
tar
or something similar. This will avoid problems with a low-level byte-for-byte copy, which might cause problems with the SSD's TRIM options. This approach will require updating boot loader entries, though, since the GUIDs on the disk won't match. (Likewise for/etc/fstab
entries in Linux.)