Re: Re: task_error bei softupdate

[Schulz, Reiner]

Mein action.DEFAULT sieht so aus:

#!/bin/bash -x

echo HOOK $0

[ -z $FAI_HOST_FQDN ]  echo FEHLER  \$FAI_HOST_FQDN nicht gesetzt, bitte 
FAI_CONFIG/class/Hostname.var erstellen. ABBRUCH ;  task_error 899


Beim softupdate kommt folgendes:

...
Calling hook: action.DEFAULT
+ echo HOOK /var/lib/fai/config/hooks/action.DEFAULT
HOOK /var/lib/fai/config/hooks/action.DEFAULT
+ '[' -z ']'
+ echo 'FEHLER  $FAI_HOST_FQDN nicht gesetzt, bitte 
FAI_CONFIG/class/Hostname.var erstellen. ABBRUCH'
FEHLER  $FAI_HOST_FQDN nicht gesetzt, bitte FAI_CONFIG/class/Hostname.var 
erstellen. ABBRUCH
+ task_error 899
+ '[' X = X0 ']'
+ task_error_func='task_error main'
+ '[' 899 -gt 0 ']'
+ task_error=899
+ '[' 899 -gt 700 ']'
+ stop_fai_installation
+ sendmon 'TASKEND action 899'
+ '[' 0 -eq 0 ']'
+ return 0
+ echo 'Error in task action. Traceback: task_error main'
Error in task action. Traceback: task_error main
+ die 'FATAL ERROR. Installation stopped.'
+ task_savelog
+ mkdir -p //var/lib/fai //var/log/fai
+ fai-savelog -l
+ '[' -f /var/log/fai/ra0656/softupdate-20150216_161801/FAI_CLASSES ']'
+ '[' -f /var/log/fai/ra0656/softupdate-20150216_161801/disk_var.sh ']'
+ fai-savelog -r
+ echo 'FATAL ERROR. Installation stopped.'
FATAL ERROR. Installation stopped.
+ '[' Xsoftupdate = Xinstall ']'
+ exit 99
action.DEFAULT   FAILED with exit code 99.
Calling task_action
FAI_ACTION: softupdate
Performing FAI system update. All data may be overwritten!
...

Und hier läuft es dann weiter als ob nichts weiter war...

Reiner Schulz

   1. Re: task_error bei softupdate (Thomas Lange)

--

Message: 1
Date: Mon, 9 Feb 2015 16:57:17 +0100
From: Thomas Lange la...@informatik.uni-koeln.de
To: fully automatic installation for Linux linux-fai@uni-koeln.de
Subject: Re: task_error bei softupdate
Message-ID: 21720.55517.296627.601...@informatik.uni-koeln.de
Content-Type: text/plain; charset=iso-8859-1

 On Fri, 23 Jan 2015 15:53:32 +, Schulz, Reiner r.sch...@dvz-mv.de 
 said:

 Wenn meine Pr?fung fehlschl?gt und ich abbrechen m?chte, rufe ich
 task_error 899

 Wenn ich die dann beende, l?uft der Rest des softupdate weiter.
 Wie kann ich fai abbrechen?
Mmm, das scheint ein Bug zu sein. Kannst du das mal mit 

bash -x /usr/sbin/fai softupdate

debuggen?
-- 
regards Thomas


--

Subject: Digest Footer

___
linux-fai mailing list
linux-fai@uni-koeln.de
https://lists.uni-koeln.de/mailman/listinfo/linux-fai


--

End of linux-fai Digest, Vol 92, Issue 4

Option to set Ports for NFS mount

[Schulz, Reiner]

Hi,

in our enviroment we must to use a ssh tunnelt to connect to fai clients.
So we have to  use reverse ssh tunnel for all connections from client to  
server (nfs, save-log, etc)
Up to now we patch the fai programs to use/change the used ports.

Could you make an option to used  custom ports?

Reiner Schulz

AW: Option to set Ports for NFS mount

[Schulz, Reiner]

We use fai 3.4.8 for now and patch /usr/sbin/fai at line   export 
romountopt to

 export romountopt=-t nfs4 -o 
port=20549,soft,async,noatime,nolock,ro,actimeo=1800

and /usr/lib/fai/fai-savelog in save_log_remote() to

export remotesh=ssh  -p20550 -i /var/lib/fai/config/.ssh/id_ecdsa.failoguser
export remotecp=scp  -P20550 -i /var/lib/fai/config/.ssh/id_ecdsa.failoguser

For background:
We connect to the client via  ssh tunnel with two reverse tunnel, one for nfs 
and another for remote logging. 

Reiner Schulz

-Ursprüngliche Nachricht-
Von: linux-fai [mailto:linux-fai-boun...@uni-koeln.de] Im Auftrag von Thomas 
Lange
Gesendet: Montag, 30. März 2015 12:16
An: fully automatic installation for Linux
Betreff: Re: Option to set Ports for NFS mount

 On Mon, 30 Mar 2015 06:30:15 +, Schulz, Reiner r.sch...@dvz-mv.de 
 said:

 in our enviroment we must to use a ssh tunnelt to connect to fai clients.
 So we have to  use reverse ssh tunnel for all connections from client to  
server (nfs, save-log, etc)
 Up to now we patch the fai programs to use/change the used ports.

 Could you make an option to used  custom ports?
...

I'm not sure where to set the port for the NFS mount, maybe specifying
this on the kernel command line would help.


...

-- 
regards Thomas

Re: Re: task_error bei softupdate

[Schulz, Reiner]

...

Die Frage ist also eher: Soll dann abgebrochen werden oder soll 
der Wert ignoriert werden. Das ist eine Designentscheidung, wobei
ich zu ersterem tendiere: Wenn es einen fatalen Fehler in einem
hook gibt, sollte FAI abbrechen.

Daf?r scheint mir der Error-Code 99 ideal zu sein...

...

Ich hatte auf dieser Liste ein Posting von Thomas gefunden in der er schrieb, 
das task_error genau dafür gedacht ist. Deshalb habe ich diesen Weg gewählt.

Reiner

task_error bei softupdate

[Schulz, Reiner]

Hallo!

Ich möchte in einem Hook action.DEFAULT prüfen, ob  class/hostname.var 
alles enthält was ich brauche, falls nicht möchte ich den fai-lauf sauber 
beenden.

Wenn meine Prüfung fehlschlägt und ich abbrechen möchte, rufe ich

task_error 899

auf.

