This is a first for me. I am running a dual boot machine. Leap 42.2 and Windows 10 Pro, each on their own SSD. I have been using Leap 42.2 for a few months now and have had no issues with anything. Today I did an update and after the update everything seemed normal. I came back to the computer several hours later and everything had a serious time lag (30 seconds or more), such as opening apps, input from the keyboard, changing desktops, closing apps, etc. There were 14 updates but I did not pay much attention to what they were. I know one was Google Chrome but I cannot remember the rest. I decided to do a reboot to make sure there were no conflicts with the updates and libraries that might still be in ram. That is the last time I have been able to see my linux desktop. I can get to grub but every time I try to boot into Leap 42.2 I end up in emergency mode. The screen is totally blank prior to the emergency screen and my keyboard does not work in the emergency mode screen. I end up having to use the reset button to reboot out of the emergency mode screen. I have used both kernels both in default and recovery and every time end up in emergency mode. With the recovery kernels I do see output to the screen prior to emergency mode but I am not seeing anything that would suggest this failure. This is a basic install, I have done nothing fancy and update regularly when prompted. The only thing that is a bit different is my drive configuration. Besides a separate 500G SSD for Windows and Leap. There is a shared 4T drive that is formatted in NTFS. There is also a NAS Server. Users can access files on the NAS and shared drive from either Windows or Leap. I am typing this from Windows. In Windows I can access files on the NAS server and the shared drive so they are both up and working properly. I am totally stumped what could be wrong. Anyone with ideas on how to get my system back online? Dave -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org