Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #262011 > unrolled thread

Debian will not boot any more, wrong UUID

Back to article view | Back to linux.debian.user

Contents

  Debian will not boot any more, wrong UUID Hans <hans.ullrich@loop.de> - 2023-09-30 17:40 +0200
    Re: Debian will not boot any more, wrong UUID David Christensen <dpchrist@holgerdanske.com> - 2023-10-01 02:50 +0200
      Re: Debian will not boot any more, wrong UUID Hans <hans.ullrich@loop.de> - 2023-10-01 20:00 +0200
    Re: Debian will not boot any more, wrong UUID hw <hw@adminart.net> - 2023-10-01 05:10 +0200
      Re: Debian will not boot any more, wrong UUID David Christensen <dpchrist@holgerdanske.com> - 2023-10-01 09:10 +0200
        Re: Debian will not boot any more, wrong UUID Hans <hans.ullrich@loop.de> - 2023-10-01 19:50 +0200
          Re: Debian will not boot any more, wrong UUID Stefan Monnier <monnier@iro.umontreal.ca> - 2023-10-01 20:20 +0200
            Re: Debian will not boot any more, wrong UUID Hans <hans.ullrich@loop.de> - 2023-10-01 20:40 +0200
              Re: Debian will not boot any more, wrong UUID Stefan Monnier <monnier@iro.umontreal.ca> - 2023-10-02 01:00 +0200
        Re: Debian will not boot any more, wrong UUID hw <hw@adminart.net> - 2023-10-01 22:30 +0200
      Re: Debian will not boot any more, wrong UUID Hans <hans.ullrich@loop.de> - 2023-10-01 19:10 +0200
        Re: Debian will not boot any more, wrong UUID Jeffrey Walton <noloader@gmail.com> - 2023-10-01 19:40 +0200
          Re: Debian will not boot any more, wrong UUID Hans <hans.ullrich@loop.de> - 2023-10-01 20:30 +0200
        Re: Debian will not boot any more, wrong UUID Eduardo M KALINOWSKI <eduardo@kalinowski.com.br> - 2023-10-01 21:20 +0200
        Re: Debian will not boot any more, wrong UUID Hans <hans.ullrich@loop.de> - 2023-10-01 21:30 +0200
          Re: Debian will not boot any more, wrong UUID David Wright <deblis@lionunicorn.co.uk> - 2023-10-02 05:10 +0200
    Re: Debian will not boot any more, wrong UUID "Andrew M.A. Cater" <amacater@einval.com> - 2023-10-01 16:30 +0200
      Re: Debian will not boot any more, wrong UUID Hans <hans.ullrich@loop.de> - 2023-10-01 19:50 +0200
        Re: Debian will not boot any more, wrong UUID Jeffrey Walton <noloader@gmail.com> - 2023-10-02 00:40 +0200
    Re: Debian will not boot any more, wrong UUID Michel Verdier <mv524@free.fr> - 2023-10-01 20:30 +0200
      Re: Debian will not boot any more, wrong UUID Hans <hans.ullrich@loop.de> - 2023-10-01 20:50 +0200
        Re: Debian will not boot any more, wrong UUID Michel Verdier <mv524@free.fr> - 2023-10-02 00:20 +0200
    Re: Debian will not boot any more, wrong UUID The Wanderer <wanderer@fastmail.fm> - 2023-10-01 20:50 +0200
      Re: Debian will not boot any more, wrong UUID Hans <hans.ullrich@loop.de> - 2023-10-01 21:40 +0200
        Re: Debian will not boot any more, wrong UUID The Wanderer <wanderer@fastmail.fm> - 2023-10-01 23:50 +0200
          Re: Debian will not boot any more, wrong UUID The Wanderer <wanderer@fastmail.fm> - 2023-10-01 23:50 +0200
        Re: Debian will not boot any more, wrong UUID Steve McIntyre <steve@einval.com> - 2023-10-02 10:50 +0200
          [SOLVED] Re: Debian will not boot any more, wrong UUID Hans <hans.ullrich@loop.de> - 2023-10-02 17:20 +0200
    Re: Debian will not boot any more, wrong UUID Felix Miata <mrmazda@earthlink.net> - 2023-10-01 22:40 +0200
    Re: Debian will not boot any more, wrong UUID Curt <curty@free.fr> - 2023-10-02 17:10 +0200
      Re: Debian will not boot any more, wrong UUID Hans <hans.ullrich@loop.de> - 2023-10-02 17:20 +0200

Page 1 of 2  [1] 2  Next page →

