[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Debian will not boot any more, wrong UUID



On 9/30/23 19:59, hw wrote:
On Sat, 2023-09-30 at 17:34 +0200, Hans wrote:
Dear folks,

since days I am now fighting with a big and special problem I fell into.

On my notebook I have 2 drives, one is a NVME drive, the other a normal
harddrive.

The NVME has got Widows_11 and Debian_12 on it.

But here is the problem:

As I resized the Windows and Linux partitions, the UUIDs have changed. Thus,
now the root partition can not be found any more, as the UUID has changed.

This is not the only problem! Windows has changed the BIOS settings during an
update. Now it has set from AHCI to RAID. This is the first problem.

Second: The setting of AHCI has disappeared, so I can not change the settings
in BIOS. And: the BIOS can not be reflashed!

In the meantime I was able to disable UEFI in BIOS (with a trick), and it is
no AMI-BIOS. The BIOS is called "INSYDEH20" Rev. 5.0.

I tried hard, used lots of livefile systems (Ubuntu, Kali, Knoppix, Debian-
live, Debian-Installer in rescue mode, super-grub-disk, Rescatux and lots
more).

Whatever I do, no system is showing me /dev/nvme0pXXX! Of course tried nvme-
cli tools, without any success.

Important: The partitions and its content are still existent! I can get access
to them in Windows using a tool, which let me get access to the partitions and
its content. This means, I could edit /etc/fstab, if I could find out the
correct UUID.

At boot, I can edit the kernel params, there is root=UUID=MY_UUID, here I also
tried "root=/dev/nmve0p1n6", but also got no success. As I said, I can get
access to the /etc/fstab, but without the correct UUID it makes no sense.

I tried also a complete reinstall of Debian_12, but the installer does not see
/dev/nvme0XXXXX whatever. The kernel parameter "nvme_load=YES" did also not
help.

Now I am complete lost, because I have no more clue.

In short, things do not work:

1. Debian Installer does not see the harddrive (/dev/nvmeXXXX)

2. With UEFI enabled, most lifesystems do NOT boot.

3. All /dev/nvmeXXXXX can not be seen or activated

4. All UUID lost!

5. In BIOS there is no setting "AHCI/IDE/RAID" (existed once, but it is now
gone). Windows has obviously overwritten it.

I could install a fresh debian_12 on the second harddrive (which is no nvme),
but also from this one, I can not get access to the first harddrive (nvme),
even not with nvme-cli tools.

I would be happy, if someone would share some other ideas if any, as my ideas
at the moment are out.

Thank you for reading this and any help.

Oh, last but not least: A fresh install would be no problem, but the Debian
installer DVD does ALSO NOT see the /dev/nvme.

Big big problem.....

Thanks for reading and your help.

Best regards

Hans

Reset the BIOS and maybe try Fedora.  You do want to change back from
RAID to AHCI.

Why do the livesystems not boot?

What did you update, the BIOS or Windows?

I guess your notebook is now bricked.  If it's still under warranty,
have them fix it.


AIUI Windows 11 still works, so the notebook computer is not bricked; but it no longer plays nice with dual-boot Windows 11 and Debian on the NVMe drive.


I am curious if and what the Windows 11 update did to the notebook computer firmware and/or NVRAM settings. It would be helpful to know the Microsoft Knowledge Base number(s) for the update(s).


It seems the notebook came with AMI firmware, but the OP replaced it with alternate firmware:

    https://www.insyde.com/products


If the OP did change the firmware, I am curious if InsydeH2O® UEFI BIOS is supported on that specific manufacturer and model notebook computer, how the OP obtained InsydeH2O® UEFI BIOS, how the OP installed it, and if the OP knows how to reinstall the original firmware.


If I want to boot my Dell Precision 3630 (UEFI-only firmware) using a USB flash drive containing:

    debian-11.6.0-amd64-netinst.iso

Or boot a SATA SSD or a USB flash drive containing a working Debian UEFI instance, I must enter the firmware Setup utility, create a boot entry for the specific instance, and move the entry to the top of the boot order. It is unclear if the OP's notebook computer requires similar steps or if the OP attempted them.


David


Reply to: