[Solved] Arch + W8 dual boot, UEFI, partitioning question

Hello,
I'm buying new laptop with preinstalled W8 (Lenovo E430) and I'm planning to dual boot. I've read Beginner's guide, Installation guide, searched forum, etc., but I'm still unsure how to deal with creating partitions for Arch while keeping Windows.
From the Beginners' Guide:
If you are intending to follow the advice to create a GPT partition table then you need to choose "Advanced" and then select "gpt" from the drop-down menu. This cannot be done if you have a pre-existing Windows installation on the drive which you wish not to destroy.
and from the Partitioning:
To dual-boot with Windows, one must use MBR.
A special exception to this rule: dual-booting Windows 64-bit using UEFI instead of BIOS, one must use GPT.
My W8 will be 64bit and also is Arch.
So, my question is. When I shrink W8 partition and create free space for Arch, do I have to choose 'gpt' option (2nd quote) or not (1st quote) for formatting? Or am I reading it totally wrong?
I would give it a try, but that destroying thing kind of scares me.
Last edited by centos (2013-06-18 19:24:58)

The wiki quotes you've presented make it look like the wiki was created with an MBR/BIOS assumption and then poorly edited to incorporate GPT/EFI information. The rules, presented in a more cohesive way, are these:
Windows ties its partition table type to the computer's firmware: under BIOS, Windows requires MBR; and under EFI, Windows requires GPT.
Linux is more flexible: It can use either MBR or GPT under BIOS. In theory, Linux can use either MBR or GPT under EFI, although many EFIs seem to require GPT, so it's best to stick with GPT on EFI-based computers.
When dual-booting, Windows is the limiting factor when it comes to partition table type.
Most EFIs include a Compatibility Support Module (CSM), which enables them to boot BIOS-based OSes. The CSM can usually be enabled or disabled in the firmware setup utility, although the details of how to do this vary from one implementation to another.
Computers that ship with Windows 8 pre-installed almost always use EFI, and therefore GPT.
Converting from MBR to GPT or vice-versa is possible with GPT fdisk (gdisk, cgdisk, or sgdisk), but this requires re-installing the boot loader for any already-installed OS(es). If Windows is one of those OS(es), it's probably not worth the effort.
GParted and parted can convert from MBR to GPT or vice-versa only by destroying existing partition entries, so you should use these tools to make such a change only on a blank disk or if you intend to lose all the existing partitions.
Since you (centos) say you're installing to a computer with a pre-installed Windows 8, you've almost certainly already got an EFI/GPT setup. Under these circumstances, you won't be choosing a partition table type unless you want to completely wipe that installation and install both OSes fresh. GParted will detect the partition table type and work with it automatically; you should not select the option to create a new partition table, which your first quote (partially) describes. You should, however, be sure that you install Arch in EFI mode and that you install an EFI-mode boot manager and/or boot loader, rather than a BIOS-mode version of GRUB. Getting an EFI-mode Windows and a BIOS-mode Linux to coexist is possible, but awkward. Converting a BIOS-mode Linux installation to boot in EFI mode is also possible, if you mistakenly install in BIOS mode; but it's usually easier to install in EFI mode to begin with. There are lots of threads here on EFI-mode Arch installations, as well as information in the Arch wiki on this topic. Unfortunately, EFI is still new enough that there are still a lot of kinks to be worked out, both in specific firmware implementations (many of them are buggy) and in OS support (which is still not as mature as is BIOS support).

