• Can't boot after fresh install


    Hello everyone. This is my first experience with Antergos, but I have used other linux distros before. I downloaded the latest 19.1 installer to a USB stick using dd. During installation, the default choice of Live USB doesn’t work, it says:

    Failed to execute Antergos Live System (usb) (\EFI\archiso\vmlinuz): Not Found
    

    So I tried the CD/DVD boot option and that worked. Does anyone know why I have to choose this option when I’m booting from a USB stick?
    Anyway Cnchi said I’m all up to date, and the install failed twice with an error like this, but referencing a different package each time:

    Error creating metalink for package pamac. Installation will stop': add_fatal in /usr/share/cnchi/src/misc/events.py:83
    

    On the third try (using the same options) the install completed without error, although it hung for a long time on the line about installing grub2. I was watching cnchi.log with tail. Now when I try to boot the system it shows:

    ERROR: resume: hibernation device 'UUID=xxxxxxxx' not found
    ERROR: device 'UUID=yyyyyyyyyy' not found
    mount: /new_root: can't find UUID=yyyyyyyy
    

    It says it dropped me into an emergency shell, but the keyboard doesn’t work, so I am unable to collect any log file.
    I tried booting to the USB installer again so I could find the log file, but it gives a new error this time shown here.antergos.jpeg
    How should I troubleshoot this? I installed to a SATA SSD. The machine also has an M.2 NVME drive which is running Windows, but that one is set to a lower boot priority in the BIOS.

  • The USB problem is a bug and happens on some UEFI systems - it’s being looked at.
    The long wait at the end can happen for a number of reasons but it seems that you’ve been unlucky enough to get the latest systemd 240 bug which may be linked:

    https://bugs.archlinux.org/task/61324

    So, for now, get the downgrade package:

    sudo pacman -S downgrade
    

    and downgrade systemd to 239 (ie whichever is top of the list):

    sudo downgrade systemd
    

    But you say keyboard doesn’t work? Can’t switch to a tty?

  • @robgriff444 thanks for the advice. Indeed it sounds like that bug, but I don’t know how to make the keyboard work. I’ve now installed on a second machine and it has the same issue, see the error message here. This machine uses Legacy boot instead of UEFI, and it has only one SSD installed for simplicity.

    tty.jpeg

  • 2019-01-11-162228_1320x65_scrot.png

    $ fsck -a

    and leave immediately with the letter n

    <n> n

    https://wiki.archlinux.org/index.php/fsck#Tips_and_tricks

  • @judd I’m unable to type anything on the keyboard. See the last line, it says can’t access tty. I tried Ctrl-Alt-F1 and F2 like in CentOS, but that doesn’t do anything here.

  • @llamafilm Not sure about the keyboard, I’ve said the same solution to someone else and it worked so his kbd was fine. Maybe try re-install and switch to a console window before reboot and do the systemd downgrade then before a reboot?

  • @llamafilm
    Arch bugtracker: udev 240 not recognising keyboard
    https://bugs.archlinux.org/task/61328
    Same cause ie systemd 240, downgrading to 239 solved it, wow systemd kills you twice with 2 serious bugs lol

  • I reinstalled so I could save the log file. Here is the section about grub, is this error something I should worry about?

    2019-01-11 18:19:30 [INFO   ] Installing bootloader...  (slides.py:240)
    2019-01-11 18:19:30 [DEBUG  ] Set GRUB_THEME="/boot/grub/themes/Antergos-Default/theme.txt" in /etc/default/grub  (grub2.py:222)
    2019-01-11 18:19:30 [DEBUG  ] Set GRUB_DISTRIBUTOR="Antergos" in /etc/default/grub  (grub2.py:222)
    2019-01-11 18:19:30 [DEBUG  ] Set GRUB_CMDLINE_LINUX_DEFAULT="quiet resume=UUID=05eecc66-a517-469e-add8-81a62f96b8f7" in /etc/default/grub  (grub2.py:222)
    2019-01-11 18:19:30 [DEBUG  ] Set GRUB_CMDLINE_LINUX="" in /etc/default/grub  (grub2.py:222)
    2019-01-11 18:19:30 [DEBUG  ] Grub configuration completed successfully.  (grub2.py:196)
    2019-01-11 18:19:30 [DEBUG  ] Cnchi will install the Grub2 (bios) loader  (grub2.py:74)
    2019-01-11 18:19:30 [INFO   ] Installing GRUB(2) BIOS boot loader in /dev/sdb  (grub2.py:296)
    2019-01-11 18:19:30 [DEBUG  ] Special dirs are already mounted. Skipping.  (special_dirs.py:76)
    2019-01-11 18:19:31 [DEBUG  ] Installing for i386-pc platform.
    Installation finished. No error reported.  (run_cmd.py:149)
    2019-01-11 18:19:31 [DEBUG  ] Installing Grub2 locales.  (grub2.py:442)
    2019-01-11 18:19:31 [DEBUG  ] Generating grub.cfg...  (grub2.py:270)
    2019-01-11 18:19:31 [DEBUG  ] Special dirs are already mounted. Skipping.  (special_dirs.py:76)
    2019-01-11 18:19:31 [DEBUG  ] 50mounted-tests file patched successfully  (grub2.py:436)
    2019-01-11 18:19:31 [DEBUG  ] Running grub-mkconfig...  (grub2.py:280)
    2019-01-11 18:19:41 [WARNING] Error running ['/bin/pidof', 'grub-mount']: b''  (grub2.py:265)
    2019-01-11 18:22:28 [DEBUG  ] Generating grub configuration file ...
    Found theme: /boot/grub/themes/Antergos-Default/theme.txt
    Found Intel Microcode image
    Found linux image: /boot/vmlinuz-linux
    Found initrd image: /boot/initramfs-linux.img
    Found fallback initramfs image: /boot/initramfs-linux-fallback.img
      WARNING: Failed to connect to lvmetad. Falling back to device scanning.
      WARNING: Device /dev/loop0 not initialized in udev database even after waiting 10000000 microseconds.
      WARNING: Device /dev/sda not initialized in udev database even after waiting 10000000 microseconds.
      WARNING: Device /dev/sda1 not initialized in udev database even after waiting 10000000 microseconds.
      WARNING: Device /dev/sdb not initialized in udev database even after waiting 10000000 microseconds.
      WARNING: Device /dev/sdb1 not initialized in udev database even after waiting 10000000 microseconds.
      WARNING: Device /dev/sdb2 not initialized in udev database even after waiting 10000000 microseconds.
      /dev/sdb3: open failed: No such device or address
      WARNING: Device /dev/sdb5 not initialized in udev database even after waiting 10000000 microseconds.
      WARNING: Device /dev/sdc not initialized in udev database even after waiting 10000000 microseconds.
      WARNING: Device /dev/sdc1 not initialized in udev database even after waiting 10000000 microseconds.
      WARNING: Device /dev/sdc2 not initialized in udev database even after waiting 10000000 microseconds.
      WARNING: Device /dev/loop0 not initialized in udev database even after waiting 10000000 microseconds.
      WARNING: Device /dev/sda1 not initialized in udev database even after waiting 10000000 microseconds.
      WARNING: Device /dev/sdb1 not initialized in udev database even after waiting 10000000 microseconds.
      WARNING: Device /dev/sdb2 not initialized in udev database even after waiting 10000000 microseconds.
      WARNING: Device /dev/sdb5 not initialized in udev database even after waiting 10000000 microseconds.
      WARNING: Device /dev/sdc1 not initialized in udev database even after waiting 10000000 microseconds.
      WARNING: Device /dev/sdc2 not initialized in udev database even after waiting 10000000 microseconds.
    grub-probe: error: cannot find a GRUB drive for /dev/sdc1.  Check your device.map.
    done  (run_cmd.py:149)
    2019-01-11 18:22:28 [INFO   ] GRUB(2) BIOS has been successfully installed.  (grub2.py:325)
    

    @robgriff444 I wouldn’t expect downgrade to work within the live environment, but I tried it anyway and it failed. Output: https://pastebin.com/GW605Wby

  • Fair enough, so … you can boot from usb, chroot into your install and do the downgrade. Also, the OP on the bugtracker said an external keyboard worked (not sure if you’re on a laptop or not).
    To chroot, boot from USB and mount root (and efi and boot if you want):
    XX is your device numbers - easy to get them from gparted

    sudo mount /dev/sdXX /mnt 
    sudo mount /dev/sdXX /mnt/boot  
    sudo mount /dev/sdXX /mnt/boot/efi
    sudo arch-chroot
    

    Then run pacman and downgrade stuff, and type exit when done.
    Also, I think the pidof error might be gone when systemd has been resolved.

  • @judd Based on that link, I tried adding “single” to the end of kernel parameters, but that doesn’t change anything.

    @robgriff444 After mounting both /boot and /root, in chroot I was able to downgrade systemd. I did get an error near the end about creating temporary files, but I am finally able to boot the system. Thank you!

  • @llamafilm Thank goodness! Let’s sell systemd to MS and see what else we can find on ebay lol

    And keep an eye on the bugtracker (as I will) and keep systemd at 239 until a fix is out, my guess is 3 days 🤔

  • Dear Sir,

    I had problem as Mr @llamafilm .
    I’ve tried to downgrade systemd from archlinux archive with last systemd 239 version. but still on failed boot.

    ==> Creating gzip-compressed initcpio image: /boot/initramfs-linux-fallback.img
    ==> Image generation successful  (run_cmd.py:149)
    2019-01-18 07:29:10 [DEBUG  ] File user-dirs-update-gtk.desktop patched.  (post_install.py:784)
    2019-01-18 07:29:10 [DEBUG  ] LightDM display manager configuration completed.  (post_install.py:287)
    2019-01-18 07:29:10 [INFO   ] Configuring LightDM desktop manager...  (slides.py:240)
    2019-01-18 07:29:10 [INFO   ] Installing bootloader...  (slides.py:240)
    2019-01-18 07:29:10 [DEBUG  ] Set GRUB_THEME="/boot/grub/themes/Antergos-Default/theme.txt" in /etc/default/grub  (grub2.py:222)
    2019-01-18 07:29:10 [DEBUG  ] Set GRUB_DISTRIBUTOR="Antergos" in /etc/default/grub  (grub2.py:222)
    2019-01-18 07:29:10 [DEBUG  ] Set GRUB_CMDLINE_LINUX_DEFAULT="quiet" in /etc/default/grub  (grub2.py:222)
    2019-01-18 07:29:10 [DEBUG  ] Set GRUB_CMDLINE_LINUX="" in /etc/default/grub  (grub2.py:222)
    2019-01-18 07:29:10 [DEBUG  ] Grub configuration completed successfully.  (grub2.py:196)
    2019-01-18 07:29:10 [DEBUG  ] Cnchi will install the Grub2 (bios) loader  (grub2.py:74)
    2019-01-18 07:29:10 [INFO   ] Installing GRUB(2) BIOS boot loader in /dev/sda  (grub2.py:296)
    2019-01-18 07:29:10 [DEBUG  ] Special dirs are already mounted. Skipping.  (special_dirs.py:76)
    2019-01-18 07:29:26 [DEBUG  ] Installing for i386-pc platform.
    grub-install: warning: this GPT partition label contains no BIOS Boot Partition; embedding won't be possible.
    grub-install: warning: Embedding is not possible.  GRUB can only be installed in this setup by using blocklists.  However, blocklists are UNRELIABLE and their use is discouraged..
    grub-install: error: will not proceed with blocklists.  (run_cmd.py:149)
    2019-01-18 07:29:26 [DEBUG  ] Installing Grub2 locales.  (grub2.py:442)
    2019-01-18 07:29:26 [DEBUG  ] Generating grub.cfg...  (grub2.py:270)
    2019-01-18 07:29:26 [DEBUG  ] Special dirs are already mounted. Skipping.  (special_dirs.py:76)
    2019-01-18 07:29:26 [DEBUG  ] 50mounted-tests file patched successfully  (grub2.py:436)
    2019-01-18 07:29:26 [DEBUG  ] Running grub-mkconfig...  (grub2.py:280)
    2019-01-18 07:29:36 [WARNING] Error running ['/bin/pidof', 'grub-mount']: b''  (grub2.py:265)
    2019-01-18 07:32:30 [DEBUG  ] Generating grub configuration file ...
    Found theme: /boot/grub/themes/Antergos-Default/theme.txt
    Found Intel Microcode image
    Found linux image: /boot/vmlinuz-linux
    Found initrd image: /boot/initramfs-linux.img
    Found fallback initramfs image: /boot/initramfs-linux-fallback.img
    Found fallback initramfs image: /boot/initramfs-linux-fallback.img
      WARNING: Failed to connect to lvmetad. Falling back to device scanning.
      WARNING: Device /dev/loop0 not initialized in udev database even after waiting 10000000 microseconds.
      WARNING: Device /dev/sda not initialized in udev database even after waiting 10000000 microseconds.
      WARNING: Device /dev/sda1 not initialized in udev database even after waiting 10000000 microseconds.
      WARNING: Device /dev/sda2 not initialized in udev database even after waiting 10000000 microseconds.
      WARNING: Device /dev/sda3 not initialized in udev database even after waiting 10000000 microseconds.
      WARNING: Device /dev/sda4 not initialized in udev database even after waiting 10000000 microseconds.
      WARNING: Device /dev/sdb not initialized in udev database even after waiting 10000000 microseconds.
      WARNING: Device /dev/sdb1 not initialized in udev database even after waiting 10000000 microseconds.
      WARNING: Device /dev/sdb2 not initialized in udev database even after waiting 10000000 microseconds.
      WARNING: Device /dev/loop0 not initialized in udev database even after waiting 10000000 microseconds.
      WARNING: Device /dev/sda1 not initialized in udev database even after waiting 10000000 microseconds.
      WARNING: Device /dev/sda2 not initialized in udev database even after waiting 10000000 microseconds.
      WARNING: Device /dev/sda3 not initialized in udev database even after waiting 10000000 microseconds.
      WARNING: Device /dev/sda4 not initialized in udev database even after waiting 10000000 microseconds.
      WARNING: Device /dev/sdb1 not initialized in udev database even after waiting 10000000 microseconds.
      WARNING: Device /dev/sdb2 not initialized in udev database even after waiting 10000000 microseconds.
    grub-probe: error: cannot find a GRUB drive for /dev/sdb1.  Check your device.map.
    done  (run_cmd.py:149)
    2019-01-18 07:32:30 [INFO   ] GRUB(2) BIOS has been successfully installed.  (grub2.py:325)
    

    while I check on /dev/sda1 (as /boot/efi mount endpoint), it shown nothing.
    may i know i must todo ?
    note : while tried to downgrade systemd, it shown many error and still doesn’t boot properly.
    Thank you a lot

    regards,

    qlixes

boot310 fresh41 Posts 14Views 854
Log in to reply
Bloom Email Optin Plugin

Looks like your connection to Antergos Community Forum was lost, please wait while we try to reconnect.