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
In data mercoledì 17 luglio 2019 08:38:46 CEST, Felix Miata ha scritto: list. Once done a fsck on /sdc1 which was home I found invalid inodes (which is bad enough, I will have to see which problem/corruption that may bring after repair) and repaired. Now the system boots. The point is that this error does still appear. Should I go after it and "repair it"? I will try with efibootmgr if you think it is useful, so at least from that side there will be no problem. _________________________________________________________________ ________________________________________________________ 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