[SOLVED] Dual Boot Window 7 & Arch on a Uefi system.

From the Wiki
Windows 7 x86_64 versions support booting in x86_64 UEFI mode from GPT disk only, OR in BIOS mode from MBR/msdos disk only. They do not support IA32 (x86 32-bit) UEFI boot from GPT/MBR disk, x86_64 UEFI boot from MBR/msdos disk, or BIOS boot from GPT disk.
I don't understand this. As stated in the title I have a ueif system so that means I have to create a GPT disk ? I already have a gpt disk which I confirmed by running Arch Live USB. Under type it said GPT. I don't understand this at all
However if Arch is installed in BIOS-GPT in one disk and Windows is installed in BIOS-MBR mode in another disk,  then the BIOS bootloader used by Arch CAN boot the Windows in the other disk, if the bootloader itself has the ability to chainload from another disk.
Note: If Arch and Windows are dual-booting from same disk, then Arch SHOULD follow the same firmware boot mode and partitioning combination used by the installed Windows in the disk.
In the Note above it says both Arch and Windows follow the same boot mode if they are dual booting from same disk. I DO NOT want to do this. I have already decided to partition  my drive with 200 Gb going to Windows and 500 Gb going to Arch. Does this mean that I should install both in different modes i.e. Arch in Bios-GPT and Windows in Bios-MBR.
The recommended way to setup a Linux/Windows dual booting system is to first install Windows, only using part of the disk for its partitions. When you have finished the Windows setup, boot into the Linux install environment where you can create additional partitions for Linux while leaving the existing Windows partitions untouched.
UEFI systems
Both Gummiboot and rEFInd autodetect Windows Boot Manager \EFI\Microsoft\Boot\bootmgfw.efi and show it in their boot menu, so there is no manual config required.
For GRUB(2) follow GRUB#Windows_Installed_in_UEFI-GPT_Mode_menu_entry.
Syslinux (as of version 6.02 and 6.03-pre9) and ELILO do not support chainloading other EFI applications, so they cannot be used to chainload \EFI\Microsoft\Boot\bootmgfw.efi .
Computers that come with newer versions of Windows often have secure boot enabled. You will need to take extra steps to either disable secure boot or to make your installation media compatible with secure boot.
Being a beginner should I go with Gummiboot then. GRUB made a mess last time.
Also my secure boot is NOT enabled so is that good.
I have read the FAQs, Beginner's guide, Installation Guide, Dual Boot wiki entry but I just don't understand the above concepts. But it looks this this is the main thing in dual booting. Almost everything else is doable but this I have to get right on account of what happened the last time I installed Arch without getting the above right.
Last edited by Some Arch Lovin (2014-06-14 08:53:14)

