From wnefal at gmail.com Thu Aug 19 19:54:33 2021 From: wnefal at gmail.com (Markus Falb) Date: Thu, 19 Aug 2021 21:54:33 +0200 Subject: Reinstall and keep data LV Message-ID: Hi, I am struggling! I want to reinstall LVM based installs. I want to keep some LVs (data) but want to overwrite the other LVs(system) First I did a kickstart of RHEL 7, here the storage related lines ...snip zerombr clearpart --all --initlabel part pv.0 --fstype=lvmpv --grow --asprimary part /boot --fstype=xfs --size 1000 --asprimary --label BOOT volgroup rhel_rhellv01 pv.0 logvol / --vgname=rhel_rhellv01 --name=root --size 5000 --fstype=xfs logvol /home --vgname=rhel_rhellv01 --name=home --fstype=xfs --size \ 1000 --fsoptions="defaults,nodev,nosuid,noexec" logvol swap --fstype="swap" --name=swap --vgname=rhel_rhellv01 --size 1000 snap... Next I tried a reinstall with a modified kickstart ...snip bootloader --location=mbr --append="rhgb quiet crashkernel=auto" part /boot --fstype=xfs --size 1000 --asprimary --label BOOT \ --onpart=/dev/disk/by-id/ata-QEMU_HARDDISK_QM00003-part1 part pv.0 --fstype=lvmpv --grow --asprimary \ --onpart=/dev/disk/by-id/ata-QEMU_HARDDISK_QM00003-part2 --noformat volgroup rhel_rhellv01 --noformat logvol / --vgname=rhel_rhellv01 --name=root --size 5000 --fstype=xfs \ --useexisting logvol /home --vgname=rhel_rhellv01 --name=home --fstype=xfs --size \ 1000 --fsoptions="defaults,nodev,nosuid,noexec" --noformat logvol swap --fstype="swap" --name=swap --vgname=rhel_rhellv01 --size \ 1000 --useexisting snap... this is working with RHEL 7 (so my kickstart is not totally wrong)! but with RHEL 8 error: logical volume "root" given in logvol command does not exist What is wrong with my kickstart? What should I change that it works with RHEL 8 too? Best Regards, Markus From dafydd at dafydd.com Thu Aug 19 20:40:53 2021 From: dafydd at dafydd.com (David Barr) Date: Thu, 19 Aug 2021 13:40:53 -0700 Subject: Reinstall and keep data LV In-Reply-To: References: Message-ID: On 8/19/21 12:54, Markus Falb wrote: > error: logical volume "root" given in logvol command does not exist > > What is wrong with my kickstart? What should I change that it works > with RHEL 8 too? > > Best Regards, Markus I'm going to guess that it can't find the previous root LV that you've asked it for with --useexisting. Do you have a way to test without that option? Will it build a bare root LV on a new VG? David -- David/dafydd PGP Public Key Read. Read more. Read lots. Read /everything/! -------------- next part -------------- An HTML attachment was scrubbed... URL: From wnefal at gmail.com Thu Aug 19 23:26:20 2021 From: wnefal at gmail.com (Markus Falb) Date: Fri, 20 Aug 2021 01:26:20 +0200 Subject: Reinstall and keep data LV In-Reply-To: References: Message-ID: On Thu, Aug 19, 2021 at 10:52 PM David Barr wrote: > > On 8/19/21 12:54, Markus Falb wrote: > > > > error: logical volume "root" given in logvol command does not exist > > > > What is wrong with my kickstart? What should I change that it works > > with RHEL 8 too? > > > > Best Regards, Markus > > > I'm going to guess that it can't find the previous root LV that you've asked it for with --useexisting. > Do you have a way to test without that option? Will it build a bare root LV on a new VG? I tested like you said. I removed --useexisting from logvol root, but then it complains about home etc.. So I removed --usexisting and --noformat from all logvol definitions and it actually began installing, but failed with error: logical volume "swap" already exists in volume group "rhel_rhellv01" With --useexisting the LVs are not found and it does not even begin the installation. Without --useexisting it begins installation but can't create the LVs because they already exist. This does not surprise me. And when I look on the console the LVs are not activated, but I can do vgchange -ay. However, the old /boot is destroyed at that point and the old system won't boot anymore and I have to install/repair again. I'm not sure how to proceed. Maybe I try Fedora to see if it only fails with RHEL 8 (as I said it does work with RHEL 7) Best Regards, Markus From amm at lanl.gov Wed Aug 25 17:46:10 2021 From: amm at lanl.gov (Aaron Morrison) Date: Wed, 25 Aug 2021 11:46:10 -0600 Subject: [EXTERNAL] Reinstall and keep data LV In-Reply-To: References: Message-ID: We use pre/post script to backup / restore certain data on LVM and SW Raid systems... Obviously, you'll need to modify which LVM names to mount, etc, but this should get you started.... #!/bin/bash mkdir -p /mnt/oldroot ## mdadm scan for raid to save drive mkdir -p /etc/mdadm mdadm --examine --scan >>/etc/mdadm/mdadm.conf mdadm --assemble --scan # # Look for old LVM root # In RHEL6, we deprecate mounting non-lvm file systems # mounted="" lvm="" # Check for lvm disk existence if lvm lvmdiskscan -l 2>1 /dev/null|grep -q '[1-9] LVM physical'; then ?? # root volume group scan ?? VGNAME=$(lvm vgdisplay -C --noheadings|grep -i root|awk '{print $1}') ?? # enable rootvg ?? lvm vgchange -a y \$VGNAME ?? # root and var logvols we care about ?? LVROOT=$(lvm lvdisplay -C --noheadings $VGNAME|grep -i volroot|awk '{print $1}') ?? LVVAR=$(lvm lvdisplay -C --noheadings $VGNAME|grep -i volvar|awk 'NR==1{print $1}') ?? mount /dev/$VGNAME/$LVROOT /mnt/oldroot ?? mount /dev/$VGNAME/$LVVAR /mnt/oldroot/var ?? mounted="true" ?? lvm="true" ?? (cd /mnt/oldroot; tar cvpf /tmp/oldfiles.tar etc/krb5.keytab etc/ssh/ssh_host_* etc/exports var/spool/cron/ var/cfengine/ppkeys/ ) ?? if [ -n $mounted ] ; then ????? cd /; ????? umount /mnt/oldroot/var ????? umount /mnt/oldroot ?? fi ?? if [ -n $lvm ]; then ????? lvm vgchange -a n $VGNAME ?? fi else ?? echo "Warning! Unable to mount old filesystem for backup/restore for system files..." fi ##stop sw raid if any mdadm --stop --scan Markus Falb wrote: > Hi, > I am struggling! > I want to reinstall LVM based installs. I want to keep some LVs (data) > but want to overwrite the other LVs(system) > > First I did a kickstart of RHEL 7, here the storage related lines > > ...snip > zerombr > clearpart --all --initlabel > part pv.0 --fstype=lvmpv --grow --asprimary > part /boot --fstype=xfs --size 1000 --asprimary --label BOOT > volgroup rhel_rhellv01 pv.0 > logvol / --vgname=rhel_rhellv01 --name=root --size 5000 --fstype=xfs > logvol /home --vgname=rhel_rhellv01 --name=home --fstype=xfs --size \ > 1000 --fsoptions="defaults,nodev,nosuid,noexec" > logvol swap --fstype="swap" --name=swap --vgname=rhel_rhellv01 --size 1000 > snap... > > Next I tried a reinstall with a modified kickstart > > ...snip > bootloader --location=mbr --append="rhgb quiet crashkernel=auto" > part /boot --fstype=xfs --size 1000 --asprimary --label BOOT \ > --onpart=/dev/disk/by-id/ata-QEMU_HARDDISK_QM00003-part1 > part pv.0 --fstype=lvmpv --grow --asprimary \ > --onpart=/dev/disk/by-id/ata-QEMU_HARDDISK_QM00003-part2 --noformat > volgroup rhel_rhellv01 --noformat > logvol / --vgname=rhel_rhellv01 --name=root --size 5000 --fstype=xfs \ > --useexisting > logvol /home --vgname=rhel_rhellv01 --name=home --fstype=xfs --size \ > 1000 --fsoptions="defaults,nodev,nosuid,noexec" --noformat > logvol swap --fstype="swap" --name=swap --vgname=rhel_rhellv01 --size \ > 1000 --useexisting > snap... > > this is working with RHEL 7 (so my kickstart is not totally wrong)! > > but with RHEL 8 > > error: logical volume "root" given in logvol command does not exist > > What is wrong with my kickstart? What should I change that it works > with RHEL 8 too? > > Best Regards, Markus > > _______________________________________________ > Kickstart-list mailing list > Kickstart-list at redhat.com > https://listman.redhat.com/mailman/listinfo/kickstart-list > From mats.o.karlsson at gmail.com Wed Aug 25 20:44:02 2021 From: mats.o.karlsson at gmail.com (Mats Karlsson) Date: Wed, 25 Aug 2021 22:44:02 +0200 Subject: undubscribe Message-ID: undubscribe -------------- next part -------------- An HTML attachment was scrubbed... URL: From wnefal at gmail.com Thu Aug 26 16:11:49 2021 From: wnefal at gmail.com (Markus Falb) Date: Thu, 26 Aug 2021 18:11:49 +0200 Subject: Reinstall and keep data LV In-Reply-To: References: Message-ID: > On 19.08.2021, at 22:40, David Barr wrote: > > On 8/19/21 12:54, Markus Falb wrote: >> error: logical volume "root" given in logvol command does not exist >> >> What is wrong with my kickstart? What should I change that it works >> with RHEL 8 too? >> >> Best Regards, Markus >> > > I'm going to guess that it can't find the previous root LV that you've asked it for with --useexisting. Do you have a way to test without that option? Will it build a bare root LV on a new VG? > > David I have something that works, but it was somewhat difficult to debug. Anaconda says ?kickstart insufficient? and "error: logical volume "root" given in logvol command does not exist?. The message seems clear but after complaining anaconda is now in interactive mode and the LVs are visible and I can interactive finish the installation. At that point I had the hope that the anaconda generated /root/anaconda-ks.cfg would give some hints but no news there. The solution is to activate the LVs in %pre It turns out that there is /dev/sda present but not the device files for /dev/sdaX. ?snip %pre mknod /dev/sda2 b 8 2 pvscan vgchange -ay %end snap? alternatively this oneliner is working too, interestingly ?snip %pre parted /dev/sda unit MiB print %end snip? Note that with the parted command it is not necessary to vgchange afterwards. Is there a builtin kickstart command that accomplishes the same instead of some %pre? If not, why is %pre necessary? %pre was not necessary with RHEL7. Is this by design or is it a bug? Best Regards, Markus From sreyan32 at gmail.com Fri Aug 27 19:57:55 2021 From: sreyan32 at gmail.com (Sreyan Chakravarty) Date: Sat, 28 Aug 2021 01:27:55 +0530 Subject: Why does Anaconda leave 100GB empty for LVM Thin ? Message-ID: Hi, I have just installed a new Fedora 33 KDE system. So this is my layout: NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sda 8:0 0 931.5G 0 disk ??sda1 8:1 0 512M 0 part /boot/efi ??sda2 8:2 0 1G 0 part /boot ??sda3 8:3 0 930G 0 part ??luks-aee439f3-528c-4481-ab09-622304e727bc 253:0 0 930G 0 crypt ??vgfedora-pool00_tmeta 253:1 0 424M 0 lvm ? ??vgfedora-pool00-tpool 253:3 0 829.2G 0 lvm ? ??vgfedora-fedora 253:4 0 829.2G 0 lvm / ? ??vgfedora-pool00 253:5 0 829.2G 1 lvm ??vgfedora-pool00_tdata 253:2 0 829.2G 0 lvm ??vgfedora-pool00-tpool 253:3 0 829.2G 0 lvm ??vgfedora-fedora 253:4 0 829.2G 0 lvm / ??vgfedora-pool00 253:5 0 829.2G 1 lvm The same thing as above in pastebin: https://pastebin.com/raw/xwXngMRh If you notice that /dev/sda3 is of size 930G, but the volume group is only 829.2 G. Why is that ? I have selected the size of the volume group as "Large as possible", but still 100G is left out. Is this some kind of recommended setting for thin-LVMs ? I am selecting Thin-LVM with LUKS2 during the install. Can someone help me understand why this is happening and how I can fix it ? Will making a custom kickstart help here ? -- Regards, Sreyan Chakravarty -------------- next part -------------- An HTML attachment was scrubbed... URL: From joe_wulf at yahoo.com Fri Aug 27 21:10:17 2021 From: joe_wulf at yahoo.com (Joe Wulf) Date: Fri, 27 Aug 2021 21:10:17 +0000 (UTC) Subject: Why does Anaconda leave 100GB empty for LVM Thin ? In-Reply-To: References: Message-ID: <355950609.364252.1630098617275@mail.yahoo.com> Sreyan, Since you've essentially asked this same question a month or so back, you didn't get any relief from the assistance given then?Is this a NEW build of your system since that previous email thread discussed this very same issue? Was this a F33 system you've manually installed through the GUI (or the like)?Would you share screenshot(s) of your partitioning layout out of the GUI, please. Since F34 is now out, consider attempting the same installation with the newer version of the OS. Is this a physical system, or virtual?? If virtual, which technology?What and where is this drive being partitioned?? If a hardware drive, what manufacture, brand and model. I see the output you shared was from 'lsblk -a', which is helpful. Please share the full output for 'lsblk -fas',? 'lsblk? -aflpms',? 'vgdisplay -v' and 'lvdisplay -v'Pastebin would be fine to review these, I think. Thank you. On Friday, August 27, 2021, 03:59:45 PM EDT, Sreyan Chakravarty wrote: Hi, I have just installed a new Fedora 33 KDE system.? So this is my layout: NAME ?????????????????????????????????????????MAJ:MIN RM ??SIZE RO TYPE ?MOUNTPOINT sda ????????????????????????????????????????????8:0 ???0 931.5G ?0 disk ?? ??sda1 ?????????????????????????????????????????8:1 ???0 ??512M ?0 part ?/boot/efi ??sda2 ?????????????????????????????????????????8:2 ???0 ????1G ?0 part ?/boot ??sda3 ?????????????????????????????????????????8:3 ???0 ??930G ?0 part ?? ???luks-aee439f3-528c-4481-ab09-622304e727bc 253:0 ???0 ??930G ?0 crypt ? ?????vgfedora-pool00_tmeta ??????????????????253:1 ???0 ??424M ?0 lvm ??? ???? ??vgfedora-pool00-tpool ????????????????253:3 ???0 829.2G ?0 lvm ??? ???? ????vgfedora-fedora ????????????????????253:4 ???0 829.2G ?0 lvm ??/ ???? ????vgfedora-pool00 ????????????????????253:5 ???0 829.2G ?1 lvm ??? ?????vgfedora-pool00_tdata ??????????????????253:2 ???0 829.2G ?0 lvm ??? ???????vgfedora-pool00-tpool ????????????????253:3 ???0 829.2G ?0 lvm ??? ?????????vgfedora-fedora ????????????????????253:4 ???0 829.2G ?0 lvm ??/ ?????????vgfedora-pool00 ????????????????????253:5 ???0 829.2G ?1 lvm ?? The same thing as above in pastebin:?https://pastebin.com/raw/xwXngMRh If you notice that /dev/sda3 is of size 930G, but the volume group is only 829.2 G. Why is that ? I have selected the size of the volume group as "Large as possible", but still 100G is left out. Is this some kind?of recommended?setting for thin-LVMs ? I am selecting Thin-LVM with LUKS2 during the install. Can someone help me understand why this is happening and how I can fix it ?? Will making a custom kickstart help here ? -- Regards,Sreyan Chakravarty_______________________________________________ Kickstart-list mailing list Kickstart-list at redhat.com https://listman.redhat.com/mailman/listinfo/kickstart-list -------------- next part -------------- An HTML attachment was scrubbed... URL: From gordon.messmer at gmail.com Sat Aug 28 03:29:17 2021 From: gordon.messmer at gmail.com (Gordon Messmer) Date: Fri, 27 Aug 2021 20:29:17 -0700 Subject: Why does Anaconda leave 100GB empty for LVM Thin ? In-Reply-To: References: Message-ID: <06ed96ca-8f54-2587-aeea-aa1429c3e638@gmail.com> On 8/27/21 12:57 PM, Sreyan Chakravarty wrote: > If you notice that /dev/sda3 is of size 930G, but the volume group is > only 829.2 G. I don't think the size of the group is represented in the output of lsblk.? You should get that information in detail from "vgdisplay" or in brief from "vgs". From dlehman at redhat.com Mon Aug 30 17:12:36 2021 From: dlehman at redhat.com (David Lehman) Date: Mon, 30 Aug 2021 12:12:36 -0500 Subject: Why does Anaconda leave 100GB empty for LVM Thin ? In-Reply-To: References: Message-ID: Hi, On Fri, Aug 27, 2021 at 3:00 PM Sreyan Chakravarty wrote: > Hi, > > I have just installed a new Fedora 33 KDE system. > > So this is my layout: > > > NAME MAJ:MIN RM SIZE RO TYPE > MOUNTPOINT > sda 8:0 0 931.5G 0 disk > ??sda1 8:1 0 512M 0 part > /boot/efi > ??sda2 8:2 0 1G 0 part > /boot > ??sda3 8:3 0 930G 0 part > ??luks-aee439f3-528c-4481-ab09-622304e727bc 253:0 0 930G 0 crypt > ??vgfedora-pool00_tmeta 253:1 0 424M 0 lvm > ? ??vgfedora-pool00-tpool 253:3 0 829.2G 0 lvm > ? ??vgfedora-fedora 253:4 0 829.2G 0 lvm / > ? ??vgfedora-pool00 253:5 0 829.2G 1 lvm > ??vgfedora-pool00_tdata 253:2 0 829.2G 0 lvm > ??vgfedora-pool00-tpool 253:3 0 829.2G 0 lvm > ??vgfedora-fedora 253:4 0 829.2G 0 lvm / > ??vgfedora-pool00 253:5 0 829.2G 1 lvm > > The same thing as above in pastebin: https://pastebin.com/raw/xwXngMRh > > If you notice that /dev/sda3 is of size 930G, but the volume group is only > 829.2 G. > > Why is that ? I have selected the size of the volume group as "Large as > possible", but still 100G is left out. > > Is this some kind of recommended setting for thin-LVMs ? > > I am selecting Thin-LVM with LUKS2 during the install. > > Can someone help me understand why this is happening and how I can fix it > ? > There are some circumstances under which LVM may need additional space for thin pool metadata. When we added support for thin provisioning they strongly recommended that we reserve a portion of the volume group space for this purpose.Initially it was 20% of the pool size, but the calculation may be more nuanced now. I wouldn't consider removing this bit of free space "fixing" anything unless you plan to actively monitor your system to ensure that your thin pool doesn't run out of space for metadata. > > Will making a custom kickstart help here ? > Maybe... It has been a while since I worked on this code, but you _might_ be able to override this in kickstart using `--reserved-space` or `--reserved-percent` options to the `volgroup` command. HTH, David > > -- > Regards, > Sreyan Chakravarty > _______________________________________________ > Kickstart-list mailing list > Kickstart-list at redhat.com > https://listman.redhat.com/mailman/listinfo/kickstart-list -------------- next part -------------- An HTML attachment was scrubbed... URL: From dlehman at redhat.com Mon Aug 30 17:49:07 2021 From: dlehman at redhat.com (David Lehman) Date: Mon, 30 Aug 2021 12:49:07 -0500 Subject: Reinstall and keep data LV In-Reply-To: References: Message-ID: On Thu, Aug 26, 2021 at 11:14 AM Markus Falb wrote: > > > > On 19.08.2021, at 22:40, David Barr wrote: > > > > On 8/19/21 12:54, Markus Falb wrote: > >> error: logical volume "root" given in logvol command does not exist > >> > >> What is wrong with my kickstart? What should I change that it works > >> with RHEL 8 too? > >> > >> Best Regards, Markus > >> > > > > I'm going to guess that it can't find the previous root LV that you've > asked it for with --useexisting. Do you have a way to test without that > option? Will it build a bare root LV on a new VG? > > > > David > > I have something that works, but it was somewhat difficult to debug. > > Anaconda says ?kickstart insufficient? and "error: logical volume "root" > given in logvol command does not exist?. The message seems clear but after > complaining anaconda is now in interactive mode and the LVs are visible and > I can interactive finish the installation. At that point I had the hope > that the anaconda generated /root/anaconda-ks.cfg would give some hints but > no news there. > > The solution is to activate the LVs in %pre > It turns out that there is /dev/sda present but not the device files for > /dev/sdaX. > > ?snip > %pre > mknod /dev/sda2 b 8 2 > pvscan > vgchange -ay > %end > snap? > > alternatively this oneliner is working too, interestingly > > ?snip > %pre > parted /dev/sda unit MiB print > %end > snip? > > Note that with the parted command it is not necessary to vgchange > afterwards. > > Something is wrong if no device nodes are being created for your partitions, and I don't think the problem is in the installer code. That is the job of udev and the kernel IIRC. > Is there a builtin kickstart command that accomplishes the same instead of > some %pre? > If not, why is %pre necessary? %pre was not necessary with RHEL7. Is this > by design or is it a bug? > Sounds like a bug to me, but not an installer bug. I would start by reading through the syslog and see what it says about sda. It might tell you why it isn't creating the partitions as expected. > > Best Regards, Markus > > > _______________________________________________ > Kickstart-list mailing list > Kickstart-list at redhat.com > https://listman.redhat.com/mailman/listinfo/kickstart-list -------------- next part -------------- An HTML attachment was scrubbed... URL: From bcl at redhat.com Mon Aug 30 21:26:47 2021 From: bcl at redhat.com (Brian C. Lane) Date: Mon, 30 Aug 2021 14:26:47 -0700 Subject: Reinstall and keep data LV In-Reply-To: References: Message-ID: On Thu, Aug 26, 2021 at 06:11:49PM +0200, Markus Falb wrote: > The solution is to activate the LVs in %pre > It turns out that there is /dev/sda present but not the device files for /dev/sdaX. > > ?snip > %pre > mknod /dev/sda2 b 8 2 > pvscan > vgchange -ay > %end > snap? > > alternatively this oneliner is working too, interestingly > > ?snip > %pre > parted /dev/sda unit MiB print > %end > snip? > > Note that with the parted command it is not necessary to vgchange afterwards. > > Is there a builtin kickstart command that accomplishes the same instead of some %pre? > If not, why is %pre necessary? %pre was not necessary with RHEL7. Is this by design or is it a bug? This is a bug of some sort, as David said. The fact that parted print fixed it makes me think that your storage is slow, since all parted does is open/close the device and tell the kernel to rescan the partitions -- which should have already happened at boot time when the device appeared. Brian -- Brian C. Lane (PST8PDT) - weldr.io - lorax - parted - pykickstart From wnefal at gmail.com Tue Aug 31 21:34:26 2021 From: wnefal at gmail.com (Markus Falb) Date: Tue, 31 Aug 2021 23:34:26 +0200 Subject: Reinstall and keep data LV In-Reply-To: References: Message-ID: <4C87CC5E-8714-4531-B55E-8A8A94DB5904@gmail.com> > On 30.08.2021, at 23:26, Brian C. Lane wrote: > > On Thu, Aug 26, 2021 at 06:11:49PM +0200, Markus Falb wrote: > >> The solution is to activate the LVs in %pre >> It turns out that there is /dev/sda present but not the device files for /dev/sdaX. >> >> ?snip >> %pre >> mknod /dev/sda2 b 8 2 >> pvscan >> vgchange -ay >> %end >> snap? >> >> alternatively this oneliner is working too, interestingly >> >> ?snip >> %pre >> parted /dev/sda unit MiB print >> %end >> snip? >> >> Note that with the parted command it is not necessary to vgchange afterwards. >> >> Is there a builtin kickstart command that accomplishes the same instead of some %pre? >> If not, why is %pre necessary? %pre was not necessary with RHEL7. Is this by design or is it a bug? > > This is a bug of some sort, as David said. The fact that parted print > fixed it makes me think that your storage is slow, since all parted does > is open/close the device and tell the kernel to rescan the partitions -- > which should have already happened at boot time when the device > appeared. I am testing with a kvm VM created with Virtual Machine Manager on CentOS 7. The VM has a scsi disk (changing to IDE or SATA does not change the behaviour) I remember that I was trying ?udevadm settle? in %pre and this was returning fast and that?s why I thought that it was not waiting for some slow udev event. I had another look. I added a sleep 600 and removed the parted from parted (600s should be plenty of time for detection) Here is my interpretation: The kernel *did* detect the partitions in early initramfs ? Aug 31 14:19:50 localhost kernel: sda: sda1 sda2 Aug 31 14:19:50 localhost kernel: sd 0:0:0:0: [sda] Attached SCSI disk ? If I add rd.break kernel parameter I can see that the devices are there. But after switching root (pivoting) they are gone. I do not know if this is expected or not. So while %pre is running sda1 and sda2 are not present given that I did not trigger udev with parted or similar. After %pre is finished it is detecting sda1 and sda2 again, and it is finding the VG and the LVs, but then it is stopping the VG (which is what I find strange) and throwing the error ? initramfs ? Aug 31 14:19:50 localhost kernel: sda: sda1 sda2 Aug 31 14:19:50 localhost kernel: sd 0:0:0:0: [sda] Attached SCSI disk ? pivot root filesystem ? running pre (10 minutes sleep) ? Aug 31 14:30:14 test kernel: sda: sda1 sda2 ? Aug 31 14:30:15 test org.fedoraproject.Anaconda.Modules.Storage[1903]: DEBUG:blivet: DeviceTree.handle_device: name: lvm.vg1-root ; info: {'DEVLINKS': '/dev/disk/by-uuid/9c60e33e-03e0-42c4-a583-868f4fd1b2b4 ' ? Aug 31 14:30:15 test org.fedoraproject.Anaconda.Modules.Storage[1903]: INFO:program:Running [36] lvm vgchange -an lvm.vg1 --config= devices { preferred_names=["^/dev/mapper/", "^/dev/md/", "^/dev/sd"] } log {level=7 file=/tmp/lvm.log syslog=0} ? ? Aug 31 14:30:21 test org.fedoraproject.Anaconda.Modules.Storage[1903]: Logical volume "root" given in logvol command does not exist. ? If someone is interested, I created a gist with the kickstarts and logs at https://gist.github.com/610acf7379f48d0e5c38f4edb9cda176 (you can clone it with git) I found no obvious error, but there is a lot of stuff and I could have missed something easily. Given that anaconda sees the LVs, do you still think that it is a kernel problem or the storage too slow? Best Regards, Markus and thanks too all who took the time answering. From bcl at redhat.com Tue Aug 31 23:37:40 2021 From: bcl at redhat.com (Brian C. Lane) Date: Tue, 31 Aug 2021 16:37:40 -0700 Subject: Reinstall and keep data LV In-Reply-To: <4C87CC5E-8714-4531-B55E-8A8A94DB5904@gmail.com> References: <4C87CC5E-8714-4531-B55E-8A8A94DB5904@gmail.com> Message-ID: On Tue, Aug 31, 2021 at 11:34:26PM +0200, Markus Falb wrote: [snip] > > Given that anaconda sees the LVs, do you still think that it is a kernel > problem or the storage too slow? > > Best Regards, Markus > and thanks too all who took the time answering. Oh, that's *is* weird. I'm not sure where the problem would be, but I'd start with the kernel I guess and file a bug with as much detail as you can. It might also be worthwhile to log the output of udevadm monitor and see if you can see what makes the partitions vanish. Brian -- Brian C. Lane (PST8PDT) - weldr.io - lorax - parted - pykickstart