You are not logged in.

#1 2012-05-27 18:41:00

frostyfrog
Member
From: Utah, USA
Registered: 2011-03-27
Posts: 42

Archiso-pxe-server issues

I think this is the right place to post this (I always feel like I might be posting in the wrong forum), Anyways...

So after running this command, the pxe booting seems to work, except for a few access violation problems...
command being run:

# ./archiso-pxe-server -s /tmp/atlanta/archlinux-2012.05.26-netinstall-i686.iso -i 172.16.0.1 -d eth0

Output from `tshark -i eth0`:

  0.000000      0.0.0.0 -> 255.255.255.255 DHCP 590 DHCP Discover - Transaction ID 0x4d36005a
  0.000405   172.16.0.1 -> 255.255.255.255 DHCP 356 DHCP Offer    - Transaction ID 0x4d36005a
  2.142082      0.0.0.0 -> 255.255.255.255 DHCP 590 DHCP Request  - Transaction ID 0x4d36005a
  2.199211   172.16.0.1 -> 255.255.255.255 DHCP 356 DHCP ACK      - Transaction ID 0x4d36005a
  2.203037 RealtekS_36:00:5a -> Broadcast    ARP 60 Who has 172.16.0.1?  Tell 172.16.0.182
  2.203094 CompalIn_d8:d9:48 -> RealtekS_36:00:5a ARP 42 172.16.0.1 is at 70:5a:b6:d8:d9:48
  2.203447 172.16.0.182 -> 172.16.0.1   TFTP 78 Read Request, File: syslinux/pxelinux.0, Transfer type: octet, tsize\000=0\000
  2.203658   172.16.0.1 -> 172.16.0.182 TFTP 56 Option Acknowledgement, tsize\000=26649\000
  2.203862 172.16.0.182 -> 172.16.0.1   TFTP 60 Error Code, Code: Not defined, Message: TFTP Aborted
  2.205000 172.16.0.182 -> 172.16.0.1   TFTP 83 Read Request, File: syslinux/pxelinux.0, Transfer type: octet, blksize\000=1456\000
  2.205209   172.16.0.1 -> 172.16.0.182 TFTP 57 Option Acknowledgement, blksize\000=1456\000
  2.205400 172.16.0.182 -> 172.16.0.1   TFTP 60 Acknowledgement, Block: 0
  2.205510   172.16.0.1 -> 172.16.0.182 TFTP 1502 Data Packet, Block: 1
  2.205810 172.16.0.182 -> 172.16.0.1   TFTP 60 Acknowledgement, Block: 1
  2.205876   172.16.0.1 -> 172.16.0.182 TFTP 1502 Data Packet, Block: 2
  2.206750 172.16.0.182 -> 172.16.0.1   TFTP 60 Acknowledgement, Block: 2
  2.206825   172.16.0.1 -> 172.16.0.182 TFTP 1502 Data Packet, Block: 3
  2.207735 172.16.0.182 -> 172.16.0.1   TFTP 60 Acknowledgement, Block: 3
  2.207803   172.16.0.1 -> 172.16.0.182 TFTP 1502 Data Packet, Block: 4
  2.208745 172.16.0.182 -> 172.16.0.1   TFTP 60 Acknowledgement, Block: 4
  2.208846   172.16.0.1 -> 172.16.0.182 TFTP 1502 Data Packet, Block: 5
  2.209728 172.16.0.182 -> 172.16.0.1   TFTP 60 Acknowledgement, Block: 5
  2.209798   172.16.0.1 -> 172.16.0.182 TFTP 1502 Data Packet, Block: 6
  2.210726 172.16.0.182 -> 172.16.0.1   TFTP 60 Acknowledgement, Block: 6
  2.210792   172.16.0.1 -> 172.16.0.182 TFTP 1502 Data Packet, Block: 7
  2.211722 172.16.0.182 -> 172.16.0.1   TFTP 60 Acknowledgement, Block: 7
  2.211812   172.16.0.1 -> 172.16.0.182 TFTP 1502 Data Packet, Block: 8
  2.212733 172.16.0.182 -> 172.16.0.1   TFTP 60 Acknowledgement, Block: 8
  2.212840   172.16.0.1 -> 172.16.0.182 TFTP 1502 Data Packet, Block: 9
  2.213719 172.16.0.182 -> 172.16.0.1   TFTP 60 Acknowledgement, Block: 9
  2.213823   172.16.0.1 -> 172.16.0.182 TFTP 1502 Data Packet, Block: 10
  2.214719 172.16.0.182 -> 172.16.0.1   TFTP 60 Acknowledgement, Block: 10
  2.214826   172.16.0.1 -> 172.16.0.182 TFTP 1502 Data Packet, Block: 11
  2.215709 172.16.0.182 -> 172.16.0.1   TFTP 60 Acknowledgement, Block: 11
  2.215816   172.16.0.1 -> 172.16.0.182 TFTP 1502 Data Packet, Block: 12
  2.216704 172.16.0.182 -> 172.16.0.1   TFTP 60 Acknowledgement, Block: 12
  2.216774   172.16.0.1 -> 172.16.0.182 TFTP 1502 Data Packet, Block: 13
  2.217700 172.16.0.182 -> 172.16.0.1   TFTP 60 Acknowledgement, Block: 13
  2.217806   172.16.0.1 -> 172.16.0.182 TFTP 1502 Data Packet, Block: 14
  2.218692 172.16.0.182 -> 172.16.0.1   TFTP 60 Acknowledgement, Block: 14
  2.218760   172.16.0.1 -> 172.16.0.182 TFTP 1502 Data Packet, Block: 15
  2.219690 172.16.0.182 -> 172.16.0.1   TFTP 60 Acknowledgement, Block: 15
  2.219770   172.16.0.1 -> 172.16.0.182 TFTP 1502 Data Packet, Block: 16
  2.220693 172.16.0.182 -> 172.16.0.1   TFTP 60 Acknowledgement, Block: 16
  2.220797   172.16.0.1 -> 172.16.0.182 TFTP 1502 Data Packet, Block: 17
  2.221678 172.16.0.182 -> 172.16.0.1   TFTP 60 Acknowledgement, Block: 17
  2.221767   172.16.0.1 -> 172.16.0.182 TFTP 1502 Data Packet, Block: 18
  2.222683 172.16.0.182 -> 172.16.0.1   TFTP 60 Acknowledgement, Block: 18
  2.222785   172.16.0.1 -> 172.16.0.182 TFTP 487 Data Packet, Block: 19 (last)
  2.223686 172.16.0.182 -> 172.16.0.1   TFTP 60 Acknowledgement, Block: 19
  2.327694 172.16.0.182 -> 172.16.0.1   TFTP 130 Read Request, File: syslinux/pxelinux.cfg/00020003-0004-0005-0006-000700080009, Transfer type: octet, tsize\000=0\000, blksize\000=1408\000
  2.328454   172.16.0.1 -> 172.16.0.182 TFTP 144 Error Code, Code: File not found, Message: file /tmp/archiso-pxe-server/syslinux/pxelinux.cfg/00020003-0004-0005-0006-000700080009 not found
  2.331156 172.16.0.182 -> 172.16.0.1   TFTP 114 Read Request, File: syslinux/pxelinux.cfg/01-00-e0-4c-36-00-5a, Transfer type: octet, tsize\000=0\000, blksize\000=1408\000
  2.331878   172.16.0.1 -> 172.16.0.182 TFTP 128 Error Code, Code: File not found, Message: file /tmp/archiso-pxe-server/syslinux/pxelinux.cfg/01-00-e0-4c-36-00-5a not found
  2.334585 172.16.0.182 -> 172.16.0.1   TFTP 102 Read Request, File: syslinux/pxelinux.cfg/AC1000B6, Transfer type: octet, tsize\000=0\000, blksize\000=1408\000
  2.335241   172.16.0.1 -> 172.16.0.182 TFTP 116 Error Code, Code: File not found, Message: file /tmp/archiso-pxe-server/syslinux/pxelinux.cfg/AC1000B6 not found
  2.337930 172.16.0.182 -> 172.16.0.1   TFTP 101 Read Request, File: syslinux/pxelinux.cfg/AC1000B, Transfer type: octet, tsize\000=0\000, blksize\000=1408\000
  2.338197   172.16.0.1 -> 172.16.0.182 TFTP 115 Error Code, Code: File not found, Message: file /tmp/archiso-pxe-server/syslinux/pxelinux.cfg/AC1000B not found
  2.340815 172.16.0.182 -> 172.16.0.1   TFTP 100 Read Request, File: syslinux/pxelinux.cfg/AC1000, Transfer type: octet, tsize\000=0\000, blksize\000=1408\000
  2.341115   172.16.0.1 -> 172.16.0.182 TFTP 114 Error Code, Code: File not found, Message: file /tmp/archiso-pxe-server/syslinux/pxelinux.cfg/AC1000 not found
  2.343822 172.16.0.182 -> 172.16.0.1   TFTP 99 Read Request, File: syslinux/pxelinux.cfg/AC100, Transfer type: octet, tsize\000=0\000, blksize\000=1408\000
  2.344503   172.16.0.1 -> 172.16.0.182 TFTP 113 Error Code, Code: File not found, Message: file /tmp/archiso-pxe-server/syslinux/pxelinux.cfg/AC100 not found
  2.347205 172.16.0.182 -> 172.16.0.1   TFTP 98 Read Request, File: syslinux/pxelinux.cfg/AC10, Transfer type: octet, tsize\000=0\000, blksize\000=1408\000
  2.347459   172.16.0.1 -> 172.16.0.182 TFTP 112 Error Code, Code: File not found, Message: file /tmp/archiso-pxe-server/syslinux/pxelinux.cfg/AC10 not found
  2.350150 172.16.0.182 -> 172.16.0.1   TFTP 97 Read Request, File: syslinux/pxelinux.cfg/AC1, Transfer type: octet, tsize\000=0\000, blksize\000=1408\000
  2.350406   172.16.0.1 -> 172.16.0.182 TFTP 111 Error Code, Code: File not found, Message: file /tmp/archiso-pxe-server/syslinux/pxelinux.cfg/AC1 not found
  2.353088 172.16.0.182 -> 172.16.0.1   TFTP 96 Read Request, File: syslinux/pxelinux.cfg/AC, Transfer type: octet, tsize\000=0\000, blksize\000=1408\000
  2.353371   172.16.0.1 -> 172.16.0.182 TFTP 110 Error Code, Code: File not found, Message: file /tmp/archiso-pxe-server/syslinux/pxelinux.cfg/AC not found
  2.356007 172.16.0.182 -> 172.16.0.1   TFTP 95 Read Request, File: syslinux/pxelinux.cfg/A, Transfer type: octet, tsize\000=0\000, blksize\000=1408\000
  2.356263   172.16.0.1 -> 172.16.0.182 TFTP 109 Error Code, Code: File not found, Message: file /tmp/archiso-pxe-server/syslinux/pxelinux.cfg/A not found
  2.358968 172.16.0.182 -> 172.16.0.1   TFTP 101 Read Request, File: syslinux/pxelinux.cfg/default, Transfer type: octet, tsize\000=0\000, blksize\000=1408\000
  2.359208   172.16.0.1 -> 172.16.0.182 TFTP 66 Option Acknowledgement, blksize\000=1408\000, tsize\000=74\000
  2.359433 172.16.0.182 -> 172.16.0.1   TFTP 60 Acknowledgement, Block: 0
  2.359526   172.16.0.1 -> 172.16.0.182 TFTP 120 Data Packet, Block: 1 (last)
  2.359856 172.16.0.182 -> 172.16.0.1   TFTP 60 Acknowledgement, Block: 1
  2.359874 172.16.0.182 -> 172.16.0.1   TFTP 92 Read Request, File: syslinux/archiso.cfg, Transfer type: octet, tsize\000=0\000, blksize\000=1408\000
  2.360035   172.16.0.1 -> 172.16.0.182 TFTP 67 Option Acknowledgement, blksize\000=1408\000, tsize\000=203\000
  2.360254 172.16.0.182 -> 172.16.0.1   TFTP 60 Acknowledgement, Block: 0
  2.360666   172.16.0.1 -> 172.16.0.182 TFTP 249 Data Packet, Block: 1 (last)
  2.361076 172.16.0.182 -> 172.16.0.1   TFTP 60 Acknowledgement, Block: 1
  2.361098 172.16.0.182 -> 172.16.0.1   TFTP 113 Read Request, File: syslinux/../../boot/syslinux/whichsys.c32, Transfer type: octet, tsize\000=0\000, blksize\000=1408\000
  2.361804   172.16.0.1 -> 172.16.0.182 TFTP 145 Error Code, Code: Access violation, Message: cannot access /tmp/archiso-pxe-server/syslinux/../../boot/syslinux/whichsys.c32: Permission denied
  2.361912 172.16.0.182 -> 172.16.0.1   TFTP 117 Read Request, File: syslinux/../../boot/syslinux/whichsys.c32.cbt, Transfer type: octet, tsize\000=0\000, blksize\000=1408\000
  2.363037   172.16.0.1 -> 172.16.0.182 TFTP 149 Error Code, Code: Access violation, Message: cannot access /tmp/archiso-pxe-server/syslinux/../../boot/syslinux/whichsys.c32.cbt: Permission denied
  2.363182 172.16.0.182 -> 172.16.0.1   TFTP 115 Read Request, File: syslinux/../../boot/syslinux/whichsys.c32.0, Transfer type: octet, tsize\000=0\000, blksize\000=1408\000
  2.363431   172.16.0.1 -> 172.16.0.182 TFTP 147 Error Code, Code: Access violation, Message: cannot access /tmp/archiso-pxe-server/syslinux/../../boot/syslinux/whichsys.c32.0: Permission denied
  2.363556 172.16.0.182 -> 172.16.0.1   TFTP 117 Read Request, File: syslinux/../../boot/syslinux/whichsys.c32.com, Transfer type: octet, tsize\000=0\000, blksize\000=1408\000
  2.363766   172.16.0.1 -> 172.16.0.182 TFTP 149 Error Code, Code: Access violation, Message: cannot access /tmp/archiso-pxe-server/syslinux/../../boot/syslinux/whichsys.c32.com: Permission denied
  2.363904 172.16.0.182 -> 172.16.0.1   TFTP 117 Read Request, File: syslinux/../../boot/syslinux/whichsys.c32.c32, Transfer type: octet, tsize\000=0\000, blksize\000=1408\000
  2.364129   172.16.0.1 -> 172.16.0.182 TFTP 149 Error Code, Code: Access violation, Message: cannot access /tmp/archiso-pxe-server/syslinux/../../boot/syslinux/whichsys.c32.c32: Permission denied
  7.213207 CompalIn_d8:d9:48 -> RealtekS_36:00:5a ARP 42 Who has 172.16.0.182?  Tell 172.16.0.1
  8.216593 CompalIn_d8:d9:48 -> RealtekS_36:00:5a ARP 42 Who has 172.16.0.182?  Tell 172.16.0.1
  9.219875 CompalIn_d8:d9:48 -> RealtekS_36:00:5a ARP 42 Who has 172.16.0.182?  Tell 172.16.0.1

