Can't Achieve A Bootable Void Install On UEFI + BIOS RAID + mdadm

Can't Achieve A Bootable Void Install On UEFI + BIOS RAID + mdadm

[Antonio Malcolm]

[-- Attachment #1.1: Type: text/plain, Size: 9329 bytes --]

SORRY, for the double-post, but I had left some info out in the original, 
and it doesn't appear that Google was going to allow me to edit, so let's 
try it again...

Combining my own experience with installing Linux with your  LVM + GPT + 
UEFI Wiki, I have been unable to build a Void installation which boots.
I'm able to install both Void and GRUB,successfully, but my machine does 
not recognize the OS, and GRUB doesn't load.

I've successfully installed and booted Manjaro in a way similar to that 
which I've installed Void, and it boots.

Below, are steps I took for install, with details:

RAID 0 configured in BIOS, using Intel Hybrid...

$ sudo su
# xbps-install mdadm gptfdisk
# mdadm --assemble --scan

mdadm: Container /dev/md/imsm0 has been assembled with 2 drives
mdadm: Started /dev/md/Loki_0 with 2 devices

# lsblk

NAME        MAJ:MIN RM   SIZE RO TYPE  MOUNTPOINT
sda           8:0    0 238.5G  0 disk 
  md126       9:126  0   477G  0 raid0
sdb           8:16   0 238.5G  0 disk 
  md126       9:126  0   477G  0 raid0 

# fdisk /dev/md126
  > g
  > w

# cgdisk /dev/md126

Part. #     Size        Partition Type            Partition Name
----------------------------------------------------------------
   1        200.0 MiB   EFI System                EFI             
   2        550.0 MiB   Linux filesystem         GRUB
   3        2.0 GiB       Linux swap                swap
   4        2.0 GiB       Linux filesystem          tmp
   5        6.0 GiB       Linux filesystem          var
   6        12.0 GiB     Linux filesystem          Void
   7        454.2 GiB   Linux filesystem          The Big Box

# lsblk

NAME        MAJ:MIN RM   SIZE RO TYPE  MOUNTPOINT
sda           8:0    0 238.5G  0 disk 
  md126       9:126  0   477G  0 raid0
    md126p1 259:0    0   200M  0 md   
    md126p2 259:1    0   550M  0 md   
    md126p3 259:2    0     2G  0 md   
    md126p4 259:3    0     2G  0 md   
    md126p5 259:4    0     6G  0 md   
    md126p6 259:5    0    12G  0 md   
    md126p7 259:6    0 454.2G  0 md   
sdb           8:16   0 238.5G  0 disk 
  md126       9:126  0   477G  0 raid0
    md126p1 259:0    0   200M  0 md   
    md126p2 259:1    0   550M  0 md   
    md126p3 259:2    0     2G  0 md   
    md126p4 259:3    0     2G  0 md   
    md126p5 259:4    0     6G  0 md   
    md126p6 259:5    0    12G  0 md   
    md126p7 259:6    0 454.2G  0 md   

# mkfs.vfat -F32 /dev/md126p1
# mkfs.xfs /dev/md126p2
# mkfs.xfs /dev/md126p4
# mkfs.xfs /dev/md126p5
# mkfs.xfs /dev/md126p6
# mkfs.xfs /dev/md126p7

# mkdir /mnt/void
# mount /dev/md126p6 /mnt/void

# mkdir /mnt/void/boot
# mkdir /mnt/void/tmp
# mkdir /mnt/void/var

# mount /dev/md126p2 /mnt/void/boot
# mount /dev/md126p4 /mnt/void/tmp
# mount /dev/md126p5 /mnt/void/var

# mkdir /mnt/void/boot/grub
# mkdir /mnt/void/boot/efi
# mount /dev/md126p1 /mnt/void/boot/efi

# xbps-install -S -R http://repo3.voidlinux.eu/current -r /mnt/void 
base-system grub-x86_64-efi mdadm
107 downloaded, 107 installed, 0 updated, 107 configured, 0 removed.

#cd /mnt/void
# ls -la
total 12
drwxr-xr-x 16 root root 4096 Jan 17 15:27 .
drwxr-xr-x  3 root root 4096 Jan 17 15:16 ..
lrwxrwxrwx  1 root root    7 Jan 17 15:26 bin -> usr/bin
drwxr-xr-x  4 root root  127 Jan 17 15:37 boot
drwxr-xr-x  2 root root   17 Jan 17 15:26 dev
drwxr-xr-x 26 root root 4096 Jan 17 15:27 etc
drwxr-xr-x  2 root root    6 Jan 17 15:26 home
lrwxrwxrwx  1 root root    7 Jan 17 15:26 lib -> usr/lib
lrwxrwxrwx  1 root root    9 Jan 17 15:26 lib32 -> usr/lib32
lrwxrwxrwx  1 root root    7 Jan 17 15:26 lib64 -> usr/lib
drwxr-xr-x  2 root root    6 Jan 17 15:26 media
drwxr-xr-x  2 root root    6 Jan 17 15:26 mnt
drwxr-xr-x  2 root root    6 Jan 17 15:26 opt
drwxr-xr-x  2 root root    6 Jan 17 15:26 proc
drwxr-x---  2 root root   26 Jan 17 15:39 root
drwxr-xr-x  3 root root   17 Jan 17 15:26 run
lrwxrwxrwx  1 root root    8 Jan 17 15:26 sbin -> usr/sbin
drwxr-xr-x  2 root root    6 Jan 17 15:26 sys
drwxrwxrwt  2 root root    6 Jan 17 15:15 tmp
drwxr-xr-x 11 root root  123 Jan 17 15:26 usr
drwxr-xr-x 11 root root  150 Jan 17 15:26 var

# chroot /mnt/void /bin/bash
bash-4.3#

bash-4.3# passwd root
Enter new UNIX password:
Retype new UNIX password:
passwd: password updated successfully
bash-4.3# chown root:root /
bash-4.3# chmod 755 /

bash-4.3# echo Loki >> /etc/hostname
bash-4.3# vi /etc/rc.conf

# /etc/rc.conf - system configuration for void

# Set RTC to UTC or localtime.
HARDWARECLOCK="UTC"

# Set timezone, availables timezones at /usr/share/zoneinfo.
TIMEZONE="America/Los_Angeles"

# Keymap to load, see loadkeys(8).
KEYMAP="en_us"

# Console font to load, see setfont(8).
#FONT="lat9w-16"

# Console map to load, see setfont(8).
#FONT_MAP=

# Font unimap to load, see setfont(8).
#FONT_UNIMAP=

# Kernel modules to load, delimited by blanks.
#MODULES=""

DAEMONS="mdadm"

bash-4.3# vi /etc/fstab

#
# See fstab(5).
#
# <file system> <dir>   <type>  <options>               <dump>  <pass>
tmpfs           /tmp    tmpfs   defaults,nosuid,nodev   0       0
UUID=dcdd0c5a-020b-4167-a10d-cb81d71e2ae6 / xfs 
rw,noatime,nodiratime,discard 0 1
UUID=d7d2ddae-cb94-4aea-bc4f-4784d6b3cc8e /boot xfs 
rw,noatime,nodiratime,discard 0 2
UUID=C071-6887 /boot/efi xfs rw,noatime,nodiratime,discard 0 2
UUID=97060d6a-039e-469f-b0aa-2fca2e33f464 /tmp xfs 
rw,noatime,nodiratime,discardi,nosui,nodev 0 2
UUID=4fb9395f-42c2-4b27-8545-1e9c1703c94d /var xfs 
rw,noatime,nodiratime,discardi,nosui,nodev 0 2
UUID=4a24a9e9-3c04-4aa5-826b-da2122347094 /home xfs 
rw,noatime,nodiratime,discard 0 2
PARTUUID=cfb8be30-1866-44a6-bdf5-60ced2a454f4 swap swap 
rw,noatime,nodiratime,discard 0 0v

bash-4.3# mkdir /etc/mdadm
bash-4.3# vi /etc/mdadm/mdadm.conf

# mdadm.conf
#
# Please refer to mdadm.conf(5) for information about this file.
#

DEVICE partitions

# auto-create devices with Debian standard permissions
CREATE owner=root group=disk mode=0660 auto=yes

# automatically tag new arrays as belonging to the local system
HOMEHOST <system>

# instruct the monitoring daemon where to send mail alerts
MAILADDR root

# definitions of existing MD arrays
ARRAY /dev/md/imsm0 metadata=imsm UUID=2ebff534:aa39707f:f7345046:da660d4e
ARRAY /dev/md/Loki_0 container=/dev/md/imsm0 member=0 
UUID=181551c2:a1fd1572:1afd7303:91031415

bash-4.3# vi /etc/dracut.conf

# PUT YOUR CONFIG HERE OR IN separate files named *.conf
# in /etc/dracut.conf.d
# SEE man dracut.conf(5)

# Sample dracut config file

#logfile=/var/log/dracut.log
#fileloglvl=6

# Exact list of dracut modules to use.  Modules not listed here are not 
going
# to be included.  If you only want to add some optional modules use
# add_dracutmodules option instead.
#dracutmodules+=""

# dracut modules to omit
#omit_dracutmodules+=""

# dracut modules to add to the default
#add_dracutmodules+=""

# additional kernel modules to the default
#add_drivers+=""

# list of kernel filesystem modules to be included in the generic initramfs
#filesystems+=""

# build initrd only to boot current hardware
hostonly="yes"


# install local /etc/mdadm.conf
mdadmconf="yes"

# install local /etc/lvm/lvm.conf
#lvmconf="no"

# A list of fsck tools to install. If it's not specified, module's hardcoded
# default is used, currently: "umount mount /sbin/fsck* xfs_db xfs_check
# xfs_repair e2fsck jfs_fsck reiserfsck btrfsck". The installation is
# opportunistic, so non-existing tools are just ignored.
#fscks=""

# inhibit installation of any fsck tools
#nofscks="yes"

# mount / and /usr read-only by default
#ro_mnt="no"

# set the directory for temporary files
# default: /var/tmp
tmpdir=/tmp

bash-4.3# exit

# mount --rbind /dev /mnt/void/dev
# mount -t proc /proc /mnt/void/proc
# mount --rbind /sys /mnt/void/sys

# chroot /mnt/void /bin/bash
bash-4.3#

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

Generating grub.cfg ...
Found background: /usr/share/void-artwork/splash.png
Found linux image: /boot/vmlinuz-3.18.3_1
Found initrd image: /boot/initramfs-3.18.3_1.img
done

bash-4.3# grub-install --target=x86_64-efi --efi-directory=/boot/efi 
--bootloader-id="Void Linux [GRUB]" --boot-directory=/boot --recheck --debug
...
Installation finished. No error reported.+ echo

bash-4.3# xbps-reconfigure -f linux3.18

linux3.18: configuring ...
Executing post-install kernel hook: 10-dracut ...
/bin/dracut: line 638: warning: setlocale: LC_MESSAGES: cannot change 
locale (en_US.UTF-8): No such file or directory
/bin/dracut: line 639: warning: setlocale: LC_CTYPE: cannot change locale 
(en_US.UTF-8): No such file or directory
Executing post-install kernel hook: 50-grub ...
Generating grub.cfg ...
Found background: /usr/share/void-artwork/splash.png
Found linux image: /boot/vmlinuz-3.18.3_1
Found initrd image: /boot/initramfs-3.18.3_1.img
done
linux3.18: configured successfully.

bash-4.3# exit
exit
# umount -R /mnt
umount: /mnt: not mounted
# umount -R /mnt/void
umount: /mnt/void: target is busy
        (In some cases useful info about processes that
         use the device is found by lsof(8) or fuser(1).)
#


[-- Attachment #1.2: Type: text/html, Size: 12983 bytes --]

Re: Can't Achieve A Bootable Void Install On UEFI + BIOS RAID + mdadm

[Juan RP]

[-- Attachment #1.1: Type: text/plain, Size: 133 bytes --]

Hi,

- Do you mean that your UEFI firmware does not contain any entry for 
booting void?

- What's the content of /boot/efi?


[-- Attachment #1.2: Type: text/html, Size: 185 bytes --]

Re: Can't Achieve A Bootable Void Install On UEFI + BIOS RAID + mdadm

[Antonio Malcolm]

[-- Attachment #1.1: Type: text/plain, Size: 537 bytes --]

I mean the machine doesn't recognize there's an OS to boot, and there's no 
listing for it in the UEFI control panel, so it's not recognizing an entry 
point.
Just getting back to this, and will try again, now, and make a better note 
of what's in /boot (I wiped my previous attempt clean, probably something I 
don't need to do, instead of working to make a current install work, but I 
needed to try a few times, cleanly, to view patterns in the process). 
Specifically, I'll look at where the EFI boot files are being placed.

[-- Attachment #1.2: Type: text/html, Size: 550 bytes --]

Re: Can't Achieve A Bootable Void Install On UEFI + BIOS RAID + mdadm

[Antonio Malcolm]

[-- Attachment #1.1: Type: text/plain, Size: 109 bytes --]

Ok, /boot/efi has a subdirectory: EFI.
Inside /boot/efi/EFI is a single file, labeled "Void Linux [GRUB]".

[-- Attachment #1.2: Type: text/html, Size: 134 bytes --]

Re: Can't Achieve A Bootable Void Install On UEFI + BIOS RAID + mdadm

[Juan RP]

[-- Attachment #1.1: Type: text/plain, Size: 184 bytes --]


This is your issue, you should have used "grub-instal ... 
--bootloader-id=void_grub ..."

This should add a "void_grub" entry to the EFI firmware, check it with 
`efibootmgr`.

[-- Attachment #1.2: Type: text/html, Size: 209 bytes --]

Re: Can't Achieve A Bootable Void Install On UEFI + BIOS RAID + mdadm

[Antonio Malcolm]

[-- Attachment #1.1: Type: text/plain, Size: 2172 bytes --]

BOOM GOES THE DYNAMITE! OK, concatenating my last few responses, to keep 
things organized, as I got this working, now.

After much trial, error, and research, I think the issue may have been in 
the way my logic board's firmware detects bootable volumes and maintains 
their records in NVRAM-
I'm on a Gigabyte logic board (Aorus X3 laptop), and Gigabyte's UEFI 
implementation is know to be a bit janky.

In fact, while the following IS successful, the machine conveniently 
"FORGETS" it on reboot:

efibootmgr --create --gpt --disk /dev/md126 --part 1 --label "Void Linux 
(GRUB)" --loader '\EFI\void_grub\grubx64.efi'

However, as Manjaro's GRUB install works, and sticks, I started with that, 
then installed Void again, per my above procedure, which updates GRUB, 
without overwriting the directories Manjaro's GRUB installs.
The difference, between the two, which stands out most, is the presence of 
a /BOOT/GRUBX64.EFI file, under /EFI. One issue which has been pointed out, 
not necessarily in buggy UEFI implementations, but on boards with Intel 
controllers (which my machine uses) is the seeking of directories in a 
case-sensitive manner. Nasty stuff. It might be fun to think, because it 
still works with Windows, maybe Intel has some conspiracy going on with 
them, but the reasoning is probably much dumber than that.

In Manjaro's case, they have a fairly big and broad user base, so it makes 
sense for them to "plan for all scenarios".
This benefited me, today, save for having to "clean" my boot directory, 
free of anything specific to their install (such as their linux 3.16 kernel 
images).

If you like, I can give you a more detailed description of the the /boot 
directory, and, if you're up to it, you can adjust your GRUB 
install/bootloader setup for the next release.
ALSO, as my procedure for rolling Void out on a BIOS RAID would likely work 
for most folks, without the troubles I had, I'm more than happy to clean up 
my notes, to add to the WIki, There were some additions I made to the 
dracut.conf, to assemble the array on startup. And, we can always add a 
footnote about the UEFI stuffs...

[-- Attachment #1.2: Type: text/html, Size: 2181 bytes --]

Re: Can't Achieve A Bootable Void Install On UEFI + BIOS RAID + mdadm

[Juan RP]

[-- Attachment #1.1: Type: text/plain, Size: 170 bytes --]


Great! please feel free to update the wiki with your experiences and setup. 

Just to clarify, manjaro has "/boot/efi/BOOT/GRUBX64.EFI" ?

Where /boot is the ESP.

[-- Attachment #1.2: Type: text/html, Size: 203 bytes --]

Re: Can't Achieve A Bootable Void Install On UEFI + BIOS RAID + mdadm

[Antonio Malcolm]

[-- Attachment #1.1: Type: text/plain, Size: 143 bytes --]

/boot/efi/EFI/BOOT/GRUBX64.EFI

SO, there's that and:

/boot/efi/EFI/GRUB/grubx64.efi

I'll clean up my notes and add them to the wiki.

[-- Attachment #1.2: Type: text/html, Size: 174 bytes --]

Re: Can't Achieve A Bootable Void Install On UEFI + BIOS RAID + mdadm

[Antonio Malcolm]

[-- Attachment #1.1: Type: text/plain, Size: 217 bytes --]


BTW, I also noticed an initramfs-3.17.4_1.img in /boot.
I'm not certain if it came from the Void distro or Manjaro, as neither is 
usiing that version of the Linux kernel.
Void uses 3.18, and Manjaro uses 3.16.

[-- Attachment #1.2: Type: text/html, Size: 244 bytes --]

Re: Can't Achieve A Bootable Void Install On UEFI + BIOS RAID + mdadm

[Juan RP]

[-- Attachment #1.1: Type: text/plain, Size: 103 bytes --]

Certainly this came from void.

Perhaps the live image uses this kernel and later you've updated...

[-- Attachment #1.2: Type: text/html, Size: 130 bytes --]

Re: Can't Achieve A Bootable Void Install On UEFI + BIOS RAID + mdadm

[Antonio Malcolm]

[-- Attachment #1.1: Type: text/plain, Size: 318 bytes --]

Yeah, I tested this by moving it to a backup directory, only to have the 
machine lose the Void install as a bootable option, again.
Moving it back and updating Grub fixed the issue.
Was curious, while cleaning out kernel images and other extraneous stuffs 
installed with Manjaro.
I like to keep things tidy...

[-- Attachment #1.2: Type: text/html, Size: 369 bytes --]

Re: Can't Achieve A Bootable Void Install On UEFI + BIOS RAID + mdadm

[Juan RP]

[-- Attachment #1.1: Type: text/plain, Size: 577 bytes --]

Just for the record, I've just changed mklive to install the grub EFI 
loader in ESP as `\\EFI\\BOOT\\BOOTX64.EFI'.

commit e514350f88c48f144fd2a76a3748fb35bd23b914
Author: Juan RP <xtr...@voidlinux.eu>
Date:   Sun Jul 12 08:48:08 2015 +0200

    mklive: install GRUB EFI loader as EFI/BOOT/BOOTX64.EFI.
    
    There are some EFI firmwares that expect the loader to be in that
    location and being uppercase, so that there more chances to make this
    boot on more systems.

This should make the live image even more compatible when booting with UEFI 
firmwares pre 2.3.


[-- Attachment #1.2: Type: text/html, Size: 668 bytes --]

Re: Can't Achieve A Bootable Void Install On UEFI + BIOS RAID + mdadm

[Antonio Malcolm]

[-- Attachment #1.1: Type: text/plain, Size: 54 bytes --]

Thanks, will test this on my next install.


~Antonio

[-- Attachment #1.2: Type: text/html, Size: 112 bytes --]