Sorry for the last mail. Don't know what happend but I loose what I wrote. Here again: Hi Kai. I have set rootdelay=1,2,3,4,5 but it do not solve the problem. I will see dracut to see if it works. For the record, I use Kubuntu 19.04 in an Asus Strix GL702Z with a 256GB SSD and 1TB HD. I have a 100GB SSD partition for the bcache. With Kubuntu 16.04, the config with bcache was really fast. 7s to start to login and 14s to start all the apps in the previous session of KDE. When I update, I jump to 18.04. I boot without problem and intermediately update to 19.04 and in that moment the kernel change. Now it take far more time to boot. Aprox 35s to show the login plus 20s to show the desktop. Regards, Marcelo El mar., 24 sept. 2019 a las 10:32, Marcelo RE (<marcelo.re@xxxxxxxxx>) escribió: > > > > El mar., 24 sept. 2019 a las 9:37, Kai Krakow (<kai@xxxxxxxxxxx>) escribió: > > > > 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