#262011 — Debian will not boot any more, wrong UUID

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

[toc] | [next] | [standalone]

#262027

On 9/30/23 08:34, 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


Please provide manufacturer names and part numbers for:

* notebook computer

* NVMe drive

* hard drive


David

[toc] | [prev] | [next] | [standalone]

#262057

Hi David, 


> 
> Please provide manufacturer names and part numbers for:
> * notebook computer
Acer Aspire A317-51G

> 
> * NVMe drive
> 
Kingston manufacturer, do know not more

> * hard drive
normal SSD (I intend to install Debian on this as subtitute)

> 
> 
> David

The BIOS is INSYDEH20, Rev. 5.0 (latest version), this was original on the 
notebook when it was bought. (Yes, I know, I am sking myself, which idiot is 
using such a BIOS, and not AMI or hmmmmmm, Phoenix.)

Oh, and by the way, it is not my notebook, it is belonging a friend.

Best regards

Hans

[toc] | [prev] | [next] | [standalone]

#262029

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.

[toc] | [prev] | [next] | [standalone]

#262031

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

[toc] | [prev] | [next] | [standalone]

#262056

Hi David,

> 
> 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.
> 

Yes, as Debian can not be booted any more, due to the wrong UUID of the root 
device.
> 
> 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 overwrote the BIOS setting from AHCI to RAID and let this menu point 
disappear in the BIOS.

> It seems the notebook came with AMI firmware, but the OP replaced it
> with alternate firmware:
> 
>      https://www.insyde.com/products
> 

NOPE, it came original with INSYDEH20 BIOS, NOT an AMI BIOS.
> 
> 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.
> 

Nope, it is factory original.
> 
> 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
> 

Tried this, but no success.

> 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.
> 


Nope, tried this, too. No success.
> 
> David


Thanks for help, David!

Best regards

Hans

[toc] | [prev] | [next] | [standalone]

#262059

>> 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.
> Yes, as Debian can not be booted any more, due to the wrong UUID of the root 
> device.

I don't understand how the UUID could be such a hard problem.

I can see that a change in UUID could pose a problems but not an
insurmountable one.

Maybe if you give some more details, people will be able to help.
This said, if you don't have a /dev/nvme* and the disk you need to
access is accessed via nvme, then no amunt of UUID change will help you
(the UUID is just one of the ways you can name the disk, but the actual
access needs to go through the /dev/nvme* thingy in the end anyway).


        Stefan

[toc] | [prev] | [next] | [standalone]

#262062

Hi Stefan,

that is easy to explain. The kernel is searching for a device with the special 
UUID. As I changed the size of the partition with gparted, the UUID changed.

Now the kernel says: This UUID is not existent, what is correct (kernel param: 
root=UUID=MyUUIDXXXXX)

I can not get the new UUID (blkid -l /dev/nvme0Pn6) , because no livesystem 
does see any /dev/nvme. If I could, I could edit the kernel param and set the 
correct UUID by hand. (as you know, in grub I can edit the boot parms).

This is the problem.

Hope this makes things clearer.

Best 

Hans
 
> I don't understand how the UUID could be such a hard problem.
> 
> I can see that a change in UUID could pose a problems but not an
> insurmountable one.
> 
> Maybe if you give some more details, people will be able to help.
> This said, if you don't have a /dev/nvme* and the disk you need to
> access is accessed via nvme, then no amunt of UUID change will help you
> (the UUID is just one of the ways you can name the disk, but the actual
> access needs to go through the /dev/nvme* thingy in the end anyway).
> 
> 
>         Stefan

[toc] | [prev] | [next] | [standalone]

#262080

> that is easy to explain. The kernel is searching for a device with the
> special  UUID. As I changed the size of the partition with gparted,
> the UUID changed.
>
> Now the kernel says: This UUID is not existent, what is correct
> (kernel param:  root=UUID=MyUUIDXXXXX)
>
> I can not get the new UUID (blkid -l /dev/nvme0Pn6) , because no
> livesystem  does see any /dev/nvme. If I could, I could edit the
> kernel param and set the  correct UUID by hand. (as you know, in grub
> I can edit the boot parms).
>
> This is the problem.

So the problem is not the UUID, it's the lack of /dev/nvme*
[ E.g. using the "right" UUID wouldn't magically let you access that
  partition.  ]


        Stefan

[toc] | [prev] | [next] | [standalone]

#262071

On Sun, 2023-10-01 at 00:01 -0700, David Christensen wrote:
> On 9/30/23 19:59, hw wrote:
> > 
> > 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.

