Dual booting encrypted, hidden OS

Hello,
I recently discovered Arch Linux, and am somewhat of a linux noob in general. I have yet to install Arch (computer is in repair).
I know that truecrypt allows users to fully encrypt an operating system, and to then create a hidden operating system within it. At boot, users are prompted for a passphrase, and depending on which one they enter, either one or another of the operating systems boots up.
As I understand it however, truecrypt doesn't encrypt a full system when it comes to linux.
Do you guys think it's possible to use Arch to make an encrypted partition for windows 7, and within it another encrypted partition with Arch? The idea is that while I don't intend to use windows 7 for anything beyond a few simple work-related programs, if I had it encrypted as well, it would give plausible deniability as to the existence of the linux system.
If such a thing is not possible, then another question. I've been looking at the guide here https://wiki.archlinux.org/index.php/Sy … _with_LUKS and it seems like the first thing to be done is to wipe the entire hard disk. I don't want to destroy my existing windows system unless I have to, only create a new partition and then encrypt that with linux. What would change in that guide for that to be the case? How do I tell it to use urandom and encryption only on a specific partition?
Last question: for those of you who have encrypted an entire OS like windows or Arch before, would you say there was a significant or perceptible slowing down (whether on boot or during normal operation). I'd be using a regular 7200 rpm HDD.
Thanks for any help!

kalofet wrote:I'm not sure I really understand how one would enter the OS with the first method.
So, I haven't used Phonebook myself. The fact that it's unmaintained is a barrier; I've also heard it's a PITA to set up and use.
In principle, it would work as follows. You would have a file on some partition that you're willing to leave unencrypted, or at worst, have decrypted. The file would appear to be filled with random data. Suppose you're given a decryption order on this random data. You would have two passwords, like in truecrypt. One password would decrypt innocuous stuff, another password would give access all areas.
The access-all-areas password could hide, say, a mini filesystem. It could hide some directories called usr, dev, lib, proc, and so forth. These could contain some binaries. This is all you need to enter a chroot. Inside the chroot, you could have hidden users that access hidden files and so forth.
After you leave the chroot and close the encrypted userspace filesystem, no one suspects a thing.
kalofet wrote:That seems interesting, but doesn't not having a header risk programs trying to overwrite that space, since they'll think it's unused? But I suppose if it was on it's own partition that I didn't touch, that would work. I'll have to look into this.
That's the idea. The headerless encrypted partition acts just like any other partition filled with random data. Such partitions, filled with random data, are pretty common for people who like distro-hopping, as it's standard to fill partitions with random data before installing on top of them.
kalofet wrote:Does there happen to be a GUI in which I could select which partition to overwrite with random data? Since I wouldn't know what I was doing when using terminal commands unknown to me, I'd more than likely screw up along the way. And screwing up when pointing my computer at which partition to overwrite wouldn't look good
No. If you want to play around with this stuff, I suggest you get used the command line. Take it slowly, and do some practice runs first on a harddrive that doesn't have any data you care about.
If you've never even done an encrypted install before, you should just start there for practice. Really. Just make some new partition on your machine for playing around with, and try making it a LUKS partition containing some distro, and see if you can get to the point where you can boot into it.
If you can't even do that much without help, then really you're playing with fire here.

