On 17/07/2019 09.00, stakanov wrote:
In data mercoledì 17 luglio 2019 08:38:46 CEST, Felix Miata ha scritto:
stakanov composed on 2019-07-17 08:18 (UTC+0200):
more or less that is what I find. the machine was running for long time and was suspended before the update. NVRAM may be full? How could I free it in order to boot?
Surplus entries may be removed using the efibootmgr utility in a rescue mode boot. Simply enter efibootmgr in a root login shell to list all the entries. Man efibootmgr shows the options required to remove unwanted entries.
Thank you. I checked also in the bios. I have to say that it is very(!) misleading having this error in the log when you have (like in this case) another issue. In fact I had a ext4 problem on /home that would not mount but the error shown first in the logs and in the boot process is that stupid could not get uefi list.
You said the machine was suspended?
Suspended means suspended to RAM, different than hibernation, where the image is saved to disk. If the battery runs out while suspended, on next boot the machine has to recover from bad corruption on all the mounted partitions at the time of suspend. I did not know that. Yes, it was "suspend to ram" and yes, it may have been
In data giovedì 18 luglio 2019 01:42:08 CEST, Carlos E. R. ha scritto: that the suspended partition was not correctly recovered when the update required a reboot. So the corruption may be a result of this. Thanks for the heads up. However, I still get the "could not get uefi list" while the uefi entries are correct and no residuals are to be found. I think that that error is because the machine has secure boot without a TPM. _________________________________________________________________ ________________________________________________________ Ihre E-Mail-Postfächer sicher & zentral an einem Ort. Jetzt wechseln und alte E-Mail-Adresse mitnehmen! https://www.eclipso.de -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org