TerraMaster Forum

So an interesting occurrence. I noticed an issue login in via the web interface. I would get an error "user does not exists". I logged in locally to the nas and investigated the user account... no issues... I checked drive space and found 100 percentnusage on a system partition. On 10 May a file "p" was created in /etc of 5.4gb. The file looked like a random dump with both text entries and machine code. I deleted this file and then was able to log in from web again. I'm not sure how or why this file was created but perhaps this information will assist someone else who experiences the same thing.

Herewerare2024 wrote: ↑19 May 2025, 04:18 So an interesting occurrence. I noticed an issue login in via the web interface. I would get an error "user does not exists". I logged in locally to the nas and investigated the user account... no issues... I checked drive space and found 100 percentnusage on a system partition. On 10 May a file "p" was created in /etc of 5.4gb. The file looked like a random dump with both text entries and machine code. I deleted this file and then was able to log in from web again. I'm not sure how or why this file was created but perhaps this information will assist someone else who experiences the same thing.

Thank you very much for sharing your experience! We have not previously encountered the situation you described. To help us reproduce the issue in our lab environment and conduct a more accurate investigation, we would greatly appreciate your assistance in providing the following information:

1.System Version: The TOS version number currently in use.

2.Operation History: The specific actions you performed prior to being unable to log in via the web interface.

3.Folder Details: The full name of the folder involved in the issue (there are multiple folders under /etc beginning with "p").

4.Screenshot Support: If available, related screenshots can help us better locate and understand the issue.

Note: To maintain system stability, we typically avoid writing large amounts of data to the system partition. Therefore, a detailed context is essential for analyzing the root cause of the anomaly.

We look forward to your feedback so we can begin our investigation as soon as possible!

Have you ever backed up your system configuration?

Latest TOS release. The file was created 10 may and was literally "p" with a size of 5.4gb.

Prior to being able to log in via web interface, I connected a monitor and keyboard directly to the NAS. At the prompt I ran a search command for large files. The return indicated a few files within the parameters with obvious issue in the /etc/p file.

The problem with the user account was associated with the system drive being 100 percent full which prevented web login due to no system space available. In attempting to clear memory before doing the large file search, logs and other miscellaneous files were removed to free up space. I do not know why the large file was created on 10 may.

I use the NAS for plex and picture backup. I have a ram drive for transcodes configured. The storage for pictures is not pointed to a system partition. The creation of this random large file is a mystery.

I did backup the system config. Is it possible that backup dumped the config to /etc/?

I had the same problem, which also appeared after I backed up my system configuration.

I resolved it similarly via SSH login:
# rm /etc/p
# reboot

It must be a bug somehow triggered by backing up the system config.

I suppose I was lucky that I could still log in via SSH. I'm guessing that login doesn't require writing to any system-partition logs.

Herewerare2024 wrote: ↑19 May 2025, 21:31 I did backup the system config. Is it possible that backup dumped the config to /etc/?

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. Thank you for your continued support of TerraMaster!

ethaneade wrote: ↑20 May 2025, 02:48 I had the same problem, which also appeared after I backed up my system configuration.

I resolved it similarly via SSH login:
# rm /etc/p
# reboot

It must be a bug somehow triggered by backing up the system config.

I suppose I was lucky that I could still log in via SSH. I'm guessing that login doesn't require writing to any system-partition logs.

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!

I would suggest putting this information out in a broader sense as some users may not have the same expertise in correcting the issue if they run the backup. Like a notice in the news forum or... something like that. Official bug report area etc...

Your feedback is very reasonable, and we are already working on releasing an announcement regarding this issue.