You are not logged in.

Pages: 1

#1 2015-03-10 14:19:20

BlueTRin
Member
Registered: 2015-03-10
Posts: 10

Acer S7-392 - Unable to boot Linux after installing Grub [SOLVED]

I have followed the instructions on the beginner's guide.

However after installing Grub, I am unable to boot Linux. I managed to add an entry for Windows and boot it successfully.

'blkid' returns the following:

/dev/sda: TYPE="isw_raid_member"
/dev/sdb: TYPE="isw_raid_member"
/dev/sdc1: LABEL="ARCH_201503" UUID="1E0A-194C" TYPE="vfat" PARTUUID="c3072e18-01"
/dev/loop0: TYPE="squashfs"
/dev/loop1: UUID="5aecb61b-2567-403a-a752-050e4d164111" TYPE="ext4"
/dev/loop2: UUID="5aecb61b-2567-403a-a752-050e4d164111" TYPE="ext4"
/dev/mapper/arch_airootfs: UUID="5aecb61b-2567-403a-a752-050e4d164111" TYPE="ext4"
/dev/md126p1: LABEL="Recovery" UUID="70583CED583CB3A6" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="498d4ed4-3188-4daa-8059-824c94fd919a"
/dev/md126p2: LABEL="ESP" UUID="443E-CEA7" TYPE="vfat" PARTLABEL="EFI system partition" PARTUUID="5590eefc-4879-4ad8-bdbb-83addea5df0c"
/dev/md126p4: LABEL="Windows" UUID="8C48153E4815290A" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="ad25c7d6-ab88-4e42-be00-48fb3695771c"
/dev/md126p5: LABEL="ARCH" UUID="a5e3b60e-8359-8c5e-24d5-b31dcdb7c56c" TYPE="ext4" PARTLABEL="Basic data partition" PARTUUID="1dc85605-e2b2-4887-9f91-3b8e08a9b23d"
/dev/md126p6: UUID="C65D-DD84" TYPE="vfat" PARTLABEL="Basic data partition" PARTUUID="1b97aac7-91ea-490f-c87b-de63a37540a1"
/dev/md126p7: UUID="402ac0b6-7a85-40ff-8757-6e5aa62a7d46" TYPE="swap" PARTLABEL="Basic data partition" PARTUUID="591680a4-bda3-452b-75cc-54084b005b34"
/dev/md126p8: LABEL="Push Button Reset" UUID="E45E43485E43132A" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="03da0cd7-674e-494a-9b11-94bea46585ea"
/dev/md126: PTUUID="db649bd9-6051-46ac-8a57-6506552ae288" PTTYPE="gpt"
/dev/md126p3: PARTLABEL="Microsoft reserved partition" PARTUUID="18c44381-ef76-4f4b-8b26-f92980cfe007"

My /boot/grub/grub.cfg file can be found there: http://pastebin.com/pYqPqtRf


I use the following script to install grub:

##!/bin/bash
grub-mkconfig > /boot/grub/grub.cfg
grub-install --target=x86_64-efi --efi-directory=/boot --bootloader-id=grub_uefi --boot-directory=/boot --recheck --debug

On startup, after selecting the Arch partition in grub, I see the following in the console

[ xxxxxxxxxx] Ignoring BGRT: Invalid status 0 (expected 1)
starting version 218
ERROR: device 'UUID=a5e3b60e-8359-8c5e-24d5-b31dcdb7c56c' not found. Skipping fsck.
ERROR: Unable to find root device 'UUID=a5e3b60e-8359-8c5e-24d5-b31dcdb7c56c' .
You are being dropped to a recovery shell
    Type 'exit' to try and continue booting
sh: can't access tty: job control turned off
[rootfs /]#

This is strange because my / folder is in /dev/md126p5 and the UUID looks correct (if it is not it is because I typed by hand the error message after booting):

/dev/md126p5: LABEL="ARCH" UUID="a5e3b60e-8359-8c5e-24d5-b31dcdb7c56c" TYPE="ext4" PARTLABEL="Basic data partition" PARTUUID="1dc85605-e2b2-4887-9f91-3b8e08a9b23d"

The contents of /etc/fstab are:

# 
# /etc/fstab: static file system information
#
# <file system>	<dir>	<type>	<options>	<dump>	<pass>
# /dev/md126p5 LABEL=ARCH

