So, it turns out we just had to uninstall and reinstall IIS. As far as my team can figure, because the second volume wasn't present when IIS was installed, it didn't register something about it. After that, it was fine.
For posterity, this was on Windows Server 2012, but we have also experienced this on Win 7 as well and were totally stymied in the past.