Hi Christopher, yes, same ticket - thanks for putting it in here.
rtech73, the TL;DR is there was a curious entry in the system log that read "Reset to device, \Device\RaidPort0, was issued." Googling that got this article, and when I went to check, sure enough that's what happened.
More detail: I'm mainly a *nix guy, and have used OS X as my primary OS since uhh ... 10.1? Maybe the DP? A while at any rate. The reason I have a Windows Server is to support the Windows-based HTPC which in turn exists only because I have to have a cablecard. So a number of things which I guess is normal in Windows world never occured to me. The obvious symptom was that the pool was freezing up, so I posted here and then saw that I was eligible to submit a ticket, so I did. Some rounds of troubleshooting later, Christopher mentioned checking the system log (which I forgot Windows had, honestly - "Event Viewer" doesn't immediately translate to "log" to an OS X / Unix guy). And then the rest fell into place - I know that the power went the day the errors began but the system is on a UPS, so naturally it switched over and there were no FS errors. What I didn't realize it also apparently switched power plans; again to a Unix person this is weird behavior because a) why should there be power plans; and why would a server of all things have power plans - it's a desktop server, not a laptop. The standard power plan has the PCI Express Link State Power Management option to "off"; the "balanced" plan has it to "moderate". And when I switched it, it suddenly started functioning again, so I asked Christopher to close the ticket.
Honestly, this might have been the straw that broke the camel's back. I think I'm going to use VMWare or Parallels to virtualize a Win7 instance for the HTPC on a Mac Mini and retire the Windows Server, though WAF needs to be checked