TerraMaster Forum

TOS 6.0.673 Terramaster f4-424 max

Hi,

Have the same issue with OPENVPN after upgrading to TOS 6.0.673, upgrade failed and was not able to log back into the system.

Steps taken
OS is on a MV2 drive, formatted the OS portion, reset motherboard and reinstall OS.
Installed the TOS 6.0.673 and not able to connect using the .opvn file.
ID and Password have not changed, even re-downloaded .opvn files (No change there)

System is a F4-424 Pro.

Really feel this is a new bug.

Thank you

Gremlin wrote: ↑27 Apr 2025, 23:16 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.

yep the F2-423 i cant see the F2-210 getting many more updates , and yes i probably should have mentioned i do have the two LANS bonded together to give one IP for the nas drive

i believe my routers DHCP is network aware its not a cheapo router from an ISP, but its only for home purposes so no great issue if it does assign a duplicate and it drops off the network, but assuming because the router gives me a map of the devices on the network and the NAS drive is listed then it shouldn't want to assign the same IP to another device when it knows its already in use

sianderson wrote: ↑30 Apr 2025, 05:56

All well and good, hopefully. There is one issue that I discovered early on - depending on boot process and type of bond chosen, the nas can (within the bond), allocate the MAC of LAN2 as the primary port, so the dhcp server can be confused. I believe some changes have been made already within TOS and more may be to come with regard to optimising this but I made the decision to use fixed ip and have not checked back on the latest updates.

Gremlin wrote: ↑30 Apr 2025, 06:34

I think you might be referring to this. We will see if it's possible to implement on the new network tools. If future releases include NAS models with both high and low bandwidth, we might consider it. However, feasibility still requires thorough research.
viewtopic.php?t=7668

epx8dcm4 wrote: ↑30 Apr 2025, 05:38 Hi,

Have the same issue with OPENVPN after upgrading to TOS 6.0.673, upgrade failed and was not able to log back into the system.

Steps taken
OS is on a MV2 drive, formatted the OS portion, reset motherboard and reinstall OS.
Installed the TOS 6.0.673 and not able to connect using the .opvn file.
ID and Password have not changed, even re-downloaded .opvn files (No change there)

System is a F4-424 Pro.

Really feel this is a new bug.

Thank you

This is a compatibility issue. It has been added to the list of items to be addressed; please wait for future version updates.

Vladimir wrote: ↑30 Apr 2025, 03:53 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

Sorry for the issue you are experiencing. We have reproduced the situation and are actively working to resolve it. Thank you for informing us.

I suppose someone has to ask: How could you break "configuration backup"?

Gremlin wrote: ↑30 Apr 2025, 06:34

sianderson wrote: ↑30 Apr 2025, 05:56

All well and good, hopefully. There is one issue that I discovered early on - depending on boot process and type of bond chosen, the nas can (within the bond), allocate the MAC of LAN2 as the primary port, so the dhcp server can be confused. I believe some changes have been made already within TOS and more may be to come with regard to optimising this but I made the decision to use fixed ip and have not checked back on the latest updates.

that makes perfect sense if thats whats happening, oh well static solves the issue and for a server its probably the best thing

[/quote]
Sorry for the issue you are experiencing. We have reproduced the situation and are actively working to resolve it. Thank you for informing us.
[/quote]

Thankfully I found this post after doing a recovery and trying to do another backup. So exactly how do I do a system reset? Or is that the same steps as reinstalling TOS? (Before I start the recovery process for a second time...)