Sponsored Content
Full Discussion: Grub Issues ; Prominent.
Special Forums Hardware Boot Loaders Grub Issues ; Prominent. Post 302553082 by cjcox on Tuesday 6th of September 2011 04:32:52 PM
Old 09-06-2011
Well.. that's not true. You only need to chainload when you need to call up a different boot loader other than grub (e.g. a windows boot loader). So.. grub CAN boot OS's from the grub shell... and if needed it can transfer control to a foreign boot loader as needed.

I think maybe we need to know a LOT more about your setup before we can know what exactly is wrong.
 

10 More Discussions You Might Find Interesting

1. Linux

GRUB and windows XP

After playing a bit with GRUB I got it to boot my windows XP and my Fedora (yeay!). But now my windows became awfully slow (hd seems to be the problem). Does anybody have an idea what could cause this? settings: default=1 timeout=10 splashimage=(hd1,0)/grub/splash.xpm.gz title Fedora... (1 Reply)
Discussion started by: Micky
1 Replies

2. Linux

Remove GRUB

hello i just uninstall fedora core 4 and would like to remove the GRUB from my system. i try to use windows xp startup disk and tryout the fixmbr command. however the system warn me that my computer do not have a proper mbr and performing this action may make all partition in my harddisk... (5 Replies)
Discussion started by: wsc
5 Replies

3. Linux

grub help

in dual os grub will ask like this (linux 9 (red hat)) linux(bigmem) linux(smallmem) dos so i want that grub will ask like this dos linux(bigmem) linux(smallmem) how to do this (8 Replies)
Discussion started by: seshumohan
8 Replies

4. UNIX for Dummies Questions & Answers

grub problem- keeps rebooting as soon as it tries to do grub

Hi, I installed solaris 10 a few weeks ago. It was working fine during the past two weeks. However, now when I start to load to the drive, I get this problem: The BIOS screen comes up like normal, then screen goes blank and a message "Grub loading stage 2" flashes real quick then the computer... (1 Reply)
Discussion started by: moesays
1 Replies

5. Linux

Grub.Conf

Hi, During the Initial startup of the Linux machine. Grub.conf has a entry to mount the root partition as read only after the initialistation of the Kernel. Is there any specific reason for this or the root partition can be made to mounted with read write options. Regards Arun (1 Reply)
Discussion started by: Arun.Kakarla
1 Replies

6. Solaris

grub problem

hi , was using solaris in dual boot with xp , then I ' ve installed ubuntu too . The solaris grub has been in some way damaged , maybe because during the linux installation i've delete an old partition that I was not using by some months. It's normal that the solaris grub has been overriden by... (7 Replies)
Discussion started by: freeware
7 Replies

7. Red Hat

Can we specify which grub.conf to use in grub-install.

Hi, Can we specify which grub.conf to use while installing grub on RHEL. We are working on application which requires different grub configurations needed, depending on certain criteria we need to update grub with correct grub.conf. Can we use grub-install for this purpose? (4 Replies)
Discussion started by: successlin
4 Replies

8. UNIX for Dummies Questions & Answers

"/boot/grub/grub.conf" VS "/etc/grub.conf"

can someone please explain me the difference between these two files: "/boot/grub/grub.conf" and "/etc/grub.conf" .. (7 Replies)
Discussion started by: stunn3r
7 Replies

9. Debian

Cannot install GRUB

Hello, I cannot install grub to my ESP it seems. I have a PC with both Windows 8.1 and Debian installed and I can only boot into Windows since GRUB is not installed on my PC. I am using a Ubuntu Live USB to install GRUB on /dev/sda1 (my ESP). I am using the following commands from Ubuntu... (12 Replies)
Discussion started by: sreyan32
12 Replies

10. Linux

Grub password

what if grub had a password and prevented you from getting in, what should I do, regards (2 Replies)
Discussion started by: abbya
2 Replies
bootadm(1M)															       bootadm(1M)

