On 07.01.24 20:33, songbird wrote:
i see you've solved your issue, but i just wanted to
point out that it works and is ok for people who want to
try it out.
Says who?
Richard Rosner wrote:
> So, since for whatever reason Grub seems to be broken beyond repair, I
> today tried to just replace it with rEFInd. Installation succeeded
> without any trouble. But when I start my system, rEFInd just asks me if
> I want to boot with fwupd or with the still very broken
On 04.01.24 19:49, Richard Rosner wrote:
On 04.01.24 19:02, David Wright wrote:
Could you post the new grub.cfg file, so that people running testing,
and following along the thread later, can see how boot-repair fixed it?
Cheers,
David.
Let's hope the mailing list let's this go through.
It
On 07.01.24 18:07, David Wright wrote:
I compared your new grub.cfg with mine (suitably decimated and edited)
and the significant differences are very few; extra modules are loaded:
cryptodisk, luks2, gcry_rijndael, gcry_rijndael and gcry_sha256.
Myset root='hd0,gpt5' is replaced by
set
On Thu 04 Jan 2024 at 19:49:43 (+0100), Richard Rosner wrote:
> On 04.01.24 19:02, David Wright wrote:
> > Could you post the new grub.cfg file, so that people running testing,
> > and following along the thread later, can see how boot-repair fixed it?
>
> Keep in mind, this is based on the
On Thu, Jan 4, 2024 at 6:18 PM Joel Roth wrote:
>
> On Thu, Jan 04, 2024 at 06:19:01PM +0100, Richard Rosner wrote:
> > In theory, it should
> > be as simple as refind-install. So the only reason I could guess to be the
> > reason would be that rEFInd might not be capable of handling LUKS, which
On 04.01.24 19:02, David Wright wrote:
Could you post the new grub.cfg file, so that people running testing,
and following along the thread later, can see how boot-repair fixed it?
Cheers,
David.
Let's hope the mailing list let's this go through.
Keep in mind, this is based on the
On Wed 03 Jan 2024 at 22:00:20 (+0100), Richard Rosner wrote:
> On 03.01.24 21:04, Eddie wrote:
> > On 1/3/24 14:23, Richard Rosner wrote:
> > > So, since for whatever reason Grub seems to be broken beyond
> > > repair, I today tried to just replace it with rEFInd.
> > > Installation succeeded
On Thu, Jan 04, 2024 at 06:19:01PM +0100, Richard Rosner wrote:
> In theory, it should
> be as simple as refind-install. So the only reason I could guess to be the
> reason would be that rEFInd might not be capable of handling LUKS, which
> would be quite disappointing.
My experiences are with
Well, that was a bust. I accidentally didn't just format the EFI
partition, but deleted it. So I re-created it with the help of disks and
gparted (to leave the first 3 MB empty, I remeber that being a fix added
kinda recently to combat bad BIOS/EFI implementations, since Windows is
doing the
You should really re-read the FAQ that was sent in just two days ago...
On January 4, 2024 11:58:28 AM GMT+01:00, Jeffrey Walton
wrote:
>On Thu, Jan 4, 2024 at 2:45 AM Richard Rosner wrote:
>>
>> Wow, what a bunch of unhelpful comments.
>>
>> First, if it wasn't for Eddie recommending
On Thu, Jan 4, 2024 at 2:45 AM Richard Rosner wrote:
>
> Wow, what a bunch of unhelpful comments.
>
> First, if it wasn't for Eddie recommending boot-repair, "broken beyond
> repair" in fact was the very fitting term.
Here was Eddie's comment" I have had very good results using
"Boot-Repair"
Good to know that it should be possible. But as mentioned, these symbols
only offer me to boot from grub or fwupd. F2 also doesn't show that much
more, it merely gives me the option to boot into the BIOS settings. Maybe
I'll have to completely purge all Grub packages, wipe the existing EFI
On 1/4/24 02:45, Richard Rosner wrote:
Wow, what a bunch of unhelpful comments.
First, if it wasn't for Eddie recommending boot-repair, "broken beyond
repair" in fact was the very fitting term.
Second, have you maybe considered that I've already read the home page
of rEFInd and came to the
On Wed, Jan 03, 2024 at 08:23:29PM +0100, Richard Rosner wrote:
> So, since for whatever reason Grub seems to be broken beyond repair, I today
> tried to just replace it with rEFInd. Installation succeeded without any
> trouble. But when I start my system, rEFInd just asks me if I want to boot
>
I have kept the referral to the old problem in the topic for a reason. Been
there, done that. I'm not entirely sure how, but boot-repair was the only
thing that was able to fix Grub. Before that I've reinstalled it countless
times, thanks.
But since this is very much not an answer to the question
Wow, what a bunch of unhelpful comments.
First, if it wasn't for Eddie recommending boot-repair, "broken beyond
repair" in fact was the very fitting term.
Second, have you maybe considered that I've already read the home page of
rEFInd and came to the same conclusion? Besides the fact that the
On Wed, Jan 3, 2024 at 2:24 PM Richard Rosner
wrote:
> So, since for whatever reason Grub seems to be broken beyond repair,
>
I am not sure what you mean by "broken beyond repair." I have no issues
with Grub on Debian 12 on AMD64. I had no issues with Grub on Debian 11 or
Debian 10 on AMD64
On Wed, Jan 3, 2024 at 2:24 PM Richard Rosner wrote:
>
> So, since for whatever reason Grub seems to be broken beyond repair,
I seriously doubt this is the case. I'm guessing the problem lies elsewhere.
> I today tried to just replace it with rEFInd. Installation succeeded without
> any
Thanks, this actually did the job. I don't know what it was, but my
guess is it was the step "purge Grub before reinstalling it".
PS: rewrote to the old subject, as this is clearly an answer to the
original problem, as it doesn't have anything to do with replacing Grub
all together.
On
I have had very good results using "Boot-Repair" software to recover
Grub difficulties.
Eddie
On 1/3/24 14:23, Richard Rosner wrote:
So, since for whatever reason Grub seems to be broken beyond repair, I
today tried to just replace it with rEFInd. Installation succeeded
without any trouble.
So, since for whatever reason Grub seems to be broken beyond repair, I
today tried to just replace it with rEFInd. Installation succeeded
without any trouble. But when I start my system, rEFInd just asks me if
I want to boot with fwupd or with the still very broken Grub. Am I
missing
On 01.01.24 21:20, Richard Rosner wrote:
On 01.01.24 20:30, David Wright wrote:
On Mon 01 Jan 2024 at 19:04:20 (+0100), Richard Rosner wrote:
On 01.01.24 18:13, David Wright wrote:
I can boot by hand, but since this is all archived anyways and it's
uneccessarily difficult to find some sort
On 01.01.24 20:30, David Wright wrote:
On Mon 01 Jan 2024 at 19:04:20 (+0100), Richard Rosner wrote:
On 01.01.24 18:13, David Wright wrote:
I can boot by hand, but since this is all archived anyways and it's
uneccessarily difficult to find some sort of guide how to even do
this, it might as
On Mon 01 Jan 2024 at 19:04:20 (+0100), Richard Rosner wrote:
> On 01.01.24 18:13, David Wright wrote:
> > On Mon 01 Jan 2024 at 17:55:29 (+0100), Richard Rosner wrote:
> > > On January 1, 2024 5:43:12 PM GMT+01:00, David Wright wrote:
> > >
> > > > Like this?
> > > >
> > > > └─sda6
I can boot by hand, but since this is all archived anyways and it's
uneccessarily difficult to find some sort of guide how to even do this,
it might as well be a documentation for users having such troubles in
the future.
Also, besides the way that I have no clue how it would have to look
On Mon 01 Jan 2024 at 17:55:29 (+0100), Richard Rosner wrote:
> On January 1, 2024 5:43:12 PM GMT+01:00, David Wright
> wrote:
>
> >Like this?
> >
> > └─sda6 8:60 406.2G 0 part
> >└─luks-f3fbb9ba-a556-406c-b276-555e3e8577bc 254:10 406.2G
Yes, exactly. Is there a way to show that from inside Grub? Lsblk and blkid
aren't available there?
On January 1, 2024 5:43:12 PM GMT+01:00, David Wright
wrote:
>Like this?
>
> └─sda6 8:60 406.2G 0 part
>
On Mon 01 Jan 2024 at 17:37:44 (+0100), Richard Rosner wrote:
> So, I found a way to manually mount luks partition in Grub and boot from it.
>
> What I did to get there:
> set root=(hd0,gpt2)
> cryptomount -a
>
> This gave me the unencrypted version of the root partition as (crypto1)
>
> set
So, I found a way to manually mount luks partition in Grub and boot from it.
What I did to get there:
set root=(hd0,gpt2)
cryptomount -a
This gave me the unencrypted version of the root partition as (crypto1)
set root=(crypto1)
linux /vmlinuz root=/dev/mapper/luks-UUID
initrd /initrd.img
boot
I do not see an answer to my questions.
> On Jan 1, 2024, at 11:52, Michael Kjörling <2695bd53d...@ewoof.net> wrote:
>
> On 1 Jan 2024 11:46 +0100, from rich...@rosner-online.de (Richard Rosner):
>> I'm not sure what you meant with "rescue mode", but I've reinstalled
>> grub anyways. The log of
On 1 Jan 2024 11:46 +0100, from rich...@rosner-online.de (Richard Rosner):
> I'm not sure what you meant with "rescue mode", but I've reinstalled
> grub anyways. The log of it doesn't look good though. Quite a bunch
> of errors. The result also is the same.
Please review the posts in the thread
I'm not sure what you meant with "rescue mode", but I've reinstalled grub
anyways. The log of it doesn't look good though. Quite a bunch of errors. The
result also is the same.
https://pastes.io/nvmlsxghlm
> On Jan 1, 2024, at 11:03, Michael Kjörling <2695bd53d...@ewoof.net> wrote:
>
> On 1
On 29 Dec 2023 23:29 +0100, from rich...@rosner-online.de (Richard Rosner):
> For a fraction of a second it shows something about slot 0 open, that's it.
Well, that means that GRUB at least succeeds in opening the LUKS
container. That's good; it means that we can rule out that part of the
chain
As far as I can tell, /boot and /boot/grub are the same filesystem. After all,
I didn't really do anything custom. Just your default LUKS installation with
the boot efi stuff on sda1/sdb1/whatever, LUKS on 2 and LUKS encrypted swap on
3.
I did make a video. Nothing that's not showing up
On 29 Dec 2023 18:56 +0100, from rich...@rosner-online.de (Richard Rosner):
> Hey, I have quite the strange issue. After updating a bunch of
> packages today [1], mostly related to systemd, gstreamer and udev,
> and restarting my device, it no longer boots. I have an encrypted
> system. So I do
Hey, I have quite the strange issue. After updating a bunch of packages today
[1], mostly related to systemd, gstreamer and udev, and restarting my device,
it no longer boots. I have an encrypted system. So I do get asked for my
decryption password as usual, but a few seconds later, instead of
37 matches
Mail list logo
