Booting OS X from grub legacy

Hi!
I have just installed Mavericks just to test it in another HDD as you can see here:
Disk /dev/sda: 465,8 GiB, 500107862016 bytes, 976773168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x00080fa8
Disposit. Inicio Start Final Blocks Id System
/dev/sda1 63 976768064 488384001 5 Extended
/dev/sda5 126 52436159 26218017 83 Linux
/dev/sda6 52436223 54540674 1052226 82 Linux swap / Solaris
/dev/sda7 54540738 976768064 461113663+ 83 Linux
Disk /dev/sdb: 298,1 GiB, 320072933376 bytes, 625142448 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 43082D18-323A-4A1C-A3FC-29211AF16D5F
Disposit. Start Final Size Tipo
/dev/sdb1 40 409639 200M EFI System
/dev/sdb2 409640 624880263 297,8G Apple HFS/HFS+
sda is where all Arch stuff is and sdb is where all OS X stuff is.
I've tried to boot OS X from grub legacy (I don't like too much grub 2) but I'm no capable.
Here is my menu.lst
# Config file for GRUB - The GNU GRand Unified Bootloader
# /boot/grub/menu.lst
# DEVICE NAME CONVERSIONS
# Linux Grub
# /dev/fd0 (fd0)
# /dev/sda (hd0)
# /dev/sdb2 (hd1,1)
# /dev/sda3 (hd0,2)
# FRAMEBUFFER RESOLUTION SETTINGS
# +-------------------------------------------------+
# | 640x480 800x600 1024x768 1280x1024
# ----+--------------------------------------------
# 256 | 0x301=769 0x303=771 0x305=773 0x307=775
# 32K | 0x310=784 0x313=787 0x316=790 0x319=793
# 64K | 0x311=785 0x314=788 0x317=791 0x31A=794
# 16M | 0x312=786 0x315=789 0x318=792 0x31B=795
# +-------------------------------------------------+
# for more details and different resolutions see
# http://wiki.archlinux.org/index.php/GRUB#Framebuffer_Resolution
# general configuration:
timeout 5
default 0
color light-blue/black light-cyan/blue
# boot sections follow
# each is implicitly numbered from 0 in the order of appearance below
# TIP: If you want a 1024x768 framebuffer, add "vga=773" to your kernel line.
# (0) Arch Linux
title Arch Linux
root (hd0,4)
kernel /boot/vmlinuz26 root=/dev/sda5 ro init=/usr/lib/systemd/systemd fastboot acpi_enforce_resources=lax
initrd /boot/kernel26.img
# (1) Arch Linux
title Arch Linux Fallback
root (hd0,4)
kernel /boot/vmlinuz26 root=/dev/sda5 ro
initrd /boot/kernel26-fallback.img
# (2) Arch Linux Bootchart
title Arch Linux Bootchart
root (hd0,4)
kernel /boot/vmlinuz26 root=/dev/sda5 ro init=/sbin/e4rat-preload fastboot logo.nologo quiet init=/sbin/bootchartd
initrd /boot/kernel26.img
# (3) Mac OS X
title Mac OS X
root (hd1,1)
makeactive
chainloader +1
I've tried with both (hd1,0) and (hd1,1), but they on't work
Any idea? As you can see I'm a newbie here
Thanks
Last edited by eherranzr (2014-04-07 15:34:26)

