Fwd: Help!Failed to find a suitable stage1 device when using PXE installation.

[Brooks Hu]

---------- Forwarded message ----------
From: *Brooks Hu* 
Date: Friday, December 26, 2014
Subject: Help!Failed to find a suitable stage1 device when using PXE
installation.
To: [e-mail]

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 directory
anaconda 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
attachments
10: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.13

Here comes the kick start config file(I modified based on a sample from
certain website):

-------------------------------------------------------------------------
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
%end

I 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

[d.marlin]

On 12/27/2014 06:19 PM, Brooks Hu wrote:
> ---------- Forwarded message ----------
> From: *Brooks Hu* <[e-mail] >
> Date: Friday, December 26, 2014
> Subject: Help!Failed to find a suitable stage1 device when using PXE 
> installation.
> To: [e-mail]
>
> 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 
> directory
> anaconda 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
>
> attachments
> 10: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
> [x] Language settings                 2) [!] Timezone settings
>     (English (United States))  (Timezone is not set.)
> [x] Installation source               4) [!] Software selection
>     (ftp://192.168.1.1/F21/)                 (Nothing selected)
> [!] Installation Destination          6) [x] Network configuration
>     (No disks selected)                      (Wired (eth0) connected)
> [!] 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.13
>
> Here 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-x86

I 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
> %end
>
> I 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
> [e-mail]
> https://admin.fedoraproject.org/mailman/listinfo/arm

[Brooks Hu]

David,

Thanks for the help.

Regarding my configuration file, i just copied it from other thus some
lines wrong, but i think they have nothing to do with this issue. This
issue should only be related to disk partitioning.

I tried your kickstart configuration, but the issue still exists. I noticed
in the configuration there is a line "bootloader --location=mbr", does it
mean you are using legacy BIOS rather than EFI? I am using EFI BIOS.

I downloaded the image from here
http://arm.koji.fedoraproject.org/compose/21_RC7/Server/aarch64/iso/Fedora-S...

then setup a local FTP to host it.

Best Regards,
Brooks

On Mon, Dec 29, 2014 at 9:19 AM, David A. Marlin  wrote:
> On 12/27/2014 06:19 PM, Brooks Hu wrote:
>
> ---------- Forwarded message ----------
> From: *Brooks Hu* 
> Date: Friday, December 26, 2014
> Subject: Help!Failed to find a suitable stage1 device when using PXE
> installation.
> To: [e-mail]
>
> 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
> directory
> anaconda 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
>
> attachments
> 10: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
> [x] Language settings                 2) [!] Timezone settings
>    (English (United States))                (Timezone is not set.)
> [x] Installation source               4) [!] Software selection
>     (ftp://192.168.1.1/F21/)                 (Nothing selected)
> [!] Installation Destination          6) [x] Network configuration
>     (No disks selected)                      (Wired (eth0) connected)
> [!] 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.13
>
> Here 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-x86
>
> I 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
> %end
>
> I 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 [e-mail]://admin.fedoraproject.org/mailman/listinfo/arm
>
> arm mailing list
> [e-mail]
> https://admin.fedoraproject.org/mailman/listinfo/arm

[d.marlin]

On 12/29/2014 12:05 AM, Brooks Hu wrote:
> David,
>
> Thanks for the help.
>
> Regarding my configuration file, i just copied it from other thus some 
> lines wrong, but i think they have nothing to do with this issue. This 
> issue should only be related to disk partitioning.

Are you certain that anaconda is finding the kickstart file (checked the 
server logs)?  There were two issues pointed out before:

4) [!] Software selection (Nothing selected)
   5) [!] Installation Destination (No disks selected)

Since it did not know which Software was selected (%packages in the 
kickstart) or the Installation Destination (specified as sda in the 
kickstart), it may not be finding the kickstart at all, or may not be 
able to successfully parse it.  Is it also possible that the initrd does 
not include all the requisite drivers to find the network or disk.  
Please inspect the anaconda logs to see what errors are occurring.  From 
the shell window you can also verify that the network is functional (use 
curl to get the kickstart file), and check that the expected partitions 
are available.
> I tried your kickstart configuration, but the issue still exists. I 
> noticed in the configuration there is a line "bootloader 
> --location=mbr", does it mean you are using legacy BIOS rather than 
> EFI? I am using EFI BIOS.

I am using EFI as well.  Please be sure you are using the most recent 
firmware version.
> I downloaded the image from here
> http://arm.koji.fedoraproject.org/compose/21_RC7/Server/aarch64/iso/Fedora-S...
>
> then setup a local FTP to host it.

RC7 should be a good release to install, so I suspect is it an issue in 
the setup as mentioned above.

