On Mon, Jan 22, 2018 at 9:03 AM, Oliver Kurz <okurz@suse.de> wrote:
Unfortunately, it complains that there are no configs. I have never seen an openSUSE install not set up snapper. Could this have happened?
Yes, can happen. If the root device is too small the installer suggests to not use snapshots and therefore no snapper config is created.
The root partition is bigger than on other systems where this has been set up.
Or could it be that it lost the config info when things went bad?
I doubt this would happen.
One would think so. Otherwise there is a fundamental flaw in the system!
I recommend a rescue system, try to mount the existing partitions, chroot into the existing installation and check if everything that is expected is there, e.g. in /boot/ the kernel and initrd. You might be able to call `zypper dup` within the chroot to repair some missing packages in case the upgrade got interrupted.
I mounted an older kernel. What I found was very odd. Many of the kernel module files for the kernel that was being installed when the system turned off were 0 sized! This makes no sense as there are many GB free on the partition. So I had to install the latest Tumbleweed kernel packages via rpm. After that, the boot and WiFi works as expected. I had also lost the Broadcom WiFi in the recovery kernel. But that is working as well. Anyway, all seems okay now. Except snapper is not configured. I need to find exactly how yast would have set up snapper in the original install, and then do the same. -- Roger Oberholtzer -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org