[Touch-packages] [Bug 1635729] Re: bcache won't start on boot due to exotic block devices filtered in udev rules
please reopen if this is still an issue ** Changed in: systemd (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1635729 Title: bcache won't start on boot due to exotic block devices filtered in udev rules Status in systemd package in Ubuntu: Won't Fix Bug description: If a bcache is created with a Curtis-Wright NVRAM card as caching device, the bcache device will not show up on boot without manual intervention. Tracking this down show this being due to the fact, that line 9 of /lib/udev/rules.d/60-persistent-storage.rules filters on a whitelist of devices (loop*|mmcblk*[0-9]|msblk*[0-9]|mspblk*[0-9]|nvme*|sd*|sr*|vd*|xvd*|bcache*|cciss*|dasd*|ubd*), that doesn't include the NVRAM devices (umem*). A few steps later, this results in bcache_register() not being called. Trivially patching -KERNEL!="loop*|mmcblk*[0-9]|msblk*[0-9]|mspblk*[0-9]|nvme*|sd*|sr*|vd*|xvd*|bcache*|cciss*|dasd*|ubd*", GOTO="persistent_storage_end" +KERNEL!="loop*|mmcblk*[0-9]|msblk*[0-9]|mspblk*[0-9]|nvme*|sd*|sr*|vd*|xvd*|bcache*|cciss*|dasd*|ubd*|umem*", GOTO="persistent_storage_end" resolves the issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1635729/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1635729] Re: bcache won't start on boot due to exotic block devices filtered in udev rules
** Package changed: udev (Ubuntu) => systemd (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1635729 Title: bcache won't start on boot due to exotic block devices filtered in udev rules Status in systemd package in Ubuntu: New Bug description: If a bcache is created with a Curtis-Wright NVRAM card as caching device, the bcache device will not show up on boot without manual intervention. Tracking this down show this being due to the fact, that line 9 of /lib/udev/rules.d/60-persistent-storage.rules filters on a whitelist of devices (loop*|mmcblk*[0-9]|msblk*[0-9]|mspblk*[0-9]|nvme*|sd*|sr*|vd*|xvd*|bcache*|cciss*|dasd*|ubd*), that doesn't include the NVRAM devices (umem*). A few steps later, this results in bcache_register() not being called. Trivially patching -KERNEL!="loop*|mmcblk*[0-9]|msblk*[0-9]|mspblk*[0-9]|nvme*|sd*|sr*|vd*|xvd*|bcache*|cciss*|dasd*|ubd*", GOTO="persistent_storage_end" +KERNEL!="loop*|mmcblk*[0-9]|msblk*[0-9]|mspblk*[0-9]|nvme*|sd*|sr*|vd*|xvd*|bcache*|cciss*|dasd*|ubd*|umem*", GOTO="persistent_storage_end" resolves the issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1635729/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp