Comment 11 for bug 477169

2009/11/9 Agostino Russo <email address hidden>:
> Gergely, I am well aware that grub has a built in shell you can always
> use, but what is relevant is what shell you end up into once you have
> your error.

Since it is a kernel panic, there is no shell at all....
As much as I can see the log (the screen does not scroll), it finds
the relevant partitions, and gives the above message, blinks the
scroll-lock and caps-lock lights on the keyboard indefinitely, and
nothing more.... Next: hard reboot.

> If after the error you end up in a grub shell it means it is a grub
> issue. If you end up in a busybox shell it means it is a
> filesystem/initrd issue. Because the error you mentioned is about a
> kernel panic, I would expect a filesystem/initrd issue.

It is not in a grub shell and not in busybox either. Running the boot
scripts then kernel panic. Nothing interactive about it.

> If so, you should be able to reproduce the error within the LINUX
> busybox shell, by issuing the same commands that made the initrd fail
> (basically try to mount the ntfs partition).

The problem is that no partitions are mounted, or I'm misunderstanding
the above error message?
If it would mount the ntfs volume, then it can do the loop device,
then it can do the whole process. But it kernel panics, because it
cannot mount, because it does not try ntfs, just: ext2, ext3, ext4,
fuseblk.....

> Those commands happen to be
> similar to the ones you mentioned for the grub shell, but they are
> actually performed by the Linux kernel within a Linux environments, as
> opposed to being performed by grub.

Not sure what you mean, because I don't even get a workable system to
start with.... Hard frozen every time.