in the end, I'm left with a prompt that says:

TFTP prefix: syslinux/
Trying to load: pxelinux.cfg/default                                                  ok
Could not find kernel image: boot/syslinux/whichsys.c32
boot: _

Anyone have an idea of how I could fix this? Thanks! smile

Output of directory from tree:

/tmp/archiso-pxe-server/
├── nbd-server.conf
└── syslinux
    ├── arch
    │   └── boot
    │       ├── i686
    │       │   ├── archiso.img
    │       │   └── vmlinuz
    │       ├── memtest
    │       └── memtest.COPYING
    ├── archiso.cfg
    ├── archiso_head.cfg
    ├── archiso_pxe.cfg
    ├── archiso_pxe_inc.cfg
    ├── archiso_sys.cfg
    ├── archiso_sys_inc.cfg
    ├── archiso_tail.cfg
    ├── cat.c32
    ├── chain.c32
    ├── cmd.c32
    ├── config.c32
    ├── cpuid.c32
    ├── cpuidtest.c32
    ├── disk.c32
    ├── dmitest.c32
    ├── elf.c32
    ├── ethersel.c32
    ├── gfxboot.c32
    ├── gpxecmd.c32
    ├── gpxelinux.0
    ├── gpxelinuxk.0
    ├── hdt
    │   ├── modalias.gz
    │   └── pciids.gz
    ├── hdt.c32
    ├── host.c32
    ├── ifcpu64.c32
    ├── ifcpu.c32
    ├── ifplop.c32
    ├── int18.com
    ├── kbdmap.c32
    ├── linux.c32
    ├── ls.c32
    ├── lua.c32
    ├── mboot.c32
    ├── memdisk
    ├── memdump.com
    ├── meminfo.c32
    ├── menu.c32
    ├── pcitest.c32
    ├── pmload.c32
    ├── poweroff.com
    ├── pwd.c32
    ├── pxechain.com
    ├── pxelinux.0
    ├── pxelinux.cfg
    │   └── default
    ├── reboot.c32
    ├── rosh.c32
    ├── sanboot.c32
    ├── sdi.c32
    ├── splash.png
    ├── sysdump.c32
    ├── syslinux.cfg
    ├── syslinux.com
    ├── ver.com
    ├── vesainfo.c32
    ├── vesamenu.c32
    ├── vpdtest.c32
    ├── whichsys.c32
    └── zzjson.c32