In /usr/lib/fai/subroutines wird dann als letztes die Funktion die() 
aufgerufen, die mit exec bash -i eine neu shell startet.
( Das die() hier noch prüft, on FAI_ACTION = install ignoriere ich mal, das 
könnte ich ja noch ergänzen. )

Wenn ich die dann beende, läuft der Rest des softupdate weiter.

Wie kann ich fai abbrechen?

Mit freundlichen Grüßen
Reiner

AW: Option to set Ports for NFS mount

[Schulz, Reiner]

Hi Thomas,

I tried your hint, but this work only on install not with softupdate right? 

NFSROOT/ root/.ssh/config  is only used at install time

On softupdate the local root User is used. 

my reverse tunnel use localhost as host, so I think it is a bad idea to 
change the ssh port for localhost.

May be there is another way: scp and ssh  have an option -F to use another 
config file,  if you could extent fai-savelog to use something like -F 
$MYSSHCONFIGFILEWITHSPECIALOPTION if this variable is set to an file in the 
configspace.

May be?

Reiner Schulz

-Ursprüngliche Nachricht-
Von: linux-fai [mailto:linux-fai-boun...@uni-koeln.de] Im Auftrag von Thomas 
Lange
Gesendet: Montag, 30. März 2015 12:16
An: fully automatic installation for Linux
Betreff: Re: Option to set Ports for NFS mount

 On Mon, 30 Mar 2015 06:30:15 +, Schulz, Reiner r.sch...@dvz-mv.de 
 said:

 in our enviroment we must to use a ssh tunnelt to connect to fai clients.
 So we have to  use reverse ssh tunnel for all connections from client to  
server (nfs, save-log, etc)
 Up to now we patch the fai programs to use/change the used ports.

 Could you make an option to used  custom ports?
Hi Reiner,

you can use /root/.ssh/config (inside the nfsroot) to specify a
different port for the ssh and scp commands. It should look like this:

Host faiserver.yourdomain faiserver
Port 1234

...

-- 
regards Thomas

AW: Logical Volumes on virtual drives

[Schulz, Reiner]

We use this disk_config file for Debian on vmware:
And we have to install "lvm2" and "grub-pc" in packages_config.

# example of new config file for setup-storage
#
#

disk_config sda align-at:1024K disklabel:msdos bootable:1 fstabkey:label
primary -   100%-   -

disk_config sdb align-at:1024K
primary -   100%-   -

disk_config sdc align-at:1024K
primary -   100%-   -

disk_config lvm fstabkey:label
vg  vgsys   sda1,sdb1,sdc1
vgsys-swap  swap2048swapsw
vgsys-root  /   5G  ext4defaults
vgsys-home  /home   50  ext4defaults
vgsys-mydata-   50  ext4-
vgsys-mybackup  -   20  ext4-
vgsys-pgdata-   20  ext4-
vgsys-pgbackup  -   20  ext4-
vgsys-srv   /srv20  ext4defaults
vgsys-var   /var1G-90%  ext4defaults

Reiner Schulz

> -Ursprüngliche Nachricht-
> Von: linux-fai [mailto:linux-fai-boun...@uni-koeln.de] Im Auftrag von Ronald 
> Steele
> Gesendet: Mittwoch, 27. April 2016 20:37
> An: fully automatic installation for Linux 
> Betreff: Logical Volumes on virtual drives
> 
> I’m trying to set up LV on virtual drives.  This may seem a bit weird, but it 
> for a test
> rig.
> Is this something that is supported?  I’ve tried CentOS and Debian on VmWare 
> and
> VirtualBox and it doesn’t appear to work on either.
> Besides some set ups of my own I’ve tried the LVM example in FAI distro and 
> one
> from the setup-installation section of the Wiki.
> The install works but when I reboot the new system I get errors like this:
> 
> Loading, please wait…
> Gave up waiting for root device.
> 
> Then a list of common problems.
> Then:
> 
> ALERT! /dev/mapper/my_pv-_root does not exist dropping into shell
> 
> 
> 
> 
> And then I get the initramfs prompt
> 
> I’ve no idea what /dev/mapper etc is or does.
> 
> Any ideas?
> 
> Ron

AW: example network script will misname interface if installing stretch

[Schulz, Reiner]

I'm developing a custom udev rule something like this:

For FAI Action install:

lspci -D | grep Ethernet | cut -d" " -f1

into /etc/udev/rules/70-my-persistent-net.rules:

SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", KERNELS==":03:00.0", 
NAME="eth0"

I set the interface name by pci bus

Reiner Schulz

> -Ursprüngliche Nachricht-
> Von: linux-fai [mailto:linux-fai-boun...@uni-koeln.de] Im Auftrag von
> q...@vienna.at
> Gesendet: Sonntag, 17. Juli 2016 10:01
> An: linux-fai@uni-koeln.de
> Betreff: Re: example network script will misname interface if installing 
> stretch
> 
> On Sat, Jul 16, 2016 at 02:18:25PM -0700, Ian Kelling wrote:
> > Using jessie as the base os to install stretch.
> >
> > 30-interface will setup /etc/network/interfaces with
> > something like eth0, and if you upgrade to stretch,
> > it will reboot and eth0 is now named something like
> > enp3s0f1.
> >
> > This was with version 5.0.3, so hopefully it's
> > still current.
> 
> And!
> Not all programs accept other names than ethx.

fcopy resolv.conf in task_repository

[Schulz, Reiner]

Hi Thomas,

In subroutines/task_repository you fcopy /etc/resolv.conf. 
It is possible to omit this?

While installing Debian 9 (with a Debian 8 FAI server) the installing client is 
in a extra subnet, with its own nameserver. After install is finished the 
client goes to production subnet, with another nameserver.

In task_confdir the resolv.conf of the FAI Server is copied to the installing 
client, that fine for us.
We fcopy the production resolv.conf with the LAST class.

For now I copied the task_repository into a hook "repository.DEBIAN_9" and 
remove the resolv.conf part. But I dont like that hack.

Reiner

AW: AW: nfsroot: dracut don't know to handle root=

[Schulz, Reiner]

For me it looks like there aren't drivers for nfs in the initrd:

