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 2 of 2 — ← Prev page 1 [2]

#262063

Am Sonntag, 1. Oktober 2023, 20:24:40 CEST schrieb Michel Verdier:


Hi Michel,> Did you change both kernel param and fstab ? You can use /dev/xxx 
in
> fstab, no need to know the uuid.
> 
I tried /dev/nvmeXXXXX (I could see the correct device in /etc/fstab "device 
was /dev/nvmeXXXX at inbstallation"), but this did not help.

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

Hmm, this I did not try! Will try it tomorrow.
> 
> If you don't remember partitioning you can install cygwin and use fdisk
> on it. cygwin also provides blkid to get label and uuid.

I tried to get the UUID in Windows but I am not sure, if GUID (Microsoft 
naming?) is the same as UUID in Linux. 


Setting the GUID in kernel parm did also not help.

But I will try biosdevname=0, thats a good hint!

Best regards

Hans 

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

#262077

On 2023-10-01, Hans wrote:

>> If you don't remember partitioning you can install cygwin and use fdisk
>> on it. cygwin also provides blkid to get label and uuid.
>
> I tried to get the UUID in Windows but I am not sure, if GUID (Microsoft 
> naming?) is the same as UUID in Linux. 

Not directly from windows, Install cygwin on windows. You will have *nix
tools. From cygwin install and launch blkid. It will show you partitions
names and uuid.

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

#262064

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

On 2023-09-30 at 11: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.

Having read over the rest of this thread, so far I do not see anything
to indicate that 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.

Rather, I think that this is likely to be the entire problem.

At least on some (many?) systems, when this is set to RAID rather than
AHCI, a different driver is required. When that driver is not present or
is not compatible with the hardware, Linux will not see the storage
device.

That is the symptom which you are seeing, and because of that, I think
that this is the cause you need to deal with.

It is possible that the UUID of the storage device and/or the partitions
on it may have also changed, but until the storage device is accessible
from Linux again, the question of whether it has or not is irrelevant.

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

Please describe exactly what you have done to try to downgrade the UEFI
(which isn't a BIOS, as I understand the definitions of those terms, but
may sometimes be called one).

It's possible that there may be parameters which you could pass to the
tool you're using to try to do this, which would override the refusal to
downgrade.


If you can get the "AHCI" option back, then that is almost certainly
going to be the simplest way to fix the problem (or at least to move on
to the next stage of the problem, which would probably be more tractable).

If you can't, then the solution is likely to require getting a
compatible driver in the Linux environment (whether live or otherwise)
that you're using to try to access the system. The details of *that* are
not something that I have sufficient experience with to want to try to
advise someone on at a distance.

(If you're unlucky, there may not *be* any such driver for that model,
or at least not one you can get your hands on. In which case, barring
the downgrade-the-firmware angle, you'd probably be out of luck.)

-- 
   The Wanderer

The reasonable man adapts himself to the world; the unreasonable one
persists in trying to adapt the world to himself. Therefore all
progress depends on the unreasonable man.         -- George Bernard Shaw

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

#262069

Hi the Wanderer,
> Having read over the rest of this thread, so far I do not see anything
> to indicate that the UUID has changed.
Ok 
> 
> Rather, I think that this is likely to be the entire problem.
> 
> At least on some (many?) systems, when this is set to RAID rather than
> AHCI, a different driver is required. When that driver is not present or
> is not compatible with the hardware, Linux will not see the storage
> device.
> 
> That is the symptom which you are seeing, and because of that, I think
> that this is the cause you need to deal with.
> 
> It is possible that the UUID of the storage device and/or the partitions
> on it may have also changed, but until the storage device is accessible
> from Linux again, the question of whether it has or not is irrelevant.
> 
> > Second: The setting of AHCI has disappeared, so I can not change the
> > settings in BIOS. And: the BIOS can not be reflashed!
> 
> Please describe exactly what you have done to try to downgrade the UEFI
> (which isn't a BIOS, as I understand the definitions of those terms, but
> may sometimes be called one).

In short; I tried (as most people tell): Starting windows in secure mode, then 
boot into the BIOS and there set from RAID to AHCI, afterwards start windows 
as normal.

This setting in BIOS was existent some time ago, but now it is complete gone 
(this point is completele disappeared!)!!  I know that it is in RAID, because 
Windows told so: BUS form = RAID.


> 
> It's possible that there may be parameters which you could pass to the
> tool you're using to try to do this, which would override the refusal to
> downgrade.
> 
> 
> If you can get the "AHCI" option back, then that is almost certainly
> going to be the simplest way to fix the problem (or at least to move on
> to the next stage of the problem, which would probably be more tractable).
> 
> If you can't, then the solution is likely to require getting a
> compatible driver in the Linux environment (whether live or otherwise)
> that you're using to try to access the system. The details of *that* are
> not something that I have sufficient experience with to want to try to
> advise someone on at a distance.
> 

Yes. I am wondering, why the debian installer DVD does not see the nvme-
device. When I installed Debian_11 a year ago, it did see the drive. Of course 
I tried with this DVD again to reinstall, but today it does not see the drive 
any more (I suppose because of RAID).  

> (If you're unlucky, there may not *be* any such driver for that model,
> or at least not one you can get your hands on. In which case, barring
> the downgrade-the-firmware angle, you'd probably be out of luck.)

I guess I am unlucky..... :)

Thanks for the help.

best

Hans

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

#262075

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

On 2023-10-01 at 15:36, Hans wrote:

> Hi the Wanderer,

>>> Second: The setting of AHCI has disappeared, so I can not change
>>> the settings in BIOS. And: the BIOS can not be reflashed!
>> 
>> Please describe exactly what you have done to try to downgrade the
>> UEFI (which isn't a BIOS, as I understand the definitions of those
>> terms, but may sometimes be called one).
> 
> In short; I tried (as most people tell): Starting windows in secure
> mode, then boot into the BIOS and there set from RAID to AHCI,
> afterwards start windows as normal.
> 
> This setting in BIOS was existent some time ago, but now it is
> complete gone (this point is completele disappeared!)!!  I know that
> it is in RAID, because Windows told so: BUS form = RAID.

I apologize; it seems I was not sufficiently clear.

By "downgrade the UEFI" I meant "revert the installed UEFI to an older
version" - what you were attempting to do by "reflash"ing the "BIOS".

I was looking for a response like "double-clicked the EXE which I got
from [place] and followed the prompts, selecting [option] when given a
choice" or "ran the EXE which I got from [place] from the command line,
using [list of command-line parameters]".

If you did it via a graphical interface, and ran into a no-downgrade
wall, it may well be worth looking at the documentation which is
probably available along with the download; it may provide a
command-line version of the process, which might support parameters to
tell the tool to allow the downgrade to occur.

(Downgrading is suboptimal, but would be one way to address the
proximate issue.)

>> If you can get the "AHCI" option back, then that is almost
>> certainly going to be the simplest way to fix the problem (or at
>> least to move on to the next stage of the problem, which would
>> probably be more tractable).
>> 
>> If you can't, then the solution is likely to require getting a 
>> compatible driver in the Linux environment (whether live or
>> otherwise) that you're using to try to access the system. The
>> details of *that* are not something that I have sufficient
>> experience with to want to try to advise someone on at a distance.
> 
> Yes. I am wondering, why the debian installer DVD does not see the
> nvme- device. When I installed Debian_11 a year ago, it did see the
> drive. Of course I tried with this DVD again to reinstall, but today
> it does not see the drive any more (I suppose because of RAID).

My first suspicion would be that the installer environment does not
include - or, at least, is not loading - the necessary drivers for some
portion of the stack which is in use when the "RAID" option is enabled.

>> (If you're unlucky, there may not *be* any such driver for that
>> model, or at least not one you can get your hands on. In which
>> case, barring the downgrade-the-firmware angle, you'd probably be
>> out of luck.)
> 
> I guess I am unlucky..... :)

I don't think we've reached the stage of concluding that there is no
such Linux driver, at least not yet.

What steps have you taken to try to identify the device for which a
driver is needed?

A 'lspci' verbose report, from one of the live environments where the
NVMe device does not appear, might be helpful as a starting point in
doing that. I'd probably start with 'lspcn -nnn', and look in the output
for either anything which mentions "NVM" or "nvm", or any unidentified
devices.

> Thanks for the help.

You're quite welcome.

-- 
   The Wanderer

The reasonable man adapts himself to the world; the unreasonable one
persists in trying to adapt the world to himself. Therefore all
progress depends on the unreasonable man.         -- George Bernard Shaw

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

#262076

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

On 2023-10-01 at 17:39, The Wanderer wrote:

> On 2023-10-01 at 15:36, Hans wrote:
> 
>> Hi the Wanderer,

>>> (If you're unlucky, there may not *be* any such driver for that 
>>> model, or at least not one you can get your hands on. In which 
>>> case, barring the downgrade-the-firmware angle, you'd probably
>>> be out of luck.)
>> 
>> I guess I am unlucky..... :)
> 
> I don't think we've reached the stage of concluding that there is no 
> such Linux driver, at least not yet.
> 
> What steps have you taken to try to identify the device for which a 
> driver is needed?
> 
> A 'lspci' verbose report, from one of the live environments where
> the NVMe device does not appear, might be helpful as a starting point
> in doing that. I'd probably start with 'lspcn -nnn', and look in the
> output for either anything which mentions "NVM" or "nvm", or any
> unidentified devices.

