Bug Reports, Operation Guides, and Experience Sharing
https://forum.terra-master.com/en/
I don't think this is the reason. During first load (v 783) I rejected system proposal to create a new Pool. Then I opened settings to ensure that disks were properly recognised - no issues there. Then I opened system observer and found that I have /home folder full of data. Can you believe in it? According to control panel I didn't have a pool, didn't have volumes, but had a "/home" folder with data on it! Then I opened File Manager - there was no data there. Only after this I closed control panel and rebooted the system. It looked and smelled like a some glitch or something like this. I'm pretty sure that experienced user will handle this well, but I decided to let you know about this situation.RyanYang wrote: ↑22 Sep 2025, 19:28Upon receiving your feedback, our lab promptly conducted a retest to replicate the issue. Analysis indicates that this phenomenon is likely due to certain disks not being recognized in time during the system update and restart process.
Therefore, we recommend you try the following steps:
1. Check whether the disk tray is securely fastened with screws and ensure the disk is fully locked in place. You can try reseating the disk and then restarting the device.
2. It is advised to enable Debug Mode in the "Support & Help" section of the system before restarting. If the anomaly occurs again after restarting, further analysis can be performed using the debug logs.
If the issue persists, please feel free to contact us, and we will assist you as soon as possible.
Hello! Can you provide us with your TNAS model, disk model, quantity, and capacity? Our laboratory will try to reproduce your problem. Thank you for your feedback!vitali wrote: ↑23 Sep 2025, 04:36I don't think this is the reason. During first load (v 783) I rejected system proposal to create a new Pool. Then I opened settings to ensure that disks were properly recognised - no issues there. Then I opened system observer and found that I have /home folder full of data. Can you believe in it? According to control panel I didn't have a pool, didn't have volumes, but had a "/home" folder with data on it! Then I opened File Manager - there was no data there. Only after this I closed control panel and rebooted the system. It looked and smelled like a some glitch or something like this. I'm pretty sure that experienced user will handle this well, but I decided to let you know about this situation.RyanYang wrote: ↑22 Sep 2025, 19:28Upon receiving your feedback, our lab promptly conducted a retest to replicate the issue. Analysis indicates that this phenomenon is likely due to certain disks not being recognized in time during the system update and restart process.
Therefore, we recommend you try the following steps:
1. Check whether the disk tray is securely fastened with screws and ensure the disk is fully locked in place. You can try reseating the disk and then restarting the device.
2. It is advised to enable Debug Mode in the "Support & Help" section of the system before restarting. If the anomaly occurs again after restarting, further analysis can be performed using the debug logs.
If the issue persists, please feel free to contact us, and we will assist you as soon as possible.
P.S. I didn't see any issues later.
model: F4-424TMbuddy wrote: ↑23 Sep 2025, 09:25Hello! Can you provide us with your TNAS model, disk model, quantity, and capacity? Our laboratory will try to reproduce your problem. Thank you for your feedback!vitali wrote: ↑23 Sep 2025, 04:36I don't think this is the reason. During first load (v 783) I rejected system proposal to create a new Pool. Then I opened settings to ensure that disks were properly recognised - no issues there. Then I opened system observer and found that I have /home folder full of data. Can you believe in it? According to control panel I didn't have a pool, didn't have volumes, but had a "/home" folder with data on it! Then I opened File Manager - there was no data there. Only after this I closed control panel and rebooted the system. It looked and smelled like a some glitch or something like this. I'm pretty sure that experienced user will handle this well, but I decided to let you know about this situation.RyanYang wrote: ↑22 Sep 2025, 19:28
Upon receiving your feedback, our lab promptly conducted a retest to replicate the issue. Analysis indicates that this phenomenon is likely due to certain disks not being recognized in time during the system update and restart process.
Therefore, we recommend you try the following steps:
1. Check whether the disk tray is securely fastened with screws and ensure the disk is fully locked in place. You can try reseating the disk and then restarting the device.
2. It is advised to enable Debug Mode in the "Support & Help" section of the system before restarting. If the anomaly occurs again after restarting, further analysis can be performed using the debug logs.
If the issue persists, please feel free to contact us, and we will assist you as soon as possible.
P.S. I didn't see any issues later.