Hi Nathan,
that is a great idea. Unfortunately it does not work for me, at least not from
the rescue shell, as no size information is output:
grub rescue> ls
(hd0) (hd0,gpt2) (hd0,gpt1) (hd1) (hd1,gpt2) (hd1,gpt1) (lvm/vg0-root0)
(md/root0)
grub rescue> ls (hd0)
(hd0): Filesystem is unknown.
grub rescue> ls (hd0,gpt1)
(hd0,gpt1): Filesystem is unknown.
grub rescue> ls (hd0,gpt2)
(hd0,gpt2): Filesystem is unknown.
grub rescue> ls (lvm/vg0-root0)
(lvm/vg0-root0): Filesystem is ext2.
grub rescue> ls (md/root0)
(md/root0): Filesystem is unknown.
Regarding one of my earlier questions:
> 1) Is it expected that `nativedisk` takes effect automatically?
I have now found one place (https://bugzilla.redhat.com/show_bug.cgi?id=866559)
where somebody says:
> there is a downside on adding many modules to the core ELF: they are fully
> initialized in the grub's first stage
This seems to explain what I'm seeing with `nativedisk` taking effect
immediately without having to run the command, but I still cannot conclude that
from the GRUB2 docs so I'm not sure if it really does.
On the "which modules to I have to build in" question, follwoing Pascal's
suggestion to use `nativedisk`, I've tried various approaches so far, with the
longest being:
"--modules=pata part_gpt part_msdos diskfilter mdraid1x lvm ext2 nativedisk"
but still `ls` shows absolutely no disks as soon as `nativedisk` is in effect,
so I'm not sure what else to try.
Greetings and thanks,
Niklas
