I would speculate that this particular portion of users is very close to 100%!
TOS 5.1.123 (X86) is Released for Update
Re: TOS 5.1.123 (X86) is Released for Update
F2-220, TOS 5.1.123 (8GB system partition), Docker 2.0.16 (Nextcloud, AdGuard Home), Terra Photos 2.0.13
- astrolinux
- Posts: 2
- Joined: 04 Aug 2022, 23:31
Re: TOS 5.1.123 (X86) is Released for Update
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
Thank you
Re: TOS 5.1.123 (X86) is Released for Update
There is no other way, you need to back up the data and then format it.
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)
Technical team: support(at)terra-master.com (for technical support)
Service team: service(at)terra-master.com (for purchasing, return, replacement)
Re: TOS 5.1.123 (X86) is Released for Update
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.:
/var/log/crond.log:
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.
P.S. In /var/log/crond.log also a lot of strange logs with "exit status 1"
E.g.:
Code: Select all
*/5 * * * * docker exec -u www-data nextcloud-app-1 php cron.php
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
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
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.
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)
Support team: support(at)terra-master.com (for technical support only)
Service team: service(at)terra-master.com (for purchasing, return, replacement, RMA service)
-
- Posts: 17
- Joined: 15 Apr 2020, 08:15
Re: TOS 5.1.123 (X86) is Released for Update
Re: TOS 5.1.123 (X86) is Released for Update
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
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