[Bug 2092222] Re: ata: libata-scsi: Honor the D_SENSE bit for CK_COND=1 and no error

If you want to spend cycles on this you could try the mainline kernels
to see if it's fixed in a later version:

https://kernel.ubuntu.com/mainline/v6.12/amd64/
https://kernel.ubuntu.com/mainline/v6.13-rc1/amd64/

--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2092222

Title:
ata: libata-scsi: Honor the D_SENSE bit for CK_COND=1 and no error

Status in linux package in Ubuntu:
Incomplete

Bug description:
Hi,

I'm running Ubuntu 24.04.1 LTS (GNU/Linux 6.8.0-51-generic x86_64) as
a guest system in Proxmox VE 8.3.2. I have connected a WD SATA-HDD via
passthrough directly to the Ubuntu guest system. It is mountable and
works flawlessly.

However, I want it to spin down to "standby" state if it is not in
use. So, I ran the "hdparm" command to check the current power mode
status. The status of the SATA-HDD had been "idle" or "active" at this
point:

root@xyz:~# hdparm -C /dev/sdb

/dev/sdb:
SG_IO: bad/missing sense data, sb: 70 00 05 00 00 00 00 0a 00 00 00 00 20 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 drive state is: standby

As you can see, "hdparm" threw an error and returned the wrong power
mode state "standby". I doublechecked by touching the SATA-HDD. It was
spinning and the head was moving.

After, I did some googling and found a post in the Majaro (sorry!) forum exactly matching this issue:
https://forum.manjaro.org/t/ata-libata-scsi-sense-data-errors-breaking-hdparm-with-wd-drives/166634/10

The post also points out the solution - a kernel fix as part of the linux6.10.6-1 point release:
https://git.kernel.org/pub/scm/linux/kernel/git/libata/linux.git/commit/?id=fa0db8e5

Now my request - Could you please add this fix also to one of the next point releases of Ubuntu 24.04.1 LTS's "Linux 6.8.0-5x" kernel?
I would really like to avoid introducing a "custom" kernel into my 100%-standard Ubuntu LTS system.

Thanks in advance!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2092222/+subscriptions