Why not retain the settings of the UEFI on the laptop?

To begin with prehistory breakage.

Given the laptop is Lenovo Ideapad Flex 10 running OpenSuse Tumbleweed. A week ago, unfortunately, suffered a fall on a floor from height of human growth and got a little cosmetic damage.

Through the day I found out that it was severely damaged hard drive (more than 8 thousand bad blocks) and one section is severely damaged.

If you try replacing the screw also found another oddity with UEFI:
1. Saved only 2 custom settings and no more: this is the date and time hardware clock and password to access the hard drive. All other settings are not saved. Reset to factory settings also does not change the settings.
2. The program efibootmgr can not create, delete, modify, and fine to use records in UEFI on boot. When command execution error occurs "Interupted system call". The result is UEFI cannot boot from a flash drive or to find grub on the new hard drive and always tries to load the old system.

There is a suspicion that a corrupted NVRAM Board and it allows you only to read information but not write. This implies the following questions:
1. Can you check if the NVRAM is corrupted (Ala fsck)?
2. As you can see that the problem is caused by NVRAM?
June 10th 19 at 15:40
1 answer
June 10th 19 at 15:42
Data UEFI might lie on the hard, in the HPA area or somewhere in the area. Saw this, not only the settings were lying, but the backup uefi.
That is not saved, for hard dead. Reading from sehardcore default settings. Password screw is in the flash of the controller screw, clock - in RAM of the RTC block, because it is stored.
Hmm, that explains why everything is bad except for one nuance. Settings saved do not default from the factory, and the last successfully stored.

Then you can try using dd to throw from the hard drive to the hard drive EFI and will it help? - abbey_Rath55 commented on June 10th 19 at 15:45
You can try, but unlikely to help. On the drive from the factory (more precisely, from the place of Assembly of the laptop) has a HPA area of 500 meters. There lies the backup uefi settings. After exiting the uefi part of the disk is no longer available to all, it is blocked once until the next reset of the disk to read the area is just sticking the drive into a usb sata adapter.
Maybe leg fell off WP from SPI flash on the Board, and now the chip is locked on the entry. - julie_DAmore commented on June 10th 19 at 15:48
okay, did not help.

And what motherboard you can find "leg WP from SPI flash" and is it possible to restore it by yourself? Or for those already in service to apply? - abbey_Rath55 commented on June 10th 19 at 15:51
with this in service. The flash drive is not likely to SO8 and without equipment there will not do anything. - julie_DAmore commented on June 10th 19 at 15:54

Find more questions by tags UEFISystem administrationLinux