Created attachment 99632 [details] Photo of the error After the upgrading packages through the built in updater, the system fails to boot. This might not be an kde neon specific bug, but maybe more of an ubuntu bug. The system 'hangs' on the loading screen. When I ctrl+alt+f1 you see the error message in the photo. {quote}/dev/mapper/neon-vg-root does not exist{quote} from kernel: 4.4.0-22-generic to kernel: 4.4.0-24-generic
This bug also affects me. I was unable to start my system again. However, I found that "lvm2" was not installed anymore on my system. I guess a "apt full-upgrade" removed it without me noticing it. To fix the problem, I needed to run a live system, open my luks partition, and chroot into the installed system. Then I simply ran "apt install lvm2" and rebooted. Now my system works again. So I guess there is a problem with package dependencies that lvm2 got removed during an update?
attach /var/log/apt/* and /var/log/dpkg/* to the bug report
Created attachment 100178 [details] /var/log/history.log Note that I used apt after solving the problem for me.
Created attachment 100179 [details] /var/log/term.log I just remembered that I installed kmail, removed it, and did and auto-remove afterwards to clean up my system. Looks like the auto-remove also removed lvm2 for some reason.
Created attachment 100180 [details] /var/log/dpkg.log
Correct file names are /var/log/apt/history.log /var/log/apt/term.log (I missed the "apt/" in the attachment description)
Created attachment 100669 [details] Apt History log right after the update that removed LVM2 This is taken moments after Discover installed an update and I found LVM2 missing. No reboots or further apt actions have been taken. Near the bottom you can see the Remove: that gets rid of liblvm2cmd2, libdevmapper, dmeventd, lvm2, liblvm2app2, and libreadline5
Created attachment 100670 [details] Apt Term log right after the update that removed LVM2
Created attachment 100671 [details] Dpkg log right after the update that removed LVM2
I've had this happen a few times myself. I've found myself reinstalling Neon for it. On the most current install I noticed it right after a system update that I completed through the update notification/Discover app. I suspected this update had something to do with it so immediately after it was done I checked for lv* commands. All missing. I attached the relevant logs. I'm going to reinstall lvm2 manually.
Affected me too, unsure if after upgrading some packages (include framework upgrade 5.7.5 to 5.8 and Kernel 4.4.0-36 to 4.4.0-38) or after running "apt autoremove". Package "lvm2" was removed and boot to kernel 4.4.0-38 failed. As fallback I was able to choose Kernel 4.4.0-36 in grub, install package lvm2 and afterwards boot with 4.4.0-38.
I have the same problems. Unfortunately i am not able to get it back running reinstalling lvm2, updating/reinstaling grub or initramfs. :(
4 computers at work with encrypted disks failed to boot today. They were updated with "apt update, apt upgrade, apt autoremove". Fits this bug report perfectly. Managed to fix them by installing lvm2 manually.
This issue has been occurring for months with many reports online, it convinced me to abandon Neon and may have the same effect on many others. This bug should not still be UNCONFIRMED. https://forum.kde.org/viewtopic.php?f=309&t=136107
I also faced this issue with a recent (December) neon (non-lts) user edition installation. Reinstalling lvm2 through a chroot didn't fix the issue for me. I'm generally experienced fixing broken Linux systems, but couldn't fix it within 1-2 hours, so I ended up with reinstalling neon. Upon first upgrade, `apt autoremove` now proposes to remove `dmeventd libdevmapper-event1.02.1 liblvm2app2.2 liblvm2cmd2.02 libreadline5 lvm2 ubuntu-core-launcher` again. I'll not do this and I can investigate the state of the system (at least briefly) if someone tells me what to do.
Hello, I have the same issue on neon-useredition-20161222-1018-amd64. Command "apt autoremove" removed some important applications, and I cant boot to my LUKS encrypted LVM partition anymore, boot is always ending in initramfs without prompt for LUKS password. Unfortunately lvm2 package installation doesn't helped, and I don't remembre which packages was removed exactly. Anyway, nVidia proprietary driver was installed before autoremove.
The first time i saw this, it was on Kubuntu Desktop 14.04. Now, couple of years later, i still see the same dependency issue on KDE neon LTS (based on the latest Ubuntu LTS) Was trying this distro in a virtual machine to see how it looks like, and right after the installation, i saw it was possible to autoremove lvm2, wich cause the present problem. The LVM2 package is added by "apt-get --yes install lupin-casper linux-signed-generic neon-live" during the installation. Once the installation is complete, there should be no invitation to autoremove the following package : dmeventd libdevmapper-event1.02.1 liblvm2app2.2 liblvm2cmd2.02 libreadline5 lvm2 ubuntu-core-launcher Doing apt-get autoremove after the installation remove those packages, and then break the system. To fix, simply switch the installation of those packages to manual mode by doing : sudo apt-get install --reinstall dmeventd libdevmapper-event1.02.1 liblvm2app2.2 liblvm2cmd2.02 libreadline5 lvm2 ubuntu-core-launcher ...you (should) never experience this problem again. :) apt-get autoremove will never ask you again to remove those packages. I suggest bug should be marked with a high priority, because lambda users may never look back to a system that crashed with data loss!
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version? If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!