On 29/7/25 22:56, Diego Zuccato wrote:
Using trusted.gpg is deprecated.
I missed that - thanks!
(https://salsa.debian.org/apt-team/apt/-/raw/2.9.24/debian/NEWS)
Just use another dir and add to the list files a "signed-by" option.
/etc/fai/apt/keys/ works fine (ref: man fai-make-nfsroot)
Die
Il 29/07/25 19:28, Christopher Huhn ha scritto:
Hi,
Am 29.07.25 um 14:56 schrieb Diego Zuccato:
Using trusted.gpg is deprecated.
Hm, dut deprecation means "it will probably stop working" and not that
it's already broken, doesn't it?
I'm not sure of the current deprecation stage: I'm using
Hi,
Am 29.07.25 um 14:56 schrieb Diego Zuccato:
Using trusted.gpg is deprecated.
Hm, dut deprecation means "it will probably stop working" and not that
it's already broken, doesn't it?
Just use another dir and add to the list files a "signed-by" option.
Is this already supported by FAI i
Using trusted.gpg is deprecated.
Just use another dir and add to the list files a "signed-by" option.
Diego
Il 17/07/25 06:53, Scott Ferguson ha scritto:
On 14/7/25 14:00, Scott Ferguson wrote:
Debian Bookworm fai-server running latest fai-project packages,
creating installation .iso images
On 14/7/25 14:00, Scott Ferguson wrote:
Debian Bookworm fai-server running latest fai-project packages,
creating installation .iso images for Debian Bookworm clients.
I have put the .gpg keys in $NFSROOT/etc/apt/trusted.gpg.d (per 2010
instructions on this mailing list as I failed to find anot
Hi Richard,
there's the variable FAI_KEEP_CRYPTKEYFILE that inhibits the deletion
of the key file. See
https://fai-project.org/doc/man/setup-storage.html
We delete the file by default for security reasons.
--
best regards Thomas
> On Mon, 16 Jun 2025 11:12:22 -0500, "John G. Heim"
> said:
> $ROOTCMD mkdir -p $xfdir
> $ROOTCMD cp /etc/xdg/xfce4/panel/default.xml
$xfdir/xfce4-panel.xml
> # group name is the same as user name
> $ROOTCMD chown -R $username:$username $userd
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'm looking at the example scripts in the fai-doc pac
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 ---
Doh! That was a typo in my email message. I know I sh
> On Mon, 16 Jun 2025 16:48:07 +0200, Stefan Möding via linux-fai
> said:
> Have you tried to use a comma instead of the colon between the username
> and the groupname?
That's it. We only split the three arguments at the comma.
fcopy should also print this error message:
fcopy:
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 ---
"John G. Heim via linux-fai" writes:
> My fcopy cam
Do you have any error message?
fcopy must lookup the user and group inside the /target environment
(we use a perl oneliner and getpwnam/getgrnam for that). Maybe this
causes a problem.
--
regards Thomas
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 ---
On Tue, Jun 10, 2025 at 11:32:07AM +0200, Thomas Lang
> On Tue, 10 Jun 2025 09:48:32 +0100, Stephen Quinney via linux-fai
> said:
> I've tried changing the alignment (we normally use 4096 for SSDs),
> varying the order in which the partitions are specified and varying
> the sizes of the partitions, nothing helps. Attached is my
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'm also attaching the full debug log from setup-stor
Am 05.06.25 um 09:02 schrieb Diego Zuccato:
It's now on the wiki:
https://wiki.fai-project.org/index.php/FullDiskEncryption
Tks for all the support!
Great, thanks for your write-up!
OpenPGP_0x7D6C604A57E37237.asc
Description: OpenPGP public key
OpenPGP_signature.asc
Description: OpenPGP di
Il 04/06/2025 12:34, Thomas Lange ha scritto:
We do not have a special place for user contributed scripts, this
mailing list is fine IMO. You may want to add it to the FAI wiki.
It's now on the wiki:
https://wiki.fai-project.org/index.php/FullDiskEncryption
Tks for all the support!
--
Diego Z
Hi Diego,
Am 04.06.25 um 14:19 schrieb Diego Zuccato:
Wiki is OK for me, but I'm not (yet) registered.
I could format it as a howto.
I have wiki r/w access. If you'd like, I can upload your how-to to the
wiki under your name. Just drop me a pm.
Best regards,
Robert
OpenPGP_0x7D6C604A57E3
Wiki is OK for me, but I'm not (yet) registered.
I could format it as a howto.
Diego
Il 04/06/2025 12:34, Thomas Lange ha scritto:
On Wed, 4 Jun 2025 12:27:27 +0200, Diego Zuccato said:
> Update: it now works as expected. Might it be worthy of inclusion with
> other user-contribute
Update: it now works as expected. Might it be worthy of inclusion with
other user-contributed scripts?
class/ENCRYPTED.var :
-8<--
FAI_KEEP_CRYPTKEYFILE=1
LUKS_PASS="YourBootPassword"
-8<--
hooks/configure.ENCRYPTED :
-8<--
#!/bin/sh
# Requires ENCRYPTED.var for setup
srctab="${LOGDIR}/cryptta
> On Wed, 4 Jun 2025 12:27:27 +0200, Diego Zuccato
> said:
> Update: it now works as expected. Might it be worthy of inclusion with
> other user-contributed scripts?
We do not have a special place for user contributed scripts, this
mailing list is fine IMO. You may want to add i
Il 03/06/2025 09:43, Thomas Lange ha scritto:
> > From where is it best to call such a script?
> A good place is as a hook for the partition task as seen in
> partition.WIPEDISKS
Urgh... Stupid me: forgot about hooks.
BTW, the problem that triggered my request was an install on a machine
> On Tue, 3 Jun 2025 08:06:38 +0200, Diego Zuccato
> said:
> Tks!
> Seems partition.WIPEDISKS is wiping too much (including data disks not
> marked for repartitioning and hence not in $disklist), while wipe-all
> considers only disks in $disklist (then why '-all'?) but
Tks!
Seems partition.WIPEDISKS is wiping too much (including data disks not
marked for repartitioning and hence not in $disklist), while wipe-all
considers only disks in $disklist (then why '-all'?) but does not
account for LVM and MDRAID. But they're a good starting point.
Neither run only wh
Maybe some LVM, soft RAID blog are still on the disk?
You can find two scripts/hooks which help removing all data from all
disks on
https://fai-project.org/download/misc/
--
regards Thomas
Hi Andrej.
I have many different partition schemes, sometimes per-class, sometimes
per-host.
The last I used is:
-8<--
disk_config disk1 disklabel:msdos bootable:1 fstabkey:uuid align-at:1M
preserve_reinstall:6,8
primary / 12G-16Gext4 rw,noatime,errors=remount-ro
logical
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 ---
Buongiorno Diego,
How exactly are you using FAI, how
Hi y'all
I like to know who is using the DHCP server from ISC when doing a FAI
network installation.
We do too.
Debian plans to remove this package for the> upcoming release (trixie) and I'm
not sure how much work it may cause
to sysadmin to migrate to a replacement, for e.g. the new DHCPD
Thomas,
We are using ISC DHCP in the Electrical and Computer Engineering Department at
the University of British Columbia.
We generate our dhcpd.conf programmatically from our in-house IP address
management tool, and our template does things like putting devices that are
marked as FAI-enabled
Hi
On 5/27/25 09:33, Thomas Lange wrote:
I like to know who is using the DHCP server from ISC when doing a FAI
network installation. Debian plans to remove this package for the
upcoming release (trixie) and I'm not sure how much work it may cause
to sysadmin to migrate to a replacement, for e.g.
On Tue, 2025-05-27 at 09:33 +0200, Thomas Lange wrote:
> Hi,
>
> I like to know who is using the DHCP server from ISC when doing a FAI
> network installation. Debian plans to remove this package for the
> upcoming release (trixie) and I'm not sure how much work it may cause
> to sysadmin to migrat
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 Thomas, all,
We're using ISC DHCPD with FAI and a
Hi Thomas,
[I initially accidentally replied to just Thomas, replying to the list
for the benefit of the community conversation.]
We currently run ISC also. We looked at KEA as it was the recommended
option in opnsense. However, in researching KEA we read about enough
problems that we decide
Hi Sinh,
what do you mean by awful? Do you expect major problems or a lot of
work for migrating to kea?
--
regards Thomas
Hi.
I already tried migrating to kea and it's been quite a pain in the a$$
(quite a lot of work). Quickly returned to the default.
Also, does not bode well with centralized management (Salt, in my case),
unless I missed something.
If ISC DHCP can't be kept, amen. It will be quite a lot of work
I use ISC DHCP server with FAI. I have been wanting to migrate to KEA but
have not done so. If I could I’d stay on ISC DHCP forever cause kea’s
config is just awful. Just really really awful.
Sinh
On May 27, 2025 at 12:34:18 AM, Thomas Lange (la...@cs.uni-koeln.de) wrote:
Hi,
I like to kn
I wonder why this happens, because an error in get-config-dir-nfs
causes my network installation to abort.
By default the variable STOP_ON_ERROR=700 is set and that causes errors
greater 700 to abort the installation.
I'm working on a patch to check the error from get-config-dir-$method
after its
just closing the loop. the general issue for i40e had been logged in
oct 2024 as https://bugs.debian.org/1080975 and is a "wontfix"
--
andrew bezella
internet archive
oh, ftr looks like it was previously reported here in a slightly
different context (bookworm vs noble):
https://lists.uni-koeln.de/pipermail/linux-fai/2024-May/013214.html
sorry for missing that. the OP there ended up using sed.
--
andrew bezella
internet archive
On Thu, 2025-05-08 at 23:13 +1200, Andrew Ruthven wrote:
> On Thu, 2025-05-08 at 08:54 +0200, Steffen Grunewald wrote:
> > On Wed, 2025-05-07 at 13:49:45 -0700, andrew bezella wrote:
> > > hello -
> > >
> > > i'm running into a situation where the systemd network device
> > > naming
> > > changes
On Thu, 2025-05-08 at 23:13 +1200, Andrew Ruthven wrote:
> use ethX as systemd refuses to rename things to ethX now. And can't
> use enoX
> for a similar reason.
you can use (in trixie) the ethX schema with a kernel command-line
parameter, in debian under /etc/default/grub:
--snip--
GRUB_CMDLINE_L
On Thu, 2025-05-08 at 08:54 +0200, Steffen Grunewald wrote:
> On Wed, 2025-05-07 at 13:49:45 -0700, andrew bezella wrote:
> > hello -
> >
> > i'm running into a situation where the systemd network device naming
> > changes with kernel version (bookworm/6.1 vs trixie/6.12 in this case).
> > this is
On Wed, 2025-05-07 at 13:49:45 -0700, andrew bezella wrote:
> hello -
>
> i'm running into a situation where the systemd network device naming
> changes with kernel version (bookworm/6.1 vs trixie/6.12 in this case).
> this is possibly related to a change/update in devlink support in the
> i40e dr
Hi Balder,
you have to provide more details.
I guess you have upgraded your FAI versions from buster to
bookworm. Is that on your own FAI server? Did you recreated the
nfsroot?
Did you checked the logs of the build process (fai-make-nfsroot) and
checked which FAI and which dracut versions are used
m Anhang.
>
> This message was wrapped to be DMARC compliant. The actual message
> text is therefore in an attachment.
>
>
> -- Forwarded message --
> From: "Étienne Mollier"
> To: fully automatic installation for Linux
> Cc:
> Bcc:
> Date
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 Kumaran,
>> This error ressembles to something th
gt; From: "Étienne Mollier"
> To: fully automatic installation for Linux
> Cc:
> Bcc:
> Date: Sat, 29 Mar 2025 10:42:20 +0100
> Subject: Re: Setup Storage Issue
> Hi Kumaran,
>
> This error ressembles to something that should be fixed by FAI
> commit 27c7267bad
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 Kumaran,
This error ressembles to something that
Il 05/03/2025 11:59, Thomas Lange ha scritto:
I never tried such a configuration and I don't know if this can work.
Didn't think that having to keep some RAID volumes across reinstalls
would be so problematic :) Should be quite a common scenario :)
Can you please check if the RAID is already
I never tried such a configuration and I don't know if this can work.
Can you please check if the RAID is already assembled before
setup-storage starts? I'm not sure if setup-storage can handle an
already running raid, or if it wan't to detect the partitions and the
reassembles the RAID itself.
Th
Something now works, but seems the problem is with the preservation of
RAID volumes: if I remove the "preserve_lazy:3,6" from RAID config, the
system installs. But overwrites partitions with data I'd need to keep.
I also tried moving preserve_lazy to volume lines like
raid1 - disk1.3,disk2.3,dis
allation for Linux
Subject: Re: New to FAI, having some issues building
One thing I have since noticed, the core networks dhcp server is sending
example.com as the dhcp domain and our sub domain is not included in the domain
search it provides. I can see in the fai boot.log of the localhost machine
oursubdomain.example.com, not sure if this is a problem,
nslookup works fine on machines with the core networks dhcp server sent
information.
Best Regards,
Stuart
From: Stuart Green
Sent: 30 January 2025 12:49
To: fully automatic installation for Linux
Subject: Re: New to FAI, having
___
From: linux-fai on behalf of Thomas Lange
Sent: 27 January 2025 08:46
To: fully automatic installation for Linux
Subject: Re: New to FAI, having some issues building
[You don't often get email from la...@cs.uni-koeln.de. Learn why this is
important at https://aka.ms/LearnAboutSend
On Thu, Jan 23, 2025 at 2:15 PM Stuart Green via linux-fai <
linux-fai@uni-koeln.de> wrote:
>
> I'm still unsure how to have the hostname set correctly, it keeps getting
> installed as localhost.
>
I had to modify fai-chboot so that it sets an environment variable on the
booting system. Find th
> On Thu, 23 Jan 2025 19:15:14 +, Stuart Green via linux-fai
> said:
> How are hostnames controlled/set when using autodiscover?
Usually the hostname is provided by the DHCP server (via the option
use-host-decl-names on).
This also work when using the autodiscover ISO.
--
rega
On Fri, 2025-01-24 at 11:41:22 -0500, Matthew Pounsett wrote:
> On Fri, Jan 24, 2025 at 7:57 AM Thomas Lange wrote:
> > Did you used the command wipefs -a on all disks and partitions?
> > Maybe also use dd and write some MB of zeros onto the disks. There may
> > be signatures of soft raid and GPT
On Fri, Jan 24, 2025 at 1:07 PM Christopher Huhn wrote:
> > sda8:00 7.3T 0 disk
> > sdb8:16 0 7.3T 0 disk
> > sdc8:32 0 447.1G 0 disk
> > sdd8:48 0 447.1G 0 disk
> as you can see here the large disks are sda (disk1) and sdb (disk2)
> while the SSDs are sdc and sd
Hi Matthew,
Am 24.01.25 um 18:18 schrieb Matthew Pounsett:
The server has four drives: two SSDs that I'm trying to mirror and put
volumes on, and two larger HDDs that FAI should be ignoring. It does
seem to be ignoring the two HDDs now, thanks to help in the last thread.
[…]
$disklist shows
On Fri, Jan 24, 2025 at 7:57 AM Thomas Lange wrote:
> > On Thu, 23 Jan 2025 17:33:56 -0500, Matthew Pounsett <
> m...@conundrum.com> said:
>> I've used dd to wipe all four drives of data left behind by the
> previous hardware controller, and
> > when I started the install all four dri
> On Thu, 23 Jan 2025 17:33:56 -0500, Matthew Pounsett
> said:
> Executing: mdadm --assemble --scan
--config=/tmp/fai/mdadm-from-examine.conf
> mdadm --assemble --scan --config=/tmp/fai/mdadm-from-examine.conf had
exit code 1
> (STDERR) mdadm: Devices UUID-01c77a40:7ab3107d
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 ---
What you said made me look around a little. I see db
d64simple
interprocess messaging system (Python 3 interface)
root@localhost:~#
Best Regards,
Stu
From: linux-fai on behalf of Thomas Lange
Sent: 23 January 2025 16:50
To: fully automatic installation for Linux
Subject: Re: New to FAI, having some iss
> On Thu, 23 Jan 2025 16:38:31 +, Stuart Green via linux-fai
> said:
> On the simple installation which finishes with a congratulations, after
booting it and logging on I find:
> root@localhost:~# ls -l /run/dbus/system_bus_socket
> ls: cannot access '/run/dbus/system_b
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
RE:
*
This is an error because
> On Thu, 23 Jan 2025 15:23:54 +, Stuart Green via linux-fai
> said:
> The bootable autodiscover iso finds the server no problem and if I select
the Simple install which does headless Debian it runs through without
> error. However if I try Ubuntu then it consistently fini
A tarball for a generic nfsroot for arm64 can be found at
https://fai-project.org/download/misc/
You can extract it on any x86 server and serve it to your arm64
clients via NFS. Do not forget to adjust the etc/hosts and
etc/resolv.conf files inside the nfsroot. fai-make-nfsroot -a may
help you.
On Fri, 2025-01-17 at 15:15:01 +0100, Thomas Lange wrote:
> > On Fri, 17 Jan 2025 15:01:07 +0100, Steffen Grunewald
> > said:
>
> > Will do as soon as I know how...
> > Random thought: Would this also run on a more "normal" ARM64 machine?
> What's a normal machine?
One that uses
ISC DHCP is well established. Although it's deprecated it will be used
for many more years. Many people/companies rely on it and can not
easily switch to another software, so IMO there will be people that
will fix bugs if they arise.
--
reagrds Thomas
Il 17/01/2025 18:46, Thomas Lange ha scritto:
> Hijacking thread for a possibly quick question: is a migration to
> isc-kea planned ? isc-dhcp-server has been obsoleted, but the tests
No, there's no plan to use the kea DHCP server in the near future (not
in the next two years I guesss)
> On Fri, 17 Jan 2025 18:00:34 +0100, Diego Zuccato
> said:
> Hi.
> Hijacking thread for a possibly quick question: is a migration to
> isc-kea planned ? isc-dhcp-server has been obsoleted, but the tests
No, there's no plan to use the kea DHCP server in the near future (not
Hi.
Hijacking thread for a possibly quick question: is a migration to
isc-kea planned ? isc-dhcp-server has been obsoleted, but the tests
we've done highlighted many problems with the change (at leas with isc's
upstream packages, not tested yet with Debian ones).
Tks,
Diego
Il 17/01/2025 12
> On Fri, 17 Jan 2025 15:01:07 +0100, Steffen Grunewald
> said:
> Will do as soon as I know how...
> Random thought: Would this also run on a more "normal" ARM64 machine?
What's a normal machine?
>> Add this to dhcpd.conf:
>>
>> if substring(option vendor-class-iden
Hi Thomas,
On Fri, 2025-01-17 at 12:00:21 +0100, Thomas Lange wrote:
> Hi,
>
> I've already successfully booted an ARM64 server via UEFI/PXE using
> FAI. No installation was done, because this was a special FAI
> environment, were no installation is needed, but some hardware testing
> tools are u
Hi,
I've already successfully booted an ARM64 server via UEFI/PXE using
FAI. No installation was done, because this was a special FAI
environment, were no installation is needed, but some hardware testing
tools are used.
FAI 6.2.5 also includes some new code for creating a FAI-CD for
arm64. I cou
Thanks for this feedback.
I'm always very interested in user experiences with FAI. Can you
please fill out the FAI questionnaire
https://fai-project.org/questionnaire
and send it back to me when you finished a project with FAI.
--
best regards Thomas
I took my degree exam based on your project and I used it successfully in
large laboratories. I thank you very much! Greetings from Chile.
El lun, 23 de dic de 2024, 8:58 a. m., Thomas Lange
escribió:
> Read my blog post about the 25th birthday of FAI.
>
> https://blog.fai-project.org/posts/25-y
On Tue, 2024-12-17 at 10:07:56 +0100, Steffen Grunewald wrote:
> Good morning,
>
> after a very promising start, I experienced a set-back yesterday with an
> otherwise proven-to-work FAI setup, and need an alternative now.
>
[...]
>
> After setting up multipath and storage zpools, I can no longe
On Wed, 2024-12-18 at 10:32:00 +0100, Markus Köberl wrote:
> Maybe a good idea is to look at the vdev_id script from openzfs.
> It uses a config file vdev_id.conf and can handle different topology,
> multipath and aliases to create links under /dev/disk/by-vdev
>
> https://openzfs.github.io/openz
On Wed, 2024-12-18 at 08:40 +, Schulz, Reiner wrote:
> Hi!
>
> here a snip of the solution i use:
> Unforturnately it work only at install
Just checking, are you installing the cryptsetup-initramfs package in the
target? Not doing this has bitten me before.
Cheers,
Andrew
--
Andrew Ruthve
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 ---
On Tuesday, 17 December 2024 16:57:24 CET Steffen Gru
On Tue, 2024-12-17 at 17:05:17 +0100, Steffen Grunewald wrote:
> I had written to additional.var in a partition.* hook, is this too late?
Apparently yes.
> Do I have to do this in a class/* script? Hm...
Done this - with /dev/ in front, resulting in
Setting disklist
Hi Henning,
On Tue, 2024-12-17 at 14:13:00 +0100, Henning Glawe wrote:
> Moin,
>
> are you booting via BIOS/legacy or UEFI (with the corresponding GRUB)?
UEFI, with the right GRUB.
It's not the first time I'm doing this, and it works without the JBODs
connected.
I haven't even found a LEGACY se
Hi Andrew,
On Tue, 2024-12-17 at 22:34:04 +1300, Andrew Ruthven wrote:
> My provided script is in:
> https://lists.uni-koeln.de/pipermail/linux-fai/2024-January/013143.html
Now that I dug this out of the archive, I remember having seen it before ;)
Part of this went into the latest version of FAI
On Tue, 2024-12-17 at 16:45:56 +0100, Steffen Grunewald wrote:
> On Tue, 2024-12-17 at 14:02:17 +0100, Thomas Lange wrote:
> > But then try to modifiy the disklist variable (see
> > class/20-hwdetect.sh for that) to get a well defined order and then use
> > disk1, disk2,...
But ... I'm apparently
On Tue, 2024-12-17 at 14:02:17 +0100, Thomas Lange wrote:
> > On Tue, 17 Dec 2024 13:52:22 +0100, Steffen Grunewald
> > said:
>
> > Can I use the full-fledged path, e.g.
> > /dev/disk/by-path/pci-:06:00.0-ata-..0
> > in all places? This seems to work for the disk_config
Moin,
are you booting via BIOS/legacy or UEFI (with the corresponding GRUB)?
"out of memory" sounds like something more likely to hit in a BIOS/legacy
boot.
On Tue, Dec 17, 2024 at 10:07:56AM +0100, Steffen Grunewald wrote:
> Good morning,
>
> after a very promising start, I experienced a set-b
> On Tue, 17 Dec 2024 13:52:22 +0100, Steffen Grunewald
> said:
> Can I use the full-fledged path, e.g.
> /dev/disk/by-path/pci-:06:00.0-ata-..0
> in all places? This seems to work for the disk_config line itself,
> but for mdraid definitions?!
I never tried it, but
Hi Thomas,
On Tue, 2024-12-17 at 10:43:57 +0100, Thomas Lange wrote:
> I wonder if you have a grub or a FAI problem?
Until yesterday I had none of both...
FAI worked perfectly installing my plan, but with the 120 disks now
partitioned (something I didn't hand over to FAI, due to a lack of
plannin
I wonder if you have a grub or a FAI problem?
If it's a grub problem, I suggest to try Super Grub2 Disk which is a
very sophisticated grub menu detecting all sorts of configurations. If
this also fails, grub itself can't handle your environment (maybe
because of bug in an edge case).
Or is it only
Hey Steffen,
I can't really provide any insight into your issue with running out of
memory with ZFS. But I can answer your question below...
On Tue, 2024-12-17 at 10:07 +0100, Steffen Grunewald wrote:
> I'm afraid I've got to go back to md raid, but with all disks connected,
> how do I find the t
Have a look at
https://fai-project.org/download/misc/disk_config/
--
best regards Thomas
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 ---
Ignore me - that needs to be /target/etc/fstab
S
> On Thu, 14 Nov 2024 11:57:11 + (UTC), Andreas Leitz via linux-fai
> said:
> The tftp settings is:
> append initrd=initrd.img-6.1.0-26-amd64 ip=dhcp
root=192.168.1.254:/srv/fai/nfsroot:vers=3
> rootovl FAI_FLAGS=verbose,sshd,reboot
FAI_CONFIG_SRC=nfs://192.168.1.254/
Hi Thomas -
thank you for your answer …
On 06.11.24 18:11, Thomas Lange wrote:
which FAI version are you using? Do you do PXE installation or boot
from USB stick? Which ISO are you using?
FAI is the version available in the Debian bookworm repository, ie.
fai-quickstart 6.0.3+deb12u1 and its
FAI 6.0 does not yet use systemd during installation. Version 6.2 uses
systemd and then it works.
Good to hear that this is solved.
--
regards Thomas
Hi Thoralf,
which FAI version are you using? Do you do PXE installation or boot
from USB stick? Which ISO are you using?
There was a bug when mixing old FAI configs with a new FAI version that
no disks are detected if the block device does
not belong to the group disk.
On my machine this looks lik
Am 28.10.24 um 12:59 schrieb Thomas Lange:
Here's a blog post about the FAIme service that created its 30.000th job.
Great job Thomas!
Nice to see the increasing usage numbers.
Robert
OpenPGP_0x7D6C604A57E37237.asc
Description: OpenPGP public key
OpenPGP_signature.asc
Description: OpenPGP d
You may not prevent that, because we do not know how the run script
tries to detect a kernel version. In the chroot there's the target
kernel installed, but it's still running the FAI installation kernel.
Try to use the .deb packages instead of the run script.
> On Fri, 25 Oct 2024 09:34:30 +
Hi,
I have created several versions of the nfsroot including new nvidia
drivers and CUDA libraries, because we needed the newest drivers for
new hardware.
Often I used a mixture of packages from testing and experimental. I've
also created a nfsroot using the drivers and CUDA libs from nvidia
itse
1 - 100 von 4912 matches
Mail list logo
