-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Mon, 4 Aug 2003 13:39:54 -0400, Kenneth Goodwin wrote:
> what I am saying is that the MBR may be crafted or rebuild > by anaconda for the two drive setup disk info. It's grub-install/grub that creates stage1 based on the grub.conf created by anaconda. > "Grub-install". which I have not seen admittedly, may be based > on a MAKE environment strategy. IF SO IT ONLY REBUILDS The > MBR if and only if some local disk file has changed that a > dependency has been declared for. It may not check to see > if the hardware environment changed. By cleansing out the > existing config > info via a MAKE CLEAN or CLOBBER sequence , you should force > it to do a fresh > rebuild from scratch on the MBR program which should insert > the new single drive related information. ie SO FAR your > newly written grub > is the same image as the old grub that was on the mbr to > begin with. You can get rid of the generated files like this, preferably after removing slave drive and after booting with boot disk: rm /boot/grub/*1_5 /boot/grub/stage* grub-install --recheck --force-lba /dev/hda Option --force-lba might be interesting. - -- -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQE/Lp7Y0iMVcrivHFQRAoFkAJ0Z9nIV5jhIQgnmpDLuoJrbg43CgQCfcEWT LMknoC8k84oEiBhxdCtWxb0= =y8mK -----END PGP SIGNATURE----- -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED] https://www.redhat.com/mailman/listinfo/redhat-list
