Chainload Truecrypt bootloader on sda from Grub2 on sdb

Hi,
i have an installation where i installed windows 8 on /dev/sda1. I encrypted it with Truecrypt which installed it's bootloader to /dev/sda.
Then I have Arch on a luks-encrypted lva on /dev/sdb2, sdb1 is the /boot partition. Grub2 is installed to /dev/sdb.
This Setup works relatively well because i choose to what drive i want to boot from my bios on every startup. I'd like it more though, if i could chainload the Truecrypt-loader from Grub2.
I've found some instructions for this when both Systems are on the same drive, e.g. here: http://ubuntuforums.org/showthread.php? … st10015847
But since both systems are on different drives and have differnent MBRs, there must be a simpler solution?
Any idea how to achieve that chainloading of /dev/sda's truecrypt loader in an easier way?
Thanks
Michael

I can't speak for the Win 8 installer, but the Win 7 installer chokes if you install it (in GPT mode) onto a different hard drive to the one with your current EFI system partition (ESP). Assuming there's space, it'll annoyingly create a new 100MB ESP on the disk with the existing ESP on it, install it's EFI bootloader on to it, then report that it can't reboot to continue the installation.
You're better off doing what fukawi2 suggested, and unplugging the drive with Arch installed, install Windows onto the other drive, reconnect the Arch drive, and copy over the bootloader from one of the ESP to the other. It's what I ended up doing.
Or you can use a virtual machine, though you might not get the performance you'd like.

Similar Messages

Booting ISO from Grub2 without Loopback support

