Bug 1803500

Summary: /usr/lib/udev/rules.d/60-block-scheduler.rules:5 Failed to write ATTR{...block/mmcblk0/mmcblk0p2/queue/scheduler}
Product: [Fedora] Fedora Reporter: Andrey Motoshkov <motoskov>
Component: systemdAssignee: systemd-maint
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 31CC: gigzbyte, kwizart, lnykryn, msekleta, ssahani, s, systemd-maint, zbyszek
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: systemd-245~rc2-1.fc33 systemd-243.8-1.fc31 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-04-02 09:55:38 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Andrey Motoshkov 2020-02-16 13:24:44 UTC
Description of problem:
Error during boot:
Feb 16 11:48:31 (removed) systemd-udevd[622]: mmcblk0p2: /usr/lib/udev/rules.d/60-block-scheduler.rules:5 Failed to write ATTR{/sys/devices/pci0000:00/0000:00:1c.0/0000:01:00.0/rtsx_pci_sdmmc.0/mmc_host/mmc0/mmc0:59b4/block/mmcblk0/mmcblk0p2/queue/scheduler}, ignoring: No such file or directory


Version-Release number of selected component (if applicable):
systemd-245~rc1-2.fc32.x86_64
kernel-5.6.0-0.rc1.git2.1.fc32.x86_64

How reproducible:
100%

Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Zbigniew Jędrzejewski-Szmek 2020-02-26 21:34:29 UTC
I think the rule only needs to apply to devices with DEVTYPE==disk. I pushed a commit
to dist-git, it'll go out with the next build.

Comment 2 Zbigniew Jędrzejewski-Szmek 2020-03-03 13:21:24 UTC
Fixed in rawhide now.

Comment 3 Dmitri L 2020-03-06 21:17:13 UTC
How can it be fixed on F31?

Comment 4 Zbigniew Jędrzejewski-Szmek 2020-03-13 11:26:41 UTC
*** Bug 1813219 has been marked as a duplicate of this bug. ***

Comment 5 Nicolas Chauvet (kwizart) 2020-03-13 13:06:37 UTC
Seems like the rawhide fix when applied on f31 works...
Please consider a backport for all affected branches.

Comment 6 Fedora Update System 2020-03-18 21:18:39 UTC
FEDORA-2020-645de57f2e has been submitted as an update to Fedora 32. https://bodhi.fedoraproject.org/updates/FEDORA-2020-645de57f2e

Comment 7 Fedora Update System 2020-03-19 02:26:28 UTC
systemd-245.2-1.fc32 has been pushed to the Fedora 32 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-645de57f2e

Comment 8 Fedora Update System 2020-03-23 20:24:51 UTC
FEDORA-2020-645de57f2e has been pushed to the Fedora 32 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 9 Nicolas Chauvet (kwizart) 2020-03-26 09:32:49 UTC
f31 ?
Thx in advance.

Comment 10 Fedora Update System 2020-03-27 19:12:18 UTC
FEDORA-2020-287a343a35 has been pushed to the Fedora 31 testing repository.
In short time you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-287a343a35`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-287a343a35

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 11 Fedora Update System 2020-04-02 09:55:38 UTC
FEDORA-2020-287a343a35 has been pushed to the Fedora 31 stable repository.
If problem still persists, please make note of it in this bug report.