There are a whole host of tweaks for SSD's, but reading through, I didn't really put many on.Īlso, by comparison, the time from power on to logon screen reduced from 28 secs on original HDD to about 13 secs on the SSD. I then expanded the partitions to fill the new drive (using the built in Windows tool again), reenabled the items disabled previously and disabled disk defragmentation so it wouldn't auto run. On swapping the disks after copying, booting from the SSD was fine (previous attempts at copying only partitions had failed)
Naturally, only the first 64GB of data was copied, hence why all the data needed moving to the front of the original disk. Used EaseUS Disk Copy to do a disk-to-disk on the system. Used GParted to move the recovery partition to the front of the disk (in all fairness, I could have just deleted this, but this also worked) Used the Windows 7 Disk Manager to shrink the system partition down as small as it would go (about 32GB - before doing the above steps, I could only shrink it to about 300GB as the above files sit in the middle of the partition and cannot be moved) Turned off hibernation, pagefile and system restore within Windows The solution I eventually came up with (and this assumes that, like me, you are on Windows 7): In my case I was going from a 500GB HDD to a 64GB SSD.Īfter thinking I could be clever by making HP restore disks and then restoring them, it turns out that you can only restore to an equal or greater size disk, so that idea went out of the window. It took a bit of faffing around to get it to work but I got there in the end. This should allow you to a) shrink the ext4 filesystem, b) the partion, c) the logical volume, d) the logical volume group and finaly d) the persitant volume.I did this with a PC the other week (HP Pro 6200) - did as such because of the environment it was going into. If the disk is a standalone disk (not part of a raid/SHR volume), you will need to make sure that the drive does have less that 100gb on its volume. Maybe the simplest solution would be to move the packages to other volumes and then simply replace the harddisk? Not sure how reliable it is, but moving packges usual does a solid job. Click to expand.You are aware that all drives are "sytem drives", aren't you? Or do you mean system drive as in "this is the volume where I install my packages and keep their data"? if you mean the later one, the worst thing that can happen is that the DSM will boot, but installed packages won't be available.
0 kommentar(er)
