• Boot up error


    I had a healthy Antergos XFCE installation using BTRFS and I decided to shrink the existing partition down and create another BTRFS partition and install Arch on it, using the same swap partition (not specifying an EFI partition). Unfortunately it did not go well and Arch was installed but not bootable (appeared in grub2 menu) and henceforth I get an error when booting up Antergos XFCE. After the ‘Starting version 239’ text, instead of lightdm starting up the login screen, I get a text error ‘Error - Resume: hibernation device UUID…no.’ then on the next line ‘A start job is running’ then it counts up to 90 seconds before I get the login screen starting up and I can log in and XFCE starts up as normal. I have updated the grub config file which didn’t really help with the above although I get no errors when shutting down now. Solutions? TIA.

    BTW I checked the UUID of the main partition in /etc/ftstab and it was the same as the UUID I for that partition in Gparted.

  • I think the problem is caused by a change in the drive path after I shrunk the original Antergos partition, added a new partition, and installed Arch, even if the UUIDs remained the same. I have two NVMe drives and their paths have swapped. Disk 0 is now disk 1, and disk 1 is now disk 0. Is this is the problem, how does one go about fixing it please? Cheers.

    Update: Perhaps this was a red herring. After a number of reboots the path IDs went back to how they were before with still the same error during boot up.

  • @Pl1SsK
    You could use LABELs instead of UUIDs in /etc/fstab, something like

    LABEL=Name / btrfs defaults
    

    where you choose the “Name” for the root partition. But use the existing syntax of your /etc/fstab, don’t change anything else than UUID=… part of that line.

    Also, you probably need to give command

    sudo grub-mkconfig -o /boot/grub/grub.cfg
    

    And machine’s BIOS/Firmware settings should give you a way to change which disk to boot.

  • @manuel Hi, thanks for the input. I tried this just now, and I still had the same fault, albeit it was slightly different because the UUID specified in the error message was no longer that for the root partition but another UUID which I didn’t recognise, which didn’t pertain to any of the Linux partitions (EFI, Swap or Root).

  • @Pl1SsK
    Could you show the output of commands

    lsblk -fm
    sudo fdisk -l
    cat /etc/fstab
    
  • @manuel Here are the outputs. I changed the fstab back to what it was. Basically I have a 250GB Samsung 960 Evo NVMe drive with Windows (132GB) and Linux (95.7GB) on it, then a 500GB Samsung 960 Evo NVMe drive with OS X, and finally a Fusion Drive (Samsung 850 Evo & WD 2TB Drive with OS X). I use Grub2 to boot up Antergos.

    In addition to the previously reported issues, I was getting an error when regenerating the Grub config file that it could not find sdc0 (perhaps an external EFI partition accidentally created on the usb stick during the botched Arch installation?) but I fixed that by inserting ‘btrfs’ in mkinitcpio.conf file.

    lsblk -fm:

    NAME FSTYPE LABEL UUID                                 FSAVAIL FSUSE% MOUNTPOINT   SIZE OWNER GROUP MODE
    sda                                                                                1.8T           
    ├─sda1
    │    vfat   EFI WD20
    │                 67E3-17ED                                                        200M          
    ├─sda2
    │                                                                                  1.8T          
    └─sda3
         hfsplu Recovery HD
                      154dde5a-8dab-3817-855d-97d5c54e4ff1                           619.9M       
    sdb                                                                              465.8G       
    ├─sdb1
    │    vfat   EFI 850
    │                 67E3-17ED                                                        200M           
    ├─sdb2
    │                                                                                465.5G             
    └─sdb3
         hfsplu Boot OS X
                      0d932d18-fce0-336d-8b17-fef75ba49330                             128M          
    nvme1n1
    │                                                                                232.9G           
    ├─nvme1n1p1
    │    ntfs   Recovery
    │                 2AE86035E8600185                                                 300M            
    ├─nvme1n1p2
    │    vfat         6E60-C1AE                                                        100M           
    ├─nvme1n1p3
    │                                                                                  128M           
    ├─nvme1n1p4
    │    ntfs   Windows
    │                 FC0C620E0C61C46C                                               132.2G          
    ├─nvme1n1p5
    │    vfat   EFI   ED0C-D0F3                             509.4M     0% /boot/efi    512M         
    ├─nvme1n1p6
    │    swap   Swap  74aa3d39-940e-462d-9ac8-905fd1727a86                               4G            
    └─nvme1n1p7
         btrfs  Antergos
                      980dace1-9253-444d-98c4-72391d3b431f   83.7G    12% /           95.7G           
    nvme0n1
    │                                                                                465.8G            
    ├─nvme0n1p1
    │    vfat   EFI CLOVER
    │                 67E3-17ED                                                        200M            
    └─nvme0n1p2
         apfs         bf7fa970-adb1-4091-b7d3-3931ed546683                           465.6G         
    

    sudo fdisk -l:

    Disk /dev/nvme1n1: 232.9 GiB, 250059350016 bytes, 488397168 sectors
    Disk model: Samsung SSD 960 EVO 250GB               
    Units: sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 512 bytes / 512 bytes
    Disklabel type: gpt
    Disk identifier: 9BE05ADB-670D-467C-9137-C110AFE2EE1D
    
    Device             Start       End   Sectors   Size Type
    /dev/nvme1n1p1      2048    616447    614400   300M Windows recovery environment
    /dev/nvme1n1p2    616448    821247    204800   100M EFI System
    /dev/nvme1n1p3    821248   1083391    262144   128M Microsoft reserved
    /dev/nvme1n1p4   1083392 278308766 277225375 132.2G Microsoft basic data
    /dev/nvme1n1p5 278308767 279357439   1048673   512M EFI System
    /dev/nvme1n1p6 279357440 287746047   8388608     4G Linux swap
    /dev/nvme1n1p7 287746048 488396799 200650752  95.7G Linux filesystem
    
    
    Disk /dev/nvme0n1: 465.8 GiB, 500107862016 bytes, 976773168 sectors
    Disk model: Samsung SSD 960 EVO 500GB               
    Units: sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 512 bytes / 512 bytes
    Disklabel type: gpt
    Disk identifier: 6E22CA88-7A7E-4210-A278-1C86F3463D4F
    
    Device          Start       End   Sectors   Size Type
    /dev/nvme0n1p1     40    409639    409600   200M EFI System
    /dev/nvme0n1p2 409640 976773127 976363488 465.6G unknown
    
    
    Disk /dev/sda: 1.8 TiB, 2000398934016 bytes, 3907029168 sectors
    Disk model: WDC WD20EFRX-68E
    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: 4147D635-1D96-45FB-AC25-4AA43E08E1DC
    
    Device          Start        End    Sectors   Size Type
    /dev/sda1          40     409639     409600   200M EFI System
    /dev/sda2      409640 3905759591 3905349952   1.8T Apple Core storage
    /dev/sda3  3905759592 3907029127    1269536 619.9M Apple boot
    
    
    Disk /dev/sdb: 465.8 GiB, 500107862016 bytes, 976773168 sectors
    Disk model: Samsung SSD 850 
    Units: sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 512 bytes / 512 bytes
    Disklabel type: gpt
    Disk identifier: B0AE18D8-4A97-46FB-A775-4C26DB464760
    
    Device         Start       End   Sectors   Size Type
    /dev/sdb1         40    409639    409600   200M EFI System
    /dev/sdb2     409640 976510983 976101344 465.5G Apple Core storage
    /dev/sdb3  976510984 976773127    262144   128M Apple boot
    

    /etc/fstab entries:

    UUID=ED0C-D0F3 /boot/efi vfat defaults,relatime 0 0
    UUID=c410dea7-3304-43ee-8f0b-93598b17a00d swap swap defaults 0 0
    UUID=980dace1-9253-444d-98c4-72391d3b431f / btrfs defaults,relatime,space_cache,autodefrag,inode_cache 0 0
    
  • @Pl1SsK
    Seems that UUID for swap in /etc/fstab matches nothing.

    Also there is no reason to have many EFI partitions on a single disk, like nvme1n1p2 and nvme1n1p5 (it could have been only nvme1n1p5). But that probably doesn’t really hurt either.

  • @manuel Thanks for looking - fixing the Swap UUID in fstab fixed it. Apologies that I didn’t think of that myself as I should have checked it. I made some wrong assumptions about the nature of the problem and only tried meddling with the UUID of Root. I likely caused the problem when I recreated the swap partition during the Arch installation, as simply mounting the partition from command prompt in Arch did not seemingly work.

    You are right about the excessive EFI partitions, the reason I have 2 on /dev/nvme1 is that I tend to use Clover as default and when I choose Windows to boot up from the menu, I’d rather it ran the Windows Bootloader than go into Grub which would happen otherwise if I had both bootloaders in the same EFI partition (not a big deal anyway).

  • @Pl1SsK
    Great that you now got it working!

    And yes, multiple EFI partitions aren’t really a big deal, they don’t take much space anyway.

    And still one other thing: https://antergos.com/wiki/uncategorized/howto-forum-post-editor/#Mark_as_solved
    :)

  • @manuel Yes lol indeed, thanks again. When I say it’s working, it is still hanging 5-10 seconds and giving an error message after the ‘Starting version 239’ text, regarding hibernation for UUID=c410dea7-3304-43ee-8f0b-93598b17a00d (which I think is the old UUID before Arch recreated it); but it is not counting up to 1m30s before starting lightdm like previously, which was my main point of contention. Can this be fixed by changing the UUID of the swap partition back to c410dea7 etc. and updating the fstab file to reflect the change? I tried doing this quickly now but the change UUID option in Gparted was greyed out and couldn’t figure it out in command line. Cheers.

  • @Pl1SsK
    Are you sure that UUID is still not in /etc/fstab?

    I don’t think it is easy to change UUID to something fixed (well I’ve never done that TBH). But I think you could reformat that swap partition with gparted after booting with the USB installer stick. Be sure to change new UUID value into /etc/fstab.

  • @manuel Hi, yes. I tried that with gparted from live usb and it seems it is possible to generate a new random UUID for a partition but not a specific one that you want. I stumbled upon a forum post on askubuntu where it was claimed one needed to update 3 different files with the UUID, /etc/fstab being just one of them. The other files were ubuntu or debian specific but one of them was evidently the grub config file, so I edited this manually and found that the superceded UUID was there in 2 places under ‘quiet resume’, so I changed these to the present swap partition UUID and it fixed it. I had updated the grub config file with the relevant terminal command and rebooting a number of times after fixing the fstab file and putting the mkinitcpio.conf file back to how it was originally, but it evidently did not correct the swap UUID in the grub config file. Thanks very much for pointing me in the right direction and for the suggestions.

    #
    # DO NOT EDIT THIS FILE
    #
    # It is automatically generated by grub-mkconfig using templates
    # from /etc/grub.d and settings from /etc/default/grub
    #
    
    ### BEGIN /etc/grub.d/00_header ###
    insmod part_gpt
    insmod part_msdos
    if [ -s $prefix/grubenv ]; then
      load_env
    fi
    if [ "${next_entry}" ] ; then
       set default="${next_entry}"
       set next_entry=
       save_env next_entry
       set boot_once=true
    else
       set default="0"
    fi
    
    if [ x"${feature_menuentry_id}" = xy ]; then
      menuentry_id_option="--id"
    else
      menuentry_id_option=""
    fi
    
    export menuentry_id_option
    
    if [ "${prev_saved_entry}" ]; then
      set saved_entry="${prev_saved_entry}"
      save_env saved_entry
      set prev_saved_entry=
      save_env prev_saved_entry
      set boot_once=true
    fi
    
    function savedefault {
      if [ -z "${boot_once}" ]; then
        saved_entry="${chosen}"
        save_env saved_entry
      fi
    }
    
    function load_video {
      if [ x$feature_all_video_module = xy ]; then
        insmod all_video
      else
        insmod efi_gop
        insmod efi_uga
        insmod ieee1275_fb
        insmod vbe
        insmod vga
        insmod video_bochs
        insmod video_cirrus
      fi
    }
    
    set menu_color_normal=white/black
    set menu_color_highlight=black/light-green
    
    insmod part_gpt
    insmod btrfs
    if [ x$feature_platform_search_hint = xy ]; then
      search --no-floppy --fs-uuid --set=root  980dace1-9253-444d-98c4-72391d3b431f
    else
      search --no-floppy --fs-uuid --set=root 980dace1-9253-444d-98c4-72391d3b431f
    fi
    if loadfont /boot/grub/unicode.pf2 ; then
      set gfxmode=2560x1440
      load_video
      insmod gfxterm
      set locale_dir=$prefix/locale
      set lang=en_GB
      insmod gettext
    fi
    terminal_input console
    terminal_output gfxterm
    insmod part_gpt
    insmod btrfs
    if [ x$feature_platform_search_hint = xy ]; then
      search --no-floppy --fs-uuid --set=root  980dace1-9253-444d-98c4-72391d3b431f
    else
      search --no-floppy --fs-uuid --set=root 980dace1-9253-444d-98c4-72391d3b431f
    fi
    insmod gfxmenu
    insmod jpeg
    insmod png
    set theme=($root)/boot/grub/themes/163072-umbrela002/theme.txt
    export theme
    if [ x$feature_timeout_style = xy ] ; then
      set timeout_style=menu
      set timeout=5
    # Fallback normal timeout code in case the timeout_style feature is
    # unavailable.
    else
      set timeout=5
    fi
    ### END /etc/grub.d/00_header ###
    
    ### BEGIN /etc/grub.d/06_grub-customizer_menu_color_helper ###
    set color_normal=white/black
    set color_highlight=black/light-green
    ### END /etc/grub.d/06_grub-customizer_menu_color_helper ###
    
    ### BEGIN /etc/grub.d/10_antergos_proxy ###
    
    
    
    
    menuentry "Antergos Linux" --class antergos --class arch --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-simple-980dace1-9253-444d-98c4-72391d3b431f' {
    	load_video
    	set gfxpayload=keep
    	insmod gzio
    	insmod part_gpt
    	insmod btrfs
    	if [ x$feature_platform_search_hint = xy ]; then
    	  search --no-floppy --fs-uuid --set=root  980dace1-9253-444d-98c4-72391d3b431f
    	else
    	  search --no-floppy --fs-uuid --set=root 980dace1-9253-444d-98c4-72391d3b431f
    	fi
    	echo	'Loading  linux kernel ...'
    	linux	/boot/vmlinuz-linux root=UUID=980dace1-9253-444d-98c4-72391d3b431f rw  quiet resume=UUID=c410dea7-3304-43ee-8f0b-93598b17a00d
    	echo	'Loading initial ramdisk ...'
    	initrd	/boot/intel-ucode.img /boot/initramfs-linux.img
    }
    menuentry "Antergos Linux - Fallback" --class antergos --class arch --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-simple-980dace1-9253-444d-98c4-72391d3b431f' {
    		load_video
    		set gfxpayload=keep
    		insmod gzio
    		insmod part_gpt
    		insmod btrfs
    		if [ x$feature_platform_search_hint = xy ]; then
    		  search --no-floppy --fs-uuid --set=root  980dace1-9253-444d-98c4-72391d3b431f
    		else
    		  search --no-floppy --fs-uuid --set=root 980dace1-9253-444d-98c4-72391d3b431f
    		fi
    		echo	'Loading  linux kernel ...'
    		linux	/boot/vmlinuz-linux root=UUID=980dace1-9253-444d-98c4-72391d3b431f rw  quiet resume=UUID=c410dea7-3304-43ee-8f0b-93598b17a00d
    		echo	'Loading initial ramdisk ...'
    		initrd	/boot/intel-ucode.img /boot/initramfs-linux-fallback.img
    }
    ### END /etc/grub.d/10_antergos_proxy ###
    
    ### BEGIN /etc/grub.d/20_linux_xen ###
    ### END /etc/grub.d/20_linux_xen ###
    
    ### BEGIN /etc/grub.d/30_os-prober ###
    menuentry 'Windows Boot Manager (on /dev/nvme0n1p2)' --class windows --class os $menuentry_id_option 'osprober-efi-6E60-C1AE' {
    	insmod part_gpt
    	insmod fat
    	if [ x$feature_platform_search_hint = xy ]; then
    	  search --no-floppy --fs-uuid --set=root  6E60-C1AE
    	else
    	  search --no-floppy --fs-uuid --set=root 6E60-C1AE
    	fi
    	chainloader /efi/Microsoft/Boot/bootmgfw.efi
    }
    ### END /etc/grub.d/30_os-prober ###
    
    ### BEGIN /etc/grub.d/40_custom ###
    # This file provides an easy way to add custom menu entries.  Simply type the
    # menu entries you want to add after this comment.  Be careful not to change
    # the 'exec tail' line above.
    ### END /etc/grub.d/40_custom ###
    
    ### BEGIN /etc/grub.d/41_custom ###
    if [ -f  ${config_directory}/custom.cfg ]; then
      source ${config_directory}/custom.cfg
    elif [ -z "${config_directory}" -a -f  $prefix/custom.cfg ]; then
      source $prefix/custom.cfg;
    fi
    ### END /etc/grub.d/41_custom ###
    
    
  • @Pl1SsK to correct the resume=UUID for grub you need to edit /etc/default/grub file and regenerate grub.cfg with the command sudo grub-mkconfig -o /boot/grub/grub.cfg
    The files you ares shown say it also:

    #
    # DO NOT EDIT THIS FILE
    #
    # It is automatically generated by grub-mkconfig using templates
    # from /etc/grub.d and settings from /etc/default/grub
    #
    

    if UUID for swap is changed you need to change it inside /etc/fstab and /etc/default/grub !

  • Yes, grub.cfg needs to be updated, sorry I didn’t mention that. But I’m not 100% sure that grub updater (grub-mkconfig) always does a great job …

    But here are some additional ideas:
    https://forum.antergos.com/topic/9039/grub-boot-examples-custom-cfg
    https://forum.antergos.com/topic/9188/create-boot-grub-custom-cfg-grub-assistant

    They deal with a new file /boot/grub/custom.cfg that grub uses at boot if it exists. There you can have your grub boot entries as you like, and grub will not overwrite them (note that grub may overwrite the contents of grub.cfg).

  • @manuel @joekamprad Thanks for the replies guys. I fixed the problem (both problems). Perhaps I should have been less verbose in my last post. I included my grub config file for illustrative purposes. To summarise, I semi-broke my Antergos installation by creating a new UUID for the swap partition during Arch installation. I partially fixed it by editing the Antergos fstab file with the new swap UUID, which got rid of the 90 second wait on boot up. I then manually edited the grub config file with the new swap UUID, which still had entries in it for the old swap UUID despite my repeated attempts to generate it with the correct terminal command above. Manuel, thanks for the links, they look like interesting, I will digest this.

  • @Pl1SsK verbosity is good, but be more precise, and give exact commands you are using will result in less failures on both sides 😏

error306 boot271 Posts 16Views 212
Bloom Email Optin Plugin

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