TOS 6.0.750 (X86) is Released for Update

[ColaChen]

May I ask, after installation, can the TOS system page be opened normally when you log in again after a period of time?

[Gremlin]

Performed manual update to .750 on a test machine (minimal apps):
Update went relatively well. Points of note:
1) Undue amount of time spent (internally) on "TNAS Online Daemon". Long pauses trying to configure/start which happened 2 or 3 times. Did apparently start eventually (last line but one of boot screen on console). This is annoying for me since I DON'T USE Tnas Online.

2. UPS support not enabled on update. Not really a surprise.
Lots of errors in /var/log/messages regarding UPS configuration.
{NOTE: UPS Support is an ongoing subject between myself and @TMSupport which, at the moment, is going nowhere}
Settings maintained.
UPS support shows as being enabled when done manually - network support configured.

Code: Select all

Jul 13 11:57:26 NAS-T2 nut-server[5298]: Network UPS Tools upsd 2.8.3 release
Jul 13 11:57:26 NAS-T2 nut-server[5298]: Warning: ignoring incomplete configuration for UPS [ups]
Jul 13 11:57:26 NAS-T2 upsd[5298]: Warning: ignoring incomplete configuration for UPS [ups]
Jul 13 11:57:26 NAS-T2 nut-server[5298]: Fatal error: at least one UPS must be defined in ups.conf
Jul 13 11:57:26 NAS-T2 upsd[5298]: Fatal error: at least one UPS must be defined in ups.conf
Jul 13 11:57:27 NAS-T2 systemd[1]: Stopped Network UPS Tools - power devices information server.
Jul 13 11:57:27 NAS-T2 systemd[1]: Starting Network UPS Tools - power devices information server...

Ad infinitum
Further note: THIS is a CLIENT machine

3. CIFS/VFS
Appears to be a problem (which I think occurred in earlier versions)

Code: Select all

CIFS: VFS: Error connecting to socket. Aborting operation.
CIFS: VFS: cifs_mount failed w/return code = -101
Use of less secure dialect vers=1.0 is not recommended unless required for access to very old servers
CIFS: VFS: Use of less secure dialect vers=1.0 is not recommended unless required for access to very old servers
CIFS: VFS: Error connecting to socket. Aborting operation.
CIFS: VFS: cifs_mount failed w/return code = -101
CIFS: VFS: Error connecting to socket. Aborting operation.
CIFS: VFS: cifs_mount failed w/return code = -101
CIFS: VFS: Error connecting to socket. Aborting operation.
CIFS: VFS: cifs_mount failed w/return code = -101
CIFS: VFS: Error connecting to socket. Aborting operation.
CIFS: VFS: cifs_mount failed w/return code = -101

My config does not allow ver 1.0 under SMB config

4. Remote Folder
not mounted on update, as reported earlier. Settings are maintained.
Success on enabling.
Could this be the result of (3) above

5. ClamAV
Real-Time Protection remains ENABLED after update! YEAH!
EDIT:
Noticed that although enabled, ClamAV icon has disappeared from desktop and cannot be reinstated so far despite "Operation successful". Time: 16:55 local

As stated this test nas has minimal apps, so I can only speak for what is installed. I have no Hypercache enabled (Observe release note warnings about disabling this: Maybe the update package should make a better job of stopping/warning user if conflicting setups are found. I don't know, as I don't have particular setup.)

[crisisacting]

… have no Hypercache enabled (Observe release note warnings about disabling this: Maybe the update package should make a better job of stopping/warning user if conflicting setups are found. …

Their update procedure should be turning off all services before installing, so adding the option to disable the cache after that really should be a checkbox prior to running the update, if one is detected as enabled.

And then, upon reboot, it should be directly launching the cache wizard to allow for it to be setup again.

As you stated, the update should do a better job, full stop; they should not expect that every user is technical enough to take precautionary steps, especially those buried in release notes that most users never read.

[Gremlin]

As you stated, the update should do a better job, full stop;

Let's take that back a step or two. Does anyone actually test what happens when (when not if, it's inevitable) a user does not follow guidance.....
where are the QC people?
Never mind, a clean install will sort it.

[mmedic]

May I ask, after installation, can the TOS system page be opened normally when you log in again after a period of time?

Hi! Yes, it is all okay. I can operate TOS normally. Only Portainer is not working well.

[thierrys73]

Hi,

After updating my TerraMaster T6-423 to TOS 6.0.750, I’ve lost remote access to the NAS.

[MikeZhang]

Sorry for that, pleaes wait for our next release

[Joesh]

So lucky me, I'm not update these release yet

[Gremlin]

Regarding my earlier comment about ClamAV shortcut being lost viewtopic.php?p=48608#p48608
I uninstalled ClamAV (leaving config intact) and then re-installed (same version). Settings all came back (including "real-time protection") and I was able to successfully assign desktop shortcut again. All seems to be ok now, minimal effort required

[rfbjr]

Did a test of my UPS last night running on the F4-223. Well didn't have a choice, power went out for a minute. Ran on UPS, generated email, switched back to line power after a minute, generated email as well.
This really isn't specific to .750 but good to know anyway.