Автотусклый гm trying to the installation of Убунту Сервер 14.04LTS through PXE. I have set up в server that hosts DHCP, TFTP and HTTP. I have set up в DHCP scope with в PXE boot filename. I have copied the Убунту Сервер СD to the Веб server. I have authored в kickstart file and uploaded that to the Веб server. All of this was подарил per the instructions at https://help.ubuntu.com/community/PXEInstallServer.
When the client boots, it does get в DHCP offer, and it does PXE boot. The custom меню entry I have in /var/lib/tftpboot/pxelinux.cfg/default
gets displayed, and I хан choose this статья from the меню.
However, the kickstart file is never requested by the client одиннадцать the boot меню option is chosen, and the client ultimately panics with an "Unable to mount root fs on unknown-block" ошибка.
My pxelinux.cfg/default looks like this:
# D-I config version 2.0
include ubuntu-installer/amd64/boot-screens/menu.cfg
default ubuntu-installer/amd64/boot-screens/vesamenu.c32
prompt 0
timeout 10
LABEL CustomServerInstall
MENU LABEL Automated Trusty Install
KERNEL ubuntu-installer/amd64/linux
append ks=http://10.1.1.1/ks_ubuntuserver.cfg console=tty0 console=ttyS0 ignore_loglevel
When I choose "Аутоматед Трусти Install" from the меню, I do see the following in the boot text:
[ 3121.134818] Kernel command line: ks=http://10.1.1.1/ks_ubuntuserver.cfg console=tty0 console=ttyS0 ignore_loglevel BOOT_IMAGE=ubuntu-installer/amd64/linux
So I know my kickstart file path is given to the kernel. However, the file ks_ubuntuserver.cfg
is never requested by the client according to /var/log/apache2/access.log
When I enter curl http://10.1.1.1/ks_ubuntuserver.cfg
from another machine on the same subnet, I do get the kickstart file I authored.
So... the kickstart file is on the Веб server, but the kernel never requests it. Хан anyone help фигурировал out what гm doing wrong?
Вы не определили initrd
. Загрузчик загружает ядро и initrd
. Эти initrd
содержит файлы, которые ядро использует для начальной загрузки, включая init
, так как Вы не загружаетесь к реальной установке. Без него, ядро, вероятно, испуганное достаточно быстро.