Looking at the syslog and kern.log, the kernel has emitted the change events which trigger the bcache rules, for all 12 devices, each time. So what remains to understand is whether udevd ran the hook (69-bcache.rules) and I see no reason it wouldn't.
% grep kernel.*register_bcache /tmp/bcache-syslog.raw | head -n 13 Jan 22 14:37:54 ln-sv-ostk08 kernel: [ 14.478597] bcache: register_bcache() error /dev/sdh: device already registered (emitting change event) Jan 22 14:37:54 ln-sv-ostk08 kernel: [ 14.478608] bcache: register_bcache() error /dev/sdg: device already registered (emitting change event) Jan 22 14:37:54 ln-sv-ostk08 kernel: [ 14.478673] bcache: register_bcache() error /dev/sdb: device already registered (emitting change event) Jan 22 14:37:54 ln-sv-ostk08 kernel: [ 14.478684] bcache: register_bcache() error /dev/sde: device already registered (emitting change event) Jan 22 14:37:54 ln-sv-ostk08 kernel: [ 14.478695] bcache: register_bcache() error /dev/sdc: device already registered (emitting change event) Jan 22 14:37:54 ln-sv-ostk08 kernel: [ 14.478843] bcache: register_bcache() error /dev/sdf: device already registered (emitting change event) Jan 22 14:37:54 ln-sv-ostk08 kernel: [ 14.492735] bcache: register_bcache() error /dev/sdd: device already registered (emitting change event) Jan 22 14:37:54 ln-sv-ostk08 kernel: [ 14.522047] bcache: register_bcache() error /dev/nvme0n1p3: device already registered Jan 22 14:37:54 ln-sv-ostk08 kernel: [ 14.529593] bcache: register_bcache() error /dev/sda1: device already registered (emitting change event) Jan 22 14:37:54 ln-sv-ostk08 kernel: [ 14.537218] bcache: register_bcache() error /dev/nvme0n1p1: device already registered Jan 22 14:37:54 ln-sv-ostk08 kernel: [ 14.537606] bcache: register_bcache() error /dev/sdi4: device already registered (emitting change event) Jan 22 14:37:54 ln-sv-ostk08 kernel: [ 14.557305] bcache: register_bcache() error /dev/sdi3: device already registered (emitting change event) I didn't find the actual systemd journal (/run/log/journal/<hash>) in the sosreport, so we cannot see much of the udevd logging. It's likely that one will need to enable udevd verbose debugging and reproduce and capture to see what may be going on there. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1812925 Title: No OSDs has been initialized in random unit with "No block devices detected using current configuration" To manage notifications about this bug go to: https://bugs.launchpad.net/charm-ceph-osd/+bug/1812925/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
