[Pkg-utopia-maintainers] Bug#1071488: udisks2: Syslog filled with "Error probing device: Error sending ATA command IDENTIFY DEVICE to '/dev/sdx': Unexpected sense data returned:"

[Scott Ward]

Package: udisks2
Version: 2.9.4-4
Severity: normal

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
   * What exactly did you do (or not do) that was effective (or
     ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?

*** End of the template - remove these template lines ***


-- System Information:
Debian Release: 12.5
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 6.1.0-21-amd64 (SMP w/2 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages udisks2 depends on:
ii  dbus                   1.14.10-1~deb12u1
ii  libacl1                2.3.1-3
ii  libatasmart4           0.19-5
ii  libblockdev-fs2        2.28-2
ii  libblockdev-loop2      2.28-2
ii  libblockdev-part2      2.28-2
ii  libblockdev-swap2      2.28-2
ii  libblockdev-utils2     2.28-2
ii  libblockdev2           2.28-2
ii  libc6                  2.36-9+deb12u7
ii  libglib2.0-0           2.74.6-2+deb12u2
ii  libgudev-1.0-0         237-2
ii  libmount1              2.38.1-5+deb12u1
ii  libpolkit-agent-1-0    122-3
ii  libpolkit-gobject-1-0  122-3
ii  libsystemd0            252.22-1~deb12u1
ii  libudisks2-0           2.9.4-4
ii  libuuid1               2.38.1-5+deb12u1
ii  parted                 3.5-3
ii  udev                   252.22-1~deb12u1

Versions of packages udisks2 recommends:
ii  dosfstools           4.2-1
ii  e2fsprogs            1.47.0-2
ii  eject                2.38.1-5+deb12u1
ii  exfatprogs           1.2.0-1+deb12u1
ii  libblockdev-crypto2  2.28-2
ii  libpam-systemd       252.22-1~deb12u1
ii  ntfs-3g              1:2022.10.3-1+b1
ii  polkitd              122-3

Versions of packages udisks2 suggests:
pn  btrfs-progs          <none>
pn  f2fs-tools           <none>
pn  libblockdev-mdraid2  <none>
ii  mdadm                4.2-5
ii  nilfs-tools          2.2.9-1
pn  reiserfsprogs        <none>
pn  udftools             <none>
pn  udisks2-bcache       <none>
pn  udisks2-btrfs        <none>
pn  udisks2-lvm2         <none>
pn  udisks2-zram         <none>
pn  xfsprogs             <none>

-- no debconf information

This started happening after I upgraded from Debian 11 to Debian 12.  This copy of Debian is running as a VM under VMWare ESXi and I have a number of USB hard drives connected to it.   This message is coming from two of them, one a Western Digital and one an older Buffalo.  
I've seen this bug reported in other venues (i.e. other distributions) but it never seems to get fixed, although in one report it looks like a maintainer said they were simply going
to supress the message, which would be good.  The message appears at about 6 minute intervals and is several individual lines which makes filtering it out with grep difficult. 
Here is an example of the message:

May 20 01:00:50 lhNAS udisksd[65284]: Error probing device: Error sending ATA command IDENTIFY DEVICE to '/dev/sdm': Unexpected sense data returned:
                                      0000: f0 00 01 00  50 00 01 0a  80 00 00 00  00 1d 00 00    ....P...........
                                      0010: 00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00    ................
                                       (g-io-error-quark, 0)

Reports in other venues say the issue is most common with Western Digital drives.   I've tried changing the loglevel in /etc/udisks2/udisks2.conf but that doesn't stop the 
messages even when set to the "Alert" level.   
 
Functionality isn't affected, but if you have a number of hard drives causing this message to be put out every 6 minutes it gets very difficult to find anything else in the log,
especially since you have to use multiple filters to get rid of them all.   This message should be eliminated or set to notice level and the loglevel directive in the
config file then needs to be fixed to actaully affect messages going into the syslog.