On Sun, 20 Sep 2009 14:13:59 -0700, Eric wrote:
> After much angst, with a rescue DVD, i copied the contents of /boot out to
> a backup drive, reformatted the boot partition to ext3, and booted a
> separate disk with 2009.1 on it, then i used copied the files back
> from backup to /boot and using mcc i got the bootloader properly installed.
> However - i still have only 2 items on my main boot menu
> Here's /boot/grub/menu.lst whats wrong with it?
> Thanks
> Eric
>
> timeout 15
> color black/cyan yellow/cyan
> gfxmenu (hd0,0)/gfxmenu
> default 2
>
> title linux-nonfb
> kernel (hd0,0)/vmlinuz BOOT_IMAGE=linux-nonfb root=LABEL=/
> initrd (hd0,0)/initrd.img
>
> title failsafe
> kernel (hd0,0)/vmlinuz BOOT_IMAGE=failsafe root=LABEL=/ failsafe
> initrd (hd0,0)/initrd.img
>
> title desktop-2.6.29.6-2mnb
> kernel (hd0,0)/vmlinuz-2.6.29.6-desktop-2mnb
> BOOT_IMAGE=desktop_2.6.29.6-2mnb root=LABEL=/ vga=788
> initrd (hd0,0)/initrd-2.6.29.6-desktop-2mnb.img

Well, we have to assume on the first drive and first partition is
where you have the files /boot/vmlinuz-2.6.29.6-desktop-2mnb and
/boot/initrd-2.6.29.6-desktop-2mnb.img

What impresses me is you have a label of /. I know when I first tried
that with /some_label the system did not like the /.

I use the release value for my labels or release candidate.

Here are the labels on my system
/dev/sda1: LABEL="HP_PAVILION"
/dev/sda2: LABEL="HP_RECOVERY"
/dev/sda5: LABEL="DOZE"
/dev/sda6: LABEL="swap"
/dev/sda7: LABEL="accounts"
/dev/sda8: LABEL="hotbu"
/dev/sda9: LABEL="bk_up"
/dev/sda10: LABEL="2008_1"
/dev/sda11: LABEL="2009_0"
/dev/sda12: LABEL="beta"
/dev/sda13: LABEL="2009_1"
/dev/sda14: LABEL="cooker"
/dev/sdb1: LABEL="local"
/dev/sdb5: LABEL="vmguest"

Snippet from my menu.lst
$ grep kernel /boot/grub/menu.lst
kernel (hd0,13)/boot/vmlinuz BOOT_IMAGE=cooker root=LABEL=cooker vga=791
kernel (hd0,13)/boot/vmlinuz BOOT_IMAGE=linux-nonfb root=LABEL=cooker
kernel (hd0,13)/boot/vmlinuz BOOT_IMAGE=failsafe root=LABEL=cooker failsafe


$ grep cooker /etc/fstab
LABEL=cooker / ext3 relatime 1 1

On Sun, 20 Sep 2009 17:13:59 -0400, Eric <apophis@ruler.of.the.night.org> wrote:

> Here's /boot/grub/menu.lst whats wrong with it?

Most likely, at least one of the files in /boot does not exist.

Given that the original problem was lack of space during the
kernel install, I'd uninstall, then reinstall the kernel with
urpme kernel-desktop-2.6.29.6-2mnb kernel-desktop-devel-2.6.29.6-2mnb
urpmi kernel-desktop-2.6.29.6-2mnb kernel-desktop-devel-2.6.29.6-2mnb

Regards, Dave Hodgins

--
Change nomail.afraid.org to ody.ca to reply by email.
(nomail.afraid.org has been set up specifically for
use in usenet. Feel free to use it yourself.)

David W. Hodgins wrote:
> On Sun, 20 Sep 2009 17:13:59 -0400, Eric
> <apophis@ruler.of.the.night.org> wrote:
>
>> Here's /boot/grub/menu.lst whats wrong with it?
>
> Most likely, at least one of the files in /boot does not exist.
>
> Given that the original problem was lack of space during the
> kernel install, I'd uninstall, then reinstall the kernel with
> urpme kernel-desktop-2.6.29.6-2mnb kernel-desktop-devel-2.6.29.6-2mnb
> urpmi kernel-desktop-2.6.29.6-2mnb kernel-desktop-devel-2.6.29.6-2mnb
>
> Regards, Dave Hodgins
>
Here's my menu.lst and the contents of /boot, i dont see whats wrong.
I can boot now, but i still have only 2 entries in my main boot menu
when i expected 3.