Old one, works:
lsinitramfs  initrd.img-3.16.0-4-amd64|grep -i nfs
etc/modprobe.d/nfs.conf
lib/dracut/hooks/cleanup/99-nfsroot-cleanup.sh
lib/dracut/hooks/cmdline/90-parse-nfsroot.sh
lib/dracut/hooks/pre-udev/99-nfs-start-rpc.sh
lib/modules/3.16.0-4-amd64/kernel/fs/nfs
lib/modules/3.16.0-4-amd64/kernel/fs/nfs/blocklayout
lib/modules/3.16.0-4-amd64/kernel/fs/nfs/blocklayout/blocklayoutdriver.ko
lib/modules/3.16.0-4-amd64/kernel/fs/nfs/filelayout
lib/modules/3.16.0-4-amd64/kernel/fs/nfs/filelayout/nfs_layout_nfsv41_files.ko
lib/modules/3.16.0-4-amd64/kernel/fs/nfs/nfs.ko
lib/modules/3.16.0-4-amd64/kernel/fs/nfs/nfsv2.ko
lib/modules/3.16.0-4-amd64/kernel/fs/nfs/nfsv3.ko
lib/modules/3.16.0-4-amd64/kernel/fs/nfs/nfsv4.ko
lib/modules/3.16.0-4-amd64/kernel/fs/nfs/objlayout
lib/modules/3.16.0-4-amd64/kernel/fs/nfs/objlayout/objlayoutdriver.ko
lib/modules/3.16.0-4-amd64/kernel/fs/nfs_common
lib/modules/3.16.0-4-amd64/kernel/fs/nfs_common/nfs_acl.ko
lib/nfs-lib.sh
lib/x86_64-linux-gnu/libnfsidmap
lib/x86_64-linux-gnu/libnfsidmap.so.0
lib/x86_64-linux-gnu/libnfsidmap.so.0.3.0
lib/x86_64-linux-gnu/libnfsidmap/nsswitch.so
lib/x86_64-linux-gnu/libnfsidmap/static.so
lib/x86_64-linux-gnu/libnfsidmap/umich_ldap.so
sbin/fsck.nfs
sbin/mount.nfs
sbin/mount.nfs4
sbin/nfsroot
var/lib/nfs
var/lib/nfs/rpc_pipefs
var/lib/nfs/statd
var/lib/nfs/statd/sm

New one, dosent work:

lsinitramfs  initrd.img-4.9.0-8-amd64 |grep -i nfs
sbin/fsck.nfs

attached the fai-make-nfsroot.log

Reiner Schulz

-Ursprüngliche Nachricht-
Von: linux-fai [mailto:linux-fai-boun...@uni-koeln.de] Im Auftrag von Thomas 
Lange
Gesendet: Freitag, 4. Januar 2019 09:05
An: fully automatic installation for Linux 
Betreff: Re: AW: nfsroot: dracut don't know to handle root=

>>>>> On Fri, 4 Jan 2019 07:32:16 +, "Schulz, Reiner"  
>>>>> said:

> According to 
https://fedoraproject.org/wiki/Dracut/Options#Dracut_kernel_command_line_parameters
> and
> https://people.redhat.com/harald/dracut.html#NetworkBoot

> we need pakage " dracut-network" for dracut with nfs
You need dracut-network only inside the nfsroot not on the host itself.

-- 
regards Thomas


fai-make-nfsroot.log.gz
Description: fai-make-nfsroot.log.gz

AW: AW: AW: AW: AW: nfsroot: dracut don't know to handle root=

[Schulz, Reiner]

Works :-)

Reiner Schulz

> -Ursprüngliche Nachricht-
> Von: linux-fai [mailto:linux-fai-boun...@uni-koeln.de] Im Auftrag von
> Thomas Lange
> Gesendet: Dienstag, 8. Januar 2019 09:58
> An: fully automatic installation for Linux 
> Betreff: Re: AW: AW: AW: AW: nfsroot: dracut don't know to handle root=
> 
> >>>>> On Tue, 8 Jan 2019 08:54:45 +, "Schulz, Reiner"  mv.de> said:
> 
> > without "-s" i got:
> 
...
> 
> > livenet
> Here it is!
...
> --
> regards Thomas

AW: AW: AW: nfsroot: dracut don't know to handle root=

[Schulz, Reiner]

> -Ursprüngliche Nachricht-
> Von: linux-fai [mailto:linux-fai-boun...@uni-koeln.de] Im Auftrag von
> Thomas Lange
> Gesendet: Montag, 7. Januar 2019 17:07
> An: fully automatic installation for Linux 
> Betreff: Re: AW: AW: nfsroot: dracut don't know to handle root=
> 
> >>>>> On Mon, 7 Jan 2019 15:25:34 +, "Schulz, Reiner"  mv.de> said:
> 
> > New one, dosent work:
> 
> > lsinitramfs  initrd.img-4.9.0-8-amd64 |grep -i nfs
> > sbin/fsck.nfs
> Is this the initrd from inside the nfsroot?

[RS] Yes. 
 
> This is my output:
> 
> > lsinitrd /srv/fai//nfsroot/boot/initrd.img-4.9.0-8-amd64 |grep nfs
> Image: /srv/fai//nfsroot/boot/initrd.img-4.9.0-8-amd64: 29M
> nfs
> 
> etc/modprobe.d/nfs.conf
> lib/dracut/hooks/cleanup/99-nfsroot-cleanup.sh
> lib/dracut/hooks/cmdline/90-parse-nfsroot.sh
> lib/dracut/hooks/pre-udev/99-nfs-start-rpc.sh
> lib/modules/4.9.0-8-amd64/kernel/fs/nfs
> lib/modules/4.9.0-8-amd64/kernel/fs/nfs/blocklayout
> lib/modules/4.9.0-8-amd64/kernel/fs/nfs/blocklayout/blocklayoutdriver.ko
> lib/modules/4.9.0-8-amd64/kernel/fs/nfs_common
> lib/modules/4.9.0-8-amd64/kernel/fs/nfs_common/grace.ko
> lib/modules/4.9.0-8-amd64/kernel/fs/nfs_common/nfs_acl.ko
> lib/modules/4.9.0-8-amd64/kernel/fs/nfs/filelayout
> lib/modules/4.9.0-8-
> amd64/kernel/fs/nfs/filelayout/nfs_layout_nfsv41_files.ko
> lib/modules/4.9.0-8-amd64/kernel/fs/nfs/flexfilelayout
> lib/modules/4.9.0-8-
> amd64/kernel/fs/nfs/flexfilelayout/nfs_layout_flexfiles.ko
> lib/modules/4.9.0-8-amd64/kernel/fs/nfs/nfs.ko
> lib/modules/4.9.0-8-amd64/kernel/fs/nfs/nfsv2.ko
> lib/modules/4.9.0-8-amd64/kernel/fs/nfs/nfsv3.ko
> lib/modules/4.9.0-8-amd64/kernel/fs/nfs/nfsv4.ko
> lib/modules/4.9.0-8-amd64/kernel/fs/nfs/objlayout
> lib/modules/4.9.0-8-amd64/kernel/fs/nfs/objlayout/objlayoutdriver.ko
> lib/nfs-lib.sh
> lib/x86_64-linux-gnu/libnfsidmap
> lib/x86_64-linux-gnu/libnfsidmap/nsswitch.so
> lib/x86_64-linux-gnu/libnfsidmap.so.0.3.0
> lib/x86_64-linux-gnu/libnfsidmap.so.0 -> libnfsidmap.so.0.3.0
> lib/x86_64-linux-gnu/libnfsidmap/static.so
> lib/x86_64-linux-gnu/libnfsidmap/umich_ldap.so
> sbin/fsck.nfs
> sbin/mount.nfs
> sbin/mount.nfs4 -> mount.nfs
> sbin/nfsroot
> var/lib/nfs
> var/lib/nfs/rpc_pipefs
> var/lib/nfs/statd
> var/lib/nfs/statd/sm

