Not signed in (Sign In)

Choose a language

Vanilla 1.1.10 is a product of Lussumo. More Information: Documentation, Community Support.

: Grub flooding on boot (and errors in the installation too...)

Bottom of Page

1 to 14 of 14

  1.  
    •  
      CommentAuthorvazub
    • CommentTimeJun 3rd 2007 edited
     # 1
    Did I already mention that I can't use 014 in VMware Player 2.0 (and the previous version as well)?
    It seems to install properly - no visible errors in the process, but when you reboot it afterwards nothing happens - only black screen is visible.
    I suspect - the grub installation routine is to blame. Can anyone confirm that? (I install it in MBR section of the virual IDE harddrive, that is formatted totally over. Having the partition in Ext3 or Reiser doesn's change anything).
    • CommentAuthorm@cCo
    • CommentTimeJun 4th 2007
     # 2
    Same thing to me. Just an underscore in the upper-left corner of the screen.
    I'm experiencing some problems in a real installation too, with 013 giving a grub error 22 on boot and 014 flooding the screen with "Grub loading stage 1.5", still at boot of course.
    Can't really figure out what could be...
    • CommentAuthorm@cCo
    • CommentTimeJun 5th 2007 edited
     # 3
    I'm trying to install 014-rc1 on my laptop. I run the graphical installation and everything went fine.
    So I came up with two partitions: a 512 MB swap one and a 40 GB ext3 one to use as /. The problem is that when booting the system I got the screen flooded with a "Grub stage 1.5 loading" message (or something similar, I don't remember the exact string).
    I tried to follow the instructions found in the wiki for a manual installation, but when I perform the "setup --prefix=/System/Kernel/Boot/grub (hd0)" command I get an error 2 saying this:

    Running "install /System/Kernel/Boot/grub/stage1 (hd0) (hd0)1+17 p (hd0,1)/System/Kernel/Boot/grub
    /System/Kernel/Boot/grub/menu.l"...failed
    Error 2: Bad file or directory type
    I have to say i had to copy stages files from the original subdir i386-pc to grub for the installer to find them, maybe this could be the reason?

    I really have no idea of what the problem is...
    •  
      CommentAuthorvazub
    • CommentTimeJun 5th 2007
     # 4
    I have merged my similar post with yours in one thread since they both pinpoint the same problem - Grub install routines.
    I've just rechecked the whole installation procedure from the beginning and can confirm that we have a bug here. Auto installation gives nothing - grub is not functioning, and having it installed manually as described in wiki and in your post earlier gives precisely the same error output as you show here.
    Giving it a closer look - it seems that something is wrong with installation scripts, because this
    Posted By: m@cCo/grub/menu.l"...failed
    is a bit wrong. There should be "menu.lst" file, not "menu.l" file.
    Anyway, if no devs appear here soon I'll post the request to the mailing-list to get their answer on this one.
    • CommentAuthorm@cCo
    • CommentTimeJun 5th 2007 edited
     # 5
    Posted By: molfarI have merged my similar post with yours in one thread since they both pinpoint the same problem - Grub install routines.
    I've just rechecked the whole installation procedure from the beginning and can confirm that we have a bug here. Auto installation gives nothing - grub is not functioning, and having it installed manually as described in wiki and in your post earlier gives precisely the same error output as you show here.
    Giving it a closer look - it seems that something is wrong with installation scripts, because this
    Posted By: m@cCo/grub/menu.l"...failed
    is a bit wrong. There should be "menu.lst" file, not "menu.l" file.
    Anyway, if no devs appear here soon I'll post the request to the mailing-list to get their answer on this one.
    The strange thing is just that. There is a menu.lst in the installation dir, but the error reports the name truncated to "menu.l"...

    By the way, I've found this issue which seems to report a similar (if not the same) problem as ours: http://bugs.gobolinux.org/view.php?id=100

    EDIT: while tying to install grub with the grub-install script from the livecd I noticed the following error: grub can't find the stage1 because of a double slash in the path he search in. Looking at the script I can say the problem is likely to be the definition of the search path itself.
    In fact many variables (such as $libdir, $appdir etc) is put together to form the complete path, and it seems there's an extra "/" beetween the libdir and the file to search (something like "/Programs/Grub/0.97/lib/grub//stage1). Maybe this could be part of the problem?
    • CommentAuthorLucas
    • CommentTimeJun 6th 2007
     # 6
    I just took a look into grub-install and that concatenation doesn't have anything to do with the problem; Bash's built-in 'test' command recognizes redundant slashes correctly. Just a question: what kind of hard disk do you have? Does it use a SCSI/SATA interface?

    The following commands should work, assuming that Gobo was installed in /dev/hda1 (hd0,0) and assuming you want to install GRUB in the MBR:

    $ grub
    grub> root (hd0,0)
    grub> setup --prefix=/System/Kernel/Boot/grub (hd0)

    On a side note, it looks like our way of converting SCSI/SATA devices to grub naming scheme was wrong.. Detsch commited a fix for that some weeks ago, and that's going to appear in the new ISO, which I hope to finish today.
    •  
      CommentAuthorvazub
    • CommentTimeJun 6th 2007
     # 7
    Posted By: LucasJust a question: what kind of hard disk do you have? Does it use a SCSI/SATA interface?

    Personally, I install 014rc1 in VMWare Player 2.0 on a virtual HDD (IDE-based, vmx-file created with www.easyvmx.com, easy settings). However, now I recall having the same problem with 013 on my real SATA drive. That was why I switched to virtualization in the first place.

    Posted By: LucasThe following commands should work, assuming that Gobo was installed in /dev/hda1 (hd0,0) and assuming you want to install GRUB in the MBR:

    Precisely these commands produce the error output described earlier.
    • CommentAuthorm@cCo
    • CommentTimeJun 6th 2007 edited
     # 8
    Posted By: LucasI just took a look into grub-install and that concatenation doesn't have anything to do with the problem; Bash's built-in 'test' command recognizes redundant slashes correctly. Just a question: what kind of hard disk do you have? Does it use a SCSI/SATA interface?
    Nope, it's a simple 40GB IDE. An IBM 2.5" ultra-ATA/100 hdd to be exact.

    Posted By: LucasThe following commands should work, assuming that Gobo was installed in /dev/hda1 (hd0,0) and assuming you want to install GRUB in the MBR:

    $ grub
    grub> root (hd0,0)
    grub> setup --prefix=/System/Kernel/Boot/grub (hd0)

    On a side note, it looks like our way of converting SCSI/SATA devices to grub naming scheme was wrong.. Detsch commited a fix for that some weeks ago, and that's going to appear in the new ISO, which I hope to finish today.
    As molfar said, we already tried the "right way" :D
    Just another thing, as a little suggestion/hope, why not create a /boot symlink pointing at /System/Kernel/Boot, so that programs requiring it would (in theory) work without changes?

    In the meanwhile, let's wait for rc2 :D
    • CommentAuthorcalica
    • CommentTimeJun 7th 2007
     # 9
    Just adding a "me too". Installing on vmware server results on an empty screen on boot.
    • CommentAuthorm@cCo
    • CommentTimeJun 15th 2007
     # 10
    Any news on this front?
    • CommentAuthorm@cCo
    • CommentTimeJun 19th 2007 edited
     # 11
    Just a piece of news, I've succeded to install grub this way:

    - create a symlink named boot in / pointing at /System/Kernel
    - install grub the conventional way, i.e. root (hd*,*), setup (hd*)

    The fact is that I've now problems in adding users via the useradd command. It seems such as the installer didn't properly add my user, and if I try to add it with "useradd username" I get an error similar to: "Unknown GID 1000" followed by "Unable to create home/username/".
    Btw, the group username:1000 exists indeed...

    EDIT: the useradd problem seems to happen in the 014 release only. I've now got to install the 013 version successfully.
    •  
      CommentAuthorvazub
    • CommentTimeJun 23rd 2007 edited
     # 12
    Posted By: m@cCoJust a piece of news, I've succeded to install grub this way:

    Yes, I can confirm that it works this way*. However, it is mostly a hack and doesn't solve the issue in the long run.
    I don't know if there was such a bug in previous distro releases - it is either Gobo- or grub-inherent (maybe something was changed in the version 014rc1 is using, for example some hard-coded link was introduced in the middle of the installation routine).
    If nothing helps, there might still be an option to have /boot symlink in the distro and have it gobohidden, as m@cCo proposed.

    *edit: I didn't install grub with the installer. Instead I mounted hda1 partition, created the aforementioned symlink - "ln -s /System/Kernel/Boot /Mount/GoboLinux/boot", and installed grub manually without a prefix - "root (hd0,0)", "setup (hd0)".
    Got the output:

    Running "install /boot/grub/stage1 (hd0) (hd0)1+21 p (hd0,0)/boot/grub/stage2
    /boot/grub/menu.lst"... succeeded

    Notice, that now it writes the full string for stage2 and there is no concatenation in"menu.lst" as it was in error output before. Could it be that there was some bug in stage2 installation?

    Also, after rebooting, there is no user present that I created with the installer previously. Only "root". Checked twice. No idea what happened.
    • CommentAuthorm@cCo
    • CommentTimeJun 24th 2007
     # 13
    Posted By: vazub
    Posted By: m@cCoJust a piece of news, I've succeded to install grub this way:

    Yes, I can confirm that it works this way*. However, it is mostly a hack and doesn't solve the issue in the long run.
    I don't know if there was such a bug in previous distro releases - it is either Gobo- or grub-inherent (maybe something was changed in the version 014rc1 is using, for example some hard-coded link was introduced in the middle of the installation routine).
    If nothing helps, there might still be an option to have /boot symlink in the distro and have it gobohidden, asm@cCoproposed.

    *edit:I didn't install grub with the installer. Instead I mounted hda1 partition, created the aforementioned symlink - "ln -s /System/Kernel/Boot /Mount/GoboLinux/boot", and installed grub manually without a prefix - "root (hd0,0)", "setup (hd0)".
    Got the output:

    Running "install /boot/grub/stage1 (hd0) (hd0)1+21 p (hd0,0)/boot/grub/stage2
    /boot/grub/menu.lst"... succeeded

    Notice, that now it writes the full string for stage2 and there is no concatenation in"menu.lst" as it was in error output before. Could it be that there was some bug in stage2 installation?

    Also, after rebooting, there is no user present that I created with the installer previously. Only "root". Checked twice. No idea what happened.
    It seems that we are in front of a real mistery :D
    Here follows my procedure to get grub installed on the mbr with Gobolinux 013:

    1. Perform a normal installation, but don't install the bootloader

    2. When the installer has done, open a console and launch grub, then perform a grub installation as shown in the wiki, so type:

      root (hd*,*)
      setup --prefix=/System/Kernel/Boot/grub (hd*)
      quit
    3. Edit the "menu.lst" file if you want, then reboot

    And that's all. No users mess nor grub errors.
    I must say I haven't tried it with the 014 iso yet...
    •  
      CommentAuthorvazub
    • CommentTimeJun 25th 2007
     # 14
    so it seems something went wrong with 014rc1. either it was updated version of grub, or some changes in Installer, or other packages or everything at once. hope that devs find out what is wrong..

1 to 14 of 14

  1.