TerraMaster Official Forum

TMroy wrote: ↑04 May 2023, 23:17 Can you send us the S.M.A.R.T. report of the SAMSUNG SSD to study?

Both are Samsung, the smart readings are very weird to be honest, power-on hours are way low while they're in the F2-423 for about 6 months when I received the unit. Will try to update the firmware and check again

I don't think that's possible through TOS? I do have a laptop with 2 nvme slots on which I could load one up and try that

Or docker update or TOS update made my connected folders readonly.
That's what the app says, but they're all empty/inaccessible.
Had to re-assign folders for all docker instances.....

I think the update did something to my homefolder settings and is pointing to another location (/Volume1/User/xxx) instead of /home/xxx

Hi, . It just happened again, got the warning e-mail, so I logged in immediately and checked, all temps are 33-35 degrees fahrenheit. So I keep checking and there was a spike on temp readings of my nvme drive I only use for docker/virtualbox of 2 seconds going to 84 degrees fahrenheit and then back ...

The gateway of my fixed ethernet connections get set to 192.168.0.1, while I set them manually to 192.168.0.254.
This is irritating because I have to fix this continously.
Model is F2-423 running latest firmware

I regularly get the message that my hard drive is overheated, but it never tells me which hard drive is overheated. I've replaced my cache nvme due that was getting a bit hot (around 60 degrees farenheit), but it would be so much easier knowing which drive is getting hot. Smart is OK, temps are all ...

Hi, is it possible to autostart a VM afte rest/power-failure?

I've enabled the $startStopConfig = true; in config.php, so now the option "Startup Mode" is shown and can be set within the General->Basic option of a VM, however it doesn't work...

I had 1 windows VM and 2 linux vm's, but that doesn't really matter.
Somehow the "Default machine folder" within phpvirtualbox was changed and it wasn't by me.
Looks a bit like an earlier bug: viewtopic.php?f=73&t=2041

Hi, After the firmware update to 5.1.24-00324, my VM list in VirtualBox is empty. The vdi and sparse files are not lost (still on the Volume), but when I try to add the existing VM I get the following error: VirtualBox error: rc=0x80004005 Extra content at the end of the document. Location: '/home/x...