Comment 79 for bug 153768

So I have an idea I'm working on to finally fix this. Udisks could be modified to look for a udev attribute that indicates the drive is connected via esata, and treat the drive correctly. This attribute could be imported from the parent ata port, if it is known that the port is an esata port. The udev hwdb could be configured to know that a specific port on specific known motherboards is esata.

I'm still trying to sort out how to set up such a matching rule in the udev hdwb though since there doesn't seem to be a way to match on multiple requirements joined by AND rather than OR.