d.marlin
========
> Best Regards,
> Brooks
>
> On Mon, Dec 29, 2014 at 9:19 AM, David A. Marlin <[e-mail] 
> > wrote:
> On 12/27/2014 06:19 PM, Brooks Hu wrote:
> > ---------- Forwarded message ----------
> > From: *Brooks Hu* <[e-mail] <mailto:[e-mail]>>
> > Date: Friday, December 26, 2014
> > Subject: Help!Failed to find a suitable stage1 device when using
> > PXE installation.
> > To: [e-mail] <mailto:[e-mail]>
> >
> >
> > 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 directory
> > anaconda 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
> > attachments
> > 10: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.13
> >
> > Here 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-x86
>
> I 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
> > %end
> >
> > I 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
> > [e-mail]  <mailto:[e-mail]>
> > https://admin.fedoraproject.org/mailman/listinfo/arm
> _______________________________________________
> arm mailing list
> [e-mail] <mailto:[e-mail]>
> https://admin.fedoraproject.org/mailman/listinfo/arm

[Brooks Hu]

David,

I suppose the kickstart file was loaded successfully, because after
changing content in kickstart file(for example, text mode), the
installation process will reflect the change. You mentioned checking server
logs, how can i do this? I have only access to a serial console. Thanks a
lot.

Brooks

On Mon, Dec 29, 2014 at 11:56 PM, David A. Marlin 
wrote:
> On 12/29/2014 12:05 AM, Brooks Hu wrote:
>
> David,
>
> Thanks for the help.
>
> Regarding my configuration file, i just copied it from other thus some
> lines wrong, but i think they have nothing to do with this issue. This
> issue should only be related to disk partitioning.
>
> Are you certain that anaconda is finding the kickstart file (checked the
> server logs)?  There were two issues pointed out before:
> [!] Software selection (Nothing selected)
> [!] Installation Destination (No disks selected)
>
> Since it did not know which Software was selected (%packages in the
> kickstart) or the Installation Destination (specified as sda in the
> kickstart), it may not be finding the kickstart at all, or may not be able
> to successfully parse it.  Is it also possible that the initrd does not
> include all the requisite drivers to find the network or disk.  Please
> inspect the anaconda logs to see what errors are occurring.  From the shell
> window you can also verify that the network is functional (use curl to get
> the kickstart file), and check that the expected partitions are available.
>
> I tried your kickstart configuration, but the issue still exists. I
> noticed in the configuration there is a line "bootloader --location=mbr",
> does it mean you are using legacy BIOS rather than EFI? I am using EFI BIOS.
>
> I am using EFI as well.  Please be sure you are using the most recent
> firmware version.
>
> I downloaded the image from here
>
> http://arm.koji.fedoraproject.org/compose/21_RC7/Server/aarch64/iso/Fedora-S...
>
> then setup a local FTP to host it.
>
> RC7 should be a good release to install, so I suspect is it an issue in
> the setup as mentioned above.
> d.marlin
>
> Best Regards,
> Brooks
>
> On Mon, Dec 29, 2014 at 9:19 AM, David A. Marlin 
> wrote:
> > On 12/27/2014 06:19 PM, Brooks Hu wrote:
> >
> > ---------- Forwarded message ----------
> > From: *Brooks Hu* 
> > Date: Friday, December 26, 2014
> > Subject: Help!Failed to find a suitable stage1 device when using PXE
> > installation.
> > To: [e-mail]
> >
> > 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
> > directory
> > anaconda 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
> >
> > attachments
> > 10: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
> > [x] Language settings                 2) [!] Timezone settings
> >    (English (United States))                (Timezone is not set.)
> > [x] Installation source               4) [!] Software selection
> >     (ftp://192.168.1.1/F21/)                 (Nothing selected)
> > [!] Installation Destination          6) [x] Network configuration
> >     (No disks selected)                      (Wired (eth0) connected)
> > [!] 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.13
> >
> > Here 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-x86
> >
> > I 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
> > %end
> >
> > I 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 [e-mail]://admin.fedoraproject.org/mailman/listinfo/arm
> >
> > arm mailing list
> > [e-mail]
> > https://admin.fedoraproject.org/mailman/listinfo/arm

[d.marlin]

On 12/29/2014 08:10 PM, Brooks Hu wrote:
> David,
>
> I suppose the kickstart file was loaded successfully, because after 
> changing content in kickstart file(for example, text mode), the 
> installation process will reflect the change. You mentioned checking 
> server logs, how can i do this? I have only access to a serial 
> console. Thanks a lot.

When I refer to the 'server logs' I am referring to the logs on the 
DHCP/TFTP/HTTP server(s) where the PXE configuration, install tree, and 
kickstart configuration files are stored.

You can also inspect the anaconda logs on the target (Mustang) system 
from the serial console.  Anaconda uses tmux for the serial terminal 
session,

