Hi, try this howto: https://help.ubuntu.com/community/UbuntuLTSP/ltsp-pnp.
Let me know if it works. Better try everything in a Virtualbox. Snapshots can be pretty handy :). Best regards Martin -----Ursprüngliche Nachricht----- Von: Larry Tucker [mailto:lat...@hotmail.com] Gesendet: Montag, 10. März 2014 21:15 An: ltsp-discuss@lists.sourceforge.net Betreff: [Ltsp-discuss] mounting /dev/nbd0 on /root failed: No such file or directory Hi happy readers of ltsp-discuss@lists.sourceforge.net After much effort to install ltsp and run a thin client for the first time, I am stuck. Short story: when I boot the thin client, it stops with a message saying Error: Socket failed: Connection refused Exiting. modprobe: module unknown not found in modules.dep mount: mounting /dev/nbd0 on /root failed: No such file or directory etc. Long Story: On the server machine, I'm running Debian Testing. # cat /etc/debian_version returns jessie/sid # uname -a returns Linux 3.10-3-amd64 #1 SMP Debian 3.10.11-1 (2013-09-10) x86_64 GNU/Linux On it, I would like to run ltsp, but not dhcp, which is already provided by a D-Link router. (The router's IP address is 192.168.0.1. I have used the router's user interface to give my server machine a static IP address: 192.168.0.202. The rest of the machines are given dynamic IP addresses by the router's DHCP service.) Therefore, following instructions at http://ubuntuforums.org/showthread.php?t=2173749, I have run # apt-get install ltsp-server dnsmasq then # ltsp-build-client --arch i386 (The thin client is a netbook computer currently running 32-bit Windows 7.) Question 1: How to undo the changes made by the ltsp-build-client command? I haven't found anything like an ltsp-remove-client command. Still following the above referenced instructions, I added "ipappend 3" to the bottom of the file at /var/lib/tftpboot/ltsp/i386/pxelinux.cfg/default. I then created a file at /etc/dnsmasq.d/ltsp.conf and put into it: enable-tftp tftp-root=/var/lib/tftpboot dhcp-range=192.168.0.0,proxy dhcp-option=vendor:PXEClient,6,2b dhcp-no-override log-dhcp pxe-prompt="Press F8 for boot menu", 3 pxe-service=x86PC, "Boot from network", /ltsp/i386/pxelinux pxe-service=x86PC, "Boot from local hard disk"polaris:/home/gregs# I then restarted the dnsmasq by running # service dnsmasq restart Per instructions at https://wiki.debian.org/LTSP/Howto, I then set up what I think is called an "NFS export" by adding to the bottom of the file at /etc/exports. a line saying /opt/ltsp *(ro,no_root_squash,async,no_subtree_check) I then restarted the NFS server by running # service nfs-kernel-server restart I then started up the then client machine, and set it in its BIOS to do a boot-from-network. It seemed to get off to a good start, saying: Intel UNDI, PXE 2.1 (build 082) Copyright (C) 1997-2000 Intel Corporation For Atheros PCIE Ethernet Controller v1.0.0.5(01/22/09) CLIENT MAC ADDR: <computer_ethernet_nic_mac_addr> GUID: <a_guid> CLIENT IP: 192.168.0.102 MASK: 255.255.255.0 DHCP IP: 192.168.0.1 PROXY IP: 192.168.0.202 GATEWAY IP: 192.168.0.1 Auto-select: Boot from network BOOT SERVER IP: 192.168.0.202 !PXE entry point found (we hope) at 9CC4:0106 via plan A UNDI code segment at 9CC4 len 2E9E UNDI data segment at 9475 len 84F0 Getting cached packet 01 02 03 My IP address seems to be C0A80066 192.168.0.102 ip=192.168.0.102:192.168.0.202:192.168.0.1:255.255.255.0 BOOTIF=<some_numbers> SYSUUID=<the_same_guid_but_with_lower_case_letters> TFTP prefix: /ltsp/i386 Trying to load: pxelinux.cfg/default ok Decompressing Linux... Parsing ELF... No relocation needed... done. Booting the kernel. Loading, please wait... While the above was appearing on the thin client, the below was appearing in the /var/log/syslog file on the server machine: dnsmasq-dhcp[5327]: 3141465108 available DHCP subnet: 192.168.0.0/255.255.255.0 dnsmasq-dhcp[5327]: 3141465108 vendor class: PXEClient:Arch:00000:UNDI:002001 dnsmasq-dhcp[5327]: 3141465108 PXE(eth1) <some_numbers> proxy dnsmasq-dhcp[5327]: 3141465108 tags: eth1 dnsmasq-dhcp[5327]: 3141465108 broadcast response dnsmasq-dhcp[5327]: 3141465108 sent size: 1 option: 53 message-type 2 dnsmasq-dhcp[5327]: 3141465108 sent size: 4 option: 54 server-identifier 192.168.0.202 dnsmasq-dhcp[5327]: 3141465108 sent size: 9 option: 60 vendor-class 50:58:45:43:6c:69:65:6e:74 dnsmasq-dhcp[5327]: 3141465108 sent size: 17 option: 97 client-machine-id 00:00:62:a2:b2:b2:0d:46:81:3d:fd:90:e6:ba... dnsmasq-dhcp[5327]: 3141465108 sent size: 91 option: 43 vendor-encap 06:01:03:08:07:80:00:01:c0:a8:00:ca:09:30... dnsmasq-dhcp[5327]: 3141465108 available DHCP subnet: 192.168.0.0/255.255.255.0 dnsmasq-dhcp[5327]: 3141465108 vendor class: PXEClient:Arch:00000:UNDI:002001 dnsmasq-dhcp[5327]: 3141465108 PXE(wlan0) 90:e6:ba:3e:f4:14 proxy dnsmasq-dhcp[5327]: 3141465108 tags: wlan0 dnsmasq-dhcp[5327]: 3141465108 broadcast response dnsmasq-dhcp[5327]: 3141465108 sent size: 1 option: 53 message-type 2 dnsmasq-dhcp[5327]: 3141465108 sent size: 4 option: 54 server-identifier 192.168.0.201 dnsmasq-dhcp[5327]: 3141465108 sent size: 9 option: 60 vendor-class 50:58:45:43:6c:69:65:6e:74 dnsmasq-dhcp[5327]: 3141465108 sent size: 17 option: 97 client-machine-id 00:00:62:a2:b2:b2:0d:46:81:3d:fd:90:e6:ba... dnsmasq-dhcp[5327]: 3141465108 sent size: 91 option: 43 vendor-encap 06:01:03:08:07:80:00:01:c0:a8:00:c9:09:30... dnsmasq-dhcp[5327]: 3141465108 available DHCP subnet: 192.168.0.0/255.255.255.0 dnsmasq-dhcp[5327]: 3141465108 vendor class: PXEClient:Arch:00000:UNDI:002001 dnsmasq-dhcp[5327]: 3141465108 available DHCP subnet: 192.168.0.0/255.255.255.0 dnsmasq-dhcp[5327]: 3141465108 vendor class: PXEClient:Arch:00000:UNDI:002001 dnsmasq-dhcp[5327]: 3141465108 available DHCP subnet: 192.168.0.0/255.255.255.0 dnsmasq-dhcp[5327]: 3141465108 vendor class: PXEClient:Arch:00000:UNDI:002001 dnsmasq-dhcp[5327]: 3141465108 PXE(eth1) 192.168.0.102 90:e6:ba:3e:f4:14 /ltsp/i386/pxelinux.0 dnsmasq-dhcp[5327]: 3141465108 tags: eth1 dnsmasq-dhcp[5327]: 3141465108 bootfile name: /ltsp/i386/pxelinux.0 dnsmasq-dhcp[5327]: 3141465108 next server: 192.168.0.202 dnsmasq-dhcp[5327]: 3141465108 broadcast response dnsmasq-dhcp[5327]: 3141465108 sent size: 1 option: 53 message-type 5 dnsmasq-dhcp[5327]: 3141465108 sent size: 4 option: 54 server-identifier 192.168.0.202 dnsmasq-dhcp[5327]: 3141465108 sent size: 9 option: 60 vendor-class 50:58:45:43:6c:69:65:6e:74 dnsmasq-dhcp[5327]: 3141465108 sent size: 17 option: 97 client-machine-id 00:00:62:a2:b2:b2:0d:46:81:3d:fd:90:e6:ba... dnsmasq-dhcp[5327]: 3141465108 sent size: 35 option: 43 vendor-encap 47:04:80:00:00:00:0a:17:03:50:72:65:73:73... dnsmasq-tftp[5327]: error 0 TFTP Aborted received from 192.168.0.102 dnsmasq-tftp[5327]: failed sending /var/lib/tftpboot/ltsp/i386/pxelinux.0 to 192.168.0.102 dnsmasq-tftp[5327]: sent /var/lib/tftpboot/ltsp/i386/pxelinux.0 to 192.168.0.102 dnsmasq-tftp[5327]: file /var/lib/tftpboot/ltsp/i386/pxelinux.cfg/0062a2b2-b20d-4681-3dfd-90e6ba3ef414 not found dnsmasq-tftp[5327]: file /var/lib/tftpboot/ltsp/i386/pxelinux.cfg/01-90-e6-ba-3e-f4-14 not found dnsmasq-tftp[5327]: file /var/lib/tftpboot/ltsp/i386/pxelinux.cfg/C0A80066 not found dnsmasq-tftp[5327]: file /var/lib/tftpboot/ltsp/i386/pxelinux.cfg/C0A8006 not found dnsmasq-tftp[5327]: file /var/lib/tftpboot/ltsp/i386/pxelinux.cfg/C0A800 not found dnsmasq-tftp[5327]: file /var/lib/tftpboot/ltsp/i386/pxelinux.cfg/C0A80 not found dnsmasq-tftp[5327]: file /var/lib/tftpboot/ltsp/i386/pxelinux.cfg/C0A8 not found dnsmasq-tftp[5327]: file /var/lib/tftpboot/ltsp/i386/pxelinux.cfg/C0A not found dnsmasq-tftp[5327]: file /var/lib/tftpboot/ltsp/i386/pxelinux.cfg/C0 not found dnsmasq-tftp[5327]: file /var/lib/tftpboot/ltsp/i386/pxelinux.cfg/C not found dnsmasq-tftp[5327]: sent /var/lib/tftpboot/ltsp/i386/pxelinux.cfg/default to 192.168.0.102 dnsmasq-tftp[5327]: sent /var/lib/tftpboot/ltsp/i386/vmlinuz-3.12-1-486 to 192.168.0.102 dnsmasq-tftp[5327]: sent /var/lib/tftpboot/ltsp/i386/initrd.img-3.12-1-486 to 192.168.0.102 But then, on the client client, just connect: Connection refused read: Connection refused read: Connection refused read: Connection refused read: Connection refused Back in /var/log/syslog, dnsmasq-dhcp[5327]: 3682134051 available DHCP subnet: 192.168.0.0/255.255.255.0 dnsmasq-dhcp[5327]: 3682134051 vendor class: udhcp 1.22.1 dnsmasq-dhcp[5327]: 3682134051 available DHCP subnet: 192.168.0.0/255.255.255.0 dnsmasq-dhcp[5327]: 3682134051 vendor class: udhcp 1.22.1 dnsmasq-dhcp[5327]: 3682134051 available DHCP subnet: 192.168.0.0/255.255.255.0 dnsmasq-dhcp[5327]: 3682134051 vendor class: udhcp 1.22.1 dnsmasq-dhcp[5327]: 3682134051 available DHCP subnet: 192.168.0.0/255.255.255.0 dnsmasq-dhcp[5327]: 3682134051 vendor class: udhcp 1.22.1 The "read: Connection refused" messages were repeated about once or twice per second until, after a minute or so, came NFS over TCP not available from 192.168.0.1 connect: Connection refused read: Connection refused read: Connection refused read: Connection refused read: Connection refused and so on. It struck me as odd that the IP address in the "NFS over TCP not available" message was that of the router and not that of the computer onwhich I'm trying to run ltsp etc. This had me stumped for a while until I found http://sourceforge.net/p/ltsp/mailman/ltsp-discuss/?viewmonth=201401&viewday= saying "Tell Debian to use NBD instead of NFS." So, following also a suggestion at http://lists.alioth.debian.org/pipermail/pkg-ltsp-devel/2009-March/001759.html, I edited the file at /opt/ltsp/i386/etc/ltsp/update-kernels.conf to de-commend the line PXELINUX_DEFAULT=menu and then ran # chroot /opt/ltsp/i386 /usr/share/ltsp/update-kernels and # ltsp-update-kernels Then I ran # ltsp-update-image --config-nbd The response to which ended by saying Updating /var/lib/tftpboot directories for chroot: i386 Created /etc/nbd-server/conf.d/swap.conf Created /etc/nbd-server/conf.d/ltsp_i386.conf nbd-server. Where /etc/nbd-server/conf.d/swap.conf has this in it: [swap] exportname = /tmp/nbd-swap/%s prerun = nbdswapd %s postrun = rm -f %s authfile = /etc/ltsp/nbd-server.allow and /etc/nbd-server/conf.d/ltsp_i386.conf has this in it: [/opt/ltsp/i386] exportname = /opt/ltsp/images/i386.img readonly = true authfile = /etc/ltsp/nbd-server.allow With those files in place, I was able to run # service nbd-server start without getting a message saying ** (process:5623): WARNING **: Could not parse config file: The config file does not specify any exports ** Message: No configured exports; quitting. nbd-server. Again, I booted the client computer. This time, I was presented with a menu from which I chose "LTSP, using NBD" (the menu, it seems is derived from the file on the server machine at /var/lib/tftpboot/ltsp/i386/pxelinux.cfg/default) The subsequent result was much the same except, instead of getting an bunch of "read: Connection refused" messages, I get Error: Socket failed: Connection refused Exiting. modprobe: module unknown not found in modules.dep mount: mounting /dev/nbd0 on /root failed: No such file or directory /scripts/inti-bottom/ltsp: line 27: panic: not found chroot: can't execute '/usr/bin/test/': No such file or directory mount: mounting /root on /rofs failed: Invalid argument modprobe: module overlayfs not found in modules.dep [ 5.413948] aufs test_add:264:exe[214]: unsuppported filesystem, /rofs (rootfs ) mount: mounting aufs on /root failed: Invalid argument mount: mounting /rofs on /root/rofs failed: Invalid argument mount: mounting /dev on /root/dev failed: No such file or directory Target filesystem doesn't have requested /sbin/initi-ltsp. No init found. Try passing init= bootarg. modprobe: module ehci-orion not found in modules.dep BusyBox v1.22.1 (Debian 1:1.22.0-4) built-in shell (ash) Enter 'help' for a list of built-in commands. /bin/sh: can't access tty: job control turned off (initramfs)_ I'll add that at that (initramfs)_ prompt, I am able to run telnet 192.168.0.202 10809 and get and get a response: NBDMAGICIHAVEOPT So it doesn't look like the port being used by NBD is being blocked. Why then is "Connection refused"? How I can resolve this issue? Thanks for any pointers you can provide. Best regards, ------------------------------------------------------------------------------ Learn Graph Databases - Download FREE O'Reilly Book "Graph Databases" is the definitive new guide to graph databases and their applications. Written by three acclaimed leaders in the field, this first edition is now available. Download your free book today! http://p.sf.net/sfu/13534_NeoTech _____________________________________________________________________ Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto: https://lists.sourceforge.net/lists/listinfo/ltsp-discuss For additional LTSP help, try #ltsp channel on irc.freenode.net ------------------------------------------------------------------------------ Learn Graph Databases - Download FREE O'Reilly Book "Graph Databases" is the definitive new guide to graph databases and their applications. Written by three acclaimed leaders in the field, this first edition is now available. Download your free book today! http://p.sf.net/sfu/13534_NeoTech _____________________________________________________________________ Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto: https://lists.sourceforge.net/lists/listinfo/ltsp-discuss For additional LTSP help, try #ltsp channel on irc.freenode.net
