Bug#512787: upgrade makes system unbootable

2009-01-28 Thread David Riebenbauer 
* dann frazier da...@debian.org [2009-01-28 12:49]:
 Package: grub-pc
 Version: 1.96+20080724-14
 Severity: grave
 
 hey,
  After a recent upgrade, my laptop became unbootable. I don't have
 local access to the machine rigth now, so unfortunately the preboot
 information will have to come from memory.
 
 According to dpkg.log, the upgrade was this one:
  2009-01-20 22:37:55 upgrade grub-pc 1.96+20080724-12 1.96+20080724-14
 
 At boot time, grub complains that 'initrd' is an invalid option and
 refuses to boot.
 
 My boot entry looks like this:
 set root=(hd0,1)
 search --fs-uuid --set e7bf09bb-8d63-4bbb-84d8-4ada743f643f
 linux   /boot/vmlinuz-2.6.26-1-686 
 root=UUID=e7bf09bb-8d63-4bbb-84d8-4ada743f643f ro  
 initrd  /boot/initrd.img-2.6.26-1-686
 
 I found through experimentation that deleting the first two lines
 allows my system to boot again.

Just FYI, I got the exact same problem. Well, except that I got local
access sto the machine. But the error message is the same, and
removing the se3arch line makes it work again.

However, running, grub-install and update-grub made things work again.

Regards,
David



-- 
David Riebenbauer
Jabber: davr...@jabber.ccc.de - ICQ: 322056002 
http://liegesta.at



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

Bug#512787: upgrade makes system unbootable

2009-01-27 Thread dann frazier 
On Sun, Jan 25, 2009 at 11:39:44PM +0100, Robert Millan wrote:
 On Fri, Jan 23, 2009 at 11:05:16AM -0700, dann frazier wrote:
  
  My boot entry looks like this:
  set root=(hd0,1)
  search --fs-uuid --set e7bf09bb-8d63-4bbb-84d8-4ada743f643f
  linux   /boot/vmlinuz-2.6.26-1-686 
  root=UUID=e7bf09bb-8d63-4bbb-84d8-4ada743f643f ro  
  initrd  /boot/initrd.img-2.6.26-1-686
  
  I found through experimentation that deleting the first two lines
  allows my system to boot again.
 
 Please run grub-emu and check if the following command:
 
   search --fs-uuid --set e7bf09bb-8d63-4bbb-84d8-4ada743f643f
 
 causes any oddity (e.g. segfault).

No segfault, but:
BEGIN CUTPASTE
  Booting a command list