[anaconda] 1:main* 2:shell  3:log  4:storage-log  5:program-log

so you can toggle between the main screen (Ctrl-B 1) and a shell (Ctrl-B 
2), or to the log files themselves (Ctrl-B and 3, 4, or 5), much as you 
would switch screens (tabs) using 'screen' on a normal terminal window.  
"Ctrl-B [" will put the active screen in 'copy mode' so you can scroll 
up and down using the arrow keys to see more of the logs.  The <Esc> 
will exit copy mode.

d.marlin
=======
> Brooks
>
> On Mon, Dec 29, 2014 at 11:56 PM, David A. Marlin <[e-mail] 
> > wrote:
> On 12/29/2014 12:05 AM, Brooks Hu wrote:
> > David,
> >
> > Thanks for the help.
> >
> > Regarding my configuration file, i just copied it from other thus
> > some lines wrong, but i think they have nothing to do with this
> > issue. This issue should only be related to disk partitioning.
> Are you certain that anaconda is finding the kickstart file
> (checked the server logs)?  There were two issues pointed out before:
>
>   4) [!] Software selection (Nothing selected)
>   5) [!] Installation Destination (No disks selected)
>
> Since it did not know which Software was selected (%packages in
> the kickstart) or the Installation Destination (specified as sda
> in the kickstart), it may not be finding the kickstart at all, or
> may not be able to successfully parse it.  Is it also possible
> that the initrd does not include all the requisite drivers to find
> the network or disk.  Please inspect the anaconda logs to see what
> errors are occurring.  From the shell window you can also verify
> that the network is functional (use curl to get the kickstart
> file), and check that the expected partitions are available.
>
> > I tried your kickstart configuration, but the issue still exists.
> > I noticed in the configuration there is a line "bootloader
> > --location=mbr", does it mean you are using legacy BIOS rather
> > than EFI? I am using EFI BIOS.
> I am using EFI as well.  Please be sure you are using the most
> recent firmware version.
>
> > I downloaded the image from here
> > http://arm.koji.fedoraproject.org/compose/21_RC7/Server/aarch64/iso/Fedora-Server-DVD-aarch64-21.iso
> >
> > then setup a local FTP to host it.
> RC7 should be a good release to install, so I suspect is it an
> issue in the setup as mentioned above.
>
>
> d.marlin
> ========
>
> > Best Regards,
> > Brooks
> >
> > On Mon, Dec 29, 2014 at 9:19 AM, David A. Marlin
> > <[e-mail] <mailto:[e-mail]>> wrote:
> >
> >     On 12/27/2014 06:19 PM, Brooks Hu wrote:
> > >     ---------- Forwarded message ----------
> > >     From: *Brooks Hu* <[e-mail]
> > >     <mailto:[e-mail]>>
> > >     Date: Friday, December 26, 2014
> > >     Subject: Help!Failed to find a suitable stage1 device when
> > >     using PXE installation.
> > >     To: [e-mail]
> > >     <mailto:[e-mail]>
> > >
> > >
> > >     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 directory
> > >     anaconda 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 attachments
> > >     10: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.13
> > >
> > >     Here 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-x86
> >
> >     I 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
> > >     %end
> > >
> > >     I 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
> > >     [e-mail]  <mailto:[e-mail]>
> > >     https://admin.fedoraproject.org/mailman/listinfo/arm
> >     _______________________________________________
> >     arm mailing list
> >     [e-mail] <mailto:[e-mail]>
> >     https://admin.fedoraproject.org/mailman/listinfo/arm

[Dennis Gilmore]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

That is a very odd kickstart and is missing sections you need like a
location for the install tree.
http://fedoraproject.org/wiki/Anaconda/Kickstart has all the kickstart
options I suggest you look at them. you may be best off doing a manual
install and then tweaking the resulting kickstart for your use.

Dennis

On Sun, 28 Dec 2014 08:19:57 +0800
Brooks Hu  wrote:
> ---------- Forwarded message ----------
> From: *Brooks Hu* 
> Date: Friday, December 26, 2014
> Subject: Help!Failed to find a suitable stage1 device when using PXE
> installation.
> To: [e-mail]
>
> 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
> directory anaconda 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
>
> attachments
> 10: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
> [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.13
>
> Here comes the kick start config file(I modified based on a sample
> from certain website):
>
> 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
> %end
>
> I 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
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v2
>
> iQIcBAEBAgAGBQJUo6KYAAoJEH7ltONmPFDRA1cP/1duU1TZmUUNbGo/oNGG2IrB
> KDpNqh145xwogalJw4gcX3Wix0FbTn9CnROUMoGux3vc1+hVygKBtyVC+J6TaSKo
> ZtkGlnYM/PWZrkZOGXRItmIrEts7PbHmWiFF34km4XIi6tUaT72KHxkEIGW0pfwf
> nLVCn+QEVhzPsUA3kVvZwDhD0kmae8vDKrJCTwnDqaEizRod0LfMv9NGJhsBM/3N
> sKUrUZDhW4Ur4EDHTYGtVYp/+aScfHZJIG4QyVpy5AmBeefQqdH1PosbN5guzaPK
> kLgX4VsygkwKgB19S4pJ6Gnz4Axzc3DeadgKvK1p5Y7HQQfLmOwN6jsRmSxha9bm
> r5xiW2nx5fqs/CjW6dIbMhDFUsCDP59lNlGVAYnFoQTHuZGqmnbYSZnRZiaPj0v7
> TqwiK0bUwyECcHPjvxFdqYkFrQJkDvbVSlu3dEQ7J0gEZa2GAq0AC7ng6o7mODJ7
> 7MB887ey8VEAPxJTFx2chhrbP2MH2LUtDGElX/kpzqb/k43JYn1S4cs7AOQFcDfi
> 1YF4KVOi1O61hLt1GmQmRk3eG/wqRk7+zMFN1RLTSnEn/KauNgcdrNa5rZnCh0Ki
> oasJ/4Zi7XHCtZtUWpgIuAeqkTeaQZwXIN1XIeWy2bx5RLvGPu1r7ziRr+ivV2R5
> SuKKtBFPC75xj/4ZfJdd
> =XFkn
> -----END PGP SIGNATURE-----

[Brooks Hu]

Thank David, finally I found the root cause. I hada misconfigured
grub.conf, thus the kickstart file couldn't be rightly located. Now it
works as expected.

Brooks

On Wed, Dec 31, 2014 at 3:15 PM, Dennis Gilmore  wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> That is a very odd kickstart and is missing sections you need like a
> location for the install tree.
> http://fedoraproject.org/wiki/Anaconda/Kickstart has all the kickstart
> options I suggest you look at them. you may be best off doing a manual
> install and then tweaking the resulting kickstart for your use.
>
> Dennis
>
> On Sun, 28 Dec 2014 08:19:57 +0800
> Brooks Hu  wrote:
> > ---------- Forwarded message ----------
> > From: *Brooks Hu* 
> > Date: Friday, December 26, 2014
> > Subject: Help!Failed to find a suitable stage1 device when using PXE
> > installation.
> > To: [e-mail]
> >
> > 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
> > directory anaconda 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
> >
> > attachments
> > 10: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
> > [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.13
> >
> > Here comes the kick start config file(I modified based on a sample
> > from certain website):
> >
> > 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
> > %end
> >
> > I 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
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v2
>
> iQIcBAEBAgAGBQJUo6KYAAoJEH7ltONmPFDRA1cP/1duU1TZmUUNbGo/oNGG2IrB
> KDpNqh145xwogalJw4gcX3Wix0FbTn9CnROUMoGux3vc1+hVygKBtyVC+J6TaSKo
> ZtkGlnYM/PWZrkZOGXRItmIrEts7PbHmWiFF34km4XIi6tUaT72KHxkEIGW0pfwf
> nLVCn+QEVhzPsUA3kVvZwDhD0kmae8vDKrJCTwnDqaEizRod0LfMv9NGJhsBM/3N
> sKUrUZDhW4Ur4EDHTYGtVYp/+aScfHZJIG4QyVpy5AmBeefQqdH1PosbN5guzaPK
> kLgX4VsygkwKgB19S4pJ6Gnz4Axzc3DeadgKvK1p5Y7HQQfLmOwN6jsRmSxha9bm
> r5xiW2nx5fqs/CjW6dIbMhDFUsCDP59lNlGVAYnFoQTHuZGqmnbYSZnRZiaPj0v7
> TqwiK0bUwyECcHPjvxFdqYkFrQJkDvbVSlu3dEQ7J0gEZa2GAq0AC7ng6o7mODJ7
> 7MB887ey8VEAPxJTFx2chhrbP2MH2LUtDGElX/kpzqb/k43JYn1S4cs7AOQFcDfi
> 1YF4KVOi1O61hLt1GmQmRk3eG/wqRk7+zMFN1RLTSnEn/KauNgcdrNa5rZnCh0Ki
> oasJ/4Zi7XHCtZtUWpgIuAeqkTeaQZwXIN1XIeWy2bx5RLvGPu1r7ziRr+ivV2R5
> SuKKtBFPC75xj/4ZfJdd
> =XFkn
> -----END PGP SIGNATURE-----
> _______________________________________________
> arm mailing list
> [e-mail]
> https://admin.fedoraproject.org/mailman/listinfo/arm