[opensuse] Hard disk migration
Hi, I'm going to migrate my laptop rotating hard disk (500 GB) to an SSD. I hope to give new life to it this way. The machine is double boot Windows 10 / Leap 42.2, so I'm going to do image replication (dd_rescue), because otherwise Windows will not boot. So identical partition table. Caveats you can think of? What about sector size, 4K issues? -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar)
On 09/20/2017 11:13 AM, Carlos E. R. wrote:
Hi,
I'm going to migrate my laptop rotating hard disk (500 GB) to an SSD. I hope to give new life to it this way.
The machine is double boot Windows 10 / Leap 42.2, so I'm going to do image replication (dd_rescue), because otherwise Windows will not boot. So identical partition table.
Caveats you can think of? What about sector size, 4K issues?
No, but it is good to have you as the guinea pig :) You are much braver than I would be. I don't know how the dd_rescue image will behave going from platter to ssd. In theory a partition is just a partition and a file-system is just a file-system, but I would be concerned that Win10 may rely on the disk serial in some way -- which may leave you fighting activation issues. If dd_rescue fails, then my approach would be to use the Win10 (actually it's the old Win7) system image/restore in the old backup control panel. Just use a spare platter drive as your backup media and image your Win10 install to that. Then install the ssd and use the restore DVD (or thumb drive you created) to boot and restore the Win10 image from the platter to your new ssd. Then I would worry about the 42.2 install (actually, I wouldn't, I'd install 42.3 or 15 fresh on the ssd and then move /home from old install to new and just tweak the new config files as required) Either way you are probably at a break-even on time. Either spend the time with a new 15 install after Win10, or spend the time dorking with what didn't exactly work with the dd_rescue image ... ;-) -- David C. Rankin, J.D.,P.E.
On 09/20/2017 12:59 PM, David C. Rankin wrote:
Then I would worry about the 42.2 install (actually, I wouldn't, I'd install 42.3 or 15 fresh on the ssd and then move /home from old install to new and just tweak the new config files as required)
That's what I did when I moved from HDD to SSD. I didn't have Win 10 to worry about. I too worry that the dd-rescue will end up being a less than optimal solution. At least Carlos will have the original disk to fall back on. -- After all is said and done, more is said than done.
On 09/20/2017 04:18 PM, John Andersen wrote:
On 09/20/2017 12:59 PM, David C. Rankin wrote:
Then I would worry about the 42.2 install (actually, I wouldn't, I'd install 42.3 or 15 fresh on the ssd and then move /home from old install to new and just tweak the new config files as required) That's what I did when I moved from HDD to SSD. I didn't have Win 10 to worry about.
I too worry that the dd-rescue will end up being a less than optimal solution.
At least Carlos will have the original disk to fall back on.
Back when I moved to a larger spinning drive, I used dd to save the partitions and then restore to the new drive. The computer had Windows 7 & openSUSE on it at the time. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2017-09-20 22:20, James Knott wrote:
On 09/20/2017 04:18 PM, John Andersen wrote:
On 09/20/2017 12:59 PM, David C. Rankin wrote:
Then I would worry about the 42.2 install (actually, I wouldn't, I'd install 42.3 or 15 fresh on the ssd and then move /home from old install to new and just tweak the new config files as required) That's what I did when I moved from HDD to SSD. I didn't have Win 10 to worry about.
I too worry that the dd-rescue will end up being a less than optimal solution.
At least Carlos will have the original disk to fall back on.
Back when I moved to a larger spinning drive, I used dd to save the partitions and then restore to the new drive. The computer had Windows 7 & openSUSE on it at the time.
Unfortunately, cloning only the partition table does not clone the logical partitions. That part is not that trivial. Not in this case, as I'm cloning full disk, not partitions. I went for a disk that is slightly bigger than the original (Crucial MX300 SSD 525GB) instead of the Samsung 850 Evo SSD Series 500GB SATA3, because I did not want the original 500GB and the new 500GB to be even one sector more. That would have doomed the dd procedure, making me resize at least the last partition. As it is I will have empty unpartitioned space at the end of the disk. I may leave it unused (SSDs like that, I believe), or use it to enlarge one particular partition inside (the one used for testing the new openSUSE release, it is about 9G). -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar)
On 2017-09-20 23:16, Carlos E. R. wrote:
On 2017-09-20 22:20, James Knott wrote:
On 09/20/2017 04:18 PM, John Andersen wrote:
On 09/20/2017 12:59 PM, David C. Rankin wrote:
Not in this case, as I'm cloning full disk, not partitions.
Done. :-) The BIOS test took some time, maybe probing the disk. Linux boots fine, and it does feel faster. Not terribly fast, of course, the CPU is just a dual core T4300 @ 2.10GHz Now I have to boot Windows and see if its happy in its new home. -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" (Minas Tirith)) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 21/09/2017 3:50, Carlos E. R. wrote:
On 2017-09-20 23:16, Carlos E. R. wrote:
On 2017-09-20 22:20, James Knott wrote:
On 09/20/2017 04:18 PM, John Andersen wrote:
On 09/20/2017 12:59 PM, David C. Rankin wrote:
Not in this case, as I'm cloning full disk, not partitions.
Done. :-)
The BIOS test took some time, maybe probing the disk.
Linux boots fine, and it does feel faster. Not terribly fast, of course, the CPU is just a dual core T4300 @ 2.10GHz
Now I have to boot Windows and see if its happy in its new home.
Windows boots silently, so Windows is happy and I'm very happy ;-) Firefox in Linux feels very fast. -- Saludos/Cheers, Carlos E.R. (Minas-Morgul - W10) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 09/20/2017 09:01 PM, Carlos E. R. wrote:
Done. :-)
The BIOS test took some time, maybe probing the disk.
Linux boots fine, and it does feel faster. Not terribly fast, of course, the CPU is just a dual core T4300 @ 2.10GHz
Now I have to boot Windows and see if its happy in its new home.
Windows boots silently, so Windows is happy and I'm very happy ;-)
Firefox in Linux feels very fast.
Wohoo! the guinea succeeds! That is good info Carlos, thanks. Now the open cases are what to do about going from a 4k sector platter to SSD if SSD is 512/512 as you report. If moving from a larger drive, I guess you can shrink the partitions to less, but that leaves you in a partition copy instead of a drive copy mode. (that could be a bit dicey...) I have a new 500G SSD I'm going to use on my next install (if my son doesn't take it back to college with him...). I've been super impressed with SSD, and as cell size shrinks and endurance improves and costs drop, it looks like that will be the wave of the future. (they are currently working on 4T+ SSDs, and some drives like the Samsung Pro models offer 10 year warranties [for just under double the cost of their 3 year drives]) I built gaming rigs for my two girls a year ago, and they have M2.2 slots in their motherboards. (right now they are on platters) Since the games they download/play (League, WOW, etc...) can take 50+G per-game, I wanted to wait until the 1T (or at least the 500G+) SSDs dropped a bit in price. The M2.2 SSD should offer quite a bit more performance over the typical SATA III interface. IIRC it uses 4-PCI buses combined for throughput as opposed to the SATA bus. But, at the time, I wasn't willing to drop another $600 where a pair of WD-Black 1T drives was $128. SSD really helps with I/O intensive apps and program load times. But once you app is loaded, then it doesn't really matter as long it doesn't do a lot of I/O. On the other hand, you can get a LOT of benefit out of the SSD speed for instance compiling desktops, etc... (but talk about beating the hell out of you SSD :) Thanks again for the feedback Carlos. -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2017-09-22 16:56, David C. Rankin wrote:
On 09/20/2017 09:01 PM, Carlos E. R. wrote:
Done. :-)
The BIOS test took some time, maybe probing the disk.
Linux boots fine, and it does feel faster. Not terribly fast, of course, the CPU is just a dual core T4300 @ 2.10GHz
Now I have to boot Windows and see if its happy in its new home.
Windows boots silently, so Windows is happy and I'm very happy ;-)
Firefox in Linux feels very fast.
Wohoo! the guinea succeeds!
:-)
That is good info Carlos, thanks. Now the open cases are what to do about going from a 4k sector platter to SSD if SSD is 512/512 as you report.
I expected the SSD to be 4K hardware, 512B logical. I'm very surprised at the 512B hardware sector size. It surely makes things easy. Maybe it is because the disk is "small": 0.5TB.
If moving from a larger drive, I guess you can shrink the partitions to less, but that leaves you in a partition copy instead of a drive copy mode. (that could be a bit dicey...)
Indeed. In that case, I would do first a partition table replicate (1 sector with dd, perhaps), then clone the Windows partitions with dd, no resize. Then, I would create and format the Linux partitions, then do a file copy with rsync. That would cover the different disk size issue. Finally, I would have to install grub manually. If the logical sector sizes were different, I would have to manually create the partitions to the same or different sizes, then rsync the files. Windows would have to be reinstalled from scratch - or ask on a Windows forum. Interestingly, the SSD comes with a migration tool and license number (Acronis, I think). I have bought another one, smaller, for the desktop (only "/" and swap) and it comes with a CD or DVD. Those tools must handle Windows migration transparently (the new disk they prepare externally, with an USB to SATA cable).
I have a new 500G SSD I'm going to use on my next install (if my son doesn't take it back to college with him...). I've been super impressed with SSD, and as cell size shrinks and endurance improves and costs drop, it looks like that will be the wave of the future. (they are currently working on 4T+ SSDs, and some drives like the Samsung Pro models offer 10 year warranties [for just under double the cost of their 3 year drives])
Ah...
I built gaming rigs for my two girls a year ago, and they have M2.2 slots in their motherboards. (right now they are on platters) Since the games they download/play (League, WOW, etc...) can take 50+G per-game, I wanted to wait until the 1T (or at least the 500G+) SSDs dropped a bit in price. The M2.2 SSD should offer quite a bit more performance over the typical SATA III interface. IIRC it uses 4-PCI buses combined for throughput as opposed to the SATA bus. But, at the time, I wasn't willing to drop another $600 where a pair of WD-Black 1T drives was $128.
My small server machine has one such slot and I'm not impressed with its performance. hdparm -tT does 462.42 MB/S. I haven't tested my laptop yet.
SSD really helps with I/O intensive apps and program load times. But once you app is loaded, then it doesn't really matter as long it doesn't do a lot of I/O. On the other hand, you can get a LOT of benefit out of the SSD speed for instance compiling desktops, etc... (but talk about beating the hell out of you SSD :)
Thanks again for the feedback Carlos.
Welcome :-) -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar)
On 2017-09-20 22:18, John Andersen wrote:
On 09/20/2017 12:59 PM, David C. Rankin wrote:
Then I would worry about the 42.2 install (actually, I wouldn't, I'd install 42.3 or 15 fresh on the ssd and then move /home from old install to new and just tweak the new config files as required)
That's what I did when I moved from HDD to SSD. I didn't have Win 10 to worry about.
I too worry that the dd-rescue will end up being a less than optimal solution.
At least Carlos will have the original disk to fall back on.
Oh, I know that dd_rescue (actually, dd_rhelp) works. I had to clone that laptop computer once already, when the original rust disk failed. The unknown here is the SSD. -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar)
On 2017-09-20 21:59, David C. Rankin wrote:
On 09/20/2017 11:13 AM, Carlos E. R. wrote:
Hi,
I'm going to migrate my laptop rotating hard disk (500 GB) to an SSD. I hope to give new life to it this way.
The machine is double boot Windows 10 / Leap 42.2, so I'm going to do image replication (dd_rescue), because otherwise Windows will not boot. So identical partition table.
Caveats you can think of? What about sector size, 4K issues?
No, but it is good to have you as the guinea pig :)
LOL! X'-) It turns out, to my surprise, the SSD is 512/512, so one issue that does not need worrying.
You are much braver than I would be. I don't know how the dd_rescue image will behave going from platter to ssd. In theory a partition is just a partition and a file-system is just a file-system, but I would be concerned that Win10 may rely on the disk serial in some way -- which may leave you fighting activation issues.
Oh, I half expect Windows to complain. :-} But the serial number can be written with fdisk, advanced menu. A dd also writes it, I have already noticed that it is the same in old and new disks (the copy has just started and will take about 4 hours: the SSD is on a USB caddy).
If dd_rescue fails, then my approach would be to use the Win10 (actually it's the old Win7) system image/restore in the old backup control panel. Just use a spare platter drive as your backup media and image your Win10 install to that. Then install the ssd and use the restore DVD (or thumb drive you created) to boot and restore the Win10 image from the platter to your new ssd.
Then I would worry about the 42.2 install (actually, I wouldn't, I'd install 42.3 or 15 fresh on the ssd and then move /home from old install to new and just tweak the new config files as required)
Either way you are probably at a break-even on time. Either spend the time with a new 15 install after Win10, or spend the time dorking with what didn't exactly work with the dd_rescue image ... ;-)
I'd prefer the dd to work ;-) I just leave it running and go do something else. It is running off a 13.1 XFCE Rescue stick, by the way: there is no Leap rescue system. -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar)
participants (4)
-
Carlos E. R. -
David C. Rankin -
James Knott -
John Andersen