Red Hat Bugzilla – Bug 1400056
udisksd: Error creating watch for file /sys/devices/virtual/block/md126/md/sync_action
Last modified: 2018-06-12 22:44:09 EDT
Description of problem: udisksd: Error creating watch for file /sys/devices/virtual/block/md126/md/sync_action: No such file or directory (g-file-error-quark, 4) udisksd: Error creating watch for file /sys/devices/virtual/block/md126/md/degraded: No such file or directory (g-file-error-quark, 4) udisksd: Error creating watch for file /sys/devices/virtual/block/md127/md/sync_action: No such file or directory (g-file-error-quark, 4) udisksd: Error creating watch for file /sys/devices/virtual/block/md127/md/degraded: No such file or directory (g-file-error-quark, 4) seen during boot. Version-Release number of selected component (if applicable): udisks2-2.1.2-6.el7.x86_64 How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Raid 0 doesn't provide any redundancy, so the kernel won't expose the corresponding redundancy sysfs attributes like sync_action and degraded. So udisks should not try to add watch for these files. Additional info: These errors are seen on raid1 too. #### Environment Red Hat Enterprise Linux Server release 7.2 (Maipo) #### Similar Bug Bugs 1348161 and 985638 #### Diagnostic steps This was the error messages: ------------------------------- Nov 1 06:16:01 quanta dbus[2326]: [system] Activating via systemd: service name='org.freedesktop.UDisks2' unit='udisks2.service' Nov 1 06:16:01 quanta dbus-daemon: dbus[2326]: [system] Activating via systemd: service name='org.freedesktop.UDisks2' unit='udisks2.service' Nov 1 06:16:01 quanta systemd: Starting Disk Manager... Nov 1 06:16:01 quanta udisksd[30237]: udisks daemon version 2.1.2 starting Nov 1 06:16:01 quanta udisksd[30237]: Error creating watch for file /sys/devices/virtual/block/md126/md/sync_action: No such file or directory (g-file-error-quark, 4) Nov 1 06:16:01 quanta udisksd[30237]: Error creating watch for file /sys/devices/virtual/block/md126/md/degraded: No such file or directory (g-file-error-quark, 4) Nov 1 06:16:01 quanta udisksd[30237]: Error creating watch for file /sys/devices/virtual/block/md127/md/sync_action: No such file or directory (g-file-error-quark, 4) Nov 1 06:16:01 quanta udisksd[30237]: Error creating watch for file /sys/devices/virtual/block/md127/md/degraded: No such file or directory (g-file-error-quark, 4) Nov 1 06:16:01 quanta dbus[2326]: [system] Successfully activated service 'org.freedesktop.UDisks2' Nov 1 06:16:01 quanta systemd: Started Disk Manager. ------------------------------- Customer followed the below steps to build RSTe RAID1: 1. Select SATA controller to be RAID mode 2. "Save and reboot" for new setting 3. Boot into BIOS setup again 4. Enter Advanced/Intel RSTe SAT controller 5. Select two SSD and build RAID1 6. "Save and reboot" for new setting 7. Install RHEL 7.2 OS The below command outputs: ------------------------------- # mdadm --detail-platform # mdadm -D /dev/md126 # mdadm -D /dev/md127 ------------------------------- $ cat 40-1125.zip/1125/detail_platform.txt Platform : Intel(R) Rapid Storage Technology enterprise Version : 4.5.0.1012 RAID Levels : raid0 raid1 raid10 raid5 Chunk Sizes : 4k 8k 16k 32k 64k 128k 2TB volumes : supported 2TB disks : supported Max Disks : 8 Max Volumes : 2 per array, 4 per controller I/O Controller : /sys/devices/pci0000:00/0000:00:11.4 (SATA) Port0 : /dev/sda (S2C5NYAG600075) Port1 : /dev/sdb (S2C5NYAG500363) Port2 : - no device attached - Port3 : - no device attached - $ cat 40-1125.zip/1125/md126.txt /dev/md126: Container : /dev/md/imsm0, member 0 Raid Level : raid1 Array Size : 222715904 (212.40 GiB 228.06 GB) Used Dev Size : 222716036 (212.40 GiB 228.06 GB) Raid Devices : 2 Total Devices : 2 State : clean Active Devices : 2 Working Devices : 2 Failed Devices : 0 Spare Devices : 0 UUID : 110a0aed:4509a9cb:70773db3:fff0cca8 Number Major Minor RaidDevice State 1 8 0 0 active sync /dev/sda 0 8 16 1 active sync /dev/sdb $ cat 40-1125.zip/1125/md127.txt /dev/md127: Version : imsm Raid Level : container Total Devices : 2 Working Devices : 2 UUID : 0ea37c80:2660cd53:f137aeac:c6e67cda Member Arrays : /dev/md/Volume0 Number Major Minor RaidDevice 0 8 0 - /dev/sda 1 8 16 - /dev/sdb ------------------------------- # cat /usr/lib/systemd/system/udisks2.service > /tmp/udisks2service.txt # cat udisks2service.txt [Unit] Description=Disk Manager Documentation=man:udisks(8) [Service] Type=dbus BusName=org.freedesktop.UDisks2 ExecStart=/usr/lib/udisks2/udisksd --no-debug
After a talk with vtrefny I am able to reproduce the bug using SW RAID 0 with udisks2-2.1.2-6.el7.x86_64.rpm, but I am not able to reproduce the bug using SW RAID 1. See my reproducer in TCMS. The problem (error messages) does not occur with udisks2-2.7.3-3.el7.x86_64, so I could confirm the bug is fixed. Can customer verify the fix on the hardware RAID?
Tested again using udisks2-2.7.3-4.el7 on all archs. Problem not reproduced - seems to be fixed. Can customer verify the fix on the hardware RAID?
I've asked the customer for his results after testing with udisks2-2.7.3-4.el7 thanks, nikhil.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2018:0868