Hello! I was experiencing that, too. There may be a race in initramfs between the kernel enumerating the bcache devices and the scripts trying to figure out the filesystems. There's two ways around it: The distribution should fix the initramfs scripts to wait longer for rootfs device nodes to appear, or you could try adding rootdelay=5 to your kernel cmdline as a temporary workaround (this delays mounting for 5 seconds, you can try different values). I'm using dracut as initramfs generator and it seems fixed since a few versions. I don't think this is a bcache issue: initramfs needs to probe bcache, then the filesystems. It's more likely this is a udev issue. Regards, Kai Am Di., 24. Sept. 2019 um 10:40 Uhr schrieb Coly Li <colyli@xxxxxxx>: > > On 2019/9/24 1:33 上午, Marcelo RE wrote: > > Hi. > > > > have problems running bcache with the kernel 5.x in KUbuntu. It work > > fine with kernel 4.x but fail to start with 5.x. Currently using 5.2.3 > > (linux-image-unsigned-5.2.3-050203-generic). > > When power on the laptop, sometimes it start to busybox and sometime > > it boot fine. > > If boot to busybox, I just enter reboot until it starts correctly. > > I tested: > > linux-image-4.15.0-29-generic > > linux-image-4.15.0-34-generic > > linux-image-5.0.0-20-generic > > linux-image-5.0.0-21-generic > > linux-image-5.0.0-23-generic > > linux-image-5.0.0-25-generic > > linux-image-5.0.0-27-generic > > linux-image-5.0.0-29-generic > > linux-image-unsigned-5.2.3-050203-generic > > > > What can be done? > > It is not easy to locate the problem by kernel versions. There are quite > a lot fixes since 4.15 to 5.2. > > If there is any more information or clue, maybe I can help to guess. > > -- > > Coly Li
