AW: AW: cryptsetup disk_config example(s) ?

No, we use no encryption for the system filesystems, only for application file systems Reiner -Ursprüngliche Nachricht- Von: linux-fai Im Auftrag von Andrew Ruthven Gesendet: Mittwoch, 18. Dezember 2024 12:45 An: linux-fai@uni-koeln.de Betreff: Re: AW: cryptsetup disk_config example(s

Re: AW: cryptsetup disk_config example(s) ?

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

AW: cryptsetup disk_config example(s) ?

Hi! here a snip of the solution i use: disik_config: 5 disk_config disk1 align-at:1M fstabkey:label bootable:1 6 primary /boot 1024xfs defaults createopts="-L BOOT" 7 primary - 1025- - - 8 disk_config

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

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 +, "Schu

AW: fai-diskimage and /dev/loop0

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"

AW: FAI from CD with static IP address; $NIC1 is not defined

Hi Thomas, sorry for the late reply - i was away and then it took some time to get back to the issue. I don't know what I did wrong initially, but everything is working now and NIC1 is always set in boot.log. I am using the following parameters for GRUB: * HOSTNAME (without FQDN) * DOMAIN (I a

AW: LUKS, "no device found"

> 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-

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

> On Thu, 1 Jul 2021 09:24:37 +, "Schulz, Reiner" > said: > # 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 Oo

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

# 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-

AW: Driver replacement

Hello Pasquale, if your compute nodes are identical and all of them need the Nvidia driver, you can use a basefile that already has Nouveau removed and Nvidia installed. Then there is no need for a Nvidia installation script at all. Just as an unconventional idea… Best, Frank -- Frank Morawiet

AW: Driver replacement

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 [

AW: dracut error during nfsroot update

> The nfsroot is based on Debian 10. I have found a similar problem on this > list from 2017 > (https://lists.uni-koeln.de/pipermail/linux-fai/2017-June/011735.html

RE: AW: AW: fai-make-nfsroot failing (was: AW: fai-make-nfsroot failing with dracut version 050+35-2)

Thanks for your advice, Thomas. With the fai-project.org repos added on the install server followed by an update of fai to 5.9.4 "fai-setup -v -f" went fine and completed without errors! Regards, Frank -- Frank Morawietz This message and any attachment are confidential and may be privileged o

Re: AW: AW: fai-make-nfsroot failing (was: AW: fai-make-nfsroot failing with dracut version 050+35-2)

> On Mon, 18 May 2020 14:25:06 +, Frank Morawietz > said: > There is no FAI newer than this in the Debian default repos, right? > Do I need to add the fai-project.org repos to get a newer version? Have a look at https://tracker.debian.org/pkg/fai Debian stable has 5.8.4, bu

AW: AW: fai-make-nfsroot failing (was: AW: fai-make-nfsroot failing with dracut version 050+35-2)

Hi Thomas, > Are you sure, you are using fai 5.9.4 on your fai server, where you > call fai-make-fnsroot? What's the output of this command? > $ dpkg -l |grep fai- ooops, you are right - I have version 5.8.4 installed. Sorry, my fault. ☹ There is no FAI newer than this in the Debian default re

Re: AW: fai-make-nfsroot failing (was: AW: fai-make-nfsroot failing with dracut version 050+35-2)

> On Mon, 18 May 2020 12:10:43 +, Frank Morawietz > said: >> > I am currently installing a brand new FAI server on Debian >> > buster (10.4) with FAI 5.9.4 from the Debian repos. Are you sure, you are using fai 5.9.4 on your fai server, where you call fai-make-fnsroot? What's

AW: fai-make-nfsroot failing (was: AW: fai-make-nfsroot failing with dracut version 050+35-2)

Hello Thomas, thanks for you offer. >> I am currently installing a brand new FAI server on Debian buster (10.4) > with FAI 5.9.4 from the Debian repos. > >> Dracut is missing the 'livenet' module and therefor fails to create the > initrd. >> I re-ran fai-make-nfsroot , re-installed

Re: fai-make-nfsroot failing (was: AW: fai-make-nfsroot failing with dracut version 050+35-2)

> On Fri, 15 May 2020 13:48:16 +, Frank Morawietz > said: > I am currently installing a brand new FAI server on Debian buster (10.4) with FAI 5.9.4 from the Debian repos. > Dracut is missing the 'livenet' module and therefor fails to create the initrd. > I re-ran fai-

fai-make-nfsroot failing (was: AW: fai-make-nfsroot failing with dracut version 050+35-2)

Dear all, I am currently installing a brand new FAI server on Debian buster (10.4) with FAI 5.9.4 from the Debian repos. Following the FAI guide, currently at chapter 4.2 "Create the nfsroot". When fai-setup is calling fai-make-nfsroot , several errors are logged. I can fix most of them from

Re: AW: Install Fedora CoreOS using FAI

On Mon, 2020-04-20 at 22:40 +0200, Rémy Dernat wrote: > Hi > > I have a couple of questions. > > - Do you deploy this system to operate a k8s cluster ? No, I was requested to build this system, which will be a pet, to run some docker containers for Gitlab & Prometheus. I have just raised some

Re: AW: Install Fedora CoreOS using FAI

Hi I have a couple of questions. - Do you deploy this system to operate a k8s cluster ? - If so, I imagine you disable the swap (?). But why are you deploying this stack over bare-metal, with no VM ? - Why not using kickstart, which is the redhat standard tftp system ? (I mean, I am a big of FAI

Re: AW: Install Fedora CoreOS using FAI

Hey, Nice. I had considered using HTTP, but didn't want to deviate from the "recommended" approach. Well. Up until I decided to completely the approach. ;) That is also a much smaller initrd! The main reason I changed was to be able to configure the disk layout, the much faster build was a very

AW: Install Fedora CoreOS using FAI

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 1

AW: get-boot-info

> You issue is now fixed Great, thank you Thomas! -- Frank Morawietz This message and any attachment are confidential and may be privileged or otherwise protected from disclosure. If you are not the intended recipient, you must not copy this message or attachment or disclose the contents to an

AW: get-boot-info

> But in a particular case when interface with a proper IP setting (with > default gw) is happen to the second > interface and there is a dummy IP setting on the first active interface, > variables like IPADDR, NETMASK, > BROADCAST are filled and erroneously used with dummy IP info of the first

AW: AW: AW: PXE boot with UEFI

>>> You can troubleshoot the issue using a tftp client on one >>> of your test boxes. >> Nice idea! I booted the client into Knoppix, installed the tftp-hpa client >> and tested. >> I could successfully get every single file from the server in /srv/tftp/fai/ >> . >> Worked without any issue and

AW: AW: PXE boot with UEFI

> I had problems with my thinkpad in the past when booting UEFI. First I > needed the newest syslinux binary, in those days I was still running > stretch. Then, my thinkpad T480 needs a long time and shows several > transmision error (currently I cannot say which exact messages) when > doing UEFI

Re: AW: AW: PXE boot with UEFI

On 12/5/19 5:33 AM, Frank Morawietz wrote: You can troubleshoot the issue using a tftp client on one of your test boxes. Nice idea! I booted the client into Knoppix, installed the tftp-hpa client and tested. I could successfully get every single file from the server in /srv/tftp/fai/ . W

AW: AW: PXE boot with UEFI

> To clarify, this client can successfully tftp the pxelinux.0 file over > when configured for legacy BIOS mode? Yes, exactly. This works. > This looks suspiciously like a config problem on the server > (firewall?). The client is connected via direct cross link TP cable to the server and the fi

Re: AW: PXE boot with UEFI

On 12/4/19 1:40 AM, Frank Morawietz wrote: Some additional information: I picked the boot files from the local syslinux installation: - /usr/lib/syslinux/modules/efi32/syslinux.c32 --> syslinux32.efi - /usr/lib/syslinux/modules/efi64/syslinux.c32 --> syslinux64.efi - /usr/lib/syslinux/modu

Re: AW: PXE boot with UEFI

> On Wed, 4 Dec 2019 09:40:45 +, Frank Morawietz > said: > So it looks like the UEFI tftp connection refused error happened where ldlinux should be transferred. > Is there anything else I could examine to diagnose further? I had problems with my thinkpad in the past when bo

AW: PXE boot with UEFI

> have you considered tcp wrappers ? Thanks for your input. In my opinion, installation in legacy mode shouldn't work either if something like tcp wrappers or a firewall would hinder the installation in UEFI mode. IP addresses and ports would be the same. Some additional information: I picked

Re: AW: PXE boot with UEFI

On 12/3/19 2:50 AM, Frank Morawietz wrote: Many thanks Steffen and Merlin for your configuration details! I learned a lot already and I believe that we are on the right track. I included your suggestions into my dhpcd.conf . According to the log output below it seems to select the correct f

Re: AW: PXE boot with UEFI

On Tue, 3 Dec 2019, Frank Morawietz wrote: Many thanks Steffen and Merlin for your configuration details! I learned a lot already and I believe that we are on the right track. I included your suggestions into my dhpcd.conf . According to the log output below it seems to select the correct fil

AW: PXE boot with UEFI

Many thanks Steffen and Merlin for your configuration details! I learned a lot already and I believe that we are on the right track. I included your suggestions into my dhpcd.conf . According to the log output below it seems to select the correct file now. But I still could not yet get it to wo

AW: AW: fcopy and /dev/null

>You have to use >mknod --mode=666 $target/dev/null c 1 3 That was the key, now the error message is gone. Thanks! Frank -- Frank Morawietz IT Systems Administrator Global Computational Chemistry & Biology Healthcare | Discovery Development Technologies Merck Merck Healthcare KGaA | Frankfurte

Re: AW: fcopy and /dev/null

> On Tue, 17 Sep 2019 12:54:48 +, Frank Morawietz > said: > I added the mknod command ("mknod --mode=666 /dev/null c 1 3") to the repository hook, right before calling fcopy the first time. You have to use mknod --mode=666 $target/dev/null c 1 3 Maybe /dev/null is needed in the

AW: fcopy and /dev/null

>> But every time fcopy is used, it complains… >> “Can’t open /dev/null: No such file or directory” >I guess this comes from a redirect of some output to /dev/null. >I've checked the basefiles on >http://fai-project.org/download/basefiles/ > >and the debian, centos, Ubuntu basefiles have

AW: openSUSE starting aid

Hello Thomas and Vinzenz, thanks a lot for providing starting information and pointing me into the right directions. Also thanks for offering more support. Especially the Tuxedo config space is very useful and will provide me with lots of important details and templates. Very much appreciated!

AW: Mount point is shadowed by stacked devices

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 dev

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

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: dr

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

> On Tue, 8 Jan 2019 09:07:14 +, "Schulz, Reiner" > said: > 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 dra

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

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

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

> On Tue, 8 Jan 2019 08:54:45 +, "Schulz, Reiner" > said: > without "-s" i got: > Setting up dracut (048+80-1) ... > /usr/lib/dracut/modules.d/45url-lib/module-setup.sh: line 33: warning: command substitution: ignored null byte in input > dracut-install: ERROR: inst

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

. 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

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

> -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 roo

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

> On Tue, 8 Jan 2019 08:20:00 +, "Schulz, Reiner" > said: > lsinitramfs /srv/tftp/fai/initrd.img-4.9.0-8-amd64 | grep -i nfs > sbin/fsck.nfs I use lsinitrd, not lsinitramfs -- regards Thomas

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 m

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

> On Mon, 7 Jan 2019 15:25:34 +, "Schulz, Reiner" > 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? This is my output: > lsinitrd /srv/fai//nfsroot/boot/initrd.img-4.9.0-8-am

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

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

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 dracu

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

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

AW: Interface Naming inside nfsroot

Hello Dennis, we also had to change things like order and name of our network devices, which we solved using a udev rule. You cound write a role which changes to name from ens160[...] to eth0 and so on. Details can be found under https://lists.uni-koeln.de/pipermail/linux-fai/2017-March/011640

AW: Alter initrd inside normal fai workflow

Hi Thomas, thanks for the hint. We tried it that way (running our hook which adds the udev rule and run dkpg-reconfigure dracut inside nfs root). It didn't work. When extracting the initrd no rule appeared. After checking dracut we recognized that dracut needs custom udev rules at a special l

Re: AW: ACLs on /target/ while installation causing trouble

> On Tue, 6 Sep 2016 16:18:46 +0200 (MEST), "steven.w...@t-online.de" > said: > Hi Thomas, > we used version 1.29 . Ah, this is in testing and sid. Thanks for the info. -- regards Thomas

AW: ACLs on /target/ while installation causing trouble

Hi Thomas, we used version 1.29 . # (FAI) root@fai5-server:~# chroot /srv/fai/nfsroot/fai5/ tar --version tar (GNU tar) 1.29 Copyright (C) 2015 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later . This is free software: you are free to

AW: Fai-make-nfsroot setup-failure fai-server

Hey,

Re: AW: Fai-make-nfsroot setup-failure fai-server

> On Fri, 22 Jul 2016 13:42:28 +, "Bosch, Fabian (BITBW)" > said: > I did add "deb http://fai-project.org/download jessie koeln" to my sources.list updated apt and it didn't work either. You must add this to /etc/fai/apt/sources.list ^^^ ^^^ That's important! -- rega

Re: AW: Fai-make-nfsroot setup-failure fai-server

> On Mon, 25 Jul 2016 06:52:54 +, "Bosch, Fabian (BITBW)" > said: >> Please call fai-make-nfsroot -v and put the output onto paste.debian.net. Then I will have a look at it. > paste.debian.net/784794 You have two options. either remove dracut-config-generic from /etc/fai/NF

AW: Fai-make-nfsroot setup-failure fai-server

> Please call fai-make-nfsroot -v and put the output onto paste.debian.net. > Then I will have a look at it. paste.debian.net/784794 Thank you very much! Regards, Fabian

Re: AW: Fai-make-nfsroot setup-failure fai-server

> On Fri, 22 Jul 2016 13:42:28 +, "Bosch, Fabian (BITBW)" > said: > I did add "deb http://fai-project.org/download jessie koeln" to my sources.list updated apt and it didn't work either. > Sorry :( Please call fai-make-nfsroot -v and put the output onto paste.debian.net. Th

AW: Fai-make-nfsroot setup-failure fai-server

I did add "deb http://fai-project.org/download jessie koeln" to my sources.list updated apt and it didn't work either. Sorry :( -Ursprüngliche Nachricht- Von: linux-fai [mailto:linux-fai-boun...@uni-koeln.de] Im Auftrag von Thomas Lange Gesendet: Freitag, 22. Juli 2016 15:39 An: fully

AW: example network script will misname interface if installing stretch

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 Re

AW: AW: AW: AW: AW: Problem with virtio network boot

Hello everyone, I could fix the problem. And here's the solution if you also got the problem: VirtIO driver is included in the initrd, but when the VM boot into dracut the "dhclient" command fails. This happens, because of bad checksums with special software. Currently we use qemu/kvm on out vi

Re: AW: AW: AW: AW: Problem with virtio network boot

> On Tue, 14 Jun 2016 16:23:41 +, Denny Bortfeldt > said: > Default timeout are 20 seconds, this is way enough. DHCPOFFERS will be send out but VM don't respect them. > This problem only occur with Dracut and virtio network card. You can test the nfsroot from http://fai-proj

AW: AW: AW: AW: Problem with virtio network boot

Default timeout are 20 seconds, this is way enough. DHCPOFFERS will be send out but VM don't respect them. This problem only occur with Dracut and virtio network card. With FAI 3 everything worked fine.

Re: AW: AW: AW: Problem with virtio network boot

> On Tue, 14 Jun 2016 16:04:14 +, Denny Bortfeldt > said: > Screenshot attached: > https://data.bortfeldt.net/f/84d501dcd7/ You can use rd.net.timeout.ifup= to use a bigger timeout. See man dracut.cmdline for more info -- regards Thomas

AW: AW: AW: Problem with virtio network boot

Screenshot attached: https://data.bortfeldt.net/f/84d501dcd7/ Don't know why the interface can't get started. Jun 14 17:57:45 s110077 dnsmasq-dhcp[1840]: DHCPDISCOVER(eth1) 52:54:00:81:ff:41 Jun 14 17:57:45 s110077 dnsmasq-dhcp[1840]: DHCPOFFER(eth1) 10.0.100.108 52:54:00:81:ff:41 Jun 14 17:57:

Re: AW: AW: Problem with virtio network boot

> On Tue, 14 Jun 2016 15:51:00 +, Denny Bortfeldt > said: > The first DHCP request for pxe-boot-menu is received successfully. After that the initrd and stuff is loaded. > When dracut is running a dhcp again, then the dhcp fails - I also don't see any traffic anymore from t

AW: AW: Problem with virtio network boot

>> but only DHCP is not working Yes and no. It's only not working when booting with virtio network card when dracut is running. The first DHCP request for pxe-boot-menu is received successfully. After that the initrd and stuff is loaded. When dracut is running a dhcp again, then the dhcp fails -

Re: AW: Problem with virtio network boot

> On Tue, 14 Jun 2016 15:35:13 +, Denny Bortfeldt > said: > Drivers are included. OK. IMO the NIC is activated (so , there's is one eth0), but only DHCP is not working. Maybe your network setup is the cause the the problem, not the kernel driver. > -Ursprüngliche Nachri

AW: Problem with virtio network boot

Hey, /srv/tftp/fai# lsinitrd initrd.img-3.16.0-4-amd64 | grep virtio -rw-r--r-- 1 root root25872 Apr 9 00:54 lib/modules/3.16.0-4-amd64/kernel/drivers/block/virtio_blk.ko -rw-r--r-- 1 root root51376 Apr 9 00:54 lib/modules/3.16.0-4-amd64/kernel/drivers/net/virtio_n

AW: Problem with DNS DHCP-Name

Thank you Thomas! -Ursprüngliche Nachricht- Von: linux-fai [mailto:linux-fai-boun...@uni-koeln.de] Im Auftrag von Thomas Lange Gesendet: Montag, 13. Juni 2016 15:19 An: fully automatic installation for Linux Betreff: Re: Problem with DNS DHCP-Name > On Mon, 13 Jun 2016 12:52:54 +

AW: AW: /boot/grub/ascii.pf2 not found

I use legacy boot. (my hardware is a Toshiba Tecra Laptop) Regards Werner -Ursprüngliche Nachricht- Von: linux-fai [mailto:linux-fai-boun...@uni-koeln.de] Im Auftrag von Thomas Lange Gesendet: Mittwoch, 4. Mai 2016 16:15 An: fully automatic installation for Linux Betreff: Re: AW: /boot

AW: /boot/grub/ascii.pf2 not found

Hello, there is no error in the log-files concerning grub. Especially in shell.log: . = shell: GRUB_PC/10-setup = Generating grub configuration file ... Found linux image: /boot/vmlinuz-3.16.0-4-amd64 Found initrd image: /boot/initrd.img-3.16.0-4-amd64 Found memtest86+ imag

Re: AW: /boot/grub/ascii.pf2 not found

> On Wed, 4 May 2016 16:12:10 +0200, "Werner Pommerer" > said: > there is no error in the log-files concerning grub. Especially in shell.log: Are you using an UEFI Bios or do you use legacy boot. -- regards Thomas

AW: Logical Volumes on virtual drives

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_co

AW: AW: How to fix 'mount.nfs: Connection timed out'

> Yes. but you are installing initramfs-tools into the nfsroot. That's wrong. Please check why this is done. initramfs-tools is deprecated when using FAI. FAI uses dracut instead. I guess you have some old /etc/fai/NFSROOT configuration. Ok that was my mistake. I read "FAI packages from the offici

Re: AW: How to fix 'mount.nfs: Connection timed out'

> On Thu, 3 Mar 2016 20:22:24 +0100, "Robert Rettig" > said: > root@faiserver:~# fai-make-nfsroot -fv > There are no errors (see attached log ). Yes. but you are installing initramfs-tools into the nfsroot. That's wrong. Please check why this is done. initramfs-tools is deprecat

AW: How to fix 'mount.nfs: Connection timed out'

> Try to rebuild with fai-make-nfsroot -fv Then check if there are any errors in the log file. I rebuild it as suggested with: root@faiserver:~# fai-make-nfsroot -fv There are no errors (see attached log ). I rebooted the demohost and it hangs again in initramfs prompt http://screencast.com/t/Td

Re: AW:

> On Thu, 10 Dec 2015 16:56:55 +0100 (MET), "steven.w...@t-online.de" > said: > thanks for your help. I would like to try the build a debian jessie nsf root and a debian jessie initrd, which will install the Ubuntu 14.04 LTS. > As I understand I have to add jessie sources insid

AW:

Hi Thomas, thanks for your help. I would like to try the build a debian jessie nsf root and a debian jessie initrd, which will install the Ubuntu 14.04 LTS. As I understand I have to add jessie sources inside nfsroot.conf and run the fai-make-nfsroot without using -B option (using special base.

Re: AW: Problem with disk_config

> On Thu, 19 Nov 2015 13:55:05 +0100, "Werner Pommerer" > said: > the script 30-mkinitrd uses now the dracut part instead of the mkinitrd > code. > BUT: the result ist he same! Using LVM, it seems only by possible, to do > this > Installation, during "firstboot" (I

AW: Problem with disk_config

Hello, the script 30-mkinitrd uses now the dracut part instead of the mkinitrd code. BUT: the result ist he same! Using LVM, it seems only by possible, to do this Installation, during "firstboot" (I will paste this script) (paste.debian.net/333822) What ist he problem? Regards -Ursprünglic

Aw: Issues with booting from CD

Hello there, I solved the problem with empty $DOMAIN when booting from CD instead of NFS: Just give network some more time to come up. E.g. by adding a confdir.DEFAULT.source: n=0 until [ $n = 20 ]; do # Is there a NIC up that contains the letters 'eth'? # Yes? Go Ahead! - No? Just wait

Aw: Issues with booting from CD

Hello there, I took a deeper look at the dhcp leases and I'm still confused: Von: "Christian Meyer" > $DOMAIN is set correctly: > linux   /boot/vmlinuz boot=live root=/dev/nfs > nfsroot=172.16.0.123:/srv/fai/nfsroot > FAI_FLAGS="createvt" FAI_ACTION=install > FAI_CONFIG_SRC=nfs://fai-server/sr

Aw: Re: locales in NFSROOT

Hello Thomas and all others, I finaly got locales and keyboard-configuration working in my NFSROOT / installation system. Thank you Thomas for help. Thomas script in /etc/fai/nfsroot-hooks/locales works fine and adding (preconfigured) keyboard-configuration and console-setup for keyboard-layout

Re: AW: Packagename depends on uname -r

On Fri, 15 May 2015, Werner Pommerer wrote: it didn't work for me. In "package_config", I added the line: .. PACKAGES yumi .. kernel-module-openafs-`uname -r` .. But fai.log says: install_packages: executing chroot /target yum -y install kernel-module-openafs-`uname -r`

Re: AW: Packagename depends on uname -r

> On Fri, 15 May 2015 14:16:39 +0200, "Werner Pommerer" > said: > But fai.log says: > install_packages: executing chroot /target yum -y install kernel-module-openafs-`uname -r` ... > No package kernel-module-openafs-3.2.0-4-amd64 available. > When the I do the

AW: Packagename depends on uname -r

Hello, it didn't work for me. In "package_config", I added the line: .. PACKAGES yumi .. kernel-module-openafs-`uname -r` .. But fai.log says: install_packages: executing chroot /target yum -y install kernel-module-openafs-`uname -r` ... No package kernel-module-openafs-3.

Aw: Re: locales in NFSROOT

Gesendet: Mittwoch, 13. Mai 2015 um 08:31 Uhr Von: "Thomas Lange" An: "fully automatic installation for Linux" Betreff: Re: locales in NFSROOT   > Did you install the package locales into the nfsroot? > This package is not installed by default. Add locales to > /etc/fai/NFSROOT and then rebuild

Re: AW: Option to set Ports for NFS mount

> On Mon, 13 Apr 2015 14:54:36 +, "Schulz, Reiner" > said: > 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 f

Re: AW: fai-make-nfsroot

> On Mon, 13 Apr 2015 22:11:12 +0200, Christian Meyer said: > Of course "real merging" isn't possible, but what about > modifying /etc/fai/nfsroot.conf to something like: > DISTRIBUTION=$(cat /etc/fai/apt/sources.list | grep -Em1 > '(.debian.|.ubuntu.)' | cut -d\ -f2')

Re: AW: fai-make-nfsroot

Hello Thomas, Am Donnerstag, den 26.03.2015, 17:55 +0100 schrieb Thomas Lange: > > On Thu, 26 Mar 2015 16:36:23 +0100, werner.pomme...@uni-hohenheim.de > > said: > > > http://paste.debian.net/hidden/a7354e4b > You are mixing jessie and wheezy packages. When calling debootstrap > (lin

AW: Option to set Ports for NFS mount

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 localh

Re: AW: Option to set Ports for NFS mount

> On Mon, 30 Mar 2015 10:41:48 +, "Schulz, Reiner" > said: > 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" It should be possible to redefine the va

AW: Option to set Ports for NFS mount

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.fai

Re: AW: fai-make-nfsroot

> On Thu, 26 Mar 2015 16:36:23 +0100, werner.pomme...@uni-hohenheim.de said: > http://paste.debian.net/hidden/a7354e4b You are mixing jessie and wheezy packages. When calling debootstrap (line 4) you are using jessie, but later you are using packages from wheezy. This will cause problems.

Re: AW: fai-make-nfsroot

http://paste.debian.net/hidden/a7354e4b Regards Werner - Nachricht von Thomas Lange - Datum: Thu, 26 Mar 2015 15:56:41 +0100 Von: Thomas Lange Antwort an: fully automatic installation for Linux Betreff: Re: AW: fai-make-nfsroot An: fully automatic

Re: AW: fai-make-nfsroot

> On Thu, 26 Mar 2015 15:49:20 +0100, werner.pomme...@uni-hohenheim.de said: > I put the log on paste.debian.net Which URL? -- regards Thomas

  1   2   >