# /dev/md126p5 LABEL=ARCH
UUID=a5e3b60e-8359-8c5e-24d5-b31dcdb7c56c	/         	ext4      	rw,relatime,data=ordered	0 1

# /dev/md126p6
UUID=C65D-DD84      	/boot     	vfat      	rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro	0 2

# /dev/md126p4 LABEL=Windows
UUID=8C48153E4815290A	/win8     	ntfs      	rw,nosuid,nodev,relatime,user_id=0,group_id=0,allow_other,blksize=4096	0 0

# /dev/md126p2 LABEL=ESP
UUID=443E-CEA7      	/winboot  	vfat      	rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro	0 2

# /dev/md126p7
UUID=402ac0b6-7a85-40ff-8757-6e5aa62a7d46	none      	swap      	defaults  	0 0

Contents of /etc/mdadm.conf:

ARRAY metadata=imsm UUID=eedb9717:497c85a8:ec631f8e:2c49b564
ARRAY /dev/md/HDD0 container=eedb9717:497c85a8:ec631f8e:2c49b564 member=0 UUID=db323da7:27ba19af:05b8d528:86d344eb

Contents of /etc/mkinitcpio.conf:

# vim:set ft=sh
# MODULES
# The following modules are loaded before any boot hooks are
# run.  Advanced users may wish to specify all system modules
# in this array.  For instance:
#     MODULES="piix ide_disk reiserfs"
MODULES="dm_mod"

# BINARIES
# This setting includes any additional binaries a given user may
# wish into the CPIO image.  This is run last, so it may be used to
# override the actual binaries included by a given hook
# BINARIES are dependency parsed, so you may safely ignore libraries
BINARIES=""

# FILES
# This setting is similar to BINARIES above, however, files are added
# as-is and are not parsed in any way.  This is useful for config files.
FILES=""

# HOOKS
# This is the most important setting in this file.  The HOOKS control the
# modules and scripts added to the image, and what happens at boot time.
# Order is important, and it is recommended that you do not change the
# order in which HOOKS are added.  Run 'mkinitcpio -H <hook name>' for
# help on a given hook.
# 'base' is _required_ unless you know precisely what you are doing.
# 'udev' is _required_ in order to automatically load modules
# 'filesystems' is _required_ unless you specify your fs modules in MODULES
# Examples:
##   This setup specifies all modules in the MODULES setting above.
##   No raid, lvm2, or encrypted root is needed.
#    HOOKS="base"
#
##   This setup will autodetect all modules for your system and should
##   work as a sane default
#    HOOKS="base udev autodetect block filesystems"
#
##   This setup will generate a 'full' image which supports most systems.
##   No autodetection is done.
#    HOOKS="base udev block filesystems"
#
##   This setup assembles a pata mdadm array with an encrypted root FS.
##   Note: See 'mkinitcpio -H mdadm' for more information on raid devices.
#    HOOKS="base udev block mdadm encrypt filesystems"
#
##   This setup loads an lvm2 volume group on a usb device.
#    HOOKS="base udev block lvm2 filesystems"
#
##   NOTE: If you have /usr on a separate partition, you MUST include the
#    usr, fsck and shutdown hooks.
HOOKS="base udev autodetect modconf block filesystems keyboard fsck mdadm"

# COMPRESSION
# Use this to compress the initramfs image. By default, gzip compression
# is used. Use 'cat' to create an uncompressed image.
#COMPRESSION="gzip"
#COMPRESSION="bzip2"
#COMPRESSION="lzma"
#COMPRESSION="xz"
#COMPRESSION="lzop"
#COMPRESSION="lz4"

# COMPRESSION_OPTIONS
# Additional options for the compressor
#COMPRESSION_OPTIONS=""

I am a bit struggling on this one, is it because the Acer S7 comes with a RAID 0 by default ?

EDIT1: I checked the UUID strings, I made a mistake when copying pasting the error message, it is correct now.

EDIT2: I added the contents of /etc/mkinitcpio.conf and /etc/mdadm.conf, although I am not 100% sure it is relevant as this fails at the bootloader stage:

Last edited by BlueTRin (2015-03-12 18:46:46)

Offline

#2 2015-03-10 17:10:53

jdarnold
Member
From: Medford MA USA
Registered: 2009-12-15
Posts: 485
Website

Re: Acer S7-392 - Unable to boot Linux after installing Grub [SOLVED]