Right, it's bricked.  What good is a computer when you can't run the
software you want to run on it.

It's kinda like a bicycle you can't ride on paved surfaces.  Such a
bycicle is effectively bricked.  There aren't many surfaces that
aren't paved you could ride on, and riding bicycles on unpaved
surfaces is even worse than riding a bycicle ...

[toc] | [prev] | [next] | [standalone]

#262053

Hi, 

reset did not work. The menu for setting AHCI has completely disappeared

The livesystems do not boot, as UEFI inhibits it. And in the BIOS UEFI can NOT 
be disabled!

I updated Windows from Win_10 to Win_11.

It is not bricked, please read my first mail carefully: I canm still access the 
ext4 partitions from Windows (using Paragon drivers) and the data are still on 
the partitions.

The kernel is still starting, but does not find the root partition, as the UUID 
is wrong.

And I can not get the correct UUID, as no Linux livefile does see the /dev/nvme 
partitions.

Hope this makes it clearer.

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.

[toc] | [prev] | [next] | [standalone]

#262054

On Sun, Oct 1, 2023 at 1:09 PM Hans <hans.ullrich@loop.de> wrote:
>
> reset did not work. The menu for setting AHCI has completely disappeared
>
> The livesystems do not boot, as UEFI inhibits it. And in the BIOS UEFI can NOT
> be disabled!

Sometimes you need to set a BIOS password to unlock additional menu
items, like an item to disable Secure Boot.

Acer laptops are like that. I think Acer also uses Insyde for their
firmware upgrades, <https://www.google.com/search?q=Acer+Insyde>.

Jeff

[toc] | [prev] | [next] | [standalone]

#262061

Am Sonntag, 1. Oktober 2023, 19:25:39 CEST schrieb Jeffrey Walton:
> On Sun, Oct 1, 2023 at 1:09 PM Hans <hans.ullrich@loop.de> wrote:
> > reset did not work. The menu for setting AHCI has completely disappeared
> > 
> > The livesystems do not boot, as UEFI inhibits it. And in the BIOS UEFI can
> > NOT be disabled!
> 
> Sometimes you need to set a BIOS password to unlock additional menu
> items, like an item to disable Secure Boot.
> 
> Acer laptops are like that. I think Acer also uses Insyde for their
> firmware upgrades, <https://www.google.com/search?q=Acer+Insyde>.
> 
> Jeff

Hi Jeff,

yes, I tried this, and if I set a password for the hdd in BIOS, I can disable 
UEFI. However, the nvme-drive needs UEFI activated, thus my livesystems won't 
boot.

I tried to overwrite the actual firmware, but as it was the newest one, the 
installer inhibits to overwrite the existing BIOS.

Hope this make things clearer

Best

Hans

[toc] | [prev] | [next] | [standalone]

#262066

On 01/10/2023 14:08, Hans wrote:
> The kernel is still starting, but does not find the root partition, as the UUID
> is wrong.
> 
> And I can not get the correct UUID, as no Linux livefile does see the /dev/nvme
> partitions.

I don't think the problem is an incorrect or changed UUID, but simply 
that you SSD is not being detected, and so it cannot find the partition 
with the given UUID (it can't find any partitions, I'd guess).

Sorry I can't be of more help.

-- 
The only difference in the game of love over the last few thousand years
is that they've changed trumps from clubs to diamonds.
		-- The Indianapolis Star

Eduardo M KALINOWSKI
eduardo@kalinowski.com.br

[toc] | [prev] | [next] | [standalone]

#262067

[Multipart message — attachments visible in raw view] — view raw

Some other idea: As the kernel boots, but does not find the root-partition, I am stopping at the 
shell

(initramfs) 

Is there anything I can do from this point? 

I also see, that the kernel tries to find some "block" device, but i am not sure, what he actually 
does Kernel output is:

--------------------

Begin: Running scripts/local-block  ... done

--------------------

for about 10 times, then stops with:

--------------------

Gave up waiting for file root file system device. Common problem:
- Boot args (cat/proc/cmdline)
- Check root-delay= (did the system wait long enough?)

- Missing modules (cat /proc/modules; ls /dev)

Alert: /dev/nvme0n1p6 not exist.. Dropping to a shell.

BusyBox v1.35.0 (Debian 1: 1.35.0-4+b3) built-in shell (ash)
Enter 'help` for a list of built in commands

(initramfs)


--------------------

I looked at ls /dev/block and saw some 8:0 , 8:1 , 8:2 etc, but not sure, if these are my partitions.

Can I do more fron this shell?

Hans


 

