Re: dhcp issue...

2022-05-31 Diskussionsfäden Thomas Lange
Hi Andreas,

you should check if the dhcp request from the client (which are
technical bootpc packets are received on the dhcp server.
Does the dhcp server have more than one network card? Then check
/etc/default/isc-dhcp-server if the dhcp server is listening on all
interfaces.

# tcpdump -pnlqte udp and src port bootpc and broadcast

You should also see some messages in the log of the dhcp server, for
e.g. if the server receives the request but has no free IP addresses.

In addition to tcpdump there's also dhcpdump for debugging.

-- 
best regards Thomas


mke2fs hung

2022-05-31 Diskussionsfäden Diego Zuccato

Hello all.

Seems the first install on (used) bare metal HW found a problem.
Previous tests with a VM worked OK.

During the first reinstall on a bare metal server that already contained 
an installed system, mke2fs hung.


I switched to a second console to look at the issue and found that 
stderr tmpfile for mke2fs contains "Found a dos partition table in 
/dev/sda2" and stdio tmpfile "prompts" with "Proceed anyway? (n/Y)". 
Giving a 'y' in the main console lets it proceed, but it shouldn't have 
stopped.


It seems the wipefs -af /dev/sda* before parted is not enough. Maybe a 
second wipefs is needed between parted and mkfs [*]?


IIUC it's quite a corner case (new gpt partition overlapping an old dos 
extended partition), but probably it's better to handle it.


[*] 
https://unix.stackexchange.com/questions/394984/partition-still-encrypted-with-luks-after-wipefs/394999#394999


HIH.

--
Diego Zuccato
DIFA - Dip. di Fisica e Astronomia
Servizi Informatici
Alma Mater Studiorum - Università di Bologna
V.le Berti-Pichat 6/2 - 40127 Bologna - Italy
tel.: +39 051 20 95786


Re: fai-make-nfsroot docs and missing reboot

2022-05-31 Diskussionsfäden Robert Markula

Hi Diego,

Moreover, at the end of the install, after saying there were no 
errors, FAI asked to press ENTER to reboot, but IIUC that should me 
automatic, w/o manual confirmation: docs at 
https://fai-project.org/fai-guide/#_a_id_faiflags_a_fai_flags says 
that "If no errors occurred, the client will always reboot 
automatically." and that seems not to be the case (but it's exactly 
what I wanted: no error = boot into newly installed SO w/o any 
interaction, while specifying 'reboot' seems to suggest that it 
reboots also in case of errors).


In your template (e.g. /srv/tftp/fai/pxelinux.cfg/DEFAULT.tmpl or 
whereever your tftp root lies) you have to add 'reboot' to your 
'FAI_FLAGS'. My DEFAULT.tmpl looks like this:



# generated by fai-chboot for host default with IP no IP
default fai-generated

label fai-generated

kernel vmlinuz-4.19.0-17-amd64
append initrd=initrd.img-4.19.0-17-amd64 ip=dhcp 
root=10.12.0.1:/srv/fai/nfsroot:vers=3 rootovl 
FAI_FLAGS=verbose,sshd,createvt,reboot 
FAI_CONFIG_SRC=nfs://10.12.0.1/srv/fai/config FAI_ACTION=install



'sshd' allows me to SSH into the machine during install, with 'createvt' 
I can switch to a dedicated virtual terminal during install and 'reboot' 
instructs FAI to reboot at the end of the installation process instead 
of waiting for someone to press 'enter'.



Robert


fai-make-nfsroot docs and missing reboot

2022-05-31 Diskussionsfäden Diego Zuccato

Hello all.

FAI noob here, please be patient :)

Reading man page for fai-make-nfsroot it seems 'FULL' install is the 
default. But after having troubles adding Salt repository (could not 
verify server certificate), I noticed that ca-certificates (installed 
only in FULL nfsroot) was not present. After using

fai-make-nfsroot -k -c FULL
it works. That makes me suspect that the actual default is -s .
Could the man page be improved by specifying which is the case?

Moreover, at the end of the install, after saying there were no errors, 
FAI asked to press ENTER to reboot, but IIUC that should me automatic, 
w/o manual confirmation: docs at 
https://fai-project.org/fai-guide/#_a_id_faiflags_a_fai_flags says that 
"If no errors occurred, the client will always reboot automatically." 
and that seems not to be the case (but it's exactly what I wanted: no 
error = boot into newly installed SO w/o any interaction, while 
specifying 'reboot' seems to suggest that it reboots also in case of 
errors).


Tks.

--
Diego Zuccato
DIFA - Dip. di Fisica e Astronomia
Servizi Informatici
Alma Mater Studiorum - Università di Bologna
V.le Berti-Pichat 6/2 - 40127 Bologna - Italy
tel.: +39 051 20 95786