TerraMaster Forum

Bug Reports, Operation Guides, and Experience Sharing
https://forum.terra-master.com/en/

TOS 5.1.123 (X86) is Released for Update

https://forum.terra-master.com/en/viewtopic.php?t=5722

Page 5 of 5

Re: TOS 5.1.123 (X86) is Released for Update

Posted: 21 Apr 2024, 16:43
by topo01
TMzethar wrote: ↑19 Apr 2024, 22:25
MapaM wrote: ↑19 Apr 2024, 01:19
Upgrading from an old model of TOS4 to TOS5 is not easy, and only a portion of users wish to upgrade to TOS5, ...
I would speculate that this particular portion of users is very close to 100%!

Re: TOS 5.1.123 (X86) is Released for Update

Posted: 23 Apr 2024, 18:38
by astrolinux
Have you found a different way to upgrade system partition from 2GB to 8GB without formatting the data partition? I have an F2-221 with two 4GB disks in RAID with version 5.1.41 (and 2GB system partition of course).
Thank you

Re: TOS 5.1.123 (X86) is Released for Update

Posted: 23 Apr 2024, 22:05
by RyanYang
astrolinux wrote: ↑23 Apr 2024, 18:38
There is no other way, you need to back up the data and then format it.

Re: TOS 5.1.123 (X86) is Released for Update

Posted: 24 Apr 2024, 18:07
by XFNeo
After update TOS from 5.1.103 to 5.1.123 (also I updated docker manager to 2.0.16 version) some of my cron job stop working.
E.g.:

Code: Select all

*/5 * * * * docker exec -u www-data nextcloud-app-1 php cron.php
/var/log/crond.log:

Code: Select all

[Wed Apr 24 13:35:01 +04 2024] exec /etc/init.d/nas/everyminuteexec
[Wed Apr 24 13:36:01 +04 2024] exec /etc/init.d/nas/everyminuteexec
Apr 24 13:36:01 TNAS-MATI crond: exit status 1 from user user1 /etc/init.d/nas/everyminuteexec
Apr 24 13:37:01 TNAS-MATI crond: ignoring /var/spool/cron/crontabs/root (non-existent user)
Apr 24 13:37:01 TNAS-MATI crond: no timestamp found (user root job sys-hourly)
Apr 24 13:37:01 TNAS-MATI crond: unable to write timestamp to /var/spool/cron/cronstamps/root.sys-hourly (user root job sys-hourly)
Apr 24 13:37:01 TNAS-MATI crond: no timestamp found (user root job sys-daily)
Apr 24 13:37:01 TNAS-MATI crond: unable to write timestamp to /var/spool/cron/cronstamps/root.sys-daily (user root job sys-daily)
Apr 24 13:37:01 TNAS-MATI crond: no timestamp found (user root job sys-weekly)
Apr 24 13:37:01 TNAS-MATI crond: unable to write timestamp to /var/spool/cron/cronstamps/root.sys-weekly (user root job sys-weekly)
Apr 24 13:37:01 TNAS-MATI crond: no timestamp found (user root job sys-monthly)
Apr 24 13:37:01 TNAS-MATI crond: unable to write timestamp to /var/spool/cron/cronstamps/root.sys-monthly (user root job sys-monthly)
[Wed Apr 24 13:37:01 +04 2024] exec /etc/init.d/nas/everyminuteexec
Apr 24 13:37:01 TNAS-MATI crond: exit status 1 from user user1 /etc/init.d/nas/everyminuteexec
[Wed Apr 24 13:38:01 +04 2024] exec /etc/init.d/nas/everyminuteexec
Apr 24 13:38:01 TNAS-MATI crond: exit status 1 from user user1 /etc/init.d/nas/everyminuteexec
[Wed Apr 24 13:39:01 +04 2024] exec /etc/init.d/nas/everyminuteexec
Apr 24 13:39:01 TNAS-MATI crond: exit status 1 from user user1 /etc/init.d/nas/everyminuteexec
Apr 24 13:40:01 TNAS-MATI crond: failed to get uid for root
Apr 24 13:40:01 TNAS-MATI crond: unable to ChangeUser (user root job sys-hourly)
Apr 24 13:40:01 TNAS-MATI crond: unable to write timestamp to /var/spool/cron/cronstamps/root.sys-hourly (user root job sys-hourly)
Apr 24 13:40:01 TNAS-MATI crond: exit status 1 from user root job sys-hourly
[Wed Apr 24 13:40:01 +04 2024] exec /etc/init.d/nas/everyminuteexec
Apr 24 13:40:16 TNAS-MATI crond: exit status 1 from user user1 /etc/init.d/nas/everyminuteexec
Apr 24 13:40:16 TNAS-MATI crond: exit status 127 from user user1 docker exec -u www-data nextcloud-app-1 php cron.php
[Wed Apr 24 13:41:01 +04 2024] exec /etc/init.d/nas/everyminuteexec
Apr 24 13:41:01 TNAS-MATI crond: exit status 1 from user user1 /etc/init.d/nas/everyminuteexec
[Wed Apr 24 13:42:01 +04 2024] exec /etc/init.d/nas/everyminuteexec
Apr 24 13:42:01 TNAS-MATI crond: exit status 1 from user user1 /etc/init.d/nas/everyminuteexec
[Wed Apr 24 13:43:01 +04 2024] exec /etc/init.d/nas/everyminuteexec
Apr 24 13:43:01 TNAS-MATI crond: exit status 1 from user user1 /etc/init.d/nas/everyminuteexec
[Wed Apr 24 13:44:01 +04 2024] exec /etc/init.d/nas/everyminuteexec
Apr 24 13:44:01 TNAS-MATI crond: exit status 1 from user user1 /etc/init.d/nas/everyminuteexec
Apr 24 13:45:01 TNAS-MATI crond: exit status 127 from user user1 docker exec -u www-data nextcloud-app-1 php cron.php
[Wed Apr 24 13:45:01 +04 2024] exec /etc/init.d/nas/everyminuteexec
Apr 24 13:45:16 TNAS-MATI crond: exit status 1 from user user1 /etc/init.d/nas/everyminuteexec
[Wed Apr 24 13:46:01 +04 2024] exec /etc/init.d/nas/everyminuteexec
[Wed Apr 24 13:47:01 +04 2024] exec /etc/init.d/nas/everyminuteexec
Apr 24 13:47:01 TNAS-MATI crond: exit status 1 from user user1 /etc/init.d/nas/everyminuteexec
The command "docker exec -u www-data nextcloud-app-1 php cron.php" works when I start it from termainal manually.