#->cat grub/menu.lst
timeout 15
color black/cyan yellow/cyan
gfxmenu (hd0,0)/gfxmenu
default 2

title linux-nonfb
kernel (hd0,0)/vmlinuz BOOT_IMAGE=linux-nonfb root=LABEL=/
initrd (hd0,0)/initrd.img

title failsafe
kernel (hd0,0)/vmlinuz BOOT_IMAGE=failsafe root=LABEL=/ failsafe
initrd (hd0,0)/initrd.img

title desktop-2.6.29.6-2mnb
kernel (hd0,0)/vmlinuz-2.6.29.6-desktop-2mnb
BOOT_IMAGE=desktop_2.6.29.6-2mnb root=LABEL=/ vga=788
initrd (hd0,0)/initrd-2.6.29.6-desktop-2mnb.img

contents of /boot:
boot.backup.sda
config -> config-2.6.29.6-desktop-2mnb
config-2.6.29.6-desktop-2mnb
gfxmenu*
grub/
initrd-2.6.29.6-desktop-2mnb.img
initrd-desktop.img -> initrd-2.6.29.6-desktop-2mnb.img
initrd.img -> initrd-2.6.29.6-desktop-2mnb.img
kernel.h -> /boot/kernel.h-2.6.29.6-desktop-2mnb
kernel.h-2.6.29.6-desktop-2mnb
symvers-2.6.29.6-desktop-2mnb.gz
System.map -> System.map-2.6.29.6-desktop-2mnb
System.map-2.6.29.6-desktop-2mnb
vmlinuz -> vmlinuz-2.6.29.6-desktop-2mnb
vmlinuz-2.6.29.6-desktop-2mnb
vmlinuz-desktop -> vmlinuz-2.6.29.6-desktop-2mnb

on Sun, 20 Sep 2009 07:36 am
in the Usenet newsgroup alt.os.linux.mandriva
Eric wrote:

> I was trying to install a 2nd kernel to play with and ran out of space
> during the make install operation, thats ok (i removed what got installed
> and will add another disk later to play on), but it left my grub boot
> loader corrupted. I have 3 items in menu.lst but only 2 ever show up on
> my boot menu. I thought to just refresh my grub install, but this turns
> out to be a very confusing process. Can anyone give me a simple command
> line that will refresh my grub boot loader etc
> all my kernels are in /boot, grub is in /boot/grub and i have just the
one
> disk /dev/sda with /boot on /dev/sda1
> (/ home var usr are on separate partitions)
>
> I tried grub-install --root-directory=/boot /dev/sda but it sat there
> forever doing nothing - this process cant take more than a few seconds,
> tops, can it? Makes me wish for the good old days of lilo again.

urpmi lilo

Happy days are here again.

> I also tried the rescue CD but it cant determine my root - even though
the
> disk still boots ok.

You can try a live CD like one of the Mandriva ONE discs. Or, if you are
desperate, reinstall from your original media and selecting "update". That
will be reasonably quick, because there won't be any real updates done.

> Thanks
> Eric
> grub (GNU GRUB 0.97)
> mandriva 2009.1 x86_64 system, sata boot drive on /dev/sda
>

--
Peter D.
Sig goes here...

On Sun, 20 Sep 2009 21:48:04 -0400, Eric <apophis@ruler.of.the.night.org> wrote:

> Here's my menu.lst and the contents of /boot, i dont see whats wrong.
> I can boot now, but i still have only 2 entries in my main boot menu
> when i expected 3.

Everything there looks ok. As all three entries use the same kernel,
I'm surprised one of them isn't showing up.

Which one isn't showing up?

Regards, Dave Hodgins

--
Change nomail.afraid.org to ody.ca to reply by email.
(nomail.afraid.org has been set up specifically for
use in usenet. Feel free to use it yourself.)

