On 22/03/2019 20.15, Patrick Shanahan wrote:
* Patrick Shanahan <paka@opensuse.org> [03-22-19 15:12]:
* 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).
ps: I deleted the old EFI partition created a new one and ran grub-install from the chroot system. the grub-install reported success.
EFI was not grub install, was something else... I'll search. [...] Andrei Borzenkov: AB> You can create ESP using any tool you are familiar with - fdisk, gdisk, AB> (g)parted, YaST. All offer mnemonic names for partitions so you do not AB> need to remember EFI System Partition ID or GUID. Format it as FAT32, AB> mount as /boot/efi. Then make sure you boot rescue medium in EFI mode, AB> chroot, make sure you have all btrfs subvolumes mounted (mount -a -t AB> btrfs) besides usual /sys, /dev, /proc and do "update-bootloader AB> --reinit". Assuming bootloader configuration was correct previously, AB> this should copy whatever files are necessary onto ESP and create NVRAM AB> boot entry. AB> AB> You can also use shim-install or grub2-install directly. 21.03.2019 20:34, Hagen Buliwyf пишет: HB>> HB>> grub2-install will "repopulate" the EFI-partition (mounted at HB>> "/boot/efi", however one can tell grub2-install explicitly which HB>> partition to use) and the UEFIs NVRAM. HB>> AB> It won't work if Secure Boot is enabled. That's precisely your problem... -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)