When I changed "docker" to "/Volume1/@apps/DockerEngine/dockerd/bin/docker" it starts working again.

Code: Select all

*/5 * * * * /Volume1/@apps/DockerEngine/dockerd/bin/docker exec -u www-data nextcloud-app-1 php cron.php

P.S. In /var/log/crond.log also a lot of strange logs with "exit status 1"

Re: TOS 5.1.123 (X86) is Released for Update

Posted: 06 May 2024, 18:09
by TMroy
UncleJohnsBand wrote: ↑06 May 2024, 00:49
Thank you for your report! BUT you are posting in an incorrect forum. Please create a new post in the correct forum section, your threads will be deleted soon.

Re: TOS 5.1.123 (X86) is Released for Update

Posted: 06 May 2024, 19:03
by UncleJohnsBand
TMroy wrote: ↑06 May 2024, 18:09
UncleJohnsBand wrote: ↑06 May 2024, 00:49
Thank you for your report! BUT you are posting in an incorrect forum. Please create a new post in the correct forum section, your threads will be deleted soon.
For me the app was part of this release 5.1.123 so I reported it as such.

Re: TOS 5.1.123 (X86) is Released for Update

Posted: 10 May 2024, 19:34
by rmistry22
Hi all,
Did a complete wipe of all drives in my F5-421 as instructed by tech support.

Drives
1 - Toshiba 256Gb SSD (installed TOS OS on here)
2 - Ironwolf 6Tb - (RAID 5 Disk 1)
3 - Inonwolf 6Tb - (RAID 5 Disk 2)
4 - Ironwolf 6Tb - (RAID 5 Disk 3)
5 - Integral 1Tb SSD (will be used for Cache)

Everything seems to have gone OK, however few issues I have found.

1. Unable to create a network BOND. In TOS4, I had network ports 1,2,3 setup in a BOND. I don't seem to have the option anymore?
2. I don't seem to be able to add the SSD as a Cache drive / Hyperdrive (this maybe as the Synch is still in progress - very slow!)

Any help / input appreciated on how to resolve these issues

R

Re: TOS 5.1.123 (X86) is Released for Update

Posted: 11 May 2024, 00:08
by ColaChen
rmistry22 wrote: ↑10 May 2024, 19:34
For the BOND,can you explain in detail how it was organized? Which mode? Where are each network port connected?
All times are UTC+08:00
Page 5 of 5

Powered by phpBB® Forum Software © phpBB Limited