Re: grub doesn't work

From: m.marien (mm)
Date: 10/26/04

  • Next message: Paul Lutus: "Re: yenta_socket issue" 
    Date: Mon, 25 Oct 2004 21:56:56 -0600

    "Mike" <someone@your.house> wrote in message
    news:d4Kdnaegod6JI-DcRVn-qQ@midco.net...
    >
    > "m.marien" <mm AT RiverCityCanada DOT com> wrote in message
    > news:10nr0nhluct4i23@corp.supernews.com...
    >>
    >> "Mike" <someone@your.house> wrote in message
    >> news:kO-dncxEet9azODcRVn-ug@midco.net...
    >> >I installed WinXP, Slackware, and Fedora Core. I installed Fedora last
    >> > hoping that grub would install and detect everything. The grub.conf
    >> > file
    >> > appears to have everything in it, but I have a bigger problem. When the
    >> > computer starts up and the bios finishes the last thing that displays
    > is:
    >> >
    >> > GRUB
    >> >
    >> > The computer stops there. alt+ctrl+del doesn't work, I have to turn it
    >> > off.
    >> > I'm using a Promise TX2000 raid adapter in a Raid3,0 array (3 drives)
    >> > Linux
    >> > detected the drives as hde, hdf, and hdg. Windows is on hde, Fedora on
    > hdf
    >> > and Slackware on hdg.
    >> >
    >> > How do I manually install Grub or LiLo?
    >> >
    >> > TIA
    >> > Mike
    >> >
    >>
    >> There are a couple of ways to reinstall GRUB. One is with the
    >> /sbin/grub-install script. Just specify which device is your boot device
    >> or --help for options. The other is manually. Type /sbin/grub at the
    > command
    >> line to enter the grub command line. Specify the root directory partition
    >> and then use setup to install the files:
    >>
    >> [root]#grub
    >> grub> root (hd1,0)
    >> grub> setup (hd0)
    >> grub> quit
    >>
    >> This specifies that the first partition on drive 2 (/dev/hdf1 in your
    > case)
    >> is where the root is. And then installs grub to the MBR of the first
    >> drive
    >> (/dev/hde). Grub starts counting the drives from zero.
    >>
    >> If you installed GRUB to the Fedora partition, then setup (hd1,0) would
    >> be
    >> the command to use.
    >>
    >> The problem may also be the RAID is confusing GRUB.
    >>
    >>
    >
    > If the RAID is confusing GRUB, then WHAT?
    >
    >

    Then you probably can't use it for booting your system without some
    tweaking. That's maybe why it didn't install properly. You're at the point
    of installing so losing the installs shouldn't be a big problem.

  • Next message: Paul Lutus: "Re: yenta_socket issue"

    Relevant Pages

    • Re: Grub Installation Mini How-To
      ... "rootnoverify" is for when you point grub at a part of a disk that is ... >> map ... It's like with the "map" command, ... it doesn't actually install stage1_5 unless it's ...
      (comp.os.linux.setup)
    • Re: remove partaion
      ... The most interesting hurdle will be what the Master Boot Record ... thus kill GRUB. ... I would copy your MBR and first 63 sectors (see the MBR Copy Appendix ... GUI or command line commands to accomplish that. ...
      (Fedora)
    • Re: Serious GRUB booting problem after install Ubuntu 9.10beta for testing it.
      ... partition, and it listed the 2.5gb as "free space". ... Anyway, like the OP, I get Error 17 when I boot with the external turned on, ... and am given a grub rescue> prompt. ... Any idea why the root command isn't working for me, and what I can do to ...
      (Ubuntu)
    • Re: F8/F9 Multiboot question
      ... > What is the command for installing the "MBR" and grub into each ... The grub command to enter a GRUB shell. ... Filesystem type is ext2fs, partition type 0x83 ...
      (Fedora)
    • Re: grub menu oddity
      ... >> I have a multi-boot system using grub installed in the mbr of my ... It seems like every time my motherboard bios updates its ... if I drop to a command line and manually execute the ... >> command is exactly the same as the root command in menu.lst. ...
      (comp.os.linux.setup)