I replaced my mb and decided to update to win 11 a few days ago. My odrive was on a secondary HHD and contained a ton of image files and was formerly synced to Amazon Cloud Drive but it’d been a few years since it connected. I mostly backed up just a few folders from the root odrive folder.
When I logged in after upgrade, the odrive folder was empty. I found one item in the trash: “Amazon cloud drive” which was the main directory for all my sub folders in odrive. I restored it but had zero bytes of data. I’ve since ran DMDE and Recuva recovery software and none have been able to find any files on the the drive. nothing remotely matches the 100000 files or 2000 sub folders I had in the folder.
I’m sorry to hear this happened. In general odrive is very delete adverse, to the point that it is annoying to some folks.
Can you send a diagnostic from the odrive tray menu and let me know when it has been sent? I can investigate and see what odrive saw from its point of view.
The diagnostics show that odrive hasn’t done anything since Amazon Drive shut off its API (about 2.5 years ago), as you said. I can see odrive recently detecting a “local delete”, meaning that it sees that an item should exist and has tracking values, but it is no longer found (the Amazon Drive folder). Unfortunately the version you were running was very old (from 2022) and it didn’t have all of the logging that our more recent versions have, so I can’t tell exactly when that folder first went missing
The only thing in the odrive code that would delete that folder is if the Amazon Drive link was removed from your odrive account. In that case, though, odrive would see it as a “remote delete” rather than a “local delete”. It would also have put it in the Windows Recycle Bin and not in the odrive trash. Since it is seeing it as a local delete it means that odrive expects it to be there and hasn’t take any delete actions, so something else must’ve acted upon it as some point.
What day was it when you replaced your motherboard and updated to Windows 11?
Unfortunately I can’t find any trail for where the folder went or exactly when it disappeared (presumably sometime on Monday).
It is also very strange that there is no trace of it using file recovery tools. There should be at least some sign of these delete items on the drive, unless there is something wrong with the disk, disk controller, or there has been some sort of MFT corruption.
A few ideas of what to do next:
Drive health: Download a utility like CrystalDiskInfo to check the S.M.A.R.T. status. Look for any warnings, errors or other signs of a failing disk, like “Reallocated Sectors”.
Hidden/unexpected folders: In Windows File Explorer, enable “Show hidden files” and uncheck “Hide protected operating system files.” Check the root of the drive for a folder named found.000, or similar. This type of folder can be created if Windows attempted a repair during the upgrade.
Run a “deep” scan: I haven’t used these utilities in a long time, but I believe there are options in Recuva/DMDE to do deeper/raw scans, which can find things that the standard recovery settings can’t.
Check BIOS settings: It sounds like this happened after the Windows update and not when the motherboard was updated, but it may be worth checking if your new motherboard set the drive controller to an unexpected setting causing the OS to somehow misinterpret the file table. Unlikely, but worth a shot.