Bug 1708958 - mdadm logs "systemd-udevd[1133]: Process '/sbin/mdadm -I /dev/sdg2 --export /dev/sdg2 --offroot ${DEVLINKS}' failed with exit code 1."
Summary: mdadm logs "systemd-udevd[1133]: Process '/sbin/mdadm -I /dev/sdg2 --export /...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: mdadm
Version: 30
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: XiaoNi
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-05-12 00:03 UTC by Philippe Troin
Modified: 2020-02-25 14:38 UTC (History)
7 users (show)

Fixed In Version: mdadm-4.1-1.fc30
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-02-25 14:38:44 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Philippe Troin 2019-05-12 00:03:19 UTC
Description of problem:
mdadm logs "systemd-udevd[1133]: Process '/sbin/mdadm -I /dev/sdg2 --export /dev/sdg2 --offroot ${DEVLINKS}' failed with exit code 1." every time the system boots.

Version-Release number of selected component (if applicable):
mdadm-4.1-rc2.0.3.fc30.x86_64

How reproducible:
Always

Steps to Reproduce:
1.Reboot on a system with MD RAID arrays.
2.journalctl -b | grep 'mdadm.*fail'

Actual results:
systemd-udevd[1103]: Process '/sbin/mdadm -I /dev/sdj2 --export /dev/sdj2 --offroot ${DEVLINKS}' failed with exit code 1.
I get one line of this error per RAID array member.

Expected results:
No errors should be logged.

Additional info:
${DEVLINKS} is not a udev variable (anymore?), use $env{DEVLINKS} instead in SOURCES/mdadm.rules.

Comment 1 Philippe Troin 2019-05-12 00:07:42 UTC
After replacing ${DEVLINKS} with $env{DEVLINKS}, I still get an error, now with the correctly expanded variable:
systemd-udevd[770]: Process '/sbin/mdadm -I /dev/sda2 --export /dev/sda2 --offroot /dev/disk/by-partuuid/f2d548de-02 /dev/disk/by-id/ata-INTEL_SSDSC2BB480G4_PNXXXX-part2 /dev/disk/by-path/pci-0000:00:1f.2-ata-1-part2 /dev/disk/by-id/wwn-XXXXXX-part2' failed with exit code 1.

Comment 2 Andrew 2019-05-16 00:57:07 UTC
I'm seeing this same exact issue on Fedora 30 with mdadm-4.1-rc2.0.3.fc30.x86_64.

If I fix the ${DEVLINKS} --> $env{DEVLINKS}, it now correctly expands the variable, but mdadm still barfs on it.

I wonder if the mdadm syntax in /usr/lib/udev/rules.d/65-md-incremental.rules is wrong or something?

Before fixing $env:

May 15 09:50:48 shrew systemd-udevd[723]: Process '/sbin/mdadm -I /dev/sda1 --export /dev/sda1 --offroot ${DEVLINKS}' failed with exit code 1.

After changing $env:

May 15 17:12:00 shrew systemd-udevd[704]: Process '/sbin/mdadm -I /dev/sda1 --export /dev/sda1 --offroot /dev/disk/by-id/ata-Samsung_SSD_850_EVO_250GB_S21NNSAFC30769F-part1 /dev/disk/by-id/wwn-0x5002538da000da20-part1 /dev/disk/by-path/pci-0000:00:11.0-ata-1-part1 /dev/disk/by-partuuid/56b51657-c35c-4b0c-a850-1aaa39bbc9cb' failed with exit code 1.

Comment 3 Ben Cotton 2019-05-28 19:03:17 UTC
Fedora 28 changed to end-of-life (EOL) status on 2019-05-28. Fedora 28 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

Comment 4 Philippe Troin 2019-05-31 16:01:32 UTC
This was incorrectly filed under fedora 28, it should have been fedora 30.
Corrected release and reopening.

Comment 5 Kim Bisgaard 2019-12-28 09:47:10 UTC
I see this with mdadm-4.1-rc2.0.5.fc31.1.x86_64

I see this in the log:
systemd-udevd[688]: /usr/lib/udev/rules.d/65-md-incremental.rules:28 Invalid value "/sbin/mdadm -I $env{DEVNAME} --export $devnode --offroot ${DEVLINKS}" for IMPORT (char 58: invalid substitution type), ignoring, but please fix it.


After changing ${DEVLINKS} --> $env{DEVLINKS}, it just works without errors;-)

Comment 6 Fedora Update System 2020-02-09 09:15:45 UTC
FEDORA-2020-b7b2270753 has been submitted as an update to Fedora 30. https://bodhi.fedoraproject.org/updates/FEDORA-2020-b7b2270753

Comment 7 Fedora Update System 2020-02-10 03:07:23 UTC
mdadm-4.1-1.fc30 has been pushed to the Fedora 30 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-b7b2270753

Comment 8 Fedora Update System 2020-02-25 14:38:44 UTC
mdadm-4.1-1.fc30 has been pushed to the Fedora 30 stable repository. If problems still persist, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.