6 directories, 64 files

{arch32} {subtlewm}{Acer Aspire One AO532h}
{arch64} {Headless Server}
Grrr! 400 char limit sad

Offline

#2 2012-05-28 05:14:21

djgera
Developer
From: Buenos Aires - Argentina
Registered: 2008-12-24
Posts: 723
Website

Re: Archiso-pxe-server issues

Comment by: djgera on Mon, 05 Dec 2011 03:52:34 +0000

    archiso-pxe-server reaches end-of-life due recent changes in archiso. Now setup a pxeserver is trivially. See the wiki for more details.
    This script is for 2011.08.19.

See https://wiki.archlinux.org/index.php/Ar … d_newer.29

Offline

#3 2012-05-30 21:20:23

nomorewindows
Member
Registered: 2010-04-03
Posts: 3,375

Re: Archiso-pxe-server issues

This is funny.  It is loading a pxelinux.cfg/default from somewhere that is in a /syslinux directory, usually this is in /var/tftpboot which comes from your entry pointing to your pxelinux.0 according to the entry in /etc/dhcpd.conf.  When it hands off to your actual tftp server, in /etc/conf.d/tftpd, it is probably still pointing to /var/tftpboot when it needs to be pointing in the same place where /tmp/archiso-pxe-server is!  Not only that, it is trying to pull the *.c32 files not from its' current location but /.  Even if it was in /usr/lib/syslinux, it would still be trying to pull from / or /usr.  This is clearly not where these files are located.  It probably means something is wrong in the default file.  No matter where the actual files are, tftp will send the pxelinux.0 and pxelinux.cfg/default files on its' own, and the .c32 files should all be in the same place.  Wherever the actual installation is, that the pxe client will be drawing from should be pointed to in the pxelinux.cfg/default file as an argument to the kernel.  And wherever that actually is, needs to have an entry in /etc/exports to be mountable by NFS. 
Have a look at https://wiki.archlinux.org/index.php/Di … t_NFS_root, to see how this should all be working.


I may have to CONSOLE you about your usage of ridiculously easy graphical interfaces...
Look ma, no mouse.

Offline

Board footer

Powered by FluxBB