The IO operation at logical block address 0x0 for disk 2 (pdo name: \device\00000038) was retried.
The file system at logical block address 0x0 for disk 2 pdo name device00000038 was retried.
Some of you might be wondering, “How do I know that the IO operation at logical block address 0x0 for disk 2 (pdo name: \device\00000038) was retried?” Well, it just so happens that the IO operation at logical block address 0x0 for disk 2 pdo name device00000038 was retried. There are two reasons for this.
The first reason is because the disk is actually a SATA drive, and in theory, the drive should have been able to detect the IO operation and simply skip that one. If it had, the other IO operations should have been successful.
On a disk that’s not a SATA drive, it’s likely that it’s the SATA drive that’s being detected. If it’s not, then the IO operation would be complete. The IO operations would be complete, so if the IO operation actually detected the drive, the IO operation would be complete.
The disk is not a SATA drive. As a USB drive, it’s a different matter and if its defective or not, then it’s not a SATA drive. I’m not saying that you can’t have a SATA drive.
It’s possible it’s the problem with the drive, though. A drive that is not a standard SATA drive probably contains something that is not compatible with the standard SATA spec.
What I’m saying is I dont think we need to run an IO operation with a drive that is not a SATA drive, because that would be a pretty bad idea anyway, and there might be an error condition involved. I think we should run an IO operation with a drive that is a SATA drive. We can then see if we have a problem with the SATA drives.
But it might not be a problem at all.
SATA drives are very reliable, but there are many cases where the drive is not compatible. Also, there are many situations where a drive that is not compatible with a SATA drive is also not compatible with the standard SATA spec. For example, SATA drives that are not NAND flash drives are not compatible with SATA drives.