Bug#502333: grub-pc: Search uuid in LVM crashes the bootloader
rmh at aybabtu.com
Thu Jan 22 15:17:21 UTC 2009
On Thu, Jan 22, 2009 at 02:35:55PM +0100, Harald Braumann wrote:
> > There are two search lines in your grub.cfg, and the logs you provided
> > make it clear which of them is causing the problem.
> > grubdbg-1.96%2B20080724-10.log refers to 249d254f-9ee3-4908-aec6-177
> > is neither of them, and grubdbg-1.96%2B20081201-1.log only has scrambled
> > output.
> I entered the search command manually. Could be that I mistyped something.
No. It's a different one than what is in your grub.cfg. Perhaps you
regenerated the filesystem, I don't know. But you didn't tell us which
one. There are _two_ of them.
> > Actually, it'd be good to know if the problem appears at all in grub-emu
> > not, too.
> I would expect it to. My guess is, that grub finds the journal volume,
> its ext2 (which it kind of is) and expects to find some things, which are
> not there
> because it's not ext2, after all.
Sounds plausible. If you can reproduce it in grub-emu, it'll be much simpler.
Then you will probably get a SIGSEV instead of a reboot.
The DRM opt-in fallacy: "Your data belongs to us. We will decide when (and
how) you may access your data; but nobody's threatening your freedom: we
still allow you to remove your data and not access it at all."
More information about the Pkg-grub-devel