Overall then, it appears that the "aberrant 512B" got caught up in the physical volume I/O operation activity that ensued as part of the services startup activities performed when the system was started.
So, would it be reasonable to conclude that this storage device sometimes has very slow 512B IO when other IO is going on in parallel?
Bookmarks