![]() The Next StepĬonnect the original SSD via USB (or via whatever).ĭon’t let expert mode intimidate you. Because the next step will wipe all of that out. When you’re installing this fresh copy of Windows, leave the network disconnected because you don’t want to get snagged into doing lengthy updates for no reason.įurthermore, don’t bother changing any settings or doing anything other than the default procedure. It rendered the SSD bootable to that partition.It created a 1.86TB (usable) partition for the OS.Then I installed a fresh copy of Windows 10 using the default settings. (You won’t have to do this if you’re starting from scratch, as there won’t be any partitions.) I put the new 2TB SSD in the laptop and wiped the partitions using gparted. Literally anything is better than just assuming you’ll pull this off without issue. Show the hex representations of each file to an android so that he/she/it can later recreate them via a keyboard with their hands but a blur. So before doing any of this back up your important files to a flash drive, another SSD, a hard drive, a cloud, or 4,000,000,000,000 punch cards. Heck, even if you do everything right, your original drive might decide to poop the bed. If you make one minor mistake while doing the below, you could wipe out all the data on your original drive. backup, but when I went to restore I got some obscure error about the volume shadow copy service (?).Īnd dd just caused the thing not to boot. Windows Image Backup worked to do the actual. (The new SSD was housed temporarily in a USB enclosure.) You can’t create a RAID array using a USB drive. The same error resulted when doing a proportional clone in Clonezilla. That ostensibly worked fine, but then I got the dreaded INACCESSIBLE_BOOT_DEVICE error. I couldn’t create a partition on it using Windows (either in the GUI or using diskpart), and so I tried booting into gparted and creating a new NTFS partition at the end of the disk. However I wasn’t going to shell out between $49 and $99 to do something that should be free.Ĭlonezilla had no problem actually cloning the drive, but a non-proportional clone resulted in the remaining ~1.75TB being unusable. The free versions of the paid tools (the former three) would not clone dynamic disks, though some claimed that the paid/pro version would. I tried EASEUS, AOMEI, Acronis, Clonezilla, creating a RAID1 array, Windows Image Backup and even dd. I didn’t think for a second that would render the drive un-clone-able by most any software. So I made the main boot drive a dynamic disk. In a moment of errant stupidity, I said, “Ah-hah! If I make the drive a dynamic disk, that will allow me to rearrange the partitions!” (It most certainly will not.) ![]() ![]() There was a system reserved partition at the very end of the disk, and Acronis therefore would not proportionally scale the OS partition to fill the disk It would only scale that system reserved partition. I have a version of Acronis that came with a Crucial (or Kingston?) SSD, which has worked great in the past. I wanted to upgrade the LITE-ON 256GB SSD in my trusty ol’ Lenovo X1 Carbon laptop to a snazzy new Samsung 960 EVO 2TB drive. (But I hope it helps you, too!) The Situation This is partially just for my own reference, so I don’t have to go down this rabbit hole again.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |