Grub: After installing linux-image-2.6.14-2-k7 grub had wrong entries

Bug #27915 reported by Debian Bug Importer
6
Affects Status Importance Assigned to Milestone
grub (Debian)
Fix Released
Unknown
grub (Ubuntu)
Invalid
High
Tollef Fog Heen

Bug Description

Automatically imported from Debian bug report #343260 http://bugs.debian.org/343260

Revision history for this message
In , maximilian attems (maks-debian) wrote : reassign 343260 to yaird

# Automatically generated email from bts, devscripts version 2.9.10
reassign 343260 yaird

Revision history for this message
In , maximilian attems (maks-debian) wrote : reassign 343260 to grub

# Automatically generated email from bts, devscripts version 2.9.10
reassign 343260 grub

Revision history for this message
Debian Bug Importer (debzilla) wrote :

Automatically imported from Debian bug report #343260 http://bugs.debian.org/343260

Revision history for this message
Debian Bug Importer (debzilla) wrote :
Download full text (4.1 KiB)

Message-ID: <email address hidden>
Date: Wed, 14 Dec 2005 00:50:57 +0100
From: Stefan Hirschmann <email address hidden>
To: Debian Bug Tracking System <email address hidden>
Subject: Grub: After installing linux-image-2.6.14-2-k7 grub had wrong entries

Package: linux-image-2.6.14-2-k7
Version: 2.6.14-5
Severity: critical
Justification: breaks the whole system

After installing linux-image-2.6.14-2-k7 grub had only wrong entries.
For example
Instead of hda(0,8) hda(0,7) was in the grub config file. And also:
Instead:
    /boot/vmlinuz-2.6.14-2-k7 root=/dev/hda9 ro
there was:
    /boot/vmlinuz-2.6.14-2-k7 root=/dev/hda8 ro

This was for all 3 kernels I have ever installed including this. Only
the winxp entry at the end of the menu.lst (the name of my grub
conffile) was not affected. Until I corrected this, the system was not
bootable so I think that severity: critical, breaks the whole system is
the right one, cause until I corrected it, no kernel version was able to
boot.

The output of my partition table is:
Disk /dev/hda: 160.0 GB, 160041885696 bytes
255 heads, 63 sectors/track, 19457 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot Start End Blocks Id System
   /dev/hda1 * 4 765 6120765 b W95 FAT32
   /dev/hda2 766 19457 150143490 f W95 Ext'd
   (LBA)
   /dev/hda5 766 5227 35840983+ b W95 FAT32
   /dev/hda6 5228 14711 76180198+ b W95 FAT32
   /dev/hda7 14712 17484 22274091 b W95 FAT32
   /dev/hda8 17485 18358 7020373+ 83 Linux
   /dev/hda9 18359 19209 6835626 83 Linux
   /dev/hda10 19210 19457 1992028+ 82 Linux swap /

You should know, that linux (including the kernel) is installed on
hda9, but a few important directorys are chanced with symlinks to hda8
(e.g. home). The kernel itself is on hda9.

Another strang bug, is that if winxp is the first entry in grub, than it
will removed after an "aptitude install linux...."

Cheers,
Stefan

-- System Information:
Debian Release: testing/unstable
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.14-2-k7
Locale: LANG=de_AT@euro, LC_CTYPE=de_AT@euro (charmap=ISO-8859-15)

Versions of packages linux-image-2.6.14-2-k7 depends on:
ii module-init-tools 3.2-pre9-4 tools for managing Linux kernel mo
ii yaird [linux-initramfs-tool] 0.0.11-12 Yet Another mkInitRD

