Login or Register to Ask a Question and Join Our Community

Sponsored Content
Full Discussion: Problem with scientific Linux multiboot
Operating Systems Linux Red Hat Problem with scientific Linux multiboot Post 302892094 by verdepollo on Monday 10th of March 2014 09:25:04 PM
Old 03-10-2014
If you're not seeing any bootloader then it most likely got wiped out during the installation of SL.

If both Linux use the same GRUB version then it will be a bit easier to just reinstall the bootloader (there are plenty of tutorials in the web about reinstalling GRUB by using a rescue CD).

If one of the distributions is using GRUB while the other uses GRUB2 you'll have to "chainload" the bootlader: Basically use the first (almost empy) bootloader to call the second one and then boot from the selected partition. This should work whether you install it on the MBR or on the first partition of a disk.

Both methods require a bootloader reinstallation, though.
 

5 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Multiboot problem Help plz??

I have installed Win98 OS .......1st then RH7.2 with GRUB bootloader okay i.e in the Grub there is two choices 1-Linux 2-Dos also I install bootloader of linux in MBR -master boot record- when select Linux an error : ... (6 Replies)
Discussion started by: atiato
6 Replies

2. UNIX for Dummies Questions & Answers

cannot use mail in scientific LINUX

i'm in computer laboratory and i want to send mail to other computer in this computer lab..but the problem is it doesn't function. the result is : >N 1 Mail Delivery Subsys Mon Sep 3 11:44 71/2580 "Returned mail: see transcript for details" i already install mailx and sendmail but its still... (1 Reply)
Discussion started by: help me
1 Replies

3. Solaris

Multiboot on a laptop: windows Solaris Linux

Hi Just want to share.... Multiboot: winlinsos; June 2016 Lenovo x230, 4GB - No internal DVD driver I have # fdisk -l Disk /dev/sda: 120.0 GB, 120034123776 bytes, 234441648 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O... (0 Replies)
Discussion started by: van12
0 Replies

4. UNIX for Beginners Questions & Answers

Multiboot problem with Slackware 14.2, FreeBSD 11 & Solaris 10

I want to install Slackware 14.2, FreeBSD and Solaris 10 on a p4 machine but multiboot is not working as lilo overwrites grub and btx boot loader can't detect others. I had to boot slackware and Solaris with the installation disc for a good number of times. I installed all boot loaders on MBR. The... (0 Replies)
Discussion started by: vectrum
0 Replies

5. UNIX for Beginners Questions & Answers

Multiboot problem with Slackware 14.2, FreeBSD 11 & Solaris 10

I want to install Slackware 14.2, FreeBSD and Solaris 10 on a p4 machine but multiboot is not working as lilo overwrites grub and btx boot loader can't detect others. I had to boot slackware and Solaris with the installation disc for a good number of times. I installed all boot loaders on MBR. The... (3 Replies)
Discussion started by: harveyclayton
3 Replies

LEARN ABOUT MINIX

bootctl

BOOTCTL(1)							      bootctl								BOOTCTL(1)

NAME

       bootctl - Control the firmware and boot manager settings

SYNOPSIS

       bootctl [OPTIONS...] status

       bootctl [OPTIONS...] list

       bootctl [OPTIONS...] update

       bootctl [OPTIONS...] install

       bootctl [OPTIONS...] remove

DESCRIPTION

       bootctl checks, updates, installs or removes the boot loader from the current system.

       bootctl status checks and prints the currently installed versions of the boot loader binaries and all current EFI boot variables.

       bootctl list displays all configured boot loader entries.

       bootctl update updates all installed versions of systemd-boot, if the current version is newer than the version installed in the EFI system
       partition. This also includes the EFI default/fallback loader at /EFI/BOOT/BOOT*.EFI. A systemd-boot entry in the EFI boot variables is
       created if there is no current entry. The created entry will be added to the end of the boot order list.

       bootctl install installs systemd-boot into the EFI system partition. A copy of systemd-boot will be stored as the EFI default/fallback
       loader at /EFI/BOOT/BOOT*.EFI. A systemd-boot entry in the EFI boot variables is created and added to the top of the boot order list.

       bootctl remove removes all installed versions of systemd-boot from the EFI system partition, and removes systemd-boot from the EFI boot
       variables.

       If no command is passed, status is implied.

OPTIONS

       The following options are understood:

       -h, --help
	   Print a short help text and exit.

       --version
	   Print a short version string and exit.

       --path=
	   Path to the EFI System Partition (ESP). If not specified, /efi, /boot, and /boot/efi are checked in turn. It is recommended to mount
	   the ESP to /boot, if possible.

       -p, --print-path
	   This option modifies the behaviour of status. Just print the path to the EFI System Partition (ESP) to standard output and exit.

       --no-variables
	   Do not touch the EFI boot variables.

EXIT STATUS

       On success, 0 is returned, a non-zero failure code otherwise.

SEE ALSO

       Boot loader specification[1] systemd boot loader interface[2]

NOTES

	1. Boot loader specification
	   https://www.freedesktop.org/wiki/Specifications/BootLoaderSpec

	2. systemd boot loader interface
	   https://www.freedesktop.org/wiki/Software/systemd/BootLoaderInterface

systemd 237																BOOTCTL(1)
All times are GMT -4. The time now is 09:08 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy