Process '/lib/udev/hdparm' failed with exit code 5

Please add some debugging output to /lib/udev/hdparm with

  sudo sed -i '2 s_^_set -x; exec 2>/tmp/hdparm.txt_' /lib/udev/hdparm

then re-run the event with

   sudo udevadm trigger --action=add /sys/block/sda --verbose

then attach /tmp/hdparm.txt here. Thanks!

here is the output:

Hm, that script invocation succeeded. I figure this gets called by more than one device then. Can you please edit /lib/udev/hdparm so that the second line becomes

  set -x; exec 2>>/tmp/hdparm.txt

i. e. replace the single '>' with a double '>>', then reboot, make sure the error message is still there, and attach /tmp/hdparm.txt again? Thanks!

have applied the #4 change above, saved & rebooted. But the double '>>' seems not recognized as such.

and the code error is now: Process '/lib/udev/hdparm' failed with exit code 127.

Something went wrong, hdparm.txt now just shows "/lib/udev/hdparm: 2: exec: -x: not found". Seems you accidentally dropped the "set" in front of the -x? The second line must be

  set -x; exec 2>>/tmp/hdparm.txt

An other tweak:

#!/bin/sh
set -x; exec 2>>/tmp/hdparm.txtset -x; exec 2>>/tmp/hdparm.txtset -x; exec 2>>/tmp/hdparm.txt
set -e
....

the first change was as #4

reapplied the #2 debugging:

 sudo sed -i '2 s_^_set -x; exec 2>/tmp/hdparm.txt_' /lib/udev/hdparm
[sudo] password for oem:

oem@u64:~$ sudo udevadm trigger --action=add /sys/block/sda --verbose

/sys/devices/pci0000:00/0000:00:1f.1/ata1/host0/target0:0:0/0:0:0:0/block/sda
/sys/devices/pci0000:00/0000:00:1f.1/ata1/host0/target0:0:0/0:0:0:0/block/sda/sda1
/sys/devices/pci0000:00/0000:00:1f.1/ata1/host0/target0:0:0/0:0:0:0/block/sda/sda3
/sys/devices/pci0000:00/0000:00:1f.1/ata1/host0/target0:0:0/0:0:0:0/block/sda/sda4
/sys/devices/pci0000:00/0000:00:1f.1/ata1/host0/target0:0:0/0:0:0:0/block/sda/sda5
/sys/devices/pci0000:00/0000:00:1f.1/ata1/host0/target0:0:0/0:0:0:0/block/sda/sda6

Question: do i also need to tweak the debugging script the same way ?

--> sudo sed -i '2 s_^_set -x; exec 2>>/tmp/hdparm.txt_' /lib/udev/hdparm

Please forget about the sed, that only works exactly once ever. For further tweaks you actually need to edit the file as root. Please edit it to drop the duplication -- as I said, the second line must be *excatly* like in comment 7.

oh, i get it at last !!! set now as:

#!/bin/sh
set -x; exec 2>>/tmp/hdparm.txt
set -e
....

that seems ok into hdparm.txt; will reboot and check journalctl before commenting on .

But still get the initial error:

systemd-udevd[496]: Process '/lib/udev/hdparm' failed with exit code 5.

So if comment 11 is the latest hdparm, this still only has one invocation which succeeds. Maybe the first one is from much earlier. Can you please edit it again to output to /run/hdparm.txt instead of /tmp/hdparm.txt? That should always be available during early boot, while /tmp/ might be a separate mount point in your fstab.

This is from an other xenial install: fresh mini.iso, only genuine packages; with the same error logged (#12)

Note that /lib/udev/hdparm had not the "set -x; ...." line; so adding it.

#!/bin/sh
set -x; exec 2>>/run/hdparm.txt #added due to bug 1568474 #13
set -e

Will reboot to know if that change resolve the issue.

Feedback
Get the same error: systemd-udevd[398]: Process '/lib/udev/hdparm' failed with exit code 5.

 cat /etc/fstab
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
# / was on /dev/sdc1 during installation
UUID=dec5c521-a4b3-44f9-af5c-a23fb12227ff / ext4 errors=remount-ro 0 1
# /home was on /dev/sdc3 during installation
UUID=5d8d1ee1-f5af-40a1-a45d-dbc570808523 /home ext3 defaults 0 2
# swap was on /dev/sdc2 during installation
UUID=0a9ca7f0-6eeb-4b21-b70f-670fa600de16 none swap sw 0 0

Note that all the joined hdparm.txt are always the latest generated (the previous are erased, and the timestamp control is made before joining them)
( answer to #13 comment)

Well yes, the set -x stuff isn't meant to fix the issue, it's meant to add some debugging what actually fails in /lib/udev/hdparm . But so far we didn't yet manage to see it failing.

An other affected user have found the reason of that error: some hardware not supporting APM policy

See comment #3 of https://bugs.launchpad.net/ubuntu/+source/hdparm/+bug/1470014

Feedback:
booted with 'noapm', but the error is still logged.

Is it a duplicate of Bug #1470014?

@Amr

it is very close, as i first report it on a wily install a while back. Then the issue has not been logged on wily. And now reappear on xenial.
I wonder if it is related to ubuntu's kernels config as i've not found that error reported accross all distro.

Could it be a kernel issue ?
I've re-checked log with kernel 4.4.0-20, and this is still logged on both a fresh install & a wily to xenial dist-upgrade

Feedback with yakketi

This error is no logged now.
As yakketi is quite the same as xenial: same 4.4.0.x kernel and xenial archives copied into yakketi ones.

The only changes i can think about are: some packages rebuilt with new libpng/libicu mainly as of yesterday changes.

[Expired for hdparm (Ubuntu) because there has been no activity for 60 days.]