A few issues with the dual boot setup
Hello again, I lost my dual factor authentication grid from lastpass. Opensuse was acutally overwriting new pdf files over my old pdf files so now that grid pdf is actually an Arch cheat cheet with the name last_pass_grid.pdf. And the gmail account I used to register to Arch forums is also in last pass.
This is why I created another account. I am some arch lovin.
The installation went smoothly but I could not dual boot Windows7 with Arch because my Win7 image is not UEFI bootable so had to dual boot win8(not a fan at all) and arch.
Almost everything is working correctly. I have a few issues that aren't affecting how the system is working but they still need sorting out.
I'll do them one at a time but I want to know from the admins if I should start a new thread? Because in a way this thread accomplished it job i.e. win7 and arch dual booting in uefi system.
If the answer is yes I should create a new thread depending upon the issue then I will do that but in case its a no since I have only 2-3 problems I am going to ask help for the first one.
My gummiboot is not working on startup. I have to press f12 and use bios booting menu to boot. The problem with that is if I put Windows at the top of the boot priority the bios does not show F12 and F2 at the time of booting up so I can't access the boot menu. I have to boot into Windows and crash it by holding the power button and then the F12 options shows up and I am able to boot into Arch. If I put Arch at the top then Windows keeps restoring back to an earlier version due to start up options.
NOTE : I can't be sure but one it did work(only once). I checked the images online to compare with what I saw and its very similar. An all black screen with three bootloading options
Windows
Arch
Opensuse(don't know why I created a completely new GPT partition table)
This is what I did while installing Gummiboot
# mount -t efivarfs efivarfs /sys/firmware/efi/efivars
# pacman -S gummiboot
# gummiboot install
I tried going through the gummiboot to see if I can do something but it very difficult to comprehend as a beginner. All I get is the characters gummiboot understands but thats all.
Last edited by Archer61 (2014-06-11 13:48:56)

Similar Messages

  • [SOLVED] Dual boot windows 7 and arch Linux with seperate hard drives

    Ok so I'm stuck trying to get my computer to dual boot windows 7 and arch. They are installed on different hard drives and I have grub 2 as the boot loader. I can't find any tutorials on how to do it with seperate hard drives I know how to do it if they are on the same hard drive. Also I want windows on the "first" hard drive how do I check to see which one it considers the first?
    Last edited by bdawg (2012-09-21 23:15:37)

    DSpider wrote:
    drobole wrote:If you want to change it so that sda becomes sdb and sdb becomes sda, you should be able to do that in BIOS.
    Not from the BIOS. He would need to physically open up the computer and switch the cables between them (or add another drive).
    There's no actual performance increase in changing this order. Performance increase is when you have the partitions as close to the beginning of a HDD as possible, where the platters spin faster (basic mechanics, not to be confused with CD/DVD, which are being written from the inside-out to prevent errors after extended usage), and it especially doesn't apply to SSDs whatsoever.
    You may be right about that. I remember I had to do this a while back but I probably switched the cables. It also messed up the drive mapping in Windows 98 if I remember correctly.

  • [SOLVED] dual booting windows 7 with btrfs on grub-bios -- core.img

    I am trying to install arch in a dual boot configuration with an existing windows 7 partition. I have everything from the beginner's guide done but the bootloader. When I run grub-install it tells me that core.img is too big.
    Some googling tells me that this is relatively common with btrfs, and it seems the only work around is to switch to gpt mode and use a grub bios partition. But the info I've seen indicates that I need to use MBR mode to dual boot windows.
    Is it safe to do this with windows? Is there another workaround? Or will I have to settle for ext4?
    Last edited by jorenko (2013-06-09 03:53:24)

    Well there's your problem, your first partition starts at sector 63.  With recent versions of windows and fdisk (and every other partitioning tool I can think of off the top of my head) things now align themselves correctly.  Also because there is now GPT, the first partition typically starts later as the GPT partition table will typically sit between the MBR and the first partition. 
    On a MBR partitioned system, grub2 will actually use the first 446 bytes like normal, but will then also use the space that is empty where GPT would sit.  This is why when you have a GPT partitioned system, it will require you to create a 1-2MB grub boot partition, as it needs somewhere else to put its bloat.  GPT actually still uses the MBR section, but simply creates one large partition covering the whole disk.  This is so that tools that are not GPT aware will not think that they have a whole free disk to use as they please.
    For comparison, here is whe I get from fdisk:
    # fdisk -l /dev/sda
    sudo fdisk -l /dev/sda
    [sudo] password for curtisshima:
    WARNING: fdisk GPT support is currently new, and therefore in an experimental phase. Use at your own discretion.
    Disk /dev/sda: 250.1 GB, 250059350016 bytes, 488397168 sectors
    Units = sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 512 bytes / 512 bytes
    Disk label type: gpt
    # Start End Size Type Name
    1 2048 2099199 1G EFI System EFI System
    2 2099200 252166798 119.2G Linux filesyste arch-btrfs-1
    3 252168192 488397134 112.7G Linux filesyste arch-btrfs-3
    Note that I do use GPT.  But that is not the point here. What I am trying to show is where my first partition starts.  This is also where fdisk will start partitions these days.  This is to ensure compatibility with 4k advanced format disks.
    If you are not dead set on Grub2, you could try using syslinux.  I really like it much better, though if you are booting more than one Linux, you need to either employ chainloading to various partition boot records, or have a shared /boot.  Having a windows partition doens't really matter, as you are simply chainloading to that funky reserved partition anyway. 
    The other option is to use grub-legacy, which can still be found in the AUR.  I actually liked the orginal Grub, as it provided a nice feature set, but was still configurable by hand and it actually fit into the MBR.

  • [Solved]dual boot windows 7 and arch linux

    I have successfully installed arch linux dual boot with the original win7 on my PC. If I only use linux, then the system works well. The problem is that once I boot into Win7 then after reboot, the linux boot manager will stop working and the system always boots into windows automatically. My guess is Win7 automatically repair the boot loader.
    My current solution is whenever I have finished using Windows, I'll boot with my linux USB installation, and run "gummiboot --path=/boot install". Afterwards, linux will work fine. But I believe there must be a better solution. Any help will be appreciated.
    I have UEFI board by the way.
    Last edited by jl2014 (2015-04-19 17:35:57)

    Thanks for all your help first! I have tried Head_on_a_Stick's suggestions as the first step. Here is what I did. I have created :
    $ cat /boot/loader/entries/windows.conf
    title Windows
    efi /EFI/hidden/Boot/bootmgfw.efi
    The window boot path was :
    /boot/EFI/Microsoft/Boot/bootmgfw.efi
    and I changed
    /boot/EFI/Microsoft
    to
    /boot/EFI/hidden
    After reboot, I clicked 'Windows' option on the linux boot manager. Below are the error messages:
    Windows failed to start.
    File: \EFI\Microsoft/Boot/BCD
    Info: An error occurred while attempting to read the boot configuration data.
    Any idea what goes wrong?
    I'll try other suggestions soon. Thanks all of you again.
    Last edited by jl2014 (2015-04-19 00:03:33)

  • [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)

  • Solved Dual Boot Win7 & Arch quick ?

    Quick setup here. I have win7 installed on 1/2 of my 500GB HD. SDA: my 160GB storage drive.
    I'm in cfdisk during Arch install
    sdb1 Prim NTFS sys reserved. 100MB
    sdb2 Prim NTFS                             250GB
    sdb3 Prim Linux  "my /boot"       100MB
    sdb4 Prim Linux. "/"                      30GB
    Can't' setup my /swap & /home partition it says unusable. 
    Thanks for the help.
    Last edited by mr.marcus (2012-07-06 02:57:44)

    You can't have more than 4  primary partitions. Try extended partitions.
    Edit:
    I don't have swap, home, boot partitions. I have just one root partition.
    Last edited by hadrons123 (2012-07-06 02:01:16)

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

  • [SOLVED] Dual-boot Arch/Windows - 2 hard drives

    Hi Everyone
    I've just installed Arch and I'm having a bit of a problem dual-booting between Arch and Windows XP, which are each on a seperate Hard drive.
    I've done this successfully before with Mepis Linux and Windows XP, but for some reason it's not working this time.   
    The difference is that I've recently purchased a new computer and both Windows and Arch are on SATA drives whereas last time they were both on IDE drives.  Also I'm not sure whether or not to enable SATA AHCI mode in the BIOS (apparently it doesn't work with XP anyways), or SATA port 0-3 Native mode.  Although I've tried all possible combinations and it doesn't seem to work at all.
    Here is my menu.lst file:
    # (0) Arch Linux
    title  Arch Linux
    root   (hd0,0)
    kernel /boot/vmlinuz26 root=/dev/disk/by-uuid/0df05d3b-537c-4576-ad36-1f90a6b01ec0 ro vga=773
    initrd /boot/kernel26.img
    # (1) Windows
    title Windows
    rootnoverify (hd1,0)
    makeactive
    chainloader +1
    When I boot into Arch from Grub it works fine,  but when I try to boot into Windows from Grub, I get this:
    rootnoverify (hd1,0)
    makeactive
    chainloader +1
    and then nothing....No error message or anything. It just hangs.  Does anyone have any ideas as to what's happening? Thanks in advance.
    edit:  It seems I solved the problem by adding these lines to the menu.lst file:
    map (hd0) (hd1)
    map (hd1) (hd0)
    root (hd1,0)
    I can now boot into either Arch or Windows from the Grub menu
    Last edited by axle (2008-09-30 02:35:54)

    This is a question that can very easily be answered by doing a simple google serach.  Google is your friend.  I suggest you start there and come back if you run into issues.

  • [SOLVED] Dual boot with Windows 8, problems after updating Windows

    Hi all,
    I have been maintaining a dual boot of arch and Windows 8 for some time. I recently updated Windows to 8.1, and found that the update process had two side effects:
    1) The update added a new partition in the middle of my file table, so my /etc/fstab which referenced "/dev/sda6" was wrong because that partition is now "/dev/sda7."
    2) The default boot device was switched to the Windows Boot Loader instead of grub. But, this is not a problem because I can work around this by using the "Choose boot device" feature of my bios at start up.
    So, neither of these problems are critical for me at the moment. I can fix my fstab and just press a hotkey at startup.
    EDIT: I have avoided the /etc/fstab issue by referencing my partitions using UUID as specified in https://wiki.archlinux.org/index.php/Fstab.
    How do I set the default boot device back to grub? There is some weirdness here, I think windows is using UEFI booting and my grub uses the old booting system.
    Last edited by bjmnbraun (2014-05-14 19:00:36)

    Rex: I tried that command, got some warning messages regarding blocklists, but no dice.
    Loqs: You are right about windows using a ESP and UEFI while my linux is not booting using UEFI. My bios is configured to try "Legacy boot" first before trying UEFI. Getting linux to boot using UEFI seemed like a pain, so...
    I went into my BIOS settings and found that the Windows Boot Manager boot device was listed in front of my hard disk (which boots linux). I don't think this used to be the case, so something about the update caused my BIOS to reorder the boot devices (probably because the partitions changed).
    Switching my hard disk to be above the Windows Boot Manager in the boot device list now makes me boot into linux by default, and I can boot into windows by pressing a hotkey at bootup and selecting the windows boot manager.

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

  • Dual Boot Windows 7 and Arch with Shared NTFS partition.

    Hi everyone,
    I want to dual boot windows 7 and Arch Linux.
    Here's the problem... my hard drive isn't the biggest.  I want to store all my music, movies, pictures, and documents on partition that both linux and windows can access seamlessly.
    I want the partition to be NTFS.   -- (the programs that map an ext4 drive to Windows are trash).
    Here's what I think I need.
    30GB NTFS to Windows.
    30GB ext4 to Arch Linux
    The remainder (190ish GB) to Shared Data.
    I don't want the swap partition because I have a SSD and 4GB of RAM.
    What is the best way to setup my partitions?  And is this even possible?
    Thanks!

    Not a problem.  I would create:
    First of four primary partitions for windows.
    Second of four primary partitions for /boot
    Third of four partitions is an extended partition encompassing all the space not used by the first two partitions.
    Put everything else inside the extended partition.
    Mine is a bit more complicated, but this should give you an idea:
    ewaller@odin:~ 1005 %sudo fdisk -l /dev/sda
    Password:
    Disk /dev/sda: 320.1 GB, 320072933376 bytes
    255 heads, 63 sectors/track, 38913 cylinders, total 625142448 sectors
    Units = sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 512 bytes / 512 bytes
    Disk identifier: 0x87b33479
    Device Boot Start End Blocks Id System
    /dev/sda1 * 2048 121778159 60888056 7 HPFS/NTFS/exFAT
    /dev/sda2 597366784 625135615 13884416 83 Linux
    /dev/sda3 121778160 597366783 237794312 5 Extended
    /dev/sda5 * 121778223 123770219 995998+ 83 Linux
    /dev/sda6 123770283 131770589 4000153+ 82 Linux swap / Solaris
    /dev/sda7 193213818 597360959 202073571 83 Linux
    /dev/sda8 131781258 193213754 30716248+ 83 Linux
    /dev/sda9 131770591 131781194 5302 1 FAT12
    Partition table entries are not in disk order
    ewaller@odin:~ 1006 %
    Partitions 1 and 2 are Primary partitions.  Partition 3 is an extended partition.  All the others live in partition 3

  • 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 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)

  • T440P Dual Boot Windows 8 with Centos 7

    So I have a T440p with Windows 8 installed. I have been trying to dual boot Centos 7 and also have attempted Centos 6.5. I have been using a bottable USB to perform the installation for both Centos 7 and 6.5.
    When I try the Centos 7 install, I set the boot priority to USB first on startup, and it goes to a screen that lists options to install, verify Centos 7 or troubleshoot. Upon selecting any of these options, everytime I get the error message:
    "alua: not attached"
    When attempting the Centos 6.5 Live DVD install, I try to boot into the Live mode, but it freezes in the process each time.
    I have heard about there being issues dual booting Windows 8 in UEFI mode with another Linux Distrobution.
    Has anyone here sucessfully dual-booted Centos or any other Linux Distrobution on a T440P?
    Any help/advice would be much appreciated.
    Thanks

    It's been many, many years since I don't do dual boot anymore. Don't find the reason to do it, either. Different kinds of virtualization should be enough. Anyway...
    dfw1417 wrote:
    It took over 2 days to figure out how to adjust the bios to get my win 7 pro DVD to boot and install dual boot on this GREAT MACHINE!!
    ENJOY! This is the BEST machine I ever had!
    WHICH machine?
    Cheers.
    If I helped you, please give me some kudos! ^^

Maybe you are looking for