The IO operation at logical block address 0x5d7a68 for Disk 0 (PDO name: \Device\00000032) was retried.
You can determine what command failed and the basic reason why from the Details tab on the event record. This applies to Windows 7 and newer. It may apply to Windows Vista and Windows XP as well. I did not have resources to verify.
At the time of writing, Windows 10 is current and the information below if from Windows 10 with the November 2015 update..
To get to the event viewer, right click on My Computer, Computer, This Computer, or This PC and select Manage. There are other ways of getting to the same location. I find this method easiest.
Under Computer Management, expand Windows Logs and select System.
In the example above, the SCSI command status is 00 indicating the command did finally complete although it took at least one retry and thus the reason the event was logged. The SRB status of 04 indicates the request completed with any other error than standard errors, and SCSI command code of 8A is a WRITE(16).
- SCSI command status codes can be found on Wikipedia:
and the T10 documentation:
- SRB status codes can be found on MSDN:
- SCSI Operation Codes are found in the T10 documentation:
What this means is a write of 16 bytes was sent to the drive and an OS provided driver timed out the command at least once but it finally completed with an error that is not known. The 04 status may indicate it could not determine if the command really completed even though the SCSI command status is good.
In this case, I was getting a lot of them on a Western Digital Green drive where Steam was installed (to isolate my games from the rest of the system storage). Many IO operation errors occurred at various logical blocks on Disk 0. To determine which drive, click on Disk Management in the Manage window and find the disk noted in the Event ID 153. In this case it was my Steam drive.
I have a good image backup so I restored to another drive and verified Steam works properly there. Every download in Steam or Steam disk write generates an event.
I formatted the drive and did a complete surface scan. No errors found but any programs or applications attempting writes trigger the event. New firmware is not available for the drive and I have another like it running the same version of drivers. Time to replace the drive.