florifreeman
Posts: 16
Joined: Fri Dec 06, 2019 7:57 am

[solved] PiServer via terminal

Mon Dec 09, 2019 9:19 am

Hi folks!

I have another question to PiServer.

Is it possible to control the program via terminal without using the GUI?

Could come in handy for a Deb/Ubuntu server installation i run without desktop.

Regards,
Freeman
Last edited by florifreeman on Tue Jan 28, 2020 10:50 am, edited 1 time in total.

incognitum
Posts: 476
Joined: Tue Oct 30, 2018 3:34 pm

Re: PiServer via terminal

Mon Dec 09, 2019 6:45 pm

No.

Although you do can use the GUI remotely (ssh's X11 forwarding, broadway, vnc, etc.)

florifreeman
Posts: 16
Joined: Fri Dec 06, 2019 7:57 am

Re: PiServer via terminal

Tue Dec 10, 2019 7:22 am

Mh too bad...using remote desktop in a Linux server environment is very uncommon and not always possible (that´s why they call it headless).

incognitum
Posts: 476
Joined: Tue Oct 30, 2018 3:34 pm

Re: PiServer via terminal

Tue Dec 10, 2019 12:08 pm

florifreeman wrote:
Tue Dec 10, 2019 7:22 am
Mh too bad...using remote desktop in a Linux server environment is very uncommon and not always possible (that´s why they call it headless).
Think you are making it sound more dramatic then it is...

One still does not need to install a full desktop environment on the server.
If you are running Linux on the client as well, all it takes is SSH'ing to the server with "ssh -X pi@<server ip>" and typing "sudo -E piserver"
SSH's X11 forwarding takes care of the rest, and will only display the piserver GUI on the client.

Image

florifreeman
Posts: 16
Joined: Fri Dec 06, 2019 7:57 am

Re: PiServer via terminal

Tue Dec 10, 2019 1:23 pm

Hi!

Thx for the advice, i think this could be an option to use the PiServer.

EDIT: Now I have the warning that STP (spanning tree prot.) is enabled. Is this a serious problem? I cant find the Raspi i want to boot up.

EDIT2: I found out that my PiServer is in a different ip adress range than my Raspi. Any chance that they find each other?

incognitum
Posts: 476
Joined: Tue Oct 30, 2018 3:34 pm

Re: PiServer via terminal

Tue Dec 10, 2019 4:13 pm

florifreeman wrote:
Tue Dec 10, 2019 1:23 pm
EDIT: Now I have the warning that STP (spanning tree prot.) is enabled. Is this a serious problem? I cant find the Raspi i want to boot up.
Yes, disable it on your Ethernet switch.
Or at least set it to the portfast (Cisco) or RSTP (others) variant.

Otherwise it will take 30 seconds after the port on the switch goes up before it lets through traffic while it is testing for network loops first.
And the Pi bootcode may not wait that long.
EDIT2: I found out that my PiServer is in a different ip adress range than my Raspi. Any chance that they find each other?
How different?
Note that if netmask is 255.255.255.0 the first 3 digits should be the same to be in the same subnet.
But if it's 255.255.0.0 it is ok if only the first 2 digits are the same.

Letting a Pi in a different subnet communicate through the gateway is possible if it's a more recent Pi (Pi 3+, Pi 4).
If those subnets live in different VLANs, it will be necessary to setup DHCP relaying to the Piserver IP though.
(Usually a matter of adding "ip helper-address 1.2.3.4" to the configuration of the affected VLANs on your L3 switch. Where 1.2.3.4 is Piserver IP, if you are running that as standalone DHCP server. Don't forgot to add the IPs of other DHCP servers as well, if you are running in proxy dhcp mode)

florifreeman
Posts: 16
Joined: Fri Dec 06, 2019 7:57 am

Re: PiServer via terminal

Wed Dec 11, 2019 6:56 am

EDIT: "And the Pi bootcode may not wait that long"

- Would it be possible to modify the bootcode to wait longer? My admin is not eager to deactivate STP.


Thank you very much for your detailed explanation!

I will take another look at it and try it out.
Last edited by florifreeman on Thu Dec 12, 2019 9:24 am, edited 1 time in total.

incognitum
Posts: 476
Joined: Tue Oct 30, 2018 3:34 pm

Re: PiServer via terminal

Wed Dec 11, 2019 11:36 am

florifreeman wrote:
Wed Dec 11, 2019 6:56 am
- Would it be possible to modify the bootcode to wait longer? My admin is not eager to deactivate STP.
Either need a Pi 4 or stick a SD card with only a newer version of bootcode.bin in a Pi 3 (and keep the SD card inserted at all times, as the bootcode in the chip is ROM and not flashable) if you want it to wait longer.
Be prepared for 1 minute delays at boot. (30 second delay can both occur when the bootcode wants to start using the network, and when the Linux kernel wants to start using it).


Note that on most managed switches STP can be configured on a per-port basis.
So I would still try to convince your admin to change ports connecting to Pi (and other computers that are network booted, as they have same problem) to a different setting.
RSTP/Portfast still protects against loops, but does not wait that long.

florifreeman
Posts: 16
Joined: Fri Dec 06, 2019 7:57 am

Re: PiServer via terminal

Mon Jan 20, 2020 10:22 am

Hi there,

putting the PiServer and the clients into the same network works, i can find the Raspi very fast. Installation of Raspbian runs through.

Now my problem is that i cant boot into desktop (strange: in my other LAN at my workplace it wasn´t a problem at all)

End of boot screen shows:

[end kernel panic -not syncing: VFS: unable to mount root fs on unknown-block(2,)]

I tried to add "vers=3" to /boot/cmdline.txt but that didn´t help (there was already a v3 at the end btw)

The IP Adress of my Server is fix and doesn´t change. He has to act as a DHCP Proxy.

Any ideas??

Regards Freeman

incognitum
Posts: 476
Joined: Tue Oct 30, 2018 3:34 pm

Re: PiServer via terminal

Mon Jan 20, 2020 11:19 am

If you have a serial console cable you may want to capture and check the output above the kernel panic.

Also double check in the output that the Linux kernel is receiving a proper DHCP lease.
(It does a new request, so the lease it receives can be different then what was used during the network boot done by firmware)

And of course, double check that you do not have any iptables/nft or other firewall rules active on your server or Ethernet switch (if it is L3) that can block NFS traffic.
Can you mount the nfs share manually from another server in the network?

florifreeman
Posts: 16
Joined: Fri Dec 06, 2019 7:57 am

Re: PiServer via terminal

Mon Jan 20, 2020 12:00 pm

STP Protocol is still enabled. Could that be a problem when booting via PXE?

EDIT: Gave it another try now i get the following error:

"IP-Config: Gateway not on directly connected network" (?)

EDIT2: After waiting i get the same error as mentioned above.

incognitum wrote:
Mon Jan 20, 2020 11:19 am
If you have a serial console cable you may want to capture and check the output above the kernel panic.

Also double check in the output that the Linux kernel is receiving a proper DHCP lease.
(It does a new request, so the lease it receives can be different then what was used during the network boot done by firmware)

And of course, double check that you do not have any iptables/nft or other firewall rules active on your server or Ethernet switch (if it is L3) that can block NFS traffic.
Can you mount the nfs share manually from another server in the network?

incognitum
Posts: 476
Joined: Tue Oct 30, 2018 3:34 pm

Re: PiServer via terminal

Tue Jan 21, 2020 9:09 am

florifreeman wrote:
Mon Jan 20, 2020 12:00 pm
"IP-Config: Gateway not on directly connected network" (?)
What IP/netmask/gateway does it report receiving through dhcp?
Gateway IP must be inside same subnet as Pi. So if client IP is say 10.1.2.5 and netmask is 255.255.255.0, gateway IP must be between 10.1.2.1 and 10.1.2.254 (do not use first and last IP of subnet, so not .0 or .255 in case of netmask 255.255.255.0)

florifreeman
Posts: 16
Joined: Fri Dec 06, 2019 7:57 am

Re: PiServer via terminal

Tue Jan 21, 2020 10:35 am

Both the server and the Raspi are in the same subnet called 192.168.0.xxx

I restarted the Raspi serveral times but the message about the gateway just came once. Still not booting though.

I can´t see any IP adress during boot so iam not sure which IP it gets. How can i find out?
incognitum wrote:
Tue Jan 21, 2020 9:09 am
florifreeman wrote:
Mon Jan 20, 2020 12:00 pm
"IP-Config: Gateway not on directly connected network" (?)
What IP/netmask/gateway does it report receiving through dhcp?
Gateway IP must be inside same subnet as Pi. So if client IP is say 10.1.2.5 and netmask is 255.255.255.0, gateway IP must be between 10.1.2.1 and 10.1.2.254 (do not use first and last IP of subnet, so not .0 or .255 in case of netmask 255.255.255.0)

incognitum
Posts: 476
Joined: Tue Oct 30, 2018 3:34 pm

Re: PiServer via terminal

Tue Jan 21, 2020 12:59 pm

florifreeman wrote:
Tue Jan 21, 2020 10:35 am
I can´t see any IP adress during boot so iam not sure which IP it gets. How can i find out?
Kernel should print that to console, among the lines of:

Code: Select all

IP-config: Got DHCP answer from 1.2.3.4, my address is 1.2.3.5
IP-config: complete
    device: eth0, hwaddr: xx:xx:xx:xx:xx, ipaddr=1.2.3.5, mask=255.255.255.0, gw=1.2.3.1
You really need a serial console cable to capture such details though as the text scrolls too fast to notice on screen. (like: https://www.aliexpress.com/item/32345829369.html )

florifreeman
Posts: 16
Joined: Fri Dec 06, 2019 7:57 am

Re: PiServer via terminal

Tue Jan 21, 2020 1:49 pm

Hi there!

That sounds good, i need that cable first.

Is there any chance to see what happened on the server maybe in a log file or so?

Regards

EDIT: I did run syslog on my server:

Jan 21 14:18:05 piserver01 dhcpd[1087]: DHCPOFFER on 192.168.0.221 to b8:27:eb:bc:93:85 via ens160
Jan 21 14:18:05 piserver01 dnsmasq-dhcp[1269]: 653460281 broadcast response
Jan 21 14:18:05 piserver01 dnsmasq-dhcp[1269]: 653460281 sent size: 1 option: 53 message-type 2
Jan 21 14:18:05 piserver01 dnsmasq-dhcp[1269]: 653460281 sent size: 4 option: 54 server-identifier 192.168.0.68
Jan 21 14:18:05 piserver01 dnsmasq-dhcp[1269]: 653460281 sent size: 9 option: 60 vendor-class 50:58:45:43:6c:69:65:6e:74
Jan 21 14:18:05 piserver01 dnsmasq-dhcp[1269]: 653460281 sent size: 17 option: 97 client-machine-id 00:44:44:44:44:44:44:44:44:44:44:44:44:44...
Jan 21 14:18:05 piserver01 dnsmasq-dhcp[1269]: 653460281 sent size: 32 option: 43 vendor-encap 06:01:03:0a:04:00:50:58:45:09:14:00:00:11...
Jan 21 14:18:05 piserver01 dnsmasq-tftp[1269]: sent /var/lib/piserver/tftproot/b8-27-eb-bc-93-85/bootcode.bin to 192.168.0.221
Jan 21 14:18:05 piserver01 dnsmasq-tftp[1269]: file /var/lib/piserver/tftproot/b8-27-eb-bc-93-85/bootsig.bin not found
Jan 21 14:18:05 piserver01 dhcpd[1087]: DHCPDISCOVER from b8:27:eb:bc:93:85 via ens160
Jan 21 14:18:05 piserver01 dhcpd[1087]: DHCPOFFER on 192.168.0.221 to b8:27:eb:bc:93:85 via ens160
Jan 21 14:18:05 piserver01 dnsmasq-dhcp[1269]: 653460281 available DHCP subnet: 192.168.0.68/255.255.255.0
Jan 21 14:18:05 piserver01 dnsmasq-dhcp[1269]: 653460281 vendor class: PXEClient:Arch:00000:UNDI:002001
Jan 21 14:18:05 piserver01 dnsmasq-dhcp[1269]: 653460281 PXE(ens160) b8:27:eb:bc:93:85 proxy
Jan 21 14:18:05 piserver01 dnsmasq-dhcp[1269]: 653460281 tags: piserver, known, ens160
Jan 21 14:18:05 piserver01 dnsmasq-dhcp[1269]: 653460281 reply delay: 1
Jan 21 14:18:06 piserver01 dnsmasq-dhcp[1269]: 653460281 broadcast response
Jan 21 14:18:06 piserver01 dnsmasq-dhcp[1269]: 653460281 sent size: 1 option: 53 message-type 2
Jan 21 14:18:06 piserver01 dnsmasq-dhcp[1269]: 653460281 sent size: 4 option: 54 server-identifier 192.168.0.68
Jan 21 14:18:06 piserver01 dnsmasq-dhcp[1269]: 653460281 sent size: 9 option: 60 vendor-class 50:58:45:43:6c:69:65:6e:74
Jan 21 14:18:06 piserver01 dnsmasq-dhcp[1269]: 653460281 sent size: 17 option: 97 client-machine-id 00:85:93:bc:f8:85:93:bc:f8:85:93:bc:f8:85...
Jan 21 14:18:06 piserver01 dnsmasq-dhcp[1269]: 653460281 sent size: 32 option: 43 vendor-encap 06:01:03:0a:04:00:50:58:45:09:14:00:00:11...
Jan 21 14:18:06 piserver01 dnsmasq-tftp[1269]: file /var/lib/piserver/tftproot/b8-27-eb-bc-93-85/f8bc9385/start.elf not found
Jan 21 14:18:06 piserver01 dnsmasq-tftp[1269]: file /var/lib/piserver/tftproot/b8-27-eb-bc-93-85/autoboot.txt not found
Jan 21 14:18:06 piserver01 dnsmasq-tftp[1269]: sent /var/lib/piserver/tftproot/b8-27-eb-bc-93-85/config.txt to 192.168.0.221
Jan 21 14:18:06 piserver01 dnsmasq-tftp[1269]: file /var/lib/piserver/tftproot/b8-27-eb-bc-93-85/recovery.elf not found
Jan 21 14:18:07 piserver01 dnsmasq-tftp[1269]: sent /var/lib/piserver/tftproot/b8-27-eb-bc-93-85/start.elf to 192.168.0.221
Jan 21 14:18:07 piserver01 dnsmasq-tftp[1269]: sent /var/lib/piserver/tftproot/b8-27-eb-bc-93-85/fixup.dat to 192.168.0.221
Jan 21 14:18:07 piserver01 dnsmasq-tftp[1269]: file /var/lib/piserver/tftproot/b8-27-eb-bc-93-85/recovery.elf not found
Jan 21 14:18:07 piserver01 dnsmasq-tftp[1269]: sent /var/lib/piserver/tftproot/b8-27-eb-bc-93-85/config.txt to 192.168.0.221
Jan 21 14:18:07 piserver01 dnsmasq-tftp[1269]: file /var/lib/piserver/tftproot/b8-27-eb-bc-93-85/dt-blob.bin not found
Jan 21 14:18:07 piserver01 dnsmasq-tftp[1269]: file /var/lib/piserver/tftproot/b8-27-eb-bc-93-85/recovery.elf not found
Jan 21 14:18:07 piserver01 dnsmasq-tftp[1269]: sent /var/lib/piserver/tftproot/b8-27-eb-bc-93-85/config.txt to 192.168.0.221
Jan 21 14:18:08 piserver01 dnsmasq-tftp[1269]: file /var/lib/piserver/tftproot/b8-27-eb-bc-93-85/bootcfg.txt not found
Jan 21 14:18:08 piserver01 dnsmasq-tftp[1269]: sent /var/lib/piserver/tftproot/b8-27-eb-bc-93-85/cmdline.txt to 192.168.0.221
Jan 21 14:18:08 piserver01 dnsmasq-tftp[1269]: sent /var/lib/piserver/tftproot/b8-27-eb-bc-93-85/bcm2710-rpi-3-b.dtb to 192.168.0.221
Jan 21 14:18:08 piserver01 dnsmasq-tftp[1269]: sent /var/lib/piserver/tftproot/b8-27-eb-bc-93-85/config.txt to 192.168.0.221
Jan 21 14:18:08 piserver01 dnsmasq-tftp[1269]: sent /var/lib/piserver/tftproot/b8-27-eb-bc-93-85/overlays/pi3-disable-wifi.dtbo to 192.168.0.221
Jan 21 14:18:08 piserver01 dnsmasq-tftp[1269]: sent /var/lib/piserver/tftproot/b8-27-eb-bc-93-85/overlays/sdtweak.dtbo to 192.168.0.221
Jan 21 14:18:10 piserver01 dnsmasq-tftp[1269]: file /var/lib/piserver/tftproot/b8-27-eb-bc-93-85/recovery8.img not found
Jan 21 14:18:10 piserver01 dnsmasq-tftp[1269]: file /var/lib/piserver/tftproot/b8-27-eb-bc-93-85/recovery8-32.img not found
Jan 21 14:18:10 piserver01 dnsmasq-tftp[1269]: file /var/lib/piserver/tftproot/b8-27-eb-bc-93-85/recovery7.img not found
Jan 21 14:18:10 piserver01 dnsmasq-tftp[1269]: file /var/lib/piserver/tftproot/b8-27-eb-bc-93-85/recovery.img not found
Jan 21 14:18:10 piserver01 dnsmasq-tftp[1269]: error 0 Early terminate received from 192.168.0.221
Jan 21 14:18:10 piserver01 dnsmasq-tftp[1269]: failed sending /var/lib/piserver/tftproot/b8-27-eb-bc-93-85/kernel8.img to 192.168.0.221
Jan 21 14:18:10 piserver01 dnsmasq-tftp[1269]: file /var/lib/piserver/tftproot/b8-27-eb-bc-93-85/kernel8-32.img not found
Jan 21 14:18:10 piserver01 dnsmasq-tftp[1269]: error 0 Early terminate received from 192.168.0.221
Jan 21 14:18:10 piserver01 dnsmasq-tftp[1269]: failed sending /var/lib/piserver/tftproot/b8-27-eb-bc-93-85/kernel7.img to 192.168.0.221
Jan 21 14:18:10 piserver01 dnsmasq-tftp[1269]: file /var/lib/piserver/tftproot/b8-27-eb-bc-93-85/armstub8-32.bin not found
Jan 21 14:18:12 piserver01 dnsmasq-tftp[1269]: sent /var/lib/piserver/tftproot/b8-27-eb-bc-93-85/kernel7.img to 192.168.0.221
Jan 21 14:18:17 piserver01 dhcpd[1087]: DHCPDISCOVER from b8:27:eb:bc:93:85 via ens160
Jan 21 14:18:17 piserver01 dhcpd[1087]: DHCPOFFER on 192.168.0.221 to b8:27:eb:bc:93:85 via ens160
Jan 21 14:18:17 piserver01 dnsmasq-dhcp[1269]: 802546463 available DHCP subnet: 192.168.0.68/255.255.255.0
Jan 21 14:18:18 piserver01 dnsmasq-dhcp[1269]: 802546463 available DHCP subnet: 192.168.0.68/255.255.255.0
Jan 21 14:18:18 piserver01 dhcpd[1087]: Wrote 0 class decls to leases file.
Jan 21 14:18:18 piserver01 dhcpd[1087]: Wrote 22 leases to leases file.
Jan 21 14:18:18 piserver01 dhcpd[1087]: DHCPREQUEST for 192.168.0.221 (192.168.0.68) from b8:27:eb:bc:93:85 via ens160
Jan 21 14:18:18 piserver01 dhcpd[1087]: DHCPACK on 192.168.0.221 to b8:27:eb:bc:93:85 via ens160
Jan 21 14:18:30 piserver01 dhcpd[1087]: DHCPINFORM from 192.168.0.222 via ens160: not authoritative for subnet 192.168.0.0
Jan 21 14:18:30 piserver01 dnsmasq-dhcp[1269]: 2807178235 available DHCP subnet: 192.168.0.68/255.255.255.0
Jan 21 14:18:30 piserver01 dnsmasq-dhcp[1269]: 2807178235 vendor class: MSFT 5.0
Jan 21 14:18:30 piserver01 dnsmasq-dhcp[1269]: 2807178235 client provides name: xa201


I can see "not authoritative for subnet 192.168.0.0" and file /var/lib/piserver/tftproot/b8-27-eb-bc-93-85/XXXXXXXX not found??


incognitum wrote:
Tue Jan 21, 2020 12:59 pm
florifreeman wrote:
Tue Jan 21, 2020 10:35 am
I can´t see any IP adress during boot so iam not sure which IP it gets. How can i find out?
Kernel should print that to console, among the lines of:

Code: Select all

IP-config: Got DHCP answer from 1.2.3.4, my address is 1.2.3.5
IP-config: complete
    device: eth0, hwaddr: xx:xx:xx:xx:xx, ipaddr=1.2.3.5, mask=255.255.255.0, gw=1.2.3.1
You really need a serial console cable to capture such details though as the text scrolls too fast to notice on screen. (like: https://www.aliexpress.com/item/32345829369.html )

incognitum
Posts: 476
Joined: Tue Oct 30, 2018 3:34 pm

Re: PiServer via terminal

Tue Jan 21, 2020 5:47 pm

florifreeman wrote:
Tue Jan 21, 2020 1:49 pm
dhcpd[1087]
You also have (ISC?) dhcpd running on the same server?!

florifreeman
Posts: 16
Joined: Fri Dec 06, 2019 7:57 am

Re: PiServer via terminal

Wed Jan 22, 2020 6:44 am

The server is a fresh clean install of Ubuntu Server. I modified nothing just installed PiServer with all its packets.

I removed isc-dhcpd manually from the system now.

Still no luck: "Jan 22 12:48:09 piserver01 dnsmasq-tftp[1269]: error 0 Early terminate received from 192.168.0.221"

EDIT: Adding "modprobe.blacklist=bcm2835_v4l2 pxe" to cmdline.txt in the raspbian light image doesn´t help.


incognitum wrote:
Tue Jan 21, 2020 5:47 pm
florifreeman wrote:
Tue Jan 21, 2020 1:49 pm
dhcpd[1087]
You also have (ISC?) dhcpd running on the same server?!

incognitum
Posts: 476
Joined: Tue Oct 30, 2018 3:34 pm

Re: PiServer via terminal

Thu Jan 23, 2020 12:45 pm

florifreeman wrote:
Wed Jan 22, 2020 6:44 am
The server is a fresh clean install of Ubuntu Server.
I recall Ubuntu server offers a list of server roles to install during install.
Any chance you could have accidentally selected "DHCP daemon" when you meant "DHCP client" there?

If there may be more servers in your network that could have this problem, you may want to run software like odhcploc to scan for other rogue DHCP servers.
Still no luck: "Jan 22 12:48:09 piserver01 dnsmasq-tftp[1269]: error 0 Early terminate received from 192.168.0.221"
Ignore that.
There is unlikely to be anything wrong with tftp, or it would not get to the stage where it boots the kernel.

It is likely to be either:

- Something wrong with the DHCP lease received when the Linux kernel does DHCP.

- Something wrong with the NFS part.
As mentioned before. Try if you can mount the share on different server in same network ("sudo mount 1.2.3.4:/var/lib/piserver/os /mnt" where 1.2.3.4 is piserver IP)

florifreeman
Posts: 16
Joined: Fri Dec 06, 2019 7:57 am

Re: PiServer via terminal

Thu Jan 23, 2020 3:37 pm

Hi there!

I tried to mount the shared folder:

sudo mount 192.168.0.XX:/var/lib/piserver/os /mnt

Now it shows => "mount.nfs: requested NFS version or transport protocol is not supported" (??)


incognitum wrote:
Thu Jan 23, 2020 12:45 pm
florifreeman wrote:
Wed Jan 22, 2020 6:44 am
The server is a fresh clean install of Ubuntu Server.
I recall Ubuntu server offers a list of server roles to install during install.
Any chance you could have accidentally selected "DHCP daemon" when you meant "DHCP client" there?

If there may be more servers in your network that could have this problem, you may want to run software like odhcploc to scan for other rogue DHCP servers.
Still no luck: "Jan 22 12:48:09 piserver01 dnsmasq-tftp[1269]: error 0 Early terminate received from 192.168.0.221"
Ignore that.
There is unlikely to be anything wrong with tftp, or it would not get to the stage where it boots the kernel.

It is likely to be either:

- Something wrong with the DHCP lease received when the Linux kernel does DHCP.

- Something wrong with the NFS part.
As mentioned before. Try if you can mount the share on different server in same network ("sudo mount 1.2.3.4:/var/lib/piserver/os /mnt" where 1.2.3.4 is piserver IP)

incognitum
Posts: 476
Joined: Tue Oct 30, 2018 3:34 pm

Re: PiServer via terminal

Thu Jan 23, 2020 3:55 pm

florifreeman wrote:
Thu Jan 23, 2020 3:37 pm
Now it shows => "mount.nfs: requested NFS version or transport protocol is not supported" (??)
NFS server did not throw any errors on startup?
("systemctl status nfs-kernel-server" on piserver server)

florifreeman
Posts: 16
Joined: Fri Dec 06, 2019 7:57 am

Re: PiServer via terminal

Fri Jan 24, 2020 8:34 am

Hi i found the problem:

NFS was looking for /images folder but that didn´t exist. After creating it nfs-kernel-server started.

The client is booting up:

The desktop environment (raspbian full) lacks all graphics. No background and icons show a red cross. Is this a graphics bug? Or is the raspbian image corrupt?

EDIT: I tried the normal raspbian image and it works!

Thank you very much for your help!

incognitum wrote:
Thu Jan 23, 2020 3:55 pm
florifreeman wrote:
Thu Jan 23, 2020 3:37 pm
Now it shows => "mount.nfs: requested NFS version or transport protocol is not supported" (??)
NFS server did not throw any errors on startup?
("systemctl status nfs-kernel-server" on piserver server)

incognitum
Posts: 476
Joined: Tue Oct 30, 2018 3:34 pm

Re: PiServer via terminal

Fri Jan 24, 2020 11:14 am

florifreeman wrote:
Fri Jan 24, 2020 8:34 am
Hi i found the problem:

NFS was looking for /images folder but that didn´t exist.
The only folder Piserver adds to /etc/exports is /var/lib/piserver/os
So I do am curious where that /images comes from...

It really was a clean Ubuntu installation, and you did not install and attempt to remove again software like FOG (which does use isc dhcp and does has a /images)?

florifreeman
Posts: 16
Joined: Fri Dec 06, 2019 7:57 am

Re: PiServer via terminal

Fri Jan 24, 2020 11:54 am

Hi!

I can´t tell you. I found some FOG installation ressources and a FOG user, but it really was just a clean installation w/o any software installation.

Another things I don´t understand:

- After upgrading the image (raspbian) it shows white boxes and red crosses; no desktop background (like something went wrong with graphics)?
It still happens even after removing an image and reinstalling.

mv: cannot stat '/var/lib/piserver/os/Raspbian_Full-2019-09-26/etc/ld.so.preload': No such file or directory
mount: /var/lib/piserver/os/Raspbian_Full-2019-09-26/proc: none already mounted on /var/lib/piserver/os/Raspbian_Full-2019-09-26/proc.

- I cant remove the "raspbian" image (i did this by hand in the "os" folder, but it still shows up in PiServer...)

incognitum wrote:
Fri Jan 24, 2020 11:14 am
florifreeman wrote:
Fri Jan 24, 2020 8:34 am
Hi i found the problem:

NFS was looking for /images folder but that didn´t exist.
The only folder Piserver adds to /etc/exports is /var/lib/piserver/os
So I do am curious where that /images comes from...

It really was a clean Ubuntu installation, and you did not install and attempt to remove again software like FOG (which does use isc dhcp and does has a /images)?

Return to “Staffroom, classroom and projects”