m2mexpert

Been using this container for quite some time and it has been great. I really like it. Recently I have something odd happening and I cannot resolve it. The container doesn't appear to bind to an IP even when configured to do so. The logs show no issue and it appears to be running. Anyone have an idea what I might be missing?

Seeing a few errors in FCP. Also noting instability in my GUI. It's probably related but not sure exactly what may be going on. Perhaps someone may have some thoughts. 1. Seeing undefined notification popups FCP Errors 1. Rootfs file is getting full (currently 100 % used)Possibly an application is storing excessive amount of data in /tmp. Seek assistance on the forums 2. Invalid folder none contained within /mntGenerally speaking, most times when other folders get created within /mnt it is a result of an improperly configured application. This error may or may not cause issues for you nasvm-diagnostics-20240909-1009.zip

Things are still rebuilding but so far no changes and no drops. Not sure what exactly was going on. I will continue to monitor. Thank you for the help.

Lets see if these upload properly. nasvm-diagnostics-20240508-1119.zip

Thanks for the guidance. I was able to get things running again although with data loss. I’m trying to figure out why Drive 5 keeps dropping out in error after rebuild now. SMART tests pass so it must be something else. i’ve attached a current diagnostics dump. it’s probably what’s contributing to whatever happened before. nasvm-diagnostics-20240507-0724.zip

I just ran into an issue with rebuilding a drive. I have an array with dual parity disks. I had 2 disks exhibit an error. This has happened before and I usually rebuild one then when complete rebuild the other. In this case the disk was partially rebuilt and I noticed some array data was missing. I stopped the rebuild, rebooted the server and saw that 3 disks were unmountable. Something is causing my disks to drop out of the array and now I'm in a state that I don;t know how to recover from. I've attached diagnostics in case that might help diagnose the issue. nasvm-diagnostics-20240429-1948.zip