David W. Hodgins wrote:

> On Sun, 20 Sep 2009 21:48:04 -0400, Eric <apophis@ruler.of.the.night.org>
> wrote:
>
>> Here's my menu.lst and the contents of /boot, i dont see whats wrong.
>> I can boot now, but i still have only 2 entries in my main boot menu
>> when i expected 3.
>
> Everything there looks ok. As all three entries use the same kernel,
> I'm surprised one of them isn't showing up.
>
> Which one isn't showing up?
>
> Regards, Dave Hodgins
>
only "failsafe" and "desktop-2.6.29.6-2mnb" show up
"linux-nonfb" doesnt show.
Eric


--
Msg to ET:
If you get here and there's no planet -
dont ever build a Large Hadron Collider

On Sun, 20 Sep 2009 18:48:04 -0700, Eric wrote:


>
> #->cat grub/menu.lst
> timeout 15
> color black/cyan yellow/cyan
> gfxmenu (hd0,0)/gfxmenu
> default 2
>
> title linux-nonfb
> kernel (hd0,0)/vmlinuz BOOT_IMAGE=linux-nonfb root=LABEL=/ initrd
> (hd0,0)/initrd.img
>
> title failsafe
> kernel (hd0,0)/vmlinuz BOOT_IMAGE=failsafe root=LABEL=/ failsafe initrd
> (hd0,0)/initrd.img
>
> title desktop-2.6.29.6-2mnb
> kernel (hd0,0)/vmlinuz-2.6.29.6-desktop-2mnb
> BOOT_IMAGE=desktop_2.6.29.6-2mnb root=LABEL=/ vga=788 initrd
> (hd0,0)/initrd-2.6.29.6-desktop-2mnb.img
>

You say only two menu items come up on your grub menu? I may be
repeating myself, but are there any other partitions that may have a grub
menu.lst file. If you don't mind, could you try one more thing. When
grub loads and you get to the menu, drop to the grub command prompt by
hitting the letter "c". In the grub prompt type the following:

root (hd0,0)
configfile /boot/grub/menu.lst

Does that bring up the menu with all three items?

jellybean stonerfish wrote:

> On Sun, 20 Sep 2009 18:48:04 -0700, Eric wrote:
>
>
>>
>> #->cat grub/menu.lst
>> timeout 15
>> color black/cyan yellow/cyan
>> gfxmenu (hd0,0)/gfxmenu
>> default 2
>>
>> title linux-nonfb
>> kernel (hd0,0)/vmlinuz BOOT_IMAGE=linux-nonfb root=LABEL=/ initrd
>> (hd0,0)/initrd.img
>>
>> title failsafe
>> kernel (hd0,0)/vmlinuz BOOT_IMAGE=failsafe root=LABEL=/ failsafe initrd
>> (hd0,0)/initrd.img
>>
>> title desktop-2.6.29.6-2mnb
>> kernel (hd0,0)/vmlinuz-2.6.29.6-desktop-2mnb
>> BOOT_IMAGE=desktop_2.6.29.6-2mnb root=LABEL=/ vga=788 initrd
>> (hd0,0)/initrd-2.6.29.6-desktop-2mnb.img
>>
>
> You say only two menu items come up on your grub menu? I may be
> repeating myself, but are there any other partitions that may have a grub
> menu.lst file. If you don't mind, could you try one more thing. When
> grub loads and you get to the menu, drop to the grub command prompt by
> hitting the letter "c". In the grub prompt type the following:
>
> root (hd0,0)
> configfile /boot/grub/menu.lst
>
> Does that bring up the menu with all three items?

if i use root (hd0,0) it cant find the menu.lst but if i use root(hd1,0)
it finds the menu.lst with 2 items on it

There is only 1 copy of menu.lst on my disk, at least thats what "locate
menu.lst" shows (i ran updatedb 1st)
I'm grateful for the time you're taking on this
Eric

On Sat, 26 Sep 2009 02:57:22 -0400, Eric <apophis@ruler.of.the.night.org> wrote:

