roirraWedorehT

Cross-quoting my workaround that definitely works:

Thanks for the details, and the work necessary to gather them and post about it. I'm working around the issue currently by having a Hyper-V virtual PC set only for using Google Drive Backup and Sync, or whatever they happen to be calling it at this moment. I gave the virtual PC a secondary virtual hard drive - I made it a 10 GB dynamically expanding drive, so it'll only take up as much space as it needs to, but is open to expansion for a good long while, and have Drive sync to a folder on that VHDX. Then I have it shared over the network, and I assigned it the letter G: on my host desktop. I know there are plenty of people out there who don't have experience with virtual PCs, but Windows' built-in Hyper-V makes it so easy and fast. I would obviously prefer to use it locally, but this will work for now. The sync app hasn't crashed at all, and everything is synced. Edit: Now that I think about it, creating a .VHDX locally on the host desktop through Disk Management, mounting it (as drive G: or whatever you prefer), and pointing Google Drive and Sync to that virtual drive sitting on a drivepool would probably work, as well - but I'm tired of playing around and chancing that something else will still cause issues, so I'll keep Google Drive and Sync in my virtual PC for the foreseeable future. Edit 2: It's possible I actually tried that proposed second simpler solution first, but I still had issues. The issues might've been because, when rebooting, or signing out and signing back in to Windows (if you ever do that), it's possible that the VHDX wasn't mounted before Google Drive Backup and Sync automatically launched. While it's possible that there's a way to force Google Drive Backup and Sync to wait to launch, I either didn't look at that possibility, or didn't want to have to go down that road. Or there were circumstances where the VHDX could be temporarily unmounted, causing Google's program to crash. Anyone, please let me know if you test the local .VHDX solution, and it has no issues for weeks. Cheers, all.

I didn't have a problem with using Google Drive sync (untested with stream mode, but that would defeat my purpose) with several DrivePooled SSDs until a couple of months ago when I added four more SSDs to the pool, and now sometimes Google Drive sync works for a short time, or sometimes weeks, but then inevitably always ends up having issues in such a way that the Google Drive sync program must quit and re-launch frequently, and eventually this causes crashing of the whole PC. Yesterday I saw there were many dozens of old Google Drive sync notification icons (they disappear as you move the mouse across them) - indicating how many times the sync program has quit and relaunched itself while having issues, so I've just quit Google's sync program and configured it to not start when Windows boots for now. I'm not sure what I'm going to do from this point forward. I haven't had any issue with using Microsoft OneDrive (free account) with DrivePool over the last few years, but I hate to buy into two cloud solutions, as I definitely need Google's too. I just wanted to confirm for anyone more recently who's looking for answers that this is still an issue. I have no idea why Google Drive sync worked for me for so long and now fails very regularly.