http://bugzilla.suse.com/show_bug.cgi?id=1127766 http://bugzilla.suse.com/show_bug.cgi?id=1127766#c5 Ancor Gonzalez Sosa <ancor@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(ohering@suse.com) --- Comment #5 from Ancor Gonzalez Sosa <ancor@suse.com> --- (In reply to Ancor Gonzalez Sosa from comment #4)
(In reply to Stefan Hundhammer from comment #1)
This "installation-helper" call tries to create a pre-update snapshot. It shouldn't do that in the first place. That this fails because there is no .snapshots directory is only a consequence of that.
Now I wonder why it even wants to create that snapshot.
From the attached logs:
Checking if Snapper is configured: "/usr/bin/snapper --no-dbus --root=%{root} list-configs | /usr/bin/grep "^root " >/dev/null" returned: {"exit"=>0, "stderr"=>"", "stdout"=>""}
Since the exit code of that command is zero, the installer concludes Snapper if configured and a snapshot can/must be performed.
Needless to say, %{root} is substituted by /mnt when the command is executed. Olaf, since your system is so special, would you mind to paste the full output of this command? /usr/bin/snapper --no-dbus --root=/mnt list-configs Executed in the installation media, after the system to upgrade has been mounted. ==== If that's too hard, I guess it would be enough to just execute this in any of the systems that are installed into that filesystem: /usr/bin/snapper --no-dbus list-configs ==== Or alternatively do something like this with a rescue system ...activate the volume... mount -t btrfs /dev/sd240_crypt_lvm/sd240_btrfs /mnt /usr/bin/snapper --no-dbus --root=/mnt list-configs The first alternative would be the best, but whatever works for you... I guess you get the idea. -- You are receiving this mail because: You are on the CC list for the bug.