Bug#540125: grub-pc: upgrade renders system unbootable

2009-08-28 Thread Michal Suchanek
2009/8/26 Michal Suchanek hramr...@centrum.cz:
 2009/8/26 Robert Millan r...@aybabtu.com:
 On Thu, Aug 06, 2009 at 10:24:57AM +1000, Jayen wrote:
 Package: grub-pc
 Version: 1.96+20090725-1
 Severity: critical
 Justification: breaks the whole system


 I know On i386-pc (and amd64), the grub package never updates the installed
 version of GRUB automatically.  However, this has rendered the system
 unbootable for me twice now.  I know I'm running something unstable, but 
 users
 should NOT be expected to know how to fix an unbootable system.  There 
 should
 at least be a debconf question of whether to run grub-install.

 The error I'm getting is Unknown command: initrd similar to #513592 and
 #497791 (and probably others).

 What happens if you comment out the search commands?  (all of them)

 And if you add insmod linux at the beginning of grub.cfg?


 Neither helps.

 You have to load kernel first.

 I tried loading the kernel by hand which sort of works but then I do
 not get the 'boot' command so I cannot start it.

 With grub rescue CD I managed to do this so I suspect there is
 something deficient in the on-disk installation of grub.


With a newer grub (1.96+20090808-1)  I can at least load the kernel
manually as I could with the rescue CD. The menu still fails to boot
with the same message, though.

Thanks

Michal



--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#540125: grub-pc: upgrade renders system unbootable

2009-08-28 Thread Robert Millan
On Fri, Aug 28, 2009 at 03:05:04PM +0200, Michal Suchanek wrote:
 2009/8/26 Michal Suchanek hramr...@centrum.cz:
  2009/8/26 Robert Millan r...@aybabtu.com:
  On Thu, Aug 06, 2009 at 10:24:57AM +1000, Jayen wrote:
  Package: grub-pc
  Version: 1.96+20090725-1
  Severity: critical
  Justification: breaks the whole system
 
 
  I know On i386-pc (and amd64), the grub package never updates the 
  installed
  version of GRUB automatically.  However, this has rendered the system
  unbootable for me twice now.  I know I'm running something unstable, but 
  users
  should NOT be expected to know how to fix an unbootable system.  There 
  should
  at least be a debconf question of whether to run grub-install.
 
  The error I'm getting is Unknown command: initrd similar to #513592 and
  #497791 (and probably others).
 
  What happens if you comment out the search commands?  (all of them)
 
  And if you add insmod linux at the beginning of grub.cfg?
 
 
  Neither helps.
 
  You have to load kernel first.
 
  I tried loading the kernel by hand which sort of works but then I do
  not get the 'boot' command so I cannot start it.
 
  With grub rescue CD I managed to do this so I suspect there is
  something deficient in the on-disk installation of grub.
 
 
 With a newer grub (1.96+20090808-1)  I can at least load the kernel
 manually as I could with the rescue CD. The menu still fails to boot
 with the same message, though.

Please try with 1.96+20090826-3

-- 
Robert Millan

  The DRM opt-in fallacy: Your data belongs to us. We will decide when (and
  how) you may access your data; but nobody's threatening your freedom: we
  still allow you to remove your data and not access it at all.



-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#540125: grub-pc: upgrade renders system unbootable

2009-08-26 Thread Michal Suchanek
2009/8/26 Robert Millan r...@aybabtu.com:
 On Thu, Aug 06, 2009 at 10:24:57AM +1000, Jayen wrote:
 Package: grub-pc
 Version: 1.96+20090725-1
 Severity: critical
 Justification: breaks the whole system


 I know On i386-pc (and amd64), the grub package never updates the installed
 version of GRUB automatically.  However, this has rendered the system
 unbootable for me twice now.  I know I'm running something unstable, but 
 users
 should NOT be expected to know how to fix an unbootable system.  There should
 at least be a debconf question of whether to run grub-install.

 The error I'm getting is Unknown command: initrd similar to #513592 and
 #497791 (and probably others).

 What happens if you comment out the search commands?  (all of them)

 And if you add insmod linux at the beginning of grub.cfg?


