TerraMaster Forum

terramaster t9-450

op system latest 6.0794

the problems thats happening now is if theres no useage after around 4-6 hrs the nas is going into some sort of sleep or hubernation or somthing i have no idea

i have checked my drive setting says to allow sleep after 30 mins this has always been the case so not changed i dont think its this as not changed

i have checked control panel i have wake on lan set

there is no power scedule to sleep or turn off

what i can say is after returning to use the nas is the network on the pc shows as empty ie no folders that should be there along with usb devices attached all gone like its turned off


i try going to the web page and just get a bad gateway message instead of to log in

the nas itsself none of the green lights are blinking all solid green

i also try t nas pc app intresting it lists the server there but cant do anything with it log in will take me to the page bad gateway all i can do is go to the server and press the power button it makes a long beep then shuts down press the power button and its all back and running i just cant work out what sis putting it into sleep /hybernate and why it wont wake

my problem started yesterday i wanted to make more storage so took a 18tb out and put in a 26tb i have used before in this machine so no problems
in sync and was ready to use after 3 days

Based on your description, your device is not in sleep mode but has crashed—likely due to a system panic triggered by certain factors. Possible causes include memory failure or hard drive issues. You’ll need to troubleshoot these possibilities systematically.

many thanks for your reply

i have forched the nas to stay awake all night by running plex on it
not sure if that info will help but it did not crash

the nas says all drives are heathy is there anything else i need to do to check hard drive issue ??
also how do i test memory failure ??

as i brought this less than 2 years ago i would hope this is not a hardware failure like memory

i have the system installed on a m2 which i put in about 1 year ago do you think this would propably be the problem drive ?? if so how do i go about it

if i place a new m2 in i take it the op needs reinstall so would i just pull all the drives and insert the new m2 and install op then reinsert drives to get my storage pool back ??

awaiting your reply about memory

jwills70 wrote: ↑15 May 2026, 17:29

You may enable debug mode at TOS desktop dock bar "Support and Help", when this issue happens again, by pressing power button to enter TOS again and export debug log, send to support email for analysis

You can also enable SSH in TOS control panel>terminal, when the issue occurs again, check if you can connect via SSH: viewtopic.php?f=78&t=2350, if yes, we can remote in to troubleshoot for you

About memory, you may use memtester tool to check if the memory can PASS the test

ok as soon as i enabled debug mode it crashed out and said operation failed

its not showing me anything like server info or nothing on the dock bar works i can log in with ssh

i rebooted and downloaded log unsure if its any good or i should wait for it to crash






https://www.dropbox.com/scl/fi/9wsymuvv ... 5jyow&dl=0

also unsure how to use memory test thing i am only used to windows

i have pulled the new disk out and reinserted it to make sure it was in properbly as this is when all the problems started it may just be coincadance so its currently doing a rebuild just to make sure

it frooze again now and taking ages to boot i can still use putty

Hi jwills70,
We did not find any obvious anomalies in the log files you provided. (There are three debug logs; the other two may have been blocked by your browser, so please check them.)
Your RAID is currently undergoing high-speed synchronization, which results in high system load, especially since you are running many services and applications simultaneously. We recommend waiting until the RAID synchronization is complete before observing the situation further.
You can listen to the sound of the HDDs; if they are spinning at high speed, it indicates they are not in sleep mode but are actively synchronizing. Generally, RAID synchronization does not enter sleep mode.
Overall, this is caused by excessive system load. If you wish to perform limited operations while the RAID is synchronizing, you may consider reducing the RAID synchronization speed,