Event Viewer ID153 and ntfsID40

These ID's in event viewer are described as ID153(retry notifications), ntfsID40(corruption occurred). Both these ID's are the result of Read/Write processes on the disk surface while reading the disk surface with Victoria HDD software and Chkdsk /r. Most of my external hard drives are Seagate Drives and I learned from Microsoft Learn site that the miniport driver(USB Controller under Universal Serial Bus Controllers in Device Manager) logs timeouts while communicating with the device and the read/write operation is retried. Then after several retries in reading or writing to the disk the storport driver (Storage Port Controllers in Device Manager) Resets the USB Port causing the disk to become corrupted and causing bad sectors on the disk. In talking with Microsoft about this issue I was told that the Storport Controller driver is designed by the same company that designed the external hard drive. Well Seagate therefore is responsible for causing corruption and bad sectors on disks when using software to do surface tests on those hard drives. Who knows how many Seagate External hard drives died because the Storport driver(Designed by Seagate) resetting the usb port during read/write operations. In there warranty they state that they are not responsible for data loss or corruption, however this proves that they ARE RESPONSIBLE for bad sectors and corruption on Seagate External Hard Drives because they design the drivers that communicate with their external hard drives. Sure the bad sectors and corruption can be caused by many other actions like unplugging the drive while it is busy or system crashes during power outages and other things. So if you have Seagate external hard drives NEVER try to do a surface test on your drive unless you want a corrupted disk and bad sectors. Seagate needs to re-design their Storport controllers drivers so the don't reset the USB port during read/write operations while trying to resolve timeout errors. I lost over 9TB of storage before i realized what was happening. I hope this post benefits many of seagate's customers. And I hope This post get back to Seagate so they can re-design their drivers for Storage Controllers. I will be calling Seagate customer service tomorrow to report what i have found.
Windows 10 Pro version 22H2 (OS Build 19045.3393)

In Reply to the last post
Seagate ST1000LM035-1RK172 1TB External Hard Drive
There are 968 bad sectors on the disk surface. The contents of these sectors were moved to the spare area.
The drive found 5208 bad sectors during its self test.
There are 5208 weak sectors found on the disk surface. They may be remapped any time in the later use of the disk.
38542 errors occurred during data transfer.

Seagate ST8000DM004-2CX188 8TB Backup Plus Hub
There are 24704 bad sectors on the disk surface. The contents of these sectors were moved to the spare area.
The drive found 176 bad sectors during its self test.
There are 176 weak sectors found on the disk surface. They may be remapped any time in the later use of the disk.
29729 errors occurred during data transfer.

All data provided by Hard Disk Sentinel 6.10.4c

- - - Updated - - -

I learned that possible causes of the warning ID153 in event viewer are:

Some type of throttling is configured, such as I/O limitations. Sometimes, Storage I/O Control in VMware causes this issue.

Too many drives with a high load are on the same storage controller. Therefore the drives need to be split among different controllers.

If Multipath I/O (MPIO) is configured, a single cable or a damaged NIC can cause issues with iSCSI.

I already have three internal HDD's one is a SSD the other two are HDD's but one of them is dead. I have 4 four sata connectors on my motherboard but one is used for the optical drive and two of the other 3 are used by a 3TB HDD and my SSD. I also have a M.2 PCIE connected NVME SSD that is drive C (My boot drive). The 3TB hard drive is a backup drive. And the 1TB SSD is my Software install files storage drive. So I only have one SATA port available on my motherboard. It did hold the drive that is dead now. So I need to replace that drive. Dell was going to sell me a 1TB 64MB cache 7200RPM hard drive for $49 and a slimline dvd writer for $9 to replace the drives that stopped working in my system. I did a cursory check on Newegg site looking for 7200rpm 1TB drives and they were anywhere from $55 to $89. I am considering larger drives up to 4TB to upgrade instead of a one to one replacement of the failed drive size.

I booted to command prompt and did a CHKDSK /R on the 60TB SSD and it was done in about 2HRS then it failed with unspecified error after it finished scanning the free space for bad clusters and chkdsk never paused during the scan so I assume there weren't any bad sectors detected on the free space. I scanned the drive with Victoria software but didn't finish and it found timeout errors reading data at about 63GB then the drive was reset and there were I/O errors in Victoria. there were a bunch of retries on the read operation before the drive was reset noted by event ID 153 in event viewer there were like 30 of these the I saw event ID 129 that said the device on raidport1 was reset. What was interesting to me was the timeout errors ID 153 were for drive 9 which is a SD Card Reader that drive is read only since dell replaced my motherboard troubleshooting USB issues. and not for drive7 which was the 60TB Fake SSD

- - - Updated - - -

@Megahertz I cleaned the 60TB in a command prompt boot through diskpart. then I created par recommended quick and it formatted 57TB with ntfs file system. Then I said assign letter=m and the volume10 was assigned the letter m then I did a fsutil fsinfo ntfsinfo M: command in command prompt and it showed me the file info for the volume10 which is M drive then i did the fsutil dirty query m: command and it said the M drive was dirty so then i did a chkdsk /r on the m drive and it took all of 2HRS to run but completed the free space verification and didn't pause during the scan so I can assume the free space had no bad clusters but anyway the CHKDSK ended with an unspecified error. all that was done in a command prompt boot. I read another post that said controlled folder access was the culprit in unspecified errors in windows 10 chkdsk command. so I checked and controlled folder access is turned of on my system. then the corruption troubleshooting tactics on Microsoft's learn site said the event ID153 could be caused by too many drives connected to one controller so I checked and I have 6 external usb connected hard drives. two of them are Seagate drives and they are controlled by the SCSI controller. The WD MY Book has a SES Controller. The two fake SSD's I guess use the same miniport driver called Universal Serial Bus Controller. In fact, all of the USB connected drives use the same miniport driver called the Universal Serial Bus Controller, they vary at the StorPort driver the two Seagate's use the SCSI as their Storport driver. The WD My Book uses the SES as it's StorPort driver. I guess the fake SSD's use the Intel(R) controller as their StorPort driver. so there's only up to two drives connected to the StorPort driver at any one time. however, they all use the same miniport driver named the Universal Serial Bus Controller so that could possible be the cause of the ID153 errors in event viewer. when I was scanning the surface of the fake 60TB ssd the read rate was 39.8MB/s is this comparable to and SSD read rate? is there any way to estimate the size of the drive by taking the read rate and multiplying that by the hours the software said was remaining it was only 3% done at 14HRS running