Thought I'd share an odd experience I had, in hopes that it helps people.
I use an offbrand tiny PC; an acepc T11 as a backup destination. I was using a seagate 5tb 2.5" external drive, and when it died I replaced with a 3.84tb MMicron Pro 5400, moving to the internal 2.5" bay. This led to a bunch of issues with data corruption. it turns out the internal bay is really also USB/Sata, using what I believe is a Genesys bridge. If the drive was pulled and connected to a different PC, either via SATA or USB/SAta, it would show a UEFI proected partition.
That was the real clue-it turns out the Micron is a 512 byte sector device, but the Genesys bridge was translating to 4096 byte sectors due to the >2tb size. This evidently is buggy, and was leading to the corruption. When I moved to a different Ugreen adapter, the Micron was passed through with 512 byte sectors, and no more corruption.
Here is one article that pointed me in the right direction; finally
I use an offbrand tiny PC; an acepc T11 as a backup destination. I was using a seagate 5tb 2.5" external drive, and when it died I replaced with a 3.84tb MMicron Pro 5400, moving to the internal 2.5" bay. This led to a bunch of issues with data corruption. it turns out the internal bay is really also USB/Sata, using what I believe is a Genesys bridge. If the drive was pulled and connected to a different PC, either via SATA or USB/SAta, it would show a UEFI proected partition.
That was the real clue-it turns out the Micron is a 512 byte sector device, but the Genesys bridge was translating to 4096 byte sectors due to the >2tb size. This evidently is buggy, and was leading to the corruption. When I moved to a different Ugreen adapter, the Micron was passed through with 512 byte sectors, and no more corruption.
Here is one article that pointed me in the right direction; finally
USB adapters silently change the sector size
Why does my drive work when connected directly to a SATA port, but does not work with a USB adapter?
www.klennet.com