|
|
Subject: Question: Booting off any drive connected to a RAID controller .. . - msg#00076
List: boot-loaders.grub.bugs
In the environment that I am currently using, I have a 3ware RAID controller (operating in JBOD mode) having 12 drives connected to it. I am using Linux 2.4. In this env, I can only boot off the first drive that is detected by 3ware. So, if 3ware labels the drives from sda to sdl, then I can only boot off sda. If sdb is a bootable drive, then I cannot boot off that as long as sda exists. So, this actually means that BIOS is unable transfer control to the boot loader.
Is it possible by using GRUB to boot off any drive? I would think that the same problem would continue here. How would the BIOS know where GRUB resides so that it can transfer control to it?
Thanks
Manish
_______________________________________________
Bug-grub mailing list
Bug-grub@xxxxxxx
http://mail.gnu.org/mailman/listinfo/bug-grub
Was this page helpful?
Thread at a glance:
Previous Message by Date:
click to view message preview
Re: geometry output / floppy chainloading from El Torrito
After some tests:
On Fri, Jan 10, 2003 at 09:40:30AM +0100, Treutwein Bernhard wrote:
> >
> > (fd0) is indeed the floppy image on the El Torito CD.
> >
> > The problem I think with (fd1) ("real (fd0)") is that you
> > have an "old" version of GRUB specifying the booting device
> > as (fd0). Then the stage1 on (fd1) calls a stage2 on (fd0)
> > that is on the floppy El Torito image. Hence this fails. If
> > you upgrade your stage1 on the floppy (not specifying explicitely
> > the booting device) this should work.
> >
>
> hmm, that may be, on the CDROM is a 0.5.96.1 and on the floppy
> is a fresh 0.93 from the cvs last week.
>
> But - please correct me if I it should be different - if I boot
> from floppy I see only the (fd0) logical and physical floppy.
The problem doesn't seem to rely on the El Torito extension but with
a screwded way of handling chainloader (device)+offset.
Would you mind trying this kind of syntax ?
root (fd1)
chainloader +1
boot
This always succeeds with me. IIRC, such a strange behavior (hiatus
between chainloader (device)+1 and root (device); chainloader +1 appeared
with 0.92.
There is something to be fixed.
Cheers,
--
Thierry Laronde (Alceste) <tlaronde@xxxxxxxxxxx>
Key fingerprint = 0FF7 E906 FBAF FE95 FD89 250D 52B1 AE95 6006 F40C
Next Message by Date:
click to view message preview
password for grub-0.93-i386-pc.ext2fs
Hi,
I've downloaded the grub-0.93-i386-pc.ext2fs floppy image, and am
booting off of it. However, all I get is a menu with the options
a, b, and c, and the option enter a password. So, for this floppy to be
useful to me, I'm going to need the password. What is it?
BTW: why is there a password on this floppy anyway?
James A. Morrison
Previous Message by Thread:
click to view message preview
[Bug #505] add possibility to boot off the DiskOnChip flash device
=================== BUG #505: LATEST MODIFICATIONS ==================
http://savannah.gnu.org/bugs/?func=detailbug&bug_id=505&group_id=68
Changes by: Ilguiz Latypov <ilatypov@xxxxxxxxxxx>
Date: 2003-Jan-10 18:58 (GMT)
------------------ Additional Follow-up Comments ----------------------------
* stage2/stage2.c (cmain): Set boot_drive to the drive number
where configuration file was found. This fixes the menu option
processing when menu.lst is found on a drive different from the
hardcoded one. The multiple drive boot order is enabled only
with DiskOnChip, but it doesn't depend on DiskOnChip.
------------------ Additional Bug Attachment ----------------------------
File name: grub-2003-01-08-doc.patch Size:81 KB
fix menu handling when the menu is found on non-default drive
http://savannah.gnu.org/bugs/download.php?group_id=68&bug_id=505&bug_file_id=229
=================== BUG #505: FULL BUG SNAPSHOT ===================
Submitted by: ilgiz Project: GNU GRUB
Submitted on: 2002-May-30 18:24
Category: Booting Severity: Major
Priority: Later Bug Group: Feature Request
Resolution: Later Assigned to: okuji
Status: Open Release: 0.92
Reproducibility: None Planned Release:
Summary: add possibility to boot off the DiskOnChip flash device
Original Submission: This is a request to add a compile time configuration
option that
would allow to store GRUB bootloader on DiskOnChip flash memory
device and boot off it.
The DiskOnChip flash device is usually available to the system
via the 8 KiB I/O memory window (chip select mechanism?) and can
be detected by BIOS as an extension device.
Follow-up Comments
*******************
-------------------------------------------------------
Date: 2003-Jan-10 18:58 By: ilgiz
* stage2/stage2.c (cmain): Set boot_drive to the drive number
where configuration file was found. This fixes the menu option
processing when menu.lst is found on a drive different from the
hardcoded one. The multiple drive boot order is enabled only
with DiskOnChip, but it doesn't depend on DiskOnChip.
-------------------------------------------------------
Date: 2002-Oct-14 15:53 By: mmeade
Patch is based on Ilguiz Latypov's <ilatypov@xxxxxxxxxxxxx> 07-29 patch for
DiskOnChip support, with the following changes:
a) Added a patch from Karim Yaghmour (karim@xxxxxxxxxxx) that provides a way to
bypass the DiskOnChip boot entirely, in case Grub is misconfigured or doesn't
behave as planned.
b) Added support for DiskOnChip devices formatted with newer versions (5.x) of
the M-Sys DFORMAT utility. The Grub firmware may now be burned using the
DFORMAT utility, possibly eliminating many problems that can occur when using
doc_loadbios under Linux.
c) Backed out requirement for automake 1.6 from previous DiskOnChip patch.
This patch needs automake 1.5 and autoconf 2.53, like the main GRUB tree.
Instructions/HOWTO available at:
http://lists.infradead.org/pipermail/linux-mtd/2002-October/006166.html
-------------------------------------------------------
Date: 2002-Sep-11 16:00 By: hno
After testing the GRUB DOC patch I must say that I disagree on the
fallback/last resort approach for searching for the menu. Personally I think
this part of the patch does more damage than benefit.
What is needed is a tool to set the menu location, not to have GRUB try to
guess where it should be.
Other than this having the DOC support in the standard GRUB tree would be great.
-------------------------------------------------------
Date: 2002-Aug-06 16:35 By: ilgiz
a) Apply Mark Meade's unification of DiskOnChip 2000 and
DiskOnChip Millennium code. Just as with stage2 or Linux
MTD DiskOnChip driver, the stage1 code will determine page
size by looking at the manufacturer and chip ID numbers.
b) Read chip ID into the stage2 RAM area.
c) Add floppy drive BIOS access as a last resort when looking
for /boot/grub/menu.lst.
-------------------------------------------------------
Date: 2002-Jul-26 14:40 By: dwmw2
Copyright assignment should now be complete.
-------------------------------------------------------
Date: 2002-Jun-22 01:45 By: ilgiz
* stage1/doc_stage1.S: Set data transfer direction flag.
Shuffle code to make room in the first 256 bytes.
* stage1/doc_stage1b.S: Shuffle code to make room in the first
256 bytes.
* stage1/doc_stage1.h: Assign 1 not an empty value to the macro
symbol.
* configure.in: Change AS, ASFLAGS to comply with new automake.
* Makefile.am: Likewise.
* stage2/Makefile.am: Likewise.
* README_DiskOnChip: Add missing files when generating build files.
-------------------------------------------------------
Date: 2002-May-30 19:34 By: okuji
We are waiting for the copyright being assigned to the FSF.
I'm going to apply the patch, once the copyright problem is
resolved.
Okuji
CC list is empty
File Attachments
****************
-------------------------------------------------------
Date: 2003-Jan-10 18:58 Name: grub-2003-01-08-doc.patch Size: 81KB By: ilgiz
fix menu handling when the menu is found on non-default drive
http://savannah.gnu.org/bugs/download.php?group_id=68&bug_id=505&bug_file_id=229
-------------------------------------------------------
Date: 2002-Oct-14 15:53 Name: grub-2002-10-08-doc.patch Size: 81KB By:
mmeade
Linux MTD DiskOnChip 2000/Millennium patch to the GRUB 2002-10-08 snapshot
http://savannah.gnu.org/bugs/download.php?group_id=68&bug_id=505&bug_file_id=107
-------------------------------------------------------
Date: 2002-Aug-06 16:35 Name: grub-2002-07-29-doc.patch Size: 83KB By: ilgiz
Linux MTD DiskOnChip 2000/Millennium patch to the GRUB 2002-07-29 snapshot
http://savannah.gnu.org/bugs/download.php?group_id=68&bug_id=505&bug_file_id=67
-------------------------------------------------------
Date: 2002-Jun-22 01:45 Name: grub-2002-06-21-doc.patch Size: 86KB By: ilgiz
The updated Linux MTD DiskOnChip patch against the 2002-06-21 snapshot.
http://savannah.gnu.org/bugs/download.php?group_id=68&bug_id=505&bug_file_id=37
-------------------------------------------------------
Date: 2002-May-30 18:24 Name: grub-2002-05-30-doc.patch Size: 81KB By: ilgiz
The adjusted DiskOnChip patch to GRUB CVS tree as of 2002-05-30 originally
written by David Woodhouse <dwmw2@xxxxxxxxxxxxx>
http://savannah.gnu.org/bugs/download.php?group_id=68&bug_id=505&bug_file_id=18
For detailed info, follow this link:
http://savannah.gnu.org/bugs/?func=detailbug&bug_id=505&group_id=68
Next Message by Thread:
click to view message preview
password for grub-0.93-i386-pc.ext2fs
Hi,
I've downloaded the grub-0.93-i386-pc.ext2fs floppy image, and am
booting off of it. However, all I get is a menu with the options
a, b, and c, and the option enter a password. So, for this floppy to be
useful to me, I'm going to need the password. What is it?
BTW: why is there a password on this floppy anyway?
James A. Morrison
|
|