Mrph. I of course meant 'lspci -nnn'.

-- 
   The Wanderer

The reasonable man adapts himself to the world; the unreasonable one
persists in trying to adapt the world to himself. Therefore all
progress depends on the unreasonable man.         -- George Bernard Shaw

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

#262083

Hi Hans!

hans.ullrich@loop.de wrote:
>
>In short; I tried (as most people tell): Starting windows in secure mode, then 
>boot into the BIOS and there set from RAID to AHCI, afterwards start windows 
>as normal.
>
>This setting in BIOS was existent some time ago, but now it is complete gone 
>(this point is completele disappeared!)!!  I know that it is in RAID, because 
>Windows told so: BUS form = RAID.

Right. I have one of these machines as a test box locally, and I think
I know what the problem is.

The core issue is that the BIOS setup screen has a ridiculous
mis-feature - it hides some BIOS entries from the user, with no
indication that it has done so. On the model I have, it needs you to
hit Ctrl-s on each of the BIOS setup screens to show them. I've read
about other models where you need to hit other key combinations. Doing
a web search for "<model> hidden bios settings" should help you here.

The "InsydeBIOS" thing is utter crap, basically. I'd *reallY* strongly
recommend getting rid of the machine and replacing it with something
less awful.

Be aware that if you switch storage from RAID to AHCI mode then you'll
probably lose access to the Windows installation - it will be
depending on the RAID setup.