Inxsible wrote:
eherranzr wrote:Is there any way to boot a HDD with a GUID Partition Table (GPT) from grub legacy or I must upgrade to grub 2?
No grub legacy does not support GPT partitions as stated in the wiki. https://wiki.archlinux.org/index.php/Gr … cessary.3F
try syslinux. its simpler than the mess that is grub2 (IMO, of course )
So, as I have read what I have to do is the following:
Install syslinux
Execute
# syslinux-install_update -i -a -m
for an "automatic" installation
Create and configure syslinux.cfg (I think I'll ask for some help here)
Make it graphical:
# cp /usr/lib/syslinux/bios/vesamenu.c32 /boot/syslinux/
Reboot
It should work like that. Am I right?

Similar Messages

DRMK when booting to W7 from grub

Hi.
I've got myself a brand new Precision M4600 laptop, and decided to dual boot Archie and Windows 7. So I received the Precision with w7 installed, btw i've got a 256gb SSD which is partitioned as shown:
[ama@ama-precision ~]$ sudo fdisk -l
Disk /dev/sda: 256.1 GB, 256060514304 bytes
255 heads, 63 sectors/track, 31130 cylinders, total 500118192 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x4e92f42b
Device Boot Start End Blocks Id System
/dev/sda1 * 63 80324 40131 6 FAT16
/dev/sda2 81920 1622015 770048 7 HPFS/NTFS/exFAT
/dev/sda3 1622016 266729471 132553728 7 HPFS/NTFS/exFAT
/dev/sda4 266729472 500103449 116686989 5 Extended
/dev/sda5 266729535 275517026 4393746 83 Linux
/dev/sda6 275517090 324338561 24410736 83 Linux
/dev/sda7 324338625 500103449 87882412+ 83 Linux
I installed GRUB on the mbr, install goes fine, arch goes fine (posting this message from arch, met some issues though but nvm) but when i try to boot to w7 from grub, it shows:
Booting Windows 7
rootnoverify (hd0,0)
chainloader +1
Loading DRMK V8.00...
DRMK Version 8.00
COMMAND.COM Build 37 - Jul 20, 2008
DRMK KERNEL Build 15 - Aug 8, 2008
Copyright (c) 2006-2008 Dell Inc. All rights reserved.
C:\>
so wtf is this dell drmk thing ? Googling didn't help me that much...
Oh and here's my menu.lst
# Config file for GRUB - The GNU GRand Unified Bootloader
# /boot/grub/menu.lst
# DEVICE NAME CONVERSIONS
# Linux Grub
# /dev/fd0 (fd0)
# /dev/sda (hd0)
# /dev/sdb2 (hd1,1)
# /dev/sda3 (hd0,2)
# FRAMEBUFFER RESOLUTION SETTINGS
# +-------------------------------------------------+
# | 640x480 800x600 1024x768 1280x1024
# ----+--------------------------------------------
# 256 | 0x301=769 0x303=771 0x305=773 0x307=775
# 32K | 0x310=784 0x313=787 0x316=790 0x319=793
# 64K | 0x311=785 0x314=788 0x317=791 0x31A=794
# 16M | 0x312=786 0x315=789 0x318=792 0x31B=795
# +-------------------------------------------------+
# for more details and different resolutions see
# http://wiki.archlinux.org/index.php/GRUB#Framebuffer_Resolution
# general configuration:
timeout 5
default 0
color light-blue/black light-cyan/blue
# boot sections follow
# each is implicitly numbered from 0 in the order of appearance below
# TIP: If you want a 1024x768 framebuffer, add "vga=773" to your kernel line.
# (0) Arch Linux
title Arch Linux
root (hd0,5)
kernel /boot/vmlinuz26 root=/dev/sda6 ro
initrd /boot/kernel26.img
# (1) Arch Linux
title Arch Linux Fallback
root (hd0,5)
kernel /boot/vmlinuz26 root=/dev/sda6 ro
initrd /boot/kernel26-fallback.img
# (2) Windows
title Windows 7
rootnoverify (hd0,0)
#makeactive
chainloader +1
i've also tried uncommenting the makeactive line but no help.
thanks for your help.

rootnoverify (hd0,0) = /dev/sda1
rootnoverify (hd0,1) = /dev/sda2
see whitch one is your windows installed sda2 or sda3 and point that into /boot/grub/menu.lst
aka..
# (2) Windows
title Windows 7
rootnoverify (hd0,1)
#makeactive
chainloader +1
or
# (2) Windows
title Windows 7
rootnoverify (hd0,2)
#makeactive
chainloader +1

[SOLVED] Unable to Boot Windows 7 from GRUB

I recently reinstalled Arch onto my laptop (Lenovo Thinkpad t520) and have been having problems with Grub. For the last week I've been having trouble getting it to run grub at boot at all, only being able to run windows 7 by flagging it as the bootable drive. The other day I finally got it to boot into grub, and from grub I can boot into Arch. However, I can not boot into windows 7 through grub. When I attempt to, it throws an error:
Invalid EFI file path
I'm somewhat new to arch, and especially new to efi bootloading and such. Right now the only way I can get into windows is either booting from the arch install disk > boot other os and specifying partition 2 (where I have windows installed) or by pressing f12 at boot. When I do this (not sure what the term is, if anyone knows please tell me), it brings up a menu asking where I want to boot with "arch_efi" "cd drive" "Hard drive" etc. I choose hard drive and it will then boot to windows by default. Booting normally takes me to grub where I can boot into arch but not windows. If there's any more info you need please let me know and I'll try to provide it. Thanks in advance.
Also, here is my current partition setup
/dev/sda1 /boot/efi
/dev/sda2 Windows7
/dev/sda3 Extended partition containing sda 5,6, & 7
/dev/sda4 swap
/dev/sda5 /boot
/dev/sda6 /
/dev/sda7 /home
UPDATE
Terminator seems to be right (still on a roll!), so I wiped the partition I had grub on, removed grub, and installed syslinux. Now I have another problem that I'm hoping can be solved in the same thread to avoid another. It boots to syslinux no problem, and I can boot to windows from there all good, but when I select arch I get:
Root device mounted successfully but /sbin/init does not exist
I haven't been able to look for solutions too much on my own, but any help would be appreciated, thank you.
Last edited by IamFuzzles (2012-08-22 04:20:56)

Terminator wrote:If I understand it correctly, what you are trying is impossible: you are trying to boot windows using UEFI on a disk with MBR partitioning. Windows 7 only supports UEFI on discs with GPT partitioning but AFAIK, extended partitions only exist in MBR partitioning.
i also saw this in the arch wiki, but i have a brand new lenovo ideapad y570 running windows 7 64-bit that i'm in the process of setting up for someone, and it has what i think is an efi system partition but the disk uses mbr partitioning. does anyone know why this might be, or is there a way i can verify that the system is actually being booted via bios-mbr?
Last edited by e_tank (2012-08-21 11:56:15)

[SOLVED] UEFI system booting from MBR partition table and GRUB legacy

I'm trying to understand once and for all the process by which Arch can be booted from a system with UEFI firmware and an MBR partition table. Some of the information on the wiki seems conflictual / non-nonsensical at times. Apologies in advance if this has been answered time and time again, but I did search around and all I found was fixes to get Arch to boot rather than comprehensive explanations of the boot process.
Now, the way I would imagine it works is that it's just completely identical to the way it would work with a BIOS firmware. The UEFI firmware detects an MBR partitioning scheme (or is configured to know it's an MBR partitioning scheme), activates some "legacy" mode and executes the MBR boot code, just like a BIOS firmware would.
The wiki however, says different. From the Macbook article: "Do not install GRUB onto /dev/sda !!! Doing so is likely to lead to an unstable post-environment."?
So what is there in the MBR boot sector? Nothing?
How does the firmware know what to boot if there's no 0xEF BIOS boot partition and no Grub stage 1 in the MBR boot sector?
Also, how does installing Grub stage 1 to a partition work? Does it have to be at the beginning of the partition? Wouldn't that overwrite some existing data?
I'm especially puzzled since many guides to installing Vista on a macbook recommend simply formatting as MBR, and installing as normal, which I suppose entails having the Windows installation process write its boot code to the MBR, ie the equivalent of installing grub stage 1 to /dev/sda rather than to the /boot partition, as the Macbook article suggests.
Any input is appreciated.
P.S. I realize it's probably simpler, if I just want to dual boot Windows and Arch, to install Windows 7 in UEFI-GPT mode, let it create the EFI System Partition, and then install GRUB 2 to that partition, but I'm still curious about the UEFI-MBR boot process.
Last edited by padavoine (2012-06-06 09:35:10)

