Source: debian-installer
Version: 20250803+deb13u4
Severity: wishlist
I end up with unbootable trixie system which just gives me
GRUB loading...
Welcome to GRUB!
error: disk `mduuid/d34becde8dd18f589114b5532a391c87' not found.
grub rescue>
if I partition like this:
https://www.oneukrainian.com/tmp/trixie-btrfs-raid1.png . Per brief IRC chat,
such setup is not supported by grub ATM. Hence I think it would be great if
user was warned and insisted to create /boot partition.
Here is a log from IRC with a recommended workaround:
14:55 --- Channel #debian-boot was created on Thu Jun 28 20:40:19 2018
14:55 --- Channel #debian-boot was synced in 0 seconds
14:57 yoh: getting "error: disk `mduuid/d34becde8dd18f589114b5532a391c87'
not found." on fresh trixie install where I have sw-raid over 2 drives, and
then btrfs on top of it. And no dedicated /boot (best pattern to avoid
messing with multiple md/partitions etc).
14:58 yoh: here is how config looks like (I believe no EFI - just bios):
https://www.oneukrainian.com/tmp/trixie-btrfs-raid1.png
14:58 yoh: so the question is -- why it doesn't even find a raid?
14:59 yoh: 'ls' in grub gives: (hd0) (hd0,gpt2) (hd0,gpt1) (hd1)
(hd1,gpt2) (hd1,gpt1) (hd2)
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
15:28 Sledge: yoh: what size disks and partitions are you using?
15:28 Sledge: and booting in BIOS mode?
15:29 Sledge: in fact, that partition tells me everything
15:29 Sledge: you've partitioned using GPT and RAID
15:30 Sledge: grub can't read an 8T disk in BIOS mode, that's your problem
15:30 Sledge: in this situation you've done *exactly* the wrong thing
15:31 Sledge: to support big disks like that, you need a /boot filesystem
which lives entirely within the first 2T of each disk
15:32 Sledge: then grub will be able to read the rest of itself from
/boot, load and start the kernel from /boot and you're all good
15:49 yoh: Sledge: thank you Sledge. Ok, I will restart installer and
repartition to get leading /boot partition . I guess I could make it RAID1
too, correct? I wonder if d-i could add such safe-guards as "if /boot is on
a partition on GPT table and it is over 8T -- warning?"
15:49 Sledge: yes, a RAID1 /boot is what I'd recommend
15:50 Sledge: (it's what I do on all machines with more than 1 disk)
Cheers,
-- System Information:
Debian Release: forky/sid
APT prefers testing
APT policy: (900, 'testing'), (600, 'unstable'), (300, 'experimental'), (100,
'stable-updates'), (100, 'stable-security'), (100, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 6.19.8+deb14-amd64 (SMP w/20 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_USER, TAINT_OOT_MODULE,
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
