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

[Micah Anderson]

--61jdw2sOBCFtR2d/
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

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:

On Thu, 04 Mar 2004, Paul Schulz wrote:

> 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.

It should be explicitly noted here that the user did not install using
a tradtional installation method, but is doing his own thing.

>=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)

This "grub config" is crucial information, if it includes a device.map
=66rom 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

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?

>     chroot into filesystem and run grub.

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

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
>   This previously worked with an older version of the 'stable' GRUB
>   package.

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.

micah

--61jdw2sOBCFtR2d/
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline

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

iD8DBQFAgHx79n4qXRzy1ioRAuoDAJ40tx6i4/g4l/HysMX0xGM9duTlZgCfWTRX
JOHXIx7mMFNg/VdRoajXSbE=
=liql
-----END PGP SIGNATURE-----

--61jdw2sOBCFtR2d/--