Yes, this is was i expected.

This ist the /usr/sbin/fai-make-nfsroot i used:
# ls -l /usr/sbin/fai-make-nfsroot
-rwxr-xr-x 1 root root 24029 Jan  3 12:44 /usr/sbin/fai-make-nfsroot
# md5sum /usr/sbin/fai-make-nfsroot
1bb5110e68f245a65bdf7a8608bbc608  /usr/sbin/fai-make-nfsroot

Then I added 

echo 'show_modules="yes"' > $NFSROOT/etc/dracut.conf.d/35-debug.conf
to "/usr/sbin/fai-make-nfsroot"

and got this:

Setting up dracut (048+80-1) ...
dracut: Generating /boot/initrd.img-4.9.0-8-amd64
bash
network
ifcfg
dm
dmsquash-live
kernel-modules
kernel-network-modules
overlay-root
qemu
qemu-net
lunmask
rootfs-block
terminfo
udev-rules
base
fs-lib
img-lib
Setting up firmware-misc-nonfree (20161130-4) ...

and:
lsinitramfs /srv/tftp/fai/initrd.img-4.9.0-8-amd64 | grep -i nfs
sbin/fsck.nfs

AW: nfsroot: dracut don't know to handle root=

[Schulz, Reiner]

According to 
https://fedoraproject.org/wiki/Dracut/Options#Dracut_kernel_command_line_parameters
and
https://people.redhat.com/harald/dracut.html#NetworkBoot

we need pakage " dracut-network" for dracut with nfs

On my Server it looks like:

dpkg -l | grep -e 'dracut\|initram'
rc  dracut  
rc  dracut-core 
ii  initramfs-tools 
ii  initramfs-tools-core

How can i install dracut* without switching the servers initramdisk?

In the past we had problems to use dracut to boot, so I dont want to test this 
at my production server

Reiner Schulz

-Ursprüngliche Nachricht-
Von: linux-fai [mailto:linux-fai-boun...@uni-koeln.de] Im Auftrag von Thomas 
Lange
Gesendet: Donnerstag, 3. Januar 2019 15:58
An: fully automatic installation for Linux 
Betreff: Re: nfsroot: dracut don't know to handle root=

>>>>> On Thu, 3 Jan 2019 14:52:34 +, "Schulz, Reiner"  
>>>>> said:

> fai-chboot -v -I  -F -s4.9.0-8-amd64 -u nfs://fai.fai.scm/srv/fai/config  
default

> Booting with it result in an dracut error:
> dracut Warning: dracut: FATAL: Don't know hoe to handle 
'root=/srv/fai/nfsroot.stretch:vers=3'
Maybe dracut is confused because you did not specified the IP of the
server but an NFS option.
Concerning to the man page dracut.cmdline this should work, but maybe
you've found a bug in dracut.

You can enable debugging, by adding rd.debug to the kernel cmdline.

-- 
regards Thomas

nfsroot: dracut don't know to handle root=

[Schulz, Reiner]

Hi!

I tried  to build a new  nfsroot with fai-chboot:

fai-chboot -v -I  -F -s4.9.0-8-amd64 -u nfs://fai.fai.scm/srv/fai/config
  default

Booting with it result in an dracut error:

dracut Warning: dracut: FATAL: Don't know hoe to handle 
'root=/srv/fai/nfsroot.stretch:vers=3'

My pxe line is:

kernel vmlinuz-4.9.0-8-amd64
append initrd=initrd.img-4.9.0-8-amd64 ipv6.disable=1  ip=dhcp  
root=/srv/fai/nfsroot.stretch:vers=3 rootovl monserver=0 
FAI_FLAGS=verbose,sshd,createvt 
FAI_CONFIG_SRC=nfs://10.4.90.94/rschulz/fai/config  FAI_ACTION=install

Any idea where to start debugging?

Reiner Schulz

AW: AW: AW: AW: AW: nfsroot: dracut don't know to handle root=

[Schulz, Reiner]

Sorry.
At the Debain Bug Tracker for dracut, i read a bug ticket which discusses the 
warning " ignored null byte in input " with dracut an bash 4.4
as i remember you wrote that this ist solved in current dracut version.

Reiner Schulz
 
> > At BTS you wrote the BASH thing should resolved??
> I do not understand this.
> --
> regards Thomas

AW: AW: AW: AW: nfsroot: dracut don't know to handle root=

[Schulz, Reiner]

I found this part off fai-make-nfsroot:

if [ $full = 1 ];then
echo 'add_dracutmodules+=" livenet "' > 
$NFSROOT/etc/dracut.conf.d/13-add-cd-support.conf
fslist="nfs lockd ext4"
else
echo 'add_dracutmodules+=" dmsquash-live "' > 
$NFSROOT/etc/dracut.conf.d/13-add-cd-support.conf
fslist="ext4"
fi

for now i called fai-make-nfsroot with "-s" option. I like to keep initrd  small

without "-s" i got:

