doing an fdisk /mbr shouldn't hurt you physically, in fact it is quite useful for when the master boot record gets corrupted. Unfortunately, it wipes out lilo in the boot record, so you can't boot without a disk. If you have a disk that will allow you to boot to the normal OS & have everything mounted, do the following: 1) fdisk /mbr 2) reboot into single user mode 3) ensure /etc is mounted 4) cd to /etc 5) ensure lilo.conf is as it should be 6) run lilo - you should see a message saying something like "added XXX" 7) reboot - you should be good to hook -----Original Message----- From: redhat-list-bounces@xxxxxxxxxx [mailto:redhat-list-bounces@xxxxxxxxxx]On Behalf Of Magee, Fred (MRC) Sent: Tuesday, May 17, 2005 6:44 PM To: redhat-list@xxxxxxxxxx Subject: MBR A co-worker swapped SCSI RAID controllers on our system running RHEL 3.0 and lost the partition table of our boot disk. He was able to recover it (apparently) using gpart but the system will not boot. I can boot into rescue mode using a cd and mount all partitions and they all appear to be ok. Fsck marks them all as ok. I have run grub to be sure /boot was ok and grub-install /dev/sda to rebuild the MBR but we still get: No Operating System found when we try to boot the system. Isn't grub-install supposed to rebuild the MBR? Do I need (dare) to run fdisk /mbr? Any ideas will be gratefully appreciated. Fred -- redhat-list mailing list unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=subscribe https://www.redhat.com/mailman/listinfo/redhat-list -- redhat-list mailing list unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subjecthttps://www.redhat.com/mailman/listinfo/redhat-list
