Ubuntu
grub package

Can't mount /boot partition

Asked by doclist

Since installing Hardy grub is using an old menu.lst so I am not booting newer kernels. I'm using LVM but my /boot is on its own partition. The menu.lst in /boot/grub looks to be correct (checked after I boot). How can I determine where grub is obtaining the menu.lst from and how can I fix it?

<edit>
My problem stems from not being able mount by /boot partition. Details in later comments.
</edit>

Question information

Language:
English Edit question
Status:
Solved
For:
Ubuntu grub Edit question
Assignee:
No assignee Edit question
Solved by:
doclist
Solved:
Last query:
Last reply:
Revision history for this message
Old_Soldier (charles.davis) said : 		#1

try reinstalling grubto the mbr if this is feasible for you.
sudo grub
root (hd0,1) --->assuming the menu.lst resides on the first partition of the first drive
setup (hd0) ------>puts grub in mbr of the first hdd
quit

sudo reboot now

Revision history for this message
doclist (dclist) said : 		#2

I think root (hd0, 1) installs to the second partition not the first
(e.g. sda2, not sda1). After further investigation it seems that my
/boot partition is not being mounted at boot time making the kernel
images (and menu.lst) stored on the wrong partition. When trying to
mount it I get "mount: /dev/sda4 already mounted or /boot busy". It
seems to be this issue:
http://ubuntuforums.org/archive/index.php/t-583958.html

I have uninstalled evms but to no avail. (Although, strangely, /dev/evms
still exists).

The following issues might also be pertinent:
https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.22/+bug/122568
https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.15/+bug/30995

I do not have the dm-X symlinks as described in:
https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.22/+bug/122568/comments/4

I suspect it is some kind of bad device mapping problem but I don't
have any idead how to debug it.

Revision history for this message
Old_Soldier (charles.davis) said : 		#3

actually you are correct as to hd (0,1) being the second partition. my apologies i wasn't paying real close attention and had mixed it up when making sure i didn't say setup (hd0,0). I'm not sure how to cure the underlying issue of the boot partition. Have you considered lilo as an alternative to grub?

Revision history for this message
doclist (dclist) said : 		#4

Any ideas greatly appreciated.

Revision history for this message
doclist (dclist) said : 		#5

I solved my problem by changing /dev/sda4 (my boot partition) to
/dev/evms/sda4. I guess I need to look up resources on how to
completely and safely remove evms.