Le 06/04/2023 à 13:40, Per Jessen a écrit :
Boot a rescue system, mount the partition and fix the fstab. Fix the initrd at the same time.
I did that pretty often, but right now failing. I boot a rescue image, mount the root partition, and can access it. Then I mount --bind sys, dev and proc and chroot in /mnt. but then I was used to fire yast to make the hard work like editing fstab and updating the boot system. but here, no yast!! All the yast in /sbin or /usr/sbin are ??? (orphaned links? on the original disk they are there) I made the clone with clonezilla, may be a bug in it? I tried to fix fstab by hand, but with all the subvols it's hard I have till tomorrow to try booting this new computer, I ordered some more hardware for it. If not successful, I will reinstall, but I have some extra repos that are not that easy to cope with :-( the old laptop was intel i7 sata, the new is amd rysen nvme... thanks jdd -- mon serveur usenet: dodin.fr.nf c'est quoi, usenet? http://www.dodin.org/wiki/pmwiki.php?n=Usenet.Usenet