#Moving my system from one disk to another
69 messages · Page 1 of 1 (latest)
dd -if=oldroot -of=newroot
then use ext4 stuff to resize the newroot to use the whole partition
dd is slow because it copies everything, including the empty space
I usually create the new partitions and then rsync (with the right flags) and update the fstab, install the bootloader
That was my first idea, but it doesn't show up in the boot screen for some reason (maybe could because the other drive is still in, but I cant take it out because I can't find something to screw it out since yesterday)
Did you dd just the root or the whole drive
The whole drive
The new drive is identical
So there's no way to differentiate them
other than the model
The efi entry points to a GUUID
Old one is nvme, new one is ssd
grub?
If you boot either system they're going to be confused
because you have identical UUIDs
And UUIDs are different
But PARTUUIDs are the same
Nvme is the old drive
Sda the new one
And sdb is the bootable usb
UUID is in the filesystem, PARTUUID is in the GPT
They seem to be the same
I tried booting
It mounted root and /boot on nvme, but /home and /mnt/shared (another partition with windows filesystem) on ssd
p1 is vfat and sda1 is ext4 but they have the same PARTUUID
So you formatted either the p1 or the sda1
You need to either change the fstab to mount with by-id or detach the sda
/dev/disk/by-id
Also your bootloader may boot either of them because they're identical
You can change the UUID of ext4 partitions
tune2fs -U random /dev/sdXX
I'll just try booting the ssd on my dad's pc, see if that works rn
?
If your bootloaders efi file isn't in the fallback location then you can't boot it from a another pc
If grub then you need --removable
Otherwise there's a entry in the nvram
Because I can't take out the nvme disk because I can't finda small enough screwdriver
I missed that the nvme was the old one
because usually nvme is the new one
Yeah so you did something wrong because sda1 is now ext4
p1 was vfat
Yeah, that's true, but I am just using what I have around, and I found a larger ssd than my nvme
But you could have just mounted it
I haven't noticed that before
/boot can be ext4 but the esp must be fat32
and it's often mounted at /boot or /boot/efi
How should I fix this?
That didn't work
I tried dd if=p1 of=sda1 and by running blkid it seems to be fixed
It booted from sda
But for some reason decided to mount root on nvme
Change the UUID
For both of the ext4 on the nvme
And the vfat
tune2fs -U random /dev/sdXX # ext4
mlabel -i /dev/sdXX -N 12345678 # fat32
But that shouldn't be a problem if I am planning to overwrite the nvme drive?
(I'm dual booting and before I had linux on 500gb nvme and windows on 120gb ssd, now im planning to have linux on 1tb ssd and windows on 500gb nvme)
Well its a problem now as you can see
I think I'll keep it in mind if I'll need to do it, but now i want to reorganize my partitions on the new ssd
But your / is on the nvme still
....
So remember you're diverging the state
I'm mainly working from a bootable usb here