error: unknown command `initrd'
   Press any key to continue...

END CUTPASTE

 Also, try unsetting the root variable, run the search command, and
 see if it finds the correct value for it.

Looks right to me:

grub set root=
grub echo $root

grub search --fs-uuid --set e7bf09bb-8d63-4bbb-84d8-4ada743f643f
grub echo $root
hd0,1

-- 
dann frazier




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

Bug#512787: upgrade makes system unbootable

2009-01-26 Thread Michael Schuerig 

The same happened on my notebook (Dell D820) after the recent upgrade 
from 1.96+20080724-12 to 1.96+20080724-14.

set root=(hd0,1)
search --fs-uuid --set 546d6205-7424-4a37-86e5-d1e355c3d2ba
menuentry Debian GNU/Linux, linux 2.6.26-1-686 {
linux   /boot/vmlinuz-2.6.26-1-686 
root=UUID=546d6205-7424-4a37-86e5-d1e355c3d2ba ro
initrd  /boot/initrd.img-2.6.26-1-686
}

I checked in grub-emu (...-14!) and

  search --fs-uuid --set 546d6205-7424-4a37-86e5-d1e355c3d2ba

didn't produce any output at all. Whatever it did, I got another prompt 
afterwards.

Michael



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

Bug#512787: upgrade makes system unbootable

2009-01-26 Thread Felix Zielcke 
Am Montag, den 26.01.2009, 10:38 +0100 schrieb Michael Schuerig:

 I checked in grub-emu (...-14!) and
 
   search --fs-uuid --set 546d6205-7424-4a37-86e5-d1e355c3d2ba
 
 didn't produce any output at all. Whatever it did, I got another prompt 
 afterwards.
 

With `--set' argument it just sets the root variable to the device and
doestn't print out any output.
With `set' command you can check the value of the root variable.

-- 
Felix Zielcke




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

Bug#512787: upgrade makes system unbootable

2009-01-25 Thread Robert Millan 
On Fri, Jan 23, 2009 at 11:05:16AM -0700, dann frazier wrote:
 
 My boot entry looks like this:
 set root=(hd0,1)
 search --fs-uuid --set e7bf09bb-8d63-4bbb-84d8-4ada743f643f
 linux   /boot/vmlinuz-2.6.26-1-686 
 root=UUID=e7bf09bb-8d63-4bbb-84d8-4ada743f643f ro  
 initrd  /boot/initrd.img-2.6.26-1-686
 
 I found through experimentation that deleting the first two lines
 allows my system to boot again.

Please run grub-emu and check if the following command:

  search --fs-uuid --set e7bf09bb-8d63-4bbb-84d8-4ada743f643f

causes any oddity (e.g. segfault).  Also, try unsetting the root variable,
run the search command, and see if it finds the correct value for it.

-- 
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#512787: upgrade makes system unbootable

2009-01-23 Thread dann frazier 
Package: grub-pc
Version: 1.96+20080724-14
Severity: grave

hey,
 After a recent upgrade, my laptop became unbootable. I don't have
local access to the machine rigth now, so unfortunately the preboot
information will have to come from memory.

According to dpkg.log, the upgrade was this one:
 2009-01-20 22:37:55 upgrade grub-pc 1.96+20080724-12 1.96+20080724-14

At boot time, grub complains that 'initrd' is an invalid option and
refuses to boot.

My boot entry looks like this:
set root=(hd0,1)
search --fs-uuid --set e7bf09bb-8d63-4bbb-84d8-4ada743f643f
linux   /boot/vmlinuz-2.6.26-1-686 
root=UUID=e7bf09bb-8d63-4bbb-84d8-4ada743f643f ro  
initrd  /boot/initrd.img-2.6.26-1-686

I found through experimentation that deleting the first two lines
allows my system to boot again. There are obviously more experiments I
could do - see if just removing one of the two lines fixes things, and
try downgrading to see if it makes my system bootable again. I haven't
had time to do these tests (and probably won't until next week), but I
wanted to get a bug filed in the meantime.

I'll attach my grub.cfg for reference.
-- 
dann frazier

#
# DO NOT EDIT THIS FILE
#
# It is automatically generated by /usr/sbin/update-grub 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,1)
search --fs-uuid --set e7bf09bb-8d63-4bbb-84d8-4ada743f643f
if font /usr/share/grub/ascii.pff ; then
  set gfxmode=640x480
  insmod gfxterm
  insmod vbe
  terminal gfxterm
fi
### END /etc/grub.d/00_header ###

### BEGIN /etc/grub.d/05_debian_theme ###
set menu_color_normal=cyan/blue
set menu_color_highlight=white/blue
### END /etc/grub.d/05_debian_theme ###

### BEGIN /etc/grub.d/10_hurd ###
### END /etc/grub.d/10_hurd ###

### BEGIN /etc/grub.d/10_linux ###
menuentry Debian GNU/Linux, linux 2.6.26-1-686 {
set root=(hd0,1)
search --fs-uuid --set e7bf09bb-8d63-4bbb-84d8-4ada743f643f
linux   /boot/vmlinuz-2.6.26-1-686 
root=UUID=e7bf09bb-8d63-4bbb-84d8-4ada743f643f ro  
initrd  /boot/initrd.img-2.6.26-1-686
}
menuentry Debian GNU/Linux, linux 2.6.26-1-686 (single-user mode) {
set root=(hd0,1)
search --fs-uuid --set e7bf09bb-8d63-4bbb-84d8-4ada743f643f
linux   /boot/vmlinuz-2.6.26-1-686 
root=UUID=e7bf09bb-8d63-4bbb-84d8-4ada743f643f ro single 
initrd  /boot/initrd.img-2.6.26-1-686
}
### 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 ###