Hi Diego,
Nice catch for the scsi grep.
Will try that ASAP.
Thanks
Le ven. 23 févr. 2024 à 14:35, Diego Zuccato a écrit :
>
> Just a followup.
> My script had a serious bug (plus a typo), too: since it gets sourced,
> $0 is not what I expected :( After many failed atttempts finally I
>
Hi Thomas,
I will wait for the patch, because, yes, I have this bug.
I do not know exactly what is going on, but I can send you, for
example, some of my logs privately with privatebin. We can keep in
touch on IRC about that.
TYVM,
Best
Le mer. 7 févr. 2024 à 10:01, pa...@kish.by a écrit :
>
>
Hi,
I don't know if this is really related, but as I also said on IRC,
`checkdisk` returns an empty string. All the functions depending on it
are also returning an empty string. I tried to modify it manually in
subroutines with the following content, but it did not help either:
```bash
I know I could change directly the subroutine code from the
"set_disk_info" function, but if I can avoid doing this and doing
something better / cleaner...
Le mer. 31 janv. 2024 à 12:48, Rémy Dernat a écrit :
>
> Ok, Thanks Thomas.
>
> So, let's say I want to get a `$diskl
modifying `class/20-hw-detect.sh` (?); in the beginning of the
scripts, it says that the outputs of `*.sh` scripts are ignored ...
Thanks,
Rémy
Le mer. 31 janv. 2024 à 12:42, Thomas Lange a écrit :
>
> >>>>> On Wed, 31 Jan 2024 11:15:46 +0100, Rémy Dernat
> >>
ct.org/download/misc/99-disklist.sh
>
>
> >>>>> On Mon, 29 Jan 2024 17:13:39 +0100, Rémy Dernat
> >>>>> said:
>
>
> > So, I would like to define something like disk1 / sda is :
> > fdisk -l 2>/dev/null |awk '/Disk / {print $2,$3}' |sort -n -k2 |head -1
>
> > Then, this would be used by setup-storage.
>
> --
> regards Thomas
Hi,
I have a weird issue since Ubuntu 22.04.
It seems that disks are not in the right order; for example sda became
sdg, etc...
This is really annoying as my smallest disk should be used for system,
not the other disks. Normally, it was sda.
So, I would like to define something like disk1 / sda
,defaults,noatime,compress=zstd
```
??
Le mar. 5 déc. 2023 à 13:15, Rémy Dernat a écrit :
>
> Hi,
>
> After digging some time around this issue, I am finally able to boot
> the RAID1 partition with EFI boot enabled on it (using this example:
> https://fai-project.org/download/mi
fig lvm
vg vg_system md1
vg_system-swap swap 16G swap sw
vg_system-root / 60G-200G ext4 rw,noatime
vg_system-tmp /tmp 20G-50G ext2 rw,noatime,nosuid,nodev
vg_system-home /home 30%- ext4 rw,noatime,nosuid,nodev
```
Best regards,
Rémy
Le ven. 1 déc. 2023 à 12:11, Rémy Dernat a écri
> one.
>
> I've found that some servers allow the EFI partition to be RAID1, the
> current servers we're using support that. So no need to copy files around.
>
> Cheers,
> Andrew
>
> On Thu, 2023-11-30 at 17:20 +0100, Rémy Dernat wrote:
>
> > Ok, FYI, I think I h
atime,nosuid,nodev
##vg_system-scratch /scratch 30%- ext2 rw,noatime
vg_system-home /home 30%- ext4 rw,noatime,nosuid,nodev
```
My previous message was crystal clear. md0 did not have any formatted
filesystem on it. So I added `vfat` option on /boot.
Best regards,
Rémy
Le jeu. 30 nov. 2023 à 16:5
. 2023 à 14:52, Rémy Dernat a écrit :
>
> Hi Andrew,
>
> Indeed, this removed the syntax issue. However, I have a new error now:
>
> ```
> /sbin/blkid -c /dev/null -s UUID -o value /dev/md0 had exit code 2
> Command had non-zero exit code
> ```
> Indeed, blkid is not
nosuid,nodev
```
I also tried to change the raid metadata to 1.0, but that did not
change anything. I wrote back ` fstabkey:uuid` behind disk_config raid
because it does not fail with syntax error.
Thanks for help
Le jeu. 30 nov. 2023 à 11:55, Andrew Ruthven a écrit :
>
> Hey,
>
> On Thu,
Hi awesome Fai guys,
I have a weird syntax issue with the following disk_config:
```
# example of new config file for setup-storage
#
#
disk_config disk1 disklabel:gpt fstabkey:uuid
primary - 2G - -
primary /boot/efi 1G vfat rw createopts="-F32"
primary swap 2G swap sw,pri=1
primary -
Hi,
I did not read this whole threads, but yes, here we are currently managing
a FAI server through SaltStack. It configures pxelinux files and my DHCP
server. FAI rootfs installs the SaltStack repository with a script class,
and my SaltStack server auto-accept keys from known hostnames through a
noatime,nosuid,nodev
vg_system-scratch /scratch 30%- ext2 rw,noatime
##vg_system-home /home 30%- ext4 rw,noatime,nosuid,nodev
Maybe I can try it now.
Best regards,
Le mer. 10 mars 2021 à 10:24, Thomas Lange a écrit :
>
>
> >>>>> On Wed, 10 Mar 2021 10:00:30 +0100, Rémy
``` in html. Can you please disable html mails?
>
> >>>>> On Wed, 10 Mar 2021 09:43:27 +0100, Rémy Dernat
> >>>>> said:
>
> > Hi,I currently have that
> kind of disk configuration for my UEFI machines
> :```disk_config disk1 disklabel:ms
Hi,
I currently have that kind of disk configuration for my UEFI machines :
```
disk_config disk1 disklabel:msdos bootable:1 fstabkey:uuid
primary / 40G-200Gext4 rw,noatime,errors=remount-ro
logical /tmp20G-50G ext4 rw,noatime,nosuid,nodev
createopts="-L tmp -m 0"
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
Oh I see, Ok... That explains why it worked before and then, why it does
not work anymore.
Thanks,
Le lun. 4 févr. 2019 à 11:27, Thomas Lange
a écrit :
> >>>>> On Mon, 4 Feb 2019 10:26:02 +0100, Rémy Dernat
> said:
>
> > I have some difficulties to setup
Hi,
I have some difficulties to setup a working nfsroot environement; The
initrd image does not seem to contain all the necessary modules :
chroot /srv/fai/nfsroot
find /lib/modules/4.9.0-8-amd64/ -name "*bnx2*"
/lib/modules/4.9.0-8-amd64/kernel/drivers/scsi/bnx2i
particularly your
"variables.log" (for example, to check $NIC1) and "error.log".
Moreover, if you can also supply your network configuration files
(/etc/network/interfaces and so on...), it would be useful.
Best regards,
Rémy.
Le jeu. 22 nov. 2018 à 17:22, Steffen Grunewal
$newnicname|" $target/etc/network/interfaces
sed -ri "s|mac_to_replace|$mac|" $target/etc/netplan/01-netcfg.yaml
```
With `{mac,inet}_to_replace` in those files (which is replaced with my sed).
Best regards,
Rémy.
Le jeu. 22 nov. 2018 à 09:54, Rémy Dernat a écrit :
> Hi,
Hi,
I am facing the same issue. However, I would like to adopt the new naming
style, and so, retrieving the interface name dynamically.
The Debian script previously cited seems to do the job at the FAI nfsroot
step, during installation. However, when it reboots, it looses the ability
to get this
Hi Thomas,
Indeed, I am working with SaltStack templates to generate those tftp files.
I will compare with those generated with fai-chboot.
Thanks,
Rémy
Le mar. 9 oct. 2018 à 13:54, Thomas Lange a
écrit :
> >>>>> On Tue, 9 Oct 2018 12:03:24 +0200, Rémy Dernat
> sai
Hi,
I have a weird behaviour concerning my nfsroot configuration.
If I use a kernel 3.X (3.16.0-6-amd64) created with another fai server, my
clients boot fine, but if I try to create a kernel 4.9.0-8, my clients are
always stuck in a "read only file system" error ( The exact error message
is the
Hi,
I am not doing this, but I think it should not be to difficult. I have a
similar script running as a post-install step; maybe you can use something
like this as a script :
#!/bin/bash
check_zpool()
{
zfs_value=`/sbin/zpool list|grep -ic "zfs_bigvol"`
}
check_zpool
if [ $zfs_value -eq 0
Hi,
I suggest you to retrieve the version of SYSLINUX 6.04; look here for more
informations :
https://groups.google.com/a/lbl.gov/forum/#!msg/warewulf/klTLgX-L4nw/IJZo3-jgAAAJ
BTW, sometimes an update of the firmware on the client give great results.
Best regards,
Rémy.
Le lun. 3 sept. 2018 à
Hi,
Yes ! Thanks ! It works after modifying the file "60-misc" like described
by Thomas and this line :
```
primary /boot/efi 204800K vfat rw
```
to
```
primary /boot/efi 204800K vfat rw createopts="-s2 -F32"
```
Thank you very much.
Best regards,
Rémy.
Le lun. 9 juil. 2018 à 15:39, Thomas
# 2018-07-04: jheim
> disk_config disk1 disklabel:gpt fstabkey:label align-at:1
> primary /boot/efi 204800K vfat rw
> primary/usr/local 157286400Kext4 rw,relatime
> createopts="-L LOCALFS"
> primary/ 72G- ext4 rw,relatime
> crea
s. I think that
"FAI_CONFIG_SRC=nfs://faiserv.acme.ltd/srv/fai/config" is not loading at
the install step. Maybe I have some syntax error...
Best regards,
Rémy.
Le ven. 6 juil. 2018 à 14:27, Rémy Dernat a écrit :
> Hi,
>
> I am trying to set up an UEFI boot pxe mainly because our hard
Hi,
I am trying to set up an UEFI boot pxe mainly because our hardware servers
do not support full legacy BIOS anymore (particularly hard disk plugin on
those servers).
Our legacy pxelinux works just fine from a while now (and thanks for it).
I followed this link :
32 matches
Mail list logo
