1

I am running Linux Ubuntu 16.04 LTS, and I wasn't able to run my Operating System anymore after my latest update attempt. Here's what happened:

  1. I first ran the upgrade procedures through terminal as usual: sudo apt-get update, sudo apt-get upgrade, sudo apt-get autoremove, and sudo apt-get autoremove.
  2. However, I was told that 4 not upgraded, so I decided to run Software Updater as well, and there was indeed updates available concerning Ubuntu base. I installed those successfully, and decided to proceed with restart my system.

After the restart, my system doesn't start though. Instead, I receive the following error message:

[ 1.452270] genirq: Flags mismatch irq 0. 00000080 (nvme0q0) vs. 00015a00 (timer)
[ 1.452551] iounmap: bad address ffffc90001b88000
Scanning for Btrfs filesystems
Gave up waiting for root device. Common problems:
 - Boot args (cat /proc/cmdline)
  - Check rootdelay= (did the system wait for the right device?)
  - Check root= (did the system wait for the right device?)
 - Missing modules (cat /proc/modules; ls /dev)
ALERT! UUID=a5ccaf22-ffde-44c2-8c59-84a851f9fd90 does not exist. Dropping to shell!

BusyBox v1.222.1 (Ubuntu 1:1.22.0-15ubuntu1) built-in shell (ash)
Enter 'help' for a list of built-in commands.

(initramfs)

I was able to recover my system through the +Advanced options for Ubuntu, which I opened after. There I had total of nine choices, three options for each version. I first tried the recovery version of the latest one, but it didn't work. After that, I tried the generic version of the second latest, and — thank God — that one managed to recover my system!

UPDATE: The three version I have available are the following, running from the latest to the oldest: 1) Ubuntu, with Linux 4.4.0-3**9** generic, 2) Ubuntu, with Linux 4.4.0-3**8** generic, and 3) Ubuntu, with Linux 4.4.0-3**7** generic. With the second one I was able to start the system.

What went wrong? How can I fix it? Now I am afraid to update my system :-( Please help!!!

Jayaguru-Shishya
  • 483

1 Answers1

1

I got the exact same problem. Downgraded to 4.4.0-38, then blocked -39 from being installed, by pinning that version with priority -1. This is a kernel regression, which might show up in later 4.4.0 updates too. Hopefully it is fixed in the kernel version shipping with Ubuntu 16.10. The -39 kernel fails to detect my NVMe SSD that I'm booting from, while the -38 kernel works perfectly. According to the release notes there were two fixes to the NVMe code: (LP: #1602724) and (LP: #1620317). It is possible one of these broke the NVMe detection.

Fairglow
  • 26