new install, GRUB issues - Suse

This is a discussion on new install, GRUB issues - Suse ; I tried installing OpenSUSE 11.0 last night. It got to the point at the end of the install where it was setting up the bootloader, and started giving errors. Unfortunately, since I'm running off the Vista install on the same ...

+ Reply to Thread
Results 1 to 8 of 8

Thread: new install, GRUB issues

  1. new install, GRUB issues



    I tried installing OpenSUSE 11.0 last night. It got to the point at the end
    of the install where it was setting up the bootloader, and started giving
    errors. Unfortunately, since I'm running off the Vista install on the same
    box, I can't provide the initial error messages. I'll try the install again
    once I'm done posting this, and I'll write them down.

    In the meantime, I *can* provide some preliminaty stuff about the hard
    drives and system...

    -- Asus P5B motherboard
    -- Seagate 500GB SATA hard drive as /dev/sda
    -- Western Digital 160GB SATA as /dev/sdb

    Windows Vista is installed on the majority of dev/sda. I have a 6GB
    partition at the end of the same drive for Linux swap space.

    /dev/sdb is partitioned as:

    /boot 125MB
    / ~30GB
    /usr 15GB
    /opt ~50GB
    /home 39GB

    there's also a 10GB partition for the Windows swap file on this drive.

    I want GRUB to install its boot-time files into the MBR of /dev/sda, as was
    done on /dev/hda on my other box. For some reason, it's not doing it. My
    Windows boot setup has remained untouched, so I can boot into that OS fine.

    I tried running the repair program off the OpenSUSE install DVD, and it told
    me it fixed some things, and installed GRUB into the MBR of /dev/sda, but
    when I went to reboot, I was told that there were errors during
    installation. It didn't tell me what the errors were.

    I'm going to try reinstalling, in case I missed something... If I still get
    the same problem, is there any way of forcing GRUB to put itself into the
    MBR of my first disc, like it's supposed to do?

    ** Posted from http://www.teranews.com **

  2. Re: new install, GRUB issues

    Paul in Toronto wrote:

    > I want GRUB to install its boot-time files into the MBR of /dev/sda, as
    > was
    > done on /dev/hda on my other box. For some reason, it's not doing it. My
    > Windows boot setup has remained untouched, so I can boot into that OS
    > fine.


    Latest update... It wasn't BIOS anti-virus protection. I reinstalled, and
    got a message saying that my hard drive was labelled as "GET" or something
    like that, and that erasing the partition table and starting from scratch
    would fix it. So I followed the advice (didn't touch the windows disc at
    all), and the Linux system booted after the installation.

    However... Windows Vista does not boot. When I pick that OS in the GRUB
    menu, I get the following:

    rootnoverify (hda2,0)
    chainloader (hd0,0)+1

    And it just sits there serenely.

    Any thoughts on how to fix?
    ** Posted from http://www.teranews.com **

  3. Re: new install, GRUB issues

    Paul in Toronto wrote:
    > I want GRUB to install its boot-time files into the MBR of /dev/sda, as was
    > done on /dev/hda on my other box. For some reason, it's not doing it. My
    > Windows boot setup has remained untouched, so I can boot into that OS fine.


    Perhaps your MBR is protected. Turn off the 'virus protection' in your
    BIOS.

    houghi
    --
    How do you ask a man to be the last man to die in Iraq?
    How do you ask a man to be the last man to die for a mistake?

  4. Re: new install, GRUB issues

    Paul in Toronto wrote:
    > rootnoverify (hda2,0)


    That syntax is wholly wrong, grub syntax should be something like
    rootnoverify (hd0,0)
    (for sda1, hd0 means "first harddisk", 0 means "first partition")
    There is NO difference between IDE, S-ATA and/or SCSI disks in
    grub, they all are hd. And all the numbers start at
    0, so "partion 1" becomes ,0, partition 4 ",3", etc.
    Just as in Linux "primary partions" are the first 4, so extended
    ones start at ,4, etc.

    > chainloader (hd0,0)+1


    You do have the (hd0,0) part good here but if you already set it
    in the root statement before, it is default, so just "+1" will be
    just as well.
    --
    ************************************************** *****************
    ** Eef Hartman, Delft University of Technology, dept. SSC/ICT **
    ** e-mail: E.J.M.Hartman@tudelft.nl, fax: +31-15-278 7295 **
    ** snail-mail: P.O. Box 5031, 2600 GA Delft, The Netherlands **
    ************************************************** *****************

  5. Re: new install, GRUB issues

    On Sep 2, 9:11*am, Eef Hartman wrote:
    > Paul in Toronto wrote:
    >
    > > rootnoverify (hda2,0)

    >
    > That syntax is wholly wrong, grub syntax should be something like
    > * *rootnoverify (hd0,0)
    > (for sda1, hd0 means "first harddisk", 0 means "first partition")
    > There is NO difference between IDE, S-ATA and/or SCSI disks in
    > grub, they all are hd. And all the numbers start at
    > 0, so "partion 1" becomes ,0, partition 4 ",3", etc.
    > Just as in Linux "primary partions" are the first 4, so extended
    > ones start at ,4, etc.
    >
    > > chainloader (hd0,0)+1

    >
    > You do have the (hd0,0) part good here but if you already set it
    > in the root statement before, it is default, so just "+1" will be
    > just as well.


    I'll look into that when I get home this evening. I didn't actually
    go and edit the GRUB configs manually because I assumed (based on past
    experience with SUSE installs) that it'd get set up properly
    automatically. I've taken a closer look at the information I posted,
    and what you're saying makes sense. It should be pointing to hd0 if
    my first drive is sda1.

    Thanks for pointing that out. I'll let you know how it works.

  6. Re: new install, GRUB issues

    swampyfern@hotmail.com wrote:
    > I'll look into that when I get home this evening. I didn't actually
    > go and edit the GRUB configs manually because I assumed (based on past
    > experience with SUSE installs) that it'd get set up properly
    > automatically. I've taken a closer look at the information I posted,
    > and what you're saying makes sense. It should be pointing to hd0 if
    > my first drive is sda1.


    sda1 is not a hard disk. sda is. sda1 is the first partition on the
    sda disk.

  7. Re: new install, GRUB issues

    On Sep 2, 4:03*pm, Nikos Chantziaras wrote:
    > swampyf...@hotmail.com wrote:
    > > I'll look into that when I get home this evening. *I didn't actually
    > > go and edit the GRUB configs manually because I assumed (based on past
    > > experience with SUSE installs) that it'd get set up properly
    > > automatically. *I've taken a closer look at the information I posted,
    > > and what you're saying makes sense. *It should be pointing to hd0 if
    > > my first drive is sda1.

    >
    > sda1 is not a hard disk. *sda is. *sda1 is the first partition on the
    > sda disk.


    Yes, yes. Semantics. I put the 1 in there by mistake. Force of
    habit, I guess.

  8. Re: new install, GRUB issues

    Eef Hartman wrote:

    > Paul in Toronto wrote:
    >> rootnoverify (hda2,0)

    >
    > That syntax is wholly wrong, grub syntax should be something like
    > rootnoverify (hd0,0)


    Well... That worked. I changed it to (hd0,0) and Windows booted. Thank
    you very much.

    Although I should have spotted that myself...
    ** Posted from http://www.teranews.com **

+ Reply to Thread