On 30/07/2019 13.44, Roger Oberholtzer wrote:
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.
Ah! Ok, my mistake. I always use UUID, which is cloned. I don't see a reason to use by-id, which I believe I have seen changing with OS updates. What is /etc/fatback? :-? Ok, then to update initrd you do: * boot a rescue system, preferably of same approximate version as the system rescued. * mount the system being rescued. Mount its "/", "/boot" and whatever it has in correct sequence. Possibly not "/home". * mount bind the /dev, /sys, and /proc filesystems (whatever they are on version 12) * chroot to the rescued system. * Possibly you may have to edit /etc/mtab on the rescued system. * If you need internet you may have to do other things. Now you can run programs of the rescued system, possibly yast boot module (in text mode). mkinird should work, but first edit fstab and grub (maybe lilo!). -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)