Neither helps.

You have to load kernel first.

I tried loading the kernel by hand which sort of works but then I do
not get the 'boot' command so I cannot start it.

With grub rescue CD I managed to do this so I suspect there is
something deficient in the on-disk installation of grub.

Thanks

Michal



--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#540125: grub-pc: upgrade renders system unbootable

2009-08-25 Thread Robert Millan
On Thu, Aug 06, 2009 at 10:24:57AM +1000, Jayen wrote:
 Package: grub-pc
 Version: 1.96+20090725-1
 Severity: critical
 Justification: breaks the whole system
 
 
 I know On i386-pc (and amd64), the grub package never updates the installed 
 version of GRUB automatically.  However, this has rendered the system 
 unbootable for me twice now.  I know I'm running something unstable, but 
 users 
 should NOT be expected to know how to fix an unbootable system.  There should 
 at least be a debconf question of whether to run grub-install.
 
 The error I'm getting is Unknown command: initrd similar to #513592 and 
 #497791 (and probably others).

What happens if you comment out the search commands?  (all of them)

And if you add insmod linux at the beginning of grub.cfg?

-- 
Robert Millan

  The DRM opt-in fallacy: Your data belongs to us. We will decide when (and
  how) you may access your data; but nobody's threatening your freedom: we
  still allow you to remove your data and not access it at all.



-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#540125: grub-pc: upgrade renders system unbootable

2009-08-08 Thread Jayen Ashar

hrm.  you are quite right.  i'm pretty sure i had set debconf to re-ask old 
questions, but apparently not.  dpkg-reconfigure debconf doesn't give me this 
option, and i'm really sure it used to.  i'll file a bug against debconf in 
that case.

sorry for your troubles.  thanks for your help.

--jayen



- Original Message 
From: Felix Zielcke fziel...@z-51.de
To: 540...@bugs.debian.org
Cc: Jayen j...@yahoo.com
Sent: Thursday, 6 August, 2009 4:12:08 PM
Subject: Re: Bug#540125: grub-pc: upgrade renders system unbootable

Am Donnerstag, den 06.08.2009, 07:57 +0200 schrieb Felix Zielcke:
 Am Donnerstag, den 06.08.2009, 10:24 +1000 schrieb Jayen:
  Package: grub-pc
  Version: 1.96+20090725-1
  Severity: critical
  Justification: breaks the whole system
  
  
  I know On i386-pc (and amd64), the grub package never updates the installed 
  version of GRUB automatically.  However, this has rendered the system 
  unbootable for me twice now.  I know I'm running something unstable, but 
  users 
  should NOT be expected to know how to fix an unbootable system.  There 
  should 
  at least be a debconf question of whether to run grub-install.
  
  The error I'm getting is Unknown command: initrd similar to #513592 and 
  #497791 (and probably others).
  
 
 Uhm we have already a debconf prompt for running grub-install.
 Currently it gets shown when core.img exists and the package is
 upgraded. But in SVN we changed it now that it gets shown when there are
 no grub-legacy files in /boot/grub and core.img exists, i.e. no check if
 the package gets upgraded.

Try dpkg-reconfigure grub-pc
that should show the debconf prompt.
I just tried it now out again with current sid/squeeze version.
debconf prompts are by design shown only once, so maybe it was shown and
you didn't notice this.

-- 
Felix Zielcke
Proud Debian Maintainer


  
__
Find local businesses and services in your area with Yahoo!7 Local.
Get started: http://local.yahoo.com.au




--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#540125: grub-pc: upgrade renders system unbootable

