> A network installs need about 2G ram unfortunately. You can use NFS to > provide the initramfs using > 'inst.stage2=nfs://192.168.X.X:/path/to/install.img'. Thanks for the hint Paul. I tried with the file name appended as you suggested as well as just the directory. When using the file name in the mount path, it complains that it can't mount due to not being a directory and when I remove the filename it mounts but says it can't find any suitable images. But I can see the install.img in the mount path:
[ 51.219503] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready [ 55.251825] FS-Cache: Loaded [ 55.427167] FS-Cache: Netfs 'nfs' registered for caching [ 55.523210] dracut-initqueue[881]: /lib/anaconda-lib.sh: line 71: shift: 2: shift count out of range [ 55.560399] dracut-initqueue[881]: Warning: no suitable images [ 226.962375] dracut-initqueue[881]: Warning: dracut-initqueue timeout - starting timeout scripts dracut:/# mount 172.16.16.12:/opt/rootfs/ on /run/install/repo type nfs (ro,relatime,vers=3,rsize=262144,wsize=262144,namlen=255,hard,nolock,proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=172.16.16.12,mountvers=3,mountport=20048,mountproto=udp,local_lock=all,addr=172.16.16.12) dracut:/# ls -l /run/install/repo total 478920 -rw-r--r-- 1 root root 490414080 Jun 3 2019 install.img _______________________________________________ arm mailing list -- [email protected] To unsubscribe send an email to [email protected] Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/[email protected]
