Roger
On Jul 30, 2019, at 13:31, Carlos E. R.
wrote: If you did that, the IDs are also cloned and no need to mess with them. If you have to change the IDs, you cloned differently.
The ID I’m referring to is the hardware serial number as in /dev/disk/by-id. If you use a different physical disk then this must be updated in /etc/fatback. Maybe it’s the boot config that defines hd(0) - in /etc somewhere. I’ll check when I’m back in the office.
How exactly, please?
We always mount by_id since there may be multiple disks. So, after the dd, one needs to mount the new disk and edit /etc/fstab with the new disk's ID. This has been done. The boot seems to then be looking for the correct disk.
However, the boot does not happen. It just hangs. The kernel command line is the only thing printed.
I do not have the disk in my possession (it's on a different continent). So, before I tell them to send it to me, I just want to be sure that I have not missed another step. Could there be a need to remake the initial ram disk? Is the disk id in there as well?
Certainly the initrd can have a copy of the old fstab. Also, there is grub, which has references to the old IDs.
If one has to do mkinitrd, how can one do that on a mounted disk (not the system's root disk)?
Or maybe it is something else?
First let's make sure that the IDs changed and why.
-- Cheers / Saludos,
Carlos E. R. (from 15.0 x86_64 at Telcontar)
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org