Leaderboard

@cardinal Thanks for that strace, that did help alot! I noticed one major difference while initializing. It seems that on my system its using: /usr/lib/python-exec/python3.4/../../../lib64/python3.4/encodings/ascii.py and on your system its using: /usr/lib/python-exec/python3.4/../../../lib64/python3.4/encodings/utf_8.py Using ascii instead of utf_8 in python is not completely unexpected on my system since I try to avoid building anything outside en_US locale with ISO-8859-1 encoding. Later, (on both yours and mine) it reads the file: /var/git/meta-repo/kits/core-kit/profiles/base/make.defaults In that file, it finds non-ascii (code points >0x7e) characters in the file contents as part of a utf-8 sequence in one of the first author's names in a comment, and mine dies immediately after, because the python ascii parser does not attempt to handle any extended characters and throws exceptions instead. So this brings up the next question of why my system is using ascii instead of utf_8. I do have utf-8 support enabled in some places, and I have the referenced "utf_8.py" file (the one yours loaded earlier) in my system, but it's not choosing to load it for some reason. I guess I'll dig in deeper and see where the rabbit hole leads. Thanks again cardinal!

Arg, I figured it out right after posting this. I specified my LVM root partition by two different paths, although both of them are valid. In boot.conf I had /dev/mapper/vg1-rootfs In fstab I had /dev/vg1/rootfs (which is a symbolic link to /dev/mapper/vg1-rootfs) Once I made them the same, boot-update worked. I realized two other mistakes I made, which I would like to point out. 1) In boot.conf I had this: kernel kernel[-v] initrd initramfs-genkernel[-v] This does not work because [-v] is not a wildcard like I had thought. It seems to be a variable which gets its value from the kernel line. On my system the kernel is 'kernel-debian-sources-x86_64-4.4.6-1'. So I think [-v] equals '-debian-sources-x86_64-4.4.6-1'. Boot-update cannot find a match for my initrd line, which would be 'initramfs-genkernel-debian-sources-x86_64-4.4.6-1' -- that file does not exist. I thought my initrd line would match to initramfs-genkernel-x86_64-4.4.6-1, but I was wrong about that. The other mistake I made is that I do not need the genkernel initramfs at all. The debian one works fine for an LVM root filesystem. So my files now look like this, and my system is bootable. /etc/boot.conf: boot { generate grub default "Funtoo Linux genkernel lvm" timeout 3 } "Funtoo Linux genkernel lvm" { kernel kernel[-v] initrd initramfs[-v] params += dolvm real_root=/dev/vg1/rootfs rootfstype=ext4 resume=swap:/dev/mapper/vg1-swap /etc/fstab: /dev/sda1 /boot ext2 noauto,noatime 1 2 /dev/vg1/swap none swap sw 0 0 /dev/vg1/rootfs / ext4 noatime 0 1 boot-update configures grub.cfg with the following kernel and initrd: kernel-debian-sources-x86_64-4.4.6-1 initramfs-debian-sources-x86_64-4.4.6-1 Sorry for the noise!