Subject: Re:Re: Problem with setup-storage
Hi all, other people also have this problem (disks under /dev are not in group disk but root). I wonder if you have checked /etc/fai/NFSROOT after upgrading to FAI 6.2. Make sure this line is removed and recreate the nfsroot. sysvinit-core systemd-sysv- It was used with FAI 6.0.x because we did not used systemd inside the nfsroot. FAI 6.2 now ships an /etc/fai/NFSROOT which will install systemd that's used nowadays. I hope that this is the cause of your wrong group ownership for /dev. Concerning setup-storage, I wonder if it is really broken inside the FAI boot environment. FAI should define the functions needed for setup-storage before calling setup-storage. There may be still problems when you log in via ssh into the FAI environment and call setup-storage. Then the functions needed are not defined. A patch is already applied and will be available in the next FAI version. See https://github.com/faiproject/fai/compare/eb8f779aa4c69157d448..cd33235318279a962 -- viele Grüße Thomas
Re: Problem with setup-storage
Here's the patch https://github.com/faiproject/fai/commit/cd33235318279a96267d3377661dbeba93eacac3 -- viele Grüße Thomas
Subject: Re:Re: Problem with setup-storage
Hy there, as I struggled with all those Problems the last 24 hours since I’ve updated to 6.2 I figured some out some stuff: first of all, the subroutines seams not to be loaded by the .profile file in nfsroot/root/.profile I changed it from . /usr/lib/fai/subroutines To source /usr/lib/fai/subroutines That fixed the command not found issue and regarding the disks are not detected. At least in my environment it was: all subs in /dev have group root. So the detection method for group “disk” in subroutines->checkdisk() function wont work. I switched it back to the one, in the comment (line above in the file) wich checks for /removeable and its working now. Hopefully that helps a bit. -- Mit freundlichen Grüßen / Best regards Axel Lodyga
Re: Problem with setup-storage
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 Thomas, > Also FAI 6.2 have problem with setup-storage when we use mdadm+lvm > I wrote later about it > > > > 7 февр. 2024 г., в 11:53, Thomas Lange написал(а): > > I'm preparing a patch and will upload a new FAI version if it's ready. > >
Re: Problem with setup-storage
Hi Thomas, Also FAI 6.2 have problem with setup-storage when we use mdadm+lvm I wrote later about it > 7 февр. 2024 г., в 11:53, Thomas Lange написал(а): > > I'm preparing a patch and will upload a new FAI version if it's ready.
Re: Problem with setup-storage
Hi Remy, it seems you hit bug https://bugs.debian.org/1063146. I'm preparing a patch and will upload a new FAI version if it's ready. But this bug should only appear, if you use setup-storage as a standalone command. Inside the FAI environment everything should work. It's not clear to me in which kind of environment you have problems. -- regards Thomas
Re: Problem with setup-storage
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
checkdisk() {
# read lines with device name and size and check if device is a disk
# $1 can be a device name that will be ignored. Used for the device
# name of the USB stick if we boot from it
local igndev=('loop') #devices to ignore
igndev+=($1)
local isdisk
ls /dev | while read device blocks; do
isdisk=1
# old way of detecting disks: [ $(cat
/sys/block/$device/removable) -eq 1 ] && isdisk=0
[ $(stat -c %G /dev/$device) = "disk" ] || isdisk=0
# if set, ignore these devices
[[ "${igndev[@]}" =~ ${device}* ]] && isdisk=0
if [ $isdisk -eq 1 ]; then
echo "$device"
fi
done
}
```
here is the content of `fai-disk-info`:
```bash
#! /bin/bash
set_bootstick
all_disks_and_size | checkdisk $FAI_BOOTSTICK | once_only
```
That is really odd, because when I checked that modified version of
`checkdisk` locally, it works on my local machine. Moreover, I am able
to see disk devices in /dev when dracut spawn a shell terminal. I
don't know why it does not work in the dracut chroot mounted space
system; maybe a `sh` vs a `bash` issue although the subroutine calls
directly `/bin/bash` .. O_o ... All files in /usr/lib/fai/ are set in
755 mode, with owner and group root.
I am currently stuck with some machines unable to install because of
this issue...
Best regards,
Rémy
Le mar. 6 févr. 2024 à 15:59, Stephen Quinney via linux-fai
a écrit :
>
> 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.
>
>
> -- Forwarded message --
> From: Stephen Quinney
> To: linux-fai
> Cc:
> Bcc:
> Date: Tue, 6 Feb 2024 14:59:08 +
> Subject: Problem with setup-storage
> I'm using the packages from Debian unstable so I reported this to the
> Debian bug tracker first but then thought that it might be better done
> through the mailing list.
>
> We use the setup-storage utility in a standalone manner in our local
> installation and configuration scripts with the rest of FAI. Up until
> 6.2 this worked just fine but now it fails.
>
> This seems to be related to changes in the fai-disk-info script.
>
> With 6.0 I get:
>
> /usr/lib/fai/fai-disk-info
> sda
>
> and with 6.2 I now get:
>
> /usr/lib/fai/fai-disk-info
> bash: set_bootstick: command not found
> bash: once_only: command not found
> bash: all_disks_and_size: command not found
> bash: checkdisk: command not found
>
> At first I thought it was down to not having the fai-client package
> installed (it's not listed as a dependency for fai-setup-storage)
> since it provides the /usr/lib/fai/subroutines. However, installing
> that package hasn't helped.
>
> Any help would be appreciated.
>
> Regards,
>
> Stephen Quinney
Problem with setup-storage
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 using the packages from Debian unstable so I reported this to the Debian bug tracker first but then thought that it might be better done through the mailing list. We use the setup-storage utility in a standalone manner in our local installation and configuration scripts with the rest of FAI. Up until 6.2 this worked just fine but now it fails. This seems to be related to changes in the fai-disk-info script. With 6.0 I get: /usr/lib/fai/fai-disk-info sda and with 6.2 I now get: /usr/lib/fai/fai-disk-info bash: set_bootstick: command not found bash: once_only: command not found bash: all_disks_and_size: command not found bash: checkdisk: command not found At first I thought it was down to not having the fai-client package installed (it's not listed as a dependency for fai-setup-storage) since it provides the /usr/lib/fai/subroutines. However, installing that package hasn't helped. Any help would be appreciated. Regards, Stephen Quinney --- End Message ---
Re: Problem with setup-storage preserving an existing LVM over RAID volume (workaround)
Hello Thomas and all,
Am Donnerstag, den 31.01.2019, 10:32 +0100 schrieb Thomas Lange:
> This is a bug we fixed in 5.7.3, see #909318.
> So please try a newer FAI version. But I'm not sure if this will also
> fix your other problems.
Thank you for looking into it. I'm sad that I can't help with perl.
> I'm not sure if anyone ever tried to preserve LVM over RAID and had success.
In the meantime I succeeded with what you suggested 'years ago': I used
a script under class/
My solution is an ugly hack, but it works for both preserving and
deleting an existing LVM over RAID.
So I'm able to just reinstall KVM host (on md0) and keep all the guests
in a LVM-VG on a different RAID. If anyone is trying something similar:
remember to backup your kvm-settings, too, e.g. with 'virsh dumpxml
vmname > vmname.xml' and similar for storage and networking.
This workaround is just for the record, perhaps it is useful for
others:
First I try to mount a previous FAI Installation (this is expected
under /dev/md0 without LVM) and to copy the old disk_config logs:
mdadm --assemble /dev/md0 --force --run /dev/sdb1 /dev/sda1
mount /dev/md0 /mnt
cat /mnt/var/log/fai/localhost/last-install/fstab > $LOGDIR/fstab;
cat /mnt/var/log/fai/localhost/last-install/disk_var.sh >
$LOGDIR/disk_var.sh
grep UUID /mnt/var/log/fai/localhost/last-install/format.log >
$LOGDIR/format.log
umount /mnt
To preserve LVM and RAID I do this:
===
[ $(cat $LOGDIR/fstab | wc -l) -gt 0 ] && {
UUID_old=$(grep -P '\t/\t' $LOGDIR/fstab | cut -d\= -f2 | cut -f1)
UUID_new=$(mkfs.ext4 /dev/md0 | tee $LOGDIR/format.log | grep UUID |
cut -d\ -f4)
sed -i -e "s:UUID=$UUID_old:UUID=$UUID_new:" $LOGDIR/disk_var.sh
sed -i -e "s:^UUID=$UUID_old:UUID=$UUID_new:" $LOGDIR/fstab
skiptask partition;
}
To delete the old LVM and RAID I do that:
=
VGs="$(echo $(vgscan | grep "Found volume group" | cut -d\" -f2))"
for VG in $VGs; do
vgchange -an $VG
vgremove -q -y -ff $VG
done
mdadm --stop --scan
for partition in $(for disk in $disklist; do echo $disk | grep -qv md -
&& echo /dev/$disk[1-9]; done); do
mdadm --zero-superblock $partition 2>/dev/null;
done
# (from class/20-hwdetect.sh)
odisklist=$disklist
set_disk_info # recalculate list of available disks
if [ "$disklist" != "$odisklist" ]; then
echo New disklist: $disklist
echo disklist=\"$disklist\" >> $LOGDIR/additional.var
fi
-> continue with regular disk_config (without any 'preserve'-line)
building a new RAID and LVM.
Christian
Re: Problem with setup-storage preserving an existing LVM over RAID volume
> On Mon, 07 Jan 2019 22:45:18 +0100, Christian Meyer said:
> INTERNAL ERROR in setup-storage:
> convert_unit 1,81TiB
> Please report this error to the Debian Bug Tracking System.
> at /usr/share/fai/setup-storage/Parser.pm line 379.
> FAI::convert_unit("1,81TiB") called at /usr/share/fai/setup-
> storage/Volumes.pm line 416
This is a bug we fixed in 5.7.3, see #909318.
So please try a newer FAI version. But I'm not sure if this will also
fix your other problems.
I'm not sure if anyone ever tried to preserve LVM over RAID and had success.
--
regards Thomas
Re: Problem with setup-storage preserving an existing LVM over RAID volume
Hello Thomas
Am Freitag, den 04.01.2019, 19:41 +0100 schrieb Thomas Lange:
> It will take some effort to debug this.
Okay, I will try to help as much as I can, but sadly I don't understand
any perl.
> The initrd (created by dracut) may also detect and active softraid
> and lvm. I'm not sure if this really happens.
Yes, it seems so.
I switched to tty2 right after class/20-hwdetect and vgdisplay
lvdisplay shows my whole lvm drive.
But even when I do:
# lvchange -an vg_guests
# vgchange -an vg_guests
# mdadm --stop /dev/md*
the problem still exists. The main difference is that disklist is
without raid or lvm stuff:
disklist: sda
sdb
sdc
sdd
sde
But then it looks similar:
# setup-storage -f /var/lib/fai/config/disk_config/KVM -d
1>/tmp/logfile 2>/tmp/logfile
#
Using config file: /var/lib/fai/config/dUse of uninitialized value
$this_mp in string eq at /usr/share/fai/setup-storage/Parser.pm line
1225, <$config_file> line 1.
Use of uninitialized value $this_mp in hash element at
/usr/share/fai/setup-storage/Parser.pm line 1226, <$config_file> line
1.
Use of uninitialized value $this_mp in string eq at
/usr/share/fai/setup-storage/Parser.pm line 1230, <$config_file> line
1.
Use of uninitialized value $this_mp in hash element at
/usr/share/fai/setup-storage/Parser.pm line 1230, <$config_file> line
1.
File descriptor 4 (/dev/tty2) leaked on vgdisplay invocation. Parent
PID 3710: /usr/bin/perl
File descriptor 63 (pipe:[14475]) leaked on vgdisplay invocation.
Parent PID 3710: /usr/bin/perl
WARNING: Failed to connect to lvmetad. Falling back to device
scanning.
File descriptor 4 (/dev/tty2) leaked on vgdisplay invocation. Parent
PID 3710: /usr/bin/perl
File descriptor 63 (pipe:[14475]) leaked on vgdisplay invocation.
Parent PID 3710: /usr/bin/perl
WARNING: Failed to connect to lvmetad. Falling back to device
scanning.
INTERNAL ERROR in setup-storage:
convert_unit 1,81TiB
Please report this error to the Debian Bug Tracking System.
at /usr/share/fai/setup-storage/Parser.pm line 379.
FAI::convert_unit("1,81TiB") called at /usr/share/fai/setup-
storage/Volumes.pm line 416
FAI::get_current_lvm called at /usr/sbin/setup-storage line 167
ey:uuid preserve_reinstall:1
primary - 300G- - -
disk_config sdd sameas:sdc
# RAID:
# =
#disk_config raid fstabkey:uuid
disk_config raid fstabkey:uuid preserve_reinstall:2,3
raid1 / sda1,sdb1ext4rw,noatime,errors=remount-ro
raid1 - sda3,sdb3- -
raid1 - sdc1,sdd1- -
#
But why has $this_mp an uninitialized value?
Christian
Re: Problem with setup-storage preserving an existing LVM over RAID volume
Hello Thomas, I'm using fai 5.3.6 (Debian stable). Since I could use hooks and skiptask it's not that important, but I wonder if there is a working example for "preserve_reinstall". I read something about raid, lvm and "preserve_reinstall" in the archive: https://lists.uni-koeln.de/pipermail/linux-fai/2009-October/007387.html and that you suggested to run "mdadm-startall" https://lists.uni-koeln.de/pipermail/linux-fai/2009-October/007389.html in 20-hwdetect.[source|sh] instead of including it in setup-storage. But since it's more than 9 years ago and there is no command "mdadm- startall" nor do I find anything helpfull about this, I thought that there is a different solution. Since raid/lvm is not needed during installation there should be no need to activate or mount it. Ok, how could setup-storage know about lvm when not starting raid before. Difficult. setup-storage sees the three raid devices, but no lvm / volumegroup: > setup-storage is running in test-only mode > disklist: md125 > md126 > md127 > sda > sdb > sdc > sdd There is the > "WARNING: Failed to connect to lvmetad." and # lsmod | grep -i lvm is empty. Is this related? Christian Am Freitag, den 04.01.2019, 19:41 +0100 schrieb Thomas Lange: > It will take some effort to debug this. > > > The initrd (created by dracut) may also detect and active softraid > and > lvm. I'm not sure if this really happens. I remember that we already > had some issue with raid or lvm activated by dracut and then > setup-storage could handle this later on. > > BTW, which FAI version? This is also important.
Re: Problem with setup-storage preserving an existing LVM over RAID volume
It will take some effort to debug this.
The initrd (created by dracut) may also detect and active softraid and
lvm. I'm not sure if this really happens. I remember that we already
had some issue with raid or lvm activated by dracut and then
setup-storage could handle this later on.
BTW, which FAI version? This is also important.
> On Fri, 04 Jan 2019 18:43:13 +0100, Christian Meyer said:
> Hello there,
> doing my fist server-lessions, I'm facing two problems with setup-
> storage.
> This one is about preserving an existing LVM over RAID volume.
> I managed to install an lvm over two raid volumes (md1 and md2) with
> FAI and the first disk_config line (now #-ed).
> In the second run I try to preserve partitions, md's and lv's, but I'm
> getting an error telling me to file a bug report. (I rather think it's
> a problem with configuration and/or my customized configspace. BTW: I
> don't do anything with mdadm or lv* in class/*)
> Obviously Parser.pm complains about an "uninitialized value $this_mp",
> but I found the syntax of "disk_config ..." in the mailing list archive
> and have no glue what it could mean.
> Is the problem anyway related with "WARNING: Failed to connect to
> lvmetad." or missing commands in my class/* or hook/* ?
> Previously there has been a problem reinstalling the complete RAID/LVM,
> but this I could fix by calling:
> # lvremove /dev/vg_guests/*
> # mdadm --stop /dev/md*
> # mdadm --zero-superblock /dev/sd*
> But since I want to keep my VMs, this is not what I want to do.
> Thanks a lot for your help.
> Christian
> The error says:
> #
> # setup-storage -f /var/lib/fai/config/disk_config/KVM
> setup-storage is running in test-only mode
> Starting setup-storage 2.0
> Using config file: /var/lib/fai/config/disk_config/KVM
> Use of uninitialized value $this_mp in string eq at
> /usr/share/fai/setup-storage/Parser.pm line 1225, <$config_file> line
> 1.
> Use of uninitialized value $this_mp in hash element at
> /usr/share/fai/setup-storage/Parser.pm line 1226, <$config_file> line
> 1.
> Use of uninitialized value $this_mp in string eq at
> /usr/share/fai/setup-storage/Parser.pm line 1230, <$config_file> line
> 1.
> Use of uninitialized value $this_mp in hash element at
> /usr/share/fai/setup-storage/Parser.pm line 1230, <$config_file> line
> 1.
> File descriptor 4 (/dev/tty2) leaked on vgdisplay invocation. Parent
> PID 4072: /usr/bin/perl
> File descriptor 63 (pipe:[14331]) leaked on vgdisplay invocation.
> Parent PID 4072: /usr/bin/perl
> WARNING: Failed to connect to lvmetad. Falling back to device
> scanning.
> File descriptor 4 (/dev/tty2) leaked on vgdisplay invocation. Parent
> PID 4072: /usr/bin/perl
> File descriptor 63 (pipe:[14331]) leaked on vgdisplay invocation.
> Parent PID 4072: /usr/bin/perl
> WARNING: Failed to connect to lvmetad. Falling back to device
> scanning.
> INTERNAL ERROR in setup-storage:
> convert_unit 1,81TiB
> Please report this error to the Debian Bug Tracking System.
> at /usr/share/fai/setup-storage/Parser.pm line 379.
> FAI::convert_unit("1,81TiB") called at /usr/share/fai/setup-
> storage/Volumes.pm line 416
> FAI::get_current_lvm called at /usr/sbin/setup-storage line 167
> #
> This is my disk_config/KVM
> #
> # This is my disk_config/KVM
> # Disks:
> # ==
> # disk_config sda disklabel:msdos bootable:1 fstabkey:uuid
> disk_config sda disklabel:msdos bootable:1 fstabkey:uuid
> preserve_reinstall:3
> #
> primary - 10G - -
> primary swap2G swap sw
> primary - 50G-- -
> disk_config sdb sameas:sda
> # disk_config sdc disklabel:msdos fstabkey:uuid
> disk_config sdc disklabel:msdos fstabkey:uuid preserve_reinstall:1
> primary - 300G- - -
> disk_config sdd sameas:sdc
> # RAID:
> # =
> # disk_config raid fstabkey:uuid
> disk_config raid fstabkey:uuid preserve_reinstall:2,3
> raid1 / sda1,sdb1ext4rw,noatime,errors=remount-ro
> raid1 - sda3,sdb3- -
> raid1 - sdc1,sdd1- -
> # LVM:
> #
> # disk_config lvm fstabkey:uuid
> disk_config lvm fstabkey:uuid preserve_reinstall:vg_guests-1,vg_guests-
> 2,vg_guests-3,vg_guests-4
> vg vg_guests md1,md2
> vg_guests-1 - 50Gext4 rw,noatime,errors=remount-ro
> vg_guests-2 - 50Gext4 rw,noatime,errors=remount-ro
> vg_guests-3 - 50Gext4 rw,noatim
Problem with setup-storage preserving an existing LVM over RAID volume
Hello there,
doing my fist server-lessions, I'm facing two problems with setup-
storage.
This one is about preserving an existing LVM over RAID volume.
I managed to install an lvm over two raid volumes (md1 and md2) with
FAI and the first disk_config line (now #-ed).
In the second run I try to preserve partitions, md's and lv's, but I'm
getting an error telling me to file a bug report. (I rather think it's
a problem with configuration and/or my customized configspace. BTW: I
don't do anything with mdadm or lv* in class/*)
Obviously Parser.pm complains about an "uninitialized value $this_mp",
but I found the syntax of "disk_config ..." in the mailing list archive
and have no glue what it could mean.
Is the problem anyway related with "WARNING: Failed to connect to
lvmetad." or missing commands in my class/* or hook/* ?
Previously there has been a problem reinstalling the complete RAID/LVM,
but this I could fix by calling:
# lvremove /dev/vg_guests/*
# mdadm --stop /dev/md*
# mdadm --zero-superblock /dev/sd*
But since I want to keep my VMs, this is not what I want to do.
Thanks a lot for your help.
Christian
The error says:
#
# setup-storage -f /var/lib/fai/config/disk_config/KVM
setup-storage is running in test-only mode
Starting setup-storage 2.0
Using config file: /var/lib/fai/config/disk_config/KVM
Use of uninitialized value $this_mp in string eq at
/usr/share/fai/setup-storage/Parser.pm line 1225, <$config_file> line
1.
Use of uninitialized value $this_mp in hash element at
/usr/share/fai/setup-storage/Parser.pm line 1226, <$config_file> line
1.
Use of uninitialized value $this_mp in string eq at
/usr/share/fai/setup-storage/Parser.pm line 1230, <$config_file> line
1.
Use of uninitialized value $this_mp in hash element at
/usr/share/fai/setup-storage/Parser.pm line 1230, <$config_file> line
1.
File descriptor 4 (/dev/tty2) leaked on vgdisplay invocation. Parent
PID 4072: /usr/bin/perl
File descriptor 63 (pipe:[14331]) leaked on vgdisplay invocation.
Parent PID 4072: /usr/bin/perl
WARNING: Failed to connect to lvmetad. Falling back to device
scanning.
File descriptor 4 (/dev/tty2) leaked on vgdisplay invocation. Parent
PID 4072: /usr/bin/perl
File descriptor 63 (pipe:[14331]) leaked on vgdisplay invocation.
Parent PID 4072: /usr/bin/perl
WARNING: Failed to connect to lvmetad. Falling back to device
scanning.
INTERNAL ERROR in setup-storage:
convert_unit 1,81TiB
Please report this error to the Debian Bug Tracking System.
at /usr/share/fai/setup-storage/Parser.pm line 379.
FAI::convert_unit("1,81TiB") called at /usr/share/fai/setup-
storage/Volumes.pm line 416
FAI::get_current_lvm called at /usr/sbin/setup-storage line 167
#
This is my disk_config/KVM
#
# This is my disk_config/KVM
# Disks:
# ==
# disk_config sda disklabel:msdos bootable:1 fstabkey:uuid
disk_config sda disklabel:msdos bootable:1 fstabkey:uuid
preserve_reinstall:3
#
primary - 10G - -
primary swap2G swap sw
primary - 50G-- -
disk_config sdb sameas:sda
# disk_config sdc disklabel:msdos fstabkey:uuid
disk_config sdc disklabel:msdos fstabkey:uuid preserve_reinstall:1
primary - 300G- - -
disk_config sdd sameas:sdc
# RAID:
# =
# disk_config raid fstabkey:uuid
disk_config raid fstabkey:uuid preserve_reinstall:2,3
raid1 / sda1,sdb1ext4rw,noatime,errors=remount-ro
raid1 - sda3,sdb3- -
raid1 - sdc1,sdd1- -
# LVM:
#
# disk_config lvm fstabkey:uuid
disk_config lvm fstabkey:uuid preserve_reinstall:vg_guests-1,vg_guests-
2,vg_guests-3,vg_guests-4
vg vg_guests md1,md2
vg_guests-1 - 50Gext4 rw,noatime,errors=remount-ro
vg_guests-2 - 50Gext4 rw,noatime,errors=remount-ro
vg_guests-3 - 50Gext4 rw,noatime,errors=remount-ro
vg_guests-4 - 200G-500G ext4 rw,noatime,errors=remount-ro
#
If it's helpfull, here is the full output of
# setup-storage -f /var/lib/fai/config/disk_config/KVM -d
#
setup-storage is running in test-only mode
disklist: md125
md126
md127
sda
sdb
sdc
sdd
Starting setup-storage 2.0
Using config file: /var/lib/fai/config/disk_config/KVM
Input was:
--- see config-file above ---
Use of uninitialized value $this_mp in string eq at
/usr/share/fai/setup-storage/Parser.pm line 1225, <$config_file> line
1.
Use of uninitialized value $this_mp in hash element at
/usr/share/fai/setup-storage/Parser.pm line 1226, <$config_file> line
1.
Use of uninitialized value $this_mp in string eq at
/usr/share/fai/setup-storage/Parser.pm line 1230, <$config_file> line
1.
Use of uninitialized value $this_mp in hash element at
/us
Having a problem with setup-storage trying to partition
Hello, I was wondering if I could get any help debugging the following error message, which I am getting when trying to partition a disk in fai: Starting setup-storage 1.4 Using config file: /var/lib/fai/config/disk_config/OFFICE Executing: parted -s /dev/sda unit TiB print Executing: parted -s /dev/sda unit B print free Executing: parted -s /dev/sda unit chs print free Finding all volume groups Finding volume group "vg" Finding all volume groups Finding volume group "vg" Finding all volume groups Finding volume group "vg" Finding all volume groups Finding volume group "vg" Executing: mdadm --examine --scan --verbose -c partitions Cannot satisfy pre-depends for true: vgchange_a_n_VG_vg,pv_sigs_removed_vg,self_cleared_distfs,self_cleared_fscache,self_cleared_local.hd,self_cleared_root,self_cleared_swap,self_cleared_unused,self_cleared_var -- system left untouched. Error in task partition. Traceback: task_error task_partition task task_install task task_action task main The un-commented OFFICE config looks like the following (also note FAI_FLAGS=reboot,initial,sshd): disk_config disk1 disklabel:msdos bootable:1 fstabkey:uuid align-at:1M primary/boot224Mext3 defaults,rw,errors=panic createopts="-L boot" tuneopts="-c 90 -i 90d" primary-70G--- vg vg disk1.2 disk_configlvm fstabkey:device preserve_reinstall:vg-local.hd vg-swapswap4G-8Gswapsw createopts="-L swap" vg-root/36G-40Gext4 defaults,rw,errors=panic,relatime createopts="-L root" tuneopts="-c 90 -i 90d" vg-var/var3G-5Gext4 defaults,rw,errors=panic,relatime createopts="-L var" tuneopts="-c 90 -i 90d" vg-fscache/var/cache/fscache8G-16Gext4 defaults,rw,errors=panic,user_xattr,relatime createopts="-L fscache" tuneopts="-c 90 -i 90d" vg-local.hd/local.hd512M-90%ext4 defaults,rw,errors=panic,nosuid,nodev,acl,user_xattr,relatime createopts="-L local.hd -m 1" tuneopts="-c 90 -i 90d" vg-unused-5G-10G-- vg-distfs-10G-- I have the debug output from the setup-storage that I can send separately, if requested. Appreciate any help, Thanks, Ken
Re: Question/Problem with setup-storage
On 08/03/2012 08:16 AM, Ralf Aumueller wrote: > Hello, > > I try to partition my disk like this: > > - Preserve partition 1 (Windows) > - create 500MB /boot > - create 20GB for LVM > - create LVs for filesystems > > using the following config file for setup-storage: > > # > # LVM config > # > # config file for setup-storage > # > disk_config disk1 bootable:2 preserve_always:1 > primary /boot 500 ext4rw > primary - 20GiB - - > > disk_config lvm > vg vg0 disk1.3 > vg0-lv01swap2GiBswapsw > vg0-lv02/ 6GiBext4errors=remount-ro > vg0-lv03/var1GiBext4defaults > vg0-lv04/tmp1GiBext4defaults > > and get the following error: > > Cannot determine size of /dev/sda3 > > What is wrong with my configuration? I think you are missing the "primary"-line for your Windows partition. Have a look at: [1] https://lists.uni-koeln.de/pipermail/linux-fai/2009-June/007006.html HTH && Regards, - Darsha
Question/Problem with setup-storage
Hello, I try to partition my disk like this: - Preserve partition 1 (Windows) - create 500MB /boot - create 20GB for LVM - create LVs for filesystems using the following config file for setup-storage: # # LVM config # # config file for setup-storage # disk_config disk1 bootable:2 preserve_always:1 primary /boot 500 ext4rw primary - 20GiB - - disk_config lvm vg vg0 disk1.3 vg0-lv01swap2GiBswapsw vg0-lv02/ 6GiBext4errors=remount-ro vg0-lv03/var1GiBext4defaults vg0-lv04/tmp1GiBext4defaults and get the following error: Cannot determine size of /dev/sda3 What is wrong with my configuration? (If i remove "preserve_always:1" and change "disk1.3" to "disk1.2" this config file works fine -- but deletes as expected my Windows installation) fai version: 3.4.8ubuntu2 setup-storage: 1.3 (also tried 1.4 from fai 4.x) Best regards, Ralf
Re: FAI 3.2.12: new problem with setup-storage
> Michael Tautschnig a écrit : >> >>> The only thing I've seen that could work better is management of >>> errors in the disk config file: with the following files, >>> setup-storage seems to crash, and even suggests to report the bug, >>> whereas it could just say that the file is lousy. >>> >>> [...] >>> >> >> Could you provide some logs for these cases? That would be really cool and >> helpful :-) >> >> >> > Sure, you'll find the logs there: > > debug disabled: http://paste.debian.net/19413/, > http://paste.debian.net/19414/ > > debug enabled: http://paste.debian.net/19415/, > http://paste.debian.net/19417/ > Ok, the logs aren't available anymore on paste.debian.net, but I think I've fixed the remaining issue with the volume groups not being properly cleared in 3.2.13+experimental2, which just got uploaded to Thomas' repository. Best, Michael pgpGWyLjxOa0P.pgp Description: PGP signature
Re: FAI 3.2.12: new problem with setup-storage
Michael Tautschnig a écrit : debug disabled: http://paste.debian.net/19413/, http://paste.debian.net/19414/ debug enabled: http://paste.debian.net/19415/, http://paste.debian.net/19417/ The second one should be fixed in experimental7, the first one requires a bit more work it seems, but I'll try to get it done as well. Thanks a lot for the logs, and if you find the time to give it another try, I'd be even more grateful :-) It does work, the error message is now easy to understand. My pleasure :-) . -- Nicolas
Re: FAI 3.2.12: new problem with setup-storage
> Michael Tautschnig a écrit : >> >>> The only thing I've seen that could work better is management of >>> errors in the disk config file: with the following files, >>> setup-storage seems to crash, and even suggests to report the bug, >>> whereas it could just say that the file is lousy. >>> >>> [...] >>> >> >> Could you provide some logs for these cases? That would be really cool and >> helpful :-) >> >> >> > Sure, you'll find the logs there: > > debug disabled: http://paste.debian.net/19413/, > http://paste.debian.net/19414/ > > debug enabled: http://paste.debian.net/19415/, > http://paste.debian.net/19417/ > The second one should be fixed in experimental7, the first one requires a bit more work it seems, but I'll try to get it done as well. Thanks a lot for the logs, and if you find the time to give it another try, I'd be even more grateful :-) Thanks, Michael pgpw4ReQt0PZn.pgp Description: PGP signature
Re: FAI 3.2.12: new problem with setup-storage
Michael Tautschnig a écrit : The only thing I've seen that could work better is management of errors in the disk config file: with the following files, setup-storage seems to crash, and even suggests to report the bug, whereas it could just say that the file is lousy. [...] Could you provide some logs for these cases? That would be really cool and helpful :-) Sure, you'll find the logs there: debug disabled: http://paste.debian.net/19413/, http://paste.debian.net/19414/ debug enabled: http://paste.debian.net/19415/, http://paste.debian.net/19417/ -- Nicolas
Re: FAI 3.2.12: new problem with setup-storage
[...] > The experimental repository et FAI version both work fine, I have > checked that both problems I've had are now fixed. > That's good news :-) > The only thing I've seen that could work better is management of errors > in the disk config file: with the following files, setup-storage seems > to crash, and even suggests to report the bug, whereas it could just say > that the file is lousy. > > File 1: forget the line for the preserved primary partition > > disk_config sda preserve_always:1 bootable:2 > > primary/boot 512ext3rw > logical- 37000--- > > disk_config lvm > vg vg0 sda5 > vg0-swapswap2048swapsw > [...] > > > File 2: define a primary partition and use a logical one > > disk_config sda preserve_always:1 bootable:2 > > primary - 0- - > primary/boot 512ext3rw > primary- 37000--- > > disk_config lvm > vg vg0 sda5 > vg0-swapswap2048swapsw > [...] > Could you provide some logs for these cases? That would be really cool and helpful :-) Thanks a lot for your testing work, Michael pgpwEPhhVIMY8.pgp Description: PGP signature
Re: FAI 3.2.12: new problem with setup-storage
Michael Tautschnig a écrit : Thanks for the detailed report, this is now known as bug #502462 and fixed in the experimental packages which are now available using deb http://www.informatik.uni-koeln.de/fai/download experimental koeln in your sources.list (you need to tweak /etc/fai/apt/sources.list as well). This is in fact the first time that the experimental builds are available in a proper apt repository, so consider this as a very first announcement :-) The experimental repository et FAI version both work fine, I have checked that both problems I've had are now fixed. The only thing I've seen that could work better is management of errors in the disk config file: with the following files, setup-storage seems to crash, and even suggests to report the bug, whereas it could just say that the file is lousy. File 1: forget the line for the preserved primary partition disk_config sda preserve_always:1 bootable:2 primary/boot 512ext3rw logical- 37000--- disk_config lvm vg vg0 sda5 vg0-swapswap2048swapsw [...] File 2: define a primary partition and use a logical one disk_config sda preserve_always:1 bootable:2 primary - 0- - primary/boot 512ext3rw primary- 37000--- disk_config lvm vg vg0 sda5 vg0-swapswap2048swapsw [...] Thanks for setup-storage, and all these quick fixes, it's a very nice tool! -- Nicolas
Re: FAI 3.2.12: new problem with setup-storage
> Hello, > > After installing fai 3.2.12, I have a new problem with setup-storage, > with the following disk config; the full log is on > http://paste.debian.net/19353/. > Thanks for the detailed report, this is now known as bug #502462 and fixed in the experimental packages which are now available using deb http://www.informatik.uni-koeln.de/fai/download experimental koeln in your sources.list (you need to tweak /etc/fai/apt/sources.list as well). This is in fact the first time that the experimental builds are available in a proper apt repository, so consider this as a very first announcement :-) Best, Michael pgpf9G3e8OD0B.pgp Description: PGP signature
FAI 3.2.12: new problem with setup-storage
Hello, After installing fai 3.2.12, I have a new problem with setup-storage, with the following disk config; the full log is on http://paste.debian.net/19353/. The disk config file is the following: disk_config sda preserve_always:1 bootable:2 primary - 0- - primary/boot 512ext3rw logical- 22000--- disk_config lvm vg vg0 sda5 vg0-swapswap2000swapsw vg0-root/6000ext3rw vg0-var/var2000ext3rw vg0-usr/usr6000ext3rw vg0-local/local6000ext3rw I get a similar error message when removing the preserved partition, or when changing the lvm partition to primary. -- Nicolas
