Public bug reported:

Hi,

Since I upgrade my desktop to Ubuntu 19.04, the boot process is enable
to find the root file system, and drop me to a single user command line.

It seems that kernel 5.0 does not automatically register the bcache caching 
device (/dev/sdb, SSD). However, it does register the backing device 
(/dev/sda6, rotating HDD). To recover, I have to type the following commands :
  # echo /dev/sdb > /sys/fs/bcache/register
  # lvm vgscan
  # lvm vgchange -ay
  # exit
and then, the boot proceed to its normal end (graphical display manager).


The problem does not occur if the system is booted with kernel 4.18.0.

=========================
# lsb_release -rd
Description:    Ubuntu 19.04
Release:        19.04

# apt-cache policy linux-image-5.0.0-13-generic
linux-image-5.0.0-13-generic:
  Installed: 5.0.0-13.14
  Candidate: 5.0.0-13.14
  Version table:
 *** 5.0.0-13.14 500
        500 http://fr.archive.ubuntu.com/ubuntu disco/main amd64 Packages
        100 /var/lib/dpkg/status

#  apt-cache policy linux-image-4.18.0-17        
linux-image-4.18.0-17-generic:
  Installed: 4.18.0-17.18
  Candidate: 4.18.0-17.18
  Version table:
 *** 4.18.0-17.18 100
        100 /var/lib/dpkg/status

** Affects: linux (Ubuntu)
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1825987

Title:
  kernel 5.0 won't auto register bcache caching device

Status in linux package in Ubuntu:
  New

Bug description:
  Hi,

  Since I upgrade my desktop to Ubuntu 19.04, the boot process is enable
  to find the root file system, and drop me to a single user command
  line.

  It seems that kernel 5.0 does not automatically register the bcache caching 
device (/dev/sdb, SSD). However, it does register the backing device 
(/dev/sda6, rotating HDD). To recover, I have to type the following commands :
    # echo /dev/sdb > /sys/fs/bcache/register
    # lvm vgscan
    # lvm vgchange -ay
    # exit
  and then, the boot proceed to its normal end (graphical display manager).

  
  The problem does not occur if the system is booted with kernel 4.18.0.

  =========================
  # lsb_release -rd
  Description:  Ubuntu 19.04
  Release:      19.04

  # apt-cache policy linux-image-5.0.0-13-generic
  linux-image-5.0.0-13-generic:
    Installed: 5.0.0-13.14
    Candidate: 5.0.0-13.14
    Version table:
   *** 5.0.0-13.14 500
          500 http://fr.archive.ubuntu.com/ubuntu disco/main amd64 Packages
          100 /var/lib/dpkg/status

  #  apt-cache policy linux-image-4.18.0-17        
  linux-image-4.18.0-17-generic:
    Installed: 4.18.0-17.18
    Candidate: 4.18.0-17.18
    Version table:
   *** 4.18.0-17.18 100
          100 /var/lib/dpkg/status

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1825987/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to     : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to