• Installation failed


    The installation went without problem, but I noticed that at the end the installation the bootloader took about 15 minutes to complate.

    After reboot I get error massages like:

    error no such device: UUID …

    error no such partition

    You need to load the kernel first

    But the biggest problem is that the bootloader folders and files and kernel images duplicated on the efi partition filling up my efi partion so other distros like Manjaro complaining that the efi partition is full free up space.

    In other places they told me that: “A standard grubx64.efi from debian, gentoo, arch, LFS, efc., is only about 120K. A custom grubx64.efi from Fedora/CentOS and Ubuntu is about 1M. As you can see, Linux does not take up much space on the EFI. You can easily install about two dozen Linuxes on a 100MiB EFI.”

    Look at my harddrive layout and some of the relevant info:

    [[email protected] ~]$ sudo fdisk -l
    [sudo] password for mak: 
    Disk /dev/sda: 238.5 GiB, 256060514304 bytes, 500118192 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
    Disklabel type: gpt
    Disk identifier: 2F26A21D-D414-4F41-5F52-2B9C892CF72D
    
    Device         Start       End   Sectors  Size Type
    /dev/sda1       2048    923647    921600  450M Windows recovery environment
    /dev/sda2     925696   1130495    204800  100M EFI System
    /dev/sda3    1130496   1163263     32768   16M Microsoft reserved
    /dev/sda4    1163264 126838783 125675520 59.9G Microsoft basic data
    /dev/sda5  126838784 168781823  41943040   20G Linux filesystem
    /dev/sda6  168781824 210724863  41943040   20G Linux filesystem
    /dev/sda7  210724864 252667903  41943040   20G Linux filesystem
    /dev/sda8  252667904 294610943  41943040   20G Linux filesystem
    /dev/sda9  294610944 336553983  41943040   20G Linux filesystem
    /dev/sda10 336553984 344942591   8388608    4G Linux swap
    /dev/sda11 344942592 500118158 155175567   74G Linux filesystem
    

    The efi partion:

    [[email protected] ~]$ ls /boot/efi
    EFI  grub  initramfs-linux-fallback.img  initramfs-linux.img  vmlinuz-linux
    
    

    The boot directory:

    [[email protected] efi]$ ls /run/media/mak/41d3f9f1-4e62-4089-9520-d4a61e89d72c/boot
    efi  grub  initramfs-linux-fallback.img  initramfs-linux.img  intel-ucode.img  vmlinuz-linux
    [[email protected] efi]$ 
    
    

    The efi partition:

    [[email protected] efi]$ du -h .
    153K	./EFI/Microsoft/Boot/bg-BG
    196K	./EFI/Microsoft/Boot/cs-CZ
    194K	./EFI/Microsoft/Boot/da-DK
    202K	./EFI/Microsoft/Boot/de-DE
    205K	./EFI/Microsoft/Boot/el-GR
    147K	./EFI/Microsoft/Boot/en-GB
    191K	./EFI/Microsoft/Boot/en-US
    198K	./EFI/Microsoft/Boot/es-ES
    153K	./EFI/Microsoft/Boot/es-MX
    149K	./EFI/Microsoft/Boot/et-EE
    196K	./EFI/Microsoft/Boot/fi-FI
    157K	./EFI/Microsoft/Boot/fr-CA
    202K	./EFI/Microsoft/Boot/fr-FR
    151K	./EFI/Microsoft/Boot/hr-HR
    200K	./EFI/Microsoft/Boot/hu-HU
    198K	./EFI/Microsoft/Boot/it-IT
    175K	./EFI/Microsoft/Boot/ja-JP
    175K	./EFI/Microsoft/Boot/ko-KR
    149K	./EFI/Microsoft/Boot/lt-LT
    149K	./EFI/Microsoft/Boot/lv-LV
    194K	./EFI/Microsoft/Boot/nb-NO
    200K	./EFI/Microsoft/Boot/nl-NL
    198K	./EFI/Microsoft/Boot/pl-PL
    196K	./EFI/Microsoft/Boot/pt-BR
    196K	./EFI/Microsoft/Boot/pt-PT
    54K	./EFI/Microsoft/Boot/qps-ploc
    151K	./EFI/Microsoft/Boot/ro-RO
    197K	./EFI/Microsoft/Boot/ru-RU
    153K	./EFI/Microsoft/Boot/sk-SK
    151K	./EFI/Microsoft/Boot/sl-SI
    46K	./EFI/Microsoft/Boot/sr-Latn-CS
    153K	./EFI/Microsoft/Boot/sr-Latn-RS
    195K	./EFI/Microsoft/Boot/sv-SE
    194K	./EFI/Microsoft/Boot/tr-TR
    153K	./EFI/Microsoft/Boot/uk-UA
    169K	./EFI/Microsoft/Boot/zh-CN
    169K	./EFI/Microsoft/Boot/zh-HK
    169K	./EFI/Microsoft/Boot/zh-TW
    13M	./EFI/Microsoft/Boot/Fonts
    5.0K	./EFI/Microsoft/Boot/Resources/en-US
    33K	./EFI/Microsoft/Boot/Resources
    24M	./EFI/Microsoft/Boot
    41K	./EFI/Microsoft/Recovery
    24M	./EFI/Microsoft
    1.3M	./EFI/Boot
    4.0K	./EFI/Dell/logs
    12M	./EFI/Dell/Bios/Recovery
    12M	./EFI/Dell/Bios
    12M	./EFI/Dell
    121K	./EFI/Manjaro
    121K	./EFI/antergos_grub
    121K	./EFI/antergos_grub_vl0n
    121K	./EFI/ArchLabs
    37M	./EFI
    1.0K	./grub
    70M	.
    
  • @jmak said in Installation failed:

    The efi partion:
    [[email protected] ~]$ ls /boot/efi
    EFI grub initramfs-linux-fallback.img initramfs-linux.img vmlinuz-linux

    grub initramfs-linux-fallback.img initramfs-linux.img vmlinuz-linux
    this looks screwed up to me as it is doubled and on wrong place…
    As i remember at the moment normal way is to mount EFI-Partittion under /boot/efi/ and inside efi folder you will find only EFI not grub-folder and images…

    [updates once a week] = [90% less problems]
    [Li{u}n//u//{i}x] since 1988 - overcoming failure means success
    http://kamprad.net/howto-installing-antergos/
    how to add system logs

  • That’s what I think too.
    But this is not the first time this happened to me.

  • I deleted all the grub directories and image files from the efi partition.

    I chrooted into the installation and issued: grub-mkconfig -o /boot/grub/grub.cfg

    and I got an error message:

    EDIT:
    I was told that “os-prober” has a hard time to handle more complex partitions. When the system has one or two partitions it works fine, but otherwise it gets confused

    I don’t know this is true or not.

    /usr/bin/grub-mkconfig: line 237: /boot/grub/grub.cfg.new: No such file or directory```
  • The trick against os-prober issue is to mount all harddisks, before.
    I would reinstall grub to see if this solves your “No such file or directory” error…

    [updates once a week] = [90% less problems]
    [Li{u}n//u//{i}x] since 1988 - overcoming failure means success
    http://kamprad.net/howto-installing-antergos/
    how to add system logs

  • Thanks for the os-prober tip.

    I tried to reinstall grub, but I got an error message:

    grub-install: error: cannot find EFI directory
    

    even if the EFI directory was mounted

    Some time ago I installed Manjaro Gnome. After on a separate partition I installed Manjaro LXQT. When I rebooted I noticed that only one Manjaro was listed on the efi partition. The Gnome entry was overwritten. I asked the Manjaro people about this and they told me that only one Manjaro entry can exist on the efi partition, so if I install another one on a separate partition the existing one will always be overwritten by the latest. I can launch the new Manjaro from the grub menu, but not from the firmware launcher.

    I already have a functioning antergos installed on my system.

    [[email protected] ~]$ ls /boot/efi/EFI
    antergos_grub  antergos_grub_vl0n  ArchLabs  Boot  Dell  Manjaro  Microsoft
    [[email protected] ~]$ 
    
    

    When I installed that one it was properly done. But when I installed the second one I get this grub problems.

    Do you think, what the Manjaro people said, has something to do with the antergos installation as well?

  • @jmak said in Installation failed:

    That’s what I think too.
    But this is not the first time this happened to me.

    Do you mind if i ask you how did you fix last time?

    Antergos (default OS) - WIN10 (abandoned)
    I3wm - Mate desktop
    AMD - A4 7300 Radeon graphics
    16 GB ram
    HD 1 TB
    Linux newbie since 06/2016

  • I didn’t fix it because nobody who I asked had any idea. I just removed it.

    If you can’t have more than one flavor of the same distro on the same harddrive that is a major limitation of the efi system in my view.

    EDIT:

    I just downloaded debian and I will install it to see how that one will handle the efi system.
    This is a new dell laptop, I just got it 3 weeks ago, and debian was never installed on it.

    Before, I had a legacy pc with 1TB harddrive and 16 partition on it - all Linux. Sometimes I installed 3-4 flavors of the same disto -on different partitions- but grub always worked properly.

  • EFI/UEFI is “new”, and is not made for Linux so we as alternative OS enthusiasts need to hack it first completely…

    As far as i understand Grub is not the perfect boot code to boot out of a EFI-“Bios” , also the way we need to do this looks a bit “hackish” to me.

    jmak say

    If you can’t have more than one flavor of the same distro on the same harddrive that is a major limitation of the efi system in my view.

    I think that there are some issueswith Grub and more then 2 OS installed at the moment, maybe related to os-prober (what is origin from Debian A:F:A:I:K).
    And it is a long time that there is no solution for an exact recognition of disks inside Grub, there are to much different device naming code-systems aviable, and Grub itself uses another one extra too…:confused:

    But it should be possible to get more then 2 OS booted up with EFi > Grub!

    [updates once a week] = [90% less problems]
    [Li{u}n//u//{i}x] since 1988 - overcoming failure means success
    http://kamprad.net/howto-installing-antergos/
    how to add system logs

  • Hello all,

    I made an experiment by installing debian on two partitions to see what happens. Debian follows the same strategy like Manjaro. I doesn’t create another boot directory for the second flavor on the efi partition, like for instance debian, debian_2 but overwrites the debian directory with the new bootloader.

    So most probably that grub and the image files were installed in my case on the efi partition due to grub confusion as antergos create different boot dirictory for each flavor.

    EDIT:
    I wonder how the original Arch will react as Manjaro and Antergos are also Arch derivatives. It may be that Arch grub will get problems by confusing Manjaro and Antergos as arch installs.

  • @joekamprad said in Installation failed:

    EFI/UEFI is “new”, and is not made for Linux so we as alternative OS enthusiasts need to hack it first completely…

    As far as i understand Grub is not the perfect boot code to boot out of a EFI-“Bios” , also the way we need to do this looks a bit “hackish” to me.

    jmak say

    If you can’t have more than one flavor of the same distro on the same harddrive that is a major limitation of the efi system in my view.

    I think that there are some issueswith Grub and more then 2 OS installed at the moment, maybe related to os-prober (what is origin from Debian A:F:A:I:K).
    And it is a long time that there is no solution for an exact recognition of disks inside Grub, there are to much different device naming code-systems aviable, and Grub itself uses another one extra too…:confused:

    But it should be possible to get more then 2 OS booted up with EFi > Grub!

    Hi joekamprad,

    As far as my limited understanding of the topic tells me, in the case of Antergos the only way to install two antergos flavors is to tell somehow to the installer not to create a second boot directory on the efi partition but overwrite the existing one.

    Then, you boot in the first distro - number 1 in efibootmgr - make a grub update, which detects the new install and launch it from the grub menu.

    But you won’t be able to launch it from the firmware because it won’t have an efi boot entry.

Posts 11Views 358
Log in to reply