> if i use root (hd0,0) it cant find the menu.lst but if i use root(hd1,0)
> it finds the menu.lst with 2 items on it

This helps a lot, in figuring out what the problem is.

You have multiple hard drives, and there is a difference as to what is
seen as hd0 or hd1 by grub/grub-install, depending on how you boot the
system.

The menu.lst on hd1 is not showing up in locate, because the filesystem
it's on was not mounted when the updatedb was run.

Are these drives sata, or pata (aka ide), or a mixture of the two?

Make sure the bios is set to boot from the cd first.

Boot from the cd, get to a command line, and run /sbin/hdparm -i /dev/sda
Take note of which model is seen as sda.

Boot into linux and run the same command. Assuming the two drives are
not the same model number, I expect you'll find the other drive is now
/dev/sda, as the bios has been configured to switch the drive order.

Getting a consistent result for the drive order will require figuring out
which drive is sda (aka hd0) when booted from the cd, installing grub on
that drives mbr, and changing the order of hard drive selection in the
bios setup program, such that that drive is the one that is used as the
first hard drive to boot from.

Regards, Dave Hodgins

--
Change nomail.afraid.org to ody.ca to reply by email.
(nomail.afraid.org has been set up specifically for
use in usenet. Feel free to use it yourself.)

On Fri, 25 Sep 2009 23:57:22 -0700, Eric wrote:

> jellybean stonerfish wrote:
>
>>>
>> You say only two menu items come up on your grub menu? I may be
>> repeating myself, but are there any other partitions that may have a
>> grub menu.lst file. If you don't mind, could you try one more thing.
>> When grub loads and you get to the menu, drop to the grub command
>> prompt by hitting the letter "c". In the grub prompt type the
>> following:
>>
>> root (hd0,0)
>> configfile /boot/grub/menu.lst
>>
>> Does that bring up the menu with all three items?
>
> if i use root (hd0,0) it cant find the menu.lst but if i use root(hd1,0)
> it finds the menu.lst with 2 items on it
>
> There is only 1 copy of menu.lst on my disk, at least thats what "locate
> menu.lst" shows (i ran updatedb 1st)
> I'm grateful for the time you're taking on this Eric


The grub shell has completion. If you enter the grub shell before
booting, you can see what drives and partitions are available. Type:

root (

Then hit tab twice. That should show you the possible entries for the
"root" command. It appears you have a menu.lst file on a partition or
disk that wasn't mounted and searched when you did your "locate"

jellybean stonerfish wrote:
> On Fri, 25 Sep 2009 23:57:22 -0700, Eric wrote:
>
>> jellybean stonerfish wrote:
>>
>>> You say only two menu items come up on your grub menu? I may be
>>> repeating myself, but are there any other partitions that may have a
>>> grub menu.lst file. If you don't mind, could you try one more thing.
>>> When grub loads and you get to the menu, drop to the grub command
>>> prompt by hitting the letter "c". In the grub prompt type the
>>> following:
>>>
>>> root (hd0,0)
>>> configfile /boot/grub/menu.lst
>>>
>>> Does that bring up the menu with all three items?
>> if i use root (hd0,0) it cant find the menu.lst but if i use root(hd1,0)
>> it finds the menu.lst with 2 items on it
>>
>> There is only 1 copy of menu.lst on my disk, at least thats what "locate
>> menu.lst" shows (i ran updatedb 1st)
>> I'm grateful for the time you're taking on this Eric
>
>
> The grub shell has completion. If you enter the grub shell before
> booting, you can see what drives and partitions are available. Type:
>
> root (
>
> Then hit tab twice. That should show you the possible entries for the
> "root" command. It appears you have a menu.lst file on a partition or
> disk that wasn't mounted and searched when you did your "locate"
>
I booted with 1 drive connected to sata port 0. i then went into /boot/grub
and deleted everything except device.map install.sh and menu.lst. device.map
has one entry for hd0. Then in kde i used mcc to reinstall the botloader, i
checked that it saw the 3 entries and that all references were to hd0. so far
so good, i then rebooted and i still see only 2 menu entries at the boot screen.
I'm moving to 2010 anyway so I'm not sure this is worth persuing further
Thanks
Eric

Eric