Don't forget to mark the / root filesystem as active / bootable, just like your old SSD. Try to keep everything the same as your old SSD's partition table (aside from partition sizes and UUID's). Use gparted to set up your new SSD with the desired partition table and format the filesystems.Mixing things up would make it a lot harder to get grub to install properly later on. If my assumption is invalid, make sure your BIOS boots the thumbdrive in UEFI mode instead. Make sure your BIOS always boots the thumbdrive in legacy/MBR mode instead of UEFI mode, since it sounds like your old system is using MBR. Boot from the Ubuntu installation USB thumb drive in Linux live mode.Keeping the old SSD disconnected makes it impossible to destroy any of our precious data while we do potentially destructive work. Connect the new SSD to the computer and disconnect the old SSD.Take a screenshot of your old SSD's partition table for reference later when we set up your new SSD's partition table.Here's what I would do if it were my system: Using dd to copy a partition with lots of free space ends up copying EVERY BYTE of said partition, even the bytes that aren't actually containing any allocated data! Most partitions are typically no where near 100% utilization. The other problem is that dd is slow and puts unnecessary wear on your target SSD. if= and of= are only one small mistyped keystroke away from each other! The only thing keeping it working right is if you're VERY careful with typing the commands correctly and not mixing up the source and destinations. dd has no safeguards for accidentally writing your new drive over the old drive. disk destroyer) there is a potential for messing up your data. This can be done by first mount the new drive after cloning: sudo mount /dev/sdc1 /mnt/, then edit the /mnt/etc/fstab file.Īm I right about all of this? Any potential risk of messing up my old drive here? Thanks a lot!Īny time you use dd (a.k.a. This approach will save me from resizing the disk.Īnd for both approaches, I need change the UUID in the /etc/fstab file. By doing this I made it bootable and also preserved the partition table for 500GB+500GB. So I canĭd if=/dev/sda of=/tmp/mbrsda.bak bs=512 count=1 then dd if=/tmp/mbrsda.bak of=/dev/sdc bs=446 count=1. At this point, this disk should be unbootable, right? In order to make it bootable, I need copy the bootloader into the new one. do dd if=/dev/sda1 of=/dev/sdc1 and dd if=/dev/sda2 of=/dev/sdc2 to clone both partitions. The resizing might take long, right?Ģ) The second approach is format the new drive first, make two 500GB partitions. Right? Then I need resize the sdc1 and sdc1 into 500GB with something like gparted. After this I should get a bootable disk with two 125 GB partions and some unallocated space. After some research, I proposed two approaches:ġ)do dd if=/dev/sda of=/dev/sdc to clone the whole disk. Now I want to move everything into a new 1TB ssd (let's say it is /dev/sdc) and expand each drive into 500GB. The sda1 is mounted to / and sda2 is mounted to /home. I am running Ubuntu on a 250GB ssd (/dev/sda) which has two partitions, each is about 125GB big. Since mistakes could easily destroy my drive and data, I really want things to be clear. I have search for an answer for a while but not sure I got the correct answer.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |