Bug#236093: grub: Boot 'stages' not installed correctly.

Paul Schulz paul@mawsonlakes.org, 236093@bugs.debian.org
Sat, 17 Apr 2004 15:04:15 +0930


--=-pBHxAO1Cog3z+cRSpprY
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

Micah,=20

Thank you for replying.  I believe that this specific problem lies in
the way that I am (ad)using grubs 'device.map' file.  So, the bug is
probably invalid (and I'm happy for it to go away).

There is indeed a 'menu.lst' and a 'device.map' file in the=20
'grub config' (It is the entire contents of the /boot directory.)
and it get's copied to the target machine.

The previous version of GRUB (0.91-2) worked using the method I
described, which is why I logged the bug when this behaviour changed
(ie. something broke between this and 0.93+cvs20031021-8).

I will use the 'grub-install' script with the --recheck option
(maybe even deleting the 'device.map' file before using it).

[BACKBROUND: The installer was 'inherited' was a previous employee,=20
and the aim is to bring it as soon as posible into line with the
current Debian installer so that more sensible debugging/testing
can take place, and benefit everyone.]   =20

Cheers,
Paul


On Sat, 2004-04-17 at 10:08, Micah Anderson wrote:
> There is some crucial information that needs to be provided to
> understand if this is indeed a critical bug or if you were simply not
> installing grub properly. Please see comments in-line below:
>=20
> On Thu, 04 Mar 2004, Paul Schulz wrote:
>=20
> > Package: grub
> > Version: 0.93+cvs20031021-8
> > Severity: critical
> > Justification: breaks the whole system
> >=20
> > After a installation[1], on reboot the system does not boot.
> > This is on a freshly configured disk, parition and filesystem.
>=20
> It should be explicitly noted here that the user did not install using
> a tradtional installation method, but is doing his own thing.
>=20
> >=20
> > It looks like the BIOS passes control to the GRUB stage1, a couple
> > of blank lines are printed onto the screen, and the system hangs.
> >=20
> > An older version of GRUB can be used to fix the system, after
> > booting from floppy.
> >=20
> > [1] - The install process was:
> >     boot from cdrom (custom)
> >     partition the disk=20
> >     format the partition
> >     mount the filesystem
> >     untar a root filesystem (including grub config)
>=20
> This "grub config" is crucial information, if it includes a device.map
> from another system that does not correspond to the system that you
> are trying to install to, you will have this problem because your
> device.map does not match up and this would be why you would need to
> recreate it.=3D20
>=20
> Can you provide more details of what is included in this "grub
> config"? Is it just a menu.lst? Is there a device.map included?
>=20
> >     chroot into filesystem and run grub.
>=20
> I assume when you say "run grub" you are *not* running grub-install,
> but instead running grub the way you detailed in your followup message
> (run grub, specify the root, run setup).=3D20
>=20
> The documented procedure is to run grub-install because this will
> create a necessary device.map file if there is not one (ie. you don't
> provide it with your "grub config"). If you did not provide a
> device.map in your "grub config" and you did not run grub-install then
> the device.map would not be valid.
>=20
>=20
> >  =20
> >   This previously worked with an older version of the 'stable' GRUB
> >   package.
>=20
> On other systems where this worked were you using ide drives? Have you
> always used scsi drives in the exact same configuration? If not, your
> device.map file, if you are providing this with your "grub config"
> will not match up and grub will think that hd(0) is possibly /dev/hda
> instead of /dev/sda which you are using in this scenario.
>=20
> micah

--=-pBHxAO1Cog3z+cRSpprY
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)

iD8DBQBAgMHWR7GbvP4HDg8RAqGJAKCd2HwLBvIMnC4rt80qkaLjQq3WqACfZ0RX
MXAf9iJkM3ebvaVsN0tdJ10=
=I+z1
-----END PGP SIGNATURE-----

--=-pBHxAO1Cog3z+cRSpprY--