-- 
Steve McIntyre, Cambridge, UK.                                steve@einval.com
Can't keep my eyes from the circling sky,
Tongue-tied & twisted, Just an earth-bound misfit, I...

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

#262102 — [SOLVED] Re: Debian will not boot any more, wrong UUID

Am Montag, 2. Oktober 2023, 10:42:42 CEST schrieb Steve McIntyre:
Hi Steve and all ones who helped me.

I had to search a solution for my problem and so I dind the following:

1. After I spoke to my customer, i installed Debian_12 to the second 
harddrive. And yes, it is a normal SSD and slower than the NVME-drive.

2. After it I accessed to the old partitions on the NVME under Windows. Here I 
am using Paragon drivers, to get access to the partitions. So I could rescue 
the old data and copied them to the new /home.

3. It appeared, that grub was now on the second drive and does NOT see windows 
any more. So I can not start Windows from the grub menu (os-prober in grub is 
activated, but does not see /dev/nvme and so not windows) The solution is, to 
boot via "F12" key which shows the BIOS option to choose, what to start. My 
customer agreed to this.

All in all, this solution is unsatisfied, but accepted by my friend (customer). 

Some important: During the installation, I discovered, that the BIOS was 
corrupted. The menu, where the boot line should be shown (1. Windows, 2. 
LinpusLite, 3. Debian) was completely crapped with random signs. 


Even "Load defaults" could not rescue it! More bad: I could not get into the 
BIOS any more with the F2-key. 

The trick: Using the grub menu and there the point: UEFI-settings I managed to 
get into the BIOS again, but the menu point was still no more existent. The 
screen was full with random signs.