[toc] | [prev] | [next] | [standalone]

#262082

On Sun 01 Oct 2023 at 21:27:17 (+0200), Hans wrote:
> Some other idea: As the kernel boots, but does not find the root-partition, I am stopping at the 
> shell
> 
> (initramfs) 
> 
> Is there anything I can do from this point? 
> 
> I also see, that the kernel tries to find some "block" device, but i am not sure, what he actually does 

Disks, USB sticks, SD cards, and so on, are all block devices.

> Kernel output is:
> 
> --------------------
> 
> Begin: Running scripts/local-block  ... done
> 
> --------------------
> 
> for about 10 times, then stops with:
> 
> --------------------
> 
> Gave up waiting for file root file system device. Common problem:
> - Boot args (cat/proc/cmdline)
> - Check root-delay= (did the system wait long enough?)
> 
> - Missing modules (cat /proc/modules; ls /dev)
> 
> Alert: /dev/nvme0n1p6 not exist.. Dropping to a shell.
> 
> BusyBox v1.35.0 (Debian 1: 1.35.0-4+b3) built-in shell (ash)
> Enter 'help` for a list of built in commands
> 
> (initramfs)
> 
> 
> --------------------
> 
> I looked at ls /dev/block and saw some 8:0 , 8:1 , 8:2 etc, but not sure, if these are my partitions.

Yes, they'll be symlinks to the appropriate /dev/… devices. Under
normal circumstances, they'll have equivalent entries like
/run/udev/data/b8:0, which contain plain text information about
the corresponding device file.

8:0 will be the disk device, and 8:1 … will be partitions. However,
8 means they're probably the "normal harddrive", mentioned at the
top of your OP. Check there is the correct number of them—but
don't be fooled by seeing 8:16, 8:17 …, which would mean that you've
got a USB stick plugged in. Or if you booted from an SD card, you
might see symlinks like 179:0 …

However, the "NVME drive" would typically be numbered 259:0, 259:1 …
rather than 8:0.

> Can I do more fron this shell?

I'm afraid stopping at this point (rather than earlier or later
in the booting up sequence) is something I've never done.

BTW your OP confused me somewhat— In the summary you wrote:

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

Presumably you meant: "NVME drive (/dev/nvmeXXXX)"; and so you can
see what you called the "normal harddrive", ie those 8:0 … devices.
I guess you have both Windows and Linux OSes on the NVME disk, which
is why you had to resize things. What's the "normal" harddrive for?

Cheers,
David.

[toc] | [prev] | [next] | [standalone]

#262045

On Sat, Sep 30, 2023 at 05:34:31PM +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.
> 

I hate to say this: you need to reinstall Windows 11, potentially and then
reinstall Debian. AHCI is the appropriate setting - maybe if you wipe the
machine it should work.

Quite often, the machine has a setting in firmware which embeds a Windows
licence key these days.

Windows first, then Debian, I think.

All best, as ever,
> 
> 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
> 
> 
> 

[toc] | [prev] | [next] | [standalone]

#262055

I already thought of this. Problem is in the BIOS, as I can not set AHCI there 
(Menu disappeared), so no Linux sees the device.
  
> I hate to say this: you need to reinstall Windows 11, potentially and then
> reinstall Debian. AHCI is the appropriate setting - maybe if you wipe the
> machine it should work.
> 
> Quite often, the machine has a setting in firmware which embeds a Windows
> licence key these days.
> 
> Windows first, then Debian, I think.
> 
> All best, as ever,
> 

Best 

Hans

[toc] | [prev] | [next] | [standalone]

#262078

On Sun, Oct 1, 2023 at 6:29 PM Hans <hans.ullrich@loop.de> wrote:
>
> I already thought of this. Problem is in the BIOS, as I can not set AHCI there
> (Menu disappeared), so no Linux sees the device.

Maybe it is hidden?

https://superuser.com/questions/1711770/unlock-advanced-menu-hidden-in-bios

Jeff

[toc] | [prev] | [next] | [standalone]

#262060

On 2023-09-30, Hans wrote:

> 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.

Did you change both kernel param and fstab ? You can use /dev/xxx in
fstab, no need to know the uuid.

You can also add the kernel param biosdevname=0 to get the old name. In
this case your nvme should be the first so named /dev/sda.

If you don't remember partitioning you can install cygwin and use fdisk
on it. cygwin also provides blkid to get label and uuid.

[toc] | [prev] | [next] | [standalone]

Page 1 of 2  [1] 2  Next page →

Back to top | Article view | linux.debian.user

csiph-web