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


Groups > linux.debian.user > #262102

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

From Hans <hans.ullrich@loop.de>
Newsgroups linux.debian.user
Subject [SOLVED] Re: Debian will not boot any more, wrong UUID
Date 2023-10-02 17:20 +0200
Message-ID <HksSd-d3NG-1@gated-at.bofh.it> (permalink)
References <HksSd-d3NG-3@gated-at.bofh.it> <HjKet-cBwE-1@gated-at.bofh.it> <Hk9FT-cR6q-7@gated-at.bofh.it> <HkmMN-cZUv-11@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw


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.

Back to linux.debian.user | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread


Thread

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

csiph-web