Setting up dracut (048+80-1) ...
dracut: Generating /boot/initrd.img-4.9.0-8-amd64
bash
network
ifcfg
url-lib
/usr/lib/dracut/modules.d/45url-lib/module-setup.sh: line 33: warning: command 
substitution: ignored null byte in input
dracut-install: ERROR: installing '/etc/ssl/certs/ca-certificates.crt'
dracut: FAILED: /usr/lib/dracut/dracut-install -D 
/var/tmp/dracut.WQwmWg/initramfs /etc/ssl/certs/ca-certificates.crt
/usr/lib/dracut/modules.d/45url-lib/module-setup.sh: line 33: warning: command 
substitution: ignored null byte in input
dracut-install: ERROR: installing '/etc/ssl/certs/ca-certificates.crt'
dracut: FAILED: /usr/lib/dracut/dracut-install -D 
/var/tmp/dracut.WQwmWg/initramfs /etc/ssl/certs/ca-certificates.crt
/usr/lib/dracut/modules.d/45url-lib/module-setup.sh: line 33: warning: command 
substitution: ignored null byte in input
dracut-install: ERROR: installing '/etc/ssl/certs/ca-certificates.crt'
dracut: FAILED: /usr/lib/dracut/dracut-install -D 
/var/tmp/dracut.WQwmWg/initramfs /etc/ssl/certs/ca-certificates.crt
dm
dmsquash-live
kernel-modules
kernel-network-modules
livenet
overlay-root
qemu
qemu-net
lunmask
nfs
rootfs-block
terminfo
udev-rules
base
fs-lib
img-lib
Setting up openssl (1.1.0j-1~deb9u1) ...

At BTS you wrote the BASH thing should resolved??

Reiner Schulz
> -Ursprüngliche Nachricht-
> Von: linux-fai [mailto:linux-fai-boun...@uni-koeln.de] Im Auftrag von
> Thomas Lange
> Gesendet: Dienstag, 8. Januar 2019 09:26
> An: fully automatic installation for Linux 
> Betreff: Re: AW: AW: AW: nfsroot: dracut don't know to handle root=
> 
> 
> I use the same fai-make-nfsroot version. I have these dracut modules
> in my initrd:
> 
> 
> dracut modules:
> bash
> network
> ifcfg
> url-lib
> dm
> dmsquash-live
> kernel-modules
> kernel-network-modules
> livenet
> overlay-root
> qemu
> qemu-net
> lunmask
> nfs
> rootfs-block
> terminfo
> udev-rules
> base
> fs-lib
> img-lib
> 
> 
> livenet is missing.
> 
> 
> --
> regards Thomas

fai-client as RPM, depends "libgraph-perl"

[Schulz, Reiner]

Hi,

i try to "alien" the fai-client deb to rpm for our RHEL Systems.

There ist a depend for libgraph-perl  which provides "perl::Graph::Directed"

I only found this git commit for that:
commit 993b6f1b5f09fdc788eb55777532f5e566238ae7
with note: " Also build-depend on libgraph-perl, so the compile check succeeds. 
"

For what is this used?
AND it is possible to remove the dependency?

libgraph-perl and libfile-lchown-perl are not available for RHEL or EPEL

Reiner Schulz

Mount point is shadowed by stacked devices

[Schulz, Reiner]

Hello FAIs,

I've a problem with setup-storage and RHEL 7

While setup-storage is runing it give " Error in task partition. Code: 710":

Calling task_partition
WARNING: The variable USE_SETUP_STORAGE is not needed any more.
setup-storage is now the default tool for partitioning.
Starting setup-storage 2.2
Using config file: /var/lib/fai/config/disk_config/dvzsn-rb7540
>> Mount point /boot is shadowed by stacked devices  <<

This is your disk_config file:
# example of new config file for setup-storage
#
#

disk_config sda align-at:1024K disklabel:msdos bootable:1 fstabkey:device
primary /boot   1000 xfsrw,noatime createopts="-L BOOT"
primary -   1100-   -   -

disk_config lvm fstabkey:device
vg  vgsys   sda1
vgsys-swap  swap1024swapsw
vgsys-root  /   50G xfs defaults
vgsys-home  /home   10G xfs defaults
vgsys-custom/opt/custom 20  xfs defaults
vgsys-srv   /srv20  xfs defaults
vgsys-var   /var1G-90%  xfs defaults
Error in task partition. Code: 710


With Debian 9 i use:

disk_config disk1 align-at:1M fstabkey:label bootable:1
primary /boot   250 ext2rw,noatime createopts="-L BOOT  
   -m 0"
primary -   500- -   -
disk_config lvm 
vg  vgsys disk1.2   
vgsys-swap  swap1024swapsw
vgsys-root  /   5G  ext4defaults 
createopts="-L ROOT"
and so on...

This works fine
My disk_configs are attached

Any ideas?

Reiner Schulz


DEBIAN_9
Description: DEBIAN_9


dvzsn-rb7540
Description: dvzsn-rb7540

AW: Mount point is shadowed by stacked devices

[Schulz, Reiner]

Argh :-( Stupid me.

Thank you. :-)

Reiner Schulz


> -Ursprüngliche Nachricht-
> Von: linux-fai [mailto:linux-fai-boun...@uni-koeln.de] Im Auftrag von Robert
> Markula
> Gesendet: Montag, 13. Mai 2019 11:20
> An: linux-fai@uni-koeln.de
> Betreff: Re: Mount point is shadowed by stacked devices
> 
> Am 13.05.19 um 11:09 schrieb Schulz, Reiner:
> > This is your disk_config file:
> > # example of new config file for setup-storage
> > #
> > #
> >
> > disk_config sda align-at:1024K disklabel:msdos bootable:1 fstabkey:device
> > primary /boot   1000 xfsrw,noatime createopts="-L 
> > BOOT"
> > primary -   1100-   -   -
> >
> > disk_config lvm fstabkey:device
> > vg  vgsys   sda1
> > vgsys-swap  swap1024swapsw
> > vgsys-root  /   50G xfs defaults
> > vgsys-home  /home   10G xfs defaults
> > vgsys-custom/opt/custom 20  xfs defaults
> > vgsys-srv   /srv20  xfs defaults
> > vgsys-var   /var1G-90%  xfs defaults
> 
> Hi Reiner,
> 
> your LVM goes to the wrong partition. In your LVM config you request the
> LVM to be installed on sda1, which is /boot with a fixed size of 1000
> MiB. Most likely you want LVM to be on sda2 in your case.
> 
> Cheers,
> 
> 
> Robert

AW: fai-diskimage variable "classes" not inherited to fai

[Schulz, Reiner]

# fai-diskimage -v -N -u dvzsn-ra0317 image.raw
ERROR: No classes are defined

From /usr/sbin/fai-diskimage:

