hpsa Abort request on C0:B0:T0:L0 FAILED. Aborted command has not completed after 30 seconds.

When you’re running Linux on a HP Proliant Server with a SmartArray Controller attached and have errors in Syslog like

hpsa 0000:0e:00.0: Abort request on C0:B0:T0:L0
hpsa 0000:0e:00.0: ABORT REQUEST on C0:B0:T0:L0 Tag:0x00000000:00000010 Command:0x28 SN:0x88896  REQUEST SUCCEEDED.
hpsa 0000:0e:00.0: ABORT REQUEST on C0:B0:T0:L0 Tag:0x00000000:00000010 Command:0x28 SN:0x88896  FAILED. Aborted command has not completed after 30 seconds.
hpsa 0000:0e:00.0: resetting device 0:0:0:0
hpsa 0000:0e:00.0: device is ready.

and disk IO hangs but the SmartArray Controller reports no problems at all

Smart Array P410i in Slot 0 (Embedded)

   array A (SAS, Unused Space: 0  MB)

      logicaldrive 1 (558.7 GB, RAID 1+0, OK)

      physicaldrive 2I:1:1 (port 2I:box 1:bay 1, SAS, 300 GB, OK)
      physicaldrive 2I:1:2 (port 2I:box 1:bay 2, SAS, 300 GB, OK)
      physicaldrive 2I:1:3 (port 2I:box 1:bay 3, SAS, 300 GB, OK)
      physicaldrive 2I:1:4 (port 2I:box 1:bay 4, SAS, 300 GB, OK)

then chances are high that you have one drive that is going to die very soon.

After some hours and some more IO stalls and kernel logs like above the disk status will hopefully change to this:

Smart Array P410i in Slot 0 (Embedded)

   array A (SAS, Unused Space: 0  MB)

      logicaldrive 1 (558.7 GB, RAID 1+0, OK)

      physicaldrive 2I:1:1 (port 2I:box 1:bay 1, SAS, 300 GB, OK)
      physicaldrive 2I:1:2 (port 2I:box 1:bay 2, SAS, 300 GB, Predictive Failure)
      physicaldrive 2I:1:3 (port 2I:box 1:bay 3, SAS, 300 GB, OK)
      physicaldrive 2I:1:4 (port 2I:box 1:bay 4, SAS, 300 GB, OK)

Now you know which disk is causing the problem and can replace it.