After some reboots and removing from power, holding power button for 10 
seconds and some other things, this was suddenly ok again (luckyly!!!).

What shall I say? I suppose, the INSYDEH20 Bios is fully crap and should 
avoided in the future whenever possible.

Oh, and there is no way, to overwrite it, as the BIOS installer does only an 
upgrade, no overwrite. Yes, there is HOW20EZE, which you can edit the binaries 
and maybe give thme a highjer version. But you need specialo knowledge and it 
is dangerous and could brick your notebook completely. Thus I did not burn my 
fingers.

Ok, I found a solution, not for the problem, but for my friend. And I am sure, 
the cause of all these is the BIOS itself, Changed by Windows or changed by 
crap.

Again, thank you all for your help. I learnt again a lot (what is always 
important) and could see the reason.

This problem can be marked as solved. 

Best and happy hacking!

Hans 

> Hi Hans!
> 
> hans.ullrich@loop.de wrote:
> >In short; I tried (as most people tell): Starting windows in secure mode,
> >then boot into the BIOS and there set from RAID to AHCI, afterwards start
> >windows as normal.
> >
> >This setting in BIOS was existent some time ago, but now it is complete
> >gone (this point is completele disappeared!)!!  I know that it is in RAID,
> >because Windows told so: BUS form = RAID.
> 
> Right. I have one of these machines as a test box locally, and I think
> I know what the problem is.
> 
> The core issue is that the BIOS setup screen has a ridiculous
> mis-feature - it hides some BIOS entries from the user, with no
> indication that it has done so. On the model I have, it needs you to
> hit Ctrl-s on each of the BIOS setup screens to show them. I've read
> about other models where you need to hit other key combinations. Doing
> a web search for "<model> hidden bios settings" should help you here.
> 
> The "InsydeBIOS" thing is utter crap, basically. I'd *reallY* strongly
> recommend getting rid of the machine and replacing it with something
> less awful.
> 
> Be aware that if you switch storage from RAID to AHCI mode then you'll
> probably lose access to the Windows installation - it will be
> depending on the RAID setup.

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

#262072

Hans composed on 2023-09-30 17:34 (UTC+0200):
...
> On my notebook I have 2 drives, one is a NVME drive, the other a normal 
> harddrive....

What I would try to do in sequence if I had it here:

1-have Acer support explain why the AHCI option disappeared, and get it to restore
it with new BIOS or laptop if necessary. I wouldn't have high expectations that
this would succeed unless the OEM boot device with Windows remained as shipped for
delivery to support for analysis, but try at least. Usually best when buying a
brand new computer with Windows for use with Linux to not disturb the OEM drive
content before the warranty expires. IOW, store it elsewhere than in the computer.

2-remove both drives

3-clear/reset the UEFI BIOS so that no boot devices appear

4-reboot into BIOS do see if AHCI option has reappeared

5-try booting a live USB without any installed HDD or NVME

6-install one NVME or HDD that has been wiped or otherwise virgin

7-install Debian in UEFI mode
-- 
Evolution as taught in public schools is, like religion,
	based on faith, not based on science.

 Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!

Felix Miata

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

#262101

On 2023-09-30, Hans <hans.ullrich@loop.de> wrote:
>
> Second: The setting of AHCI has disappeared, so I can not change the settings 
> in BIOS. And: the BIOS can not be reflashed!
>

I've read that on some Acer machines the procedure is:

'Main' BIOS tab/ctrl+s (as suggested by Steve and Jeffrey)/toggle VMD
Controller to [Disabled].

-- 

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

#262103

Am Montag, 2. Oktober 2023, 17:03:57 CEST schrieb Curt:
> On 2023-09-30, Hans <hans.ullrich@loop.de> wrote:
> > Second: The setting of AHCI has disappeared, so I can not change the
> > settings in BIOS. And: the BIOS can not be reflashed!
> 
> I've read that on some Acer machines the procedure is:
> 
> 'Main' BIOS tab/ctrl+s (as suggested by Steve and Jeffrey)/toggle VMD
> Controller to [Disabled].

Hi Curt, 

tried both, but sadly no success. 

Thanks anyway!

Best regards

Hans

[toc] | [prev] | [standalone]

Page 2 of 2 — ← Prev page 1 [2]

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

csiph-web