I am trying to boot an archlinux install ISO from grub2 menu, but I have no loopback support. I am not sure how I got to this point, but I installed Ubuntu first (just to test out the system and make sure that UEFI works fine. Then I booted the ISO file just fine, (I used grub-config to modify the bootup). During the install, I used cgdisk to redo my partition tables. After that, cgdisk said something about the partitions not taking effect until I rebooted... after reboot, I now get the grub console and nothing else. UEFI bios will not allow booting USB, so the only way I can do this is via this grub console.
The only things I did were; create a new partition at the end of the drive to store my ISO file and mkfs.ext4 /dev/sda2... The UEFI partition is still intact from ubuntu (i did not format that one).
I tried following this guide, http://wiki.grml.org/doku.php?id=rescueboot ,but it wasn't successful.
insmod part_msdos
insmod ext2
set root='(hd0,4)'
linux /arch/boot/x86_64/vmlinuz boot=live findiso=/archlinux-2014.01.05-dual.iso toram
initrd /arch/boot/x86_64/archiso.img
When I try to set the linux variables, i get an error that says /arch/boot/x86_64/vmlinuz cant be found.
I tried putting a livecd onto a usb drive, but when I get all of the parameters set and type boot, it just reboots the machine and goes right back to the grub console.
Any help would be greatly appreciated.

I really don't understand why you would go find some random guide and not check our wiki.

Boot 2011.08.19 installation media from grub2 via loopback

I have been trying to get the new installation media to boot from grub2 using loopback. The kernel and ramdisk load fine but it fails when it gets to the loopback mounting hook. I receive the following error message:
::Setup a loop device from iso/archlinux-2011.08.19-core-dual.iso located at device /dev/disk/by-label/MULTIBOOT
losetup: /dev/loop0: No suck file or directory
It then tries booting of of a CD, fails, and throws me to the minimal shell.
Has anyone gotten loopback booting of the install media working?
My grub2 entries are:
set drive_label=MULTIBOOT
menuentry "ArchLinux 2011.08.19 i686" {
set isofile="iso/archlinux-2011.08.19-core-dual.iso"
loopback loop /$isofile
echo 'loading kernel...'
linux (loop)/arch/boot/i686/vmlinuz lang=en locale=en_US.UTF-8 ramdisk_size=75% img_dev=/dev/disk/by-label/$drive_label img_loop=$isofile
echo 'loading ramdisk...'
initrd (loop)/arch/boot/i686/archiso.img
menuentry "ArchLinux 2011.08.19 x86_64" {
set isofile="iso/archlinux-2011.08.19-core-dual.iso"
loopback loop /$isofile
echo 'loading kernel...'
linux (loop)/arch/boot/x86_64/vmlinuz lang=en locale=en_US.UTF-8 ramdisk_size=75% img_dev=/dev/disk/by-label/$drive_label img_loop=$isofile
echo 'loading ramdisk...'
initrd (loop)/arch/boot/x86_64/archiso.img
Last edited by billyburly (2011-08-27 19:48:24)

You are welcome.
Oh, but in your case you also need to remaster iso. (I was think when I test these things directly with qemu, passing arguments -kernel/-initrd/-append )
mkdir -p /tmp/archlinux/{mnt,iso}
mount /path/to/your/archlinux-2011.08.19-core-dual.iso /tmp/archlinux/mnt
cp -a /tmp/archlinux/mnt/* /tmp/archlinux/iso
umount /tmp/archlinux/mnt
Now repack initramfs in /tmp/archlinux/iso/arch/boot/{i686,x86_64}/archiso.img
cd /tmp/archlinux/iso/arch
find -type f ! -name checksum.md5 -print0 | xargs -0 md5sum > checksum.md5
mkisofs -r -l \
-b isolinux/isolinux.bin -c isolinux/boot.cat \
-uid 0 -gid 0 \
-udf -allow-limited-size -iso-level 3 \
-input-charset utf-8 -p "prepared by mkarchiso" \
-no-emul-boot -boot-load-size 4 -boot-info-table \
-publisher "Arch Linux <http://www.archlinux.org>" \
-A "Arch Linux Live/Rescue CD" \
-V "ARCH_201108" \
-o "/tmp/archlinux/archlinux-2011.08.19-core-dual.iso" "/tmp/archlinux/iso"
isohybrid "/tmp/archlinux/archlinux-2011.08.19-core-dual.iso"
cd /tmp
rm -r /tmp/archlinux/iso
Good Luck.
Last edited by djgera (2011-08-27 23:02:20)

Error while deploying an sda from SDM.

Hi All
Am trying to deploy a sda file from SDM. But am getting this error during the deployment process
Caught exception during access of archive ...'the sda archive'
java.lang.NullPointerException
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).null)
What s/d be going wrong here??
Please help me on this.

Hi Bhupesh,
Have a look at this link...
http://help.sap.com/saphelp_nw04/helpdata/en/76/fb72ec091f4bf8a2d8ba321bb7e8d9/content.htm
It may help you in troubleshooting your problem
Hope it helps you.
Regards,
Maheswaran.B

Switching from GRUB2 to gummiboot

Hey everyone, just a quick question.
I currently use GRUB2 as a bootloader and, as the title would suggest, I wish to switch to gummiboot.
Currently, I have my EFI partition (/dev/sda1) mounted on /boot/efi, though the gummiboot wiki article says for best results, mount on /boot.
So I'm just wondering if what I do is just:
1) Replace /boot/efi with /boot in the /etc/fstab entry for /dev/sda1
2) # umount /dev/sda1
3) # mount /dev/sda1
4) # gummiboot install
Thanks in advance.

You don't have to put it on /boot. But there are a few things that are written into gummiboot that assume that it is going to be on /boot. I think that if you don't have it on /boot the automatic gummiboot update command in the install script won't run when the package is update. But this can be done automatically just like every other bootloader out there.
I actually wish the package didn't include that auto-updater. But I was unaware that it had been included when it showed up. It will also create an entry in your firmware automatically if you have efibootmgr installed, which I was not a fan of. In fact it took the 0000 spot which was previously the setup (entry to the bios), though it was recreated at 0011. I don't know if it will still do that, but it kind of bothered me.
Otherwise, I really do like gummiboot, it is super simple and for me it has been very reliable. Though there are a great number of people who have had issues with the efistub loader. But I just keep elilo around as a backup just in case.
So if you like things at /boot/efi then keep it that way. There is the advantage that yu can still keep the kernel on the root filesystem, enabling you to use bootloaders and boot managers that include drivers for common Linux filesystems. For example, rEFInd can locate and use kernels and initramfs' off of ext2, ext4, (I think ext3), reiserfs, hfs+ and iso9660.

One wallpaper from GRUB2 boot, to login (wihtout flickering)

I've been usage-testing arch for some time on my netbook-esque laptop (ultraportable?), and I'm happy to say that I have decided to stick with the beast! (Seriously, I lost track of time tweaking my system last night and went to bed in the wee hours of the morning!)
I've decided to take up the task of creating a "seamless" boot setup, while keeping things light -- basically making one background image stick to the screen from the bootup to the start of the x session while trying to avoid showing any. My setup is as follows:
1-- GRUB2 - used to set initial resolution (1366x768x24) and wallpaper (wallpaper.tga)
2-- **** I have all the problems here. I may put Splashscreen-solution: Splashy? fbsplash? Plymouth? ****
3-- SLiM with a modified theme using (a link to) wallpaper.png
4-- Openbox session with wallpaper and desktop icons set by pcmanfm
Currently, after selecting my grub entry, the wallpaper shamelessly disappears and is replaced by a black screen with some arch logos and console output for a moment before abruptly switching over to the all-black console output where all of the boot info is shown. Then it goes to tty login, then SLiM starts up...
I recall 3 times the console output "flickers" and changes: after I leave grub, there's the console with the archlogos, then there's the boot output console, then there's the tty login that waits on SLiM to startup. Can I just set background.png/tga for all of these console backgrounds during boot? (I may possibly remove SLiM if I can do that...) Do I HAVE to install a bootsplash app (like splashy fbsplash or plymouth) to get this desired behavior? If so will those apps set my background during the tty login prompt while SLiM loads up?

It's an old thread, but I can't see it has been solved. My try has been using the following setup: grub2, plymouth, systemd and lightdm.
I've tried to archieve this, using the following options:
/etc/default/grub:
The idea is to boot to tty7, the same as lightdm, so no VT switch makes things "ugly".
GRUB_CMDLINE_LINUX_DEFAULT="vt.handoff=7 quiet splash init=/usr/lib/systemd/systemd logo.nologo add_efi_memmap"
GRUB_GFXMODE=1280x800x32
GRUB_GFXPAYLOAD_LINUX=keep
GRUB_BACKGROUND="/boot/bg.png"
Systemd:
Enable lightdm-plymouth.service unit and disable any other greeter (kdm.service, gdm.service, lightdm.service, etc.)
/etc/lightdm/lightdm.conf:
greeter-user=lightdm
minimum-display-number=0
minimum-vt=7
run-directory=/run/lightdm
start-default-seat=true
With this setup I'm getting all three flicks, so it's not working as I'd like. I'm using a Dell Latitude E4300 with integrated graphics (Mobile Intel® GM45).

Removing grub from sda from mac internet recovery

So late night I tried to make a bootable Ubuntu DVD on my Mac.. This lead to messing up my bootloader I have been trying to fix it for hours the closest To fixing it was finding.
https://discussions.apple.com/thread/3109456?tstart=0
One person states
"Boot OSX and in the terminal write:
mkdir mnt ; sudo mount -t msdos /dev/disk0s1 mnt
Will show a new drive EFI
open this drive and open the folder EFI. Inside you will have the folders APPLE and UBUNTU
just delete the UBUNTU"
So I keep reading and see
"When in -Recovery From Internet- it is impossible to use mkdir, but you can "cd /tmp" and mount it there."
So I haven't been able to figure out how to mount disk0s1 in the /tmp. If someone could please show me the commands to get into the EFI Folder so I can delete the Ubuntu folder I would be a very happy person!!
Thanks again!

I finally resolved the problem in two steps.
Step 1 : remove "Boot Linux from HD"
you have to run the following command from a terminal window:
fdisk -u /dev/disk0
As ds store said, the suffix number might change depending on the configuration, apparently for a Macbook pro 5,4 with one disk, 0 seems to be the good guess
Step 2 : remove "Boot EFI\ubuntu\grubx64.efi from EFI"
This one is a bit more tricky, surely there is another way but this one is simple and not so risky
1- burn a GParted Live CD iso
2- boot on the GParted live CD (press alt on boot and wait for the CD boot option to appear) and choose the first boot entry
3- during the boot process accept every option with its default value
4- in GParted select the EFI partition and somewhere in the menus select the "flags" entry and uncheck "boot"
5- exit GParted Live CD and boot in Mac OS
6- a new volume has appeared "/volumes/efi"
in the finder go to "/volumes/efi/EFI" and delete the "ubuntu" folder
7- repeat steps 2/3 and step 4 but check "boot" instead of unchecking it
8- exit GParted live CD and reboot
9- enjoy
hope this will help someone in the future as i spend some time on it!

[Solved] Howto boot Windows 7 from grub2 and uefi?

I have added the following entry in my grub.cfg file..:
menuentry "Windows 7" {
insmod part_gpt
insmod fat
search --file --no-floppy --set=root /efi/Microsoft/Boot/bootmgfw.efi
chainloader ()/efi/Microsoft/Boot/bootmgfw.efi
But if I choose this entry, I get an error telling me "No such disk"
What am I missing?
Regards,
BTJ
Last edited by bjorntj (2011-09-13 08:41:42)

bjorntj wrote:
Thx...
BTJ
Mark the thread as [SOLVED].
Last edited by skodabenz (2011-09-13 08:39:14)

Boot arch netinstall iso from grub2

http://www.panticz.de/MultiBootUSB
I found this blog post and I successfully did it with linux mint but I couldn't do it with arch. what are the correct grub2 commands?
I tried with:
set root=(hd0,1)
loopback loop /arch.iso
linux (loop)/boot/vmlinuz26 iso-scan/filename=/arch.iso
initrd (loop)/boot/System.map26
I have no idea what System.map26 is and grub2 didn't choke when I offered it to him so I tried it. I couldn't find the normal initrd file.
Moreover, I know that there should be some boot=something parameter to the kernel in order for it to work but I couldn't guess the right one and I found no documentation about it.
If someone did it, I would appreciate your help
Thanks.

This is what I have:
menuentry "ArchLinux 2009-08 Core 64bit" {
set root=(hd0,1)
loopback loop /boot/iso/archlinux-2009.08-core-x86_64.iso
linux (loop)/boot/vmlinux26 iso-scan/filename=/boot/iso/archlinux-2009.08-core-x86_64.iso quiet
Get I get a "File not found" error.
*Edit*
I found /boot/grub/menu.lst (inside the iso) and found this:
title Boot Arch Linux Live CD
kernel /boot/vmlinuz26 lang=en locale=en_US.UTF-8 archisolabel=ARCHISO_KE1AECIE ramdisk_size=75%
initrd /boot/archiso_pata.img
There's the path for the initrd
*Edit #2*
"You need to load the kernel first." Well duh. You're supposed to do that grub.
Last edited by jordanwb (2009-11-10 19:37:19)

Fresh install of Arch on sda, need win8 on sdb

I'm running GPT and GRUB2. Is this about just adding the grub entry and fixing mbr?
I've been away for quite some time, now I need win8 for Civ5...luckily I have an extra HD to spare.

I can't speak for the Win 8 installer, but the Win 7 installer chokes if you install it (in GPT mode) onto a different hard drive to the one with your current EFI system partition (ESP). Assuming there's space, it'll annoyingly create a new 100MB ESP on the disk with the existing ESP on it, install it's EFI bootloader on to it, then report that it can't reboot to continue the installation.
You're better off doing what fukawi2 suggested, and unplugging the drive with Arch installed, install Windows onto the other drive, reconnect the Arch drive, and copy over the bootloader from one of the ESP to the other. It's what I ended up doing.
Or you can use a virtual machine, though you might not get the performance you'd like.

Dd to /dev/sda instead of /dev/sdb, how to restore /dev/sda

Hello,
yesterday I made a mistake, I did a dd to /dev/sda:
dd if=imagefile.img of=/dev/sda
Problem is my /dev/sda is my harddisk and it should have been /dev/sdb (usbstick).
Now my computer doesn't boot anymore.
How can I restore my harddisk without losing my data? The image file I copied was around 120MB.
Did dd than only overwrite the first 120MB or is there more?
Regards,
Roel

Thank You guys,
my arch-linux is up and running again in aprox. 1,5h time!!
First I tried to backup the harddisk with knoppix and saw my harddisk was empty, in gparted it seemed like it was never used... I was down, down, down... I didn't give up and downloaded systemrescuecd. Testdisk rstored my partition table and I saw it was my lucky day. The first partition on my harddrive was SWAP. All my files where intact and my stupid mistake only overwrote SWAP and MBR.
Reinstall grub would do the trick, i thought... but it didn't. Wy? Testdisk allocated my partitions to hda1 and hda2. In arch I had sda1 (swap); sda2 (/) and sda3 (/home). Now when I reinstalled grub the partition table didn't correspond to the ona in arch. A little bit fiddling in menu.lst, fstab and devices.map managed me to boot my arch system from fallback. My normal boot doesn't work though, I already changed everything to the right partitions but it keeps complaining about not finding my root partition. I already tried root=/dev/hda1; /sda1 and the whole rimram.
Can somebody tell me what's the problem?
It is probably my initrd file, isn't it?

[solved] Can grub2-efi chainload a bios target?

Hi,
my laptop runs arch in efi-mode which works fine for me for everyday use. However (its summer break) I would like to install windows for some gaming.
Since my internal hard drive is occupied by linux and data, I tried to install to an external hard drive, following this guide. To make matters worse, since there is no windows on my laptop, I did this using virtual box, which does not allow booting windows in uefi mode, so I'm stuck with a bios windows install on my external hard drive that I would like to chainload from grub2-efi. Is this possible, and if yes, how?
I tried the commands from the wiki page:
menuentry "Windows" {
set root=(hd1,1)
chainloader --force +1
but this gives me an error, saying that the efi path is invalid (not a big surprise)
Last edited by Mox (2013-08-05 17:33:24)

Okay, so is the windows installation on bare-metal or not? You say you did this via virtualbox, but that would imply that there is no reason to have to chainload from grub to bios mode. So I am a bit confused here. (And by bare-metal, I just mean not in a virtual machine image, I know that it is on an external drive at least).
I have not come across any documentation that suggests that this is a possibility from grub2-efi. That doesn't mean that there is no way to do this, but I do not think that there is a legitimate (read "supported") way to do this. rEFInd, Rod Smith's fork of rEFIt, is supposedly able to handle the bios boot sector, but it is not totally reliable unless you are using a Mac, for which this functionality was actually designed.
I have seen tutorials about how to convert windows from bios to UEFI or vice versa though. So that may be an option.
On my system, I can set the machine to use both UEFI and bios modes at the same time. It then also gives me a choice of which should be the preferred method in the event that both methods are available. So if I were to have this setup, where Linux (or whatever) is configured to boot with UEFI, and another operating system (not just limited to windows) is configured to use bios mode, then I could quite easily make both available. What I would need to do is to configure the system to use my UEFI bootloader using a firmware entry. That is it would need a direct nvram entry created using something like efibootmgr. Then I would set the bios to use 'both" (UEFI and legacy bios) and give preference to legacy bios. That way I could select that created entry to boot the UEFI thing (in your case grub-efi), while also having the option of booting from the disk itself to get to the bios booting OS.
But unfortunately, every firmware is different, and I have heard of many machines that don't offer such functioanlity. This method would also require that I would have to potentially deal with two boot managers. So I could hold (on my machine) F12 and select the windows disk, or let it boot the default UEFI entry and get grub (or gummiboot in my case).

[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.

Config Grub2 + winxp + win7 (loader or not)

Hi everyone!
Im new as user, not only in the Arch Linux but also in the forums. So far (few months), no problems with the distro, everything perfect, but i have an issue with Loaders.
I have been testing several things, following the wiki and i don't know how to solve it.
My fdisk -l
Device Boot Start End Blocks Id System
/dev/sda1 * 2048 139681791 69839872 7 HPFS/NTFS/exFAT
/dev/sda2 139681792 180641791 20480000 7 HPFS/NTFS/exFAT
/dev/sda3 180641792 242081791 30720000 5 Extended
/dev/sda4 242081792 976773119 367345664 7 HPFS/NTFS/exFAT
/dev/sda5 180643840 239982591 29669376 83 Linux
/dev/sda6 239984640 242081791 1048576 82 Linux swap / Solaris
sda1 only Windows 7
sda2 only Windows xp (latest in format and install)
sda4 ntfs for data
sda5 arch linux
sda6 swap
So far i only can do two things: or working windows but not linux, or linux but not windows.
TO recover the MBR of Windows (because from Linux i cannot access in the WIndows Loader from grub menu), insert recovery cd xp, and i do:
fixboot (over C:)
fixmbr
copy F:\I386\NTDLR D:\
copy F:\I386\NTDETECT.COM D:\
F is CDROM y D is the partition with windows xp (i do this because if not later i get errors to go to windows).
reboot, and it works the windows, but i lost the GRUB2 loader.
If i want to recover the grub, i insert archlinux live and do:
mkdir /mnt/
mkdir /mnt/arch
mount /dev/sda5 /mnt/arch
cd /mnt/arch
mount -o bind /dev dev/
mount -t proc proc proc/
mount -t sysfs sys sys/
chroot . /bin/bash
grub-install /dev/sda
And i recover grub and the linux, but i cannot access again to windows loader...
How can i solve it? I think that when i do grub-install it destroys the before MBR, and i would like to preserve or move to other side to allow after that that Grub Loader can access to NTLDR (before MBR) through WIndows Loader entry.
I have also tried another alternative that appears here: https://wiki.archlinux.org/index.php/Gr … ot_in_BIOS
Trying to avoid the WIndows Loader and put the two entries specifically in Grub Loader.
I do the process and add to /etc/grub.d/40_custom
#Windows 7
menuentry "Microsoft Windows 7 BIOS-MBR" {
insmod part_msdos
insmod ntfs
insmod search_fs_uuid
insmod ntldr
search --fs-uuid --no-floppy --set=root --hint-bios=hd0,msdos1 --hint-efi=hd0,msdos1 --hint-baremetal=ahci0,msdos1 5950F0AB218845D1
ntldr /bootmgr
menuentry "Microsoft Windows XP" {
insmod part_msdos
insmod ntfs
insmod search_fs_uuid
insmod ntldr
search --fs-uuid --no-floppy --set=root --hint-bios=hd0,msdos2 --hint-efi=hd0,msdos2 --hint-baremetal=ahci0,msdos2 F0FC4E7EFC4E3EDA
ntldr /ntldr
Then, grub-mkconfig but when i reboot, they don't appear.
Another test i have done is change the chainloader from this:
#Windows 7 Loader
menuentry "Windows Loader" {
set root=(hd0,0)
chainloader (hd0,0)+1
To this:
#Windows 7 Loader
menuentry "Windows Loader" {
set root=(hd0,1)
chainloader (hd0,1)+1
But nothing. I don't know if there is any way to move the NTLDR (Windows Loader for xp and 7) e.g. to /dev/sda2, and in /dev/sda1 allocated the MBR that points to GRUB2, and then from GRUB2 in Windows Loader, a pointer to /dev/sda2 NTLDR. I don't know if it works like that.
Any help?
Last edited by Zzipo (2013-01-07 22:11:01)

Boot Info Script 0.61 [1 April 2012]
============================= Boot Info Summary: ===============================
=> Grub2 (v1.99) is installed in the MBR of /dev/sda and looks at sector 1 of
the same hard drive for core.img. core.img is at this location and looks
in partition 99 for .
sda1: __________________________________________________________________________
File system: ntfs
Boot sector type: Windows XP: NTFS
Boot sector info: No errors found in the Boot Parameter Block.
Operating System: Windows 7
Boot files: /boot.ini /bootmgr /Boot/BCD
/Windows/System32/winload.exe /ntldr /NTDETECT.COM
sda2: __________________________________________________________________________
File system: ntfs
Boot sector type: Windows XP: NTFS
Boot sector info: No errors found in the Boot Parameter Block.
Operating System: Windows XP
Boot files: /NTLDR /NTDETECT.COM
sda3: __________________________________________________________________________
File system: Extended Partition
Boot sector type: Unknown
Boot sector info:
sda5: __________________________________________________________________________
File system: ext4
Boot sector type: -
Boot sector info:
Operating System: Arch Linux ()
Boot files: /boot/grub/grub.cfg /etc/fstab /etc/lilo.conf
/boot/syslinux/syslinux.cfg
sda6: __________________________________________________________________________
File system: swap
Boot sector type: -
Boot sector info:
sda4: __________________________________________________________________________
File system: ntfs
Boot sector type: Windows Vista/7: NTFS
Boot sector info: No errors found in the Boot Parameter Block.
Operating System:
Boot files:
============================ Drive/Partition Info: =============================
Drive: sda _____________________________________________________________________
Disk /dev/sda: 500.1 GB, 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
Partition Boot Start Sector End Sector # of Sectors Id System
/dev/sda1 * 2,048 139,681,791 139,679,744 7 NTFS / exFAT / HPFS
/dev/sda2 139,681,792 180,641,791 40,960,000 7 NTFS / exFAT / HPFS
/dev/sda3 180,641,792 242,081,791 61,440,000 5 Extended
/dev/sda5 180,643,840 239,982,591 59,338,752 83 Linux
/dev/sda6 239,984,640 242,081,791 2,097,152 82 Linux swap / Solaris
/dev/sda4 242,081,792 976,773,119 734,691,328 7 NTFS / exFAT / HPFS
"blkid" output: ________________________________________________________________
Device UUID TYPE LABEL
/dev/sda1 5950F0AB218845D1 ntfs Juegos
/dev/sda2 F0FC4E7EFC4E3EDA ntfs
/dev/sda4 25EF7EEE7BF9CEE0 ntfs Datos
/dev/sda5 d24b6d6c-53ae-4559-b453-ab085e2625a6 ext4
/dev/sda6 c66e6518-27a5-46ab-8063-b8675049d58f swap
================================ Mount points: =================================
Device Mount_Point Type Options
/dev/sda4 /media/Datos fuseblk (rw,nosuid,nodev,relatime,user_id=0,group_id=0,allow_other,blksize=4096)
/dev/sda5 / ext4 (rw,relatime,data=ordered)
================================ sda1/boot.ini: ================================
[boot loader]
timeout=30
default=multi(0)disk(0)rdisk(0)partition(2)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(2)\WINDOWS="Windows XP Professional" /fastdetect
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Professional" /noexecute=optin /fastdetect
=========================== sda5/boot/grub/grub.cfg: ===========================
# DO NOT EDIT THIS FILE
# It is automatically generated by grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
### BEGIN /etc/grub.d/00_header ###
insmod part_gpt
insmod part_msdos
if [ -s $prefix/grubenv ]; then
load_env
fi
set default="0"
if [ x"${feature_menuentry_id}" = xy ]; then
menuentry_id_option="--id"
else
menuentry_id_option=""
fi
export menuentry_id_option
if [ "${prev_saved_entry}" ]; then
set saved_entry="${prev_saved_entry}"
save_env saved_entry
set prev_saved_entry=
save_env prev_saved_entry
set boot_once=true
fi
function savedefault {
if [ -z "${boot_once}" ]; then
saved_entry="${chosen}"
save_env saved_entry
fi
function load_video {
if [ x$feature_all_video_module = xy ]; then
insmod all_video
else
insmod efi_gop
insmod efi_uga
insmod ieee1275_fb
insmod vbe
insmod vga
insmod video_bochs
insmod video_cirrus
fi
if [ x$feature_default_font_path = xy ] ; then
font=unicode
else
insmod part_msdos
insmod ext2
set root='hd0,msdos5'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos5 --hint-efi=hd0,msdos5 --hint-baremetal=ahci0,msdos5 d24b6d6c-53ae-4559-b453-ab085e2625a6
else
search --no-floppy --fs-uuid --set=root d24b6d6c-53ae-4559-b453-ab085e2625a6
fi
font="/usr/share/grub/unicode.pf2"
fi
if loadfont $font ; then
set gfxmode=auto
load_video
insmod gfxterm
set locale_dir=$prefix/locale
set lang=es_ES
insmod gettext
fi
terminal_input console
terminal_output gfxterm
set timeout=5
### END /etc/grub.d/00_header ###
### BEGIN /etc/grub.d/10_linux ###
menuentry 'Arch GNU/Linux, with Linux core repo kernel' --class arch --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-core repo kernel-true-d24b6d6c-
53ae-4559-b453-ab085e2625a6' {
load_video
set gfxpayload=keep
insmod gzio
insmod part_msdos
insmod ext2
set root='hd0,msdos5'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos5 --hint-efi=hd0,msdos5 --hint-baremetal=ahci0,msdos5 d24b6d6c-53ae-4559-b453-ab085e2625a6
else
search --no-floppy --fs-uuid --set=root d24b6d6c-53ae-4559-b453-ab085e2625a6
fi
echo 'Loading Linux core repo kernel ...'
linux /boot/vmlinuz-linux root=UUID=d24b6d6c-53ae-4559-b453-ab085e2625a6 ro quiet
echo 'Loading initial ramdisk ...'
initrd /boot/initramfs-linux.img
menuentry 'Arch GNU/Linux, with Linux core repo kernel (Fallback initramfs)' --class arch --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-core repo
kernel-fallback-d24b6d6c-53ae-4559-b453-ab085e2625a6' {
load_video
set gfxpayload=keep
insmod gzio
insmod part_msdos
insmod ext2
set root='hd0,msdos5'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos5 --hint-efi=hd0,msdos5 --hint-baremetal=ahci0,msdos5 d24b6d6c-53ae-4559-b453-ab085e2625a6
else
search --no-floppy --fs-uuid --set=root d24b6d6c-53ae-4559-b453-ab085e2625a6
fi
echo 'Loading Linux core repo kernel ...'
linux /boot/vmlinuz-linux root=UUID=d24b6d6c-53ae-4559-b453-ab085e2625a6 ro quiet
echo 'Loading initial ramdisk ...'
initrd /boot/initramfs-linux-fallback.img
### END /etc/grub.d/10_linux ###
### BEGIN /etc/grub.d/20_linux_xen ###
### END /etc/grub.d/20_linux_xen ###
### BEGIN /etc/grub.d/20_memtest86+ ###
### END /etc/grub.d/20_memtest86+ ###
### BEGIN /etc/grub.d/30_os-prober ###
### END /etc/grub.d/30_os-prober ###
### BEGIN /etc/grub.d/40_custom ###
# This file provides an easy way to add custom menu entries. Simply type the
# menu entries you want to add after this comment. Be careful not to change
# the 'exec tail' line above.
#Windows 7 Loader
menuentry "Windows Loader" {
set root=(hd0,2)
chainloader (hd0,2)+1
### END /etc/grub.d/40_custom ###
### BEGIN /etc/grub.d/41_custom ###
if [ -f ${config_directory}/custom.cfg ]; then
source ${config_directory}/custom.cfg
elif [ -z "${config_directory}" -a -f $prefix/custom.cfg ]; then
source $prefix/custom.cfg;
fi
### END /etc/grub.d/41_custom ###
=============================== sda5/etc/fstab: ================================
# /etc/fstab: static file system information
# <file system> <dir> <type> <options> <dump> <pass>
tmpfs /tmp tmpfs nodev,nosuid 0 0
# UUID=d24b6d6c-53ae-4559-b453-ab085e2625a6
/dev/sda5 / ext4 rw,relatime,data=ordered 0 1
# UUID=B2A1-1615
#/dev/sdc1 /media/pen vfat rw,relatime,fmask=0022,dmask=0022,codepage=cp437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro 0 2
# UUID=c66e6518-27a5-46ab-8063-b8675049d58f
/dev/sda6 none swap defaults 0 0
/dev/sda4 /media/Datos ntfs-3g rw,relatime,auto 0 1
============================= sda5/etc/lilo.conf: ==============================
# /etc/lilo.conf
boot=/dev/hda
# This line often fixes L40 errors on bootup
# disk=/dev/hda bios=0x80
default=arch
timeout=50
lba32
prompt
image=/boot/vmlinuz-linux
label=arch
root=/dev/hda3
initrd=/boot/initramfs-linux.img
read-only
image=/boot/vmlinuz-linux
label=arch-fallback
root=/dev/hda3
initrd=/boot/initramfs-linux-fallback.img
read-only
#other=/dev/hda1
# label=dos
======================= sda5/boot/syslinux/syslinux.cfg: =======================
# Config file for Syslinux -
# /boot/syslinux/syslinux.cfg
# Comboot modules:
# * menu.c32 - provides a text menu
# * vesamenu.c32 - provides a graphical menu
# * chain.c32 - chainload MBRs, partition boot sectors, Windows bootloaders
# * hdt.c32 - hardware detection tool
# * reboot.c32 - reboots the system
# * poweroff.com - shutdown the system
# To Use: Copy the respective files from /usr/lib/syslinux to /boot/syslinux.
# If /usr and /boot are on the same file system, symlink the files instead
# of copying them.
# If you do not use a menu, a 'boot:' prompt will be shown and the system
# will boot automatically after 5 seconds.
# Please review the wiki: [url]https://wiki.archlinux.org/index.php/Syslinux[/url]
# The wiki provides further configuration examples
DEFAULT arch
PROMPT 0 # Set to 1 if you always want to display the boot: prompt
TIMEOUT 50
# You can create syslinux keymaps with the keytab-lilo tool
#KBDMAP de.ktl
# Menu Configuration
# Either menu.c32 or vesamenu32.c32 must be copied to /boot/syslinux
UI menu.c32
#UI vesamenu.c32
# Refer to [url]http://syslinux.zytor.com/wiki/index.php/Doc/menu[/url]
MENU TITLE Arch Linux
#MENU BACKGROUND splash.png
MENU COLOR border 30;44 #40ffffff #a0000000 std
MENU COLOR title 1;36;44 #9033ccff #a0000000 std
MENU COLOR sel 7;37;40 #e0ffffff #20ffffff all
MENU COLOR unsel 37;44 #50ffffff #a0000000 std
MENU COLOR help 37;40 #c0ffffff #a0000000 std
MENU COLOR timeout_msg 37;40 #80ffffff #00000000 std
MENU COLOR timeout 1;37;40 #c0ffffff #00000000 std
MENU COLOR msg07 37;40 #90ffffff #a0000000 std
MENU COLOR tabmsg 31;40 #30ffffff #00000000 std
# boot sections follow
# TIP: If you want a 1024x768 framebuffer, add "vga=773" to your kernel line.
LABEL arch
MENU LABEL Arch Linux
LINUX ../vmlinuz-linux
APPEND root=/dev/sda3 ro
INITRD ../initramfs-linux.img
LABEL archfallback
MENU LABEL Arch Linux Fallback
LINUX ../vmlinuz-linux
APPEND root=/dev/sda3 ro
INITRD ../initramfs-linux-fallback.img
#LABEL windows
# MENU LABEL Windows
# COM32 chain.c32
# APPEND hd0 1
LABEL hdt
MENU LABEL HDT (Hardware Detection Tool)
COM32 hdt.c32
LABEL reboot
MENU LABEL Reboot
COM32 reboot.c32
LABEL off
MENU LABEL Power Off
COMBOOT poweroff.com
=================== sda5: Location of files loaded by Grub: ====================
GiB - GB File Fragment(s)
90.323257446 = 96.983859200 boot/grub/grub.cfg 1
112.360614777 = 120.646291456 boot/initramfs-linux-fallback.img 1
87.491901398 = 93.943713792 boot/initramfs-linux.img 1
110.640808105 = 118.799663104 boot/vmlinuz-linux 1
================= sda5: Location of files loaded by Syslinux: ==================
GiB - GB File Fragment(s)
98.263214111 = 105.509322752 boot/syslinux/syslinux.cfg 1
======================== Unknown MBRs/Boot Sectors/etc: ========================
Unknown BootLoader on sda3
00000000 96 6f 4e 5e d0 3b 99 1c 18 98 de 4a ca 47 ed 0a |.oN^.;.....J.G..|
00000010 72 79 71 b5 e0 5d 2c f5 c1 71 de d9 63 04 84 c7 |ryq..],..q..c...|
00000020 b2 6f 3e a3 5f 99 1b a0 2d 78 17 ad fb 69 ee c2 |.o>._...-x...i..|
00000030 a9 4e 96 33 a1 1c c3 80 06 ee 22 f1 be 5a 06 62 |.N.3......"..Z.b|
00000040 c8 8f 6f d6 bb cf 7e 12 c0 d8 5b 90 85 95 ff 1e |..o...~...[.....|
00000050 80 fa ea 89 d5 aa e6 cd b5 ed 01 93 24 05 fb 81 |............$...|
00000060 00 00 0c f6 08 00 00 e8 01 42 5c 00 00 00 00 af |.........B\.....|
00000070 01 21 0c 4f bf ff ff ff ff fe a9 c2 61 50 91 84 |.!.O........aP..|
00000080 64 11 09 04 7e 37 1d 71 aa 99 ed 37 5a 9e 6b 61 |d...~7.q...7Z.ka|
00000090 75 ca f9 b6 d2 eb 89 47 14 ba be bc b6 1e c7 fc |u......G........|
000000a0 7f 36 30 c5 54 f6 c5 9d dc e4 e7 1a af 69 4e bc |.60.T........iN.|
000000b0 12 94 d0 81 d2 f1 a9 4d d4 6f b1 25 e8 0f dc a2 |.......M.o.%....|
000000c0 e8 de 64 84 c5 a4 67 32 95 c0 00 51 27 70 0b 08 |..d...g2...Q'p..|
000000d0 82 f6 02 e0 80 02 c1 00 05 a6 0a 00 22 16 00 5c |............"..\|
000000e0 00 99 20 05 00 04 40 00 00 25 4a e1 60 a0 48 c2 |.. ...@..%J.`.H.|
000000f0 62 08 fc 4e b8 be ab 5b f3 51 c5 ca c8 bb ad 97 |b..N...[.Q......|
00000100 b9 59 17 37 24 c8 4b 6a f5 c8 7e 21 68 d0 52 ba |.Y.7$.Kj..~!h.R.|
00000110 dc ae 15 ed 16 8d 48 c7 21 12 e8 1c 9c 6f 44 bb |......H.!....oD.|
00000120 16 82 f5 23 69 e7 09 f7 25 45 55 93 08 b9 44 c5 |...#i...%EU...D.|
00000130 8a 09 b1 16 9c 80 05 2c 2b 31 0a c4 50 13 00 27 |.......,+1..P..'|
00000140 40 12 54 09 00 02 40 a0 02 f3 00 98 01 30 50 01 |@[email protected].|
00000150 10 14 00 01 70 01 c0 00 00 00 f3 08 00 00 e5 01 |....p...........|
00000160 42 73 00 00 00 00 af 01 21 2c 4f ff ff ff ff ff |Bs......!,O.....|
00000170 fe a6 02 61 40 91 87 e9 6b 89 d6 aa b8 bc b4 f3 |[email protected].......|
00000180 b9 55 14 cd 65 65 4a ae 12 a5 8b 4b bf a7 20 be |.U..eeJ....K.. .|
00000190 97 e8 79 05 32 cb 1b 76 c6 34 a5 99 6d 7e 48 dd |..y.2..v.4..m~H.|
000001a0 b9 d6 1c 46 51 c9 06 49 2d 05 b0 05 63 64 62 50 |...FQ..I-...cdbP|
000001b0 bc 65 05 9b 83 18 98 1c 20 7e 00 13 28 81 00 fe |.e...... ~..(...|
000001c0 ff ff 83 fe ff ff 00 08 00 00 00 70 89 03 00 fe |...........p....|
000001d0 ff ff 05 fe ff ff 00 78 89 03 00 08 20 00 00 00 |.......x.... ...|
000001e0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
000001f0 00 00 00 00 00 00 00 Boot Info Script 0.61 [1 April 2012]
============================= Boot Info Summary: ===============================
=> Grub2 (v1.99) is installed in the MBR of /dev/sda and looks at sector 1 of
the same hard drive for core.img. core.img is at this location and looks
in partition 99 for .
sda1: __________________________________________________________________________
File system: ntfs
Boot sector type: Windows XP: NTFS
Boot sector info: No errors found in the Boot Parameter Block.
Operating System: Windows 7
Boot files: /boot.ini /bootmgr /Boot/BCD
/Windows/System32/winload.exe /ntldr /NTDETECT.COM
sda2: __________________________________________________________________________
File system: ntfs
Boot sector type: Windows XP: NTFS
Boot sector info: No errors found in the Boot Parameter Block.
Operating System: Windows XP
Boot files: /NTLDR /NTDETECT.COM
sda3: __________________________________________________________________________
File system: Extended Partition
Boot sector type: Unknown
Boot sector info:
sda5: __________________________________________________________________________
File system: ext4
Boot sector type: -
Boot sector info:
Operating System: Arch Linux ()
Boot files: /boot/grub/grub.cfg /etc/fstab /etc/lilo.conf
/boot/syslinux/syslinux.cfg
sda6: __________________________________________________________________________
File system: swap
Boot sector type: -
Boot sector info:
sda4: __________________________________________________________________________
File system: ntfs
Boot sector type: Windows Vista/7: NTFS
Boot sector info: No errors found in the Boot Parameter Block.
Operating System:
Boot files:
============================ Drive/Partition Info: =============================
Drive: sda _____________________________________________________________________
Disk /dev/sda: 500.1 GB, 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
Partition Boot Start Sector End Sector # of Sectors Id System
/dev/sda1 * 2,048 139,681,791 139,679,744 7 NTFS / exFAT / HPFS
/dev/sda2 139,681,792 180,641,791 40,960,000 7 NTFS / exFAT / HPFS
/dev/sda3 180,641,792 242,081,791 61,440,000 5 Extended
/dev/sda5 180,643,840 239,982,591 59,338,752 83 Linux
/dev/sda6 239,984,640 242,081,791 2,097,152 82 Linux swap / Solaris
/dev/sda4 242,081,792 976,773,119 734,691,328 7 NTFS / exFAT / HPFS
"blkid" output: ________________________________________________________________
Device UUID TYPE LABEL
/dev/sda1 5950F0AB218845D1 ntfs Juegos
/dev/sda2 F0FC4E7EFC4E3EDA ntfs
/dev/sda4 25EF7EEE7BF9CEE0 ntfs Datos
/dev/sda5 d24b6d6c-53ae-4559-b453-ab085e2625a6 ext4
/dev/sda6 c66e6518-27a5-46ab-8063-b8675049d58f swap
================================ Mount points: =================================
Device Mount_Point Type Options
/dev/sda4 /media/Datos fuseblk (rw,nosuid,nodev,relatime,user_id=0,group_id=0,allow_other,blksize=4096)
/dev/sda5 / ext4 (rw,relatime,data=ordered)
================================ sda1/boot.ini: ================================
[boot loader]
timeout=30
default=multi(0)disk(0)rdisk(0)partition(2)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(2)\WINDOWS="Windows XP Professional" /fastdetect
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Professional" /noexecute=optin /fastdetect
=========================== sda5/boot/grub/grub.cfg: ===========================
# DO NOT EDIT THIS FILE
# It is automatically generated by grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
### BEGIN /etc/grub.d/00_header ###
insmod part_gpt
insmod part_msdos
if [ -s $prefix/grubenv ]; then
load_env
fi
set default="0"
if [ x"${feature_menuentry_id}" = xy ]; then
menuentry_id_option="--id"
else
menuentry_id_option=""
fi
export menuentry_id_option
if [ "${prev_saved_entry}" ]; then
set saved_entry="${prev_saved_entry}"
save_env saved_entry
set prev_saved_entry=
save_env prev_saved_entry
set boot_once=true
fi
function savedefault {
if [ -z "${boot_once}" ]; then
saved_entry="${chosen}"
save_env saved_entry
fi
function load_video {
if [ x$feature_all_video_module = xy ]; then
insmod all_video
else
insmod efi_gop
insmod efi_uga
insmod ieee1275_fb
insmod vbe
insmod vga
insmod video_bochs
insmod video_cirrus
fi
if [ x$feature_default_font_path = xy ] ; then
font=unicode
else
insmod part_msdos
insmod ext2
set root='hd0,msdos5'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos5 --hint-efi=hd0,msdos5 --hint-baremetal=ahci0,msdos5 d24b6d6c-53ae-4559-b453-ab085e2625a6
else
search --no-floppy --fs-uuid --set=root d24b6d6c-53ae-4559-b453-ab085e2625a6
fi
font="/usr/share/grub/unicode.pf2"
fi
if loadfont $font ; then
set gfxmode=auto
load_video
insmod gfxterm
set locale_dir=$prefix/locale
set lang=es_ES
insmod gettext
fi
terminal_input console
terminal_output gfxterm
set timeout=5
### END /etc/grub.d/00_header ###
### BEGIN /etc/grub.d/10_linux ###
menuentry 'Arch GNU/Linux, with Linux core repo kernel' --class arch --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-core repo kernel-true-d24b6d6c-
53ae-4559-b453-ab085e2625a6' {
load_video
set gfxpayload=keep
insmod gzio
insmod part_msdos
insmod ext2
set root='hd0,msdos5'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos5 --hint-efi=hd0,msdos5 --hint-baremetal=ahci0,msdos5 d24b6d6c-53ae-4559-b453-ab085e2625a6
else
search --no-floppy --fs-uuid --set=root d24b6d6c-53ae-4559-b453-ab085e2625a6
fi
echo 'Loading Linux core repo kernel ...'
linux /boot/vmlinuz-linux root=UUID=d24b6d6c-53ae-4559-b453-ab085e2625a6 ro quiet
echo 'Loading initial ramdisk ...'
initrd /boot/initramfs-linux.img
menuentry 'Arch GNU/Linux, with Linux core repo kernel (Fallback initramfs)' --class arch --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-core repo
kernel-fallback-d24b6d6c-53ae-4559-b453-ab085e2625a6' {
load_video
set gfxpayload=keep
insmod gzio
insmod part_msdos
insmod ext2
set root='hd0,msdos5'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos5 --hint-efi=hd0,msdos5 --hint-baremetal=ahci0,msdos5 d24b6d6c-53ae-4559-b453-ab085e2625a6
else
search --no-floppy --fs-uuid --set=root d24b6d6c-53ae-4559-b453-ab085e2625a6
fi
echo 'Loading Linux core repo kernel ...'
linux /boot/vmlinuz-linux root=UUID=d24b6d6c-53ae-4559-b453-ab085e2625a6 ro quiet
echo 'Loading initial ramdisk ...'
initrd /boot/initramfs-linux-fallback.img
### END /etc/grub.d/10_linux ###
### BEGIN /etc/grub.d/20_linux_xen ###
### END /etc/grub.d/20_linux_xen ###
### BEGIN /etc/grub.d/20_memtest86+ ###
### END /etc/grub.d/20_memtest86+ ###
### BEGIN /etc/grub.d/30_os-prober ###
### END /etc/grub.d/30_os-prober ###
### BEGIN /etc/grub.d/40_custom ###
# This file provides an easy way to add custom menu entries. Simply type the
# menu entries you want to add after this comment. Be careful not to change
# the 'exec tail' line above.
#Windows 7 Loader
menuentry "Windows Loader" {
set root=(hd0,2)
chainloader (hd0,2)+1
### END /etc/grub.d/40_custom ###
### BEGIN /etc/grub.d/41_custom ###
if [ -f ${config_directory}/custom.cfg ]; then
source ${config_directory}/custom.cfg
elif [ -z "${config_directory}" -a -f $prefix/custom.cfg ]; then
source $prefix/custom.cfg;
fi
### END /etc/grub.d/41_custom ###
=============================== sda5/etc/fstab: ================================
# /etc/fstab: static file system information
# <file system> <dir> <type> <options> <dump> <pass>
tmpfs /tmp tmpfs nodev,nosuid 0 0
# UUID=d24b6d6c-53ae-4559-b453-ab085e2625a6
/dev/sda5 / ext4 rw,relatime,data=ordered 0 1
# UUID=B2A1-1615
#/dev/sdc1 /media/pen vfat rw,relatime,fmask=0022,dmask=0022,codepage=cp437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro 0 2
# UUID=c66e6518-27a5-46ab-8063-b8675049d58f
/dev/sda6 none swap defaults 0 0
/dev/sda4 /media/Datos ntfs-3g rw,relatime,auto 0 1
============================= sda5/etc/lilo.conf: ==============================
# /etc/lilo.conf
boot=/dev/hda
# This line often fixes L40 errors on bootup
# disk=/dev/hda bios=0x80
default=arch
timeout=50
lba32
prompt
image=/boot/vmlinuz-linux
label=arch
root=/dev/hda3
initrd=/boot/initramfs-linux.img
read-only
image=/boot/vmlinuz-linux
label=arch-fallback
root=/dev/hda3
initrd=/boot/initramfs-linux-fallback.img
read-only
#other=/dev/hda1
# label=dos
======================= sda5/boot/syslinux/syslinux.cfg: =======================
# Config file for Syslinux -
# /boot/syslinux/syslinux.cfg
# Comboot modules:
# * menu.c32 - provides a text menu
# * vesamenu.c32 - provides a graphical menu
# * chain.c32 - chainload MBRs, partition boot sectors, Windows bootloaders
# * hdt.c32 - hardware detection tool
# * reboot.c32 - reboots the system
# * poweroff.com - shutdown the system
# To Use: Copy the respective files from /usr/lib/syslinux to /boot/syslinux.
# If /usr and /boot are on the same file system, symlink the files instead
# of copying them.
# If you do not use a menu, a 'boot:' prompt will be shown and the system
# will boot automatically after 5 seconds.
# Please review the wiki: [url]https://wiki.archlinux.org/index.php/Syslinux[/url]
# The wiki provides further configuration examples
DEFAULT arch
PROMPT 0 # Set to 1 if you always want to display the boot: prompt
TIMEOUT 50
# You can create syslinux keymaps with the keytab-lilo tool
#KBDMAP de.ktl
# Menu Configuration
# Either menu.c32 or vesamenu32.c32 must be copied to /boot/syslinux
UI menu.c32
#UI vesamenu.c32
# Refer to [url]http://syslinux.zytor.com/wiki/index.php/Doc/menu[/url]
MENU TITLE Arch Linux
#MENU BACKGROUND splash.png
MENU COLOR border 30;44 #40ffffff #a0000000 std
MENU COLOR title 1;36;44 #9033ccff #a0000000 std
MENU COLOR sel 7;37;40 #e0ffffff #20ffffff all
MENU COLOR unsel 37;44 #50ffffff #a0000000 std
MENU COLOR help 37;40 #c0ffffff #a0000000 std
MENU COLOR timeout_msg 37;40 #80ffffff #00000000 std
MENU COLOR timeout 1;37;40 #c0ffffff #00000000 std
MENU COLOR msg07 37;40 #90ffffff #a0000000 std
MENU COLOR tabmsg 31;40 #30ffffff #00000000 std
# boot sections follow
# TIP: If you want a 1024x768 framebuffer, add "vga=773" to your kernel line.
LABEL arch
MENU LABEL Arch Linux
LINUX ../vmlinuz-linux
APPEND root=/dev/sda3 ro
INITRD ../initramfs-linux.img
LABEL archfallback
MENU LABEL Arch Linux Fallback
LINUX ../vmlinuz-linux
APPEND root=/dev/sda3 ro
INITRD ../initramfs-linux-fallback.img
#LABEL windows
# MENU LABEL Windows
# COM32 chain.c32
# APPEND hd0 1
LABEL hdt
MENU LABEL HDT (Hardware Detection Tool)
COM32 hdt.c32
LABEL reboot
MENU LABEL Reboot
COM32 reboot.c32
LABEL off
MENU LABEL Power Off
COMBOOT poweroff.com
=================== sda5: Location of files loaded by Grub: ====================
GiB - GB File Fragment(s)
90.323257446 = 96.983859200 boot/grub/grub.cfg 1
112.360614777 = 120.646291456 boot/initramfs-linux-fallback.img 1
87.491901398 = 93.943713792 boot/initramfs-linux.img 1
110.640808105 = 118.799663104 boot/vmlinuz-linux 1
================= sda5: Location of files loaded by Syslinux: ==================
GiB - GB File Fragment(s)
98.263214111 = 105.509322752 boot/syslinux/syslinux.cfg 1
======================== Unknown MBRs/Boot Sectors/etc: ========================
Unknown BootLoader on sda3
00000000 96 6f 4e 5e d0 3b 99 1c 18 98 de 4a ca 47 ed 0a |.oN^.;.....J.G..|
00000010 72 79 71 b5 e0 5d 2c f5 c1 71 de d9 63 04 84 c7 |ryq..],..q..c...|
00000020 b2 6f 3e a3 5f 99 1b a0 2d 78 17 ad fb 69 ee c2 |.o>._...-x...i..|
00000030 a9 4e 96 33 a1 1c c3 80 06 ee 22 f1 be 5a 06 62 |.N.3......"..Z.b|
00000040 c8 8f 6f d6 bb cf 7e 12 c0 d8 5b 90 85 95 ff 1e |..o...~...[.....|
00000050 80 fa ea 89 d5 aa e6 cd b5 ed 01 93 24 05 fb 81 |............$...|
00000060 00 00 0c f6 08 00 00 e8 01 42 5c 00 00 00 00 af |.........B\.....|
00000070 01 21 0c 4f bf ff ff ff ff fe a9 c2 61 50 91 84 |.!.O........aP..|
00000080 64 11 09 04 7e 37 1d 71 aa 99 ed 37 5a 9e 6b 61 |d...~7.q...7Z.ka|
00000090 75 ca f9 b6 d2 eb 89 47 14 ba be bc b6 1e c7 fc |u......G........|
000000a0 7f 36 30 c5 54 f6 c5 9d dc e4 e7 1a af 69 4e bc |.60.T........iN.|
000000b0 12 94 d0 81 d2 f1 a9 4d d4 6f b1 25 e8 0f dc a2 |.......M.o.%....|
000000c0 e8 de 64 84 c5 a4 67 32 95 c0 00 51 27 70 0b 08 |..d...g2...Q'p..|
000000d0 82 f6 02 e0 80 02 c1 00 05 a6 0a 00 22 16 00 5c |............"..\|
000000e0 00 99 20 05 00 04 40 00 00 25 4a e1 60 a0 48 c2 |.. ...@..%J.`.H.|
000000f0 62 08 fc 4e b8 be ab 5b f3 51 c5 ca c8 bb ad 97 |b..N...[.Q......|
00000100 b9 59 17 37 24 c8 4b 6a f5 c8 7e 21 68 d0 52 ba |.Y.7$.Kj..~!h.R.|
00000110 dc ae 15 ed 16 8d 48 c7 21 12 e8 1c 9c 6f 44 bb |......H.!....oD.|
00000120 16 82 f5 23 69 e7 09 f7 25 45 55 93 08 b9 44 c5 |...#i...%EU...D.|
00000130 8a 09 b1 16 9c 80 05 2c 2b 31 0a c4 50 13 00 27 |.......,+1..P..'|
00000140 40 12 54 09 00 02 40 a0 02 f3 00 98 01 30 50 01 |@[email protected].|
00000150 10 14 00 01 70 01 c0 00 00 00 f3 08 00 00 e5 01 |....p...........|
00000160 42 73 00 00 00 00 af 01 21 2c 4f ff ff ff ff ff |Bs......!,O.....|
00000170 fe a6 02 61 40 91 87 e9 6b 89 d6 aa b8 bc b4 f3 |[email protected].......|
00000180 b9 55 14 cd 65 65 4a ae 12 a5 8b 4b bf a7 20 be |.U..eeJ....K.. .|
00000190 97 e8 79 05 32 cb 1b 76 c6 34 a5 99 6d 7e 48 dd |..y.2..v.4..m~H.|
000001a0 b9 d6 1c 46 51 c9 06 49 2d 05 b0 05 63 64 62 50 |...FQ..I-...cdbP|
000001b0 bc 65 05 9b 83 18 98 1c 20 7e 00 13 28 81 00 fe |.e...... ~..(...|
000001c0 ff ff 83 fe ff ff 00 08 00 00 00 70 89 03 00 fe |...........p....|
000001d0 ff ff 05 fe ff ff 00 78 89 03 00 08 20 00 00 00 |.......x.... ...|
000001e0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
000001f0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 55 aa |..............U.|
00000200
=============================== StdErr Messages: ===============================
No volume groups found
mdadm: No arrays found in config file or automatically
00 00 00 00 00 00 00 55 aa |..............U.|
00000200
=============================== StdErr Messages: ===============================
No volume groups found
mdadm: No arrays found in config file or automatically
Last edited by Zzipo (2013-01-07 22:12:58)

Installing grub2 1.99rc1 on Linux Software RAID (/dev/md[0-x])

Hello!
In the last days I tried to install Archlinux x64 on my server. This server consists of 4 SATA drives. I'm using Linux software Raid with the following configuration:
mdadm --create --verbose /dev/md0 --auto=yes --level=10 --raid-devices=4 /dev/sda1 /dev/sdb1 /dev/sdc1 /dev/sdd1
mdadm --create --verbose /dev/md1 --auto=yes --level=10 --raid-devices=4 /dev/sda2 /dev/sdb2 /dev/sdc2 /dev/sdd2
mdadm --create --verbose /dev/md2 --auto=yes --level=0 --raid-devices=4 /dev/sda3 /dev/sdb3 /dev/sdc3 /dev/sdd3
md0 --> / including /boot
md1 --> /data (my storage partiton)
md2 --> my swap partion
In the last step of the installer I don't installed grub and leave the installer without installing a bootloader.
I mounted the /dev folder to /mnt/dev and chrooted in my new system:
chroot /mnt bash
In my new system I installed the new grub2 bootloader with:
pacman -S grub2-bios
In the next step I tried to install the bootloader to the MBR with the following command:
grub_bios-install --boot-directory=/boot --no-floppy --recheck /dev/md0
But I get the following error:
/sbin/grub-probe: error: no such disk.
Auto-detection of a filesystem of /dev/md0 failed.
Please report this together with the output of "/sbin/grub-probe --device-map="/boot/grub/device.map" --target=fs -v /boot/grub" to <[email protected]>
I also tried to install the grub2 directly on my discs with the following command:
grub_bios-install --boot-directory=/boot --no-floppy --recheck /dev/sda
But the error is the same as above.
Following the instruction of the error message I executed the following command:
/sbin/grub-probe --device-map="/boot/grub/device.map
I get a large debug output:
/sbin/grub-probe: info: scanning hd3,msdos2 for LVM.
/sbin/grub-probe: info: the size of hd3 is 3907029168.
/sbin/grub-probe: info: no LVM signature found
/sbin/grub-probe: info: scanning hd3,msdos1 for LVM.
/sbin/grub-probe: info: the size of hd3 is 3907029168.
/sbin/grub-probe: info: no LVM signature found
/sbin/grub-probe: info: scanning hd4 for LVM.
/sbin/grub-probe: info: the size of hd4 is 2068992.
/sbin/grub-probe: info: no LVM signature found
/sbin/grub-probe: info: the size of hd4 is 2068992.
/sbin/grub-probe: info: scanning hd4,msdos1 for LVM.
/sbin/grub-probe: info: the size of hd4 is 2068992.
/sbin/grub-probe: info: no LVM signature found
/sbin/grub-probe: info: changing current directory to /dev.
/sbin/grub-probe: info: opening md0.
/sbin/grub-probe: error: no such disk.
There is a tutorial for installing grub2 at ArchLinux in the wiki:
https://wiki.archlinux.org/index.php/Grub2
But I can't find any solution for my problem.
Does anybody know a solution for this problem?
Thanks for help
Best regards,
Flasher
Last edited by Flasher (2011-03-03 20:13:13)

hbswn wrote:Maybe it cannot handle the new mdadm format. Here the other partitions have version 0.90. Only the failing md0 has version 1.2:
I'm sure it is the cause of the problem. But not new format. The old one (0.90) is incompatible with grub2.
I hit the same problem and today I managed to fix it.
What I did: I copied /boot to tmp directory, destroyed /dev/md0 (my /boot) with metadata 0.90, created new /dev/md0 (metadata 1.2), copied back /boot content.
After that, grub_bios-install /dev/sda && grub_bios-install /dev/sdb finished without any errors.

Chainload Truecrypt bootloader on sda from Grub2 on sdb

Similar Messages

Maybe you are looking for