Drivepool warning in event log after Veeam runs

[Thronic]

Had about 10 of these happening last night in my event log. Disk 11 is Drivepool. This followed directly after Veeam (free agent for Windows) started, so maybe related to that. I'll update and keep an eye on it.

 

Quote

Log name:      System
source:         Disk
Event-ID:  153
Level:          Warning
I/U-operation at logical block address 0x11 for disk 11 (PDO-name: \Device\00000041) was retried.
Event-XML-file:
<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="2018-09-20T02:00:44.131241200Z" />
    <EventRecordID>7597</EventRecordID>
    <Security />
  </System>
  <EventData>
    <Data>\Device\Harddisk11\DR11</Data>
    <Data>0x11</Data>
    <Data>11</Data>
    <Data>\Device\00000041</Data>
    <Binary>0F01040004002C0000000000990004800000000000000000000000000000000000000000000000000000048A</Binary>
  </EventData>
</Event>

 

[Christopher (Drashna)]

This is harmless. 

"logical block  address" is the sector location on a disk. The pool has no actual sectors, so it generates an error. 

[zeroibis]

Cool, just saw this. It appears that writes that use sector by sector write verification like to trigger this. For example I only see this error generated when I am using acronis to copy to a drivepool volume. (even if done via network). Would be neat if drivepool was somehow able to automatically suppress this error message but it is something that I suspect is tied heavily in the os.

[Christopher (Drashna)]

Yup, exactly. 

And it's not really something that DrivePool does/handles, it's something the OS itself does.   So, there isn't much that we could do. Especially in a safe manner.