Bug#246327: Done and more info?

["Nathan Tallent" <eraxxon@alumni.rice.edu>]

Hi,

I hope I was not misunderstood.  I did not mean that 'menu.lst' currently
contains the literal string "(hd0,*)" and that I'm currently having boot
problems.  (I've already spent a lot of time fixing them!)

I was sending an update about a strange discrepancy between
debian-installer's interpretation of hd0/hd1 and Grub's, at least after
using BIOS to boot from the second drive.  In this context Grub interprets
hd0 to mean disk2.  In contrast, when using d-i, one had better put Grub on
hd1 (disk2) because hd0 (the default)will clobber the MBR of disk0.

I was also sending an update about the default kernel on d-i (2.4.25, I
think) and its recognition of my disks (hda, hde) in contrast to 2.6.5 (sda,
sdb).  Scott had previously asked me to send Grub's 'device.map'.  (These
differences also meant that I had to change Grub's root device for booting
2.6.5.  Since /dev/hde5 was the default root, I encountered a lot of fatal
kernel panics before I figured out root had to be /dev/sdb5.)

However, thanks for the response.

-Nathan.

----- Original Message ----- 
From: "Harald Dunkel" <harald.dunkel@t-online.de>
To: "Nathan Tallent" <eraxxon@alumni.rice.edu>
Cc: "Scott Robinson" <scott@tranzoa.com>
Sent: Tuesday, May 04, 2004 3:00 PM
Subject: Re: Bug#246327: Done and more info?


> I don't have SATA disks. But "(hd0,*)" looks like Grub. Did you
> verify /boot/grub/menu.lst ?
>
>
> Regards
>
> Harri
>