Dual boot windows 7+archlinux on separate disks; grub errors. [solved]

Hello,
I am very excited to try arch linux, but am having trouble with the
installation.  My situation is as follows:  I have 3 hard drives: windows 7
lives on sda and sdb.  I am installing arch on sdc, which is 500GB.
I partitioned the hard drive as follows (which may look kind of ridiculous,
but please understand I am new at this):
sdc1    /boot    1GB    ext2
sdc2    swap    8GB     swap
sdc3    /       50GB    ext3
sdc4    /home   400+GB  ext3
After some initial issues, I managed to run the installation program
smoothly, performed the basic configuration, and then went to install grub. I
scrutinized the grub menu.lst file over and over, and could not find anything
wrong.  It had the following entry for archlinux:
title: Arch Linux
root: (hd2,0)
kernel: /vmlinuz26 root=/dev/sdc3 ro
initrd: /kernel26.img
There is no entry for windows, as I can just use the BIOS boot menu to switch
between the two bootable hard disks, or at least that was my plan...
When I boot to windows, everything works just fine.  When I go to the
BIOS boot menu and choose to boot from the third disk, I get the grub
bootloader with choices of arch and arch fallback, just as expected. 
I select the former, and I get the following message from grub:
Booting 'Arch Linux'
root    hd(2,0)
Filesystem type unknown, partition type 0x7
kernel /vmlinuz26 root=/dev/sdc3 ro
Error17: cannot mount selected partition
The same thing happens for the fallback image.  I made very sure to install
grub to the mbr, /dev/sdc.
I have also tried to use the UUID entry for /root in the menu.lst file, and
this gives the exact same results.  I have also run grub interactively from
the bootable CD image, and it does not give such errors-  it knows that
hd(2,0) has type 82, and not 7.  However, when I try the initrd command in
interactive grub, I get a complaint about the image not fitting in memory.
However, I have 16GB of ram...
One other note that may be (but probably is not) relevant:  initially I could
not get the Arch disk to recognize the hard drive (the format disk phase of
installation would always fail), so from windows, I went to the disk manager
and formatted it with ntfs.  This enabled me to format the disk from the arch
install process and install the new FS.  I didn't think the temporary presence
of ntfs would be any kind of an issue since I immediately reformatted it.
Many thanks for your time reading this.  Much appreciated.
Last edited by wes (2011-03-07 21:24:44)

I guess here:
https://wiki.archlinux.org/index.php/Be … Bootloader
or here
https://wiki.archlinux.org/index.php/Wi … ard_Drives
would be sensible places, but as a complete rookie, I don't feel qualified to start editing the wiki...