Similar Messages

  • Linux - OS X dual boot/encryption/shared partition suggestions?

    Hi,
    I've been wanting to encrypt my hard drive for a while and have a MacBook. Currently I have the following setup:
    - sda1: GUID partition table
    - sda2: OS X (~60GB)
    - sda3: Arch (~15GB)
    I mount my OS X partition using HFS+ (non-journaled) and keep everything in the OS X partition except for temp stuff on Linux (downloads I don't care about, various documents I might be working on but will eventually delete or move to OS X). This way, I have one repo for all my files. I use rsync to backup my Arch home dir to OS X and then use Carbon Copy Cloner to backup OS X to an external hard drive.
    Now I'd like to do some encryption... but am not really sure how. Here's two scenarios I've considered after reading a bunch. Thoughts?
    --- Option 1 ---
    - sda1: GUID partition table
    - sda2: HFS+ volume for OS X
    --- TrueCrypt volume to be created and mounted at /home
    - sda3: /boot for Linux
    - sda4: Linux with dm-crypt/LUKS
    --- just / (no LVM making separate partitions)
    --- mount the OS X TrueCrypt volume for filesharing between OSs
    Notes: I don't like this for a couple of reasons.
    - I have to kind of guess at how much OS X will accumulate over time and make my TC volume for /home accordingly. If I ever run into issues... I'll have to backup, delete, make a new and larger TC volume and then copy it all over
    --- Option 2 ---
    - sda1: GUID partition table
    - sda2: OS X
    --- FireVault used on /home
    - sda3: /boot for Linux
    - sda4: Linux with dm-crypt/LUKS
    --- take the plunge and just start keeping all my files on Linux instead of OS X (everything used to be on OS X and I'd just mount the HFS+ drive in Linux to access things)
    --- perhaps create a TC volume file that can be used to share files between partitions via the OS X /Shared directory?
    Notes: I like this better. Everything is encrypted and thus I can just estimate like 15-20GB for OS X and only keep OS X specific files there (iWork, i* files, etc.) and then make the rest of the disk available for Linux. Since dm-crypt can be used for the whole Linux partition I can let everything (/usr, /var, /home) grow however it wants and not worry about my bad partition size/TC container size predictions.
    Remaining issues/questions:
    - Still bummed that I can't just keep everything on one OS or the other and share unless I go the TrueCrypt container for OS X home route. I really like that feature now as, essentially, my Linux /home folder right now is just for .configs and temp... everything I actually care about is only in one place. I don't like the idea of having to "merge" two sets of documents I really care about and make the dir hierarchy work...
    - Unanswered question remains of whether I can mount logical volumes on both OSs. If I have a logical HFS+ volume in an extended partition, can Linux mount that and vice versa (assuming the filesystem is readable by both, that is)?
    - How others get around the issue of making partition size predictions when creating separate partitions for /home vs. /, /usr, etc.
    - What partitions are nice to have on their own (besides /home)?
    Any thoughts? Am I best just going with TrueCrypt? I've read a lot of people who vote against it due to the license, though I'm not clear on why exactly... just not "totally" open-source? For this reason, I guess I'm leaning toward the second option since I can use standard tools on each. I don't think that plausible deniability is a huge deal for me... though perhaps that could be seen as another advantage of TC? I'll shut up now. Serious thanks for any suggestions... I can't find hardly anything on OS X/Linux dual booting and the use of encryption.

    Hi,
    I've been wanting to encrypt my hard drive for a while and have a MacBook. Currently I have the following setup:
    - sda1: GUID partition table
    - sda2: OS X (~60GB)
    - sda3: Arch (~15GB)
    I mount my OS X partition using HFS+ (non-journaled) and keep everything in the OS X partition except for temp stuff on Linux (downloads I don't care about, various documents I might be working on but will eventually delete or move to OS X). This way, I have one repo for all my files. I use rsync to backup my Arch home dir to OS X and then use Carbon Copy Cloner to backup OS X to an external hard drive.
    Now I'd like to do some encryption... but am not really sure how. Here's two scenarios I've considered after reading a bunch. Thoughts?
    --- Option 1 ---
    - sda1: GUID partition table
    - sda2: HFS+ volume for OS X
    --- TrueCrypt volume to be created and mounted at /home
    - sda3: /boot for Linux
    - sda4: Linux with dm-crypt/LUKS
    --- just / (no LVM making separate partitions)
    --- mount the OS X TrueCrypt volume for filesharing between OSs
    Notes: I don't like this for a couple of reasons.
    - I have to kind of guess at how much OS X will accumulate over time and make my TC volume for /home accordingly. If I ever run into issues... I'll have to backup, delete, make a new and larger TC volume and then copy it all over
    --- Option 2 ---
    - sda1: GUID partition table
    - sda2: OS X
    --- FireVault used on /home
    - sda3: /boot for Linux
    - sda4: Linux with dm-crypt/LUKS
    --- take the plunge and just start keeping all my files on Linux instead of OS X (everything used to be on OS X and I'd just mount the HFS+ drive in Linux to access things)
    --- perhaps create a TC volume file that can be used to share files between partitions via the OS X /Shared directory?
    Notes: I like this better. Everything is encrypted and thus I can just estimate like 15-20GB for OS X and only keep OS X specific files there (iWork, i* files, etc.) and then make the rest of the disk available for Linux. Since dm-crypt can be used for the whole Linux partition I can let everything (/usr, /var, /home) grow however it wants and not worry about my bad partition size/TC container size predictions.
    Remaining issues/questions:
    - Still bummed that I can't just keep everything on one OS or the other and share unless I go the TrueCrypt container for OS X home route. I really like that feature now as, essentially, my Linux /home folder right now is just for .configs and temp... everything I actually care about is only in one place. I don't like the idea of having to "merge" two sets of documents I really care about and make the dir hierarchy work...
    - Unanswered question remains of whether I can mount logical volumes on both OSs. If I have a logical HFS+ volume in an extended partition, can Linux mount that and vice versa (assuming the filesystem is readable by both, that is)?
    - How others get around the issue of making partition size predictions when creating separate partitions for /home vs. /, /usr, etc.
    - What partitions are nice to have on their own (besides /home)?
    Any thoughts? Am I best just going with TrueCrypt? I've read a lot of people who vote against it due to the license, though I'm not clear on why exactly... just not "totally" open-source? For this reason, I guess I'm leaning toward the second option since I can use standard tools on each. I don't think that plausible deniability is a huge deal for me... though perhaps that could be seen as another advantage of TC? I'll shut up now. Serious thanks for any suggestions... I can't find hardly anything on OS X/Linux dual booting and the use of encryption.

  • Separately encrypt dual-boot system: Windows+Arch

    Hey guys, I want to use a dual-boot system: Windows 7 + Arch (windows being first on hdd). I would also want to encrypt them, but make it so I could access them with different passwords, like if I enter arch, i woudn't be able to see contents of windows, and vice-versa. I need arch to be on LVM, ext4 filesystem(the latter not so important, if it's trouble).
    I've come accross this guide: https://aprescott.com/posts/dual-bootin … encryption which describes windows 7 encrypted with truecrypt + arch(on lvm) encrypted with dm-crypt+luks, grub legacy is put inside MBR, truecrypt bootloader resides on linux /boot, copied from MBR after truecrypt installed it there and then replaced with GRUB. With described approach there is windows boot partition and linux boot partition which remain unencrypted.
    1) The question is, is it possible to do something similar but make those boot partitions encrypted too? so the only thing unencrypted would be MBR? I've read that people used Disc cryptor and with it easily encrypted windows boot partition with no trouble. What about linux boot partition? Maybe there is a way not to make separate /boot for linux, and encrypt the whole lvm partition with truecrypt(so truecrypt would install it's bootloader into MBR and i could save it and use just like in the link i gave above)?
    2)Another question is for people using truecrypt for whole disk encryption. When you do full disk encryption or system encryption(for example Windows), the only thing left unencrypted is MBR? Is the boot sector of windows partition encrypted too? So in this case it maybe possible to keep MBR(at least the bootloader, without partition table) on separate media.
    3)Also, in case of full disk encryption, is partition table encrypted too?
    and please, I don't want questions as "Why do you need it this way?". I just want to have full disk encryption, so if the MBR is the only thing unencrypted I could keep it on separate media and boot from it(Disc Cryptor allows such feature), but I also need the system to be split into windows and linux parts, accessible by different passwords. And I dont think the idea of using truecrypt hidden partition and hidden os is good in here.
    Thanks in advance.
    Last edited by Kape (2013-01-24 13:58:41)

    hiciu wrote:
    /dev/sda
    +--------------------------------------+
    |(mbr and partition table) |
    | +----------------------------------+ |
    | |(truecrypt) windows boot partition| |
    | |----------------------------------| |
    | |(truecrypt) windows 7 | |
    | |----------------------------------| |
    | |linux boot partition | |
    | |----------------------------------| |
    | |(lvm on luks) | |
    | | +------------------------------+ | |
    | | |rootfs | | |
    | | |------------------------------| | |
    | | |home | | |
    | | |------------------------------| | |
    | | |swap | | |
    | | +------------------------------+ | |
    | +----------------------------------+ |
    +--------------------------------------+
    3)Also, in case of full disk encryption, is partition table encrypted too?
    Take a look at diagram #1 . Mbr and partition table will be not encrypted. You don't want that: there are no sensitive data in there; both windows and linux need to access partition table to know where are partitions on disk; mbr must contain some not encrypted code that will be loaded by bios, since that code can't be encrypted it can be modified (potentially in such a way to hide the modifications from the system), as long as you boot from this device there is no way around it without "secure boot" and mbr singing.
    I believe windows boot partition and windows partition can be encrypted with truecrypt (you need to check that, I don't know truecrypt). There still will be some minimal not encrypted bootloader in order to ask you for for key / passphrase, so it is not 100% secure (someone could replace it; search for "evil maid" attack by Joanna Rutkowska).
    Linux bootloader (I forgot about it on diagram) and linux boot partition can't be encrypted (again, unless you do: truecrypt -> grub2 / syslinux -> linux, and there still will be not encrypted minimal bootloader).
    You see, the problem is always the same: you can't boot from encrypted device. You need something that will decrypt it first.
    I just want to have full disk encryption, so if the MBR is the only thing unencrypted I could keep it on separate media and boot from it(Disc Cryptor allows such feature), but I also need the system to be split into windows and linux parts, accessible by different passwords.
    In order to secure boot partitions / bootloaders one could separate encryption and bootloaders, keep data on encrypted disk and keep bootloaders code at secure location (i.e. on pen drive attached to key chain). Take a look at diagram #2:
    /dev/sda /dev/usb-stick
    +--------------------------------------+ +--------------------------+
    |(mbr and partitions table) | |(mbr and partitions table)|
    | +----------------------------------+ | | +----------------------+ |
    | |other data / partitions | | | |linux boot partition | |
    | +----------------------------------+ | | | +------------------+ | |
    | |(lvm on luks) | | | | |grub / syslinux | | |
    | | +------------------------------+ | | | | |kernel | | |
    | | |rootfs | | | | | |initramfs | | |
    | | |------------------------------| | | | | +------------------+ | |
    | | |home | | | | +----------------------+ |
    | | |------------------------------| | | +--------------------------+
    | | |swap | | |
    | | +------------------------------+ | |
    | +----------------------------------+ |
    +--------------------------------------+
    In this setup you boot your system from usb stick. Bios will load and execute mbr and bootloader from usb stick (and you know its good since you have it physically secured), it should decrypt luks and boot system. You still can run windows with truecrypt using /dev/sda as boot device. I know I didn't exactly answered your questions.
    1)so this way i can leave mbr(including partition table) empty on hdd, while having them on usb stick? good. I can put copy of mbr with truecrypt loader on that usb stick too along with /boot partition just like in the link i gave above? So there would be NOTHING left unencrypted on my hdd? i like it.
    2)My main goal is that hdd would look like blank if someone would want to check its contents. I've heard using Luks leaves some traces in the volume header?(it's not possible to use truecrypt for full linux system encryption too, right?)
    3)How do i properly put /boot on usb stick? Also will there be any troubles updating arch with /boot being on separate media?
    thanks!

  • Win 7 dual boot with SafeBoot encryption halfway there!

    EDIT: Sorry for changing the title. It used to be Need those knowledgeable with Windows (esp. 7) for dual boot input, but I had some success and didn't want to start a whole new post. See the last comment for the update!
    Hi,
    Disclaimer: please don't feel compelled to issue warnings regarding doing this on a work computer. I'm aware of the risks, have talked about what I do on my computer (such as wiping it and installing Linux only over my Win issued encrypted system) with a higher-up in IT that I know well, and I have spoken with IT reps about my running Linux. They don't care; they just don't support it or help. I even have an online community for Linux users at work. I'm searching for a work-around that will allow me dual boot while fully maintaining the protection my company seeks by issuing encrypted systems (i.e. replacing a proprietary encryption tool with an open source one).
    I'm in a tricky situation. At work I'm issued a computer with SafeBoot, a full-disk encryption tool. On my last computer, I simply installed Arch over everything because dual booting was not possible. I really need Windows, but since I had a desktop as well for CAD usage, I used that for Win and just had Linux on the laptop. My lease just came up and I was issued a new laptop for the next three years. In addition, they upgraded the laptop so I can run CAD from it and they'll be taking my Windows desktop.
    So... I'm on a mission to try to find a dual boot solution. I used to run Linux from a flash drive, but sharing data was impossible since I still can't even mount the Win partition and the flash drive isn't big enough to hold anything useful besides the OS itself (8gb). Here's my hope forward:
    - Make a bootable clone of Win 7 while it's running with the hope that it's not encrypted
    - Test it quite repeatedly to make sure I can boot from it
    - Wipe the drive and create a partition for Win and one for Arch
    - Use TrueCrypt (or some other cross-platform encryption system) for Win 7
    - Restore Win 7 from my bootable clone back onto the encrypted partition on the laptop HD
    - Install Arch with LUKS/dm-crypt
    - Be extremely happy and celebrate.
    Does anyone know if the first steps in particular are feasible? I have used Carbon Copy Cloner on my Mac and it can make a bootable clone while the system is running. It's actually quite awesome because you have an incremental backup solution that youc an also boot from in a pinch in case you need to do something to your HD that can't be done when it's mounted. Much faster than booting from the OS X install disk.
    I've been looking for an equivalent on Win and not happy so far. Macrium sounded promising, but when running it, it seems to want to backup to some kind of image file, not simply do a file copy of everything on the drive. Perhaps this will work... I'm just not sure. I also looked at DriveImageXML, but am not sure about that either. I'm using the built-in Win backup tool right now and will see if that works.
    Does anyone know of a tool that will do this? CloneZilla or any Linux tool will not work because a literal clone (like dd) made while the computer is off is worthless. I need a decrypted backup.
    Lastly, any other general input? Does this seem feasible?
    Thanks!
    Last edited by jwhendy (2011-04-15 22:02:07)

    Wow! I can't believe this is working. The rough gist of it is that I think I've found a method that won't require virtualization or fiddling with SafeBoot or having to jump through hoops to either clone while running (to have a decrypted clone), or try to do something like THIS (this is terrifying, since it involves making a clone with dd while it's encrypted and then restoring the SafeBoot encrypted mbr somewhere else later). The gist is like so:
    - Use Win7 built in partition editor to shrink it down as far as possible. For me, this was down to about 130G (out of ~230G)
    - Use same tool to creat two additional partitions: one for Arch and one for TrueCrypt
    - Used Partition Wizard Home Edition to change the type to 0x83 (very necessary)
    - Reboot, install Arch to /dev/sda2
    - Install grub to /dev/sda2, not to the MBR!
    - Reboot into Windows and used EasyBCD to add an archLinux entry to the Win7 boot options
    - Rebooted and tried it out!
    - I'm logged into Arch right now!
    This is actually quite incredible. I think this is about the best I could have asked for. I get to avoid any issues with replacing SafeBoot with something else (even though I'm not sure my IT group really cares [1]), I get a dedicated Linux install, which runs much better and cleaner than virtualizing, and I can share all my stuff via the TrueCrypt partition [2].
    I'll keep everyone posted and will probably end up adding this to the wiki. I think this is a win-win situation. [3]
    Footnotes:
    [1] For example, users are permitted to use their personal Macs at work... but they're not encrypted. People just bring them in and use them. They're obviously not protected, so why would IT care if my computer is encrypted with TrueCrypt vs. SafeBoot when they let people run around with no encryption? Not to mention, as said above, I've talked about my doings with an IT higher-up and he's never said anything of caution about not having encryption -- just suggested I routinely run ClamAV. I did get some strong words of caution on SuperUser. I guess everyone can be happy this way.
    [2] I have yet to set this up, but think it will be far easier than what I just went through!
    [3] The only thing I'm bummed about is that Win7 couldn't be resized any smaller because of unmovable safeboot related files during defrag. It's only using 30G of space right now, but wouldn't shrink below 129G. It doesn't really matter -- I have 30G for Linux and about 80G for my storage. My storage isn't more than 11G for all my work documents right now, so I don't really anticipate blowing through another 70G anytime soon.

  • Win XP (in dual boot) is seeing a hidden partition

    Hi everybody!
    I'm having some difficult in install a win xp in dual boot with win 7 (which came with the G550 notebook).
    I modified the D: (Lenovo) partition to a primary partition to install the XP.  Also I installed the EasyBCD to manage the boots and both S.O. load fine. 
    The problem is that Win XP is seeing a boot partition (the first partition on disk) with 200MB that is hidden for Win 7 !   So this partition takes the C: letter in XP and mess all the configuration once that many programs uses the C: as a default letter. 
    The disk is divided in (approx):
    200 MB hidden partition (from factory)
    160GB with Win 7 installed
    40GB with Win XP installed
    19GB hidden partition (Recovery - from factory)
    Someone has any idea who to solve this problem or  to do a XP installation from the beginning without problems?
    Thanks a lot! 

    first of all, i'm not sure windows xp works on your system.
    secondly, you need to install previous operation system before. you can not install xp on windows 7 or vista.
    if you do that, you may need to change boot volume or make changes on volumes. but one key recover will stop working.
    so, i suggest you not.

  • Wiki article finished: dual boot when SafeBoot encryption is present

    Hi,
    I just started a new article on how to dual boot when one receives a computer with SafeBoot drive encryption installed already. I posted for help on this HERE and HERE if you want some back-story. It wasn't easy, but I'm super excited about the setup now and wanted to write a HowTo. There is a decent amount of discussion about this on the web and I have not found many solutions that aren't a bit convoluted (making backups of the encrypted SafeBoot MBR, then trying to chainload to that file with grub) and I think where I ended up is the simplest, least risky, leaves company issued junk as untouched as possible, and yet provides a dual boot setup with shared file access.
    Best of all, I've not found my setup elsewhere; if that's really the case, it happened on Arch first!
    Check out the article where I've summarized what I did: LINK
    I'm posting here as I wonder if it deserves its own page or if I should merge it with Windows and Arch Dual Boot, which already exists. I could see it either way, so I wanted to ask here. While it would make it easier to find being grouped with the general dual-boot with Win article, it's also fairly specialized so I could see leaving it top level so that it develops a page rank when someone searches for "safeboot linux" or "safeboot dual boot windows" or something like that.
    Thoughts? I hope to finish the article tonight or tomorrow with specifics.
    Last edited by jwhendy (2011-04-20 05:47:23)

    Hi,
    I just started a new article on how to dual boot when one receives a computer with SafeBoot drive encryption installed already. I posted for help on this HERE and HERE if you want some back-story. It wasn't easy, but I'm super excited about the setup now and wanted to write a HowTo. There is a decent amount of discussion about this on the web and I have not found many solutions that aren't a bit convoluted (making backups of the encrypted SafeBoot MBR, then trying to chainload to that file with grub) and I think where I ended up is the simplest, least risky, leaves company issued junk as untouched as possible, and yet provides a dual boot setup with shared file access.
    Best of all, I've not found my setup elsewhere; if that's really the case, it happened on Arch first!
    Check out the article where I've summarized what I did: LINK
    I'm posting here as I wonder if it deserves its own page or if I should merge it with Windows and Arch Dual Boot, which already exists. I could see it either way, so I wanted to ask here. While it would make it easier to find being grouped with the general dual-boot with Win article, it's also fairly specialized so I could see leaving it top level so that it develops a page rank when someone searches for "safeboot linux" or "safeboot dual boot windows" or something like that.
    Thoughts? I hope to finish the article tonight or tomorrow with specifics.
    Last edited by jwhendy (2011-04-20 05:47:23)

  • Dual booted Grub-settings on an encrypted arch-install

    So I recently installed arch on my SATA drive (which is /dev/sda). I encrypted it with the encryption scheme in the standard installer and everything (to my knownledge) is working fine. Now here's the kicker, I want to dual boot Windows 7. I have already installed it on an old IDE drive. However there's a problem, due to how my motherboard recognized the harddrives the Windows 7 drive becomes /dev/sda and arch becomes /dev/sdb. So I set up my BIOS to boot from the SATA drive, and grub loaded as it should, but it failed when trying to boot Arch.
    I tried just changing to /dev/sdb for the root drive in grub, and I also tried using map (hd0) (hd1) and map (hd1) (hd0). Neither worked.
    What grub-settings do I need to have this dual-boot work smoothly?
    - Knut

    sj87 wrote:Maybe you should try mapping sd1 to sd0 instead of the hd* variants?
    This is a setting for GRUB, and from what information I can gather it doesn't seem to work that way.
    Anyone else know anything?

  • Windows XP and Windows 7 dual boot (unable to create partition)

    Hello, 3 months ago I bought in Bangkok a Lenovo S10-2 with 2 GB Memory (it came with 1 GB) and Thai Keyboard (Thai Keyboard is the American Keyboard with the Thai Alphabet)  which works just fine.
    I'd like to install Windows 7 in a new partition and a dual boot with the existing Windows XP. The problem is that It's not possible to create a partition on the C: disk. I've been trying with EASEUS Partition Master, Partition Manager 10 Express and none of them let me do it, only Resizing/Moving the existing partition is an option.
    Hard disk looks as follows:
     C:  Type: NTFS | Size 103.91 GB | Used: 29.49 GB | Unusued: 79.42 GB | Status: System | Pri/Log: Primary
     D: (Lenovo) Type: NTFS | Size 30.38 GB | Used: 1.44 GB | Unusued: 28.95 GB | Status: None| Pri/Log: Logical
     *:  (Hidden) Type: NTFS | Size 14.75 GB | Used: 4.88 GB | Unusued: 9.87 GB | Status: None| Pri/Log: Primary
    After search the forums I didn't find a solution.
    I've read elsewhere that Windows des not allow more than 3 partitions. Is there a safe way to partition the C: volume which has Windows XP and Install Windows Seven along with it?
    Thanks in advance,
    George
    Solved!
    Go to Solution.

    Hi,
    be sure that you backup your system.... partitioning and resizing  is always on risk...
    be sure that you can restore if something goes wrong...
    if you dont know what happens ... dont do this...
    first you can have 3 active (primary & 1 logical ..
    as i have for example 1.XP,2. Win7,3. Ubuntu...and 4. Logical (for common data like music,video,textfiles,picture and...)
    or 4 active primary...(..)
    ...hope that you knows easeus partitionmanager a bit ...
    ...lets have a look :
    so you have ... partition c: (XP) .....  ca. 70 GB .... thats enough room for windows 7...(prefer 30GB workspace)
    start in windows ... start easeus PM .. click on drive c: (XP) and resize to ... GB leave 30 GB black space behind..(for W7)..
    go on this empty space create new primary NTFS partition   ... and after that ,  right click on new primary drive set active !!!! .... click apply button and cross fingers
     ... system will restart and easeus will manage all your changes takes time...
    after restart... prepared for booting windows 7 install and if windows asking you , take the second partition on your harddrive (30 GB)..... and ....so on...  
    thats the way to go ...
    sincerely KalvinKlein
    Thinkies 2x X200s/X301 8GB 256GB SSD @ Win 7 64
    Ideas Centre A520 ,Yoga 2 256GB SSD,Yoga 2 tablet @ Win 8.1

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

  • Dual Booting Windows 7 and Linux on a IdealPad Y580

    Okay, I am a gradaute student and need to have linux dual booted with windows 7 on my y580.  It currently has windows 7 on it. However, it already has four primary partitions.
    C:/ Windows OS
    A hidden OEM
    D:/Lenovo 
    And a boot system drive.
    Is there anyway to convert one of thse drives into an extended partition ?   HowCan I delete one of the partitions ? did you guys get your dual boots to work in this case. Please list step by step if possible. 

    Hello and welcome,
    You can probably finagle the partitions to allow for dual boot: copy the contents of D: to C: and delete D:, for instance.   Speculating, since I don't have an IdeaPad to test on. You usually/probably/maybe lose the OneKey Recovery feature if you touch the partitions.
    Others here on the Linux board may have been able to preserve OKR, but I'll leave that to them to describe since I haven't done it.
    Long way of leading up to the question: is it sufficient to run Linux in a virtual machine, or as a WUBI install within windows?  That keeps things simple and makes backups much easier as well.
    Whatever you do, burn your recovery media first.  Now.
    Z.
    The large print: please read the Community Participation Rules before posting. Include as much information as possible: model, machine type, operating system, and a descriptive subject line. Do not include personal information: serial number, telephone number, email address, etc.  The fine print: I do not work for, nor do I speak for Lenovo. Unsolicited private messages will be ignored. ... GeezBlog
    English Community   Deutsche Community   Comunidad en Español   Русскоязычное Сообщество

  • [Solved]dual boot windows 7 and arch linux

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

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

  • S110 Dual boot Windows 7 and windows xp

    Hello,
    I have purchased lenovo S110 with out of the box windows 7 and microsoft office starter.
    I want to install windows xp as dual boot option, can moderator guide me how to achieve it.
    I have researched a bit and I think I will face issues on the following:
    1. Partioning D drive - allready made d drive to about 100 GB and copied back the lenovo recovery hidden folder
    2. Windoows xp drivers for machine - I could not find windows xp drivers on support.lenovo.com wizard, however in my drive some drivers are allready copied and some of the text files explain installation for windows xp, thus I wanted to try this out.
    3. Making netbook dualboot keeping one key recovery and quickstart working, I think this is the most difficult problem as windows 7 doesnt behaves like xp does and dont know how QS will responnd after xp installation..
    I would request moderators and experts to guide me on this..
    regards,
    Manuj

    Forget about XP man video driver is mission imposible

  • Re: Tecra S11 - Dual boot Windows 7 and XP

    I have installed Windows 7 (from the hidden recovery section of the hardrive) on my new Tecra S11. I would like to know whether I can use the Windows XP
    recovery media provided by Toshiba to create a dual boot Windows 7/Windows XP rather than reverting to XP?

    You can create dual boot but not using two recovery images. Recovery image can be used for first OS installation. You cannot define on which partition the recovery image will be installed. It will always be installed on first partition.
    I recommend you to do follow:
    -at first install WXP using original Toshiba recovery disc
    -Windows 7 install using Microsoft installation disc
    I have done the same on my Satellite A300.

  • Dual booting pre-installed Windows 8 and Linux?

    I just bought a G780 with Windows 8 pre-installed. Ideally, I would also like to install some flavor of Linux. I've been searching but not finding much info on how difficult or time-consuming this would be, or if there are any special considerations or anything. I've found some guides on dual-booting Windows 8 and Linux but they were all for installing Windows straight from a disk, not anything where it's already pre-installed, and some indicated they thought it might be problematic to use a pre-installed version of Windows. Anyway I was hoping that if anybody has done this on the G780 or even a similar laptop that you could share how it went and any difficulties you encountered. I'm open to using any Linux distro if it'll be easy to install. I would appreciate any info you could share. Thanks.

    I had issues with Windows 8 as pre-installed on my G580, my employer at the time was using Windows 7 only and would not allow upgrades for security purposes.  I deleted the entire drive (including hidden) knowing at some point I would re-install Windows 8 or later from retail disk when needed.
    Linux can resize partitions during the install process, but be careful not to disturb the hidden partition or the windows boot loader in the process.  Linux Mint is the best yet for this purpose, OpenSUSE and Fedora failed, CentOS failed and Ubuntu was not able to boot, but did not "hurt" the windows partitions.
    Good luck.

  • OS X and Arch dual-boot on MBP - bootloader error

    I have a Macbook Pro 9,2, and I dual-boot OS X and Arch. My main Arch partition is encrypted with an LVM on LUKS setup, and my main OS X partition is encrypted with Firevault 2. I run the vanilla Arch kernel, and I use xfce as my DE. I use refind as my boot manager, and grub as the bootloader for the Arch partition. This setup has worked flawlessly for several months. I update my Arch system once per week, and last Sunday was a large update since xfce got a large overhaul (in terms of program and config files). However, since the update I cannot boot into OS X (I am posting this here instead of an OS X forum since no change occurred to the OS X system so the problem must be with a change to my Arch system).
    When I attempt to boot into OS X, I am asked for my password to decrypt the partition, but then I get the following error message:
    efiboot loaded from device: Acpi (PNP0A03,0)/Pci(1F12)/SATA(0,0)/HD(Part3.Sig698A
    48BA-88E6-471C-9359-AD63C7EEBE74
    boot file path: \System\Library\CoreServices\boot.efi
    ............Read error 0x6
    Error loading kernel cache (0x6)
    Error: Aborted returned from boot.efi
    *Hit any key to continue*
    Starting boot.efi
    Using load options ''
    efiboot loaded from device: Acpi (PNP0A03,0)/Pci(1F12)/SATA(0,0)/HD(Part3.Sig698A
    48BA-88E6-471C-9359-AD63C7EEBE74
    boot file path: \com.apple.recovery.boot\boot.efi
    .............Read error 0x6
    Error loading kernel cache (0x6)
    Error: Aborted returned from boot.efi
    *Hit any key to continue*
    When I hit a key, I get taken back to the refind menu. If I choose OS X again, I get the same error. This cycle can be repeated ad nauseam. Booting into my Arch partition, on the other hand, works just fine, with one hiccup. While usability does not seem to be reduced, after I input my password to decrypt the Arch partition, and before I see the tty1 login, I (since Sunday) occasionally get the following error message that I have never had before:
    19.636262] [drm:crypt_set_fifo_underrun_reporting] *ERROR* uncleared pch fifo underrun on pch transcoder
    19.636264] [drm:crypt_serr_int_handler] *ERROR* PCH transcoder A FIFO underrun
    19.331860] ata1.00: exception Emask 0x50 SAct 0x1100 SErr 0x280900 action 0x6 frozen
    19.331927] ata1.00: irq_stat 0x08000000, interface fatal error
    19.331974] ata1: SError: {UnrecovData HostInt 10B8B BadCRC }
    19.332821] ata1.00: failed command: READ FPDMA QUEUED
    19.332866] ata1.00: cmd 60/00:40:70:c1:01/01:00:24:00:00/40 tag 8 ncq 131072 in
    19.332866] res 40/00:60:b0:55:2a/00:00:24:00:00/40 Emask 0x50 (ATA bus error)
    19.332176] ata1.00: status: { DRDY }
    The "READ FPDMA QUEUED" line and those below it repeat a few time with different numbers following "cmd" and "res," but then after a few moments the messages clear off the screen and I arrive at my tty1 login screen and from there everything in Arch (including my now-upgraded DE) works normally. This error does not occur during all boots, but I cannot discern any pattern behind when I see it and when I do not. The OS X error and failure to boot occurs every time I try to boot into OS X.
    I have learned a lot as an Arch user, but this problem is beyond me. Google has not been particularly friendly, understandably so given the peculiarity of the problem and my setup. I have not yet tried undoing the update I did on Sunday because (a) it would be a pain since there were >30 packages that were upgraded, and (b) I have no evidence that the upgrade was actually causative of this issue, though I may eventually attempt the downgrade out of desperation if I cannot find a solution. Note that the update I keep referencing did not including a kernel update.
    I appreciate any advice or insight that you can offer.

    I don't have much in the way of a solution for your problem, but to start with, what were the  > 30 packages? In particular, was grub/refind updated (or anything else that would likely touch your efi partition? I know from my own messing with refind, that you can potentially 'damage' your partition layout with certain commands which maybe causing osx not to boot...
    Then again, the errors may have nothing to do with your arch installation and maybe indicative of a different problem all together. Normal procedure is at this point is to backup your complete disk (clone/mirror it, read up on how to do that especially with regards to the encryption systems used), and try to diagnose for any problems the mbp maybe having.
    You could use an apple rescue cd (that may no longer be available with newer mbp , I have no idea..) or maybe use a different harddisk and install osx there and see if you can get everything running 'normally' thus ruling out any funky errors with the hw.  check apple's recovery options if need be.
    I guess you'll just have to fiddle about a bit and try to more closely determine what the actual problem is. and again, backup your stuff!

Maybe you are looking for