padavoine wrote:
CSM in UEFI firmwares do the exact same job as normal BIOS firmware.
So it's something specific to the Mac that it's able to boot from a partition's VBR while ignoring the MBR?
The reason that warning is given is because grub-legacy modifies more than just the MBR boot code region. It can overwrite some parts of GPT header.
Not true, the instruction is given in the context of an MBR format, not in the context of a GPT format, so there's nothing to overwrite and Stage 1.5 should be safely embeddable in the post-MBR gap.
In BIOS boot (normal case in non-UEFI firmwares or CSM in UEFI firmwares) does not read the partitition table (atleast it is supposed to be dumb in this regard), it simply launches whatever boot code exists in the 1st 440-byte of the MBR region.
So again, you're saying it's specific to the Mac UEFI that it lets you choose a partition whose VBR to load, regardless of what's in the MBR?
I haven't used Macs so I can't comment on Mac firmware behaviour. But normal BIOS firmwares (legacy and CSM) launch only the MBR boot code and not the partition boot code. We need some chainload capable boot manager in the MBR to launch the partition VBR.
grub-legacy does not know anything about GPT. So when you install grub-legacy to /dev/sda, it install the MBR boot code (stage1) and stage 1.5 code to the (supposed) post MBR gap. Since there is no actual post MBR gap in GPT (which has been taken over by the header and partition table), grub-legacy does not check for GPT and it assumes the post MBR gap actually exists which is invalid in case of GPT. grub-legacy embeds the stage 1.5 code in GPT header and table region (which grub assumes to be unused post MBR gap) and thus corrupts it.
0xEF is the MBR type code for UEFISYS partition. grub stage 1 (used in grub-legacy, not in grub2) is the 440-byte boot code stored in MBR for use in BIOS boot.
That's precisely my point: with neither proper executable code in the MBR (since grub was installed to a partition, not to the MBR) nor a UEFI system partition, what does the firmware default to, and how does it know what partition to boot from?
In that case it might fallback to UEFI Shell (if it exists) or give an error similar to the case where BIOS does not find any bootable code in 440-byte MBR region.
So even with bootcamp/CSM, the disk also needs to be MBR partitioned. So Macs use something called "Hybrid GPT/MBR" ( http://rodsbooks.com/gdisk/hybrid.html ) where the MBR table is synced to match the first 3 partitions in the GPT table.
I know what Bootcamp does, and that's not what I was referring to. I was referring to standalone Vista installs. I wasn't puzzled at the fact that they were using MBR, I was puzzled at the fact that contrary to the recommendations for the standalone Arch install on the wiki (with MBR partitioning, not GPT), they didn't do anything to try and prevent Windows from writing to the MBR.
You can't prevent Windows from overwriting the MBR region. You have to re-install the bootloader (grub2/syslinux etc.) after installing Windows. That is the reason why it is recommended to install Windows first and linux later.
Thats not true. I actually find it is much easier to install Windows UEFI-GPT using USB rather than a DVD.
I haven't done it since the only UEFI system I own has no DVD drive, but I was under the impression that it was simply a matter of choosing DVD UEFI boot in the firmware's boot menu.
format the USB as FAT32 and extract the iso to it. That it.
No, thats not it, precisely, it doesn't work out of the box with a standard Windows install USB, you need to fiddle around:
2.3 Extract bootmgfw.efi from [WINDOWS_x86_64_ISO]/sources/install.wim => [INSTALL.WIM]/1/Windows/Boot/EFI/bootmgfw.efi (using 7-zip aka p7zip for both the files), or copy it from C:\Windows\Boot\EFI\bootmgfw.efi from a working Windows x86_64 installation.
2.4 Copy the extracted bootmgfw.efi file to [MOUNTPOINT]/efi/microsoft/boot/bootmgfw.efi .
Most of the Windows isos already have /EFI/BOOT/BOOTX64.EFI file, so no need to extract the bootmgfw.efi file.
There is no difference between in BIOS booting in UEFI firmwares and BIOS booting with legacy firmware.
There has to be a difference, at least in the Mac firmware (sorry, I keep switching), since legacy firmware, AFAIK, cannot chainload a bootloader in a partition's VBR without there being some sort of "stage1" code in the MBR.
No idea about Mac EFI. Apple made a spagetti out of UEFI Spec. To actually understand how Mac firmwares work, read the blog posts by Matthew Garrett of Redhat, about his efforts in getting Fedora to boot in Macs.

Dual boot , windows 7 keep restart after select from grub section

Hello everyone, i am new here.
I want to make a dual boot in my computer.
I am using a same hardisk to install both OS.
1st, I install arch linux , after install working well from grub.
2nd, I install windows 7, after install , it skip the grub section , directly load windows 7.
I boot my archlinux live cd.
Go to grub .
type root (hd0, and press tab to make sure my partition.
setup (hd0).
The grub section was recover and success to login arch linux.
but fail to login windows 7 , then i modify /boot/grub/menu.lst . modify the windows (hd0, 1).
My trouble probem is here, after i select the windows section , my com just like restart computer.
Even i try change to (hd0, 2 or 3 ) also same problem, windows 7 restart computer.

I have try to install dual boot for more than 5 time, first i install windows then only come to arch linux, but always fail to boot up windows.
Thank for helping me ^^
This is my fdisk -l
I have 2 hardisk, but i install both Os in the same hardisk.
Device Boot Start End Block ID System
/dev/sdb1 1 24 192742+ 83 Linux
/dev/sdb2 25 37 102400 7 HPFS/NTFS
Partition 2 does not end on cylinder boundry
/dev/sdb3 37 8243 65939456 7 HPFS/NTFS
/dev/sdb4 8247 14593 50982277+ 5 Extended
/dev/sdb5 8247 8368 979933+ 83 Linux
/dev/sdb6 8364 10858 20000893+ 83 Linux
/dev/sdb7 10859 14593 20001356 82 Linux Swap / Solaris
# (0) Arch Linux
title Arch Linux
root (hd0,0)
kernel /vmlinuz26 root=/dev/sd5 ro
initrd /kernel26.img
# (1) Arch Linux
title Arch Linux fallback
root (hd0,0)
kernel /vmlinuz26 root=/dev/sd5 ro
initrd /kernel26_fallback.img
# (2) windows
title windows 7
rootnoverify (hd0, 1)
makeactive
chainloader +1

Solaris + Windows 7 .. delete Solaris Partition .. how do i boot from GRUB?

i had Solaris and W7 partitions -- together summing to the entire disk size -- but i needed to expand W7 partition. i was not able to resize the ZFS so i deleted it; i can now only boot as far as GRUB "BASH-like commands" window [GRUB> prompt], which rejects everything i enter.
the ultimate goal is to expand the W7 partition and effect another Solaris install (and possibly another primary partition -- Linux?)
how can i recover?
Edited by: Neal Weissman on May 21, 2012 12:22 PM

You saved my obtuse butt again
... THANK YOU AGAIN ALAN !!
i was contemplating this strategy of the W7 install dvd repair mechanism, but i refrained because of the imagined risk of destroying my W7 install -- i was not going to attempt it unless someone knowledgeable confirmed it.
the W7 repair took ~ 25 minutes -- it installed a recovery partition.
my original idea was to uninstall GRUB, but i was anxious about that solution too.
Edited by: Neal Weissman on May 22, 2012 12:28 AM

[Solved] Removing multiple entries from grub

Hi
There are many entries in my arch's grub boot loader:
Arch Linux pkg-linux kernel
*Arch Linux pkg-linux kernel (fallback initramfs)
Arch Linux
Advanced options for Arch Linux
Linux Mint 15
Advanaced options for Linux Mint 15
Microsoft Windows 7 Professional
But I also want to keep following three entries:
Arch Linux
Linux Mint 15
Microsoft Windows 7 Professional
How can I remove remaining entries from grub menu?
Regards
Last edited by zetrotrack000 (2014-03-11 20:01:45)

Grub2 menu entries are created by a set of scripts in /etc/grub.d
Your first 2 entries are standard for arch and are generated by the 10_archlinux script. The 10_archlinux script is distributed by arch. It exists because the standard 10_linux script does not always create reliable menu entries for arch.
Your other linux entries are generated by the 10_linux script which is distributed by grub upstream.
Your windows entry is generated by the os-prober script. That can just be left alone.
To sort out the redundant linux entries you could try disabling either of the linux scripts and regenerating the menu.
Alternatively, you could disable both linux scripts and define your menu entries manually in the 40_custom script. The syntax for custom menu entries is similar to that of grub legacy. See the grub wiki article for info.
Hope this helps!
Last edited by Chazza (2014-03-10 22:45:18)

Grub-Legacy-gfx on i686 system

Hi. I'm trying to install some eyecandy for grub (ie. a splash image on grub boot menu), but I'm having some problems. On wiki page https://wiki.archlinux.org/index.php/Grub-Legacy-gfx it says that the grub-gfx package can be compiled on x86_64 architecture only with gcc-multilib. Now I managed to add multilib mirrors to mirrorlist and when I try to install gcc-multilib with
# pacman -S gcc-multilib
I get the following error:
error: failed to prepare transaction (package architecture is not valid)
:: package gcc-multilib-4.6.2-6-x86_64 does not have a valid architecture
I downloaded grub-gfx from AUR, and when I 'makepkg -S' on it, it ends with error:
patching file stage2/shared.h
patching file stage2/stage2.c
patching file stage2/term.h
==> ERROR: A failure occurred in build().
Aborting...
I don't know what to do next. Should I try maybe GRUB2, or simply give up on splash image in grub menu?

https://aur.archlinux.org/packages/gr/grub-gfx/PKGBUILD
It conflicts with grub / grub-legacy, so no, it's not possible to have them both, you need to pick one or the other. grub-gfx is a version of grub-legacy.
Why do you think you need grub2? At which point does it say anything about installing grub2?

Cannot boot Windows 7 from UEFI bootable usb

Hello,
I need to install Windows 7 in UEFI mode using USB flash drive and for this purpose:
- created Windows 7 UEFI bootable USB using Rufus application
- In BIOS choosed UEFI Hybrid boot option with CSM
- disabled switchable graphics
- disabled fast boot
- secure boot is disabled
When I reboot and choose to boot from the USB using F9 boot menu, the computer continues to load my current system from my HDD and not the UEFI from the USB.
(I used the same USB and Windows 7 and succesfully installed windows in UEFI mode on my desktop machine but the laptop doesn`t want to recognize the USB as a bootable.)
I tried to put the USB on different slots but that doesn`t help.
Tried to boot from the UEFI USB drive in Legacy boot mode in BIOS, but no result.
My sistem is as follows:
System Model HP ProBook 4540s
BIOS Version/Date Hewlett-Packard 68IRR Ver. F.40, 29-Jan-13
SMBIOS Version 2.7
System Type x64-based PC
Processor Intel(R) Core(TM) i5-3230M CPU @ 2.60GHz, 2601 Mhz, 2 Core(s), 4 Logical Processor(s)
I searched the HP forum and the internet for a solution but nothing helps.
Cindly ask for support. Do anyone have or resolved the same problem?
Regards.

UEFI will not permit Windows 7 install did you disable that to Legacy Bios boot?
If not sure follow this help?
Boot to UEFI Mode or Legacy BIOS mode
I am a Volunteer to help others on here-not a HP employee.
Replies aren't online 24/7 because of Time Zone differences.
Remember in this Day and Age of Computing the Internet is Knowledge at your fingertips if you choose understand it. -2015-

[Solved] Grub not displaying menu, error messages from grub-mkconfig

Hi I'm new
I have (or rather, am trying to setup) a dual boot with Windows 8.1 and Arch, with each OS on separate SSDs.
Windows 8.1 already installed, Arch installation (seems to have) has gone smoothly. However, when I remove the installation usb, and try to boot, I get a command line prompt:
grub >_
...instead of a menu. I tried typing 'boot', but got 'you need to load the kernel first'. So I cannot access my arch installation without chrooting (or knowing how to compile the kernel in the command line, which I could not find after a lot of searching)
I followed the documentation in the Beginner's Guide and the GRUB page for installing and configuring GRUB. This is UEFI (grub2), not BIOS (grub legacy).
pacman -S grub efibootmgr
grub-install --target=x86S64-efi --efi-directory=/boot --bootloader-id=arch_grub --recheck
No error messages. I also installed os-prober for kicks. When I went to generate the config file (as recommended for beginners), I got a torrent of what I interpreted to be error messages, not just copacetic output:
grub-mkconfig -o /boot/grub/grub.cfg
resulted in:
click this link for error messages
(sorry about the image. I had to shutdown and reboot into my windows partition, since I still can't arch it up. If any/all of you have a better way to reproduce output and feel it pertinent, I'm all ears)
so upon exiting chroot and rebooting, grub boots up to the above effect; no menu is displayed. And I am sad panda.
Background Information:
Partition scheme:
/dev/sda1 - BIOS boot partition (I didn't read carefully, lol)
/dev/sda2 - EFI System Partition - mounted to /mnt/boot when chrooting in
/dev/sda3 - Root partition - mounted to /mnt/ when chrooting in
/dev/sda4 - Home partition - mounted to /mnt/home when chrooting in
The installation and configuration described above was done in chroot with the above partition scheme
I originally had issues booting into UEFI mode with the arch iso (written to a usb stick for the initial install). The boot would hang at 'triggering uevents'. I ultimately fixed this by pressing 'e' in the bootloader menu (also grub, I believe) and prepended
linux /boot/vmlinux-linux root=UUID=978e3e81-8048-4ae1-8a06-aa727458e8ff nomodeset nouveau.modeset=0
It then (successfully triggered uevents? and) booted normally
ALSO:
This is a custom built pc.
Hardware:
intel i7 4930K
ASUS Sabertooth X79 mobo
ASUS GTX 780 Ti gpu
ballistix sport DDR3 RAM (4 x 8 GB)
3 x 128 GB SSD (ADATA P900)
1 x 2 TB HDD (Toshiba, 7200 rpm)
Hey, if you made it to the bottom of this post, I really appreciate you taking the time out of your day. Thank you!
Last edited by Otsdarva (2014-06-09 03:22:25)

I realized that since I was not using EFISTUB, I could not mount the ESP to /boot; it had to be /boot/efi. A quick remount-reinstall of grub, then rerunning grub-mkconfig solved the issue.
Also, regarding WonderWoofy's suggestion: I learned by trying gummiboot that for whatever reason the kernel hadn't compiled properly when I ran
pacstrap /mnt base base-devel
Fixed via
pacman -S linux
Thanks for your help, everybody!

Boot Loader Problem(rEFIt & GRUB/LILO)

Hi,
I'm planning to "triple boot" my iMac with "Mac SL, Win 7, & openSUSE". But installing the "GRUB/LILO" makes my origanel boot loader rEFIt cannot work directly.
I have to select "Win 7/openSUSE" from the rEFIt, and select "WIn 7/openSUSE" again (from GRUB/LILO).
Any suggestion for fixing the problerm so I can boot straight to the OSes?
Thanks.

Boot from the solaris dvd in to singe user mode, mount the system under /a and run the instalgrub command in the shell:
/sbin/installgrub -m /boot/grub/stage1 /boot/grub/stage2 /dev/rdsk/c?d?s? (whatever your drive is).
Maybe make a backup copy of /a/boot/grub/menu.lst, I cant remember if it gets over written that way you can copy it back if necessary.

Installing Grub and grub-legacy side by side

Hello, I have Grub installed already in my arch machine. I need to install grub-legacy. Is there any way to install grub-legacy and both grub at a time? it's not needed that grub-legacy is active.
I don't want grub-legacy active. I just want it to installed in my machine, If it's installed as another name no problem. Why i needed to install is for cross compilation. I am cross compiling for another Embedded system.

arungupta2008 wrote:Can we download grub-legacy src files and then install it manually? by changing the names of bin. As ubuntu have done?
In Arch you should be using PKGBUILDs to compile and install packages. You need to edit https://aur.archlinux.org/packages/gr/g … y/PKGBUILD and apart from moving the files, you have to remove
conflicts=('grub')
too.

Boot into WDS from external PXE

Hi there,
in our Company (huge datacenter) we use ONE PXE-Bootmenu for ALL Servers (not managed by me) to boot into different deployment-systems (predominant Linux-Based deployments). Now we want to implement WDS (on Server 2012 R2) to boot into Windows-Deployment-Services.
Now I asked the Team which is managing the DHCP and PXE to add a new Option to the PXE-Bootmenu so we can boot into WDS. On that machine there is ONLY WDS-Service running.
What do they need to setup? Which file must be linked from the PXE-Menu? Which path? Do I have to make any additional settings on WDS?
When I search the web, I can only find infos how I can setup SYSLINUX on a Microsoft WDS, but not how to boot into WDS from an external PXE.
Please can someone help?
Regards
Miranda

I wasn't referring to the setup, but the menu. The menu and config files are the same regardless of what the host OS is. I posted it as a reference to how it is possible to boot WDS from PXELinux, but the specific example is where the WDS is on the same
server.
Chainloading is definately what is needed, but even that iPXE link is chainloading via HTTP (hence my Apache/IIS remark)... I do not know how you can PXE boot a WDS via HTTP.
Windows Server also has a WDSUTIL command that sends out a "browse" option with the PXE Boot request. The result ends up being you can press F11 or F9 instead of F12 and the client machine will search the network for PXE servers. This is how I
currently manage having multiple PXE servers. My default option is to press F12 to do a Legacy PXE boot to the main server, or use F11 if I want to boot to the Linux or UEFI server. See here for that example:
http://www.stephan-schwarz.net/?p=58
If Linux has a similar option, it could be used so you can choose a different PXE server. Otherwise, still have to research how to chainload to an external server, without using HTTP unless someone knows how to PXE boot WDS via HTTP.
EDIT: pxechn.c32 looks promising to add a menu option to chainload to another server:
http://www.syslinux.org/wiki/index.php/Pxechn.c32

/usr/bin changes and grub legacy

Hello,
Grub legacy is one of the packages that keeps its binaries in /sbin. I'm just wondering if this means that I have to replace grub legacy with another bootloader before I upgrade my system? I certainly wouldn't know how to update grub legacy so that the binaries are found in /usr/bin.
Thanks.

The reason to change to systemd is that the daemon scripts in /etc/rc.d are disappearing, as are hte /etc/conf.d stuff. It will break sooner or later (probably sooner) and I am actually really surprised it hasn't already. There is a reason why the news indicated that you should switch, as the old initscripts are not longer supported. That means more than just not getting updates, the files that make that work are slowly being pulled from the packages (and slowly in Arch is not very slow at all).
As for consolekit, it is an unmaintained piece of software. Its functionality has been replcaed by systemd's logind (quite successfully I mgith add) which is another reason why you should switch.
I'm not saying that you have to switch, as there are other alternatives out there that you could use. There is a whole thread on how to use openrc, and some stuff about using various other thigns as well, like runit or even the busybox init. But I have seen very little quality stuff in regard to maintenance of the old initscripts. Sticking with this is not something you should really want to do. I think in the end, you will end up with a much larger headache than simply ironing out any issues may have with moving to systemd.

Arch Linux Netboot Environment under grub legacy

I am trying to boot under grub legacy with the following menu.lst entry:
Arch Linux Netboot Environment
root (hd0,5)
kernel ipxe.krn
initrd conf.ipxe
boot
This does not work. Do you have any suggestion?
Last edited by francois.e (2013-01-07 02:49:52)

Indeed - more information is needed.
What is your partitioning scheme, is sda6 your /boot parition? Are your kernel and intrd in /boot/grub/? This would be unusual, but it is what that entry implies. Also, where is your root partition specified?
You also don't need the boot command in the menu.lst. I don't know if it would cause a problem, but I've never seen it there. In addition to the links in cfr's signature, you should (have already) read the wiki page on grub legacy.
Last edited by Trilby (2013-01-06 04:35:54)

Booting OS X from grub legacy

Similar Messages

Maybe you are looking for