2009-08-06 Thread Felix Zielcke
Am Donnerstag, den 06.08.2009, 10:24 +1000 schrieb Jayen:
 Package: grub-pc
 Version: 1.96+20090725-1
 Severity: critical
 Justification: breaks the whole system
 
 
 I know On i386-pc (and amd64), the grub package never updates the installed 
 version of GRUB automatically.  However, this has rendered the system 
 unbootable for me twice now.  I know I'm running something unstable, but 
 users 
 should NOT be expected to know how to fix an unbootable system.  There should 
 at least be a debconf question of whether to run grub-install.
 
 The error I'm getting is Unknown command: initrd similar to #513592 and 
 #497791 (and probably others).
 

Uhm we have already a debconf prompt for running grub-install.
Currently it gets shown when core.img exists and the package is
upgraded. But in SVN we changed it now that it gets shown when there are
no grub-legacy files in /boot/grub and core.img exists, i.e. no check if
the package gets upgraded.


-- 
Felix Zielcke
Proud Debian Maintainer




-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#540125: grub-pc: upgrade renders system unbootable

2009-08-06 Thread Felix Zielcke
Am Donnerstag, den 06.08.2009, 07:57 +0200 schrieb Felix Zielcke:
 Am Donnerstag, den 06.08.2009, 10:24 +1000 schrieb Jayen:
  Package: grub-pc
  Version: 1.96+20090725-1
  Severity: critical
  Justification: breaks the whole system
  
  
  I know On i386-pc (and amd64), the grub package never updates the installed 
  version of GRUB automatically.  However, this has rendered the system 
  unbootable for me twice now.  I know I'm running something unstable, but 
  users 
  should NOT be expected to know how to fix an unbootable system.  There 
  should 
  at least be a debconf question of whether to run grub-install.
  
  The error I'm getting is Unknown command: initrd similar to #513592 and 
  #497791 (and probably others).
  
 
 Uhm we have already a debconf prompt for running grub-install.
 Currently it gets shown when core.img exists and the package is
 upgraded. But in SVN we changed it now that it gets shown when there are
 no grub-legacy files in /boot/grub and core.img exists, i.e. no check if
 the package gets upgraded.

Try dpkg-reconfigure grub-pc
that should show the debconf prompt.
I just tried it now out again with current sid/squeeze version.
debconf prompts are by design shown only once, so maybe it was shown and
you didn't notice this.

-- 
Felix Zielcke
Proud Debian Maintainer




-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#540125: grub-pc: upgrade renders system unbootable

2009-08-05 Thread Jayen
Package: grub-pc
Version: 1.96+20090725-1
Severity: critical
Justification: breaks the whole system


I know On i386-pc (and amd64), the grub package never updates the installed 
version of GRUB automatically.  However, this has rendered the system 
unbootable for me twice now.  I know I'm running something unstable, but users 
should NOT be expected to know how to fix an unbootable system.  There should 
at least be a debconf question of whether to run grub-install.

The error I'm getting is Unknown command: initrd similar to #513592 and 
#497791 (and probably others).

--Jayen

-- Package-specific info:

*** BEGIN /proc/mounts
/dev/disk/by-uuid/ab5d8c7a-80a8-4241-a80b-28496df577d4 / ext3 
rw,noatime,errors=remount-ro,data=ordered 0 0
/dev/disk/by-uuid/ab5d8c7a-80a8-4241-a80b-28496df577d4 /home/jayen/pkg/32/home 
ext3 rw,errors=remount-ro,data=ordered 0 0
/dev/disk/by-uuid/ab5d8c7a-80a8-4241-a80b-28496df577d4 /home/jayen/pkg/32/tmp 
ext3 rw,errors=remount-ro,data=ordered 0 0
*** END /proc/mounts

*** BEGIN /boot/grub/device.map
(hd0)   /dev/sda
*** END /boot/grub/device.map

*** BEGIN /boot/grub/grub.cfg
#
# DO NOT EDIT THIS FILE
#
# It is automatically generated by /usr/sbin/grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
#

### BEGIN /etc/grub.d/00_header ###
set default=0
set timeout=5
set root=(hd0,5)
search --no-floppy --fs-uuid --set ab5d8c7a-80a8-4241-a80b-28496df577d4
if loadfont /usr/share/grub/ascii.pf2 ; then
  set gfxmode=640x480
  insmod gfxterm
  insmod vbe
  if terminal_output.gfxterm ; then true ; else
# For backward compatibility with versions of terminal.mod that don't
# understand terminal_output
terminal gfxterm
  fi
fi
### END /etc/grub.d/00_header ###

### BEGIN /etc/grub.d/05_debian_theme ###
set root=(hd0,5)
search --no-floppy --fs-uuid --set ab5d8c7a-80a8-4241-a80b-28496df577d4
insmod png
if background_image /boot/grub/moreblue-orbit-grub.png ; then
  set color_normal=black/black
  set color_highlight=magenta/black
else
  set menu_color_normal=cyan/blue
  set menu_color_highlight=white/blue
fi
### END /etc/grub.d/05_debian_theme ###

### BEGIN /etc/grub.d/10_linux ###
menuentry Debian GNU/Linux, Linux 2.6.29-2-amd64 {
set root=(hd0,5)
search --no-floppy --fs-uuid --set ab5d8c7a-80a8-4241-a80b-28496df577d4
linux   /boot/vmlinuz-2.6.29-2-amd64 
root=UUID=ab5d8c7a-80a8-4241-a80b-28496df577d4 ro quiet 
initrd  /boot/initrd.img-2.6.29-2-amd64
}
menuentry Debian GNU/Linux, Linux 2.6.29-2-amd64 (recovery mode) {
set root=(hd0,5)
search --no-floppy --fs-uuid --set ab5d8c7a-80a8-4241-a80b-28496df577d4
linux   /boot/vmlinuz-2.6.29-2-amd64 
root=UUID=ab5d8c7a-80a8-4241-a80b-28496df577d4 ro single quiet
initrd  /boot/initrd.img-2.6.29-2-amd64
}
menuentry Debian GNU/Linux, Linux 2.6.26-2-amd64 {
set root=(hd0,5)
search --no-floppy --fs-uuid --set ab5d8c7a-80a8-4241-a80b-28496df577d4
linux   /boot/vmlinuz-2.6.26-2-amd64 
root=UUID=ab5d8c7a-80a8-4241-a80b-28496df577d4 ro quiet 
initrd  /boot/initrd.img-2.6.26-2-amd64
}
menuentry Debian GNU/Linux, Linux 2.6.26-2-amd64 (recovery mode) {
set root=(hd0,5)
search --no-floppy --fs-uuid --set ab5d8c7a-80a8-4241-a80b-28496df577d4
linux   /boot/vmlinuz-2.6.26-2-amd64 
root=UUID=ab5d8c7a-80a8-4241-a80b-28496df577d4 ro single quiet
initrd  /boot/initrd.img-2.6.26-2-amd64
}
### END /etc/grub.d/10_linux ###

### BEGIN /etc/grub.d/30_os-prober ###
### END /etc/grub.d/30_os-prober ###

### BEGIN /etc/grub.d/40_custom ###
# This file is an example on how to add custom entries
### END /etc/grub.d/40_custom ###
*** END /boot/grub/grub.cfg

-- System Information:
Debian Release: squeeze/sid
  APT prefers testing
  APT policy: (980, 'testing'), (960, 'stable'), (900, 'unstable'), (800, 
'experimental'), (500, 'oldstable')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.29-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages grub-pc depends on:
ii  debconf [debconf-2.0]1.5.27  Debian configuration management sy
ii  grub-common  1.96+20090725-1 GRand Unified Bootloader, version 
ii  libc62.9-12  GNU C Library: Shared libraries
ii  ucf  3.0018  Update Configuration File: preserv

grub-pc recommends no packages.

Versions of packages grub-pc suggests:
pn  desktop-base  none (no description available)
ii  genisoimage   9:1.1.9-1  Creates ISO-9660 CD-ROM filesystem
ii  os-prober 1.28   utility to detect other OSes on a 

-- debconf information:
* grub-pc/linux_cmdline:
* grub-pc/chainload_from_menu.lst: false
  grub-pc/install_devices:



-- 
To