>>>>> "Kevin" == Kevin Freeman <kfreem02@xxxxxxxxxxx> writes:
>> From http://myrddin.org/howto/debian-grub.php :
Kevin> mkfs /dev/fd0 mount /media/floppy/ #or /mnt/floppy if FC2
Kevin> mkdir -p /media/floppy/boot/grub
Kevin> cp /boot/grub/stage1 /boot/grub/stage2 /boot/grub/menu.lst
Kevin> /media/floppy/boot/grub/ umount /media/floppy/
Kevin> /sbin/grub --batch --device-map=/dev/null <<EOT device
Kevin> (fd0) /dev/fd0 root (fd0) setup (fd0) quit EOT
Kevin> In theory that gives you a grub floppy which includes a
Kevin> working menu. In my testing, it produces a floppy that
Kevin> boots to a grub command prompt. In any case, you can now
Kevin> attempt to boot the sick machine.
Thanks a million, Kevin. You're a star!
Kevin> Assuming the FC boot partition on /dev/hda1, type root
Kevin> (hd0,0), followed by configfile /grub/grub.conf. This will
Kevin> load the "lost" boot menu.
Assumptions not valid. But with some trial and error, I found the
following commands sufficient to attempt a boot:
root (hd0,4)
configfile /etc/grub.conf
(Disk has FC1 on it, if that is relevanet).
This then attempts to boot a kernel (I'm not presented with a grub
menu - I guess there's only one kernel present).
But fails with a message something like:
Disk (hd1,4) not found.
There used to be ANOTHER hard disk in this machine, before that one
proved to be unusable, so I'm guessing that this hard disk must have
been the primary IDE slave (is that what hd1 is?).
Can I just re-cable the disk as a slave, or better, is there someway
of changing the grub.conf on the disk to specify hd0 instead of hd1
(I'm guessing that there is where the problem is)?
--
Colin Paul Adams
Preston Lancashire