Versions of packages linux-image-2.6.14-2-k7 recommends:
ii libc6-i686 2.3.5-8 GNU C Library: Shared libraries [i

-- debconf information:
  linux-image-2.6.14-2-k7/preinst/elilo-initrd-2.6.14-2-k7: true
  linux-image-2.6.14-2-k7/preinst/lilo-initrd-2.6.14-2-k7: true
  linux-image-2.6.14-2-k7/preinst/abort-overwrite-2.6.14-2-k7:
  linux-image-2.6.14-2-k7/postinst/bootloader-error-2.6.14-2-k7:
  linux-image-2.6.14-2-k7/preinst/overwriting-modules-2.6.14-2-k7: true
  linux-image-2.6.14-2-k7/postinst/old-system-map-link-2.6.14-2-k7: true
  linu...

Read more...

Revision history for this message
Debian Bug Importer (debzilla) wrote :

Message-Id: <E1EtoUR-0001mt-HN@nancy>
Date: Tue, 3 Jan 2006 16:54:23 +0100
From: maximilian attems <email address hidden>
To: <email address hidden>
Subject: reassign 343260 to yaird

# Automatically generated email from bts, devscripts version 2.9.10
reassign 343260 yaird

Revision history for this message
Debian Bug Importer (debzilla) wrote :

Message-Id: <E1EtoVX-0001nE-MU@nancy>
Date: Tue, 3 Jan 2006 16:55:31 +0100
From: maximilian attems <email address hidden>
To: <email address hidden>
Subject: reassign 343260 to grub

# Automatically generated email from bts, devscripts version 2.9.10
reassign 343260 grub

Revision history for this message
In , Jason Thomas (jason-debian) wrote : more info please

Can you please send a copy of:
- menu.lst
- copy of menu.lst with winxp as the first entry.
- fstab
- output of `mount` command

Do you have any idea why this has happened?

Thanks.

Revision history for this message
Debian Bug Importer (debzilla) wrote :

Message-ID: <email address hidden>
Date: Wed, 4 Jan 2006 08:32:28 +1100
From: Jason Thomas <email address hidden>
To: <email address hidden>
Subject: more info please

Can you please send a copy of:
- menu.lst
- copy of menu.lst with winxp as the first entry.
- fstab
- output of `mount` command

Do you have any idea why this has happened?

Thanks.

Revision history for this message
Chuck Short (zulcss) wrote :

Not us

Revision history for this message
In , Stefan Hirschmann (krasnoj) wrote : Re: Bug #343260

Hi!

Sorry for the late answer, but I havent seen youre answer earlier.

First of all I could find a solution to my problem. It was a wron
entry in the menu.lst. There was the line:
# kopt=root=/dev/hda8 ro
in the menu.lst

After I changed it to
# kopt=root=/dev/hda9 ro
I could install any kernel or run update-grub (what was the real
problem) and everything still runs fine.

Hope, that this helps you, but I have no idea why this entry was wrong.

Here ist the output of fstab:

$ cat /etc/fstab
# /etc/fstab: static file system information.
#
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc defaults 0 0
/dev/hda9 / ext3 defaults,errors=remount-ro
0 1
/dev/hda10 none swap sw 0 0
/dev/hdc /media/cdrom0 iso9660 ro,user,noauto 0 0
/dev/hdd /media/cdrom1 iso9660 ro,user,noauto 0 0
/dev/fd0 /media/floppy0 auto rw,user,noauto 0 0

/dev/hda8 /backup/ ext3 defaults,errors=remount-ro 0 0
/dev/hda1 /windows/win_c vfat rw,user,uid=1000 0 0
/dev/hda5 /windows/win_d vfat rw,user,uid=1000 0 0
/dev/hda6 /windows/win_e vfat
rw,user,exec,gid=krasnoj,umask=007 00
/dev/hda7 /windows/win_f vfat rw,user,uid=1000 0 0
/dev/hdb1 /windows/win_g vfat rw,user,uid=1000 0 0

Then mount:
# mount
/dev/hda9 on / type ext3 (rw,errors=remount-ro)
proc on /proc type proc (rw)
sysfs on /sys type sysfs (rw)
devpts on /dev/pts type devpts (rw,gid=5,mode=620)
tmpfs on /dev/shm type tmpfs (rw)
usbfs on /proc/bus/usb type usbfs (rw)
/dev/hda8 on /backup type ext3 (rw,errors=remount-ro)
/dev/hda1 on /windows/win_c type vfat (rw,noexec,nosuid,nodev,uid=1000)
/dev/hda5 on /windows/win_d type vfat (rw,noexec,nosuid,nodev,uid=1000)
/dev/hda6 on /windows/win_e type vfat (rw,nosuid,nodev,gid=1000,umask=007)
/dev/hda7 on /windows/win_f type vfat (rw,noexec,nosuid,nodev,uid=1000)
/dev/hdb1 on /windows/win_g type vfat (rw,noexec,nosuid,nodev,uid=1000

Cheers Stefan
--
If you answer, please send it CC: <email address hidden> AND TO:
<email address hidden>

Revision history for this message
In , Stefan Hirschmann (krasnoj) wrote : My menu.lst

Hi!

I added two files. menu.lst.withwindowsfirst contains my menu.list with
windows as the first entry.

menu.lst is the same file after I started update-grub. As you can see,
the windows entry is away (but if the windows entry is at the end of the
list it will survive (as you can also see in the files).

Cheers, Stefan

Revision history for this message
In , Kristian Edlund (edlund) wrote : Closing

I am closing this bug for now, feel free to reopen it if you disagree.

As far as I can see this is normal behaviour, if you want the windows
entry to be the first it has to be put before the start tag:

### BEGIN AUTOMAGIC KERNELS LIST

The thing about the wrong drive number, well it seems that the groot
option was wrong, and update grub did work as intended.
--
Best Regards
Kristian Edlund

GPG ID: 7DD7559F

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.