• cannot boot after full system update


    I just pacman -Syu today and cant boot on next boot (wait what)
    I cant even use this console, my keyboard is not working there.
    ![0_1513948735071_IMG20171222201404.jpg](Uploading 100%)
    ![0_1513948847353_IMG20171222201404.jpg](Uploading 100%)
    (wtf, how did this forum handle attachment)
    external link to the screenshoot. https://pasteboard.co/GZojzYO.jpg

    what should I do?
    thank you

  • @Pegasusearl
    Maybe your update didn’t finish right and that broken the system. It is interesting that fstab is not finding your partition by UUID, did you remove your HDs and inserted again?

    Ok, for now you should boot Antergos liveimage and mount your partitions, follow one of those tutorials acording to your bios:

    Legacy BIOS
    https://antergos.com/wiki/miscellaneous/how-to-fix-grub-with-bios-boot/

    EFI BIOS
    https://antergos.com/wiki/miscellaneous/how-to-fix-grub-with-efi-boot/

    After mounting and chrooting you can updte your system again:
    sudo pacman -Syu

    Also type sudo blkid and check if the UUIDs matches the ones from /etc/fstab (or from /mnt/etc/fstab if you didn’t chroot), if not correct fstab.

    then unmount partitions and reboot to see if your system is working.

  • Yes, I think the update process is interupted in the middle of installing new software, I accidentaly close the wrong terminal. Which has no prompt.

    I booted to antergos live and follow the step in EFI BIOS. It said I should mount /, /boot,
    and /boot/efi. But as far as I remembered I didn’t use /boot when installing. I only use /boot/efi, so I skipped it
    it doesn’t work. I don’t know where did I go wrong
    Here is what happened:
    http://pasted.co/1e4e45ac/fullscreen.php?hash=ff82614c7cd6a758d52dd4a14706e96b&linenum=false

    everything in /mnt/etc/fstab is also correct, I think.

    # /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=8CAE-8E59 /boot/efi vfat defaults,relatime 0 0
    UUID=a83ad3b1-e433-4543-9057-91d6316c3492 / ext4 defaults,relatime,data=ordered 0 1
    UUID=72ce4fff-4aa3-4bce-9c27-b2a42b7fa9f3 /home ext4 defaults,relatime,data=ordered 0 0
    
    #output of blkid
    
    /dev/sda1: LABEL="Recovery" UUID="52A6ACB2A6AC984D" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="23d52bf2-e912-4d6a-b6dd-c4a553b1aca7"
    /dev/sda2: UUID="8CAE-8E59" TYPE="vfat" PARTLABEL="EFI system partition" PARTUUID="2912dc35-6af2-4cec-8d42-90dbb7d20ef0"
    /dev/sda3: PARTLABEL="Microsoft reserved partition" PARTUUID="76e0046c-0d32-4b31-baa4-c1a34dfb539a"
    /dev/sda4: LABEL="TEN CORE" UUID="3E38B40338B3B86B" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="160f60c1-d945-4b20-9428-604dd7b826f3"
    /dev/sda5: LABEL="VAULT" UUID="72ce4fff-4aa3-4bce-9c27-b2a42b7fa9f3" TYPE="ext4" PARTLABEL="Basic data partition" PARTUUID="41d39f89-67c4-4476-af82-21dbf7b84831"
    /dev/sda6: LABEL="WAREHOUSE" UUID="0CE4ADF7E4ADE366" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="fb700694-3b21-47d6-9a8e-6a4aa22d7d0a"
    /dev/sda7: LABEL="INTERCEPTOR" UUID="0c883b7b-ffe5-4dd6-aaa4-ba64a2c78c5e" TYPE="swap" PARTUUID="75f282f0-d129-4541-a458-738180430227"
    /dev/sda8: LABEL="NEXT" UUID="a83ad3b1-e433-4543-9057-91d6316c3492" TYPE="ext4" PARTLABEL="ARCHON" PARTUUID="80fb11c8-42b8-435c-8739-6accfba1b53e"
    /dev/sda9: LABEL="kosongan" UUID="fab2389c-656b-4737-9864-30b770f56d44" TYPE="ext4" PARTLABEL="SHARE" PARTUUID="ce270063-1427-4834-b0c3-0fb17b1c5f33"
    /dev/sdb1: LABEL="ANTERGOS" UUID="EC47-10E0" TYPE="vfat" PARTLABEL="Microsoft Basic Data" PARTUUID="f82d2cbe-872b-4bc6-824a-63c06f3bd164"
    /dev/loop0: TYPE="squashfs"
    

    I rebooted and it still not working. Same message.
    alt text

  • @Pegasusearl said in cannot boot after full system update:

    Yes, I think the update process is interupted in the middle of installing new software, I accidentaly close the wrong terminal. Which has no prompt.

    Ok, i guess that’s the problem then.

    I booted to antergos live and follow the step in EFI BIOS. It said I should mount /, /boot,
    and /boot/efi. But as far as I remembered I didn’t use /boot when installing. I only use /boot/efi, so I skipped it
    it doesn’t work. I don’t know where did I go wrong

    I don’t use EFI here, but i guess you should do just like the tutorial.
    So you couldn’t chroot and nor update the system?
    *I recommend you to repeat the steps from tutorial again.

    About your partitions everything seems fine, the weird thing is the complain about /new_root, but maybe updating the system will fix it.

  • So you couldn’t chroot and nor update the system?

    I can, as shown in there:

    [[email protected] antergos]# arch-chroot /mnt
    [[email protected] /]#
    
    [[email protected] /]# pacman -Syu
    :: Synchronizing package databases...
     antergos is up to date
     core is up to date
     extra                   1643.9 KiB  1134K/s 00:01 [######################] 100%
     community                  4.2 MiB  1462K/s 00:03 [######################] 100%
     multilib is up to date
     liri-unstable is up to date
    :: Starting full system upgrade...
    warning: liri-wallpapers-git: local (20170915.45f24d6-1) is newer than liri-unstable (20170915.30.45f24d6-1)
    warning: pepper-flash: local (1:26.0.0.137-1) is newer than extra (28.0.0.126-1)
    warning: python-xapp: local (1.0.1-2) is newer than antergos (1.0.1-1)
     there is nothing to do
    [[email protected] /]#
    

    =======

    /dev/sda1        2048     923647     921600  450M Windows recovery environment 
    **/dev/sda2      923648    1128447     204800  100M EFI System**
    /dev/sda3     1128448    1161215      32768   16M Microsoft reserved
    /dev/sda4     1161216  104859647  103698432 49.5G Microsoft basic data 
    /dev/sda5   352323584 1400899583 1048576000  500G Microsoft basic data (This is my /home)
    /dev/sda6  1400899584 1946159103  545259520  260G Microsoft basic data (This is my NTFS storage for windows)
    /dev/sda7  1946159104 1952018478    5859375  2.8G Linux filesystem (I think this is swap)
    **/dev/sda8   104859648  229078397  124218750 59.2G Linux filesystem**
    /dev/sda9   229079040  352323583  123244544 58.8G Linux filesystem (This is nothing)
    

    I don’t use EFI here, but i guess you should do just like the tutorial.

    my sda2 is my /mnt/boot/efi, and my sda8 is my /mnt
    Which one should I mount to /mnt/boot? Since it ask me to mount those 3 things and I only did two.

    This is what happened last time, I just gonna put it here.

    [[email protected] ~]$ sudo su
    [[email protected] antergos]# lsblk
    NAME   MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
    loop0    7:0    0   1.7G  1 loop /run/archiso/sfs/root-image
    sda      8:0    0 931.5G  0 disk 
    ├─sda1   8:1    0   450M  0 part 
    ├─sda2   8:2    0   100M  0 part 
    ├─sda3   8:3    0    16M  0 part 
    ├─sda4   8:4    0  49.5G  0 part 
    ├─sda5   8:5    0   500G  0 part 
    ├─sda6   8:6    0   260G  0 part 
    ├─sda7   8:7    0   2.8G  0 part 
    ├─sda8   8:8    0  59.2G  0 part 
    └─sda9   8:9    0  58.8G  0 part 
    sdb      8:16   1   3.8G  0 disk 
    └─sdb1   8:17   1   3.8G  0 part /run/archiso/bootmnt
    sr0     11:0    1  1024M  0 rom  
    [[email protected] antergos]# mount /dev/sda8 /mnt
    [[email protected] antergos]# mount /dev/sda2 /mnt/boot
    [[email protected] antergos]# umount /mnt/boot
    [[email protected] antergos]# mount /dev/sda2 /mnt/boot/efi
    [[email protected] antergos]# arch-chroot mnt
    ==> ERROR: Can't create chroot on non-directory mnt
    [[email protected] antergos]# arch-chroot /mnt
    [[email protected] /]# os-prober
      WARNING: Failed to connect to lvmetad. Falling back to device scanning.
    [[email protected] /]# grub-mkconfig -o /boot/grub/grub.cfg
    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.
    done
    [[email protected] /]# grub-install --target=x86_64-efi --efi-directory=/boot/efi --bootloader-id=Antergos-grub
    Installing for x86_64-efi platform.
    Installation finished. No error reported.
    [[email protected] /]# pacman -Syu
    :: Synchronizing package databases...
     antergos is up to date
     core is up to date
     extra                   1643.9 KiB  1134K/s 00:01 [######################] 100%
     community                  4.2 MiB  1462K/s 00:03 [######################] 100%
     multilib is up to date
     liri-unstable is up to date
    :: Starting full system upgrade...
    warning: liri-wallpapers-git: local (20170915.45f24d6-1) is newer than liri-unstable (20170915.30.45f24d6-1)
    warning: pepper-flash: local (1:26.0.0.137-1) is newer than extra (28.0.0.126-1)
    warning: python-xapp: local (1.0.1-2) is newer than antergos (1.0.1-1)
     there is nothing to do
    [[email protected] /]#
    
  • @Pegasusearl said in cannot boot after full system update:

    Which one should I mount to /mnt/boot? Since it ask me to mount those 3 things and I only did two.

    Ok then.

    Try to regenerate initramfs image with mkinitpio -P under chroot and then regenerate grub

  • Thank you sir! 😄
    It did said ‘failed to start kernel module’ when booting but it still worked well.
    So far doing my daily task had me no problem.

  • @Pegasusearl
    That’s good! I’m glad you fixed it! I was running out of ideas. hehehe
    :)

Posts 8Views 531
Bloom Email Optin Plugin

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