182 if [ -z "$classes" ]; then
183 die 7 "No classes are defined"
184 fi

And

218 LC_ALL=C fai $renew -u $hname -s $uri -c$classes install $mnt

So "-c" is needed

I hoped to use fai-diskimage like i do pxe boot.  using class/ * to define 
classes

Grüße 
Reiner 


> -Ursprüngliche Nachricht-
> Von: linux-fai [mailto:linux-fai-boun...@uni-koeln.de] Im Auftrag von Thomas
> Lange
> Gesendet: Mittwoch, 30. Juni 2021 10:32
> An: fully automatic installation for Linux 
> Betreff: Re: fai-diskimage variable "classes" not inherited to fai
> 
> >>>>> On Wed, 30 Jun 2021 08:09:43 +, "Schulz, Reiner"  mv.de> said:
> 
> > How is "-c" concatenate to the classes from config_space/class ?
> 
> > We set a couple of default classes (class/49-always_set_classes) and add
> only the invidual, server specific, classes via class/50-host-classes
> 
> > # fai-diskimage -v -N  -cDEBIAN_10,S2APP  image.raw
> 
> I guess the man page of fai(8) explains it better, since -c and -N
> from fai-diskimage are passed to the fai call itself.
> -N executes the scripts in the class/ subdirectory. -c just sets the
> variable $cmdlineclasses which is then used by class/01-classes. So if
> you do not have the script class/01-classes
> the classes from -c are not used. If you rename 01-classes to
> 99-classes you can change the order of the classes defined by -c.
> 
> BTW, I never use -c and -N at the same time.
> 
> --
> viele Grüße Thomas

fai-diskimage variable "classes" not inherited to fai

[Schulz, Reiner]

Hi

How is "-c" concatenate to the classes from config_space/class ?

We set a couple of default classes (class/49-always_set_classes) and add only 
the invidual, server specific, classes via class/50-host-classes

# fai-diskimage -v -N  -cDEBIAN_10,S2APP  image.raw

Formatting 'image.raw', fmt=raw size=838860800   
  -
   Fully Automatic Installation  -  FAI

   5.10.3~buster1   (c) 1999-2021
   Thomas Lange  
 -
Starting FAI execution - 20210630_092050
Hostname set to debian.example.com

Using configuration files from /etc/fai
Calling task_confdir
FAI_FLAGS:
NO SERVER FOUND FOR FAI_CONFIG_SRC
No monitor daemon defined.
FAI_CONFIG_SRC is set to file:///srv/fai/config 


Using local path /srv/fai/config as config space.   


Calling task_setup
FAI_FLAGS:
Calling task_defclass
fai-class: Defining classes.
Executing /srv/fai/config/class/10-base-classes.
10-base-classes  OK.
Executing /srv/fai/config/class/20-hwdetect.sh.
FAI_VERSION -5.10.3~buster1-
20-hwdetect.sh   OK.
Executing /srv/fai/config/class/49-always_set_classes.
49-always_set_IAMBCUBE_PATCHMGM-classes OK.
Executing /srv/fai/config/class/50-host-classes.
50-host-classes  OK.
Executing /srv/fai/config/class/51-STEP.
51-STEP  OK. 
List of all classes:  DEFAULT LINUX X86_64 NETWORK SUDO SSH SSL POSTFIX NTP 
SYSLOG SHOREWALL CUSTOM_RULES SNMP IAMBCUBE PATCHMGM NRPE FAICLIENT LIMA 
KILLIDLE DEEPSEC RUNONCE GRUB_PC debian.example.com LAST
Calling task_defvar
Executing DEFAULT.var
++ LOGREMOTEDIR=/var/log/fai/remotelog
++ AINSL_TARGET=
...
Calling task_action
FAI_ACTION: install
Performing FAI installation. All data may be overwritten!
Calling task_install
Calling task_partition
No matching disk_config found

Error in task partition. Code: 710
Traceback: task_error task_partition task task_install task task_action task 
main
...

# cat /srv/fai/config/disk_config/DEBIAN_10
# example of new config file for setup-storage
#
#

disk_config disk1 align-at:1M fstabkey:label bootable:1
primary /boot   499 ext2rw,noatime createopts="-L BOOT  
   -m 0"
primary -   500- -   -

disk_config lvm fstabkey:label

vg  vgsys disk1.2
#createopts= -L Label in fstag, 
-m root reserve
vgsys-swap  swap4096swapsw
vgsys-root  /   7G-99%  ext4defaults 
createopts="-L ROOT"
vgsys-home  /home   50  ext4defaults 
createopts="-L HOME -m 0"
vgsys-postgres  -   50  ext4defaults
 createopts="-L POSTGRES -m 0"
vgsys-jboss -   20  ext4-
createopts="-L JBOSS-m 0"
vgsys-custom/opt/custom 20  ext4defaults 
createopts="-L CUSTOM-m 0"
vgsys-tomcat-   20  ext4-
createopts="-L TOMCAT   -m 0"
vgsys-deploy-   20  ext4-
createopts="-L DEPLOY   -m 0"
vgsys-srv   /srv20  ext4defaults 
createopts="-L SRV  -m 0"
vgsys-var   /var8G  ext4defaults 
createopts="-L VAR  -m 0"
vgsys-mysql -   50  ext4defaults
 createopts="-L MYSQL-m 0"
vgsys-data  -   50  ext4defaults
 createopts="-L DATA -m 0"
vgsys-backup-   20  ext4defaults
createopts="-L BACKUP   -m

cat FAI_CLASSES
DEFAULT
LINUX
X86_64
NETWORK
SUDO
SSH
SSL
POSTFIX
NTP
SYSLOG
SHOREWALL
CUSTOM_RULES
SNMP
IAMBCUBE
PATCHMGM
NRPE
FAICLIENT
LIMA
KILLIDLE
DEEPSEC
RUNONCE
GRUB_PC
debian.example.com
LAST

grep cmdlineclasses variables.log
cmdlineclasses='DEBIAN_10 S2APP'


Reiner Schulz

AW: LUKS, "no device found"

[Schulz, Reiner]

> Sorry for the dumb question, but where would I add the "-d" flag?

If fai stop with an error, you can go to a second tty  via "Alt-F2" and type 
there any command you like to test.

first check if the fai configspace is mountet

