Re: [Fwd: Re: Bug#495049: grub-pc: does not boot because module "normal" is not loaded]

[Bean]

On Fri, Aug 15, 2008 at 10:56 PM, Felix Zielcke <address@hidden> wrote:
> Hello Marco,
>
> Am Freitag, den 15.08.2008, 16:46 +0200 schrieb Marco Gerards:
>
>> Perhaps he simply clicked on "newest version" without bothering to
>> make sure?  I can image such things just happen...
>
> Right your not a Debian guy ;)
>
> -- Package-specific info:
> [...]
>
> Because of this I can be sure that he used the `reportbug' or maybe the
> `reportbug-ng' program/script
> I don't know anything about the -ng version except that's it's graphical
> instead of console.
>
> At least for `reportbug' I can say that it luckly get's the version
> number from `dpkg'.
> You don't need to find the version out yourself, or even have to choose
> from a list.
> But the whole things `reportbug' sends to the Debian BTS is shown in
> your favourite editor where you have to add your actual bug report
> before it get's send to bugs.debian.org
> I hope he's just not that intelligent to choose the right severity or
> make a correct bug report.
> Hopefully he wasn't that smart to change the version number `reportbug'
> put in the report.
>
> Maybe he installed an earlier version and used grub-install only on that
> i.e. real GRUB is outdated, but the report was made after the grub-pc
> package was updated to that version.
>
> I really hope that it's just his fault instead of that GRUB still has a
> bug which can lead to this fd0 problem :((

Hi,
On Fri, Aug 15, 2008 at 10:26 PM, Felix Zielcke <address@hidden> wrote:
> Am Donnerstag, den 14.08.2008, 18:40 +0200 schrieb Felix Zielcke:
>> Hello,
>>
>> anyone has an idea why grub itself fails to switch from rescue to normal
>> mode, but just `insmod normal; normal' does work?
>>
>> For me this doestn't make any sense at all.
>>
>> If you want to see the initial report:
>> http://bugs.debian.org/495049
>
> Now finally he said that GRUB fails to rescue mode with "unknown device
> fd0"
> At least I didn't need to ask for this.
> Maybe Robert has an idea about this and he sees the Debian bugreport
> anyway.
> With cross installing and so this fd0 problem was already topic on here
> and I even had it myself.
> But I haven't an idea about this anymore.
> I thought that this shouldn't happen anymore?
> And he reported against newest lenny version where this changes were
> included by Robert and me.

Hi,

Just like raid, lvm needs to scan all device. I think this is caused
when it try to open (fd0), and fails. The grub_errno is not cleared,
it's carried out and cause the rescue shell. I think we can improve
the test of (fd0) so that it won't appear in machine that don' t have
floppy, or reset grub_errno in lvm scan code when error occurs.

-- 
Bean