URL:
<http://savannah.gnu.org/support/?108055>
Summary: GRUB2 onto Partittions
Project: Savannah Administration
Submitted by: None
Submitted on: vie 11 may 2012 12:08:24 UTC
Category: None
Priority: 5 - Normal
Severity: 1 - Wish
Status: None
Assigned to: None
Originator Email: z666zz6...@terra.es
Operating System: None
Open/Closed: Open
Discussion Lock: Any
_______________________________________________________
Details:
I am getting really mad trying to install Grub2.00_Beta3 (the one included on
SystemRescueCD.iso version 2.6.0 onto parttitions.
Let me explain:
-I install one Grub2.00Beta3 onto MBR and on /dev/sda9 (the /boot dedicated
parttition) and it works perfect
-I want another Grub2.00Beta3 onto /dev/sda1 and another one onto /dev/sda2,
another one onto /dev/sda7, etc...
The MBR one will show a menu (under my own control, i manually edit
/boot/grub2/grub.cfg file), this one works perfect.
On this menu i can select where to boot from (in terms of parttitions... doing
chainloader)
I want for some options that a differnt Grug, Lilo or whatever the System
installed on such parttition uses to be shown... for testing i want
Grub2.00_Beta3
I mean this:
-BIOS read MBR
-MBR has Grub2.00_Beta3 and such reads from EXT4 parttition on /dev/sda9 the
files, menu, etc..
-A menu i designed (by manually editing /boot/grub2/grub.cfg) is shown
-I select one option
-A chainload must let load another thing (Windows, Linux, etc... also another
Grub2.00_Beta3) from the parttition.
The case is that if for such "Grub" onto parttitions i use Grub Legacy it
works perfect, but all times i try with Grub2 i fails!!
The failure occurs at Boot time... the first Grub2 shows the menu, i select
the option to load the second Grub2 (the one on a parttition like /dev/sda#)
and the screen goes black with text: "GRUB _" on it and hangs!!!
What can i do to get Grub2 get installed onto a parttition?
Imagine i do not want to touch MBR for any good reason, how i get Grub2
installed onto a parttition?
I know how to chainload on MBR Grub2 to this:
-MBR (like doing a re-load)
-Any PBR (Parttition Boot Record)
-SystemRecueCD.iso (loop device) stored on /boot dedicated parttition where
MBR Grub2 files are
-Any Windows (including Windows7)
-Another Grub Legacy on another parttition (same as for PBR)
-etc
The problem while booting is that MBR Grub2 get to load PBR boot record, but
hangs after that.
For tests i am using SystemRescueCD.iso version 2.6.0 that cames with
Grub2.00Beta3, since with SystemRescueCD.iso version 2.5.0 it cames with
Grub2.00Beta2 and such one do not install Grub2 onto parttition, instead it
installs GRUB version 1.99 and so it works perfect... but with Grub2.00Beta3
the Grub2 get installed onto the parttition but when telling onto menu to
chainload it, fails!!!
All parttitions for testing are formatted onto EXT4 and must be!!!
Grub2.00Beta3 on MBR and /boot (/dev/sda9 EXT4 formatted) dedicated parttition
boots perfect because Grub2 uses MBR, but i want Grub2 onto a partition not on
MBR.
Maybe am i doing something wrong by using chainloader? May i use another
method to chain to that other Grub2? or is just that Grub2.00Beta3 can not be
installed onto a parttition!!!
I am getting really mad to know what i am doing wrong!!!
Thanks in advande for any help!!!
P.D.: I also have tested to run grub2-install with --force and --no-floppy
with no luck!!!
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/support/?108055>
_______________________________________________
Mensaje enviado vía/por Savannah
http://savannah.gnu.org/
