Bug#467501: submitter address changed (Stealing this bug ;))

[Jonathan McDowell]

On Tue, Jul 15, 2008 at 02:17:06PM +0200, Robert Millan wrote:
> On Tue, Jul 15, 2008 at 10:29:40AM +0100, Jonathan McDowell wrote:
> > On Mon, Jul 14, 2008 at 04:04:07PM +0200, Robert Millan wrote:
> > > On Mon, Jul 14, 2008 at 01:16:58PM +0100, Jonathan McDowell wrote:
> > > > On Mon, Jul 14, 2008 at 02:11:51PM +0200, Robert Millan wrote:
> > > > > On Mon, Jul 14, 2008 at 09:55:22AM +0100, Jonathan McDowell
> > > > > wrote:
> > > > > > 
> > > > > > It's not fixed, but behaviour appears to be slightly
> > > > > > different.
> > > > > > 
> > > > > > root is getting detected as (hd0,1) while prefix is ending
> > > > > > up set to (hd0,1)(md0)/boot/grub/ and I'm still getting
> > > > > > dropped to the rescue shell.
> > > > > 
> > > > > Which version did you use for that test?
> > > > 
> > > > grub-pc 1.96-20080704-2 (installed from unstable/amd64 this
> > > > morning).
> > > 
> > > Which device did you install grub to?
> > 
> > Um. I don't think I got to specify. I just did "aptitude install
> > grub-pc" and then chose the chainloading option from the existing
> > grub1 install. I didn't get as far as actually replacing the grub1
> > install as chainloading didn't work.
> 
> Then how come you were using 1.96-20080704-2 ?  Did you manualy
> propagate the files to /boot without calling grub-install?

root's .bash_history indicates I did the following before rebooting:

apt-cache show grub2
aptitude install grub-pc
dpkg -i /usr/src/linux-image-2.6.26_meepok.1_amd64.deb 

An md5sum of /boot/grub/boot.img and /usr/lib/grub/i386-pc/boot.img
shows they are identical files. I did not manually copy anything to
/boot/grub. The timestamp on all the files in /boot/grub is 14th July
except for the old grub1 files. dpkg indicates 1.96+20080704-2 is the
version of grub-pc that is installed, so I kinda assumed that's what I
was using.

> If not, you weren't using 1.96-20080704-2.  Either purge grub2
> completely (from /boot too) and start over, or run grub-install on
> your disk.

Running grub-install will wipe the grub1 install and leave me with
grub2, right? Is that more likely to work than the existing chainloading
grub2 from grub1 approach?

I can try an "aptitude purge; rm /boot/grub/*.{mod,img}; aptitude
install grub-pc" tonight and let you know if that's any better.

J.

-- 
Revd. Jonathan McDowell, ULC | Ok ramblers, let's get rambling.