Re: mke2fs hung
Tks Robert.
The issue I had was a bit less extreme :)
md and lvm devices are another can of worms, but luckily I don't use 'em
often :)
BYtE,
Diego
Il 01/06/2022 12:31, Robert Markula ha scritto:
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.
In the past I stumbled across that issue as well. So I created a hook
'mountdisks.DANGEROUS' that includes, among others, the following lines:
# Clear any MD arrays:
if [ $(grep md0 /proc/mdstat) ]; then
mdadm --stop /dev/md0
fi
if [ $(grep md1 /proc/mdstat) ]; then
mdadm --stop /dev/md1
fi
if [ $(grep md /proc/mdstat) ]; then
# Clear the whole disks:
mdadm --zero-superblock --force $DISK_A
# Clear arrays using a partition (e.g. a swap partition):
mdadm --zero-superblock --force ${DISK_A_SWAP}
fi
# Clear the partition table:
sgdisk --zap-all $DISK_A
Somehow redundant, I know, but I had issues with mdadm before. Never had
a problem ever since. But be careful - this ensures that the disk gets
completely wiped and no partition is preserved, even if you have a
'preserve' statement in your disk_config.
--
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
Hi Robert. Then it seems the docs are outdated. Not a big issue, even if the described behaviour would be more useful (automatic reboot if no errors, wait for confirmation in case of errors unless 'reboot' is given). :) BYtE, Diego Il 31/05/2022 12:23, Robert Markula ha scritto: 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 -- 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
