I recently added a Samsung 990 4TB SSD to my Legion Slim 5 to replace the original 512GB drive. After installing the new SSD, I used Disk Management to allocate it and assigned it a drive letter (D). I then utilized Clonezilla to clone my old drive, resizing the partitions in the process. While the new drive boots correctly, I noticed a problem: both the C and D drives appear to have almost the same available space in File Explorer. Disk Management shows that C has 474GB and D has a capacity of 3710GB, but the storage usage shows D with only 23.6GB free and 3.59TB used. Also, there's a difference in how the partitions are labeled - the old drive shows 'boot volume' in the Windows-SSD partition while the new one has 'system volume' in SYSTEM_DRV. I feel like I'm really close to resolving this but something seems off with the partitioning.
2 Answers
You might want to check how Clonezilla handled the cloning process. Some tools, like Macrium Reflect, automatically handle the partition layout for you when you clone. It might be worth looking at your Disk Management setup - could you share a screenshot to see what it looks like?
Cloning isn't always the best option and can lead to issues like you're experiencing. With modern SSDs and fast internet speeds, consider backing up your files to a flash drive and performing a fresh Windows installation on the new drive. It’ll clear up a lot of potential complications!
If I decide to go that route, can I just reformat the new SSD first? Do I need to partition it in a certain way before the Windows installation, or does that get handled during the setup?
Sure thing! Here's the link to my Disk Management screenshot: [https://imgur.com/a/EqpUcRq](https://imgur.com/a/EqpUcRq)