T480 Upgrade internal 2280 NVME SSD 256 to !Tb

[TeraByte Support(PP)]

Since it's a RAM cache it wouldn't affect things like hibernation or fast startup do. However, you'd need to be careful about power interruptions and it may not actually improve performance (it may just add risk). I would assume it wouldn't cause issues creating backups.

[ronk]

OK, I will leave the 'Momentum Cache' disabled, though recommended by Crucial to reduce random read/write wear over time on a boot drive. The SSD is the P3 1TB PCIe Gen3 3D NAND NVMe M.2 , rated up to 3500MB/s - CT1000P3SSD8. According to CrystalDiskMark, getting 1/2 the rated speed, which is expected since the T480 is only using the 2 lane vs. 4 lane interface. Happy with the upgrade.

Ron

insert-terabyte1.jpg (73.3 KiB) Viewed 1521 times

[ronk]

Perhaps should be a new posting, but I took the next step on my T480 and added a second 512gb m.2 2242 NVME PCIe3 x2 SSD in the WAN slot. I would like to make it the Boot drive instead of the 2280 SSD, but I don't want to have to reinstall Windows 11. I have full image of the current Disk0 SSD1. If I remove (temporarily) all but the boot (C:) partition from SSD1, can I clone the OS to the other internal SSD with the copy or restore function of TBWINRE IFW, and if so, what settings do I need?

Ron

[TeraByte Support]

restore the entire drive and ensure you use the change disk id and guids option.

[ronk]

Need some help. From the internal 1TB NMVE drive, deleted all but the C Drive partition 117Gb, 60 used(Windows11), rest unallocated, with the EFI system partition at the end. Next I did IFW full backup with TBWINRE. Then attempted first a Restore Full to the internal 256Gb NVME, DiskID and GUID box checked, and 'Scale to Fit'. It failed during with 'reduction failed'. So tried again only this time with 'Scale to Target', but got the same error during the resize process part 2 of 4.

What might I be missing so that the Restore completes. Also, curious at what point the DiskID and GuID get changed, is that automatic?

I am in a 'hold' pattern until this is resolved or not, using my backup laptop for now.

Thanks,

Ron

[TeraByte Support]

1 - add the remove gaps option.
2 - for resizing, you may need to chkdsk /f your partitions to ensure they are clean before doing the backup.

also, be specific with any messages and error codes it gives.

[ronk]

I added the 'remove gaps' checkbox along with 'scale to target' and change diskID and Guid, with the same result. It occurs during the filesytem check that is done after the resizing.

Specific error popup:
Partition Reduction Failed (3/2/14592)
Please run a file system check.

I haven't yet done a chkdsk /f on the single boot partion/C Drive because I have read that doing that on an SSD can have harmful effects. Is there any truth to that?

Ron

[TeraByte Support]

It's complaining about an attribute too large after the resize - running chkdsk /f isn't going to hurt a ssd.

You'd typically use scale to fit not scale to target, or just restore without any scaling and use remove gaps/change disk id / guids.

If you still have problem after chkdsk /f and new backup, If you can make that image available for download, contact support at support@ and it can be tested here.

[ronk]

Actually completed the OS migration from SSD to SSD before your last note. All worked well after 1) chkdsk /f 2) full backup 3) full restore with remove gaps, change disk id & guids. I did use scale to target, even though apparently didn't need it, per your last note. Then restored the data partitions and all works without a hitch.

Temperature of the 2nd 2242 SSD is warmer (113F), as before the OS move, than the 2280 SSD (90F), so no big change there.

Thanks for the helpful tips.