ZWQbpkzl [none/use name]

Filesystem sized is grown fine? If so wow that was easy.

I recently read that luks containers don’t actually know their size they will always adapt to the size of the entire disk (it makes shrinking them dangerous). So you should be good unless your SSD is bigger than your new nvme.

Very curious about how this goes. It might not work but it won’t wipe the original nvme. I’d love to hear how it goes.

I suspect your plan might be safer and less of a pain than pvmove. I’ve just never done that before so I can’t say for sure.

Be sure you can open and mount the USB ssd after the first dd. Also check the status of the disk size of the luks container. I’m assuming your dd’ing the encrypted partition not the data inside.

Look into pvmove. I’d take a backup with dd but try to do the actual move with pvmove. This might involve multiple steps if you can’t have both nvme’s installed at the same time. In that case I hope you have other drives.

Edit: I think what you’re doing won’t be a disaster because you’re not writing anything to the old nvme so that data is still there. So you won’t bork anything if the new drive doesn’t work.

• X11 is the displayer server, a real process running on your computer.
• X11 window managers are clients to that server. It communicates with the server and tells it where to draw the windows.
• A desktop environment is a window manager plus a whole suite of other applications and processes that a common computer user would expect.

A window manager and display server are the bare minimum of the x11 graphical environment. Desktop environment is draw the rest of the owl.

Wayland is is a completely different beast than x11. There is no Wayland program, just a wide set of protocols. There are no Wayland window managers, just “compositors”. Compositors are responsible for everything both the display server and window manager would do in x11. Everything is up to the compositor to implement. It just has to follow the Wayland protocols.

This can make migrating to Wayland a bit tricky. If a program worked in one x11 window manager, it was basically guaranteed to work in all window managers becuase it was always communicating to the same X server directly. In Wayland that’s not guaranteed. If a compositor didn’t (or didn’t correctly) implement a certain subset of protocols then the utility wouldn’t work correctly.

IE take xrandr and wlr-randr. They both are a , “display settings” CLI utility. xrandr works on any x11 environment because it always communicates with x11. wlr-randr only works if the compositor implements the wlr_output_management_unstable_v1 protocol. See the protocol deifnition here