Noam Rathaus wrote:
Hi,
We encountered a grub weirdness and I can't find any reference to this issue
on the Internet.
Recipe:
1) Install debian via debian-installer (testing version)
2) Get a "standard desktop" running
3) Download a tar.gz of another debian-installer based system
4) Boot into a network-based rescue disk
5) untar the tar.gz into the system
6) Reboot
From this point the grub boots and shows the prompt, Internet sites suggest
that the /boot/grub/ directory is malformed, or missing, or doesn't have the
configuration files - this is not true, everything is there :)
If I "move" the /boot/ directory to /boot.backup/ prior to untaring, then move
it back to /boot/ (replacing the one found inside the tar.gz) the system
boots - but with a wrong kernel, obviously.
Ideas?
Is /boot on the same partition as the root of the system? If not, are
they after the tar extraction? Are they the same file system?
Is the version of grub in the tar the same as the version installed?
I'm not sure I understand what the problem is. Is it that the menu
doesn't come up? If so, does /boot/grub/ exist, and is it populated with
the stage* files? /boot/grub/device.map? Does the content of
/boot/grub/device.map make sense?
Shachar
=================================================================
To unsubscribe, send mail to [EMAIL PROTECTED] with
the word "unsubscribe" in the message body, e.g., run the command
echo unsubscribe | mail [EMAIL PROTECTED]
