• Antergos Suddenly Not Booting

    Hey, so apologies for being back so quick. Ran into what is to me a rather serious issue, Antergos is failing to start on my laptop.
    The laptop is a Lenovo E460, it was all working fine then Spotify started to mess up (I suppose that’s what you get for using non-open sourced software :P) this has happened before so I just restarted. Now it’s failing to boot giving this message after the GRUB (The blue one with the logo and ‘Antergos’ on it) menu.

    Warning: /lib/modules/4.8.2-1-ARCH/modules.devname not found - ignoring
    started version 231
    ERROR: resume: hibernation device 'UUID=da90300c-0e8f-472f-a64a-6c8aa4b9be76' not found
    ERROR: device 'UUID=a8db176a-e9f8-4a10-ae0d-239b71e0db' not found. Skipping fsck.
    ERROR: Unable to find root device 'UUID=a8db176a-e9f8-4a10-ae0d-239b71e0db'.
    You are being dropped to a recovery shell
            Type 'exit' to try and continue loading
    sh: can't access tty; job control turned off
    [rootfs ]# _

    So this appears normally where it requests me to input the keypass for my LUKS partition. I’m super confused since I haven’t changed anything recently, all was working well until now.
    I’ve got backups of the super important documents but not all, just broke up for half-term today and was going to attempt backing everything up during it :( Looks like I’m too late…

    Any help appreciated, I’m just lucky this didn’t happen during school term…

    EDIT: I would love to give more detail into current versions but I can’t really seem to find any except the version 231 during the errors…

  • @Sirex Do you have a USB Stick with the Antergos Live-ISO / Installation Media on it? If yes, could you please boot it on your laptop and post your /etc/fstab and /etc/crypttab?

    Did you run an update before the reboot, e. g. installing the new kernel (4.8.1) or one of kernel modules for LUKS?
    And could you please outline your partition layout?

    EDIT 2:
    I forgot to ask for your kernel parameters.😲

  • Hello,

    I had something like that, and I think that this can be the solution for you:


    I do not know if this is the reason for the error, but you can give it a try.

  • Yesterday has faced the same problem. There was no time to look for the decision (all did not work, only with live cd) and consequently has reinstalled system. And someone waited a kernel 4.8 …

  • This post is deleted!
  • @liketechnik2000
    Hey, sorry for the late reply. Got the Live-ISO working now.
    My /etc/fstab looks like this

      GNU nano 2.7.0                                 File: /run/media/antergos/AntergosRoot/etc/fstab                                            
    # /etc/fstab: static file system information.
    # Use 'blkid' to print the universally unique identifier for a
    # device; this may be used with UUID= as a more robust way to name devices
    # that works even if disks are added and removed. See fstab(5).
    # <file system> <mount point>   <type>  <options>       <dump>  <pass>
    UUID=da90300c-0e8f-472f-a64a-6c8aa4b9be76 swap swap defaults 0 0
    UUID=c127a9ca-865d-4191-9cd6-0e5e90d5247e / ext4 defaults,rw,noatime,discard 0 1
    UUID=1a53fba3-c6c8-4599-8cbd-27de9c57628a /boot ext4 defaults,rw,noatime,discard 0 0

    Meanwhile my /etc/crypttab looks like this:

    # crypttab: mappings for encrypted partitions
    # Each mapped device will be created in /dev/mapper, so your /etc/fstab
    # should use the /dev/mapper/<name> paths for encrypted devices.
    # The Arch specific syntax has been deprecated, see crypttab(5) for the
    # new supported syntax.
    # NOTE: Do not list your root (/) partition here, it must be set up
    #       beforehand by the initramfs (/etc/mkinitcpio.conf).
    # <name>       <device>                                     <password>              <options>
    # home         UUID=b8ad5c18-f445-495d-9095-c9ec4f9d2f37    /etc/mypassword1
    # data1        /dev/sda3                                    /etc/mypassword2
    # data2        /dev/sda5                                    /etc/cryptfs.key
    # swap         /dev/sdx4                                    /dev/urandom            swap,cipher=aes-cbc-essiv:sha256,size=256
    # vol          /dev/sdb7                                    none

    I did indeed update before the reboot. Can’t remember exactly what the updates are, the contents of my /var/log/pacman.log is:

    [2016-10-21 20:43] [PAMAC] synchronizing package lists
    [2016-10-21 20:43] [PAMAC] synchronizing package lists
    [2016-10-21 20:44] [PAMAC] synchronizing package lists
    [2016-10-21 20:47] [ALPM] transaction started
    [2016-10-21 20:47] [ALPM] upgraded tzdata (2016g-1 -> 2016h-1)
    [2016-10-21 20:47] [ALPM] upgraded geoip-database (20160907-1 -> 20161004-1)
    [2016-10-21 20:47] [ALPM] upgraded bind-tools (9.11.0-1 -> 9.11.0-2)
    [2016-10-21 20:47] [ALPM] upgraded btrfs-progs (4.7.3-1 -> 4.8.1-1)
    [2016-10-21 20:47] [ALPM] upgraded ca-certificates-mozilla (3.26-1 -> 3.27.1-1)
    [2016-10-21 20:47] [ALPM] upgraded dbus (1.10.10-3 -> 1.10.12-1)
    [2016-10-21 20:47] [ALPM] upgraded jack (0.124.1-6 -> 0.125.0-1)
    [2016-10-21 20:47] [ALPM] upgraded netcdf (4.4.1rc1-1 -> 4.4.1-2)
    [2016-10-21 20:47] [ALPM] upgraded libpng (1.6.25-1 -> 1.6.26-2)
    [2016-10-21 20:47] [ALPM] upgraded libxi (1.7.7-1 -> 1.7.7-2)
    [2016-10-21 20:47] [ALPM] upgraded ffmpeg (1:3.1.4-2 -> 1:3.1.4-3)
    [2016-10-21 20:47] [ALPM] upgraded nspr (4.12-1 -> 4.13-1)
    [2016-10-21 20:47] [ALPM] upgraded nss (3.26-1 -> 3.27.1-1)
    [2016-10-21 20:47] [ALPM] upgraded jasper (1.900.2-1 -> 1.900.5-1)
    [2016-10-21 20:47] [ALPM] upgraded firefox (49.0.1-1 -> 49.0.2-1)
    [2016-10-21 20:47] [ALPM] upgraded ghostscript (9.20-2 -> 9.20-4)
    [2016-10-21 20:47] [ALPM] upgraded git (2.10.0-1 -> 2.10.1-1)
    [2016-10-21 20:47] [ALPM] upgraded gobject-introspection-runtime (1.50.0+1+gb8d92b0-1 -> 1.50.0+1+gb8d92b0-2)
    [2016-10-21 20:47] [ALPM] upgraded grep (2.25-2 -> 2.26-1)
    [2016-10-21 20:47] [ALPM] upgraded grub (1:2.02.beta3-3 -> 1:2.02.beta3-4)
    [2016-10-21 20:47] [ALPM] upgraded lib32-glib2 (2.48.1-1 -> 2.50.1-1)
    [2016-10-21 20:47] [ALPM] upgraded lib32-libjpeg-turbo (1.5.0-1 -> 1.5.1-1)
    [2016-10-21 20:47] [ALPM] upgraded lib32-libpng (1.6.24-1 -> 1.6.26-1)
    [2016-10-21 20:47] [ALPM] upgraded libtracker-sparql (1.10.1-1 -> 1.10.1+3+g0e839d0-1)

    These were the updates from yesterday, the 21st, just before the fatal reboot.

    I’m not really sure what you mean by “outline your partition layout” so here’s all my partitions for the drive. The information was taken from the Drive utility.

    Size: 267 MB — 205 MB free (23.2% full)
    Device: /dev/sda1
    Partition Type: Linux (Bootable)
    Contents: Ext4 (version 1.0)

    Size: 492 GB (492,018,073,600 bytes)
    Device: /dev/sda2
    Partition Type: Linux
    Contents: LUKS Encryption (version 1) — Unlocked

    Size: 492 GB — 427 GB free (13.2% full)
    Device: /dev/mapper/luks-c127a9ca-865d-4191-9cd6-0e5e90d5247e
    Contents: Ext4 (version 1.0) — Mounted at /run/media/antergos/AntergosRoot

    Extended Partition
    Size: 7.8 GB (7,821,352,960 bytes)
    Device: /dev/sda3
    Partition Type: W95 Ext d (LBA)
    Contents: Extended Partition

    Size: 7.8 GB (7,820,304,384 bytes)
    Device: /dev/sda5
    Partition Type: Linux Swap
    Contents: Swap (version 1) — Not Active

    As for the kernel parameters, the correct command is $ cat /proc/cmdline right? :S
    The output for the command is:

    vga=0x37e video=1920x1080  lang=en_US keytable=us layout=us initrd=/arch/boot/intel_ucode.img,/arch/boot/archiso.img archisobasedir=arch archisolabel=ANTERGOS earlymodules=loop modules-load=loop rd.modules-load=loop udev.log-priority=crit rd.udev.log-priority=crit quiet splash

    Thank you so very, very much for your help so far! :)

  • @Sirex First, I’m no expert at encryption with LUKS, but I hope I’ll be able to help you, but any help from someone who really is an expert of LUKS would be appreciated.

    So now let’s take care of your partition layout and the kernel parameters:

    • Could you please run lsblk -laf from your live system and post the output here (Sorry for not being more clear with the outline of your partition layout).
    • Do you have your root partition on an encrypted file system?
    • Which file systems do you use? (and on which partition?)
    • Kernel parameters: The command you were using outputs the kernel parameters of the booted system, that’s right. But the point of interest are the kernel parameters of your system that is broken at the moment. Usually they can be found in /etc/default/grub.

    But your /etc/fstab and your /etc/crypttab confuse me a bit:

    • Your crypttab is completely commented out, which seems strange.
    • You use only UUID’s in your fstab, but the only way to mount an encrypted partition I know is via /dev/mapper/name entrys in fstab, so did you create your encrypted partition manually or with the installer and did you change something manually later?

    P.S.: Sorry for my late reply, I’m don’t know LUKS well, as I mentioned above. But I can remmoned you to read the articles in ArchWiki concerning encryption:

  • you should check if the uuid of the partitions you want to boot from is matching the ones in


    and in your


    you can check it by running

    blkid /dev/sdXX
  • Yep, this error got me too on my Openbox setup but it was version 4.8.4-1. It happened in the middle of an update, my screen went black and when I rebooted I got that same message. I have Antergos on a separate partition along with several other Linux OS’s. Is there a way to modify a file or do I need a cd/stick to get it going again?

booting55 suddenly7 failing to boot2 Posts 9Views 3509
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.