ArchLabs & multiboot: boot problem

For general ARCHLabs and Arch issues.
Please make a serious attempt to search for your issue before posting here.
We can't offer help if you have the Testing Repos enabled.

Moderator: Founder

ArchLabs & multiboot: boot problem

PostPosted by sardus-X » Sun Aug 06, 2017 9:29 pm

Hi All,
I installed ArchLabs v. 5.0.0 on a multiboot linux system (no bootloader option selected), updated Grub from linux mint 18.1 (main OS in in the multiboot system), reboot, but by selecting ArchLabs from the grub menu the startup process stops with this error:

Starting version 233
ERROR: resume: no device specified for hibernation
ERROR: device ‘UUID= ********-****-****-****-************’ not found. Skipping fsck.
mount: can’t find UUID=********-****-****-****-************
You are now being dropped into an emergency shell.
sh: can’t access tty; job control turned off
[rootfs ]#_

How can I fix this?
Thanks in advance for Your help
sardus-X
 
Posts: 2
Joined: Sun Aug 06, 2017 9:51 am
Running Release: v5.0.0

Re: ArchLabs & multiboot: boot problem

PostPosted by natemaia » Wed Aug 09, 2017 12:24 pm

My quick and easy suggestion would be to have Archlabs provide the bootloader, as it has everything needed for multi installed.
It will find your other boot partitions/disks and load them into the list. May I ask whether this is a UEFI boot or Legacy?

Dumb question, did grub-update complete successfully in Linux Mint and did it detect ArchLabs?
Was there anything specific to your install (aside from no bootloader option)?
User avatar
natemaia
ArchLabs Guru
ArchLabs Guru
 
Posts: 75
Joined: Thu Mar 16, 2017 10:14 pm
Location: Canada - British Columbia
Running Release: 5.0

Re: ArchLabs & multiboot: boot problem

PostPosted by sardus-X » Thu Aug 10, 2017 2:19 am

natemaia wrote:My quick and easy suggestion would be to have Archlabs provide the bootloader, as it has everything needed for multi installed.
It will find your other boot partitions/disks and load them into the list. May I ask whether this is a UEFI boot or Legacy?

For personal needs I installed first Linux Mint 18.1 in UEFI mode on a BIOS system on a disk with GPT partition table. Everything went well and afterwards I installed Elementary OS, KDE neon, Deepin OS (installing grub in / because there isn't a "no bootloader" option during install), Manjaro, Antergos, opensuse, each in a separate partition on the same HDD without problems.
natemaia wrote:Dumb question, did grub-update complete successfully in Linux Mint and did it detect ArchLabs?
Was there anything specific to your install (aside from no bootloader option)?

Yes, after grub-update and reboot an "ArchLabs" item has been added to the grub menu
I do not know if it is useful to understanding the problem but I have verified that the UUID in the "Archlabs" menuentry (grub.cfg file) at the line:
Code: Select all
linux /boot/vmlinuz-linux root=UUID=********-****-****-****-************ rw quiet

does not match the UUID retrieved with the "blkid" command for the sdc11 partition (ArchLabs) unlike the menuentries concerning the other distributions installed

This is the /boot/grub/grub.cfg file from ArchLabs File System after installation:
Code: Select all
#
# 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
set default="0"

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
}

if [ x$feature_default_font_path = xy ] ; then
   font=unicode
else
insmod part_msdos
insmod ext2
set root='hd0,msdos5'
if [ x$feature_platform_search_hint = xy ]; then
  search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos5 --hint-efi=hd0,msdos5 --hint-baremetal=ahci0,msdos5  ad4103fa-d940-47ca-8506-301d8071d467
else
  search --no-floppy --fs-uuid --set=root ad4103fa-d940-47ca-8506-301d8071d467
fi
    font="/usr/share/grub/unicode.pf2"
fi

if loadfont $font ; then
  set gfxmode=auto
  load_video
  insmod gfxterm
  set locale_dir=$prefix/locale
  set lang=en_US
  insmod gettext
fi
terminal_input console
terminal_output gfxterm
set timeout=5
### END /etc/grub.d/00_header ###

### BEGIN /etc/grub.d/10_linux ###
menuentry 'Arch Linux, with Linux core repo kernel' --class arch --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-core repo kernel-true-ad4103fa-d940-47ca-8506-301d8071d467' {
   load_video
   set gfxpayload=keep
   insmod gzio
   insmod part_msdos
   insmod ext2
   set root='hd0,msdos5'
   if [ x$feature_platform_search_hint = xy ]; then
     search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos5 --hint-efi=hd0,msdos5 --hint-baremetal=ahci0,msdos5  ad4103fa-d940-47ca-8506-301d8071d467
   else
     search --no-floppy --fs-uuid --set=root ad4103fa-d940-47ca-8506-301d8071d467
   fi
   echo   'Loading Linux core repo kernel ...'
   linux   /boot/vmlinuz-linux root=UUID=ad4103fa-d940-47ca-8506-301d8071d467 rw  quiet
   echo   'Loading initial ramdisk ...'
   initrd   /boot/initramfs-linux.img
}
menuentry 'Arch Linux, with Linux core repo kernel (Fallback initramfs)' --class arch --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-core repo kernel-fallback-ad4103fa-d940-47ca-8506-301d8071d467' {
   load_video
   set gfxpayload=keep
   insmod gzio
   insmod part_msdos
   insmod ext2
   set root='hd0,msdos5'
   if [ x$feature_platform_search_hint = xy ]; then
     search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos5 --hint-efi=hd0,msdos5 --hint-baremetal=ahci0,msdos5  ad4103fa-d940-47ca-8506-301d8071d467
   else
     search --no-floppy --fs-uuid --set=root ad4103fa-d940-47ca-8506-301d8071d467
   fi
   echo   'Loading Linux core repo kernel ...'
   linux   /boot/vmlinuz-linux root=UUID=ad4103fa-d940-47ca-8506-301d8071d467 rw  quiet
   echo   'Loading initial ramdisk ...'
   initrd   /boot/initramfs-linux-fallback.img
}

### END /etc/grub.d/10_linux ###

### BEGIN /etc/grub.d/20_linux_xen ###
### END /etc/grub.d/20_linux_xen ###

### BEGIN /etc/grub.d/20_memtest86+ ###
### END /etc/grub.d/20_memtest86+ ###

### BEGIN /etc/grub.d/30_os-prober ###
### 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 ###

The UUID=ad4103fa-d940-47ca-8506-301d8071d467 doesn't match any partition UUID on the HDD
sardus-X
 
Posts: 2
Joined: Sun Aug 06, 2017 9:51 am
Running Release: v5.0.0

Re: ArchLabs & multiboot: boot problem

PostPosted by ector » Sat Aug 12, 2017 1:43 am

remove grub on archlabs and reconfigure grub on mint,whit grub-update !
ector
 
Posts: 23
Joined: Thu Jun 01, 2017 6:14 am


Return to Basic Help and Support

Who is online

Users browsing this forum: No registered users and 0 guests