Probably something to do with RAID & GRUB? Have you read this? https://wiki.archlinux.org/index.php/So … ID_and_LVM

Offline

#3 2015-03-10 17:19:28

BlueTRin
Member
Registered: 2015-03-10
Posts: 10

Re: Acer S7-392 - Unable to boot Linux after installing Grub [SOLVED]

jdarnold wrote:

Probably something to do with RAID & GRUB? Have you read this? https://wiki.archlinux.org/index.php/So … ID_and_LVM

I will read this, but it looks like it starts from setuping a new RAID, in my case I could manage to get the USB stick Arch linux image to recognise the RAID 0 and perform the install. The only thing I miss is the boot loader to start and the devices to be mounted correctly.

I could do the Arch-chroot and the rest of the install.

Offline

#4 2015-03-10 17:19:28

nullified
Member
From: Massachusetts, USA
Registered: 2013-12-09
Posts: 468

Re: Acer S7-392 - Unable to boot Linux after installing Grub [SOLVED]

BlueTRin wrote:
ERROR: device 'UUID=a5e3b60e-8359-8c5e-24d5-b31dcbdb7c56c' not found. Skipping fsck.

This is strange because my / folder is in /dev/md126p5 and the UUID looks correct (if it is not it is because I typed by hand the error message after booting):

/dev/md126p5: LABEL="ARCH" UUID="a5e3b60e-8359-8c5e-24d5-b31dcdb7c56c" TYPE="ext4" PARTLABEL="Basic data partition" PARTUUID="1dc85605-e2b2-4887-9f91-3b8e08a9b23d"

I am a bit struggling on this one, is it because the Acer S7 comes with a RAID 0 by default ?

They aren't the same. Are you saying that is simply a mistake because you are typing it out? Make sure they are exactly the same. An assurance that it is just a typo isn't helpful for troubleshooting. Can you post your fstab and the exact error message.

"We may say most aptly, that the Analytical Engine weaves algebraical patterns just as the Jacquard-loom weaves flowers and leaves." - Ada Lovelace

Offline

#5 2015-03-10 17:21:41

BlueTRin
Member
Registered: 2015-03-10
Posts: 10

Re: Acer S7-392 - Unable to boot Linux after installing Grub [SOLVED]

nullified wrote:
BlueTRin wrote:
ERROR: device 'UUID=a5e3b60e-8359-8c5e-24d5-b31dcbdb7c56c' not found. Skipping fsck.

This is strange because my / folder is in /dev/md126p5 and the UUID looks correct (if it is not it is because I typed by hand the error message after booting):

/dev/md126p5: LABEL="ARCH" UUID="a5e3b60e-8359-8c5e-24d5-b31dcdb7c56c" TYPE="ext4" PARTLABEL="Basic data partition" PARTUUID="1dc85605-e2b2-4887-9f91-3b8e08a9b23d"

I am a bit struggling on this one, is it because the Acer S7 comes with a RAID 0 by default ?

They aren't the same. Are you saying that is simply a mistake because you are typing it out? Make sure they are exactly the same. An assurance that it is just a typo isn't helpful for troubleshooting. Can you post your fstab and the exact error message.

I'll check, I typed it out from my desktop, since the laptop is not booting and not mounting anything I could not copy paste, this is why it may be different, I must have made a mistake when typing it. I'll check when I am back home to make sure.

Offline

#6 2015-03-10 18:17:28

BlueTRin
Member
Registered: 2015-03-10
Posts: 10

Re: Acer S7-392 - Unable to boot Linux after installing Grub [SOLVED]

I checked and the strings are the same, I edited the original post and added the contents of the fstab.

Offline

#7 2015-03-11 12:58:37

BlueTRin
Member
Registered: 2015-03-10
Posts: 10

Re: Acer S7-392 - Unable to boot Linux after installing Grub [SOLVED]

Thanks again to both of you, I think I got the minimum to boot up correctly now. I will summarise and post a reply here whenver I get some time. Hopefully this will help others.

Offline

#8 2015-03-12 16:34:13

BlueTRin
Member
Registered: 2015-03-10
Posts: 10

Re: Acer S7-392 - Unable to boot Linux after installing Grub [SOLVED]

I put here a summary of how I solved the issues I encounted:

http://nguyen.ly/2015/03/11/installing- … er-s7-392/

Offline

Pages: 1

Board footer

Powered by FluxBB