TerraMaster Forum

agarza647 wrote: ↑25 Dec 2024, 00:54

TMRyan wrote: ↑24 Dec 2024, 22:41

I have restarted the NAS via the power button on the back several times. I have a configuration back that is two weeks old. As previously mentioned, I cannot log into the TOS dashboard. I can log into the NAS via SSH, so if you can give me any commands or the location of log files I can post those needed.

We have conducted extensive experiments in the lab, and so far, we have not been able to reproduce the failure phenomenon you described. It is inferred that the database files in your system partition may have been corrupted due to several forced shutdowns. Even so, we have tried multiple forced shutdowns ourselves and have not been able to replicate the issue. Please provide more information so that we can troubleshoot the problem.

I am wondering if something in those "two dozen docker containers" is causing the problems you describe. I am presuming you had a similar setup under 5.1 when that was displaying your issues. So the dockers could be the common denominator.

TMroy wrote: ↑26 Dec 2024, 10:21

I could understand files being corrupted for forced shutdowns, but the system ran without problems for several days. And if you have tried forced shutdowns and the files are not corrupted then that is probably not causing the issue.

At this point, I need a more reliable solution. One of the main reasons for purchasing a TerraMaster NAS was the ability to install other operating systems which is proven at viewtopic.php?t=6937.

Gremlin wrote: ↑26 Dec 2024, 17:33

That is something to think about. The NAS is currently set up with the OS on the same pool as storage. I have purchased an M.2 SSD and will install the OS on it and recreate the storage pool to remove any possible cross-file corruption. But I feel that a more robust and stable OS is in my future.

Another consideration (and I don't know if it applies here) is that Docker does not necessarily 'like' BTRFS.