Gentoo: List of Issues After an Installation

Pretty much every time I install Gentoo I hit a new minor issue that requires my attention. Sometimes its caused by a new version of a particular package, sometimes I’ve simply forgot to configure something correctly. Either way, here is an on-going list of issues that I’ve faced after a new installation.

Networking Interfaces Renamed

The networking interfaces were renamed from eth0 to enp10s0 and enp09s0. While this did not make any difference as to whether or not they work, it is annoying!

storm ~ # ifconfig
enp10s0: flags=4163  mtu 1500
        inet  netmask  broadcast
        inet6 fe80::223:8cff:fe7b:5f0g  prefixlen 64  scopeid 0x20
        ether 00:23:8c:7b:5f:0g  txqueuelen 1000  (Ethernet)
        RX packets 2161  bytes 226082 (220.7 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 96  bytes 16270 (15.8 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

enp9s0: flags=4099  mtu 1500
        ether 00:21:7c:7b:60:ff  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0


To fix, just run the following command (as root) and then reboot.

storm ~ #  touch /etc/udev/rules.d/80-net-name-slot.rules 

RAID Devices Renamed

The RAID devices work renamed from /dev/md0, /dev/md1 and /dev/md2 to /dev/md126, /dev/md127 and /dev/md128. Again they work, but quite annoying!


If you are affected by this issue (and it bothers you), you may need to alter your /etc/mdadm.conf file to include a map between the UUID and the device name. In which case you first need to make a note of the UUID, which you can find with mdadm --detail /dev/md126 and then add an entry similar to the below.

Obviously you need to make sure the right UUID matches the right device name!

nano /etc/mdadm.conf

ARRAY /dev/md0 uuid=bffb1668:11863a10:bf3af795:0aa37b76
ARRAY /dev/md1 uuid=147ec32e:2721ff1a:3769d3d6:285e5546
ARRAY /dev/md2 uuid=0a3417f5:885e6352:c56063cf:7cc765e3

You may also need to edit the /etc/genkernel.conf file.

nano /etc/genkernel.conf

And add the following if needed.


You still need to run the following. Pay close attention to the output to make sure it is picking up and using the /etc/mdadm.conf file.

genkernel --lvm --mdadm initramfs
grub2-mkconfig -o /boot/grub2/grub.cfg

Hopefully that worked! If you get strange output from watch cat /proc/mdstat, make sure you give it long enough time to sync.


Be the first to comment

Leave a Reply