having trouble installing Arch on encrypted fakeraid partition

thomaszout · 2016-09-11 12:23:05

Hi,

I'm trying to install Arch on a encrypted fakeraid partition. I have installed Arch before on a encrypted volume, so I think my trouble has to do with the fakeraid (Intel). I follow the guide (https://wiki.archlinux.org/index.php/In … _Fake_RAID) to the letter... I have an UEFI system and my partition is formatted as BTRFS. When I boot I get the message device 'dev/mapper/root' not found. Anyone able to help?

Kind regards,

Thomas

fstab:

# /dev/mapper/root
UUID=cab58d3a-2e9d-4c3c-9fd3-bc45d8984222	/         	btrfs     	rw,relatime,space_cache,subvolid=5,subvol=/	0 0
# /dev/md/thomas0p_1

# /dev/md126p4
UUID=3ad27931-4a46-4e79-98c4-c0faa72b5a05	/boot     	btrfs     	rw,relatime,space_cache,subvolid=5,subvol=/	0 0


# /dev/md126p3
UUID=7AC9-F7A4      	/boot/efi 	vfat      	rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro	0 2

# /dev/mapper/home
UUID=a590c2fc-698c-4923-b1de-8287a024fd0c	/home     	ext4      	rw,relatime,data=ordered	0 2

grub

GRUB_DEFAULT=0
GRUB_TIMEOUT=5
GRUB_DISTRIBUTOR="Arch"
GRUB_CMDLINE_LINUX_DEFAULT="quiet"
GRUB_CMDLINE_LINUX="cryptdevice=UUID=cbd47ff5-0b89-4028-ab65-cfd4204fbf23:root root=/dev/mapper/root"
GRUB_CMDLINE_LINUX="cryptdevice=/dev/md/thomas_0p1:root root=/dev/mapper/root"

# Preload both GPT and MBR modules so that they are not missed
GRUB_PRELOAD_MODULES="part_gpt part_msdos"

# Uncomment to enable Hidden Menu, and optionally hide the timeout count
#GRUB_HIDDEN_TIMEOUT=5
#GRUB_HIDDEN_TIMEOUT_QUIET=true

# Uncomment to use basic console
GRUB_TERMINAL_INPUT=console

# Uncomment to disable graphical terminal
#GRUB_TERMINAL_OUTPUT=console

# The resolution used on graphical terminal
# note that you can use only modes which your graphic card supports via VBE
# you can see them in real GRUB with the command `vbeinfo'
GRUB_GFXMODE=auto

# Uncomment to allow the kernel use the same resolution used by grub
GRUB_GFXPAYLOAD_LINUX=keep

# Uncomment if you want GRUB to pass to the Linux kernel the old parameter 
# format "root=/dev/xxx" instead of "root=/dev/disk/by-uuid/xxx" 
# GRUB_DISABLE_LINUX_UUID=true

# Uncomment to disable generation of recovery mode menu entries
GRUB_DISABLE_RECOVERY=true

# Uncomment and set to the desired menu colors.  Used by normal and wallpaper 
# modes only.  Entries specified as foreground/background.
#GRUB_COLOR_NORMAL="light-blue/black"
#GRUB_COLOR_HIGHLIGHT="light-cyan/blue"

# Uncomment one of them for the gfx desired, a image background or a gfxtheme
#GRUB_BACKGROUND="/path/to/wallpaper"
#GRUB_THEME="/path/to/gfxtheme"

# Uncomment to get a beep at GRUB start
#GRUB_INIT_TUNE="480 440 1"

#GRUB_SAVEDEFAULT="true"

mkinit

# 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=""

# 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="/sbin/mdmon"

# 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 mdadm_udev encrypt filesystems keyboard fsck"

# 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=""

Update:
Thnx for the advice, I'll try it later. However, I think it has to do with the grub-file...

Last edited by thomaszout (2016-09-13 13:57:59)

basica · 2016-09-13 10:33:41

Hey Thomas,

First off, when pasting output please put it in code tags. You can find out here. It makes the content scrollable and easier for everyone to read.

From the error message, it's obviously not picking up the root drive to boot, which hopefully just means there's something up with your fstab. Usually mapping to a UUID isn't a problem, but I've had this issue myself. Try regenerating your fstab with genfstab from the live environment, but without the -U option and instead use -L and see if that makes any difference. Perhaps someone with some more knowledge could be of further help if this doesn't sort it out for you.

R00KIE · 2016-09-13 23:18:13

How did you install arch and how did you configure it to use fakeraid? Which guides or tutorials have you followed?

Arch Linux

#1 2016-09-11 12:23:05

having trouble installing Arch on encrypted fakeraid partition

#2 2016-09-13 10:33:41

Re: having trouble installing Arch on encrypted fakeraid partition

#3 2016-09-13 23:18:13

Re: having trouble installing Arch on encrypted fakeraid partition

Board footer