Hi everyone!
Something strange happened a few hours ago on my D920+. It started beeping, which is definitely not a good sign. I logged-in to check what was happening and found the four following notifications, published in that order and only a few seconds or minutes apart (translated from french, official wording may vary
):
1) Container manager: Container PaperlessNGX-DB stopped unexpectedly. [Yes I run a Paperless stack with a DB]
2) Storage Group1 crashed and has been removed from the data cleaning task scheduling.
3) Volume1 has been set to Read Only (
)
4) Severity error message has been created.
My immediate action was to turn the device OFF, as I really had to go and couldn't investigate at that moment. Before turning it ON again I checked my Pushover app and Active Insight: I couldn't find anything, as if nothing happened.
After turning the NAS ON again, I could find these four notification, plus an additional one that said that "Volume1 was set to read only mode, but got automatically repaired and is now healthy." [I run a RAID5 array with an additional Hot Spare disk, I don't know if that helped to repair or not...]. That's all. Nothing else. The journals don't give any detailed information, all lights are green and everything seems normal in the storage manager, from what I can say at least. Each disk runs IronWolf health and complete S.M.A.R.T tests on a monthly basis: everything OK.
The only relevant action I could identify so far was to stop the Paperless stack. It is not critical to me. But damn I don't feel secure knowing something serious happened but having absolutely no clue, nor indication from the device itself about WHAT HAPPENED?
Has anyone an idea about what I could and should do to further investigate to ensure my system is healthy and will stay so?
The only thing I have to confess is that I put an additional "unofficial" 8Gb RAM memory into the device, but that was months ago and didn't cause any problem so far. Could that be the issue? What do you think about the notification sequence: could the paperless stack be guilty for such a problem?
Thanks a lot for your help and BR!
Something strange happened a few hours ago on my D920+. It started beeping, which is definitely not a good sign. I logged-in to check what was happening and found the four following notifications, published in that order and only a few seconds or minutes apart (translated from french, official wording may vary

1) Container manager: Container PaperlessNGX-DB stopped unexpectedly. [Yes I run a Paperless stack with a DB]
2) Storage Group1 crashed and has been removed from the data cleaning task scheduling.
3) Volume1 has been set to Read Only (

4) Severity error message has been created.
My immediate action was to turn the device OFF, as I really had to go and couldn't investigate at that moment. Before turning it ON again I checked my Pushover app and Active Insight: I couldn't find anything, as if nothing happened.
After turning the NAS ON again, I could find these four notification, plus an additional one that said that "Volume1 was set to read only mode, but got automatically repaired and is now healthy." [I run a RAID5 array with an additional Hot Spare disk, I don't know if that helped to repair or not...]. That's all. Nothing else. The journals don't give any detailed information, all lights are green and everything seems normal in the storage manager, from what I can say at least. Each disk runs IronWolf health and complete S.M.A.R.T tests on a monthly basis: everything OK.
The only relevant action I could identify so far was to stop the Paperless stack. It is not critical to me. But damn I don't feel secure knowing something serious happened but having absolutely no clue, nor indication from the device itself about WHAT HAPPENED?
Has anyone an idea about what I could and should do to further investigate to ensure my system is healthy and will stay so?
The only thing I have to confess is that I put an additional "unofficial" 8Gb RAM memory into the device, but that was months ago and didn't cause any problem so far. Could that be the issue? What do you think about the notification sequence: could the paperless stack be guilty for such a problem?
Thanks a lot for your help and BR!