0x8000ffff catastrophic failure after 2.3.12.1683 update

[ppmguire]

As the title states, after updating to 2.3.12.1683 and the required reboot I am now getting this error when trying to write anything to the pooled drive. All drives show clear and green with Stablebit Scanner in the pool and I have verified in disk management none of the drives are suddenly marked read only.
I have 2 pools, the second one doesn't produce this issue after the update. 

[Shane]

1) If you open Windows Disk Management, are any of the Disks "Read Only"? Try the solution in this post (it also shows a screenshot of what to look for).

2) If that doesn't help or isn't applicable, try resetting the pool's NTFs permissions? Try the solutions in this post.

Please let us know how it goes, and if the above don't help I'd suggest opening a support ticket.

 

[ppmguire]

5 hours ago, Shane said:

1) If you open Windows Disk Management, are any of the Disks "Read Only"? Try the solution in this post (it also shows a screenshot of what to look for).

2) If that doesn't help or isn't applicable, try resetting the pool's NTFs permissions? Try the solutions in this post.

Please let us know how it goes, and if the above don't help I'd suggest opening a support ticket.

 

1) Mentioned in my OP they aren't marked as read only.

2) Funny thing. As I was preparing to do this and grabbed the SetACL stuff I did a laughable SFC /Scannow then for sanity sake another reboot and it corrected itself. SFC found no corrupted files but luckily the reboot fixed a potentially annoying problem. 

I will add the SetACL instructions under the read only section in my documentation in case this might happen again. After several years of using Drivepool in multiple different areas this is the first I've seen this and my usual troubleshooting didn't work. Thank you for the response.