| 1 |
On 5/17/06, maxim wexler <blissfix@×××××.com> wrote: |
| 2 |
> This has gotta be the problem. Or most of it. I've |
| 3 |
> been going along all this time separately mounting a |
| 4 |
> /boot partition, formatted ext2 and a root partitiion, |
| 5 |
> formatted reiserfs which already has a "boot" dir |
| 6 |
> attached. Is that the one that actually boots? Is it |
| 7 |
> even a problem? How did it get there? Better yet, how |
| 8 |
> do I explain this to the bug folks? |
| 9 |
|
| 10 |
Yes, this is almost certainly the problem. |
| 11 |
|
| 12 |
Regarding the issue of which one boots, it is a bit of a difficult |
| 13 |
question to answer. Since you do not have a /boot/grub directory on |
| 14 |
your root filesystem, I am going to assume that grub is not looking at |
| 15 |
the files on on your root filesystem for it's configuration. By this |
| 16 |
I mean that grub needs a grub.conf or menu.lst file to tell it what |
| 17 |
boot options to present, and since you seem to have only one of those |
| 18 |
(in the /grub directory on your /boot filesystem), it must be looking |
| 19 |
at that one. |
| 20 |
|
| 21 |
Now if you use root(hd0,1) in your grub.conf file, then you are using |
| 22 |
the files on /dev/sda2. If it shows root(hd0,6), then you are trying |
| 23 |
to boot from files on /dev/sda7. But actually you don't need to |
| 24 |
specify a root, you could just as easily list your kernel as |
| 25 |
(hd0,1)/vmlinuz, so check for that as well. |
| 26 |
|
| 27 |
What really disturbs me about what you have just posted though is that |
| 28 |
the root filesystem's /boot directory was updated recently (May 9th). |
| 29 |
This tells me that in some cases you are installing kernels without |
| 30 |
/boot mounted (I think I asked this as a 'stupid question' before...), |
| 31 |
and in other cases are doing it correctly with /boot mounted. |
| 32 |
|
| 33 |
So here is what I would suggest. Since you seem to like using |
| 34 |
'vmlinuz' as the name of your kernel, you can create an empty, |
| 35 |
immutable vmlinuz file in the root filesystem's /boot/. This will |
| 36 |
give you an error if you ever try to overwrite it with a new kernel. |
| 37 |
This should work: |
| 38 |
|
| 39 |
umount /boot |
| 40 |
rm /boot/vmlinuz |
| 41 |
touch /boot/vmlinuz |
| 42 |
chattr +i /boot/vmlinuz |
| 43 |
mount /boot |
| 44 |
|
| 45 |
If you ever try to overwrite the root filesystem's vmlinuz again, you |
| 46 |
will get "Permission denied". Example: |
| 47 |
|
| 48 |
carcharias rjf # cp -v |
| 49 |
/usr/src/linux-2.6.16-suspend2-r5/arch/i386/boot/bzImage /boot/vmlinuz |
| 50 |
`/usr/src/linux-2.6.16-suspend2-r5/arch/i386/boot/bzImage' -> `/boot/vmlinuz' |
| 51 |
cp: cannot create regular file `/boot/vmlinuz': Permission denied |
| 52 |
|
| 53 |
Can you please post your /boot/grub/grub.conf. If you have posted |
| 54 |
this before, I apologize, but I can't seem to find it in the previous |
| 55 |
threads. |
| 56 |
|
| 57 |
-Richard |
| 58 |
|
| 59 |
-- |
| 60 |
gentoo-user@g.o mailing list |
Archives