Getting tons of Warning 153 on a Server2012 machine, the disk it references is a USb backup drive. Can anyone tell me what is going on?

Question

Log Name: System
Source: disk
Date: 6/14/2021 10:47:05 AM
Event ID: 153
Task Category: None
Level: Warning
Keywords: Classic
User: N/A
Computer: SERVER2012
Description:
The IO operation at logical block address 600848 for Disk 1 was retried.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="disk" />
<EventID Qualifiers="32772">153</EventID>
<Level>3</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2021-06-14T14:47:05.984062500Z" />
<EventRecordID>76114</EventRecordID>
<Channel>System</Channel>
<Computer>SERVER2012</Computer>
<Security />
</System>
<EventData>
<Data>\Device\Harddisk1\DR1</Data>
<Data>600848</Data>
<Data>1</Data>
<Binary>0F01160003003E00000000009900048000000000000000000000000000000000000000000000000000020488700003000000000A00000000110000000000</Binary>
</EventData>
</Event>

Answer 1

Hi,
Event ID 153 is an error associated with the storage subsystem. It is logged when the storport miniport driver times out a request.

The details section of the event the log record will present what error caused the retry and whether the request was a read or write.

Try to modify the registry "Timeout Value" in the link below:
https://appuals.com/fix-the-io-operation-at-logical-block-address-for-disk-was-retried/
Hope this helps and please help to accept as Answer if the response is useful.
Best Regards,
Carl

Answer 2

Please test the drive:

https://www.lifewire.com/free-hard-drive-testing-programs-2626183

a) SMART
b) surface / error
c) long generic
d) chkdsk
e) communication

https://learn.microsoft.com/en-us/archive/blogs/ntdebugging/interpreting-event-153-errors

.
.
.
.
.

Please remember to vote and to mark the replies as answers if they help.

On the bottom of each post there is:

Propose as answer = answered the question

On the left side of each post: Vote = a helpful post
.
.
.
.
.