Config paths and scripts
Diese Nachricht wurde eingewickelt um DMARC-kompatibel zu sein. Die eigentliche Nachricht steht dadurch in einem Anhang. This message was wrapped to be DMARC compliant. The actual message text is therefore in an attachment.--- Begin Message --- Hulloa again, In our 50-host we have *-dbnode*) echo "FAIBASE UBUNTU JAMMY64 WIPEALL BOND JUMBO-DBNODE GRUB_EFI" ;; Am confused as to why these are as they are. FAIBASE is a directory (scripts/FAIBASE) UBUNTU is a directory (scripts/UBUNTU) JAMMY64 seems to refer to the JAMMY64.tar.xz file WIPEALL (I hope) is hooks/partition.WIPEALL (the script you pointed me to which purges disk partitions) BOND appears to be linked to code inside 30-interface which, I assume, is the version beneath UBUNTU (UBUNTU/30-interface) JUMBO-DBNODE is our declared disk_config file GRUB_EFI is scripts/GRUB_EFI It is correct in how they are referenced, as items in the class file, regardless of whether they are the ROOT dir of the keyword or code inside a script in a referenced KEYWORD directory? If so, and I want to have an alternative network configuration for the target system, would I have to have (eg) a second referenced UBUNTU with a different 30-interface inside it (one which configures the rebooted target with a different network config)? For example, we want a link aggregated host and so could suggest UBUNTU-LA, so as to differentiate between the usual setup going on here (active-master) and our version. I could then leave BOND and it would be the 30-int bond inside our new config. Thanks for the help in understanding this. Marc --- End Message ---
RE: RAID 0 Disk config.
Diese Nachricht wurde eingewickelt um DMARC-kompatibel zu sein. Die eigentliche Nachricht steht dadurch in einem Anhang. This message was wrapped to be DMARC compliant. The actual message text is therefore in an attachment.--- Begin Message --- Forgive my ignorance, I understand the basic use of FAI but I had no hand in installing the suite or configuring it, so I am more than happy to learn more about the mechanics of it. You said wipe-all was a script and partition.WIPEDISK is a hook, yet you suggest putting wipe-all into the hooks directory. /srv/fai/config/hooks $ ls debconf.CENTOS instsoft.DEBIAN repository.CENTOS setup.DEFAULT.sh updatebase.DEBIAN debconf.IMAGE instsoft.UBUNTU savelog.LAST.shupdatebase.CENTOS updatebase.UBUNTU would include partition.WIPEDISK (wipe-all script) and in 50-host-classes we have (eg) *-dbnode*) echo "FAIBASE UBUNTU FOCAL64 BOND JUMBO-DBNODE GRUB_EFI" ;; The fact that hooks, classes, and more have similar naming is a bit confusing. However, the new class definition for the above example would then be: *-dbnode*) echo "FAIBASE UBUNTU WIPEDISK FOCAL64 BOND JUMBO-DBNODE GRUB_EFI" ;; -Original Message- From: linux-fai On Behalf Of Thomas Lange Sent: Wednesday, April 5, 2023 9:57 AM To: fully automatic installation for Linux Subject: RE: RAID 0 Disk config. EXTERNAL >>>>> On Wed, 5 Apr 2023 07:34:11 +, Marc Hoppins via linux-fai >>>>> said: > Would the wipe-all script sit in class, like > 20-hwdetect.sh > 21-wipe-all.sh No, put those script into hooks/ and name them for e.g. partition.WIPEDISKS Then it get executed before the partitioning task starts if the class WIPEDISKS is defined. -- viele Grüße Thomas --- End Message ---
RE: RAID 0 Disk config.
Diese Nachricht wurde eingewickelt um DMARC-kompatibel zu sein. Die eigentliche Nachricht steht dadurch in einem Anhang. This message was wrapped to be DMARC compliant. The actual message text is therefore in an attachment.--- Begin Message --- Thanks Thomas. Would the wipe-all script sit in class, like 20-hwdetect.sh 21-wipe-all.sh or does it live in (eg) scripts/UBUNTU/ along with 10-rootpw 20-capabilities 30-interface 40-misc -Original Message- From: linux-fai On Behalf Of Thomas Lange Sent: Tuesday, April 4, 2023 4:26 PM To: fully automatic installation for Linux Subject: RE: RAID 0 Disk config. EXTERNAL Here you can find two small bash scripts, one called wipe-all which removes all partitions without caring about raid or lvm. The other script is called partition.WIPEDISKS is a FAI hooks and first stops lvm and raid then does the wipefs call. https://fai-project.org/download/misc/ --- End Message ---
RE: RAID 0 Disk config.
Diese Nachricht wurde eingewickelt um DMARC-kompatibel zu sein. Die eigentliche Nachricht steht dadurch in einem Anhang. This message was wrapped to be DMARC compliant. The actual message text is therefore in an attachment.--- Begin Message --- For installation one would expect a clean sheet. Maybe installation could have a script which purges existing partitions first. And/or have a re-insallation option to preserve existing. However, it may seem that existing partitions may cause a lot of failures due to the issues I experienced with nvme, existing partitions, and the bash cannot set terminal process group (1076): inappropriate ioctl for device messages. Food for thought. Marc -Original Message- From: linux-fai On Behalf Of Thomas Lange Sent: Tuesday, April 4, 2023 2:39 PM To: fully automatic installation for Linux Subject: RE: RAID 0 Disk config. EXTERNAL >>>>> On Tue, 4 Apr 2023 12:11:23 +0000, Marc Hoppins via linux-fai >>>>> said: > Another disk question if I may, does FAI test for existing partitions on the target disk? I think the reason I was getting failures is that the target probably had partitions created by a previous, failed FAI. Yes it tests for existing partition, because you may want to preserve the partition and/or the data in it. regards Thomas --- End Message ---
RE: RAID 0 Disk config.
Diese Nachricht wurde eingewickelt um DMARC-kompatibel zu sein. Die eigentliche Nachricht steht dadurch in einem Anhang. This message was wrapped to be DMARC compliant. The actual message text is therefore in an attachment.--- Begin Message --- Thanks, Thomas. Another disk question if I may, does FAI test for existing partitions on the target disk? I think the reason I was getting failures is that the target probably had partitions created by a previous, failed FAI. -Original Message- From: linux-fai On Behalf Of Thomas Lange Sent: Monday, April 3, 2023 10:14 PM To: fully automatic installation for Linux Subject: Re: RAID 0 Disk config. EXTERNAL >>>>> On Thu, 23 Mar 2023 14:56:35 +0000, Marc Hoppins via linux-fai >>>>> said: > For a RAID config, the documentation only specifies pre-sized partitions which I do not want. I currently have: Hi Marc, without checking I guess our tool does not support raw disks for this setup. But you can use a size of 1G- which means create a partition with a size of at least 1Gbytes but maximize the partition with no limit. That means the partition will get the whole size of the disk. This may be similar to what you want. It looks likes this: disk_config /dev/sda fstabkey:uuid align-at:1M primary - 1G- - - - Then you can use the partitions to create your raid0. -- regards Thomas --- End Message ---
RE: Installation failure
Diese Nachricht wurde eingewickelt um DMARC-kompatibel zu sein. Die eigentliche Nachricht steht dadurch in einem Anhang. This message was wrapped to be DMARC compliant. The actual message text is therefore in an attachment.--- Begin Message --- Thanks, Steffen. I have nothing to do with setting up FAI, I am just a fai-user. How do I go about using createvt? -Original Message- From: Steffen Grunewald Sent: Monday, April 3, 2023 10:19 AM To: fully automatic installation for Linux Cc: Marc Hoppins Subject: Re: Installation failure EXTERNAL Hi Marc, On Mon, 2023-04-03 at 08:02:48 +, FAI mailing list wrote: > FAI runs to the point > > Starting cron > Starting SSHD > Starting smartd > FAI: installation aborted. > reboot with: faireboot > or after a logout > bash cannot set terminal process group (1076): inappropriate ioctl for > device > bash: no job control in this shell > > > The shell that exists (nfs) is slow and does NOT have /tmp/fai so > there are no logs This seems to point at a problem with the creation of the writable filesystem on top of the NFS root - would you mind to show your full kernel command line? (Also, do you have the "createvt" flag enabled? Do you run a fai-monitor daemon that would show which step(s) failed?) - S -- Steffen Grunewald, Cluster Administrator Max Planck Institute for Gravitational Physics (Albert Einstein Institute) Am Mühlenberg 1 * D-14476 Potsdam-Golm * Germany ~~~ Fon: +49-331-567 7274 Mail: steffen.grunewald(at)aei.mpg.de ~~~ --- End Message ---
Installation failure
Diese Nachricht wurde eingewickelt um DMARC-kompatibel zu sein. Die eigentliche Nachricht steht dadurch in einem Anhang. This message was wrapped to be DMARC compliant. The actual message text is therefore in an attachment.--- Begin Message --- Hi, Guys, We are trying to install Ubuntu20 to Supermicro (UEFI) NVME device. FAI runs to the point Starting cron Starting SSHD Starting smartd FAI: installation aborted. reboot with: faireboot or after a logout bash cannot set terminal process group (1076): inappropriate ioctl for device bash: no job control in this shell The shell that exists (nfs) is slow and does NOT have /tmp/fai so there are no logs This system is similar to others which were setup successfully by a colleague (same hardware, subnet), so the disk layout is almost the same, I just increased partition sizes a little to accommodate software to be installed. # entire disk with LVM, separate /home disk_config /dev/nvme0n1 disklabel:gpt fstabkey:uuid align-at:1M primary /boot/efi 512M vfatrw primary /boot 512M ext2rw,noatime primary - 4G- - - disk_config lvm vg vg /dev/nvme0n1p3 vg-root / 8G xfsrw,noatime,nodiratime vg-tmp /tmp1G xfsrw,noatime,nodiratime vg-var /var10G xfsrw,noatime,nodiratime vg-varlog /var/log4G xfsrw,noatime,nodiratime,nodev,nosuid,noexec vg-home /home 8G xfsrw,noatime,nodiratime,nodev,nosuid vg-opt /opt10G xfsrw,noatime,nodiratime --- End Message ---
RE: Ubuntu 22
Diese Nachricht wurde eingewickelt um DMARC-kompatibel zu sein. Die eigentliche Nachricht steht dadurch in einem Anhang. This message was wrapped to be DMARC compliant. The actual message text is therefore in an attachment.--- Begin Message --- I think what our guy was referring to was that he must have made a Ubu22 basefile, either from a dist-upgraded ubu20 system or a modified ubu22 basefile, which does not work here. In the meantime, I shall have to use a ubu20 and do dist-upgrades as the request we have is for Ubu22 and I doubt we can wait for him to finish with a working version. I was just trying to clarify that the version on the project site was good. Thanks -Original Message- From: linux-fai On Behalf Of Thomas Lange Sent: Friday, March 31, 2023 12:48 PM To: fully automatic installation for Linux Subject: RE: Ubuntu 22 EXTERNAL > The basefile on YOUR site? It is fine? It should be fine, but if you say it's not fine, please provide some more infos. regards Thomas --- End Message ---
RE: Ubuntu 22
Diese Nachricht wurde eingewickelt um DMARC-kompatibel zu sein. Die eigentliche Nachricht steht dadurch in einem Anhang. This message was wrapped to be DMARC compliant. The actual message text is therefore in an attachment.--- Begin Message --- The basefile on YOUR site? It is fine? -Original Message- From: linux-fai On Behalf Of Thomas Lange Sent: Friday, March 31, 2023 10:34 AM To: fully automatic installation for Linux Subject: Re: Ubuntu 22 EXTERNAL > I see a JAMMY64 basefile on the fai-project site. Our FAI guy here tells me that it is not functional, is this the case? > Marc Any error messages? Some more info would be good. -- regards Thomas --- End Message ---
Ubuntu 22
Diese Nachricht wurde eingewickelt um DMARC-kompatibel zu sein. Die eigentliche Nachricht steht dadurch in einem Anhang. This message was wrapped to be DMARC compliant. The actual message text is therefore in an attachment.--- Begin Message --- HI all, I see a JAMMY64 basefile on the fai-project site. Our FAI guy here tells me that it is not functional, is this the case? Marc --- End Message ---
RAID 0 Disk config.
Diese Nachricht wurde eingewickelt um DMARC-kompatibel zu sein. Die eigentliche Nachricht steht dadurch in einem Anhang. This message was wrapped to be DMARC compliant. The actual message text is therefore in an attachment.--- Begin Message --- Apologies for previous message...forgot to suggest plain text. Hi all, I am learning to use FAI and have been checking our existing disk configurations. We have similar to: disk_config /dev/sdb fstabkey:uuid raw-disk /mnt/data01 1M- xfs rw,defaults disk_config /dev/sdc fstabkey:uuid raw-disk /mnt/data02 1M- xfs rw,defaults The above examples mount using the entire disk. NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sda 8:00 3.7T 0 disk /mnt/data01 sdb 8:16 0 3.7T 0 disk /mnt/data02 For a RAID config, the documentation only specifies pre-sized partitions which I do not want. I currently have: The following devices are SSD. disk_config /dev/sda fstabkey:uuid align-at:1M raw-disk - - - - disk_config /dev/sdb fstabkey:uuid align-at:1M raw-disk - - - - disk_config /dev/sdc fstabkey:uuid align-at:1M raw-disk - - - - disk_config /dev/sdd fstabkey:uuid align-at:1M raw-disk - - - - disk_config raid fstabkey:uuid align-at:1M raid0 /mnt/data sda,sdb,sdc,sddxfsrw,defaults which is not working. I would greatly appreciate some correction here. Marc Hoppins --- End Message ---
DISK Setup RAID0
Diese Nachricht wurde eingewickelt um DMARC-kompatibel zu sein. Die eigentliche Nachricht steht dadurch in einem Anhang. This message was wrapped to be DMARC compliant. The actual message text is therefore in an attachment.--- Begin Message --- Hi all, I am learning to use FAI and have been checking our existing disk configurations. We have similar to: disk_config /dev/sdb fstabkey:uuid raw-disk /mnt/data01 1M- xfs rw,defaults disk_config /dev/sdc fstabkey:uuid raw-disk /mnt/data02 1M- xfs rw,defaults The above examples mount using the entire disk. NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sda 8:00 3.7T 0 disk /mnt/data01 sdb 8:16 0 3.7T 0 disk /mnt/data02 For a RAID config, the documentation only specifies pre-sized partitions which I do not want. I currently have: The following devices are SSD. disk_config /dev/sda fstabkey:uuid align-at:1M raw-disk - - - - disk_config /dev/sdb fstabkey:uuid align-at:1M raw-disk - - - - disk_config /dev/sdc fstabkey:uuid align-at:1M raw-disk - - - - disk_config /dev/sdd fstabkey:uuid align-at:1M raw-disk - - - - disk_config raid fstabkey:uuid align-at:1M raid0 /mnt/data sda,sdb,sdc,sddxfsrw,defaults which is not working. I would greatly appreciate some correction here. Marc Hoppins --- End Message ---
FAI, NVME, UEFI
Diese Nachricht wurde eingewickelt um DMARC-kompatibel zu sein. Die eigentliche Nachricht steht dadurch in einem Anhang. This message was wrapped to be DMARC compliant. The actual message text is therefore in an attachment.--- Begin Message --- Hi all, We recently took receipt of Dell C6520 systems. These come with 2 x 256GB NVME boot devices (RAID) 2 x 8TB SSDs 1 x 1G EMBEDDED NIC 2 x 25G INTEGRATED NIC For the sake of identification we will call these SRV 01-08 To say we are having problems is a slight understatement. Initially we could not get these up without altering the BIOS settings. UEFI boot setting in the BIOS was necessary to recognise the various devices, this meant that GRUB_EFI was needed for FAI. Disabling the 1G NIC was required as FAI wanted to create a BOND between the 1G and one of the 25G, so we have to also change the boot setting for this 25G NIC to be PXE. Our end-user was adamant that we use UBU16 as he did not want to break any of his development work, or take a chance that something would not operate as before. So we FAI’d to UBU 16 and all was fine. However, a decision was then made to upgrade to UBU18. So we decided to re-FAI them instead of doing an in-place upgrade. Out of 8 servers, 6 installed with UBU18 but decided to offer up ‘Diskfilter writes are not supported’ errors. This results in NIC failures/issues on subsequent boot. For one of the remaining two, the iDRAC decided to crap itself and all we can now do (until some living person presses the big red tit) is power cycle the server, no keyboard actions are possible at all. A further decision was then made to FAI to UBU16 as this produced success across all servers, and we will do a release-upgrade. One has successfully completed, the non-responsive KVM is still non-responsive. Our disk_config sets 1G for /boot/efi The remainder is LVM2 Of the fails: dhcp PREINIT eth0 up dhcp FAIL RTNETLINK answers: file exists …and then drops to a dracut prompt. So FAI seems to only find one of the two 25G NICs (SOMETIMES!!) and thus fails. This is odd because with a subsequent retry on SRV01 with UBU18, eth0 did not appear but eth1 did yet the FAI continued For RTNETLINK, what file exists? Doesn’t FAI start with a clean slate?? So, for all 8 attempted UBU16 installs we have SRV01 - success SRV02 - success SRV03 - No KVM SRV04 – Fail, then boots to previous OS (UBU18) with DISKFILTER WRITES error SRV05 – Fail, then boots to previous OS (UBU18) with DISKFILTER WRITES error SRV06 – success SRV07 – success SRV08 – success All hardware is the same, all BIOS settings are the same. I have retried the fails several times and all return the same errors. SRV01 - I tried a re-FAI using UBU18, eth0 did not appear in the messages but eth1 did. UBU18 then completed but we end up with DISKFILTER error again, and no bond. I tried again and eth0 appeared, as did eth1, yet I saw DHCP FAIL. This then results in DISKFILTER error yet again and I am of the opinion that FAI locating devices is an extremely hit and miss affair according to some strange sequential mis-logic. SRV01 - I went back to UBU16 and all went without mishap. SRV01 – I tried UBU20 and this also appeared to work fine. FINALLY, back to UBU16 as we are unable (at this time) to use UBU20, and all installed without issue. If anyone has any consistent success with this hardware, Ubuntu versions and FAI I’d appreciate some hints. Thanks Marc --- End Message ---
RE: 50-host-classes
Diese Nachricht wurde eingewickelt um DMARC-kompatibel zu sein. Die eigentliche Nachricht steht dadurch in einem Anhang. This message was wrapped to be DMARC compliant. The actual message text is therefore in an attachment.--- Begin Message --- HI, Juri, I don't see how that works, the hostname is going to end up being the hostname of the FAI server, isn't it? -Original Message- From: Juri Grabowski Sent: Tuesday, April 26, 2022 5:08 PM To: fully automatic installation for Linux Cc: Marc Hoppins Subject: Re: 50-host-classes EXTERNAL Hello, Maybe you are looking for something like that: #! /bin/bash MYDOMAINNAME=$(hostname -d) MYFQDN=$(hostname -f) case $MYFQDN in fqdnhost.example.com) echo "EXAMPLECLASS1" ;; *) echo "FAIBASE DEBIAN DEMO" ;; esac case $MYDOMAINNAME in mydemodomain2.example.com) echo -en "DOMCLASS2 " case $HOSTNAME in demohost|client*) echo "EXAMPLECLASS2" ;; *) echo "FAIBASE DEBIAN DEMO" ;; esac ;; mydemodomain3.example.com) case $HOSTNAME in demohost|client*) echo "EXAMPLECLASS3" ;; *) echo "FAIBASE DEBIAN DEMO" ;; esac ;; esac Best Regards, gratuxri --- End Message ---
50-host-classes
Diese Nachricht wurde eingewickelt um DMARC-kompatibel zu sein. Die eigentliche Nachricht steht dadurch in einem Anhang. This message was wrapped to be DMARC compliant. The actual message text is therefore in an attachment.--- Begin Message --- HI, Same question as in StackOverflow: Fully Automated Install (FAI) has hosts in the file 50-host-classes. We currently have a bunch of hosts which have similar names (eg, ba-hostxx.subdomain). The sub-domains are different but one cannot specify host.subdomain in the class file as the '.' is invalid. However it was setup originally, it has morphed over time and we have ba-w6* ba-w7* ba-w* dr1-w4* dr1-w6* dr1-w7* dr1-w* and so on Is it possible to have different hosts in different files? Or to specify the host in some other fashion than just hostname*) echo "BASEFILE FILE" ;; such as cluster/hostname*) echo "BASEFILE FILE" ;; ? The documentation leads one to the opinion that all hosts sit in the 50- file which makes it very unwieldy. Thanks --- End Message ---
