RE: MBR

From: Burke, Thomas G. (tg.burke_at_ngc.com)
Date: 05/18/05

  • Next message: Mike Burger: "RE: MBR"
    Date: Wed, 18 May 2005 07:18:40 -0400
    To: "General Red Hat Linux discussion list" <redhat-list@redhat.com>
    
    

    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@redhat.com [mailto:redhat-list-bounces@redhat.com]On Behalf Of Magee, Fred (MRC)
    Sent: Tuesday, May 17, 2005 6:44 PM
    To: redhat-list@redhat.com
    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@redhat.com?subject=subscribe 
    https://www.redhat.com/mailman/listinfo/redhat-list 
    -- 
    redhat-list mailing list
    unsubscribe mailto:redhat-list-request@redhat.com?subject=unsubscribe
    https://www.redhat.com/mailman/listinfo/redhat-list
    

  • Next message: Mike Burger: "RE: MBR"

    Relevant Pages

    • Re: W4 Installation hangs at first boot-up from HD
      ... Because fdisk does not know how to say anything else. ... the 1024 cylinder limit and that knows little about LVM or LBA addressing. ... Disk Partition Size Disk Name ... As others have already said, to boot beyond you the 1024 cylinder limit, ...
      (comp.os.os2.bugs)
    • Re: Handling boot viruses
      ... boot system with Windows 98SE installed, and if you can infect a system that ... has only Windows 2000 and/or Windows XP with NTFS installed via a methhod ... >>> Boot viruses is where AV software always did a lousy job. ... >> even have a chance at recognizing the results of fdisk /status to ensure ...
      (microsoft.public.security.virus)
    • Re: Need to install Windows 2000 from scratch to HDDs with Debian/Linux
      ... we need the print outputs of fdisk for the ... > Linux partitions with Windows tools. ... > Root and Boot floppy is fine for this, ...
      (comp.os.linux.setup)
    • Re: Boot failure after installation
      ... all sysinstall does is collect the information and run fdisk for you. ... Just boot it up and run it. ... slices here) within the first 1024 cylinders. ... Any partitions you use for filesystems ...
      (freebsd-questions)
    • Re: Boot failure after installation
      ... You just type fdisk devname where devname is the disk device. ... You can only mount a file system. ... Use newfs to create file systems on each of the partitions except swap & c. ... Just boot it up and run it. ...
      (freebsd-questions)