Grub can't find:
message.elyssa
in the boot process. Grub is fine, just it's normal grub, not Elyssa's. So, how do I fix it. I tried
sudo grub
find /boot/grub/stage1
and it can't find it. Here's the partition scheme:
/dev/sda1 - /boot
/dev/sda2 - swap
/dev/sda3 - /home
/dev/sda4 - /
Thanks
EDIT:
oh yeah, /boot/grub/stage1 is there, I checked via Nautilus.
EDIT2:
I put swap as /swap. I was tired haha
Grub question
Forum rules
Before you post read how to get help. Topics in this forum are automatically closed 6 months after creation.
Before you post read how to get help. Topics in this forum are automatically closed 6 months after creation.
Grub question
Last edited by LockBot on Wed Dec 28, 2022 7:16 am, edited 2 times in total.
Reason: Topic automatically closed 6 months after creation. New replies are no longer allowed.
Reason: Topic automatically closed 6 months after creation. New replies are no longer allowed.
Re: Grub question
Acid_1,
It looks as if they are still carrying that separate boot partition problem too.
First, copy "message.elyssa" from /etc/grub and put it in /boot/grub. You can use SuperGrub to boot into the install if you wish. Don't fix anything with it, just use it to boot with. Then change the line in /boot/grub/menu.lst below from:
gfxmenu=/etc/grub/message.elyssa
to
gfxmenu=/boot/grub/message.elyssa
That should get your nice boot screen when you get done.
Remember the menu.lst and Linux kernel are in the /boot folder so thats where the grub kernel should point to, not /.
Assuming you are booting from sda, you need to reset the pointers to the /boot partition. Use SuperGrub to boot into your install. Again, don't try to fix it with SuperGrub, just use it to boot into the install.
Once in the install, open a terminal and type:
sudo grub
root (hd0,0)
setup (hd0)
quit
This installs the grub kernel to the mbr of sda and points to stage 1.5 and the menu.lst on your /boot partition. Reboot and hopefully all will be well.
Fred
It looks as if they are still carrying that separate boot partition problem too.
First, copy "message.elyssa" from /etc/grub and put it in /boot/grub. You can use SuperGrub to boot into the install if you wish. Don't fix anything with it, just use it to boot with. Then change the line in /boot/grub/menu.lst below from:
gfxmenu=/etc/grub/message.elyssa
to
gfxmenu=/boot/grub/message.elyssa
That should get your nice boot screen when you get done.
Remember the menu.lst and Linux kernel are in the /boot folder so thats where the grub kernel should point to, not /.
Assuming you are booting from sda, you need to reset the pointers to the /boot partition. Use SuperGrub to boot into your install. Again, don't try to fix it with SuperGrub, just use it to boot into the install.
Once in the install, open a terminal and type:
sudo grub
root (hd0,0)
setup (hd0)
quit
This installs the grub kernel to the mbr of sda and points to stage 1.5 and the menu.lst on your /boot partition. Reboot and hopefully all will be well.
Fred
Last edited by Fred on Mon Sep 15, 2008 11:48 am, edited 1 time in total.
- T J Tulley
- Level 5
- Posts: 558
- Joined: Wed Jul 18, 2007 10:18 am
- Location: Hull, England
Re: Grub question
I am interested in Fred's reply to this question. Until today I had never met a partition allocated to /boot - to me, boot is a flag which can be set in the Partition editor, and in my set-up it is applied to the / partitions in various disks- they all work.
Yours hopefully -
Theo Tulley.
Using a PC with 2GB RAM, 3 hdds and a 1.7 GHz Celeron cpu.
Theo Tulley.
Using a PC with 2GB RAM, 3 hdds and a 1.7 GHz Celeron cpu.
Re: Grub question
Theo,
As you know, in Linux you can break things up on separate partitions. An example I am sure you are familiar with is having a separate /home partition. You don't have to have one but some want/need it depending on what they are doing with their computer and how they choose to have it laid out.
You can also have a separate /boot partition. There are reasons why some people would want this also. In this case, there is a bug in gfxgrub that causes problems reading the message, or boot screen, from another partition. Since most people using Mint as a GP desktop don't use a separate /boot partition, /boot stays in /, they don't see the problem. If you have a separate /boot partition, you usually have to put a copy of the message in the /boot/grub folder to see the boot screen.
The other problem has to do with the way the installer defaults to installing grub. As I have said before, the installer is not very smart. It assumes you don't have a separate /boot partition and installs the grub kernel pointer to / instead of /boot.
What I suggested he do is give the commands to point the grub kernel pointer at the /boot partition where it should be, in this case.
I hope this helps you understand better sir.
Fred
As you know, in Linux you can break things up on separate partitions. An example I am sure you are familiar with is having a separate /home partition. You don't have to have one but some want/need it depending on what they are doing with their computer and how they choose to have it laid out.
You can also have a separate /boot partition. There are reasons why some people would want this also. In this case, there is a bug in gfxgrub that causes problems reading the message, or boot screen, from another partition. Since most people using Mint as a GP desktop don't use a separate /boot partition, /boot stays in /, they don't see the problem. If you have a separate /boot partition, you usually have to put a copy of the message in the /boot/grub folder to see the boot screen.
The other problem has to do with the way the installer defaults to installing grub. As I have said before, the installer is not very smart. It assumes you don't have a separate /boot partition and installs the grub kernel pointer to / instead of /boot.
What I suggested he do is give the commands to point the grub kernel pointer at the /boot partition where it should be, in this case.
I hope this helps you understand better sir.
Fred