Yast2: Initializing the target directoyr failed.

Installation failed.  Details: Taget not initialized.  Package installation will be aborted.

Can’t fix my system when I can’t reinstall base packages or reinstall grub, nor boot the system.

Grossly insufficient data for assistance purposes!

What CPU and GPU(s) do you have? What did you do, in as much detail as possible, before that message appeared?

YaST is a very versatile tool do do many, many system manager tasks. You should at last explain what you are doing in YaST.

Deleted too much from /.snapshots and lost some / folders such as /bin (empty and I had to create it) and others.

I thnk

rm -r /.snapshots/410

must have deleted way more than what I intended.

I am not sure yet if I have any snapshot data left.

I am in the 15.2 leap installer and I just want to get in grub and a few other basics, and re-upgrade from my zypp cache. I started realizing I don’t like redownloading something I just received so I made a cache on my home partition in the LV I use.

Why when trying to install pieces of 15.2 does it say something about target not initialized once it gets to the install stage? I did not do this before I expanded the (not the LV – no issue there) filesystem size (or rather the btrfs slack space.

This is why I have free space to upgrade packages, but now I cannot.

I do not use btrfs and thus also not it’s snapshots, but I assume that doing this is rather destructive. I have no idea why you did that. Not for managing snapshots because for that there are special commands.

This is perfectly valid. But - “rm -r” works bottom up - it cannot remove directories until they are empty, so it first removes the content of directories. And this is not possible for read-only subvlumes on btrfs - you cannot delete anything inside such subvolume and you cannot “rm” non-empty subvolume. If this command worked it means this snapshot was read-write - which sounds very much like it was the currently mounted root filesystem.

Of course doing “rm -r /” is going to result in problems …

I have an LVM with root part 10G free.

  --- Volume group ---
  VG Name               system
  System ID             
  Format                lvm2
  Metadata Areas        1
  Metadata Sequence No  7
  VG Access             read/write
  VG Status             resizable
  MAX LV                0
  Cur LV                3
  Open LV               0
  Max PV                0
  Cur PV                1
  Act PV                1
  VG Size               107.74 GiB
  PE Size               4.00 MiB
  Total PE              27582
  Alloc PE / Size       27582 / 107.74 GiB
  Free  PE / Size

Root is 52 GB and has 10 GB free. I didn’t have issues before I expanded root filesystem size. This has caused the error

btrfs filesystem resize mounted path of /dev/system/root.

Can’t find anything in documents about this particular message.

You show a Volume Group with size 107.74 GiB. But that does not tell us anything about the LV size, nor about the file system that is on that LV.

“Root is 52 GB and has 10 GB free”. Nice stiory, but we want to see the facts.

I understand it’s for technical verification but I’m not making this up.

I had a 42GB root filesystem and a 57GB /home in a 97GB LVM.

Ran out of partition space.

So I expanded the LVM to 107GB and the root partition was still 42GB.

At this point other than not being able to install packages from installer because you know, I’m out of space (250mb free is not enough to fix the system).

FINALLY, after almost a week of research, I figured out that I needed to mount the root filesystem into some local folder of my choosing, and then do the btrfs resize command. So now root is expanded by 10G but now the installer cannot initialize the lvm? Not sure.
It may just be easier to wipe root and download 15.3, along with my home zypper cache, and move on.

I just don’t like having to think about how the previous system was setup and try recreating that experience, knowing it will take a while before I am happy with the setup and programs installed.

I should run backups. I have at least four working hard drives, there’s not a good reason not to have a full root backup.