* Carlos E. R. <robin.listas@telefonica.net> [03-22-19 14:33]:
On 22/03/2019 17.40, Patrick Shanahan wrote:
* Carlos E. R. <> [03-22-19 07:21]:
On 21/03/2019 21.23, Patrick Shanahan wrote: [...]
if that fails, the system does not boot and no yast ... ???
Ah.
Boot from rescue image, then mount the old partitions /somewhere, chroot to that, run yast there (text mode probably).
Before doing the actual chroot you need to mount bind /proc, /sys, /dev, etc:
mount --bind /proc /otros/test_a/proc mount --bind /sys /otros/test_a/sys mount --bind /dev /otros/test_a/dev
*** running system ********** system under repair
proc,sys,dev from the machine system, not the rescue image?
The "broken system" gets to see the rescue image directories as if they were its own, because they being virtual filesystem they will have nothing there. They will not match exactly what it expects to see, but usually it works.
There are files that might confuse the chrooted system, like mtab or network settings. In that case you will see messages about some error or other.
This trick can be used for other things, like running zypper dup on another partition that is not the actually running one :-)
ok, laptop will now boot but errs with: Boot failure : a proper digital signature was not found. One of the files on the selected boot device was rejected by the Secure Boot Feature. google has lots of answers but none that appear prudent. I don't want to disable secure boot as I want to restore the win10 partition(s). tks, -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Registered Linux User #207535 @ http://linuxcounter.net Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org