Similar Messages

  • [SOLVED] RTC and dual booting with Windows 8/8.1

    I am planning ahead of installing Arch on a windows 8.1 laptop, and need to understand whether or not the known Windows registry hack to get windows to use UTC for the RTC is still valid for Windows 8/8.1?  I have been searching via google and the usual sources of information, but it is not clear to me if there are problems doing this, specifically if arch is dual booted with Windows 8/8.1 rather than older versions of the MS OS. Certainly I have used the technique without any problem in the past when dual booting Windows XP with Arch on several different machines.
    Does anyone have personal experience with doing this on a Windows 8 or 8.1 machine and can report here on whether it works successfully or not?
    Thanks for any advice.
    Last edited by mcloaked (2014-02-11 21:16:21)

    Since there were no replies at this point I thought I would just go ahead and implement the registry hack on the Windows 8.1 O/S in the laptop and see if Windows behaves.  It appears to be OK, with the displayed time being correct after reboot, and time synchronisation remaining fine with no problems seen in the displayed time, although I won't be able to read the RTC directly until I have completed the Arch install in the coming week or two.  I now don't foresee any issues with the time synchronisation between booting Arch and Windows 8.1 so I will mark this as solved.
    Since the RTC is now in UTC then normal clock config in Arch using chrony should perform normally once the install is done and the new system set up.
    Last edited by mcloaked (2014-02-11 21:17:11)

  • [SOLVED] Longwinded beginner - Dual-boot & partition questions

    Hello,
    I'm interested in installing Arch Linux alongside Windows XP (dual-boot). I have little previous linux experience, although I have rented some servers that have used it in the past, as well as compiling some stuff with it while at University (studying Computer Science). Nevertheless, I am relatively confident that if I can still boot into XP, I will be able to acccustomise myself and like the fact that this distribution seems to be hands-on and leaves a lot up to the user.
    I've been reading the Beginner's Guide and the dual boot guide, and I would like to get started, however, I'm not going to go ahead with this until I am certain that I will be left with a system that can still boot into Windows XP. I assume that it'll take me a while to get to grips with Arch, and in the meantime it would be massively inconvenient if I couldn't work/play/etc...
    What I already know
    Anyway, currently I have a 250GB hard drive that I use for Windows (as well as 3 other hard drives full of stuff). I have partitioned the drive with Windows XP on it with gparted like so:
    (in order)
    UNALLOCATED                         32GB
    SDB1 (Windows XP)                 50GB
    SDB2 (Downloads)                  150GB
    I hope to use the unallocated space to hold linux (and then have access to my other windows drives in the future, using ntfs-3g), however, I am a little confused over what partitions I 'should' have and how large they should be, considering that I will use the OS to mainly develop, browse the web, listen to music, etc...
    I was thinking:
    /boot    -- ext2         -- 100MB
    /          -- ext4         -- 15GB
    swap    --                -- 1GB
    /home  -- ext4         -- 12GB
    /var     -- ReiserFS   -- 4GB
    Questions
    • Is 30GB too little, even though most of my stuff is on other NTFS hard drives?
    • How large should / be? I've read that it contains /bin, /dev, /etc and others. How do I know how much space these need? Am I misunderstanding things?
    • Is a /var partition unnecessary? How large should it be?
    • 10GB for /home, 1GB for swap, 100MB for /boot?
    • Do I need a /tmp or /usr? This is a single-user machine, but I don't want it to get messy!
    • I was thinking of giving /boot ext2, and /var ReiserFS, and then giving every other partition ext4. That okay?
    • Do I need to set these partitions up when installing, or can I set them up in advance with gparted - it might be simpler.
    • Due to already having 2 NTFS primary partitions on the hard disk, I presume that some of the above will need to be logical partitions in an extended partition? How is this done?
    Once the partitions have been set up, and linux is installed, I presume it's just a matter of completing the rest of Part I of the guide, and then ammending /boot/grub/menu.lst to include 'Windows XP'? At that point I am able to restart Windows XP, and only delve into Arch when I want to continue with the configuration, fixing, and so on...
    Sorry for the wall of text, and thanks for your patience. (:
    Last edited by Bedtimes (2009-09-27 14:21:55)

    That's the thing, I expect that I'm doing something wrong with the GRUB loader - and I admit my hard disk layout has been quite strange for a long time before installing linux.
    Basically, it currently looks like this:
    /dev/sda1    ntfs    Music           250GB
    /dev/sdb3    ext2   /boot           120MB
    /dev/dsb4    extended
    ---- /dev/sdb5    linux-swap       1GB
    ---- /dev/sdb6    ext4    /           20GB
    ---- /dev/sdb7    ext4    /home   12GB
    /dev/sdb1    ntfs    Windows XP  50GB
    /dev/sdb2    ntfs    Downloads    150GB
    /dev/sdc1    ntfs    TV & Movies   950GB
    • This list is in order that the entries appear on the hard disk, hence /boot is in the first 1024 cylinders of the hard disk, but as you can see the sdb numbers are actually in the chronological order that I created them.
    • I used an extended partition with logical partitions inside since I had read that there was an issue with more than 4 partitions in a hard disk, and I already had 2 NTFS partitions.
    • When it asked me to install GRUB to the MBR, I installed it to SDB as opposed to SDBx as it asked me to in the manual. This is the drive that contains /boot!
    • I just managed to amend something in the menu.lst, in order that I can boot into Windows XP. Therefore my machine is not totally fucked up any more. (: Unfortunately, what I changed doesn't make sense to me, since I would have expected Windows XP to be on a different hard disk.
    The contents of sdb3:
    grub    kernel26-fallback.img    kernel26.img
    lost+found    System.map26    umlinuz26
    When typing the command /sbin/blkid:
    /dev/sda1: UUID="D0..." LABEL="Music" TYPE="ntfs"
    /dev/sdb1: UUID="A8..." LABEL="Windows XP" TYPE="ntfs"
    /dev/sdb2: UUID="557..." LABEL="Downloads" TYPE="ntfs"
    /dev/sdb3: UUID="2676..." TYPE="ext2"
    /dev/sdb5: UUID="0474..." TYPE="swap"
    /dev/sdb6: UUID="0886..." TYPE="ext4"
    /dev/sdb7: UUID="519becf..." TYPE="ext4"
    /dev/sdc1: UUID="46AC59" LABEL="TV & Movies" TYPE="ntfs"
    Inside /boot/grub/menu.lst:
    timeout 5
    default 0
    color light-blue/black light-cyan/blue
    # (1) Windows XP
    title Windows XP
    rootnoverify (hd0,0)
    chainloader +1
    # (2) Arch Linux
    title Arch Linux
    root (hd1,5)
    kernel /boot/vmlinuz root=/dev/disk/by-uuid/0886... ro vga=773
    initrd          /boot/kernel26.img
    # (3) Arch Linux (Fallback)
    title Arch Linux (Fallback)
    root (hd1,5)
    kernel /boot/vmlinuz root=/dev/disk/by-uuid/0886... ro vga=773
    initrd          /boot/kernel26-fallback.img
    edit: I'm able to access all of the installation partitions with gparted-live's terminal (by mounting the devices I need to access into folders in my root folder), so is there anything else you want me to check/change in order to find my linux root/boot partition?
    Last edited by Bedtimes (2009-09-27 12:54:24)

  • [SOLVED] Lenovo T530 UEFI Arch/Ubuntu Dual boot - Arch fails to boot.

    Hi All,
    I have installed Arch to my Lenovo T530 to dual boot with Ubuntu using UEFI and Grub.
    After installation, Arch is presented to me as an option when my laptop fires up. However, if I select it, the loader goes to a purple screen and then hangs.
    I have attached here the bootloader scripts for my Arch installation (not working), my Ubuntu installation (working) and the output from sudo lsblk -o name,mountpoint,label,size,uuid.
    Please let me know if there is more useful information I can provide. (I have output from Bootinfoscript available but it is quite extensive).
    I am hoping to find out if there is an easily fixable error in the booting scripts used by Grub. If not, I have seen the section on dual booting with Arch in the wiki. My worry is that if I resort to it, UEFI looks to be temperamental at best and I risk breaking my currently working Ubuntu installation.
    Thanks and regards,
    Simon
    Arch boot script (not working):
    setparams 'Arch (on /dev/sda4)'
    insmod part-gpt
    insmod ext2
    set root= 'hd0,gpt4'
    if [ x$feature_platform_search_hint = xy ]; then
    search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt4 -\
    -hint-efi=hd0,gpt4 -hint-baremetal=ahci0,gpt4 729b5164-22c4-4c21-8212-\
    66038d60943e
    else
    search --no-floppy --fs-uuid --set=root 729b5164-22c4-4c21-821\
    2-66038d60943e
    fi
    linux /boot/vmlinuz root=UUID=ad4103fa-d940-47ca-8506-301d\
    8071d467 rw quiet
    initrd /boot/initramfs-linux.img
    Ubuntu boot script (working)
    setparams 'Ubuntu, with Linux 3.13.0-24-generic'
    recordfail
    load_video
    gfxmode $linux_gfx_mode
    insmod gzio
    insmod part-gpt
    insmod ext2
    set root= 'hd0,gpt2'
    if [ x$feature_platform_search_hint = xy ]; then
    search --no-floppy --fs-uuid --set=root --hint-bios=hd\
    0,gpt2 --hint-efi=hd0,gpt2 -hint-baremetal=ahci0,gpt2 542bf27c-0fd5-42\
    4a-b4d8-107f7cf97b75
    else
    search --no-floppy --fs-uuid --set=root 542bf27c-0fd5-\
    424a-b4d8-107f7cf97b75
    fi
    echo 'Loading Linux 3.13.0-24-generic ...'
    linux /boot/vmlinuz-3.13.0-24-generic root=UUID=5\
    42bf27c-0fd5-424a-b4d8-107f7cf97b75 ro quiet spash $vt_handoff
    echo 'Loading initial ramdisk ...'
    initrd /boot/initrd.img-3.13.0-24-generic
    Output from sudo lsblk -o name,mountpoint,label,size,uuid
    NAME MOUNTPOINT LABEL SIZE UUID
    sda 119.2G
    ├─sda1 /boot/efi BOOTLOADER 524M 9360-2939
    ├─sda2 / Linux_Ubuntu 34.6G 542bf27c-0fd5-424a-b4d8-107f7cf97b75
    ├─sda3 [SWAP] Swap 9.8G 7768ae01-6e37-450b-bf0c-d873e3fd06a1
    ├─sda4 Linux_Arch 32.7G 729b5164-22c4-4c21-8212-66038d60943e
    ├─sda5 /media/Data Data 33.2G 5a971a77-685b-43d5-a8e6-c7b407a4c2ff
    └─sda6 Misc_Data 8.5G b165990d-bd25-458f-b2d6-63fae28d0870
    sdb 1T
    └─sdb1 1024G a1ee2f60-007a-4292-982b-7d5f8375fc7e
    sr0 1024M
    Last edited by simon_sjw (2015-03-22 10:43:03)

    linux /boot/vmlinuz root=UUID=ad4103fa-d940-47ca-8506-301d8071d467 rw quiet
    Change the UUID here. Where did that come from?
    EDIT: curiously, if you DuckDuckGo search this exact UUID, it comes up a bunch of times and has caused people headaches before. If you fix that you should be okay. If anyone knows why this same exact UUID would incorrectly be created on multiple systems, I'd love to know. Seems like some kind of issue with dual/triple booting and OS-prober.
    2nd EDIT: this UUID is in the default in grub.cfg. For some reason, it sometimes won't be replaced by grub-mkconfig... Maybe the user didn't run grub-mkconfig, but edited the file him or herself? simon_sjw?
    Last edited by nullified (2015-03-22 03:12:36)

  • [SOLVED] Can't install; dual-boot sharing partitions?

    Hi, I'm currently dual-booting Linux Mint 14 and Windows 7 on my laptop, and decided to replace Mint with Arch. Somehow, though, I don't think I ever divided my HDD into seperate partitions for Linux and Windows. Using gparted (or fdisk), /dev/sda (my HDD) has essentially got a Dell utility partition (100MiB, sda1), a recovery partition (15GiB, sda2), a 1 MiB unallocated space, and a 284 GiB section labeled "OS" (sda3). I can't touch the partition on Linux because it's always in use.
    I can't get through with the installation because of this, and can't find an answer no matter how often or in-depth I RTFM. If someone could point me in the right direction, that'd be great.
    Thanks.
    http://imgur.com/8qfpbbW
    EDIT: This has been [SOLVED].
    Last edited by SELame (2013-07-29 22:55:13)

    I would recommend downloading the gparted cd here, and setting up your partitioning scheme from there. I am quite suprised about your system setup though, you may want to nuke it and start again because something weird is going on.
    Yeah, I'm not sure exactly what's happening. I'll look into using gparted as a LiveCD, but I'd rather not wipe everything if I can help it.
    I don't know if this is the case, but Ubuntu had (has?) an option to install to an image on the windows partition (wubi), rather than a partition of it's own. It's possible that Mint adapted this for their spinoff, and would explain why you only have a Windows partition.
    I recommend that you modify your partition scheme if you want to install Arch. Shrink your Windows partition as much as the Windows partitioner will allow (avoid gparted and similar tools for this purpose, the Windows in-built partitioner should be adequate), then create an extended partition to house your Arch partition, swap partition, data partition, or whatever partitions you want.
    Yeah, I installed Mint from a mounted image in Daemon Tools, so that could explain it. I'll look into shrinking my Windows partition and seeing if I can somehow remove Mint from my Windows partition. I still have grub and all, if that makes any difference.
    there is a mint4win,  do you see something like this on boot? http://i.imgur.com/sPOMx.png
    Yep! I may have installed mint4win. Let me look into that.

  • Migrating from Arch to Dual Boot (Arch 64 + Win8.1 64).

    Hello my friends.
    I used to have a dual boot system (MBR, if I'm not mistaken), with Arch Linux on hda (1TB) and Windows 7 on hdb (300GB). I did this installation more than 3 years ago.
    The disk with windows died recently, and because I need it for work (virtual machine is not an option), I decided to make a "refresh" on my machine.
    I bought two new disks, a 240GB SSD and a 3TB HDD.
    What I would like to do is to install both Windows 8.1 and Arch Linux on the SSD disk (100GB for Windows, 140GB for Arch, my main system), and use the 3TB (for Arch) and the 1TB (for Windows) disks as storage.
    While doing a research on how to do the installation, some questions arised.
    I know that I must (or at least should, for make the processe easier) install Windows first. I will install in the EFI mode, as my machine alread has it.
    1. Which boot loader I should use when installing Arch Linux?
    From what I'd read, to keep things simple, I should opt for a bootloader like gummyboat, that will recognise the Windows without manual intervantion. Is this right?
    2. Will I have problems with the Windows Update?
    I read here https://bbs.archlinux.org/viewtopic.php?id=187194 that when Windows update, it mess with the EFI partition and will make the Arch stop booting (the boot will enter directly on Windows). Is this correct? Is this related only to "automatic" updates (and manual updates can be made without problem)? There is any way to avoid this?
    3. After installing both systems, will Arch Linux recognize my 1TB disk?
    My 1TB disk has my actual Arch linux installation, and data. I would like to copy this data to the 3TB disk and then, under Windows, format it to serve as my Windows storage disk.
    I can do this BEFORE installing the system, or after. But the second option causes me some concerning regarding the rights and so on, so that I do not know if my "new" system" will be able to copy things from the old system.
    Should I make the copy before installing Arch Linux?
    I think this is it.
    If you could helping me with these questions and pointing problems/flaws with my approach, I'll be immensely gratefull.
    Chhers,
    Eduardo.

    Hello elken
    While I could maintain the system under BIOS/MBR, and I don't had any problem with this in the last 2 years, I want to change my system to EFI/GPT.
    I found that Windows under EFI must be under GPT (As pre-installed Windows 8.1), while under BIOS it must be under MBR. So, as my system is (will be) a DUAL one, and It is not a MAC system (that would allow to the EFI/GPT loader to chain a BIOS/MBR, I have to choose between EFI/GPT or BIOS/MBR.
    Because my system can be setup under EFI/GPT, and because sooner or later BIOS/MBR will start to disappear, I want to change it now. This will mke it easier in the future to upgrade my system, I think.
    Not to mention that GPT has some nice advantages over MBR. For example, GPT can handle my 3TB disk without problems, while MBR not. (At least, fdisk wasn't able to deal with it).
    So, you could say that despite BIOS/MBR being fully funcional right now, it's a matter of personal taste (and learning) to me, this desire to completely change my system to EFI/GPT
    For now, I decided to mantain the LINUX and WINDOWS separated (as they are now), i.e., on separate disks. This should solve the problem of windows messing with the boot loader when upgrading (point 2).
    About the bootloader, I think I'll change to gummybot, to test it. I think I could still use grub 2 (I'm not entirely sure), but Gummybot seems simple and fair enough.
    As an aside, I think I will try to migrate my system to the new HDF using rsync and making the necessary adjustments (like in fstab).
    It seems not to difficult, and there are many documents out there on how to do this.
    When I finish, I'll post here how I did and what worked and what not
    Cheers,
    Eduardo

  • Windows 7 / Arch Linux Dual-Boot - win7 keeps changing the boot flag!

    Greetings!
    Its been a long while since I had to dual-boot with windows on the same machine.
    I 've installed windows 7 and then arch linux and installed GRUB on my sda1 where the /boot partitions is located at.
    I've managed to boot into arch successfully and later into windows also successfully.... but when i tried to boot into arch again I wasn't greeted with the typical GRUB boot screen... grub was ignored completely and win7 booting began as if it was the only OS in my hard drive.
    I've used the gparted live cd and realized that the boot flag has changed from my /boot partition (sda1) to my windows partition (sda2). I've changed it back and I was able to boot into arch again. but when I rebooted to win7 and then to arch the same thing has happened. The boot flag keeps changing whenever im rebooting into windows making impossible for me to boot with GRUB unles I manually change the flag again.
    I haven't installed GRUB into the MBR because I hear  it is a bad practice when you have a windows OS also installed (something with service packs not being able to install, among other things). I also don't want to use the easyBCD method to boot arch using the win7 loader.
    here is the partition scheme on my 500gb sata drive :
    /dev/sda1      /boot                 250mb    (primary)
    /dev/sda2      windows 7 ntfs   100gb     (primary)
    /dev/sda3      swap                  4gb        (primary)
    /dev/sda5     /                       16gb        (logical)
    /dev/sda6     /var                   8gb         (logical)
    /dev/sda7     /home               the rest of the hd space   (logical)
    What am I doing wrong and how do i prevent the boot flag from changing?
    Thanks in advance for any help you can give me!
    Last edited by kamigr (2010-01-12 14:35:07)

    naequs wrote:
    bumping this because i have the EXACT same problem !
    however i installed grub to sda1 because i didnt want my installs to mess with each other  (not that ive had any problems with grub in mbr though...) .
    this just looked cleaner to me.
    if anyone has figured out how to prevent windows from automagically changing the bootgflag, id like to know !
    but maybe this is a question more suitable for a windoze forum
    tia
    /edit: seriously, ive been searching the net for some time now, including irc chans and there seems to be no solution to this ! all threads similar to this just end dead !
    i hate how windows claims to own my computer!
    1. don't necrobump
    2. as mentioned in the thread, just install grub to mbr and chainload windows. It works just fine and is the easiest way to get it working reliable.

  • [SOLVED] Unable to dual boot into Windows 8

    I have an Acer Aspire S3 laptop which came with Windows 8 installed. After following the Beginner's Guide to install Arch alongside Windows, Linux works but Windows fails to boot. When I select Windows from the GRUB menu I get kicked out to rescue mode with a "file not found" error. This is a UEFI-GPT setup and in GRUB rescue I get an "unknown filesystem" error when I try to ls the ESP. In fact I get that error for everything except the two ext4 partitions I created during the Arch install.
    I'll just briefly run down (what I think are) the relevant parts of the installation process, then post the output of Boot Info Script at the end.
    Partitions
    I created three partitions during the installation:
    Swap (/dev/sda6)
    Root (/dev/sda7)
    Home (/dev/sda8)
    The disk already had an EFI System Partition (/dev/sda2) so I used that instead of creating my own, mounting it to /boot as described in the beginner's guide (not /boot/efi as in the GRUB docs - not sure if that makes a difference).
    Boot Loader
    I installed and configured GRUB exactly as described in the beginner's guide:
    # pacman -S grub efibootmgr os-prober
    # grub-install --target=x86_64-efi --efi-directory=/boot --bootloader-id=arch_grub --recheck
    # grub-mkconfig -o /boot/grub/grub.cfg
    This appeared to work. Os-prober found my Windows OS ("Found Windows Boot Manager on /dev/sda2@/EFI/Microsoft/Boot/bootmgfw.efi") and added a corresponding menuentry to grub.cfg. On discovering that this didn't actually boot, I added a custom Windows entry per the GRUB dual-boot instructions. That didn't work either.
    Boot Info
    Here is the output from boot info script which includes my grub config, partition info, fstab etc. One strange thing is that the script found every boot file on the ESP except the Windows Boot Manager, including leftover files from short-lived installations of Elementary OS and gummiboot. Maybe Windows is the "Unknown BootLoader" mentioned at the end.
    Boot Info Script 0.61 [1 April 2012]
    ============================= Boot Info Summary: ===============================
    => No boot loader is installed in the MBR of /dev/sda.
    => No boot loader is installed in the MBR of /dev/sdb.
    sda1: __________________________________________________________________________
    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:
    sda2: __________________________________________________________________________
    File system: vfat
    Boot sector type: Unknown
    Boot sector info: No errors found in the Boot Parameter Block.
    Operating System:
    Boot files: /grub/grub.cfg /efi/arch_grub/grubx64.efi
    /efi/Boot/bkpbootx64.efi /efi/Boot/bootx64.efi
    /efi/elementary/grubx64.efi
    /efi/gummiboot/gummibootx64.efi
    sda3: __________________________________________________________________________
    File system:
    Boot sector type: -
    Boot sector info:
    Mounting failed: mount: unknown filesystem type ''
    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: /bootmgr /Windows/System32/winload.exe
    sda5: __________________________________________________________________________
    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:
    sda6: __________________________________________________________________________
    File system: swap
    Boot sector type: -
    Boot sector info:
    sda7: __________________________________________________________________________
    File system: ext4
    Boot sector type: -
    Boot sector info:
    Operating System: Arch Linux ()
    Boot files: /etc/fstab
    sda8: __________________________________________________________________________
    File system: ext4
    Boot sector type: -
    Boot sector info:
    Operating System:
    Boot files:
    sdb1: __________________________________________________________________________
    File system:
    Boot sector type: -
    Boot sector info:
    Mounting failed: mount: unknown filesystem type ''
    mount: unknown filesystem type ''
    sdb2: __________________________________________________________________________
    File system:
    Boot sector type: -
    Boot sector info:
    Mounting failed: mount: unknown filesystem type ''
    mount: unknown filesystem type ''
    mount: unknown filesystem type ''
    ============================ 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 / 4096 bytes
    I/O size (minimum/optimal): 4096 bytes / 4096 bytes
    Partition Boot Start Sector End Sector # of Sectors Id System
    /dev/sda1 1 976,773,167 976,773,167 ee GPT
    GUID Partition Table detected.
    Partition Start Sector End Sector # of Sectors System
    /dev/sda1 2,048 821,247 819,200 Windows Recovery Environment (Windows)
    /dev/sda2 821,248 1,435,647 614,400 EFI System partition
    /dev/sda3 1,435,648 1,697,791 262,144 Microsoft Reserved Partition (Windows)
    /dev/sda4 1,697,792 130,945,023 129,247,232 Data partition (Windows/Linux)
    /dev/sda5 950,145,024 976,773,119 26,628,096 Windows Recovery Environment (Windows)
    /dev/sda6 130,945,024 139,333,631 8,388,608 Swap partition (Linux)
    /dev/sda7 139,333,632 206,442,495 67,108,864 Data partition (Linux)
    /dev/sda8 206,442,496 950,145,023 743,702,528 Data partition (Linux)
    Drive: sdb _____________________________________________________________________
    Disk /dev/sdb: 20.0 GB, 20014718976 bytes, 39091248 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/sdb1 1 4,294,967,295 4,294,967,295 ee GPT
    /dev/sdb1 ends after the last sector of /dev/sdb
    GUID Partition Table detected.
    Partition Start Sector End Sector # of Sectors System
    /dev/sdb1 7,839,744 39,090,175 31,250,432 -
    /dev/sdb2 2,048 7,837,695 7,835,648 -
    "blkid" output: ________________________________________________________________
    Device UUID TYPE LABEL
    /dev/sda1 CCAC5E91AC5E75C4 ntfs Recovery
    /dev/sda2 A05F-051D vfat ESP
    /dev/sda3
    /dev/sda4 4218603F18603457 ntfs ACER
    /dev/sda5 8088627C88627118 ntfs Push Button Reset
    /dev/sda6 d4f5415f-f771-4f9c-ba4a-0f639d055360 swap
    /dev/sda7 90d566ac-57d9-475c-9493-14ba0472d832 ext4
    /dev/sda8 8ab4a486-02d8-4cb4-af91-43acac7e81d7 ext4
    /dev/sdb1
    /dev/sdb2
    ================================ Mount points: =================================
    Device Mount_Point Type Options
    /dev/sda2 /boot vfat (rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro)
    /dev/sda7 / ext4 (rw,relatime,data=ordered)
    /dev/sda8 /home ext4 (rw,relatime,data=ordered)
    ============================= sda2/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
    if [ "${next_entry}" ] ; then
    set default="${next_entry}"
    set next_entry=
    save_env next_entry
    set boot_once=true
    else
    set default="0"
    fi
    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_gpt
    insmod ext2
    set root='hd0,gpt7'
    if [ x$feature_platform_search_hint = xy ]; then
    search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt7 --hint-efi=hd0,gpt7 --hint-baremetal=ahci0,gpt7 90d566ac-57d9-475c-9493-14ba0472d832
    else
    search --no-floppy --fs-uuid --set=root 90d566ac-57d9-475c-9493-14ba0472d832
    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=en_GB
    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 Linux, with Linux core repo kernel' --class arch --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-core repo kernel-true-90d566ac-57d9-475c-9493-14ba0472d832' {
    load_video
    set gfxpayload=keep
    insmod gzio
    insmod part_gpt
    insmod fat
    set root='hd0,gpt2'
    if [ x$feature_platform_search_hint = xy ]; then
    search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt2 --hint-efi=hd0,gpt2 --hint-baremetal=ahci0,gpt2 A05F-051D
    else
    search --no-floppy --fs-uuid --set=root A05F-051D
    fi
    echo 'Loading Linux core repo kernel ...'
    linux /vmlinuz-linux root=UUID=90d566ac-57d9-475c-9493-14ba0472d832 rw quiet
    echo 'Loading initial ramdisk ...'
    initrd /initramfs-linux.img
    menuentry 'Arch 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-90d566ac-57d9-475c-9493-14ba0472d832' {
    load_video
    set gfxpayload=keep
    insmod gzio
    insmod part_gpt
    insmod fat
    set root='hd0,gpt2'
    if [ x$feature_platform_search_hint = xy ]; then
    search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt2 --hint-efi=hd0,gpt2 --hint-baremetal=ahci0,gpt2 A05F-051D
    else
    search --no-floppy --fs-uuid --set=root A05F-051D
    fi
    echo 'Loading Linux core repo kernel ...'
    linux /vmlinuz-linux root=UUID=90d566ac-57d9-475c-9493-14ba0472d832 rw quiet
    echo 'Loading initial ramdisk ...'
    initrd /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/30_os-prober ###
    menuentry 'Windows Boot Manager (on /dev/sda2)' --class windows --class os $menuentry_id_option 'osprober-efi-A05F-051D' {
    insmod part_gpt
    insmod fat
    set root='hd0,gpt2'
    if [ x$feature_platform_search_hint = xy ]; then
    search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt2 --hint-efi=hd0,gpt2 --hint-baremetal=ahci0,gpt2 A05F-051D
    else
    search --no-floppy --fs-uuid --set=root A05F-051D
    fi
    chainloader /EFI/Microsoft/Boot/bootmgfw.efi
    ### 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.
    menuentry "Windoze Ate UEFI-GPT" {
    insmod part_gpt
    insmod fat
    insmod search_fs_uuid
    insmod chain
    search --fs-uuid --set=root --hint-bios=hd0,gpt2 --hint-efi=hd0,gpt2 --hint-baremetal=ahci0,gpt2 A05F-051D
    chainloader /EFI/Microsoft/Boot/bootmgfw.efi
    ### 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 ###
    ### BEGIN /etc/grub.d/60_memtest86+ ###
    ### END /etc/grub.d/60_memtest86+ ###
    =================== sda2: Location of files loaded by Grub: ====================
    GiB - GB File Fragment(s)
    =============================== sda7/etc/fstab: ================================
    # /dev/sda7
    UUID=90d566ac-57d9-475c-9493-14ba0472d832 / ext4 rw,relatime 0 1
    # /dev/sda8
    UUID=8ab4a486-02d8-4cb4-af91-43acac7e81d7 /home ext4 rw,relatime 0 2
    # /dev/sda2 LABEL=ESP
    UUID=A05F-051D /boot vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro 0 2
    # /dev/sda6
    UUID=d4f5415f-f771-4f9c-ba4a-0f639d055360 none swap defaults 0 0
    ======================== Unknown MBRs/Boot Sectors/etc: ========================
    Unknown GPT Partiton Type
    5850cbb887c11947baf0379ca2d4c97e
    Unknown GPT Partiton Type
    dee2bfd3af3ddf11ba40e3a556d89593
    Unknown BootLoader on sda2
    00000000 eb 58 90 4d 53 44 4f 53 35 2e 30 00 02 08 5e 1b |.X.MSDOS5.0...^.|
    00000010 02 00 00 00 00 f8 00 00 3f 00 ff 00 00 88 0c 00 |........?.......|
    00000020 00 60 09 00 51 02 00 00 00 00 00 00 02 00 00 00 |.`..Q...........|
    00000030 01 00 06 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
    00000040 80 01 29 1d 05 5f a0 4e 4f 20 4e 41 4d 45 20 20 |..).._.NO NAME |
    00000050 20 20 46 41 54 33 32 20 20 20 33 c9 8e d1 bc f4 | FAT32 3.....|
    00000060 7b 8e c1 8e d9 bd 00 7c 88 56 40 88 4e 02 8a 56 |{......|[email protected]|
    00000070 40 b4 41 bb aa 55 cd 13 72 10 81 fb 55 aa 75 0a |@.A..U..r...U.u.|
    00000080 f6 c1 01 74 05 fe 46 02 eb 2d 8a 56 40 b4 08 cd |...t..F..-.V@...|
    00000090 13 73 05 b9 ff ff 8a f1 66 0f b6 c6 40 66 0f b6 |.s......f...@f..|
    000000a0 d1 80 e2 3f f7 e2 86 cd c0 ed 06 41 66 0f b7 c9 |...?.......Af...|
    000000b0 66 f7 e1 66 89 46 f8 83 7e 16 00 75 39 83 7e 2a |f..f.F..~..u9.~*|
    000000c0 00 77 33 66 8b 46 1c 66 83 c0 0c bb 00 80 b9 01 |.w3f.F.f........|
    000000d0 00 e8 2c 00 e9 a8 03 a1 f8 7d 80 c4 7c 8b f0 ac |..,......}..|...|
    000000e0 84 c0 74 17 3c ff 74 09 b4 0e bb 07 00 cd 10 eb |..t.<.t.........|
    000000f0 ee a1 fa 7d eb e4 a1 7d 80 eb df 98 cd 16 cd 19 |...}...}........|
    00000100 66 60 80 7e 02 00 0f 84 20 00 66 6a 00 66 50 06 |f`.~.... .fj.fP.|
    00000110 53 66 68 10 00 01 00 b4 42 8a 56 40 8b f4 cd 13 |Sfh.....B.V@....|
    00000120 66 58 66 58 66 58 66 58 eb 33 66 3b 46 f8 72 03 |fXfXfXfX.3f;F.r.|
    00000130 f9 eb 2a 66 33 d2 66 0f b7 4e 18 66 f7 f1 fe c2 |..*f3.f..N.f....|
    00000140 8a ca 66 8b d0 66 c1 ea 10 f7 76 1a 86 d6 8a 56 |..f..f....v....V|
    00000150 40 8a e8 c0 e4 06 0a cc b8 01 02 cd 13 66 61 0f |@............fa.|
    00000160 82 74 ff 81 c3 00 02 66 40 49 75 94 c3 42 4f 4f |[email protected]|
    00000170 54 4d 47 52 20 20 20 20 00 00 00 00 00 00 00 00 |TMGR ........|
    00000180 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
    000001a0 00 00 00 00 00 00 00 00 00 00 00 00 0d 0a 44 69 |..............Di|
    000001b0 73 6b 20 65 72 72 6f 72 ff 0d 0a 50 72 65 73 73 |sk error...Press|
    000001c0 20 61 6e 79 20 6b 65 79 20 74 6f 20 72 65 73 74 | any key to rest|
    000001d0 61 72 74 0d 0a 00 00 00 00 00 00 00 00 00 00 00 |art.............|
    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 ac 01 b9 01 00 00 55 aa |..............U.|
    00000200
    ========= Devices which don't seem to have a corresponding hard drive: =========
    sdc
    =============================== StdErr Messages: ===============================
    cat: /tmp/BootInfo-9VAYCuxc/Tmp_Log: No such file or directory
    /dev/sdc: open failed: No medium found
    No volume groups found
    mdadm: No arrays found in config file or automatically
    I tried tackling this myself and ended up not being able to boot into Linux either. I had to go back to the USB install stick and redo a lot of the installation. I thought I'd better ask for some advice before diving in again. Let me know if you need any more info or log/config files.
    Last edited by pauldice (2013-10-11 03:06:18)

    As mentioned earlier, Fast Startup is off. I disabled it before installing Linux. dosfsck looks clean.
    $ sudo umount /dev/sda2
    $ sudo dosfsck -w -r -l -a -v -t /dev/sda2
    fsck.fat 3.0.22 (2013-07-19)
    fsck.fat 3.0.22 (2013-07-19)
    Checking we can access the last sector of the filesystem
    Boot sector contents:
    System ID "MSDOS5.0"
    Media byte 0xf8 (hard disk)
    512 bytes per logical sector
    4096 bytes per cluster
    7006 reserved sectors
    First FAT starts at byte 3587072 (sector 7006)
    2 FATs, 32 bit entries
    303616 bytes per FAT (= 593 sectors)
    Root directory start at cluster 2 (arbitrary size)
    Data area starts at byte 4194304 (sector 8192)
    75776 data clusters (310378496 bytes)
    63 sectors/track, 255 heads
    821248 hidden sectors
    614400 sectors total
    Checking file /
    Checking file /ESP
    Checking file /grub (GRUB)
    Checking file /EFI
    Checking file /loader (LOADER)
    Checking file /vmlinuz-linux (VMLINU~1)
    Checking file /initramfs-linux.img (INITRA~1.IMG)
    Checking file /initramfs-linux-fallback.img (INITRA~2.IMG)
    Checking file /grub/.
    Checking file /grub/..
    Checking file /grub/x86_64-efi (X86_64~1)
    Checking file /grub/locale (LOCALE)
    Checking file /grub/themes (THEMES)
    Checking file /grub/fonts (FONTS)
    Checking file /grub/grub.cfg (GRUB.CFG)
    Checking file /grub/grubenv (GRUBENV)
    Checking file /grub/grub.cfg.backup (GRUBCF~1.BAC)
    Checking file /grub/grub.efi (GRUB.EFI)
    Checking file /grub/x86_64-efi/.
    Checking file /grub/x86_64-efi/..
    Checking file /grub/x86_64-efi/acpi.mod (ACPI.MOD)
    Checking file /grub/x86_64-efi/adler32.mod (ADLER32.MOD)
    Checking file /grub/x86_64-efi/affs.mod (AFFS.MOD)
    Checking file /grub/x86_64-efi/afs.mod (AFS.MOD)
    Checking file /grub/x86_64-efi/ahci.mod (AHCI.MOD)
    Checking file /grub/x86_64-efi/all_video.mod (ALL_VI~1.MOD)
    Checking file /grub/x86_64-efi/aout.mod (AOUT.MOD)
    Checking file /grub/x86_64-efi/appleldr.mod (APPLELDR.MOD)
    Checking file /grub/x86_64-efi/archelp.mod (ARCHELP.MOD)
    Checking file /grub/x86_64-efi/at_keyboard.mod (AT_KEY~1.MOD)
    Checking file /grub/x86_64-efi/ata.mod (ATA.MOD)
    Checking file /grub/x86_64-efi/backtrace.mod (BACKTR~1.MOD)
    Checking file /grub/x86_64-efi/bfs.mod (BFS.MOD)
    Checking file /grub/x86_64-efi/bitmap.mod (BITMAP.MOD)
    Checking file /grub/x86_64-efi/bitmap_scale.mod (BITMAP~1.MOD)
    Checking file /grub/x86_64-efi/blocklist.mod (BLOCKL~1.MOD)
    Checking file /grub/x86_64-efi/boot.mod (BOOT.MOD)
    Checking file /grub/x86_64-efi/bsd.mod (BSD.MOD)
    Checking file /grub/x86_64-efi/btrfs.mod (BTRFS.MOD)
    Checking file /grub/x86_64-efi/bufio.mod (BUFIO.MOD)
    Checking file /grub/x86_64-efi/cacheinfo.mod (CACHEI~1.MOD)
    Checking file /grub/x86_64-efi/cat.mod (CAT.MOD)
    Checking file /grub/x86_64-efi/cbfs.mod (CBFS.MOD)
    Checking file /grub/x86_64-efi/cbls.mod (CBLS.MOD)
    Checking file /grub/x86_64-efi/cbmemc.mod (CBMEMC.MOD)
    Checking file /grub/x86_64-efi/cbtable.mod (CBTABLE.MOD)
    Checking file /grub/x86_64-efi/cbtime.mod (CBTIME.MOD)
    Checking file /grub/x86_64-efi/chain.mod (CHAIN.MOD)
    Checking file /grub/x86_64-efi/cmdline_cat_test.mod (CMDLIN~1.MOD)
    Checking file /grub/x86_64-efi/cmp.mod (CMP.MOD)
    Checking file /grub/x86_64-efi/configfile.mod (CONFIG~1.MOD)
    Checking file /grub/x86_64-efi/cpio.mod (CPIO.MOD)
    Checking file /grub/x86_64-efi/cpio_be.mod (CPIO_BE.MOD)
    Checking file /grub/x86_64-efi/cpuid.mod (CPUID.MOD)
    Checking file /grub/x86_64-efi/crc64.mod (CRC64.MOD)
    Checking file /grub/x86_64-efi/crypto.mod (CRYPTO.MOD)
    Checking file /grub/x86_64-efi/cryptodisk.mod (CRYPTO~1.MOD)
    Checking file /grub/x86_64-efi/cs5536.mod (CS5536.MOD)
    Checking file /grub/x86_64-efi/date.mod (DATE.MOD)
    Checking file /grub/x86_64-efi/datehook.mod (DATEHOOK.MOD)
    Checking file /grub/x86_64-efi/datetime.mod (DATETIME.MOD)
    Checking file /grub/x86_64-efi/diskfilter.mod (DISKFI~1.MOD)
    Checking file /grub/x86_64-efi/dm_nv.mod (DM_NV.MOD)
    Checking file /grub/x86_64-efi/echo.mod (ECHO.MOD)
    Checking file /grub/x86_64-efi/efi_gop.mod (EFI_GOP.MOD)
    Checking file /grub/x86_64-efi/efi_uga.mod (EFI_UGA.MOD)
    Checking file /grub/x86_64-efi/efifwsetup.mod (EFIFWS~1.MOD)
    Checking file /grub/x86_64-efi/efinet.mod (EFINET.MOD)
    Checking file /grub/x86_64-efi/ehci.mod (EHCI.MOD)
    Checking file /grub/x86_64-efi/elf.mod (ELF.MOD)
    Checking file /grub/x86_64-efi/eval.mod (EVAL.MOD)
    Checking file /grub/x86_64-efi/exfat.mod (EXFAT.MOD)
    Checking file /grub/x86_64-efi/exfctest.mod (EXFCTEST.MOD)
    Checking file /grub/x86_64-efi/ext2.mod (EXT2.MOD)
    Checking file /grub/x86_64-efi/extcmd.mod (EXTCMD.MOD)
    Checking file /grub/x86_64-efi/fat.mod (FAT.MOD)
    Checking file /grub/x86_64-efi/fixvideo.mod (FIXVIDEO.MOD)
    Checking file /grub/x86_64-efi/font.mod (FONT.MOD)
    Checking file /grub/x86_64-efi/fshelp.mod (FSHELP.MOD)
    Checking file /grub/x86_64-efi/functional_test.mod (FUNCTI~1.MOD)
    Checking file /grub/x86_64-efi/gcry_arcfour.mod (GCRY_A~1.MOD)
    Checking file /grub/x86_64-efi/gcry_blowfish.mod (GCRY_B~1.MOD)
    Checking file /grub/x86_64-efi/gcry_camellia.mod (GCRY_C~1.MOD)
    Checking file /grub/x86_64-efi/gcry_cast5.mod (GCRY_C~2.MOD)
    Checking file /grub/x86_64-efi/gcry_crc.mod (GCRY_CRC.MOD)
    Checking file /grub/x86_64-efi/gcry_des.mod (GCRY_DES.MOD)
    Checking file /grub/x86_64-efi/gcry_dsa.mod (GCRY_DSA.MOD)
    Checking file /grub/x86_64-efi/gcry_ecc.mod (GCRY_ECC.MOD)
    Checking file /grub/x86_64-efi/gcry_md4.mod (GCRY_MD4.MOD)
    Checking file /grub/x86_64-efi/gcry_md5.mod (GCRY_MD5.MOD)
    Checking file /grub/x86_64-efi/gcry_rfc2268.mod (GCRY_R~1.MOD)
    Checking file /grub/x86_64-efi/gcry_rijndael.mod (GCRY_R~2.MOD)
    Checking file /grub/x86_64-efi/gcry_rmd160.mod (GCRY_R~3.MOD)
    Checking file /grub/x86_64-efi/gcry_rsa.mod (GCRY_RSA.MOD)
    Checking file /grub/x86_64-efi/gcry_seed.mod (GCRY_S~1.MOD)
    Checking file /grub/x86_64-efi/gcry_serpent.mod (GCRY_S~2.MOD)
    Checking file /grub/x86_64-efi/gcry_sha1.mod (GCRY_S~3.MOD)
    Checking file /grub/x86_64-efi/gcry_sha256.mod (GCRY_S~4.MOD)
    Checking file /grub/x86_64-efi/gcry_sha512.mod (GCRY_S~5.MOD)
    Checking file /grub/x86_64-efi/gcry_tiger.mod (GCRY_T~1.MOD)
    Checking file /grub/x86_64-efi/gcry_twofish.mod (GCRY_T~2.MOD)
    Checking file /grub/x86_64-efi/gcry_whirlpool.mod (GCRY_W~1.MOD)
    Checking file /grub/x86_64-efi/geli.mod (GELI.MOD)
    Checking file /grub/x86_64-efi/gettext.mod (GETTEXT.MOD)
    Checking file /grub/x86_64-efi/gfxmenu.mod (GFXMENU.MOD)
    Checking file /grub/x86_64-efi/gfxterm.mod (GFXTERM.MOD)
    Checking file /grub/x86_64-efi/gfxterm_background.mod (GFXTER~1.MOD)
    Checking file /grub/x86_64-efi/gfxterm_menu.mod (GFXTER~2.MOD)
    Checking file /grub/x86_64-efi/gptsync.mod (GPTSYNC.MOD)
    Checking file /grub/x86_64-efi/gzio.mod (GZIO.MOD)
    Checking file /grub/x86_64-efi/halt.mod (HALT.MOD)
    Checking file /grub/x86_64-efi/hashsum.mod (HASHSUM.MOD)
    Checking file /grub/x86_64-efi/hdparm.mod (HDPARM.MOD)
    Checking file /grub/x86_64-efi/hello.mod (HELLO.MOD)
    Checking file /grub/x86_64-efi/help.mod (HELP.MOD)
    Checking file /grub/x86_64-efi/hexdump.mod (HEXDUMP.MOD)
    Checking file /grub/x86_64-efi/hfs.mod (HFS.MOD)
    Checking file /grub/x86_64-efi/hfsplus.mod (HFSPLUS.MOD)
    Checking file /grub/x86_64-efi/hfspluscomp.mod (HFSPLU~1.MOD)
    Checking file /grub/x86_64-efi/http.mod (HTTP.MOD)
    Checking file /grub/x86_64-efi/iorw.mod (IORW.MOD)
    Checking file /grub/x86_64-efi/iso9660.mod (ISO9660.MOD)
    Checking file /grub/x86_64-efi/jfs.mod (JFS.MOD)
    Checking file /grub/x86_64-efi/jpeg.mod (JPEG.MOD)
    Checking file /grub/x86_64-efi/keylayouts.mod (KEYLAY~1.MOD)
    Checking file /grub/x86_64-efi/keystatus.mod (KEYSTA~1.MOD)
    Checking file /grub/x86_64-efi/ldm.mod (LDM.MOD)
    Checking file /grub/x86_64-efi/legacycfg.mod (LEGACY~1.MOD)
    Checking file /grub/x86_64-efi/linux.mod (LINUX.MOD)
    Checking file /grub/x86_64-efi/linux16.mod (LINUX16.MOD)
    Checking file /grub/x86_64-efi/loadbios.mod (LOADBIOS.MOD)
    Checking file /grub/x86_64-efi/loadenv.mod (LOADENV.MOD)
    Checking file /grub/x86_64-efi/loopback.mod (LOOPBACK.MOD)
    Checking file /grub/x86_64-efi/ls.mod (LS.MOD)
    Checking file /grub/x86_64-efi/lsacpi.mod (LSACPI.MOD)
    Checking file /grub/x86_64-efi/lsefi.mod (LSEFI.MOD)
    Checking file /grub/x86_64-efi/lsefimmap.mod (LSEFIM~1.MOD)
    Checking file /grub/x86_64-efi/lsefisystab.mod (LSEFIS~1.MOD)
    Checking file /grub/x86_64-efi/lsmmap.mod (LSMMAP.MOD)
    Checking file /grub/x86_64-efi/lspci.mod (LSPCI.MOD)
    Checking file /grub/x86_64-efi/lssal.mod (LSSAL.MOD)
    Checking file /grub/x86_64-efi/luks.mod (LUKS.MOD)
    Checking file /grub/x86_64-efi/lvm.mod (LVM.MOD)
    Checking file /grub/x86_64-efi/lzopio.mod (LZOPIO.MOD)
    Checking file /grub/x86_64-efi/mdraid09.mod (MDRAID09.MOD)
    Checking file /grub/x86_64-efi/mdraid09_be.mod (MDRAID~1.MOD)
    Checking file /grub/x86_64-efi/mdraid1x.mod (MDRAID1X.MOD)
    Checking file /grub/x86_64-efi/memdisk.mod (MEMDISK.MOD)
    Checking file /grub/x86_64-efi/memrw.mod (MEMRW.MOD)
    Checking file /grub/x86_64-efi/minicmd.mod (MINICMD.MOD)
    Checking file /grub/x86_64-efi/minix.mod (MINIX.MOD)
    Checking file /grub/x86_64-efi/minix2.mod (MINIX2.MOD)
    Checking file /grub/x86_64-efi/minix2_be.mod (MINIX2~1.MOD)
    Checking file /grub/x86_64-efi/minix3.mod (MINIX3.MOD)
    Checking file /grub/x86_64-efi/minix3_be.mod (MINIX3~1.MOD)
    Checking file /grub/x86_64-efi/minix_be.mod (MINIX_BE.MOD)
    Checking file /grub/x86_64-efi/mmap.mod (MMAP.MOD)
    Checking file /grub/x86_64-efi/morse.mod (MORSE.MOD)
    Checking file /grub/x86_64-efi/mpi.mod (MPI.MOD)
    Checking file /grub/x86_64-efi/msdospart.mod (MSDOSP~1.MOD)
    Checking file /grub/x86_64-efi/multiboot.mod (MULTIB~1.MOD)
    Checking file /grub/x86_64-efi/multiboot2.mod (MULTIB~2.MOD)
    Checking file /grub/x86_64-efi/nativedisk.mod (NATIVE~1.MOD)
    Checking file /grub/x86_64-efi/net.mod (NET.MOD)
    Checking file /grub/x86_64-efi/newc.mod (NEWC.MOD)
    Checking file /grub/x86_64-efi/nilfs2.mod (NILFS2.MOD)
    Checking file /grub/x86_64-efi/normal.mod (NORMAL.MOD)
    Checking file /grub/x86_64-efi/ntfs.mod (NTFS.MOD)
    Checking file /grub/x86_64-efi/ntfscomp.mod (NTFSCOMP.MOD)
    Checking file /grub/x86_64-efi/odc.mod (ODC.MOD)
    Checking file /grub/x86_64-efi/ohci.mod (OHCI.MOD)
    Checking file /grub/x86_64-efi/part_acorn.mod (PART_A~1.MOD)
    Checking file /grub/x86_64-efi/part_amiga.mod (PART_A~2.MOD)
    Checking file /grub/x86_64-efi/part_apple.mod (PART_A~3.MOD)
    Checking file /grub/x86_64-efi/part_bsd.mod (PART_BSD.MOD)
    Checking file /grub/x86_64-efi/part_dfly.mod (PART_D~1.MOD)
    Checking file /grub/x86_64-efi/part_dvh.mod (PART_DVH.MOD)
    Checking file /grub/x86_64-efi/part_gpt.mod (PART_GPT.MOD)
    Checking file /grub/x86_64-efi/part_msdos.mod (PART_M~1.MOD)
    Checking file /grub/x86_64-efi/part_plan.mod (PART_P~1.MOD)
    Checking file /grub/x86_64-efi/part_sun.mod (PART_SUN.MOD)
    Checking file /grub/x86_64-efi/part_sunpc.mod (PART_S~1.MOD)
    Checking file /grub/x86_64-efi/parttool.mod (PARTTOOL.MOD)
    Checking file /grub/x86_64-efi/password.mod (PASSWORD.MOD)
    Checking file /grub/x86_64-efi/password_pbkdf2.mod (PASSWO~1.MOD)
    Checking file /grub/x86_64-efi/pata.mod (PATA.MOD)
    Checking file /grub/x86_64-efi/pbkdf2.mod (PBKDF2.MOD)
    Checking file /grub/x86_64-efi/pcidump.mod (PCIDUMP.MOD)
    Checking file /grub/x86_64-efi/play.mod (PLAY.MOD)
    Checking file /grub/x86_64-efi/png.mod (PNG.MOD)
    Checking file /grub/x86_64-efi/priority_queue.mod (PRIORI~1.MOD)
    Checking file /grub/x86_64-efi/probe.mod (PROBE.MOD)
    Checking file /grub/x86_64-efi/procfs.mod (PROCFS.MOD)
    Checking file /grub/x86_64-efi/raid5rec.mod (RAID5REC.MOD)
    Checking file /grub/x86_64-efi/raid6rec.mod (RAID6REC.MOD)
    Checking file /grub/x86_64-efi/read.mod (READ.MOD)
    Checking file /grub/x86_64-efi/reboot.mod (REBOOT.MOD)
    Checking file /grub/x86_64-efi/regexp.mod (REGEXP.MOD)
    Checking file /grub/x86_64-efi/reiserfs.mod (REISERFS.MOD)
    Checking file /grub/x86_64-efi/relocator.mod (RELOCA~1.MOD)
    Checking file /grub/x86_64-efi/romfs.mod (ROMFS.MOD)
    Checking file /grub/x86_64-efi/scsi.mod (SCSI.MOD)
    Checking file /grub/x86_64-efi/search.mod (SEARCH.MOD)
    Checking file /grub/x86_64-efi/search_fs_file.mod (SEARCH~1.MOD)
    Checking file /grub/x86_64-efi/search_fs_uuid.mod (SEARCH~2.MOD)
    Checking file /grub/x86_64-efi/search_label.mod (SEARCH~3.MOD)
    Checking file /grub/x86_64-efi/serial.mod (SERIAL.MOD)
    Checking file /grub/x86_64-efi/setjmp.mod (SETJMP.MOD)
    Checking file /grub/x86_64-efi/setjmp_test.mod (SETJMP~1.MOD)
    Checking file /grub/x86_64-efi/setpci.mod (SETPCI.MOD)
    Checking file /grub/x86_64-efi/sfs.mod (SFS.MOD)
    Checking file /grub/x86_64-efi/sleep.mod (SLEEP.MOD)
    Checking file /grub/x86_64-efi/spkmodem.mod (SPKMODEM.MOD)
    Checking file /grub/x86_64-efi/squash4.mod (SQUASH4.MOD)
    Checking file /grub/x86_64-efi/tar.mod (TAR.MOD)
    Checking file /grub/x86_64-efi/terminal.mod (TERMINAL.MOD)
    Checking file /grub/x86_64-efi/terminfo.mod (TERMINFO.MOD)
    Checking file /grub/x86_64-efi/test.mod (TEST.MOD)
    Checking file /grub/x86_64-efi/test_blockarg.mod (TEST_B~1.MOD)
    Checking file /grub/x86_64-efi/testload.mod (TESTLOAD.MOD)
    Checking file /grub/x86_64-efi/testspeed.mod (TESTSP~1.MOD)
    Checking file /grub/x86_64-efi/tftp.mod (TFTP.MOD)
    Checking file /grub/x86_64-efi/tga.mod (TGA.MOD)
    Checking file /grub/x86_64-efi/time.mod (TIME.MOD)
    Checking file /grub/x86_64-efi/trig.mod (TRIG.MOD)
    Checking file /grub/x86_64-efi/true.mod (TRUE.MOD)
    Checking file /grub/x86_64-efi/udf.mod (UDF.MOD)
    Checking file /grub/x86_64-efi/ufs1.mod (UFS1.MOD)
    Checking file /grub/x86_64-efi/ufs1_be.mod (UFS1_BE.MOD)
    Checking file /grub/x86_64-efi/ufs2.mod (UFS2.MOD)
    Checking file /grub/x86_64-efi/uhci.mod (UHCI.MOD)
    Checking file /grub/x86_64-efi/usb.mod (USB.MOD)
    Checking file /grub/x86_64-efi/usb_keyboard.mod (USB_KE~1.MOD)
    Checking file /grub/x86_64-efi/usbms.mod (USBMS.MOD)
    Checking file /grub/x86_64-efi/usbserial_common.mod (USBSER~1.MOD)
    Checking file /grub/x86_64-efi/usbserial_ftdi.mod (USBSER~2.MOD)
    Checking file /grub/x86_64-efi/usbserial_pl2303.mod (USBSER~3.MOD)
    Checking file /grub/x86_64-efi/usbserial_usbdebug.mod (USBSER~4.MOD)
    Checking file /grub/x86_64-efi/usbtest.mod (USBTEST.MOD)
    Checking file /grub/x86_64-efi/verify.mod (VERIFY.MOD)
    Checking file /grub/x86_64-efi/video.mod (VIDEO.MOD)
    Checking file /grub/x86_64-efi/video_bochs.mod (VIDEO_~1.MOD)
    Checking file /grub/x86_64-efi/video_cirrus.mod (VIDEO_~2.MOD)
    Checking file /grub/x86_64-efi/video_colors.mod (VIDEO_~3.MOD)
    Checking file /grub/x86_64-efi/video_fb.mod (VIDEO_FB.MOD)
    Checking file /grub/x86_64-efi/videoinfo.mod (VIDEOI~1.MOD)
    Checking file /grub/x86_64-efi/videotest.mod (VIDEOT~1.MOD)
    Checking file /grub/x86_64-efi/videotest_checksum.mod (VIDEOT~2.MOD)
    Checking file /grub/x86_64-efi/xfs.mod (XFS.MOD)
    Checking file /grub/x86_64-efi/xnu.mod (XNU.MOD)
    Checking file /grub/x86_64-efi/xnu_uuid.mod (XNU_UUID.MOD)
    Checking file /grub/x86_64-efi/xzio.mod (XZIO.MOD)
    Checking file /grub/x86_64-efi/zfs.mod (ZFS.MOD)
    Checking file /grub/x86_64-efi/zfscrypt.mod (ZFSCRYPT.MOD)
    Checking file /grub/x86_64-efi/zfsinfo.mod (ZFSINFO.MOD)
    Checking file /grub/x86_64-efi/moddep.lst (MODDEP.LST)
    Checking file /grub/x86_64-efi/command.lst (COMMAND.LST)
    Checking file /grub/x86_64-efi/fs.lst (FS.LST)
    Checking file /grub/x86_64-efi/partmap.lst (PARTMAP.LST)
    Checking file /grub/x86_64-efi/parttool.lst (PARTTOOL.LST)
    Checking file /grub/x86_64-efi/video.lst (VIDEO.LST)
    Checking file /grub/x86_64-efi/crypto.lst (CRYPTO.LST)
    Checking file /grub/x86_64-efi/terminal.lst (TERMINAL.LST)
    Checking file /grub/x86_64-efi/core.efi (CORE.EFI)
    Checking file /grub/x86_64-efi/grub.efi (GRUB.EFI)
    Checking file /grub/locale/.
    Checking file /grub/locale/..
    Checking file /grub/locale/ast.mo (AST.MO)
    Checking file /grub/locale/ca.mo (CA.MO)
    Checking file /grub/locale/da.mo (DA.MO)
    Checking file /grub/locale/de.mo (DE.MO)
    Checking file /grub/locale/[email protected] (DE@HEB~1.MO)
    Checking file /grub/locale/de_CH.mo (DE_CH.MO)
    Checking file /grub/locale/[email protected] (EN@ARA~1.MO)
    Checking file /grub/locale/[email protected] (EN@HEB~1.MO)
    Checking file /grub/locale/[email protected] (EN@PIG~1.MO)
    Checking file /grub/locale/[email protected] ([email protected])
    Checking file /grub/locale/eo.mo (EO.MO)
    Checking file /grub/locale/es.mo (ES.MO)
    Checking file /grub/locale/fi.mo (FI.MO)
    Checking file /grub/locale/fr.mo (FR.MO)
    Checking file /grub/locale/hu.mo (HU.MO)
    Checking file /grub/locale/id.mo (ID.MO)
    Checking file /grub/locale/it.mo (IT.MO)
    Checking file /grub/locale/ja.mo (JA.MO)
    Checking file /grub/locale/lt.mo (LT.MO)
    Checking file /grub/locale/nl.mo (NL.MO)
    Checking file /grub/locale/pa.mo (PA.MO)
    Checking file /grub/locale/pl.mo (PL.MO)
    Checking file /grub/locale/pt_BR.mo (PT_BR.MO)
    Checking file /grub/locale/ru.mo (RU.MO)
    Checking file /grub/locale/sl.mo (SL.MO)
    Checking file /grub/locale/sv.mo (SV.MO)
    Checking file /grub/locale/tr.mo (TR.MO)
    Checking file /grub/locale/uk.mo (UK.MO)
    Checking file /grub/locale/vi.mo (VI.MO)
    Checking file /grub/locale/zh_CN.mo (ZH_CN.MO)
    Checking file /grub/locale/zh_TW.mo (ZH_TW.MO)
    Checking file /grub/themes/.
    Checking file /grub/themes/..
    Checking file /grub/themes/starfield (STARFI~1)
    Checking file /grub/themes/starfield/.
    Checking file /grub/themes/starfield/..
    Checking file /grub/themes/starfield/COPYING.CC-BY-SA-3.0 (COPYIN~1.0)
    Checking file /grub/themes/starfield/README
    Checking file /grub/themes/starfield/blob_w.png (BLOB_W.PNG)
    Checking file /grub/themes/starfield/boot_menu_c.png (BOOT_M~1.PNG)
    Checking file /grub/themes/starfield/boot_menu_e.png (BOOT_M~2.PNG)
    Checking file /grub/themes/starfield/boot_menu_n.png (BOOT_M~3.PNG)
    Checking file /grub/themes/starfield/boot_menu_ne.png (BOOT_M~4.PNG)
    Checking file /grub/themes/starfield/boot_menu_nw.png (BOOT_M~5.PNG)
    Checking file /grub/themes/starfield/boot_menu_s.png (BOOT_M~6.PNG)
    Checking file /grub/themes/starfield/boot_menu_se.png (BOOT_M~7.PNG)
    Checking file /grub/themes/starfield/boot_menu_sw.png (BOOT_M~8.PNG)
    Checking file /grub/themes/starfield/boot_menu_w.png (BOOT_M~9.PNG)
    Checking file /grub/themes/starfield/dejavu_10.pf2 (DEJAVU~1.PF2)
    Checking file /grub/themes/starfield/dejavu_12.pf2 (DEJAVU~2.PF2)
    Checking file /grub/themes/starfield/dejavu_14.pf2 (DEJAVU~3.PF2)
    Checking file /grub/themes/starfield/dejavu_16.pf2 (DEJAVU~4.PF2)
    Checking file /grub/themes/starfield/dejavu_bold_14.pf2 (DEJAVU~5.PF2)
    Checking file /grub/themes/starfield/slider_c.png (SLIDER_C.PNG)
    Checking file /grub/themes/starfield/slider_n.png (SLIDER_N.PNG)
    Checking file /grub/themes/starfield/slider_s.png (SLIDER_S.PNG)
    Checking file /grub/themes/starfield/starfield.png (STARFI~1.PNG)
    Checking file /grub/themes/starfield/terminal_box_c.png (TERMIN~1.PNG)
    Checking file /grub/themes/starfield/terminal_box_e.png (TERMIN~2.PNG)
    Checking file /grub/themes/starfield/terminal_box_n.png (TERMIN~3.PNG)
    Checking file /grub/themes/starfield/terminal_box_ne.png (TERMIN~4.PNG)
    Checking file /grub/themes/starfield/terminal_box_nw.png (TERMIN~5.PNG)
    Checking file /grub/themes/starfield/terminal_box_s.png (TERMIN~6.PNG)
    Checking file /grub/themes/starfield/terminal_box_se.png (TERMIN~7.PNG)
    Checking file /grub/themes/starfield/terminal_box_sw.png (TERMIN~8.PNG)
    Checking file /grub/themes/starfield/terminal_box_w.png (TERMIN~9.PNG)
    Checking file /grub/themes/starfield/theme.txt (THEME.TXT)
    Checking file /grub/fonts/.
    Checking file /grub/fonts/..
    Checking file /grub/fonts/unicode.pf2 (UNICODE.PF2)
    Checking file /EFI/.
    Checking file /EFI/..
    Checking file /EFI/Microsoft (MICROS~1)
    Checking file /EFI/Boot (BOOT)
    Checking file /EFI/elementary (ELEMEN~1)
    Checking file /EFI/arch_grub (ARCH_G~1)
    Checking file /EFI/gummiboot (GUMMIB~1)
    Checking file /EFI/Microsoft/.
    Checking file /EFI/Microsoft/..
    Checking file /EFI/Microsoft/Boot (BOOT)
    Checking file /EFI/Microsoft/Boot/.
    Checking file /EFI/Microsoft/Boot/..
    Checking file /EFI/Microsoft/Boot/bg-BG (BG-BG)
    Checking file /EFI/Microsoft/Boot/BOOT.STL
    Checking file /EFI/Microsoft/Boot/BOOTMGR.EFI
    Checking file /EFI/Microsoft/Boot/cs-CZ (CS-CZ)
    Checking file /EFI/Microsoft/Boot/da-DK (DA-DK)
    Checking file /EFI/Microsoft/Boot/de-DE (DE-DE)
    Checking file /EFI/Microsoft/Boot/el-GR (EL-GR)
    Checking file /EFI/Microsoft/Boot/en-GB (EN-GB)
    Checking file /EFI/Microsoft/Boot/en-US (EN-US)
    Checking file /EFI/Microsoft/Boot/es-ES (ES-ES)
    Checking file /EFI/Microsoft/Boot/et-EE (ET-EE)
    Checking file /EFI/Microsoft/Boot/fi-FI (FI-FI)
    Checking file /EFI/Microsoft/Boot/fr-FR (FR-FR)
    Checking file /EFI/Microsoft/Boot/hr-HR (HR-HR)
    Checking file /EFI/Microsoft/Boot/hu-HU (HU-HU)
    Checking file /EFI/Microsoft/Boot/it-IT (IT-IT)
    Checking file /EFI/Microsoft/Boot/ja-JP (JA-JP)
    Checking file /EFI/Microsoft/Boot/ko-KR (KO-KR)
    Checking file /EFI/Microsoft/Boot/lt-LT (LT-LT)
    Checking file /EFI/Microsoft/Boot/lv-LV (LV-LV)
    Checking file /EFI/Microsoft/Boot/MEMTEST.EFI
    Checking file /EFI/Microsoft/Boot/nb-NO (NB-NO)
    Checking file /EFI/Microsoft/Boot/nl-NL (NL-NL)
    Checking file /EFI/Microsoft/Boot/pl-PL (PL-PL)
    Checking file /EFI/Microsoft/Boot/pt-BR (PT-BR)
    Checking file /EFI/Microsoft/Boot/pt-PT (PT-PT)
    Checking file /EFI/Microsoft/Boot/QPS-PLOC
    Checking file /EFI/Microsoft/Boot/ro-RO (RO-RO)
    Checking file /EFI/Microsoft/Boot/ru-RU (RU-RU)
    Checking file /EFI/Microsoft/Boot/sk-SK (SK-SK)
    Checking file /EFI/Microsoft/Boot/sl-SI (SL-SI)
    Checking file /EFI/Microsoft/Boot/sr-Latn-CS (SR-LAT~1)
    Checking file /EFI/Microsoft/Boot/sv-SE (SV-SE)
    Checking file /EFI/Microsoft/Boot/tr-TR (TR-TR)
    Checking file /EFI/Microsoft/Boot/uk-UA (UK-UA)
    Checking file /EFI/Microsoft/Boot/zh-CN (ZH-CN)
    Checking file /EFI/Microsoft/Boot/zh-HK (ZH-HK)
    Checking file /EFI/Microsoft/Boot/zh-TW (ZH-TW)
    Checking file /EFI/Microsoft/Boot/BOOTSTAT.DAT
    Checking file /EFI/Microsoft/Boot/Fonts (FONTS)
    Checking file /EFI/Microsoft/Boot/Resources (RESOUR~1)
    Checking file /EFI/Microsoft/Boot/BCD
    Checking file /EFI/Microsoft/Boot/BCD.LOG
    Checking file /EFI/Microsoft/Boot/BCD.LOG1 (BCD~1.LOG)
    Checking file /EFI/Microsoft/Boot/BCD.LOG2 (BCD~2.LOG)
    Checking file /EFI/Microsoft/Boot/bootmgfw.efi (BOOTMGFW.EFI)
    Checking file /EFI/Microsoft/Boot/bootx64.efi.grb (BOOTX6~1.GRB)
    Checking file /EFI/Microsoft/Boot/bootx64.efi (BOOTX64.EFI)
    Checking file /EFI/Microsoft/Boot/bootmgfw.bootrepair.efi (BOOTMG~1.EFI)
    Checking file /EFI/Microsoft/Boot/bg-BG/.
    Checking file /EFI/Microsoft/Boot/bg-BG/..
    Checking file /EFI/Microsoft/Boot/bg-BG/bootmgfw.efi.mui (BOOTMG~1.MUI)
    Checking file /EFI/Microsoft/Boot/bg-BG/bootmgr.efi.mui (BOOTMG~2.MUI)
    Checking file /EFI/Microsoft/Boot/cs-CZ/.
    Checking file /EFI/Microsoft/Boot/cs-CZ/..
    Checking file /EFI/Microsoft/Boot/cs-CZ/bootmgfw.efi.mui (BOOTMG~1.MUI)
    Checking file /EFI/Microsoft/Boot/cs-CZ/bootmgr.efi.mui (BOOTMG~2.MUI)
    Checking file /EFI/Microsoft/Boot/cs-CZ/memtest.efi.mui (MEMTES~1.MUI)
    Checking file /EFI/Microsoft/Boot/da-DK/.
    Checking file /EFI/Microsoft/Boot/da-DK/..
    Checking file /EFI/Microsoft/Boot/da-DK/bootmgfw.efi.mui (BOOTMG~1.MUI)
    Checking file /EFI/Microsoft/Boot/da-DK/bootmgr.efi.mui (BOOTMG~2.MUI)
    Checking file /EFI/Microsoft/Boot/da-DK/memtest.efi.mui (MEMTES~1.MUI)
    Checking file /EFI/Microsoft/Boot/de-DE/.
    Checking file /EFI/Microsoft/Boot/de-DE/..
    Checking file /EFI/Microsoft/Boot/de-DE/bootmgfw.efi.mui (BOOTMG~1.MUI)
    Checking file /EFI/Microsoft/Boot/de-DE/bootmgr.efi.mui (BOOTMG~2.MUI)
    Checking file /EFI/Microsoft/Boot/de-DE/memtest.efi.mui (MEMTES~1.MUI)
    Checking file /EFI/Microsoft/Boot/el-GR/.
    Checking file /EFI/Microsoft/Boot/el-GR/..
    Checking file /EFI/Microsoft/Boot/el-GR/bootmgfw.efi.mui (BOOTMG~1.MUI)
    Checking file /EFI/Microsoft/Boot/el-GR/bootmgr.efi.mui (BOOTMG~2.MUI)
    Checking file /EFI/Microsoft/Boot/el-GR/memtest.efi.mui (MEMTES~1.MUI)
    Checking file /EFI/Microsoft/Boot/en-GB/.
    Checking file /EFI/Microsoft/Boot/en-GB/..
    Checking file /EFI/Microsoft/Boot/en-GB/bootmgfw.efi.mui (BOOTMG~1.MUI)
    Checking file /EFI/Microsoft/Boot/en-GB/bootmgr.efi.mui (BOOTMG~2.MUI)
    Checking file /EFI/Microsoft/Boot/en-US/.
    Checking file /EFI/Microsoft/Boot/en-US/..
    Checking file /EFI/Microsoft/Boot/en-US/bootmgfw.efi.mui (BOOTMG~1.MUI)
    Checking file /EFI/Microsoft/Boot/en-US/bootmgr.efi.mui (BOOTMG~2.MUI)
    Checking file /EFI/Microsoft/Boot/en-US/memtest.efi.mui (MEMTES~1.MUI)
    Checking file /EFI/Microsoft/Boot/es-ES/.
    Checking file /EFI/Microsoft/Boot/es-ES/..
    Checking file /EFI/Microsoft/Boot/es-ES/bootmgfw.efi.mui (BOOTMG~1.MUI)
    Checking file /EFI/Microsoft/Boot/es-ES/bootmgr.efi.mui (BOOTMG~2.MUI)
    Checking file /EFI/Microsoft/Boot/es-ES/memtest.efi.mui (MEMTES~1.MUI)
    Checking file /EFI/Microsoft/Boot/et-EE/.
    Checking file /EFI/Microsoft/Boot/et-EE/..
    Checking file /EFI/Microsoft/Boot/et-EE/bootmgfw.efi.mui (BOOTMG~1.MUI)
    Checking file /EFI/Microsoft/Boot/et-EE/bootmgr.efi.mui (BOOTMG~2.MUI)
    Checking file /EFI/Microsoft/Boot/fi-FI/.
    Checking file /EFI/Microsoft/Boot/fi-FI/..
    Checking file /EFI/Microsoft/Boot/fi-FI/bootmgfw.efi.mui (BOOTMG~1.MUI)
    Checking file /EFI/Microsoft/Boot/fi-FI/bootmgr.efi.mui (BOOTMG~2.MUI)
    Checking file /EFI/Microsoft/Boot/fi-FI/memtest.efi.mui (MEMTES~1.MUI)
    Checking file /EFI/Microsoft/Boot/fr-FR/.
    Checking file /EFI/Microsoft/Boot/fr-FR/..
    Checking file /EFI/Microsoft/Boot/fr-FR/bootmgfw.efi.mui (BOOTMG~1.MUI)
    Checking file /EFI/Microsoft/Boot/fr-FR/bootmgr.efi.mui (BOOTMG~2.MUI)
    Checking file /EFI/Microsoft/Boot/fr-FR/memtest.efi.mui (MEMTES~1.MUI)
    Checking file /EFI/Microsoft/Boot/hr-HR/.
    Checking file /EFI/Microsoft/Boot/hr-HR/..
    Checking file /EFI/Microsoft/Boot/hr-HR/bootmgfw.efi.mui (BOOTMG~1.MUI)
    Checking file /EFI/Microsoft/Boot/hr-HR/bootmgr.efi.mui (BOOTMG~2.MUI)
    Checking file /EFI/Microsoft/Boot/hu-HU/.
    Checking file /EFI/Microsoft/Boot/hu-HU/..
    Checking file /EFI/Microsoft/Boot/hu-HU/bootmgfw.efi.mui (BOOTMG~1.MUI)
    Checking file /EFI/Microsoft/Boot/hu-HU/bootmgr.efi.mui (BOOTMG~2.MUI)
    Checking file /EFI/Microsoft/Boot/hu-HU/memtest.efi.mui (MEMTES~1.MUI)
    Checking file /EFI/Microsoft/Boot/it-IT/.
    Checking file /EFI/Microsoft/Boot/it-IT/..
    Checking file /EFI/Microsoft/Boot/it-IT/bootmgfw.efi.mui (BOOTMG~1.MUI)
    Checking file /EFI/Microsoft/Boot/it-IT/bootmgr.efi.mui (BOOTMG~2.MUI)
    Checking file /EFI/Microsoft/Boot/it-IT/memtest.efi.mui (MEMTES~1.MUI)
    Checking file /EFI/Microsoft/Boot/ja-JP/.
    Checking file /EFI/Microsoft/Boot/ja-JP/..
    Checking file /EFI/Microsoft/Boot/ja-JP/bootmgfw.efi.mui (BOOTMG~1.MUI)
    Checking file /EFI/Microsoft/Boot/ja-JP/bootmgr.efi.mui (BOOTMG~2.MUI)
    Checking file /EFI/Microsoft/Boot/ja-JP/memtest.efi.mui (MEMTES~1.MUI)
    Checking file /EFI/Microsoft/Boot/ko-KR/.
    Checking file /EFI/Microsoft/Boot/ko-KR/..
    Checking file /EFI/Microsoft/Boot/ko-KR/bootmgfw.efi.mui (BOOTMG~1.MUI)
    Checking file /EFI/Microsoft/Boot/ko-KR/bootmgr.efi.mui (BOOTMG~2.MUI)
    Checking file /EFI/Microsoft/Boot/ko-KR/memtest.efi.mui (MEMTES~1.MUI)
    Checking file /EFI/Microsoft/Boot/lt-LT/.
    Checking file /EFI/Microsoft/Boot/lt-LT/..
    Checking file /EFI/Microsoft/Boot/lt-LT/bootmgfw.efi.mui (BOOTMG~1.MUI)
    Checking file /EFI/Microsoft/Boot/lt-LT/bootmgr.efi.mui (BOOTMG~2.MUI)
    Checking file /EFI/Microsoft/Boot/lv-LV/.
    Checking file /EFI/Microsoft/Boot/lv-LV/..
    Checking file /EFI/Microsoft/Boot/lv-LV/bootmgfw.efi.mui (BOOTMG~1.MUI)
    Checking file /EFI/Microsoft/Boot/lv-LV/bootmgr.efi.mui (BOOTMG~2.MUI)
    Checking file /EFI/Microsoft/Boot/nb-NO/.
    Checking file /EFI/Microsoft/Boot/nb-NO/..
    Checking file /EFI/Microsoft/Boot/nb-NO/bootmgfw.efi.mui (BOOTMG~1.MUI)
    Checking file /EFI/Microsoft/Boot/nb-NO/bootmgr.efi.mui (BOOTMG~2.MUI)
    Checking file /EFI/Microsoft/Boot/nb-NO/memtest.efi.mui (MEMTES~1.MUI)
    Checking file /EFI/Microsoft/Boot/nl-NL/.
    Checking file /EFI/Microsoft/Boot/nl-NL/..
    Checking file /EFI/Microsoft/Boot/nl-NL/bootmgfw.efi.mui (BOOTMG~1.MUI)
    Checking file /EFI/Microsoft/Boot/nl-NL/bootmgr.efi.mui (BOOTMG~2.MUI)
    Checking file /EFI/Microsoft/Boot/nl-NL/memtest.efi.mui (MEMTES~1.MUI)
    Checking file /EFI/Microsoft/Boot/pl-PL/.
    Checking file /EFI/Microsoft/Boot/pl-PL/..
    Checking file /EFI/Microsoft/Boot/pl-PL/bootmgfw.efi.mui (BOOTMG~1.MUI)
    Checking file /EFI/Microsoft/Boot/pl-PL/bootmgr.efi.mui (BOOTMG~2.MUI)
    Checking file /EFI/Microsoft/Boot/pl-PL/memtest.efi.mui (MEMTES~1.MUI)
    Checking file /EFI/Microsoft/Boot/pt-BR/.
    Checking file /EFI/Microsoft/Boot/pt-BR/..
    Checking file /EFI/Microsoft/Boot/pt-BR/bootmgfw.efi.mui (BOOTMG~1.MUI)
    Checking file /EFI/Microsoft/Boot/pt-BR/bootmgr.efi.mui (BOOTMG~2.MUI)
    Checking file /EFI/Microsoft/Boot/pt-BR/memtest.efi.mui (MEMTES~1.MUI)
    Checking file /EFI/Microsoft/Boot/pt-PT/.
    Checking file /EFI/Microsoft/Boot/pt-PT/..
    Checking file /EFI/Microsoft/Boot/pt-PT/bootmgfw.efi.mui (BOOTMG~1.MUI)
    Checking file /EFI/Microsoft/Boot/pt-PT/bootmgr.efi.mui (BOOTMG~2.MUI)
    Checking file /EFI/Microsoft/Boot/pt-PT/memtest.efi.mui (MEMTES~1.MUI)
    Checking file /EFI/Microsoft/Boot/QPS-PLOC/.
    Checking file /EFI/Microsoft/Boot/QPS-PLOC/..
    Checking file /EFI/Microsoft/Boot/QPS-PLOC/bootmgfw.efi.mui (BOOTMG~1.MUI)
    Checking file /EFI/Microsoft/Boot/QPS-PLOC/bootmgr.efi.mui (BOOTMG~2.MUI)
    Checking file /EFI/Microsoft/Boot/QPS-PLOC/memtest.efi.mui (MEMTES~1.MUI)
    Checking file /EFI/Microsoft/Boot/ro-RO/.
    Checking file /EFI/Microsoft/Boot/ro-RO/..
    Checking file /EFI/Microsoft/Boot/ro-RO/bootmgfw.efi.mui (BOOTMG~1.MUI)
    Checking file /EFI/Microsoft/Boot/ro-RO/bootmgr.efi.mui (BOOTMG~2.MUI)
    Checking file /EFI/Microsoft/Boot/ru-RU/.
    Checking file /EFI/Microsoft/Boot/ru-RU/..
    Checking file /EFI/Microsoft/Boot/ru-RU/bootmgfw.efi.mui (BOOTMG~1.MUI)
    Checking file /EFI/Microsoft/Boot/ru-RU/bootmgr.efi.mui (BOOTMG~2.MUI)
    Checking file /EFI/Microsoft/Boot/ru-RU/memtest.efi.mui (MEMTES~1.MUI)
    Checking file /EFI/Microsoft/Boot/sk-SK/.
    Checking file /EFI/Microsoft/Boot/sk-SK/..
    Checking file /EFI/Microsoft/Boot/sk-SK/bootmgfw.efi.mui (BOOTMG~1.MUI)
    Checking file /EFI/Microsoft/Boot/sk-SK/bootmgr.efi.mui (BOOTMG~2.MUI)
    Checking file /EFI/Microsoft/Boot/sl-SI/.
    Checking file /EFI/Microsoft/Boot/sl-SI/..
    Checking file /EFI/Microsoft/Boot/sl-SI/bootmgfw.efi.mui (BOOTMG~1.MUI)
    Checking file /EFI/Microsoft/Boot/sl-SI/bootmgr.efi.mui (BOOTMG~2.MUI)
    Checking file /EFI/Microsoft/Boot/sr-Latn-CS/.
    Checking file /EFI/Microsoft/Boot/sr-Latn-CS/..
    Checking file /EFI/Microsoft/Boot/sr-Latn-CS/bootmgfw.efi.mui (BOOTMG~1.MUI)
    Checking file /EFI/Microsoft/Boot/sr-Latn-CS/bootmgr.efi.mui (BOOTMG~2.MUI)
    Checking file /EFI/Microsoft/Boot/sv-SE/.
    Checking file /EFI/Microsoft/Boot/sv-SE/..
    Checking file /EFI/Microsoft/Boot/sv-SE/bootmgfw.efi.mui (BOOTMG~1.MUI)
    Checking file /EFI/Microsoft/Boot/sv-SE/bootmgr.efi.mui (BOOTMG~2.MUI)
    Checking file /EFI/Microsoft/Boot/sv-SE/memtest.efi.mui (MEMTES~1.MUI)
    Checking file /EFI/Microsoft/Boot/tr-TR/.
    Checking file /EFI/Microsoft/Boot/tr-TR/..
    Checking file /EFI/Microsoft/Boot/tr-TR/bootmgfw.efi.mui (BOOTMG~1.MUI)
    Checking file /EFI/Microsoft/Boot/tr-TR/bootmgr.efi.mui (BOOTMG~2.MUI)
    Checking file /EFI/Microsoft/Boot/tr-TR/memtest.efi.mui (MEMTES~1.MUI)
    Checking file /EFI/Microsoft/Boot/uk-UA/.
    Checking file /EFI/Microsoft/Boot/uk-UA/..
    Checking file /EFI/Microsoft/Boot/uk-UA/bootmgfw.efi.mui (BOOTMG~1.MUI)
    Checking file /EFI/Microsoft/Boot/uk-UA/bootmgr.efi.mui (BOOTMG~2.MUI)
    Checking file /EFI/Microsoft/Boot/zh-CN/.
    Checking file /EFI/Microsoft/Boot/zh-CN/..
    Checking file /EFI/Microsoft/Boot/zh-CN/bootmgfw.efi.mui (BOOTMG~1.MUI)
    Checking file /EFI/Microsoft/Boot/zh-CN/bootmgr.efi.mui (BOOTMG~2.MUI)
    Checking file /EFI/Microsoft/Boot/zh-CN/memtest.efi.mui (MEMTES~1.MUI)
    Checking file /EFI/Microsoft/Boot/zh-HK/.
    Checking file /EFI/Microsoft/Boot/zh-HK/..
    Checking file /EFI/Microsoft/Boot/zh-HK/bootmgfw.efi.mui (BOOTMG~1.MUI)
    Checking file /EFI/Microsoft/Boot/zh-HK/bootmgr.efi.mui (BOOTMG~2.MUI)
    Checking file /EFI/Microsoft/Boot/zh-HK/memtest.efi.mui (MEMTES~1.MUI)
    Checking file /EFI/Microsoft/Boot/zh-TW/.
    Checking file /EFI/Microsoft/Boot/zh-TW/..
    Checking file /EFI/Microsoft/Boot/zh-TW/bootmgfw.efi.mui (BOOTMG~1.MUI)
    Checking file /EFI/Microsoft/Boot/zh-TW/bootmgr.efi.mui (BOOTMG~2.MUI)
    Checking file /EFI/Microsoft/Boot/zh-TW/memtest.efi.mui (MEMTES~1.MUI)
    Checking file /EFI/Microsoft/Boot/Fonts/.
    Checking file /EFI/Microsoft/Boot/Fonts/..
    Checking file /EFI/Microsoft/Boot/Fonts/CHS_BOOT.TTF
    Checking file /EFI/Microsoft/Boot/Fonts/CHT_BOOT.TTF
    Checking file /EFI/Microsoft/Boot/Fonts/JPN_BOOT.TTF
    Checking file /EFI/Microsoft/Boot/Fonts/KOR_BOOT.TTF
    Checking file /EFI/Microsoft/Boot/Fonts/malgunn_boot.ttf (MALGUN~1.TTF)
    Checking file /EFI/Microsoft/Boot/Fonts/malgun_boot.ttf (MALGUN~2.TTF)
    Checking file /EFI/Microsoft/Boot/Fonts/meiryon_boot.ttf (MEIRYO~1.TTF)
    Checking file /EFI/Microsoft/Boot/Fonts/meiryo_boot.ttf (MEIRYO~2.TTF)
    Checking file /EFI/Microsoft/Boot/Fonts/msjhn_boot.ttf (MSJHN_~1.TTF)
    Checking file /EFI/Microsoft/Boot/Fonts/msjh_boot.ttf (MSJH_B~1.TTF)
    Checking file /EFI/Microsoft/Boot/Fonts/msyhn_boot.ttf (MSYHN_~1.TTF)
    Checking file /EFI/Microsoft/Boot/Fonts/msyh_boot.ttf (MSYH_B~1.TTF)
    Checking file /EFI/Microsoft/Boot/Fonts/segmono_boot.ttf (SEGMON~1.TTF)
    Checking file /EFI/Microsoft/Boot/Fonts/segoen_slboot.ttf (SEGOEN~1.TTF)
    Checking file /EFI/Microsoft/Boot/Fonts/segoe_slboot.ttf (SEGOE_~1.TTF)
    Checking file /EFI/Microsoft/Boot/Fonts/wgl4_boot.ttf (WGL4_B~1.TTF)
    Checking file /EFI/Microsoft/Boot/Resources/.
    Checking file /EFI/Microsoft/Boot/Resources/..
    Checking file /EFI/Microsoft/Boot/Resources/BOOTRES.DLL
    Checking file /EFI/Microsoft/Boot/Resources/en-US (EN-US)
    Checking file /EFI/Microsoft/Boot/Resources/en-US/.
    Checking file /EFI/Microsoft/Boot/Resources/en-US/..
    Checking file /EFI/Microsoft/Boot/Resources/en-US/bootres.dll.mui (BOOTRE~1.MUI)
    Checking file /EFI/Boot/.
    Checking file /EFI/Boot/..
    Checking file /EFI/Boot/bkpbootx64.efi (BKPBOO~1.EFI)
    Checking file /EFI/Boot/bootx64.efi (BOOTX64.EFI)
    Checking file /EFI/elementary/.
    Checking file /EFI/elementary/..
    Checking file /EFI/elementary/grubx64.efi (GRUBX64.EFI)
    Checking file /EFI/arch_grub/.
    Checking file /EFI/arch_grub/..
    Checking file /EFI/arch_grub/grubx64.efi (GRUBX64.EFI)
    Checking file /EFI/gummiboot/.
    Checking file /EFI/gummiboot/..
    Checking file /EFI/gummiboot/gummibootx64.efi (GUMMIB~2.EFI)
    Checking file /loader/.
    Checking file /loader/..
    Checking file /loader/entries (ENTRIES)
    Checking file /loader/loader.conf (LOADER~1.CON)
    Checking file /loader/entries/.
    Checking file /loader/entries/..
    Checking file /loader/entries/arch.conf (ARCH~1.CON)
    Checking for bad clusters.
    Reclaiming unconnected clusters.
    Checking free cluster summary.
    /dev/sda2: 500 files, 14626/75776 clusters
    srs5694 wrote:No, it definitely looks in EFI/Microsoft/Boot for boot loader files.
    I'm not sure it does. This is the only mention of efi files I can find in the script.
    # Check FAT filesystems for EFI boot files.
    for file in "${mountname}"/efi/*/*.efi ; do
    # Remove "${mountname}" part of the filename.
    file="${file#${mountname}}";
    if [ -f "${mountname}${file}" ] && [ -s "${mountname}${file}" ] && FileNotMounted "${mountname}${file}" "${mountname}" ; then
    BootFiles="${BootFiles} ${file}";
    fi
    done
    Looking for "${mountname}"/efi/*/*.efi will only pick up files one level down from, say, /boot/EFI. Files in /boot/EFI/Microsoft/Boot are two levels down. I copied bootx64.efi into /boot/EFI/Microsoft and the script picked it up. This is with the latest version of bootinfoscript afaik.
    $ bootinfoscript -v
    Boot Info Script version: 0.61
    Release date: 1 April 2012

  • How to install Arch for dual-boot with Win 7 (on 2 hard drives)?

    Hello,
    the TLDR first: how exactly should I proceed when setting up GRUB for 2 hard drives to dual-boot Arch (64 bit)and Win 7 (64 bit)?
    Long version: So, I have the following hard drive & partition layout:
    On my first hard drive (250 GB big) I have: Win 7 64 bit, all the programs for Windows and of course the EFI partition
    My second hard drive is 1 TB big and formatted in NTFS and it only contains data. It has 2 partitions, one is about 750 GB big and used for simple storage.
    Sidenote 1: sometimes my disk management (Windows' own gparted) shows either the little disk or the big one as disk 0. Don't know what exactly this means, but I have never ever experienced any problems whatsoever during use.
    Sidenote 2: the UEFI motherboard (ASRock H67M) cannot boot into Legacy mode.
    I want to install Arch on a ~200 GB partition on the second hard drive (the one with 1 TB). (click here if you want to see a screenshot) I am posting this because I am confused with how exactly I should deal with the whole "2 hdds & UEFI" thing.
    So how exactly should I proceed when setting up GRUB for this setup?
    For partitioning I suppose I would have to use fdisk or cgdisk. I used cgdisk before and found it to be straightforward. Then, because I have experienced my fair share of problems with rEFInd, I'd like to use GRUB.
    Last edited by jones (2013-06-29 14:36:56)

    First thing you should do is become familiar with your motherboard.
    http://www.asrock.com/mb/manual.asp?Model=H67M
    This will probably help you out in understanding the sidenote 1 thingie (hdd's on sata3 and/or sata2 connectors)
    As on sidenote 2, according to the manual it seems to be possible to boot legacy mode,  see Storage Configuration.

  • [SOLVED] How to dual boot windows on separate drive with syslinux

    I'm trying to follow the directions from the arch syslinux wiki to add a windows dual boot option to my current syslinux.
    I have two hard drives: sda (windows MBR) and sdc (arch linux GPT). My BIOS is set to boot sdc, and syslinux is currently installed fine to boot arch linux off of sdc. I would like to add an entry to boot windows.
    I added an entry to /boot/syslinux/syslinux.cfg that looks like
    LABEL windows
    MENU LABEL Windows
    COM32 chain.c32
    APPEND mbr:0xf00f1fd3 # my actual identifier for sda from fdisk is here
    When I rebooted, I saw the new entry in the syslinux menu. When I went to arch linux, it booted fine. When I rebooted again and selected windows, it hung with a blinking underscore. The next time I rebooted, it didn't even get to the syslinux menu and just hung with a blinking underscore.
    I booted from my rescue arch usb drive. In fdisk, sdc's partition table now mirrored sda's! In other words, it looked like I had windows partitions on my linux drive, and it had the same MBR identifier even though it was supposed to be GPT. I ran gdisk /dev/sdc, it detected both GPT and MBR, and I asked it to use the GPT table and wrote out the partitions, and my drive looked normal again. I ran arch-chroot, syslinux-install_update, and everything was fine the next time I booted.
    Any advice on how I can set up windows dual boot with syslinux?
    Last edited by mikemintz (2013-08-17 18:25:46)

    I am assuming that you use Bios and not UEFI (I am not that quite familiar with UEFI).
    1) You must configure the Bios to boot from the disk where syslinux is installed, having a correct mbr and with syslinux correctly installed.
    2) The disk where windows reside must be bootable by itself with a valid mbr.
    It may be possible that windows try to boot from the linux disk (and of course fails), try to add the swap option to the chain command.
    To check if Windows is correctly installed, try to boot it directly from the Bios.
    The mbr of the syslinux disk should be gptmbr.bin:
    dd if=/usr/lib/syslinux/gptmbr.bin of=/dev/sd<letter of the linux disk> bs=440 count=1
    Warning: Be very careful with what you do with dd, it is very easy to destroy all your data!
    Last edited by olive (2013-08-17 08:31:44)

  • Installing Arch WinXP Dual-Boot

    Hello! I'm new with Arch-Linux.
    I'm trying to install Arch with Windows XP. I looked at the guide and several threads but I can not solve my problem. I make an installation in "Legacy" because my drive is IDE. I have installed Win XP. I do manually the partitions partitions / boot, /, / swap, / home, all logic, after the XP ntfs. And then I install  the grub in the MBR which is on the XP partition. When booting, I get a dual-boot XP and I started without problems, but when I boot Arch I get the following problem:
    FileSystem CHECK FAILED
    And here  I have not managed to solve anything, I have consulted several forum threads where people could think the same thing, wiki, but I have not been solved. If anyone can help me with the installation, or if I am wrong partition table or something, I would be very helpful.
    Sorry about my English, it isn't my frist language.
    Last edited by xunele (2009-11-13 11:48:32)

    I can see two issues here:
    I install  the grub in the MBR which is on the XP partition
    The MBR is not on any partition, is sits at the beginning of your disk. Partitions have bootsectors. And you should not install anything into the boot sector of the XP partition, since that will make XP unable to boot. Wikipedia is quite good on these topics.
    Secondly, /boot must be on a primary partition.

  • Windows 7 and Arch linux dual boot problem

    hey guys I had an issue with windows 7 dual booted with arch and i was just wondering my windows 7 crashed. I had Reinstalled windows OS and all my partitions are set up but now when I try to boot up arch I cant at all cause windows Boot took over and i have no way of getting into arch is there anyway i can fix this or maybe reinstall arch without loseing my home folder with all my data, or is there just and easyer way to fix this issue im stuck.  thank you all for your support as i am a noob

    You need to re-install grub. When you reinstalled Windows it will overwrite grub preventing you booting Arch. You'll need to boot from a liveCD and chroot into your Arch installation. details for recovering grub are in the wiki - https://wiki.archlinux.org/index.php/GR … stallation

  • [SOLVED]Trying to dual boot -- Not working so well.

    I've had arch and windows 7 dual booted before on this computer, but for some reason I cannot seem to replicate my initial steps to success.
    My current setup is:
    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: 0x0003b81c
    Device Boot Start End Blocks Id System
    /dev/sda1 * 63 208844 104391 83 Linux
    /dev/sda2 208845 1269134 530145 82 Linux swap / Solaris
    /dev/sda3 1269135 32001479 15366172+ 83 Linux
    /dev/sda4 32001480 625137344 296567932+ 83 Linux
    Sda1 = Boot Partition
    Sda2 = Swap Space
    Sda3 = Root
    Sda4 = Home
    I'm trying to figure out how to add Windows 7 to this.  Now, one thing I have tired was to delete my home partition,  create an extended partition that would include space for a windows 7 install and another home partition.
    Basically split sda4 into two logical partitions.
    That works fine, I can reboot into arch linux and change the UUID in the fstab table to point to my new home directory, but on installing Windows 7 I have to have another partition for the 100mb sys reserve.
    Can I make 3 logical paritions in the current sda4 setup?  Then just have windows install to those two locations?
    Last edited by Si1v3r (2011-08-25 21:17:01)

    Inxsible wrote:
    I am not sure Windows 7 can be installed in an extended partition. It requires primary. also, it tends to create a 100 MB hidden partition for system files which probably needs to be primary as well. So right of the bat, you need to spare 2 primary partitions for Windows. You can however move your Arch install in an extended.
    take my advice, install Windows first and then re-install Arch. It'd be a lot easier.
    Windows MUST be installed to a primary partition.
    To successfully install Windows on the same disc as an existing Arch / Linux installation you will want to pre-create an Primary NTFS partition right at the front of the drive (to prevent Windows greedily using 2 of your total 4 primary partitions) and flag all you Linux partitions as "hidden" so the Windows installer cannot "see" them - this can be checked from the windows setup before committing to anything. Once Windows is installed you can the unflag the hidden linux partition and start re-establishing Arch. I can be done but it is time consuming and very easy to get badly wrong.
    This really is no mean feat as you will need to be familiar with moving partitions with gparted (from a liveCD), flagging partitions as hidden, reinstalling and reconfiguring grub etc etc.
    As inxsible says - it is easier (and quicker) to wipe your drive and install Windows 1st.
    Back up all your data onto dvd / ext usb, copy across any custom rc.conf etc files that have been tweaked along the way to somewhere safe - boot into a live ISO and nuke away. If you create your windows partition in advance you will only use 1 primary partition as stated above - leave it to the windows installer and you lose 2 to windows
    I would also suggest creating an extended partition and your logical partition layout for Arch from a liveCD / gparted once Windows is installed to smooth the Arch install process.
    If your previous Arch was installed from the old ISO - now would be a good time to grab the new one
    Last edited by satanselbow (2011-08-25 09:25:25)

  • [SOLVED] Arch won't boot after I created a separate /var parition

    Arch won't boot after I created a separate /var parition on an existing installation.And let me confess: it was maybe stupid trying to do it on an existing install.
    I edited the fstab correctly, copied the files using rsync preserving permissions. Then I kept a backup of /var using tar. Then went on to delete everything under /var, ie /var/*, the /var folder is still there. All this I did from a live CD. After that I booted into my arch linux. Here I get messages about systemd successfully finishing fsck on each of my partitions, then the screen starts blinking. And there is no more output. Pressing Ctrl+Alt+Delete causes systemd to stop its services and reboot.
    Having realized I had borked my system, I removed the /var line from fstab and restored /var from the tar file I made earlier. Again I did this from a live cd. Rebooted into my arch system, and again similar issues, namely that after fsck and messages informing a few services had started, the screen keeps blinking.
    The live cd I used for reorganizing my partitions was elementary OS freya. They have GParted in there. I also have an arch install iso lying aroung from May 2013. If necessary, I can download the latest version. I am currently typing from a Windows installation I dual boot from.
    I don't know how to extract any boot logs as I am locked out of the system. Here is my fstab in any case:
    # Filesystem information
    # /dev/sda5 LABEL=fs_root
    UUID=b9d739cf-fd8c-46dd-a919-bd827dc47c66 / ext4 rw,noatime,data=ordered 0 1
    # /dev/sda9 LABEL=fs_var
    UUID=ec0f7a49-dccd-43ab-8651-9aa3fdb41cc7 /var ext4 rw,noatime,data=ordered 0 2
    # /dev/sda2 LABEL=fs_boot
    UUID=0e8ab31a-3bda-4b85-a901-a36f21b1583d /boot ext2 rw,noatime 0 2
    # /dev/sda6 LABEL=fs_home
    UUID=d9e63c47-274e-447f-ad01-0d97afe0fd34 /home ext4 rw,noatime,data=ordered 0 2
    # /dev/sda7 LABEL=fs_swap
    UUID=7301227c-e9f3-41b8-9d0f-4cf3c159491c none swap defaults 0 0
    # /dev/sda3 LABEL=fs_win
    UUID=12B639D1B639B5D7 /fs_win ntfs uid=1000,gid=1000,dmask=027,fmask=137,showexec,nofail,noauto,x-systemd.automount 0 0
    # /dev/sda3 LABEL=fs_share
    UUID=D272269772268079 /fs_share ntfs uid=1000,gid=1000,dmask=027,fmask=137,showexec,noauto,nofail,x-systemd.automount 0 0
    I would greatly appreciate any help.
    Last edited by richcocoa (2015-05-03 18:04:44)

    Have you moved everything from /var to /new_var (i named it for learning purpose)? You shoud copy content from /var but not on the fly but booting from arch iso cd, and than you shoud mount your / into arch-chroot environement, mount all of your mount points and than copy content from default /var to new /var. The copying should be done with this
    cp -rax
    and you can add -v switch to verbose output. I have my own /var moved the same way.
    The simples way is:
    -boot the arch iso cd
    -mount all of your mount point (i created here in this step /new_var to move /var to a new place, and this /new_var i put in /etc/fstab as /var later)
    -copy /var to /new_var with -rax or -vrax (recursive, archive, this filesystem or verbose, recursive, archive, this filesystem switches)
    -umount all of it
    -reboot.
    Last edited by firekage (2015-05-02 07:49:20)

  • Dual Booting & Recovery Partition

    Hi all, I am going to dual-boot Windows 7 and Lubuntu on my Satellite A505-S6009. I am sure some people severely disagree with dual-booting, but this is what I want to do with my machine (my mind is made up). I have installed and used Linux before. I have also done a dual-boot for my NB205, which went smoothly and easily; however, I have a question about dual-booting on my Satellite. If install Lubuntu and have two partitions--one for Lubuntu, one for Windows 7--on my machine, will the machine's recovery partition be deleted? I think I should mention that when I install any OS, I usually go through the "recommended" partitioning process, and not the "advanced." (I have a lot to learn about partitions before I move on to advanced). Thanks, all

    Satellite A505-S6009 
    If install Lubuntu and have two partitions--one for Lubuntu, one for Windows 7--on my machine, will the machine's recovery partition be deleted?
    Yes.
    Essentially by definition, if you have only two partitions then the others are gone.
    -Jerry

Maybe you are looking for

  • Pages version is too old!

    I want to open a pages document.  It says my version for pages is 4. something.  And it is too old to open document.  When I go to the App store, it says it is already downloaded and purchased.  I tried putting it in trash and then downloading it aga

  • Different tabs and formula in workcenter for capacity and scheduling.

    Dear All, I wanted to have a logical explanation for why we use different formula for capacity req calculation and scheduling. why we need 2 tabs for this in work center. As per Std SAP formula, except the tick of capacity generation and allowed for

  • Can't write to windows server

    First off, I'm not sure if this is the correct place to post this question. I am having a problem with the windows server where I work. I can copy files from the server without a problem, but if I try to write a file to the server I get the following

  • Touch screen display for HP Pavillion IPS LED Backlit Monitor

    Does it exist?

  • Adobe Professional 9

    hola quiero saber ahora a alguien a manejar Adobe Professional 9 su nuevo programa para mí y no he podrían recibir apoyo Sólo quiero saber cómo puedo copiar y pegar o importar imágenes con el fin de añadir un logotipo de un pdf de mi empresa, o ¿Qué