Similar Messages

  • [SOLVE] Dual Boot Windows and ArchLinux with Syslinux

    Ok, i installed ArchLinux on my laptop with Windows XP (syslinux) and I cannot find get Windows to boot or mount it. I have tried to do what i can to do this but cannot. I Installed XP first like a should and something i think might be needed to know is after i created the partitions scheme (10Gb (boot partition), 50GB (XP), 80GB(was unallocated)). The installation disk formated both 2 partitions in NTFS but i installed XP on the second and Windows reported them as C and D drives. Windows being D. Thought that was bit werid thinking Windows installed the mbr on that partition. When I installed ArchLinux, it did have the boot flag set on 10GB (or C drive).
    Since I installed ArchLinux, I have been unable to find a solution to mounting/booting to Windows. Installed NTFS-3G and that didn't work when i tried mount /dev/sda3 windows and i did created a folder named windows but got ...
    mount: wrong fs type, bad option, bad superblock on /dev/sda3,
    missing codepage or helper program, or other error
    In some cases useful info is found in syslog - try
    dmesg | tail or so.
    Tried dmesg | tail and got
    [ 76.524133] SGI XFS with ACLs, security attributes, realtime, large block/inode numbers, no debug enabled
    [ 179.468499] ACPI: \_SB_.PCI0.LPC0.ACAD: ACPI_NOTIFY_DEVICE_CHECK event: unsupported
    [ 705.472330] 8139too 0000:02:03.0 enp2s3: link down
    [ 717.380879] 8139too 0000:02:03.0 enp2s3: link up, 100Mbps, full-duplex, lpa 0x41E1
    [ 726.447184] 8139too 0000:02:03.0 enp2s3: link down
    [ 727.596128] ACPI: \_SB_.PCI0.LPC0.ACAD: ACPI_NOTIFY_BUS_CHECK event: unsupported
    [ 732.616138] 8139too 0000:02:03.0 enp2s3: link up, 100Mbps, full-duplex, lpa 0x41E1
    [ 733.848832] 8139too 0000:02:03.0 enp2s3: link down
    [ 834.062062] 8139too 0000:02:03.0 enp2s3: link up, 100Mbps, full-duplex, lpa 0x41E1
    [ 2131.449211] perf samples too long (2534 > 2500), lowering kernel.perf_event_max_sample_rate to 50100
    This is when i run sudo lsblk
    NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
    sda 8:0 0 149.1G 0 disk
    |-sda1 8:1 0 9.8G 0 part /boot
    |-sda2 8:2 0 1K 0 part
    |-sda3 8:3 0 53.6G 0 part
    `-sda5 8:5 0 85.7G 0 part /
    sr0 11:0 1 1024M 0 rom
    My syslinux is
    LABEL arch
    MENU LABEL Arch Linux
    LINUX ../vmlinuz-linux
    APPEND root=/dev/sda5 rw
    INITRD ../initramfs-linux.img
    LABEL windows
    MENU LABEL Windows
    COM32 chain.c32
    APPEND hd0 3
    NOTE: chain is in the same directory with syslinux
    I really think Windows got corrupted but not sure. Thought about repairing the mbr on windows and booting to it then reinstall syslinux but really don't want too.
    Thanks in advance
    Last edited by jag-ster (2014-11-27 02:12:12)

    Here is the partition table:
    /dev/sda1 one HUGE linux /boot primary partition (assuming ext4)
    /dev/sda2 "name" of the extended partition
    /dev/sda3 primary Windows partition (assuming NTFS)
    /dev/sda5 logical Linux root partition (assuming ext4)
    /dev/sda1 to /dev/sda4 are either all primary, or three primary and one extended. After /dev/sda4 all partitions are logical. If you're still wondering why is there no /dev/sda4, it's because you have 2 primary and one extended, so /dev/sda4 is reserved for another primary partition.
    Windows problem:
    The /dev/sda1 which Windows named C: is Windows equivalent of linux /boot. When you told linux to place its /boot on /dev/sda1 it formated boot files of Windows. Now you have Windows OS with no kernel. In other words there is no way to boot Windows if you don't reinstall it. Actually there is a way, but you would than screw up Arch.
    Mounting problem:
    You can never mount extended partition, only logical (an extended partition is made of logical partitions). You want to do:
    sudo mount /dev/sda3 -t NTFS-3g -o rw,uid=YourUserName /path/where/you/want/this/partition/mounted
    EDIT:
    Try it this way:
    - Backup all your data
    - Delete every partition
    - Start Windows installation
    - Make only one partition (c:/ for Windows)
    - Let Windows make another partition
    - Make one more so you could have a data partition, which does not need to be formated to reinstall Windows
    - Start Arch installation
    - Get to partitioning
        =Partitioning=
        - /dev/sda4 extended (take the rest of the drive)
        - /dev/sda5 logical /boot 512MiB
        - /dev/sda6 logical /          20GiB
        - /dev/sda7 logical /home (the rest)
    Making a separate /home partition will come in handy when reinstalling Arch (any linux distribution), or switching between distros, because it is the equivalent of D:/ in Windows. Also consider LVM.
    Last edited by bstaletic (2014-02-28 23:25:33)

  • Can I possible to use dual boot(windows 7 in internal hard disk and windows 8 in external hard disk)?

    i want to create dual boot(2 OS in 1 laptop) in my laptop but my internal hard disk reach maximum(3) logical partition so my genuine windows 7 os is not allow me to create new logical partition and install win8 pro. i planed to purchase
    one external hard disk and connect with my laptop and install win8 in external hard disk and use both win8 and 7. This is possible? If possible how to i create? please give me step by step instruction.

    This is a developers forum for the presentation manager windows forms classes and api's
    Try what has now a new name again user community forums, formerly answer forums.
    http://answers.microsoft.com
    Success
    Cor

  • Dual Booting Windows 7/8 - Two Separate Hard Drives App to Change Default OS

    Hi Guys
    I would like to make an app to change the default OS to boot to so users can run a desktop app on either os to restart and boot to the other one hopefully by just changing the registry
    The win 7 ssd is efi  the win 8.1 also but only 1 partition win 7 is disk 0 with the efi part
    If its possible via altering a reg key where would i find it ?  
    Chris Cullen

    Hi,
    The dual boot information is stored in the bcd file in the system reserved partition, also, you can see the boot option by typing “msconfig” at the command line window, there will be two options if you have two systems
    installed on your computer:
    You can set one as the default boot system, the boot information isn’t stored in the registry key, so, I am afraid altering the registry won’t help.
    Regards
    Wade Liu
    TechNet Community Support

  • How can I dual boot Windows 7 on a MBR disk and Windows 8 on GPT Disk with UEFI BIOS

    I have recently build a computer. I bought a Seagate 3TB HDD which I planned to install Windows 8.1 Pro on and I also bought another Seagate 1TB HDD which I planned to install Windows 7 Ultimate 64 bit. I wanted to dual boot the two systems.
    However, I want to format the 3TB HDD into GPT and format the 1TB HDD into MBR mode.
    Can this be done in a UEFI BIOS environment?
    Windows 7 Ultimate X64 ---------- MBR 1TB HDD
    Windows 8.1 Pro X64--------------- GPT 3TB HDD
    Please reply soon, because I am in a hurry to solve this problem.
    My family members need a working PC at home :)
    My Motherboard : AsRock Fatal1ty H97 Killer
    Please help !!!!!!!!!!!!!!!!!!!!

    Does these help?
    http://www.pagestart.com/win7win81db01171401.html
    http://www.pcmag.com/article2/0,2817,2425418,00.asp
    Arnav Sharma | http://arnavsharma.net/ Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading
    the thread.

  • Dual boot (Windows Vista + Archlinux)

    First hello people, this is my first post.I need some guidance here. I installed Archlinux in my laptop ( DELL XPS M1330) from a USB stick memory everything went smooth until i got to the grub part. I did it as the wiki mention I installed the grub at the /boot partition :
    /dev/sda1 * Windows Vista NTFS ( Marked as boot)
    /dev/sda2 Win Backups NTFS
    /dev/sda3 /boot ext2
    /dev/sda5 /SWAP ----
    /dev/sda6 / ext3
    I uncomment the windows part of the menu.lst . At boot Archlinux boots normally but when I want to boot linux , it blinks and takes me back to grub . Then with cfdisk I toggled to boot at /boot and unmarjed the original (Windows Vista ) and the same result then I toggled both /boot and Windows vista and the same result . What do you think I should do ??  I'm lost !! Thanks people.

    aragorncito wrote:At boot Archlinux boots normally but when I want to boot linux , it blinks and takes me back to grub .
    Do you mean when you try to boot Windows it blinks back to grub, or when you want to boot linux it brings you back to grub?
    Did you check your menu.lst to make sure that you adjusted what partitions it is looking for (remember, grub starts counting at 0, so sda1 will be (hd0,0) in grub)

  • Dual boot (Win XP - ARCH 0.8) / disk 80 GByte

    Hi,
    I am trying to setup DUAL Boot Windows-XP Archlinux on a Compaq nc6320
    I want to load linux  from the Window NT loader I have only a " - "  in the left uppercorner when I select --linux--
    [boot loader]
    timeout=30
    default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS
    [operating systems]
    multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Professional"
    c:\boot.lnx="-- Linux--"
    Although the boot.lnx is not a text file I could read .... è*·ëþGRUB ·Geom·Hard Disk·Read· Error·»·´Í¬<·uô÷··········
    I have a disk of 80 byte
    Sda1 NTFS Windows XP 40Gb
    Sda3   7 Mb  Grub Bootmanager  installed here (this was a unused space here)
    Sda2               
        Sda5 NTFS, about 26 Gbyte
        Sda6 /boot  130 Mb
        Sda7 swap  1024 Mb
        Sda8 /        9,7 Gb    > Arclinux 0.8
    I made the file boot.lnx this way
       dd if=/dev/sda3 of=boor.lnx bs=512 count=1
    Possible I have problems with the Cylindrer 1024 border ?
    Due to company base policy I would like to avoid changing MBR and first ntfs partiton.
    Any idea what oher solutions there are ? Thanks.
    I id not found LBA support in bios setup.
    http://www.geocities.com/epark/linux/gr … HOWTO.html
    Last edited by go4it (2007-01-29 15:29:33)

    Whenever I've put linux on the same disk as windows I've always used lilo to handle the booting by installing the linux bootloader to the "/root" of the linux partition, before that I would flag the partition as bootable with cfdisk while I was doing my partitioning and untoggle the boot flag for windows, this was also reversible so it never harmed my windows bootloader. 
    I would make an entry like this if I was using lilo:
    # Partition 3: Windows XP Home
        other = /dev/hda1
        label = WinXP
    and then run lilo for the change to stick.
    In grub I would imagine you would have to add something like this:
    title WindowsXP
        rootnoverify (hd0,0)
        chainloader +1
        makeactive
    I now just keep linux on its own seperate drive, to give you an idea how that works this is what my grub looked like last week, I repartitioned and only have arch on there now, so far..... , keep in mind my windows is actually on my second drive, hence the need for the "map" entries, reading up a bit on grub would be to your advantage, its hdd naming scheme is a bit confusing at first, but once ya get the hang of it you realise how powerful and usefull it can be, I love the password and fallback features. 
    # grub.conf generated by anaconda
    # Note that you do not have to rerun grub after making changes to this file
    # NOTICE: You do not have a /boot partition. This means that
    # all kernel and initrd paths are relative to /, eg.
    # root (hd0,1)
    # kernel /boot/kernel-genkernelreal_root=/dev/sda2
    # initrd /boot/initramfs-genkernel
    #boot=/dev/sda2
    default=0
    timeout=120
    splashimage=(hd0,1)/boot/grub/splash.xpm.gz
    password --md5 XXXXXXXXXXXXXXXXXXXXXXXXXXX
    title Sabayon Linux x86 3.25
    root (hd0,1)
    kernel /boot/kernel-genkernel-x86-2.6.19-gentoo-r4 root=/dev/ram0 ramdisk=8192 real_root=/dev/sda2 quiet init=/linuxrc splash=silent,theme:sabayon CONSOLE=/dev/tty1 pci=nomsi vga=0x31b
    initrd /boot/initramfs-genkernel-x86-2.6.19-gentoo-r4
    title Windows XP Professional
    rootnoverify (hd1,0)
    map (hd0) (hd1)
    map (hd1) (hd0)
    chainloader +1
    makeactive
    title VectorLinux 5.8 Std Gold
    root (hd0,2)
    kernel /boot/vmlinuz root=/dev/sda3 ro vga=795
    title Arch Linux Voodoo
    root (hd0,4)
    kernel /boot/vmlinuz26 root=/dev/sda5 ro vga=795
    initrd /boot/kernel26.img
    Last edited by RabidWolf (2007-01-31 12:32:39)

  • Dual booting Windows 8 and Arch Linux with UEFI

    Hi all!
    I'm trying to install Arch Linux on my computer where I already have Windows 8, and I'm getting a little stuck when it comes to the partitioning.
    Following the beginner's guide and the method here: https://wiki.archlinux.org/index.php/Un … n_in_Linux for setting up the partitions properly, regarding UEFI. My problem is that when using cgdisk to set up a new EFI system partition (ef00), I get an error message when trying to write the partition table (just saying that something went wrong). I figure the problem is that I already have a partition like this (correct me if I'm wrong), but it really looks like it succeded (see info below). So my question is: How do I preceed to keep my Windows 8 installation happy, but installing Arch? Do I remove the old EFI system partition and create a new one, or is there some method that allows me to edit the already existing one, to allow me to dual boot Windows 8 and Arch?
    My partition table now looks like this:
    Part. # Size Partition Type Partition Name
    1007KB free space
    1 500MB Windows RE Basic data partition
    2 300MB EFI System EFI system partition (this one was already present on my system)
    3 128MB Microsoft reserved Microsoft reserved partition
    4 63.5GB Microsoft basic data Basic data partition
    8 512MB EFI System EFI System partition (this is the one I tried to create when I got the error message)
    5 29.5GB Linux filesystem Arch (this is where I was going to put my Arch installation)
    6 22GB Windows RE Basic data partition
    7 1024MB Windows RE Basic data partition
    615KB free space
    Just for the record; I only created partition #8 and #5.
    Any help is appreciated! And sorry for beeing a total noob, but I really suck at this.

    sudo make sandwich wrote:If it is possible to share ESP between OSes, how do I do this (would it be sufficent to follow this section: https://wiki.archlinux.org/index.php/Beginners'_Guide#For_UEFI_motherboards)?
    There's really very little to do to share an ESP between OSes. Most OS installers will auto-detect the ESP and use it. Problem solved. For Arch it may be a bit more effort just because Arch uses a more hands-on installation process, but I've only done a couple of Arch installations, and the last one was several months ago, so I don't recall the details clearly enough to comment.
    And how big will the partition need to be? The beginner's guide says 512MB or higher.
    I don't know what was in the mind of the author, but my guess is that's because that's roughly the cutoff point where mkdosfs starts creating FAT32 by default rather than FAT16. The ESP is officially supposed to be FAT32, not FAT16, although FAT16 usually works OK. It's also possible to create FAT32 on smaller partitions by using an explicit option to mkdosfs ("-F 32").
    The optimal size of the ESP depends on the files stored on it. If you don't store your Linux kernels, something as small as 100MiB is usually adequate; but a few Linux kernels and their initrd files can consume twice that amount. My own recommendation is for the ESP to be 200-500MiB.
    The only error message I got from cgdisk is "Problem saving data! Your partition table may be damaged!", however booting Windows again works fine. Parted did not complain about antything.
    Use the "verify" function in cgdisk. That will reveal any problems with the data structures. If a verify turns up OK, then that means that cgdisk ran into some sort of disk problem. Running gdisk rather than cgdisk and using the gdisk "w" option (without making any changes) may produce a more helpful error message.

  • Dual boot Windows 7 and Arch from 2 seperate drives (UEFI)

    Hello everyone, I've been working on installing Arch to a secondary hard drive for the past few hours, but I am trying to make sure I won't mess up my Windows 7 install.  I have found several topics talking about dual booting Windows 7 and Arch, but not a whole lot on booting them from separate drives.  My drives are currently setup as follows.
    sda (120GB SSD for Windows 7)
        sda1 (100MB System Reserved NTFS partition)
        sda2 (Windows 7 install)
    sdb (1TB HDD for Windows programs, files, etc)
        sdb1 (1TB NTFS partition)
    sdc (1TB HDD)
        sdc1 (boot 512MB FAT32)
        sdc2 (root 500MB ext4)
        sdc3 (home 300GB ext4)
        sdc4 (swap 10GB)
        rest unallocated "free space"
    I used Gparted to create the partitions.  I ended up getting hung up on the "Create Filesystems" sections, specifically this line"
    # mkfs.fat -F32 /dev/sdXY
    Now that I am looking at it, I'm thinking the "Create Filesystems" section maybe isn't necessary because I've used Gparted?
    If it isn't necessary, when I get to the "mount the EFI System Partition to /boot" section, would I simply use
    # mount /dev/sdc1 /mnt/boot
    instead of
    # mount /dev/sdXY /mnt/boot ?
    The way I had this setup with Ubuntu was 3 partitions on sdc (/, home, swap) and I set my PC to boot to the sdc drive on startup.  The boot loader would then give me the option to boot into Ubuntu or Windows 7, and I never had to alter the sda or sdb drives at all.  Is this possible through Arch?  My thinking is that even if it isn't, I should still be able to enter the BIOS boot menu and select which drive to boot manually correct?  That wouldn't be too big of a deal for me because I spend 90% of my time in Linux, and only use Windows for Photoshop and gaming occasionally.
    Thanks for taking the time to read this.  I would have just tested this out, but I am afraid of messing up my Windows install.

    After several sleepless hours I had to give up and go to bed about 5 hours ago.  The installation process went smoothly (or so I thought).  I followed the tutorial closely and upon rebooting I was met with a blinking cursor.  After some googling I found others who said I should press TAB, but nothing seemed to work.
    I rebooted to the iso disk and found the "boot installed OS" option and noticed it said "Press TAB to edit".  I then found the boot parameters and tried everything from hd0 0 to hd4 4.  I believe I have Grub setup correctly because every option besides hd0 0 either says "Booting..." and then gets stuck, or says "That disk and partition combination does not exist".  So yea, I think hd0 0 is the correct boot path, it just gets stuck with the blinking cursor.
    silverhammermba wrote:
    You have the right idea. You want to install a bootloader on sdc1 which will be able to boot both Arch and Windows.
    Your best bet would be to use something like rEFInd. It has a "scanfor" option that should automatically detect your BIOS-configured Windows installation and add a boot option for it. Note that depending on your motherboard, you may have to switch to UEFI-only mode and Windows will be unbootable without the assistance of a UEFI program which is backwards compatible with BIOS (like rEFInd).
    Thank you for the link.  Considering I can't get into my install and the actual install only took about 30 minutes,  I think I am going to just start from the beginning again with REFIndr.  It seems much simpler.  I only used Grub because I've used it before with Ubuntu, but my very limited knowledge is telling me Grub is probably the problem.
    MoonSwan wrote:Just an idea:  My bios has a "Boot-up Prompt" which I can invoke when it's POSTing by hitting F11.  This brings me to a menu that allows me to choose which drive I want to boot up that day.  I use it when Syslinux isn't working properly (Which is right now as a matter of fact ...) in order to boot Windows so I can do some SCII, for example.  I, too, dual-boot but I have both OSes on different SSDs.  So my 120GB Crucial SSD has Arch on it and the 240GB Kingston has Windows, SCII, Portable Apps, etc and nary the two shall meet.  It makes dual-booting easier in the case of a corrupt OS or MBR or what-have-you.  You may want to give your Bios a better look to see if you can do the F11 trick.  It probably can and will usually tell you so at POST by printing that information on-screen along with your drives-detected and other messages (I hit Pause sometimes to read all the POST messages).
    This is exactly what I was talking about doing when I mentioned:
    My thinking is that even if it isn't, I should still be able to enter the BIOS boot menu and select which drive to boot manually correct?
    That's good to know, because even if this next install doesn't work I think if I pull the other drives I should be able to get it working fairly easily.
    Thanks again everyone.

  • Advice on dual-booting Windows 7 with UEFI motherboard

    I'm going to build a desktop PC tomorrow, having finally purchased all the parts for it. I'll be installing Arch as my main OS, and Windows for gaming. However I'm not really versed in UEFI and its uses, advantages/disadvantages; since my laptop just uses BIOS.
    My plan is to have 3 drives: 32GB SSD for the / partition, 1TB HDD for /home, and 500GB for Windows 7 x64 Ultimate.
    Being unused to UEFI I was thinking about trying to just run everything in BIOS/Legacy mode, but that doesn't seem very sensible to me, especially since I have the hardware so I might as well use it.
    So, reading the wiki and forums have led me to conclude that having a 1GB EFI System Partition on the SSD should be sufficient, and use gummiboot for my bootloader.
    Other reading about setting up dual boots suggests to me that installing Windows 7 on its own HDD with MBR partitioning and Arch on a separate (set of) drive(s) with GPT partitioning will be sufficient. The reason being that if the BIOS is set up to boot sda, which has GRUB as its bootloader, using GRUB I can choose to boot into Windows despite it being on a separate hard drive.
    My questions are (and it occurs to me that I am in the most part just looking to have my ideas confirmed):
    1. Have I gotten this all completely wrong?
    2. If I'm correct, can the above system of using GRUB on one drive to boot up an OS on another drive be applied to UEFI?
    3. Has anybody tried/succeeded/failed to dual-boot in this fashion before me, and if so what did they do?
    Thanks one and all! Hopefully I've made myself clear enough here

    billodwyer wrote:Being unused to UEFI I was thinking about trying to just run everything in BIOS/Legacy mode, but that doesn't seem very sensible to me, especially since I have the hardware so I might as well use it.
    Using BIOS/CSM/legacy mode can work fine; however, it will probably slow down the boot process by a few seconds, and it will close off some possible future (and even current) advantages, as EFI support in Linux is improved.
    So, reading the wiki and forums have led me to conclude that having a 1GB EFI System Partition on the SSD should be sufficient, and use gummiboot for my bootloader.
    A 1GB ESP is more than sufficient. In terms of space requirements, 100-500MB is enough, depending on how you use the ESP; but various bugs and default settings make me recommend 550MiB as a good size. Bigger is OK, but wastes some disk space.
    A bigger issue is that the ESP won't really benefit much from being on your SSD, since it's read once at boot time. The biggest advantage to putting the ESP on the SSD in your setup is that if you use gummiboot, you'll also have to put the Linux kernel and initrd file on the ESP, so having them on an SSD will speed up the boot process by about 1-5 seconds. Overall, I'd probably put the ESP on one of the spinning disks.
    One more comment: gummiboot can launch boot loaders from its own partition but not from other partitions. This can work fine if you plan things carefully, but with three disks and two OSes, you must be absolutely positive that Windows uses the ESP on which gummiboot is installed. I'm not an expert on Windows installation, so I can't offer any specific pointers or caveats on this. If you need something with more flexibility, both rEFInd and GRUB can redirect the boot process to other partitions or physical disks. rEFInd can also redirect from an EFI-mode boot to a BIOS/CSM/legacy-mode boot. (See below.) Overall, rEFInd's flexibility on this score is a plus compared to gummiboot; but gummiboot is covered in the Arch wiki's beginner's guide, which is a plus. You'll have to pick which advantage you prefer. (Note that I'm rEFInd's maintainer, so I'm not unbiased.)
    Other reading about setting up dual boots suggests to me that installing Windows 7 on its own HDD with MBR partitioning and Arch on a separate (set of) drive(s) with GPT partitioning will be sufficient. The reason being that if the BIOS is set up to boot sda, which has GRUB as its bootloader, using GRUB I can choose to boot into Windows despite it being on a separate hard drive.
    This is an unworkable idea, at least as stated and if you want to do an EFI-mode boot. Windows ties the partition table type to the boot mode: Windows boots from MBR disks only in BIOS mode, and from GPT disks only in EFI mode. Thus, using MBR for the Windows disk will require a BIOS/CSM/legacy-mode installation of Windows. Furthermore, neither gummiboot nor GRUB can redirect from EFI mode to BIOS mode (or vice-versa), so if you do it this way, you'll be forcing yourself to boot Linux in BIOS mode, to switch between BIOS-mode and EFI-mode boots at the firmware level (which isn't always easily controlled), or to use rEFInd to redirect from an EFI-mode boot to a BIOS-mode Windows boot.
    Overall, you're best off either using GPT for all your disks and booting all your OSes in EFI mode or using MBR for Windows (and perhaps all your disks) and using BIOS-mode booting for all your OSes.
    Under EFI, the boot process is controlled by settings in the NVRAM, which you can adjust with "efibootmgr" in Linux, "bcfg" in an EFI shell, or "bcdedit" in Windows. (The Arch wiki covers the basics at least efibootmgr and bcfg.) In a typical dual-boot setup, you tell the computer to launch your preferred boot manager (EFI-mode GRUB, rEFInd, or gummiboot, most commonly), which then controls the boot process. You set up boot loaders for all your OSes on one or more ESPs. (Note: A boot manager lets you choose which boot loader to run, and a boot loader loads the kernel into memory. GRUB is both a boot manager and a boot loader. rEFInd and gummiboot are both boot managers. The EFI stub loader, ELILO, and the EFI version of SYSLINUX are all boot loaders but not boot managers. Most EFIs include their own boot manager, but it's usually primitive and awkward to use. It's also not standardized, so my computer's built-in boot manager is likely to be different from yours. Thus, I recommend against relying on the built-in boot manager for anything but launching your preferred boot manager.) Thus, the lowest-common-denominator type of setup is to put your preferred boot manager, the Windows boot loader, and a Linux boot loader (which could mean your Linux kernel) on a single ESP. If you want to use multiple ESPs or otherwise split things up, you cannot use gummiboot as the boot manager, since it can't redirect the boot process from one partition to another. (Many EFIs can do this with their own built-in boot managers, but this isn't guaranteed, and it's usually more awkward than using rEFInd or GRUB.)
    I know this can be a lot to absorb. The official rules aren't really all that complex, but different EFIs interpret the rules differently, and the different capabilities of the various boot managers and boot loaders creates a lot of subtle implications for how you set everything up.
    1. Have I gotten this all completely wrong?
    Significant parts of it, I'm afraid; see above. You're working under BIOS assumptions, which don't apply to EFI.
    2. If I'm correct, can the above system of using GRUB on one drive to boot up an OS on another drive be applied to UEFI?
    GRUB can do this, but gummiboot can't. You set one of those (or something else, like rEFInd) as your primary boot manager. Using both GRUB and gummiboot adds unnecessary complexity, IMHO. OTOH, setting up multiple boot managers or boot loaders is possible, and can give you a fallback in case one fails. For instance, there's a known bug that affects 3.7 and later kernels, mostly on Lenovo computers, that causes the EFI stub loader to fail sometimes. Thus, if you use rEFInd, gummiboot, or the EFI's own boot manager to launch the kernel via the EFI stub loader, having GRUB, ELILO, or SYSLINUX set up as a fallback can provide helpful insurance in case a kernel upgrade causes your normal boot process to fail.
    3. Has anybody tried/succeeded/failed to dual-boot in this fashion before me, and if so what did they do?
    Many people dual-boot Windows and Linux under EFI. There are a huge number of possible solutions. My own Windows/Linux dual-boot system uses:
    rEFInd
    rEFInd's EFI filesystem drivers
    Linux kernels on Linux-native /boot partitions (two partitions, one for each of the two distributions installed on that computer)
    The Windows boot loader on the ESP
    This works well for me, but it wouldn't work with gummiboot instead of rEFInd, since gummiboot can't redirect the boot process to another partition. (gummiboot also can't automatically load filesystem drivers.) Arch Linux users who use gummiboot often mount the ESP at /boot, which enables gummiboot to easily launch the Linux kernel. Doing this with multiple Linux distributions would be awkward, though, since you'd end up with two distributions' kernels in the same directory.

  • Edge e520 i5 UEFI/GPT Dual boot Windows/Ubuntu

    Hi!
    I have an Edge e520 1143GVG. It has an UEFI-Board with Win7/64 on MBR-Harddisk.
    What I want:
    GPT-Partition scheme and dual boot Windows 7/64 and ubuntu 14.04/64.
    I managed to backup the partitions on an external HDD, install GPT on Harddisk, recopy saved Partitions and have now a fully running Win7/64 on GPT-System (it wasn't that easy as it seems here).
    Next Step is to install Ubuntu on a separate Partition. I took a standard Ubuntu boot-CD, startet the pc with that boot disk (Board-Settings: UEFI/BIOS "Both", UEFI First) and installed Ubuntu without any trouble. Unfortunately no boot entry has been generated, so I tried to add one with EasyBCD. That doesn't work, an error is shown like "Windows cannot be startet, no valid file /NST/grub.mbr" or something like that.
    I think the reason is that the cd booted in BIOS Mode, not UEFI. If I set board setting to "UEFI only", the boot CD will not start. So I built a bootable Ubuntu USB-Flashdrive with GPT-Scheme, but it didn't start as well.
    After that I updated BIOS hoping UEFI-Boot from external devices will be possible then. It isn't.
    The e520-board seems to be outdated or faulty, it is not possible to boot from USB or CD in UEFI-Mode.
    Does anyone knows a solution? Will Lenovo update the BIOS?
    kr,
    Bernd Hollermann, Germany

    I have to update my problem:
    booting in gpt/uefi-mode is impossible from usb-key, but is ok from DVD. I managed to install Ubuntu now, everything runs well, after I took a 64-bit version on a dvd.

  • Dual boot windows from USB via grub?

    HI all:
    I recently had a motherboard failure on an existing PC on which I dual-booted Windows XP and Gentoo.  I replaced that box with a new HP PC preloaded with Vista.  Wiped that immediately, and installed ARCH.  But, I would like to also boot XP, and, since my old hard drive is still OK (I have it in an external USB adapter), I was thinking that I might configure grub to point at an external USB drive like this:
    # Windows XP
    title Windows XP
    root (hd1,0)
    makeactive
    chainloader +1
    where "hd1" (I hope) would point at my old drive, now connected via USB.  In this way, I am really booting from my HDD (where grub lives), but "chain loading" from my USB external.  Can this work??
    -dvh

    dvh wrote:
    I configured as shown in the wiki, but when I try to boot XP, I get a message that says something to the effect of "missing or corrupted <windows root>\system32\ntoskrnl.exe".  I checked the disk and it seems to be there and OK.  I get the feeling that it is either NOT finding the hard disk (or partition) or it cannot interpret the NTFS file system (but grub was able to boot this before,...).  So, two questions...
    1) how do I know what the designator for the external USB hard disk will be?  I have speculated that grub will find it at "hd1", but maybe not?
    2) does the target disk NEED a windows boot loader?  as I said earlier, I used to dual boot it, so there is a grub loader on that disk also.
    ...ok, three questions...
    3) anything else that I should consider??
    Thanks again for any help.
    -dvh
    1) i don'tknow a way to check this, but the
    missing or corrupted <windows root>\system32\ntoskrnl.exe message comes from the windows boot process,
    so it seems grub is configured correctly.
    The main problem is that BOTH grub and windows boot need to have the correct settings.
    Windows takes the settings for boot from the boot.ini file in the root of C:\ , and that probably needs to be changed.
    You will need some way to get read/write access to the windows C-drive partition.
    Install ntfs-3g in archlinux (see NTFS_Write_Support ) and post the contents of boot.ini .

  • Convert PXIe-8135 controller to dual-boot Windows 7 and LabVIEW RT

    Hello. I have a PXIe-8135 controller that originally was just running Windows 7. We are trying to convert it to a dual boot system to also run LabView Real Time. (There is host computer that will run LabVIEW 2014 with the RT module, and the controller will become a target).
    I have created a FAT32 partition on the hard drive of the controller. Now, I’m trying to install the real-time OS with a USB flash drive made using the MAX utility, but I cannot boot using the USB drive for some reason. I keep getting the message “waiting for USB device to initialize”.  
    In BIOS, legacy USB support is [ENABLED] and boot configuration is set to [Windows/other OS]. I’ve tried removing the drive, waiting, and reinserting. I’ve tried two different USB drives (both 8 GB, different brands).
    I’m not sure what to do next. Apart from the USB boot issue, is converting the PXIe-8135 even possible?  I read about SATA/PATA hard drive issues with older controllers, but I don't know about this one.
    Thanks, in advance, for your help!
    -Jeff
    Solved!
    Go to Solution.

    Per Siana's licensing comment, more information on purchasing a deployment license if you do not have one for this target can be found here.
    The RT Utility USB key is used to set up non-NI hardware with LabVIEW Real-Time, but you should not need it in this situation to convert to dual-boot (*). Try this:
    1. Since you already have a FAT32 partion created, go into BIOS setup and change to booting 'LabVIEW RT'.
    2. The system will attempt to boot LabVIEW RT, see that the partition is empty, and switch over into LabVIEW RT Safe Mode. (this safemode is built into the firmware, which is why you don't really need the USB key).
    3. The system should come up correctly and be detectable from MAX, and you can proceed with installing software.
    4. To switch back to Windows, go back to BIOS setup and choose 'Windows/Other OS'
    (*) One area where the USB key is helpful on a dual boot system is with formatting the disk. If you want to convert from FAT32 to Reliance on the partition designated for LabVIEW RT, the USB key lets you attempt to format a single parition and leave the rest of the disk untouched. If you format from MAX, the standard behavior is to format only one RT partition if found, but if not found, it will format the entire disk.  Formatting from MAX on a dual boot system is consequently riskier and you could lose your Windows partition.

  • Dual boot windows mac mini

    I got a Mac mini and in general I'm happy with it but found out that there's some software I use regularly that is just much better on Windows.  They barely support OS X although technically they do.  So I would like to dual boot Windows as it seems like this is supported and not crazy.
    I followed the bootcamp and some guides I found via Google.  I have the mac mini 2014 with 8 gig ram and 1 terabyte of space.  I have dual monitors setup and a logitech mouse and a logitech gaming keyboard G110 - both USB.  (I also own a wireless apple keyboard which I occasionally use with my iPad).  My first problem was a DOS screen telling me I can't boot up on the specified disk but I did get some help off Google telling me to hold down option while booting (this should be in the guides ;p) but it was easy to fix.. however I'm stumped on what's happening now.
    When I click the Windows partition, it starts booting up Windows 7 Premium 64 bit setup and all looks good.  Then a screen pops up asking me what language/region I am.  The default is United states (perfect).  On this screen my keyboard and mouse are useless.  Or it's frozen.  I think the former.  I think the computer just can't recognize them.  And I cannot figure out a way around this.  If anyone can - please help I will be very thankful. 
    I've tried booting up using the Windows 7 DVD I own and an ISO installed on a USB flash drive per the Bootcamp installer.  Results are the same.

    Use Boot Camp!! Sounds like you have the install disc. Make sure you completely erase a USB 2.0 Thumb Drive format it as one MS DOS Master Boot Record partition. Download Drivers to it. I checked this box in boot camp only.
    Having install disc and driver thumb drive ready. Insert Windows install disc and plug in Thumb drive.
    Open Boot Camp uncheck first 2 boxes. Continue
    Size the BOOTCAMP partion you want it to be by sliding the bar. Or split your HD is an option.
    After that is complete. You will be asked where to install. Select BOOTCAMP partition
    Click Drive Options (advanced).  Click Format. Click OK. All goes well you click Next and it will format as NTFS
    Follow instructions to to install, set up and configure Windows.
    GO TO APPLE  SUPPORT no where else. PRINT BOOT CAMP Installation & Setup Guide. It is in my binder with my Windows 7 Professional Disc. You'll need this, I'm afraid, to have on hand. When Windows is up and going, Antivirus 1st, Install Windows express updates only. Do not update Apple drivers for Windows. Running Windows 7 Pro on my Mac Mini since I bought it in August. Use it for those outdated programs I can't run on Mac or Windows 8. Love it.
    GET THE MANUAL Please. Have fun with it.
    Oh, try left clicking your USB Mouse to make it work. If not use keyboard strokes. i.e. I  a ccept the license agreement (note that the a is underlined. hit "a" on the keyboard to check box.

  • Dual boot Windows 7 partition help

    I want to dual boot Windows 7 & arch but I need help with figuring out what partitions to make and where to put them because it seems the automatic partition-er won't do the trick for me.
    I have two drives that I want to completely format for a fresh, clean install: a 60GB SSD & a 750GB hard drive. I want the end result to be that the SSD only has Windows 7 Pro x64 SP1 installed to it and I will point the 'My Documents', 'My Pictures', etc. to a NTFS partition on the hard disk drive ( I know how to do this folder pointing ). I don't want arch to touch the SSD if possible so I can reformat the SSD separately if I ever just want to reformat Windows. I only want arch to be on the hard disk for that reason. I don't think I care which one handles the OS switching at boot ( should I favor Windows MBR or syslinux? Please give advice. ) And I would assume I make the NTFS partition on the hard disk a primary partition so how do I split up arch for the 3 other primary partitions left since the auto partition from the arch boot CD uses 4?

    I'm no expert, but the way I would do it would be like this:
    1. Create partitions on the HDD for /, /boot, /home and swap, along with one (or more) for your Windows personal files
    2. Set the BIOS to boot from the SSD.
    3. Install Windows on the SSD.
    4. Right-click the "My Documents" folder, select "properties", then the "Location" tab and choose the new location for the folder.
    5. Install Arch on the HDD partitions, and allow the boot manager to install itself in the MBR of the SSD.
    Then the whole boot process will be on the SSD...  If you ever need to get rid of the Linux bootloader, you can overwrite it with a "clean" Windows one using bootrec.exe (see here: http://support.microsoft.com/kb/927392).
    Last edited by esuhl (2012-03-26 04:52:12)

Maybe you are looking for