 
| Sender: |
|
| Date: |
Sat, 6 Aug 2005 00:47:22 +0200 |
| MIME-version: |
1.0 |
| Reply-To: |
|
| Content-type: |
multipart/signed; boundary=8GpibOaaTibBMecb;
protocol="application/pgp-signature"; micalg=pgp-sha1 |
| Subject: |
|
| From: |
|
| In-Reply-To: |
|
| Content-disposition: |
inline |
| Comments: |
|
| Parts/Attachments: |
|
|
On Fri, Aug 05, 2005 at 11:20:33PM +0200, Gerald Teschl wrote:
> On Fri, 5 Aug 2005, Axel Thimm wrote:
> >>After a kickstart installation, the box will not boot with a
> >>grub "failed to load stage 2" error.
> >
> >Are you using xfs?
>
> Nope. ext3
Are your ks config relabeling the disk, or are they using a disklabel
possibly created by previous FC/RH installs or Microsoft's fdisk?
I've seen this deterministic behaviour in only two occasions, the FC3
(or was it FC2) CHS bug, and the xfs installs. In both cases the bug
was that when anaconda tries to mount-move the root mountpoint while
sitting on it it would not properly install grub.
Also check the driveorder parameter to the bootloader ks command, in
case your BIOS has a different notion of boot ordering than anaconda.
That's all I can think of. :(
--
Axel.Thimm at ATrpms.net
|
|
|
