To the questions in the previous post:
What is this bios issue?
when the service person from LENOVO came and exchanged the mainboard, the mainboard was not with the newest BIOS. After the new motherboard was mounted, the service person flashed with an USB stick (if I remember, for sure it was not done with an ISO on CD) the motherboard with the newest BIOS version. When I boot the notebook with a Debian8 live USB, I can see the BIOS version indicated in DMESG is the same than the BIOS of the "old defect" motherboard (I have an DMESG file from the defect mainboard).
Did you do it already?
With the "old defect" motherboard, I made a BIOS update with an ISO on CD (from the LENOVO page). It worked fine. After that BIOS update I made End February I could boot the PC. Only the new motherboard with the updated BIOS dont boot my SSD.
Is there any bios setting that reports devices like drives or ssd's?
The view of the BIOS settings is in a previous post. We can see an ATA HDD0 Samsung (which is in fact the SSD)
From a brief look at your problem I mentioned if NvMe0 isn't the ssd.
I had a look at LENOVO page where they speak about that "drive".
https://forums.lenovo.com/t5/ThinkPa...t/td-p/3295287 This is perhaps a partition recognized by the BIOS. I moved that NvMe0 as first in the boot priority but it did not boot.
The question which came in my head is: perhaps I should re-install Debian9 again? during the installation, perhaps few key parameters are overtaken by the UEFI setup of Debian9 on the SSD. Or perhaps there is a Debian9 UEFI setup to run again in order to have a correct link between the BIOS, the MBR and the Grub bootloader. But: it should be a remote setup because the notebook dont boot from the SSD.
And:
https://wiki.debian.org/GrubEFIReinstall a repair is perhaps necessary after each BIOS update and/or motherboard change.
In the Debian8 USB boot session, I made..
download the deb package from
http://www.rodsbooks.com/refind/getting.html
install it
Quote:
sudo dpkg -i refind_0.10.7-1_amd64.deb
|
Quote:
Selecting previously unselected package refind.
(Reading database ... 152599 files and directories currently installed.)
Preparing to unpack refind_0.10.7-1_amd64.deb ...
Unpacking refind (0.10.7-1) ...
Setting up refind (0.10.7-1) ...
/var/lib/dpkg/info/refind.postinst: line 4: efibootmgr: command not found
ShimSource is none
Installing rEFInd on Linux....
The ESP doesn't seem to be mounted! Trying to find it....
Mounting ESP at //boot/efi
ESP was found at //boot/efi using vfat
Running in BIOS mode with no existing default boot loader; installing to
//boot/efi/EFI/BOOT
Note: IA32 (x86) binary not installed!
Copied rEFInd binary files
Copying sample configuration file as refind.conf; edit this file to configure
rEFInd.
Installation has completed successfully.
Processing triggers for man-db (2.7.0.2-5) ...
|
So, now the notebook boot into "rEFInd" before it goes into my Debian9 (update/upgrade works; all partitions and files accessible). Now, I should find a method to get rid of rEFInd and boot directly into grub & Debian9 as previously (whatever, booting first in rEFInd is not a massive issue; just not necessary for the usual use).
Topic CLOSED (I open another thread later to get rid out of rEFInd).
Thanks to jefro for the help.