NAME
bootadm - manage bootability of GRUB-enabled operating system SYNOPSIS
/sbin/bootadm update-archive [-vn] [-R altroot] /sbin/bootadm list-archive [-vn] [-R altroot] only /sbin/bootadm set-menu [-R altroot] key=value /sbin/bootadm list-menu [-R altroot] The bootadm command manages the boot archive and GRUB (GRand Unified Bootloader) menu. The update-archive option provides a way for user to update the boot archive as a preventative measure or as part of the recovery procedure. The set-menu subcommand allows you to switch the auto-boot timeout and default boot entry in the GRUB menu. The list-menu subcommand displays the location of the GRUB menu and the current GRUB menu entries. While the typical location of the GRUB menu is /boot/grub/menu.lst, depending on the install method used the active GRUB menu might be located somewhere else. Use the list-menu subcommand to locate the active GRUB menu. For example, if a system was installed using Live Upgrade, the GRUB menu might not be located in the current boot environment. See the section for typical output from the list-menu option. Note that a SPARC system does not have the concept of a boot archive. The bootadm command on a SPARC system is intended for managing disk- less clients. SUBCOMMANDS
The bootadm command has the following subcommands: update-archive Updates current boot archive if required. Applies to both SPARC and platforms. list-archive Lists the files and directories to be included in the boot archive. Applies to both SPARC and platforms. set-menu Maintain the GRUB menu. The current GRUB menu is boot/grub/menu.lst, relative to root. Do not depend on this location, because it is subject to change. Applies to platforms only. list-menu Lists the location of the active GRUB menu, as well as the current GRUB menu entries. This includes the autoboot-timeout, the default entry number, and the title of each entry. Applies to platforms only. The bootadm command has the following options: -v In an update-archive operation, stale files are displayed on stderr. -n In an update-archive operation, archive content is checked but not updated. -R altroot Operation is applied to an alternate root path. Note - The root file system of any non-global zones must not be referenced with the -R option. Doing so might damage the global zone's file system, might compromise the security of the global zone, and might damage the non-global zone's file system. See zones(5). key=value Possible values are: default=entrynum The item number (for example, 0, 1, or 2) in the GRUB menu designating the operating system to boot when the timer expires. timeout=seconds The number of seconds before the operating system designated by the default item number is booted. If the value is -1, auto boot is disabled. Example 1: Updating the Current Boot Archive The following command updates the current boot archive: # bootadm update-archive Example 2: Updating the Boot Archive on an Alternate Root The following command updates the boot archive on an alternate root: # bootadm update-archive -R /a Example 3: Listing Installed OS Instances The following command lists the installed operating system instances in a GRUB menu: # bootadm list-menu default=0 timeout=10(0) Solaris10(1) Solaris10 Failsafe(2) Linux Example 4: Switching Default Boot Entry The following command refers to the menu displayed in the previous example. The user selects Linux (item 2). # bootadm set-menu default=2 Example 5: Listing GRUB Menu Entries and Location of GRUB Menu The following command lists the GRUB menu entries and the location of the GRUB menu: # bootadm list-menu The location for the active GRUB menu is: /stubboot/boot/grub/menu.lst default 0 timeout 10 0 Solaris10 1 Solaris10 failsafe 2 Linux Example 6: Displaying Location of GRUB Menu The following command displays the location of the GRUB menu: # bootadm list-menu The location for the active GRUB menu is: /dev/dsk/c0t1d0s0 (not mounted) The filesystem type of the menu device is <ufs> default 2 timeout 10 0 c0t1d0s3 1 c0t1d0s3 failsafe 2 Solaris10 3 Solaris10 failsafe In this example, the active GRUB menu is located on a device which is not mounted. To access the GRUB menu, mount the device and access the GRUB menu at <mountpoint>/boot/grub/menu.lst. The following exit values are returned: 0 The command completed successfully. 1 The command exited due to an error. See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWcsu | +-----------------------------+-----------------------------+ |Interface Stability |Stable | +-----------------------------+-----------------------------+ boot(1M), installgrub(1M), attributes(5) The GRUB home page: http://www.gnu.org/software/grub/ 10 Oct 2005 bootadm(1M)
All times are GMT -4. The time now is 07:09 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy