• \[SOLVED\] Installation - Gummiboot + UEFI + GPT + Linux only


    I’m trying to install Antergos in a [ UEFI + GPT + Linux only/Single OS ] system.

    Partition scheme:

    500GB HDD:

    /dev/sda1 = swap
    /dev/sda2 = /home

    32GB mSATA:

    /dev/sdb1 = ESP
    /dev/sdb2 = /


    The problem is: I use the default installer, but I don’t mount ESP (/dev/sdb1). I let the system install normally, and after that I don’t reboot. I open the terminal, mount the ESP (/dev/sdb1) to [ /install/boot/ ], but when I try [ # gummiboot install ] or [ gummiboot install --path /install/boot/ ] I get the following error: [ File system /install/boot/ is not an EFI System Partition (ESP) ], but actually it’s, isn’t it?

    How can I proceed?

  • I’m trying to install Antergos in a [ UEFI + GPT + Linux only/Single OS ] system.

    Partition scheme:

    500GB HDD:

    /dev/sda1 = swap
    /dev/sda2 = /home

    32GB mSATA:

    /dev/sdb1 = ESP
    /dev/sdb2 = /


    The problem is: I use the default installer, but I don’t mount ESP (/dev/sdb1). I let the system install normally, and after that I don’t reboot. I open the terminal, mount the ESP (/dev/sdb1) to [ /install/boot/ ], but when I try [ # gummiboot install ] or [ gummiboot install --path /install/boot/ ] I get the following error: [ File system /install/boot/ is not an EFI System Partition (ESP) ], but actually it’s, isn’t it?

    How can I proceed?

  • You do not have any versions of Windows installed and plan to only install linux correct? Personally I would check if there is an option in your BIOS setup to disable UEFI boot. The only real need for it is if you wanted to dual boot with Windows 7 or 8. If you cant disable it then I would use Grub2 (grub-bios). Check out the wiki article below. It walks you through the installation on UEFI step by step. It is written for Arch linux but I think it will be helpful. Steps 1-10 explain the partitioning (which I believe you have a good understanding of) then you can skip all the way to step 22 b/c our installer will do the install. I suggest using the CLI installer for this. We have had some reports of partition file system types not being written to disk as selected in the Graphical Installer. (Its being worked on) Let me know if this works for you.

    Walkthrough of UEFI install: [http://pcavdisor.blogspot.com/2012/11/beginners-guide-to-installing-archlinux.html][0]">[http://pcavdisor.blogspot.com/2012/11/b][1] … linux.html

    Secure Boot w/ GRUB2: [https://wiki.archlinux.org/index.php/GRUB#UEFI_systems][0]">[https://wiki.archlinux.org/index.php/GRUB#UEFI_systems][2]

    [0]: <a href=
    [1]: http://pcavdisor.blogspot.com/2012/11/b
    [2]: https://wiki.archlinux.org/index.php/GRUB#UEFI_systems

  • Thanks, I used CLI Installer, but when reboot I get:

    nouveau […] unknown Fermi chipset
    nouveau […] unknown chipset, 0x0d7000a2
    nouveau […] failed to create 0x80000080, -22

    My graphics card is a GT 630M. My GPU is a [i:3ar7g2jn]nonfree[/i:3ar7g2jn], and the installer automatically use [i:3ar7g2jn]nouveau[/i:3ar7g2jn], I think that’s the problem…

    How can I proceed?


    I tried reinstalling, and now I got stuck at:

    [ *** ] A start job is running for dev-disk-by\x2uuid-637D\x2d275C.service

    And after a moment I get:

    [ TIME ] Timed out waiting for device dev-disk-by\x2uuid-637D\x2d275C.service
    [DEPEND] Dependency failed for /boot/efi.
    [DEPEND] Dependency failed for Local File System.

    Welcome to emergency mode! After …


    The system will surely be a Linux only, and yes, I can disable UEFI in BIOS, but, I think that my system boots up faster with UEFI enabled, and an UEFI OS installed, this can be a false impression, I don’t know.

    [b:3ar7g2jn]So, Antergos in BIOS mode and Antergos in UEFI mode, is there a performance/security difference between these two, technically speaking?[/b:3ar7g2jn]

  • From what I have read of user experiences from multiple distributions, the general consensus is that using UEFI method shortens boot time. How significant of an improvement, I am unsure. Some users have seen boot times that are 10-30 seconds faster while others said its about the same. I purchased my latest laptop last year and it was a model that launched the year before so I just slipped by as UEFI was coming out. Bottom line: as UEFI isnt going anywhere and it can be faster, I would go with it now to get the learning curve out of the way if it were me!

    Now onto the issue at hand. I have not been able to come up with a sure answer and I have searched EXTENSIVELY. It is possible that the kernel and init imgs from the 1st install were not overwritten when you re installed. Try regenerating with “sudo mkinitcpio -p linux” If you can get back to the state of display drivers failing you may want to try bumblebee diver with your specific model.
    [https://wiki.archlinux.org/index.php/Bumblebee#Installing_Bumblebee_with_Intel_.2F_nvidia][0]">[https://wiki.archlinux.org/index.php/Bu][1] … .2F_nvidia

    I will continue to look into this further and post any updates.

    [0]: <a href=
    [1]: https://wiki.archlinux.org/index.php/Bu

  • Thanks, I’ll reinstall the system and try again…

    [b:3i0xbtv6][Update][/b:3i0xbtv6] same problem:

    [ *** ] A start job is running for dev-disk-by\ … …

    I don’t know why this problem occurs, I made a normal installation with CLI, GParted, UEFI x86_64, GRUB2, basically a standard installation…

  • Did you follow steps 1-10 on the guide I originally referred you to? I remember it saying something about /dev/mapper UUIDs having to be manually entered. Check it out: [http://pcavdisor.blogspot.com/2012/11/beginners-guide-to-installing-archlinux.html][0]">[http://pcavdisor.blogspot.com/2012/11/b][1] … linux.html

    Edit: Oops its actually step 12 which I had told you to skip, sorry lol

    [0]: <a href=
    [1]: http://pcavdisor.blogspot.com/2012/11/b

  • If I understood correctly (what I think, don’t), you asked me to:

    • Do steps 1 to 10 from the external site;
    • And then install via CLI Installer, and skip the Disk Preparation, as I’ve already mounted the partitions by hand.

    So, I did this, but I get “Installation Failed.”

    Did I do something wrong, didn’t I?

  • Yes that is the process I gave you. And I added that step 12 would need to be followed after installation. Is “installation Failed” the only information presented to you on screen? I looked over the steps again and the process should work. I will make an attempt in VB to see if I can reproduce this error. There may be more information on the error in /var/log or /var/cache/pacman

  • @“lots.0.logs”:35dmjzvr said:

    Yes that is the process I gave you. And I added that step 12 would need to be followed after installation. Is “installation Failed” the only information presented to you on screen? I looked over the steps again and the process should work. I will make an attempt in VB to see if I can reproduce this error. There may be more information on the error in /var/log or /var/cache/pacman[/quote:35dmjzvr]

    Thanks, I’m waiting.

    Unfortunately, I’ve already formatted the disk to try again, and again, with other options, changes, so I can’t see if there was something in logs/var, but when I tried to press “OK” in this message I couldn’t get out of there, I was stuck at that message…

  • Anything new?

  • Sorry for the delay, I was at my day job :-/ lol…I am confused. Are you running CLI in the terminal or from a separate VT? I ask this because if you just ran it in terminal as it is launched from the start up prompt you can still access the entire live system and obtain logs. Try it from terminal and then post the output of:

    sudo journalctl -bm
    

    also any of these logs you may find:

    /var/log/pacman.log -or- /var/cache/pacman/pacman.log
    /var/log/gdm/:0-greeter.log
    /tmp/CLI.log or (similar)

    I cannot remember where the CLI logs are saved and I’m not able to run it at the moment. Its either there or in /var/cache I believe.If you cannot find any logs for the failed installation the output is also fed to VT7 so you should be able to at least read it there.

  • The CLI installer saves the pacman’s log in /tmp/pacman.log, that’s the one you need to look to see why failed

  • That’s the problem, I’ve already formatted the USB, but I’ll try to install again (UEFI + GPT).

  • Tried again but failed.

    > Live USB boot in UEFI
    > CLI Installer
    > Partitioning with GParted:

    /dev/sda1 = swap
    /dev/sda2 = /home (ext4)
    /dev/sdb1 = ESP (fat32)
    /dev/sdb2 = / (ext4)

    > System Installation
    > Bootloader - UEFI_x86_64 > GRUB (2) UEFI
    > Asked me for a ESP, guided me to make type ef00 (EFI Partition) -> /dev/sdb1
    > GRUB installation successful
    > Configure username, password, root-password, etc…
    > Installation successful
    > Reboot

    And… the same error!

    [ *** ] A start job is running for dev-disk-by\ … …

  • Maybe the fstab is wrong, open it and change the UUID codes to /dev

    E.g.:
    UUID=7db28ed4-aa17-4ec0-9619-853e11510ecf
    to
    /dev/sda3

  • @“faidoc”:53kmeyge said:

    Maybe the fstab is wrong, open it and change the UUID codes to /dev

    E.g.:
    UUID=7db28ed4-aa17-4ec0-9619-853e11510ecf
    to
    /dev/sda3[/quote:53kmeyge]

    [b:53kmeyge]Thanks!!![/b:53kmeyge]

    I did something like that, but instead I changed at CLI Installer, I don’t remember exactly where, but in the way to install the system there is a option to choose in which way you want to organize the partitions (UUID, /dev or Kernel), and I choosed /dev.

    [b:53kmeyge]Working![/b:53kmeyge]

    One question: Are there any side effect if I use the system via /dev instead of UUID (my Linux installations were always using UUID to organize)?


    BOOT SUPER FAST!!!

    Now, I have a new opponent, Bluetooth. “bluez4” came pre-installed, but Cinnamon Bluetooth Manager won’t turn on, I click the switch but the “+” key to add a device (my BT mouse in this case), but it keeps grayed out.

    I tried:

    # pacman -Syyu
    # pacman -S dbus
    # bluetooth-wizard -> open a window but, don’t find anything.
    # bluez-test-device -> failed to load dbus-org.bluz.service
    # bluez-simple-agent -> failed to load dbus-org.bluz.service

    I read there - [https://wiki.archlinux.org/index.php/Bluetooth][0]">[https://wiki.archlinux.org/index.php/Bluetooth][1] - but nothing solves the problem… =D

    [b:53kmeyge]EDIT: WORKING![/b:53kmeyge]

    # systemctl start bluetooth.service
    # systemctl enable bluetooth.service


    Thanks all you guys, now is time to customize, install themes, fonts, tools, and make it mine!

    [0]: <a href=
    [1]: https://wiki.archlinux.org/index.php/Bluetooth

  • Glad to hear you were able to get this working! As far as using /dev vs UUID: UUID is assigned inside each partition and does not change where as /dev is relative to the order each partition is found. This means there is always a chance that what is usually your /dev/sda2 could show up as /dev/sda4 while using program “X”. As long as you label each partition, I really dont think you will have any issues with this!

Posts 18Views 7951
Log in to reply