TOS 7.0.1130 (x86) Official Release Update

[Pe6yc]

F5-422 (MAPL0304V22) + D8 Hybrid
Updated w/o visible problems

[rfbjr]

Look I think it's time to start ignoring the line " Fixed various other known issues". Everyone who has reported an issue re-tests the issue reported and almost always it's not fixed yet. I'm taking the approach if I don't see the specific issue called out, I'm not re-testing it.

Oh yeah all three devices updated w/o issues.

[sianderson]

both my units updated, no actual issues but i did notice that the F2-423 did not start my VM automatically it was showing as powered off (VMS APP) whereas the F2-424 did

both set to auto start and have always auto started in the past

[RyanYang]

9. Fixed various other known issues.

Despite that non-specific & wide casting bug fix, based on the responses of others, neither of the previously observed NTP issue & docker issues are fixed; will only install to a standalone TNAS that's not in testbed nor production use.

Regarding the structure of our update notes, we would like to clarify the following:

Any issues that have been reported to us by users and have been confirmed as fixed in this release are always listed individually and item by item in the first few sections of the update notes, so that everyone can quickly check whether the issues they care about have been resolved.

As for Item #9, "Fixed some other known issues," it covers only minor issues that were discovered during our internal testing or that occur only in very specific scenarios—issues that have not been previously reported by users. They are grouped together at the end solely to keep the announcement concise and readable.

[TMlinda]

Do you have any questions about this folder?
This folder contains an icon resource library used by the file manager module. It is used to display icons corresponding to different file types, folder status, mount protocols, encryption status, etc. in the web interface. Do not delete or modify it at will, otherwise icons will be missing or displayed abnormally in the web interface.And this folder will be updated with system or file manager updates.

[mab]

After the upgrade, an error that was already there since TOS7 is now worse:

Aug 12 07:16:45 TNAS kernel: [28922.668303] pcieport 0000:00:1c.6: AER: Correctable error message received from 0000:00:1c.6
Aug 12 07:16:45 TNAS kernel: [28922.668322] pcieport 0000:00:1c.6: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
Aug 12 07:16:45 TNAS kernel: [28922.668325] pcieport 0000:00:1c.6: device [8086:54be] error status/mask=00000001/00002000
Aug 12 07:16:45 TNAS kernel: [28922.668328] pcieport 0000:00:1c.6: [ 0] RxErr (First)

This is now flooding even more the /var/log/syslog constantly, and i have a constant systemd-journal at 40% cpu



for now i'm using the workaround in another post. won't make the problem disappear, but at least systemd-journal process goes back to idle cpu

printf '\x01\x20\x00\x00' | dd of=/sys/bus/pci/devices/0000:00:1c.6/config bs=1 seek=$((0x114)) count=4 2>/dev/null

Model is an F4-424

[nitzer71]

Update / confirmed workaround:

I found the cause of the NTP issue in /etc/ntp.conf.

The following line was configured:

Code: Select all

server 127.127.1.0 minpoll 6 maxpoll 10 iburst prefer

127.127.1.0 is LOCAL(0). With prefer enabled, ntpd consistently selected the local clock instead of the external NTP servers, even though they were reachable.

I removed only prefer:

Code: Select all

server 127.127.1.0 minpoll 6 maxpoll 10 iburst

After restarting NTP, an external NTP server was selected instead of LOCAL(0).

The fix also survived a complete NAS reboot and the NAS continued synchronizing with external NTP servers.

This appears to confirm that prefer on LOCAL(0) is causing the NTP synchronization problem in TOS 7.

Could TerraMaster please confirm whether this prefer setting is intentional and, if not, whether it will be corrected in a future TOS release?

Current workaround: remove prefer from the 127.127.1.0 entry in /etc/ntp.conf.

[snapsh0t]

smartd.service = smartmontools.service
Please execute the following command to re-enable smartd.service:

Code: Select all

systemctl enable smartmontools.init.service

Code: Select all

systemctl start smartmontools.init.service

Code: Select all

ln -s /etc/systemd/system/smartmontools.init.service /etc/systemd/system/smartd.service

Code: Select all

systemctl status smartd.service

Thank you, that worked. Unfortunately, the syslog still shows it's generating the false temperature reports and switching the drives between active and standby every 30 minutes. I have to admit I'm losing faith in the development team at this point.

[CursaYang]

The fix for this issue was not included in TOS version 7.0.1130 (x86). We will address this issue in a future release.

[Lex]

Do you have any questions about this folder?
This folder contains an icon resource library used by the file manager module. It is used to display icons corresponding to different file types, folder status, mount protocols, encryption status, etc. in the web interface. Do not delete or modify it at will, otherwise icons will be missing or displayed abnormally in the web interface.And this folder will be updated with system or file manager updates.

/usr/static/images/file_manager, this folder contains an icon resource library
/"usr/static/images/file_manager, this folder is empty. And it contains a strange symbol "