TerraMaster Forum

I can't access my TNAS anymore after a reboot.
I get the page 502 Bad Gateway when i go to http://tnas.local:8181/tos/

i can SSH on the tnas, i can still see my data in /Volume1.
How to fix this issue ?

F8 SSD plus

i followed this procedure documented here viewtopic.php?t=6810 and it worked.
However i would really like to understand why we can lost the OS like this.

Also i am seeing some error on startup during the boot : is that expected ?
- Failed to start Atop advanced performance monitor
- Failed to start Iptables service

I had this same problem.

It was resolved by SSHing into the TNAS and deleting /etc/p, which was roughly 5GB in size, then rebooting:
# rm /etc/p
# reboot

I believe that file was somehow created after I did a system configuration backup. It filled the system partition, preventing a bunch of different operations that need to write to the system log.

We sincerely apologize for the inconvenience caused by this issue. After confirmation, it has been identified as a bug related to the backup system configuration. Our technical team has prioritized the fix, and it is scheduled to be resolved in an upcoming version. We truly appreciate you sharing your workaround and thank you for your continued support of TerraMaster!

Thanks a lot for the information, i had the same problem (actually 2 times, but new to Terramaster, i thought i made a mistake or something wrong the first time) : but it really was after backing up the system config.
I would like to add that SSH connection didnt work for me, the only way to use the command prompt was to connect a hdmi monitor and a usb keyboard.
For the record, the logs indicate that postgre cannot start, unable to create postmaster.pid because there's no disk space.

So DONT USE THE SYSTEM CONFIG BACKUP until it is fixed !

Sad to hear that another user encountered that bug.
Instead of sincere apologizes a warning to prevent it would be so much better.
Like a message popping up, or a link to a known bugs page, when downloading v6.0.673a (or v6.0.688a) ?
Reading all threads on the forum is not an option, you should be able to trust the stuff offered is safe.
Right now there is nothing in place, user after user is reporting their mishap.
Sad. And sorry for your and everybody else's experience.

i again had the same issue after making a backup of the system configuration and rebooting

ethaneade wrote: ↑20 May 2025, 02:45 I had this same problem.

It was resolved by SSHing into the TNAS and deleting /etc/p, which was roughly 5GB in size, then rebooting:
# rm /etc/p
# reboot

I believe that file was somehow created after I did a system configuration backup. It filled the system partition, preventing a bunch of different operations that need to write to the system log.

Thank you : rm /etc/p solve my issue. glad i not had to redo the procedure for a complete OS install

So... what does that mean in terms of a timeline for the fix? Tomorrow, next month, ???

TMjack wrote: ↑20 May 2025, 19:04 We sincerely apologize for the inconvenience caused by this issue. After confirmation, it has been identified as a bug related to the backup system configuration. Our technical team has prioritized the fix, and it is scheduled to be resolved in an upcoming version. We truly appreciate you sharing your workaround and thank you for your continued support of TerraMaster!

redpillmurica wrote: ↑23 May 2025, 10:13

There are plans to optimize it in future versions