sianderson wrote: ↑25 Apr 2025, 02:06
updated, other than upon rebooting it decided to get another IP address from the DHCP which caused a little confusion but once set to static all was good, it seems to be working and no issues so far
What did you mean? why the new IP from DHCP got you confused?
rebooting the the nas drive i get the same IP every time from the DHCP server
however when it rebooted to do the update its as if the router saw it as a different device on the network so allocated a different IP rather than its original one, so with it being a different IP then the connection just timed out to it and i couldnt access it as i didnt know its new IP, once i realised it had changed it was fine
F2-424 TOS 7.0.0765 F2-423 TOS 7.0.0765 F2-210 TOS 4.2.44 D4-320
It is normal situation. As soon as the IP lease time expired, your nas will send a request to DHCP server, DHCP server will offer a new IP to your nas, and DHCP server will decide which exact IP to offer, instead of your nas. There is a possibility that just before your update, the IP lease time is expired, this lead to a new IP offered from DHCP server.
To contact our team, please send email to following addresses, remember to replace (at) with @:
Support team: support(at)terra-master.com (for technical support only)
Service team: service(at)terra-master.com (for purchasing, return, replacement, RMA service)
To contact our team, please send email to following addresses, remember to replace (at) with @:
Support team: support(at)terra-master.com (for technical support only)
Service team: service(at)terra-master.com (for purchasing, return, replacement, RMA service)
Hello
I performed the test twice and same result.
I created a bond network with the 802.3ad compatible interface. I created the aggregation on my switch router ZYXEL 1915 and everything worked correctly for several hours.
And suddenly my username was no longer recognized.
Reboot same issue and tnas pc dont see more the tnas t6-423
I had to reinstall the system.
since then I have created a bond network with Balance-alb on my tnas and no more pb.
It is normal situation. As soon as the IP lease time expired, your nas will send a request to DHCP server, DHCP server will offer a new IP to your nas, and DHCP server will decide which exact IP to offer, instead of your nas. There is a possibility that just before your update, the IP lease time is expired, this lead to a new IP offered from DHCP server.
nope im afraid this is not the case, i have rebooted the nas drive a few times and never been given a different IP as it assigns it based on MAC address so there was no reason why it couldnt have just given the same IP back, but like i say its not a problem ive assigned it a static IP now back to its original one so wont happen in the future
F2-424 TOS 7.0.0765 F2-423 TOS 7.0.0765 F2-210 TOS 4.2.44 D4-320
Presume your are talking about F2-423; Did you happen to have both LAN connected during update and do you use any sort of network bond? (Just curious to see if it matches any of my previous experience.) Be cautious if assigning a fixed IP from the DHCP pool. That can cause issues and some (most!) routers don't support that.
thierrys73 wrote: ↑27 Apr 2025, 17:03
Hello
I performed the test twice and same result.
I created a bond network with the 802.3ad compatible interface. I created the aggregation on my switch router ZYXEL 1915 and everything worked correctly for several hours.
And suddenly my username was no longer recognized.
Reboot same issue and tnas pc dont see more the tnas t6-423
I had to reinstall the system.
since then I have created a bond network with Balance-alb on my tnas and no more pb.
Hello
i find the reason of my lost username it is not the network !!!
When i do a save configuration i lost my username
and i have to reconfire all the TNAS !!
Can you verify please ?
T6-423 TOS 6.0.673
Regarding your issue, it seems there is an unknown error causing an exception. We recommend contacting the LiveChat on the homepage or the technical support email, and providing a system report. If necessary, we can arrange for an engineer to perform a remote inspection.
To contact our team, please send email to following addresses, remember to replace (at) with @:
Technical team: support(at)terra-master.com (for technical support)
Service team: service(at)terra-master.com (for purchasing, return, replacement, RMA service)
thierrys73 wrote: ↑27 Apr 2025, 17:03
Hello
I performed the test twice and same result.
I created a bond network with the 802.3ad compatible interface. I created the aggregation on my switch router ZYXEL 1915 and everything worked correctly for several hours.
And suddenly my username was no longer recognized.
Reboot same issue and tnas pc dont see more the tnas t6-423
I had to reinstall the system.
since then I have created a bond network with Balance-alb on my tnas and no more pb.
Hello
i find the reason of my lost username it is not the network !!!
When i do a save configuration i lost my username
and i have to reconfire all the TNAS !!
Can you verify please ?
T6-423 TOS 6.0.673
I confirm the presence of this issue. When creating a system backup, all users are deleted. After rebooting, it is impossible to log in to the system. However, if you do not log out after creating the backup and perform a system reset, the system resets normally. System configuration recovery proceeds without issues.
Terramaster f4-424 max TOS 6.0.673
Last edited by Vladimir on 30 Apr 2025, 03:57, edited 1 time in total.
