On Thu, Sep 12, 2024 at 01:21:12AM +0200, Florent Rougon wrote:
> Hi,
>
> Le 11/09/2024, Andy Smith a écrit:
>
> > Since booting from sdb wasn't working in any case, I thought I'd
> > experiment a bit. I copied the first 446 bytes of sda to sdb. This
> >
On Tuesday 10 September 2024 08:39:59 pm Andy Smith wrote:
> This does leave me wondering however, if the boot code in the mBR of
> sdb is now set to believe that this is "the second drive", I suppose
> (hd1) in grub terms? With the implication that should sda fail or be
>
Hi,
Le 11/09/2024, Andy Smith a écrit:
> Since booting from sdb wasn't working in any case, I thought I'd
> experiment a bit. I copied the first 446 bytes of sda to sdb. This
> made matters worse! Instead of a "grub> " prompt, I just got a blank
> screen.
&
Hi,
On Wed, Sep 11, 2024 at 12:45:46AM +0200, Florent Rougon wrote:
> The partition table indeed starts at offset 446 (decimal), however I'd
> still rather run grub-install or “dpkg-reconfigure grub-pc” than copy
> the first 446 bytes from one drive to another drive. The reason is
27;d
still rather run grub-install or “dpkg-reconfigure grub-pc” than copy
the first 446 bytes from one drive to another drive. The reason is that,
AFAIUI, what GRUB writes in this area when installed is likely to
contain disc-specific info. More specifically, according to [1]:
There isn't roo
primary partitions of each drive are among
> these bytes.
Good point. I understand the bootloader is actually the first 446
bytes so maybe I should only be looking at these.
https://unix.stackexchange.com/a/254668/36243
> I'd rather 'dpkg-reconfigure grub-pc' where you can
ach drive are among
these bytes.
> I do not particularly want to run grub-install, as the MBR of sdb is
> known good at the moment. Perhaps though I could run:
>
> $ sudo grub-install /dev/sda
I believe so, although by habit I'd rather 'dpkg-reconfigure grub-pc'
where you
On Mon, Sep 09, 2024 at 07:59:58PM +, Andy Smith wrote:
> I was kind of hoping that there would be something I could run which
> would say "yes, this MBR has grub v and is set to find its
> grub.cfg on (hdX)", then I might be able to see some difference in
> what the
Hi,
I've come into possession of a machine running Debian 10 with two
drives in it; sda and sdb. These have been labelled with a DOS MBR
and partitioned. The first partition starts at sector 2048 of both
drives (512 byte sectors). It appears that GRUB has been installed
on both sda an
Hi,
Andy Smith wrote:
> Is there some advantage in me editing one of the files in the EFI
> partition as opposed to just putting the grub serial directives in
> /boot/grub/grub.cfg of the ISO?
None that i know of.
Editing /efi/debian/grub.cfg of the EFI partition filesystem would ju
Hi,
On Mon, Jul 29, 2024 at 12:42:05PM +0200, Thomas Schmitt wrote:
> Andy Smith wrote:
> > Should I just edit that into $iso_root/boot/grub/grub.cfg and repack
> > the ISO?
>
> If altering the EFI partition is not viable, then surely: Yes.
Is there some advantage in me edi
Hi,
Andy Smith wrote:
> Currently when I add the Debian 12 netinst ISO as a virtual media it
> EFI boots grub, not isolinux,
That's because Debian ISOs advertise a EFI System Partition with GRUB
initial boot equipment:
$ xorriso -indev debian-12.2.0-amd64-
ement controller that adds virtual media from ISOs, but I would
still like to see that install over the IPMI serial.
Currently when I add the Debian 12 netinst ISO as a virtual media it
EFI boots grub, not isolinux, so the output of grub only goes to the
graphical terminal (a web interface of the manag
Le 28/05/2024, Harald Dunkel a écrit:
> Full thread is on debian-boot mailing list.
I've read it now, thanks for the info, Harald!
Regards
--
Florent
Full thread is on debian-boot mailing list.
Hi,
Le 24/05/2024, Harald Dunkel a écrit:
> if I migrate from grub-pc to grub-uefi, then grub-pc.postrm
> removes /etc/default/grub on the final purge.
I confirm the behavior, have been bitten by this. IMHO, it is a nasty
bug: suppose your rely on your kernel command line to disable, sa
Hi folks,
if I migrate from grub-pc to grub-uefi, then grub-pc.postrm
removes /etc/default/grub on the final purge.
grub2 doesn't provide much information in its man pages, but
AFAICT /etc/default/grub is still processed for UEFI, so why
is it deleted?
Regards
Harri
On 01/05/2024 10:45, Richard wrote:
I'd like to increase the font size in Grub (v2.12, at least I think
that's the better alternative to just lowering the resolution) and
opted to just use a custom font as there seems to be an OTF version of
"GNU Unifont", though it s
I'd like to increase the font size in Grub (v2.12, at least I think that's
the better alternative to just lowering the resolution) and opted to just
use a custom font as there seems to be an OTF version of "GNU Unifont",
though it seems to be jagged by design, but I'
the output of any of
> >>
> >> # blkid
> >
> > Here I have them shown as UUID by blkid
> >
> > # grep root /boot/grub/grub.cfg
> > ...
> > search --no-floppy --fs-uuid --set=root --hint-bios=hd1,gpt2
> > --hint-efi=hd1,gpt2 --hint-bareme
> On 13 Mar 2024, at 19:00, Gareth Evans wrote:
>
> Hi Michael,
I'm sorry - Michel
On Wed 13/03/2024 at 12:50, Michel Verdier wrote:
> On 2024-03-13, Gareth Evans wrote:
>
>> That suggests perhaps something to do with an FS UUID, but it doesn't seem
>> to appear in the output of any of
>>
>> # blkid
>
> Here I have them shown as
On 2024-03-13, Gareth Evans wrote:
> That suggests perhaps something to do with an FS UUID, but it doesn't seem to
> appear in the output of any of
>
> # blkid
Here I have them shown as UUID by blkid
# grep root /boot/grub/grub.cfg
...
search --no-floppy --fs-uuid --set=roo
Does anyone know what the 16-digit hex number (truncated below to 9cbe...)
refers to in /boot/grub/grub.cfg, where it makes several appearances?
# grep 9cbe -A2 -B2 /boot/grub/grub.cfg
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root
>On 19 Feb 2024 22:44 +0100, from borde...@tutanota.com (Borden):
>>> Would you be willing to post your /boot/grub/grub.cfg for a setup
>>> where you get the blank screen GRUB?
>>
>> Yeah, I probably should have opened with that. Sorry:
>>
>> ```
&
On Tue, 20 Feb 2024 08:04:47 +
Michael Kjörling <2695bd53d...@ewoof.net> wrote:
> On 19 Feb 2024 22:44 +0100, from borde...@tutanota.com (Borden):
> >> Would you be willing to post your /boot/grub/grub.cfg for a setup
> >> where you get the blank screen GRUB?
On 19 Feb 2024 22:44 +0100, from borde...@tutanota.com (Borden):
>> Would you be willing to post your /boot/grub/grub.cfg for a setup
>> where you get the blank screen GRUB?
>
> Yeah, I probably should have opened with that. Sorry:
>
> ```
> # If you change
> On 18 Feb 2024 21:28 +0100, from borde...@tutanota.com (Borden):
> > what the default is when neither of those are set (which doesn't
> > work). Is this another "undocumented feature" of GRUB?
>
> Would you be willing to post your /boot/grub/grub.cfg fo
On 18 Feb 2024 21:28 +0100, from borde...@tutanota.com (Borden):
> what the default is when neither of those are set (which doesn't
> work). Is this another "undocumented feature" of GRUB?
Would you be willing to post your /boot/grub/grub.cfg for a setup
where you get
rks and
GRUB_TERMINAL=console works, what the default is when neither of those are set
(which doesn't work). Is this another "undocumented feature" of GRUB?
On 2024-02-16, Borden wrote:
> For a couple weeks now, I can't use graphical terminal in my GRUB
> configuration. Setting `GRUB_TERMINAL=console` works fine. With that line
> commented out, (thus using default settings), I get a blank screen on boot, 5
> second timeout,
Thank you for the tip!
So `GRUB_TERMINAL=gfxterm` works, `GRUB_TERMINAL=console` works, but whatever
the default is supposed to be does not. Does this imply that "the platform's
native terminal output" is broken?
On 16/02/2024 17:27, Borden wrote:
For a couple weeks now, I can't use graphical terminal in my GRUB
configuration. Setting `GRUB_TERMINAL=console` works fine. With that line
commented out, (thus using default settings), I get a blank screen on boot, 5
second timeout, then normal
For a couple weeks now, I can't use graphical terminal in my GRUB
configuration. Setting `GRUB_TERMINAL=console` works fine. With that line
commented out, (thus using default settings), I get a blank screen on boot, 5
second timeout, then normal boot.
Curiously, keyboard commands work nor
On 2024-02-12 15:14, Greg Wooledge wrote:
According to
<https://unix.stackexchange.com/questions/745904/how-does-the-grub-pc-postinstall-script-know-which-device-to-install-to>
it uses debconf's database. That page includes instructions for viewing
the device and changing it.
ere on the drive.
>
> Maybe the grub-pc package takes its configuration from a different drive
> which is attached to the system ?
According to
<https://unix.stackexchange.com/questions/745904/how-does-the-grub-pc-postinstall-script-know-which-device-to-install-to>
it uses debconf&#
Hi,
John Boxall wrote:
> I am aware that the label and uuid (drive and partition) are replicated on
> the cloned drive, but I can't find the model number (in text format) stored
> anywhere on the drive.
Maybe the grub-pc package takes its configuration from a different drive
which
On 2024-02-12 09:34, Thomas Schmitt wrote:
The disk/by-id file names are made up from hardware properties.
I believe to see in the name at least: Manufacturer, Model, Serial Number.
So you will have to find the configuration file which knows that
/dev/disk/by-id address and change it either to
Hi,
John Boxall wrote:
> Setting up grub-pc (2.06-3~deb11u6) ...
> /dev/disk/by-id/ata-WDC_WDS100T2B0A-00SM50_21185R801540 does not
> exist, so cannot grub-install to it!
> What is confusing to me is that the error indicates the source SDD even
> though I have u
orking SDD.
apt-get -y upgrade --without-new-pkgs
Setting up grub-pc (2.06-3~deb11u6) ...
/dev/disk/by-id/ata-WDC_WDS100T2B0A-00SM50_21185R801540 does not
exist, so cannot grub-install to it!
You must correct your GRUB install devices before
On 05/02/2024 17:40, Dmitry wrote:
> It would not work with secure boot
Yes.
But secure boot is usually turned off. It is a standard advice during
Linux installation.
That advice may be standard for distributions that do not provide signed
shim and grub. Likely it is applicable for A
On Mon, 2024-02-05 at 17:40 +0700, Dmitry wrote:
>
> But secure boot is usually turned off. It is a standard advice during
> Linux
> installation.
>
Will probably be increasingly common though, I've got a Microsoft
Surface Laptop that works fine with Debian, but if you switch off
secure boot, it
> It would not work with secure boot
Yes.
But secure boot is usually turned off. It is a standard advice during Linux
installation.
/dev/sdb2: UUID="a8...b7" TYPE="crypto_LUKS" PARTUUID="8...5"
`strings /boot/efi/EFI/Manjaro/grub64x.efi` output:
cryptomount -u a8...b7
(cryptouuid/a8...b7)/boot/grub
I have a Manjaro installed, and what to migrate to Debian. That involves
exploration of Booting o
On 03/02/2024 22:32, Dmitry wrote:
2. sudo bash
sudo -i
3. cd /boot/efi/EFI/Mangaro
4. strings grubx64.efi
5. And at the output of strings there is UUID and /boot/grub.
I am unsure what UUID you mean.
Summary: GRUB installation not only involves configuration of text
files, but
also it
Tim Woodall composed on 2024-02-03 21:25 (UTC):
> Max Nikulin wrote:
>> It seems secure boot is disabled in your case, so I am wondering why you do
>> not boot xen.efi directly.
> Because the NVRAM is extremely tempremental.
Not in my experience. I recognized long ago that WRT non-removable m
On Sat, 3 Feb 2024, Max Nikulin wrote:
It seems secure boot is disabled in your case, so I am wondering why you do
not boot xen.efi directly.
Because the NVRAM is extremely tempremental. Most updates fail, or
worse, corrupt it to the point it's hard to get anything to boot.
Additionally, the
Hi,
On Fri, Feb 02, 2024 at 02:41:38PM +0100, Franco Martelli wrote:
> There is an alternative to hardware RAID if you want a Linux RAID: you can
> disable UEFI in the BIOS and delete the ESP as I did when I bought my gaming
> PC several years ago.
I have storage devices which legacy BIOS cannot
Main question is resolved.
GRUB knows how to reach grub.cfg because grubx64.efi binary has the UUID and
path to grub configurations.
1. sudo blkid;
2. sudo bash
3. cd /boot/efi/EFI/Mangaro
4. strings grubx64.efi
5. And at the output of strings there is UUID and /boot/grub.
Summary: GRUB
On 03/02/2024 02:15, Tim Woodall wrote:
$ cat /boot/efi/EFI/XEN/xen.cfg
[...]
I'd be interested if there's a way to tell grubx64.efi to look for a
particular partition UUID.
An example of such grub.cfg from EFI/debian has been posted already in
this thread
https://lists.debian.org/msgid-sea
On 03/02/2024 02:51, Thomas Schmitt wrote:
Max Nikulin wrote:
Just copy files from LiveCD (it should have EFI/Boot/bootx64.efi)
to the ESP partition on the USB stick.
The /EFI/boot directory of a bootable Debian ISO usually does not contain
the full GRUB equipment for EFI. Important parts of
On 02/02/24 at 15:12, Dmitry wrote:
Going to read carefully.
https://www.debian.org/releases/buster/amd64/ch04s03.en.html
Interesting that Buster has more documentation than current release.
Nope, maybe you gave a quick read, the release notes of the current
release ¹ are exhaustive. If y
>...> I need to prepare that system for booting.
>...> 1. Install Kernel.
>...> 2. Install GRUB and Configure.
>...> 3. Add changes to UEFI to start booting.
dd-ing a bootable Debian ISO will not do what you describe.
Assumed the ISO is prepared for booting from USB s
On Thu, 1 Feb 2024, Marco Moock wrote:
Am 01.02.2024 um 19:20:01 Uhr schrieb Tim Woodall:
$ cat /boot/efi/EFI/XEN/xen.cfg
[global]
default=debian
[debian]
options=console=vga smt=true
kernel=vmlinuz root=/dev/mapper/vg--dirac-root ro quiet
ramdisk=initrd.img
menuentry "Xen EFI NVME" {
On Fri, 2024-02-02 at 14:41 +0100, Franco Martelli wrote:
> On 31/01/24 at 22:51, hw wrote:
> > > [...]
> > > If your suggested solution is "use hardware RAID", no need to repeat
> > > that one though: I see you said it in a few other messages, and that
> > > suggestions has been received. Assume t
On Sat, Feb 03, 2024 at 01:17:05AM +0700, Dmitry wrote:
> > Just copy files from LiveCD (it should have EFI/Boot/bootx64.efi) to the
> ESP partition on the USB stick.
>
> As I understand right now `dd` command applied to a device will copy all
> information including partitions table. Thus:
Actua
> Just copy files from LiveCD (it should have EFI/Boot/bootx64.efi) to the
ESP partition on the USB stick.
Yep. `dd` copy partitions table. Amazing.
```
dd will simply recreate the old partition scheme, as it is a bitwise copy &
applies no 'intelligence' to the operation.
```
https://askubunt
> Just copy files from LiveCD (it should have EFI/Boot/bootx64.efi) to the
ESP partition on the USB stick.
As I understand right now `dd` command applied to a device will copy all
information including partitions table. Thus:
dd if=debian-xx.iso of=/dev/sdb bs=4M status=progress; sync
Would
On Fri 02 Feb 2024 at 21:12:30 (+0700), Dmitry wrote:
> Going to read carefully.
>
> https://www.debian.org/releases/buster/amd64/ch04s03.en.html
>
> Interesting that Buster has more documentation than current release.
It appears the balance has now been spun off into a wiki page, at
https://
On 02/02/2024 21:06, Dmitry wrote:
Need additional research what to do with a FlashStick with several
partitions to make a LiveCD from it.
Just copy files from LiveCD (it should have EFI/Boot/bootx64.efi) to the
ESP partition on the USB stick.
Going to read carefully.
https://www.debian.org/releases/buster/amd64/ch04s03.en.html
Interesting that Buster has more documentation than current release.
> Do you want to install the OS on it?
Eventually no, I do not want OS on the Flash Stick.
The Flash Stick is only a testing place. I want OS at the SSD.
Now I am wondering how to prepare the Flash Stick to write LiveImage on it.
Because I already created a GPT table on that Flash and use deboo
Am 02.02.2024 schrieb Dmitry :
> I want OS at the SSD.
Then the ESP should be on that SSD too.
On 31/01/24 at 22:51, hw wrote:
[...]
If your suggested solution is "use hardware RAID", no need to repeat
that one though: I see you said it in a few other messages, and that
suggestions has been received. Assume the conversation continues
amongst people who don't like that suggestion.
Well,
Max Nikulin schrieb:
On a *removable* drive EFI/Boot/bootx64.efi (that is actually
/usr/lib/shim/shimx64.efi.signed that loads grubx64.efi) may allow to
boot without modification of boot entries in NVRAM.
Yes, UEFI can (and must be able) to boot from a device without a boot
entry in the UEFI. O
On Wed, 2024-01-31 at 23:28 +0100, Nicolas George wrote:
> hw (12024-01-31):
> > Well, I doubt it.
>
> Well, doubt it all you want. In the meantime, we will continue to use
> it.
>
> Did not read the rest, not interested in red herring nightmare
> scenarios.
>
You'll figure it out eventually.
On 01/02/2024 05:45, hw wrote:
It would make sense that all the UEFI BIOSs would be fixed so that
they do not create this problem in the first place like they
shouldn't.
Besides regular boots, sometimes it is necessary to update firmware and
.efi files loaded for this purpose may write logs or
On 02/02/2024 01:46, Dmitry wrote:
3. Now I want to boot using that Flash.
1. ESP is a partition that stores GRUB Binary. /boot/EFI/Name/grub64.eif
On a *removable* drive EFI/Boot/bootx64.efi (that is actually
/usr/lib/shim/shimx64.efi.signed that loads grubx64.efi) may allow to
boot
Am 01.02.2024 um 19:20:01 Uhr schrieb Tim Woodall:
> $ cat /boot/efi/EFI/XEN/xen.cfg
> [global]
> default=debian
>
> [debian]
> options=console=vga smt=true
> kernel=vmlinuz root=/dev/mapper/vg--dirac-root ro quiet
> ramdisk=initrd.img
>
>
> menuentry "Xen EFI NVME" {
> insmod part_gpt
>
On Thu, 1 Feb 2024, Marco Moock wrote:
Am 02.02.2024 um 01:46:06 Uhr schrieb Dmitry:
2. ==>BAM<== some how that binary knows the system partition.
That information is on the EFI partition, where the GRUB bootloader
binary also resides.
root@ryz:/boot/efi/EFI# cat /boot/efi/EFI/
On Fri, 2 Feb 2024, Dmitry wrote:
Hi Tim. The community is so kind.
So.
I'm not exactly sure what you're doing.
Understand how GRUB works, to boot myself.
1. Trying to install Debian on the Flash.
2. Use it by the Debootstrap.
3. Now I want to boot using that Flash.
Looks lik
Am 02.02.2024 um 01:46:06 Uhr schrieb Dmitry:
> 2. ==>BAM<== some how that binary knows the system partition.
That information is on the EFI partition, where the GRUB bootloader
binary also resides.
root@ryz:/boot/efi/EFI# cat /boot/efi/EFI/debian/grub.cfg
search.fs_uuid 5b8b669d-xyz
Hi Tim. The community is so kind.
So.
> I'm not exactly sure what you're doing.
Understand how GRUB works, to boot myself.
1. Trying to install Debian on the Flash.
2. Use it by the Debootstrap.
3. Now I want to boot using that Flash.
Looks like a caught the thread.
1. ESP i
you want an encrypted system?
> > Do you need a special configuration here or is the default just
> > fine?
>
> Need just working one. But I am confusing about how GRUB would get a
> plenty of things related to filesystem, kernel location and so on.
That is being done
Huge thanks.
Your message starts the understanding.
And as well give a plenty of texts to read.
> EFI/debian/grub.cfg on the EFI System Partition contains filesystem UUID
where grub files reside.
All parts are simple But when compounding them together become messy.
In the Manjaro:
/boot/
On Thu, 1 Feb 2024, Dmitry wrote:
Greetings!
After:
1. Creating GPT table and GPT partition with fdisk.
2. Copy data with a debootstrap.
3. Chroot into newly creating system.
I need to prepare that system for booting.
1. Install Kernel.
2. Install GRUB and Configure.
3. Add changes to UEFI to
ration here or is the default just fine?
Need just working one. But I am confusing about how GRUB would get a
plenty of things related to filesystem, kernel location and so on.
> If you create a separate boot partition (do you really need it?), it
must be mounted at /boot.
Here where the mess st
also
https://www.rodsbooks.com/gdisk/advice.html#esp_sizing
https://fedoraproject.org/wiki/Changes/BiggerESP
2. Need to configure GRUB to select appropriate kernel and ramdisk.
Do you need a special configuration here or is the default just fine?
EFI/debian/grub.cfg on the EFI System Partitio
the point two (Install GRUB) I a little bit confused.
>
> 1. Need to create ESP
Do that before the install with gdisk.
> and put GRUB there.
That is done automatically if it is mounted at /boot/efi.
> 2. Need to configure GRUB to select appropriate kernel and ramdisk.
Do you need a
Greetings!
After:
1. Creating GPT table and GPT partition with fdisk.
2. Copy data with a debootstrap.
3. Chroot into newly creating system.
I need to prepare that system for booting.
1. Install Kernel.
2. Install GRUB and Configure.
3. Add changes to UEFI to start booting.
And at the point
On Wed, 2024-01-31 at 06:33 +0100, to...@tuxteam.de wrote:
> On Tue, Jan 30, 2024 at 09:47:35PM +0100, hw wrote:
> > On Mon, 2024-01-29 at 18:41 +0100, to...@tuxteam.de wrote:
> > > On Mon, Jan 29, 2024 at 05:52:38PM +0100, hw wrote:
> > >
> > > [...]
> > >
> > > > Ok in that case, hardware RAID
hw (12024-01-31):
> Well, I doubt it.
Well, doubt it all you want. In the meantime, we will continue to use
it.
Did not read the rest, not interested in red herring nightmare
scenarios.
--
Nicolas George
On Tue, 2024-01-30 at 21:35 +0100, Nicolas George wrote:
> hw (12024-01-30):
> > Yes, and how much effort and how reliable is doing that?
>
> Very little effort and probably more reliable than hardware RAID with
> closed-source hardware.
Well, I doubt it. After all you need to copy a whole parti
On Wed, 2024-01-31 at 15:16 +, Andy Smith wrote:
> Hi,
>
> On Tue, Jan 30, 2024 at 09:50:23PM +0100, hw wrote:
> > On Mon, 2024-01-29 at 23:53 +, Andy Smith wrote:
> > > I think you should read it again until you find the part where it
> > > clearly states what the problem is with using MD
Hi,
On Tue, Jan 30, 2024 at 09:50:23PM +0100, hw wrote:
> On Mon, 2024-01-29 at 23:53 +, Andy Smith wrote:
> > I think you should read it again until you find the part where it
> > clearly states what the problem is with using MD RAID for this. If
> > you still can't find that part, there is l
On Wed, Jan 31, 2024 at 05:29:56AM -, David Chmelik wrote:
> Earlier this or last year I tried to use Devuan to report os-prober
> detects in wrong order. It may detect current OS partition first, but if
> you have more than 10, then it continues from 10, and (if this is all you
> have) goe
On Tue, Jan 30, 2024 at 09:47:35PM +0100, hw wrote:
> On Mon, 2024-01-29 at 18:41 +0100, to...@tuxteam.de wrote:
> > On Mon, Jan 29, 2024 at 05:52:38PM +0100, hw wrote:
> >
> > [...]
> >
> > > Ok in that case, hardware RAID is a requirement for machines with UEFI
> > > BIOS since otherwise their
Earlier this or last year I tried to use Devuan to report os-prober
detects in wrong order. It may detect current OS partition first, but if
you have more than 10, then it continues from 10, and (if this is all you
have) goes to the last in the tens but then continues somewhere in single-
digit
On Mon, 2024-01-29 at 23:53 +, Andy Smith wrote:
> Hi,
>
> On Mon, Jan 29, 2024 at 05:28:56PM +0100, hw wrote:
> > On Sun, 2024-01-28 at 21:55 +, Andy Smith wrote:
> > > On Sun, Jan 28, 2024 at 09:09:17PM +0100, hw wrote:
> > > > On Sun, 2024-01-28 at 17:32 +, Andy Smith wrote:
> > > >
On Mon, 2024-01-29 at 18:41 +0100, to...@tuxteam.de wrote:
> On Mon, Jan 29, 2024 at 05:52:38PM +0100, hw wrote:
>
> [...]
>
> > Ok in that case, hardware RAID is a requirement for machines with UEFI
> > BIOS since otherwise their reliability is insufficient.
>
> The price you pay for hardware R
hw (12024-01-30):
> Yes, and how much effort and how reliable is doing that?
Very little effort and probably more reliable than hardware RAID with
closed-source hardware.
--
Nicolas George
On Mon, 2024-01-29 at 18:00 +0100, Nicolas George wrote:
> hw (12024-01-29):
> > Ok in that case, hardware RAID is a requirement for machines with UEFI
>
> That is not true, you can still put the RAID in a partition and keep the
> boot partitions in sync manually or with scripts.
Yes, and how muc
Hi,
On Mon, Jan 29, 2024 at 05:28:56PM +0100, hw wrote:
> On Sun, 2024-01-28 at 21:55 +, Andy Smith wrote:
> > On Sun, Jan 28, 2024 at 09:09:17PM +0100, hw wrote:
> > > On Sun, 2024-01-28 at 17:32 +, Andy Smith wrote:
> > > > If someone DOES want a script option that solves that problem, a
On Mon, Jan 29, 2024 at 05:52:38PM +0100, hw wrote:
[...]
> Ok in that case, hardware RAID is a requirement for machines with UEFI
> BIOS since otherwise their reliability is insufficient.
The price you pay for hardware RAID is that you need a compatible controller
if you take your disks elsewhe
hw (12024-01-29):
> Ok in that case, hardware RAID is a requirement for machines with UEFI
That is not true, you can still put the RAID in a partition and keep the
boot partitions in sync manually or with scripts.
--
Nicolas George
On Mon, 2024-01-29 at 14:45 +0100, Franco Martelli wrote:
> On 28/01/24 at 17:17, hw wrote:
> > On Fri, 2024-01-26 at 16:57 +0100, Nicolas George wrote:
> > > hw (12024-01-26):
> > > > How do you make the BIOS read the EFI partition when it's on mdadm
> > > > RAID?
> > >
> > > I have not yet teste
On Sun, 2024-01-28 at 21:55 +, Andy Smith wrote:
> Hello,
>
> On Sun, Jan 28, 2024 at 09:09:17PM +0100, hw wrote:
> > On Sun, 2024-01-28 at 17:32 +, Andy Smith wrote:
> > > If someone DOES want a script option that solves that problem, a
> > > couple of actual working scripts were supplied
On 28/01/24 at 17:17, hw wrote:
On Fri, 2024-01-26 at 16:57 +0100, Nicolas George wrote:
hw (12024-01-26):
How do you make the BIOS read the EFI partition when it's on mdadm
RAID?
I have not yet tested but my working hypothesis is that the firmware
will just ignore the RAID and read the EFI p
Hello,
On Sun, Jan 28, 2024 at 09:09:17PM +0100, hw wrote:
> On Sun, 2024-01-28 at 17:32 +, Andy Smith wrote:
> > If someone DOES want a script option that solves that problem, a
> > couple of actual working scripts were supplied in the link I gave to
> > the earlier thread:
> >
> > https
Hello,
On Sun, Jan 28, 2024 at 09:03:50PM +0100, hw wrote:
> Show me any installer for Linux distributions that handles this
> sufficently without further ado.
That was the question I posed several posts back: what do people do
for redundant ESP.
> When you don't use btrfs, you have either hardw
1 - 100 of 1500 matches
Mail list logo
