![]() ![]() ![]() This is the easiest way to handle things, generally. One common approach is to leave the a boot partition unencrypted, typically mounted on /boot, and then using LUKS encryption on only the root partition. If you read it carefully, you can figure out what was originally done. Well, the first thing you need to determine is: what part of your current disks are encrypted? If you run the lsblk command, that will show you disks, partitions, and mountpoints. ![]() I imagine it'd look something like this pseudo-code `rsync -source /media/old_drive_unlocked_partition -dest /media/new_drive_unlocked_partition` tar/rsync the entire partition on the old drive to the new one like a glorified cp -r? e.g.Unlock both drives' encrypted partitions.Mount the new drive & set it up with a new LuksFormat.Just to make sure I'm understanding, the process is along the lines of the following? I'm about to go google it now, but do you have any tips or tricks for the process?Īlso, I've never actually used rsync (it's forever been on my todo list as I've made due with `cp`, `tar`, and `scp`), but I've used tar a ton to make/extract tarballs. Not that I can't do that, just that I was being lazy haha :bigdumbgrin: Except for walking through the (fairly idiot-proof) setup steps as part of the Pop_OS install, I've never done a new LuksFormat on a drive before. I don't see why having the disk unlocked would cause an issue, but it's the only other thing I can think to test at the moment. Is there some nuance to cloning encrypted disks I am missing? My only guess at the moment is maybe if I boot from a live disk and copy the disks that way, that way the source SSD remains locked. I'm not really sure why this isn't working. Also, I've included a screenshot of GParted to show my disk's configuration. I've checked the User's Manual, and it is compatible with NVMe drives. This appears to be the same all gray screen, but there's nothing else displayed.įor reference, my computer is a Dell Inspilaptop. Usually on bootup I am greeted by the plymouth login screen, which is gray with a password prompt. After the Dell logo, the screen is completely gray. I used to dual boot Ubuntu and Windows, but I thought I had (purposely) completely wiped the drive during the Pop_OS install). I'm currently running Pop_OS, so this indicates to me that at least UEFI is able to read the disk (I was surprised by the latter 2 options. During initial bootup, while the Dell logo is still displayed, I hit F12 check the boot options, and I see three bootloaders listed: Pop_OS 20.04, ubuntu, and Windows. However, when I swapped the new drive into my computer and rebooted the system failed to completely boot. I used GParted to check the disk, and it shows the new disk as having the exact same setup as the old disk, just with a huge unallocated block at the end (which makes sense since I the source drive is 1/4 the size). Sudo dd if=/dev/sda of=/dev/sdc bs=4M status=progress ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |