can't open '/conf/arch.conf'

[acanad]

try to load debian 9.5 from headless and it gave me this error:
vmlinuz and initrd.img (renamed from initrd) was copied from debian 9.5 netboot.

```
Select an option and press ENTER to boot/install, or F1 for Help
ready.
▒Loading, please wait...live/INITRD_N10.3.2.GZ....
/init: .: line 37: can't open '/conf/arch.conf'
[ 2.296345] Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000200
[ 2.296345]
[ 2.305438] CPU: 1 PID: 1 Comm: init Not tainted 4.9.0-7-686 #1 Debian 4.9.110-1
[ 2.312791] Hardware name: To be filled by O.E.M. To be filled by O.E.M./SHARKBAY, BIOS 4.6.5 12/11/2013
[ 2.322215] f2d21f18 c32e3132 f2ccb600 f2cfe040 c3158ac1 f2cfe040 f2ccb680 f2cfe040
[ 2.330081] f2cfe040 f2d21f64 c305c5e0 c368d010 00000200 be0509d1 00000002 f2eaade0
[ 2.337947] f2cfe040 01000154 f2ccba40 c37634c0 f51e05c0 00000000 f2d21f4c f2d21f4c
[ 2.345807] Call Trace:
[ 2.348256] [<c32e3132>] ? dump_stack+0x55/0x73
[ 2.352854] [<c3158ac1>] ? panic+0x94/0x1d8
[ 2.357107] [<c305c5e0>] ? do_exit+0xa00/0xa00
[ 2.361618] [<c305c657>] ? do_group_exit+0x37/0x90
[ 2.366478] [<c305c6c6>] ? SyS_exit_group+0x16/0x20
[ 2.371420] [<c3001a88>] ? do_fast_syscall_32+0x98/0x160
[ 2.376796] [<c359743a>] ? sysenter_past_esp+0x47/0x75
[ 2.382027] Kernel Offset: 0x2000000 from 0xc1000000 (relocation range: 0xc0000000-0xf7ffdfff)
[ 2.390594] ---[ end Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000200
[ 2.390594]

```

[NiKiZe]

You don't give much to work with,
It would be good to know which binary you are using,
also good if you posted the script you where using to get this.

With the information at hand my guess would be that you are booting in EFI mode, and are missing initrd= on the kernel line.
This is covered in the FAQ and other recent topics, for example http://forum.ipxe.org/showthread.php?tid=17447

If you are not using EFI you will have to provide more information for anyone to be able to help.

I could also guess that your initrd is broken, please run imgstat before boot, and verify the filesize between what ipxe downloaded and what is in the original file. (there have been instances of corrupted files on http server, or something else that returned data, for example a 404 page or similar)