you can do a 
ls -l /var/lib/fai/(config/disk_config/

and a

setup-storage -d

Reiner

how works flag_menu and profile

[Schulz, Reiner]

Hi,

i like to build a "Client Installation Menu" with a profile, but it is not 
shown after select "Client standalone installation - select installation type 
from menu"

I do a grep  for "flag_menu" and  "profile" in /usr/sbin/fai* and 
/usr/lib/fai/* but cant find anything. So how dose this work?

we use a higthly customized fai server for years, so may be we damage some 
concepts, but last week we upgrade from 3.8… to 5.3.6 and remove much of our 
customizing.

In config/class i created a „fai-cd.profile“, see below.

In grub.cfg ist still original:

linux   /boot/vmlinuz FAI_FLAGS="menu,verbose,createvt" FAI_ACTION


thank you for your help,

Reiner


fai-cd.profile:
--
Default: Sysinfo

Name: Debian 8 im LAN
Description: Debian Jessie im LAN
Short: Debian 8 (Codename Jessie) mit LAN
Long: Debian 8 (Codename Jessie) mit LAN Konfiguration fuer LAN
Classes: DEBAIN_8 LAN

Name: Debian 8 im NET
Description: Debian Jessie im NET
Short: Debian 8 (Codename Jessie) mit NET
Long: Debian 8 (Codename Jessie) mit LAN Konfiguration fuer NET
Classes: DEBAIN_8 NET

Name: Debian 8 im INTRANET
Description: Debian Jessie im INTRANET
Short: Debian 8 (Codename Jessie) mit INTRANET
Long: Debian 8 (Codename Jessie) mit LAN Konfiguration fuer INTRANET
Classes: DEBAIN_8 INTRANET




Name: RHEL 7 im LAN
Description: RHEL 7 im LAN
Short: RHEL 7 mit LAN
Long: RHEL 7 mit LAN Konfiguration fuer LAN
Classes: RHEL_7 LAN

Name: RHEL 7 im NET
Description: RHEL 7 im NET
Short: RHEL 7 mit NET
Long: RHEL 7  mit LAN Konfiguration fuer NET
Classes: RHEL_7 NET

Name: RHEL 7 im INTRANET
Description: RHEL 7 im INTRANET
Short: RHEL 7 mit INTRANET
Long: RHEL 7 mit LAN Konfiguration fuer INTRANET
Classes: RHEL_7 INTRANET



Name: Sysinfo
Description: Show defailed system information
Short: Show detailed hardware and system  information
Long: Execute a lot of commands for collecting system information
Classes: SYSINFO
-

AW: Install Fedora CoreOS using FAI

[Schulz, Reiner]

For our OpenShift we use http to load the PXE file:

/var/lib/tftpboot/gpxelinux.0

dhcpd.conf:
filename "gpxelinux.0";

nginx:
$ ls -lh /usr/share/nginx/html/rhcos-4.2.18-x86_64-*
  63M 11. Feb 17:04 
/usr/share/nginx/html/rhcos-4.2.18-x86_64-installer-initramfs.img
 7,8M 11. Feb 17:04 /usr/share/nginx/html/rhcos-4.2.18-x86_64-installer-kernel
 703M 11. Feb 17:04 /usr/share/nginx/html/rhcos-4.2.18-x86_64-metal-bios.raw.gz

Reiner Schulz


-Ursprüngliche Nachricht-
Von: linux-fai [mailto:linux-fai-boun...@uni-koeln.de] Im Auftrag von Andrew 
Ruthven
Gesendet: Sonntag, 19. April 2020 07:37
An: fully automatic installation for Linux 
Betreff: Install Fedora CoreOS using FAI

Hey,

I've spent the last couple of days trying to deploy Fedora CoreOS to
some physical hardware for a colleague using the official PXE
installer. It wasn't very pleasant, and just wouldn't work reliably.

A few interesting aspects I encountered:

1) The PXE installer for it has a 618MB initrd file. This takes quite
   a while to transfer via tftp!
2) It can't build software RAID for the main install device, and it 
   seems very finicky to build other RAID sets for other partitions. 
3) And, well, I just kept having problems where the built systems 
   would hang during boot for no obvious reason.
4) The time to do an installation was incredibly long.

During the night I got feed up with that and wrote a FAI profile that'd
do it instead. I can now use setup-storage using our standard
disk_config files. A big bonus is that a rebuild, timed from typing
reboot to a fresh login prompt is 10 minutes - and this is on physical
hardware so includes BIOS POST and RAID controller set up, twice each.

The FAI Profile I developed for this is located here:
  https://github.com/catalyst-cloud/fai-profile-fedora-coreos

I thought this might be of interest to other people, and is potentially
a good example of how we can easily deploy other operating systems
using FAI.

Cheers,
Andrew

-- 
Andrew Ruthven, Wellington, New Zealand
and...@etc.gen.nz  | linux.conf.au 2021, Canberra, AU
Catalyst Cloud:|   http://lca2021.linux.org.au/
   https://catalystcloud.nz|

AW: Driver replacement

[Schulz, Reiner]

Hi!

For such situations we designed a RunOnce.Service: It runs all scripts  from a 
hook-dir at boottime  and then move it away.
Or you can check the connectivity of a specific IP-address and then run the 
scripts.

And sorry, im not allowed to share our inhouse knowledge

Reiner

Von: linux-fai [mailto:linux-fai-boun...@uni-koeln.de] Im Auftrag von Pasquale 
Cantiello
Gesendet: Donnerstag, 25. Februar 2021 11:14
Cc: fully automatic installation for Linux 
Betreff: Re: Driver replacement

Dear John,
thanks for your answer.
Putting a script in the /srv/fai/config/scripts/ is the way I was trying but, 
if the system boots with the nouveau driver already installed, the sequence to 
install correctly the new one is:

- blacklist the nouveau
- reboot
- install the proper nvidia driver
- reboot again
- continue with software installation

And this sequence, I think, cannot be fully automated with those scripts.
So I have been searching for a way to prevent the nouveau installation since 
the beginning. I will study the fai-scripts in order to better understand how 
this happens.

Best regards

  Pasquale

---
ing. PhD Pasquale Cantiello
Istituto Nazionale di Geofisica e Vulcanologia
Sezione di Napoli - Osservatorio Vesuviano
Via Diocleziano, 328 - 80124 Napoli
Tel. 081-6108.332


Il giorno mer 24 feb 2021 alle ore 14:15 John G Heim 
mailto:jh...@math.wisc.edu>> ha scritto:
FAI works a lot like an installation you'd do "by hand". You boot from a
live image, partition the hard drive, install a base system via
debootstrap then chroot to do the rest of the installation steps
(install a kernel, install packages, configure grub). So, if you want to
blacklist a module, you have to do it on the new system, not on the live
boot image. In other words, in your case, you'd have to fcopy the module
configuration files to the new system after the base system is
installed. This is done by putting a script in the scripts folder of
your FAI config root. By default this would be /srv/fai/config/scripts/.

On 2/24/21 4:20 AM, Pasquale Cantiello wrote:
> Hi all
>
> I'm new to fai (only two weeks) and trying to use it to install a
> cluster with a front-end and 10 compute nodes. At present stage I am
> able to install all machines with related software and little
> customization from the faiserver with almost no problem.
>
> Now, since the nodes have a GPU card I want to install the nvidia driver
> and related sdk to the frontend and all nodes. I've downloaded all the
> files (.run file for driver and .deb files for sdk) on faiserver and put
> them in nfsroot in order to launch the installation on the nodes.
>
> My problems are now:
> How to prevent the installation of the nouveau driver on nodes? This
> will conflict with the new driver. I've also put a modeprobe.conf file
> with blacklist in /nfsroot/etc/modeprobe.d/ but with no success.
>
> And, how to use the PRELOAD or PRELOADRM command in the package
> configuration to install sdk from nfsroot? I've found no samples and
> tried all combinations...
>
> Thanks in advance to all who can help me.
>
> Best regards
>   Pasquale
>
> ---
> ing. PhD Pasquale Cantiello
> Istituto Nazionale di Geofisica e Vulcanologia
> Sezione di Napoli - Osservatorio Vesuviano
> Via Diocleziano, 328 - 80124 Napoli
> Tel. 081-6108.332

setup-storage, liks:"passwd" from variable?

[Schulz, Reiner]

Hi there.

The subject named it:

How can i set the luks:"passwd" without write it into the disk_config file?

Reiner

fai-diskimage "ERROR: No classes are defined"

[Schulz, Reiner]

Hi Thomas,

Now with fai 6.0.2 i use

fai-diskimage --cspace file:///adm/rschulz/fai/config -v -N --size 25G -u 
x-ra5285 -ra5285.raw

and got:

ERROR: No classes are defined

looking on the fai-diskimage  code at lines

182 if [ -z "$classes" ]; then
183 die 7 "No classes are defined"
184 fi
185
186 : ${cspace:=/srv/fai/config}
187 # if cspace starts with /, add prefix file://
188 uri=${cspace/#\//file:///}

First check for "$classes" and then set the cspace?
Wouldnt it better to set first the cspace and then check for classes?


Reiner

AW: fai-diskimage "ERROR: No classes are defined"

[Schulz, Reiner]

Im sorry, my fault...

Reiner

-Ursprüngliche Nachricht-
Von: linux-fai  Im Auftrag von Thomas Lange
Gesendet: Dienstag, 23. Mai 2023 13:52
An: fully automatic installation for Linux 
Betreff: Re: fai-diskimage "ERROR: No classes are defined"

>>>>> On Tue, 23 May 2023 07:48:08 +, "Schulz, Reiner"  
>>>>> said:

> Hi Thomas,
> Now with fai 6.0.2 i use
> fai-diskimage --cspace file:///adm/rschulz/fai/config -v -N --size 25G -u 
x-ra5285
> -ra5285.raw
> and got:
> ERROR: No classes are defined

> looking on the fai-diskimage  code at lines
> 182 if [ -z "$classes" ]; then
> 183 die 7 "No classes are defined"
> 184 fi
My code looks different:

if [ -z "$classes" -a -z "$renew" ]; then
die 7 "No classes are defined. Use -c or -N."
fi

Are you reall using the 6.0.2 version?


This change was done in 116a8709bc698344eaf5d00c109a8737d5273de6
-- 
regards thomas

fai-diskimage and /dev/loop0

[Schulz, Reiner]

Hi there

I am on my first steps with fai-diskimage from fai 5.8.4
I try to  to generate a debian 12 image to boot on vmware esxi

but grub ist installed on /dev/loop0 and in fstab "/" is set to /dev/loop0p1

so systemd-mount tries to mount /dev/loop0p1

what do i wrong? :)

cat disk_var.sh
SWAPLIST=${SWAPLIST:-""}
BOOT_DEVICE=${BOOT_DEVICE:-"/dev/loop0"}
ROOT_PARTITION=${ROOT_PARTITION:-/dev/loop0p2}
BOOT_PARTITION=${BOOT_PARTITION:-/dev/loop0p1}

In shell log the GRUB_PC/10-setup script output:

...
++ chroot /tmp/fai-diskimage.svkFCT grub-probe -tdrive -d /dev/loop0
+ GROOT='(hostdisk//dev/loop0)'
+ [[ /dev/loop0 =~ /dev/md ]]
+ [[ (hostdisk//dev/loop0) =~ hostdisk ]]
+ cat
+ chroot /tmp/fai-diskimage.svkFCT grub-install --no-floppy 
--modules=part_msdos /dev/loop0
Installing for i386-pc platform.
Installation finished. No error reported.
+ '[' 0 -eq 0 ']'
+ echo 'Grub installed on hostdisk /dev/loop0'
Grub installed on hostdisk /dev/loop0
+ rm /tmp/fai-diskimage.svkFCT/boot/grub/device.map
+ chroot /tmp/fai-diskimage.svkFCT update-grub
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-6.1.0-9-amd64
Found initrd image: /boot/initrd.img-6.1.0-9-amd64
...

Reiner

AW: fai-diskimage and /dev/loop0

[Schulz, Reiner]

fstabkey:uuid

thats is it

Reiner 

-Ursprüngliche Nachricht-
Von: linux-fai  Im Auftrag von Thomas Lange
Gesendet: Dienstag, 16. Mai 2023 14:11
An: fully automatic installation for Linux 
Betreff: Re: fai-diskimage and /dev/loop0

>>>>> On Tue, 16 May 2023 11:43:45 +, "Schulz, Reiner"  
>>>>> said:

> Hi there
> I am on my first steps with fai-diskimage from fai 5.8.4

> but grub ist installed on /dev/loop0 and in fstab „/“ is set to 
/dev/loop0p1
> so systemd-mount tries to mount /dev/loop0p1
> what do i wrong? J
Maybe your FAI version is too old?
Or do your disk_config uses the device name instead of an UUID for the fstab 
entries? Please try to use the option fstabkey:uuid in your disk_config.

--
ragrds Thomas