странная ошибка при сборке Xen

parted -a optimal /dev/sdd
GNU Parted 3.4
Используется /dev/sdd
Добро пожаловать в GNU Parted! Наберите 'help' для просмотра списка команд.
(parted) p                                                                
Модель: ATA Kingston SHPM228 (scsi)
Диск /dev/sdd: 240GB
Размер сектора (логич./физич.): 512B/4096B
Таблица разделов: gpt
Флаги диска: 

Номер  Начало  Конец   Размер  Файловая система  Имя     Флаги
 1     1049kB  3146kB  2097kB                    grub    bios_grub
 2     3146kB  137MB   134MB   fat16             boot    загрузочный, esp
 3     137MB   8727MB  8590MB  linux-swap(v1)    swap
 4     8727MB  240GB   231GB   f2fs              rootfs

/dev/sdd2 /boot vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro 0 0

emerge -pav xen

These are the packages that would be merged, in order:

Calculating dependencies        ... done!      
[ebuild  N     ] app-emulation/xen-4.15.1-r2::gentoo  USE="-debug -efi -flask" 0 KiB

Total: 1 package (1 new), Size of downloads: 0 KiB

USE="efi" emerge xen
Calculating dependencies ... done!               
[ebuild   R    ] sys-devel/binutils-2.37_p1  USE="multitarget*" 
[ebuild  N     ] app-emulation/xen-4.15.1-r2  USE="efi -debug -flask" 

The following USE changes are necessary to proceed:
 (see "package.use" in the portage(5) man page for more details)
# required by app-emulation/xen-4.15.1-r2::gentoo[efi]
# required by xen (argument)
>=sys-devel/binutils-2.37_p1 multitarget

Use --autounmask-write to write changes to config files (honoring
CONFIG_PROTECT). Carefully examine the list of proposed changes,
paying special attention to mask or keyword changes that may expose
experimental or unstable packages.

>>> Installing (1 of 1) app-emulation/xen-4.15.1-r2::gentoo
 * This package will overwrite one or more files that may belong to other
 * packages (see list below). You can use a command such as `portageq
 * owners / <filename>` to identify the installed package that owns a
 * file. If portageq reports that only one package owns a file then do
 * NOT file a bug report. A bug report is only useful if it identifies at
 * least two or more packages that are known to install the same file(s).
 * If a collision occurs and you can not explain where the file came from
 * then you should simply ignore the collision since there is not enough
 * information to determine if a real problem exists. Please do NOT file
 * a bug report at https://bugs.gentoo.org/ unless you report exactly
 * which two packages install the same file(s). See
 * https://wiki.gentoo.org/wiki/Knowledge_Base:Blockers for tips on how
 * to solve the problem. And once again, please do NOT file a bug report
 * unless you have completely understood the above message.
 * 
 * Detected file collision(s):
 * 
 * 	/boot/xen-4.15.2-pre.gz
 * 	/boot/xen-4.15.2-pre.config
 * 	/usr/lib/debug/xen-syms-4.15.2-pre
 * 	/usr/lib/debug/xen-syms-4.15.2-pre.map
 * 
 * Searching all installed packages for file collisions...
 * 
 * Press Ctrl-C to Stop
 * 
 * None of the installed packages claim the file(s).
 * 
 * Package 'app-emulation/xen-4.15.1-r2' merged despite file collisions.
 * If necessary, refer to your elog messages for the whole content of the
 * above message.
 * Your boot partition was detected as being mounted at /boot.
 * Files will be installed there for xen to function correctly.
 * Official Xen Guide:
 *  https://wiki.gentoo.org/wiki/Xen
 * The efi executable is installed in /boot/efi/gentoo
 * 
 * Xen 4.12+ changed the default scheduler to credit2 which can cause
 * domU lockups on multi-cpu systems. The legacy credit scheduler seems
 * to work fine.
 * 
 * Add sched=credit to xen command line options to use the legacy scheduler.
 * 
 * https://wiki.gentoo.org/wiki/Xen#Xen_domU_hanging_with_Xen_4.12.2B

>>> Recording app-emulation/xen in "world" favorites file...

 * Messages for package app-emulation/xen-4.15.1-r2:

 * This package will overwrite one or more files that may belong to other
 * packages (see list below). You can use a command such as `portageq
 * owners / <filename>` to identify the installed package that owns a
 * file. If portageq reports that only one package owns a file then do
 * NOT file a bug report. A bug report is only useful if it identifies at
 * least two or more packages that are known to install the same file(s).
 * If a collision occurs and you can not explain where the file came from
 * then you should simply ignore the collision since there is not enough
 * information to determine if a real problem exists. Please do NOT file
 * a bug report at https://bugs.gentoo.org/ unless you report exactly
 * which two packages install the same file(s). See
 * https://wiki.gentoo.org/wiki/Knowledge_Base:Blockers for tips on how
 * to solve the problem. And once again, please do NOT file a bug report
 * unless you have completely understood the above message.
 * 
 * Detected file collision(s):
 * 
 * 	/boot/xen-4.15.2-pre.gz
 * 	/boot/xen-4.15.2-pre.config
 * 	/usr/lib/debug/xen-syms-4.15.2-pre
 * 	/usr/lib/debug/xen-syms-4.15.2-pre.map
 * 
 * Searching all installed packages for file collisions...
 * 
 * Press Ctrl-C to Stop
 * 
 * None of the installed packages claim the file(s).
 * 
 * Package 'app-emulation/xen-4.15.1-r2' merged despite file collisions.
 * If necessary, refer to your elog messages for the whole content of the
 * above message.
 * Official Xen Guide:
 *  https://wiki.gentoo.org/wiki/Xen
 * 
 * Xen 4.12+ changed the default scheduler to credit2 which can cause
 * domU lockups on multi-cpu systems. The legacy credit scheduler seems
 * to work fine.
 * 
 * Add sched=credit to xen command line options to use the legacy scheduler.
 * 
 * https://wiki.gentoo.org/wiki/Xen#Xen_domU_hanging_with_Xen_4.12.2B
>>> Auto-cleaning packages...

 mount /dev/sda2 /mnt/gentoo/boot