Re: Adding a new boot disk while keeping old disk
On 10/12/2024 06:23, Charlie Gibbs wrote:
1. Do a network install on the new drive;
It was advised assuming that you would not do the following, otherwise
it is wasting of time:
sudo rsync -av /etc /mnt/backup
sudo rsync -av /lib /mnt/backup
sudo rsync -av /lib64 /mnt/backup
sudo rsync -av /sbin /mnt/backup
sudo rsync -av /usr /mnt/backup
sudo rsync -av /var /mnt/backup
Several years ago I successfully cloned Ubuntu (it should not be
relevant) from a hdd to a ssd. Though I used more rsync options
rsync -aXSHA --numeric-ids --progress -x
to ensure that other file attributes are copied.
6. Restore the new drive's /etc/fstab:
sudo cp -p ~/etc/fstab /mnt/backup/etc
Have you updated fstab to mount partitions from the new drive? Have you
created swap?
7. Re-boot from the new drive and cross your fingers.
Instead of crossing fingers I would check if more /etc files need
update: /etc/crypttab, /etc/default/grub, resume and smartmontools
configuration, etc. To make changes effective it is necessary to run
some tools (after chroot to new storage): update-grup, update-initramfs.
If the system is booted using UEFI you may need to migrate EFI system
partition and to update NVRAM (if it is not done by update-grub).
The system comes up with an xfce login window, but I can't log in
using my regular user ID. Sometimes the screen just goes black,
then after a couple of seconds re-displays a blank login screen.
Lately, though, I've been getting a window with the message:
Xsession: warning: unable to write to /tmp;
X session may exit with an error.
login as root from console (or connect using ssh)
systemctl --failed
Inspect for errors
journalctl -b
To verify that actual files meet dpkg expectations
dpkg -V
Reply to: