On 12/27/2014 06:19 PM, Brooks Hu wrote:
---------- Forwarded message ---------- From: *Brooks Hu* <brooks...@gmail.com <mailto:brooks...@gmail.com>> Date: Friday, December 26, 2014Subject: Help!Failed to find a suitable stage1 device when using PXE installation.To: arm@lists.fedoraproject.org <mailto:arm@lists.fedoraproject.org> Hi all,I am trying automatic PXE installation (Fedora 21 for AARCH64) on my Mustang board, but looks like kickstart can't work.Here comes the detail: Starting installer, one moment...find_file: stat /proc/device-tree/chosen/bootpath, No such file or directoryanaconda 21.48.21-1 for Fedora-Server 21 started. * installation log files are stored in /tmp during the installation * shell is available on TTY2* when reporting a bug add logs from /tmp as separate text/plain attachments10:26:29 Not asking for VNC because of an automated install Starting automated install...... Generating updated storage configuration storage configuration failed: failed to find a suitable stage1 device ================================================================================ Installation 1) [x] Language settings 2) [!] Timezone settings (English (United States)) (Timezone is not set.) 3) [x] Installation source 4) [!] Software selection (ftp://192.168.1.1/F21/) (Nothing selected) 5) [!] Installation Destination 6) [x] Network configuration (No disks selected) (Wired (eth0) connected) 7) [!] Root password 8) [!] User creation (Password is not set.) (No user will be created)Not enough space in filesystems for the current software selection. An additional 2861.02 MiB is needed. Please make your choice from above ['q' to quit | 'b' to begin installation |UEFI version is 1.1.0-rh-0.13Here comes the kick start config file(I modified based on a sample from certain website):
Note that the installation options indicate: 4) [!] Software selection (Nothing selected) and 5) [!] Installation Destination (No disks selected), which implies anaconda is not seeing (or accepting) some of the options in your kickstart. Please look in the logs in /tmp to find any errors.
There are some things in you kickstart that I am not familiar with, such as: vznetcfg --net=virt_network1:eth0 vztturlmap $FS_SERVER http://myrepository.com nosfxtemplate %eztmplates --cache and the following just look wrong for an aarch64 install: centos-6-x86_64 centos-6-x86 mailman-centos-6-x86_64 mailman-centos-6-x86I would try a more "standard" Fedora kickstart install first to make sure the repos, etc. are working, and then try adding the 'custom' config options to see what breaks.
Attached is an example kickstart I have successfully used for provisioning a Mustang board.
d.marlin ========
------------------------------------------------------------------------- text install lang en_US.UTF-8 keyboard us part efi --fstype=efi --size=300 --ondisk=sda part /boot --fstype=ext4 --size=512 --ondisk=sda part / --fstype=ext4 --size=20096 --ondisk=sda part /vz --fstype=ext4 --size=40768 --ondisk=sda part swap --size=4000 bootloader --location=partition --ondisk=sda network --bootproto dhcp rootpw root auth --enableshadow --passalgo=sha512 timezone --utc America/New_York reboot vznetcfg --net=virt_network1:eth0 vztturlmap $FS_SERVER http://myrepository.com nosfxtemplate %eztmplates --cache centos-6-x86_64 centos-6-x86 mailman-centos-6-x86_64 mailman-centos-6-x86 %packages @base @core @vz @ps %endI have tried all kinds of option combination, also deleted all the partitions, but it still can't work. Any suggestions/comments are welcomed!Best Regards, Brooks _______________________________________________ arm mailing list arm@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/arm
F21-aarch64-RC7.ks
Description: application/java-keystore
_______________________________________________ arm mailing list arm@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/arm