TOS 6.0.460 (X86) Beta is Released for Update

[crisisacting]

How do we determine the manufacturing date?

It's within the device's serial number. The first two numbers after the second hyphen is the year, the next two are the week. Yours would need to be 2025 or higher to not be effected by the limitation

[alpro]

My NAS also stopped working after the last update. HDD constantly goes into sleep mode after loading TOS and NAS cannot boot correctly.

[TMzethar]

My NAS also stopped working after the last update. HDD constantly goes into sleep mode after loading TOS and NAS cannot boot correctly.

Could you please add some basic information:.
TNAS model?
TOS version before update?

After the problem occurs, you can try to connect the HDMI and observe what it shows.

[tanktarta]

Since updating to 4.0.461 I have several docker containers that seem to be stuck in a restarting loop. A container will appear to start, but at some point less than a minute after doing so it will restart. The are no log events I can see in the web user interface.

I also have a couple that are absolutely fine. The same thing happens on any new containers I might add too (I tried several).

The only evidence of what is happening I could find is in /var/log/message. There are several things that look like they are maybe errors here, but all I can tell from this is that it looks like something network related.

Code: Select all

Sep  5 10:14:03 terra kernel: [33709.508156] docker0: port 1(veth525fcc3) entered blocking state
Sep  5 10:14:03 terra kernel: [33709.508160] docker0: port 1(veth525fcc3) entered disabled state
Sep  5 10:14:03 terra kernel: [33709.508251] device veth525fcc3 entered promiscuous mode
Sep  5 10:14:03 terra nasips[8757]: 2024/09/05 10:14:03 INFO Skip virtual device com=toDesiredState link=vethf22baba
Sep  5 10:14:03 terra nasips[8757]: 2024/09/05 10:14:03 INFO Skip virtual device com=toDesiredState link=veth525fcc3
Sep  5 10:14:03 terra nasips[8757]: message repeated 3 times: [ 2024/09/05 10:14:03 INFO Skip virtual device com=toDesiredState link=veth525fcc3]
Sep  5 10:14:03 terra NetworkManager[1523]: <info>  [1725527643.6800] manager: (vethf22baba): new Veth device (/org/freedesktop/NetworkManager/Devices/307)
Sep  5 10:14:03 terra NetworkManager[1523]: <info>  [1725527643.6810] manager: (veth525fcc3): new Veth device (/org/freedesktop/NetworkManager/Devices/308)
Sep  5 10:14:03 terra systemd[1]: Unnecessary job was removed for /sys/subsystem/net/devices/vethf22baba.
Sep  5 10:14:03 terra systemd[1]: Started Netscript ifup for vethf22baba.
Sep  5 10:14:03 terra systemd[1]: Stopping Netscript ifup for vethf22baba...
Sep  5 10:14:03 terra sh[360242]:   netscript: you must be root to run this command.
Sep  5 10:14:03 terra netscript[360243]:   netscript: you must be root to run this command.
Sep  5 10:14:03 terra systemd[1]: [email protected]: Main process exited, code=exited, status=1/FAILURE
Sep  5 10:14:03 terra systemd[1]: [email protected]: Control process exited, code=exited, status=1/FAILURE
Sep  5 10:14:03 terra systemd[1]: [email protected]: Failed with result 'exit-code'.
Sep  5 10:14:03 terra systemd[1]: Stopped Netscript ifup for vethf22baba.
Sep  5 10:14:03 terra systemd[1]: run-docker-runtime\x2drunc-moby-8bb5856230c9c2a54b5bffe8072a4a478bca9dba1c9ee6cbeab06f02a4522f8c-runc.VAoRPj.mount: Deactivated successfully.
Sep  5 10:14:03 terra systemd[1]: Started libcontainer container 8bb5856230c9c2a54b5bffe8072a4a478bca9dba1c9ee6cbeab06f02a4522f8c.
Sep  5 10:14:03 terra nasips[8757]: 2024/09/05 10:14:03 INFO Skip virtual device com=toDesiredState link=vethf22baba
Sep  5 10:14:03 terra kernel: [33709.680601] eth0: renamed from vethf22baba
Sep  5 10:14:03 terra nasips[8757]: 2024/09/05 10:14:03 INFO Skip virtual device com=toDesiredState link=veth525fcc3
Sep  5 10:14:03 terra kernel: [33709.687329] IPv6: ADDRCONF(NETDEV_CHANGE): veth525fcc3: link becomes ready
Sep  5 10:14:03 terra kernel: [33709.687363] docker0: port 1(veth525fcc3) entered blocking state
Sep  5 10:14:03 terra kernel: [33709.687366] docker0: port 1(veth525fcc3) entered forwarding state
Sep  5 10:14:03 terra NetworkManager[1523]: <info>  [1725527643.8584] device (veth525fcc3): carrier: link connected
Sep  5 10:14:03 terra systemd[1]: docker-8bb5856230c9c2a54b5bffe8072a4a478bca9dba1c9ee6cbeab06f02a4522f8c.scope: Deactivated successfully.
Sep  5 10:14:03 terra kernel: [33709.757293] docker0: port 1(veth525fcc3) entered disabled state
Sep  5 10:14:03 terra kernel: [33709.757434] vethf22baba: renamed from eth0
Sep  5 10:14:03 terra nasips[8757]: 2024/09/05 10:14:03 INFO Skip virtual device com=toDesiredState link=veth525fcc3
Sep  5 10:14:03 terra nasips[8757]: 2024/09/05 10:14:03 INFO Skip virtual device com=toDesiredState link=vethf22baba
Sep  5 10:14:03 terra NetworkManager[1523]: <info>  [1725527643.9435] manager: (vethf22baba): new Veth device (/org/freedesktop/NetworkManager/Devices/309)
Sep  5 10:14:03 terra nasips[8757]: 2024/09/05 10:14:03 INFO Skip virtual device com=toDesiredState link=veth525fcc3
Sep  5 10:14:03 terra kernel: [33709.783895] docker0: port 1(veth525fcc3) entered disabled state
Sep  5 10:14:03 terra kernel: [33709.784282] device veth525fcc3 left promiscuous mode
Sep  5 10:14:03 terra kernel: [33709.784285] docker0: port 1(veth525fcc3) entered disabled state
Sep  5 10:14:03 terra nasips[8757]: 2024/09/05 10:14:03 ERROR LinkIsNil event=addrchange err="Link not found"
Sep  5 10:14:03 terra nasips[8757]: 2024/09/05 10:14:03 INFO Skip virtual device com=toDesiredState link=vethf22baba
Sep  5 10:14:03 terra nasips[8757]: 2024/09/05 10:14:03 INFO Skip virtual device com=toDesiredState link=veth525fcc3
Sep  5 10:14:03 terra NetworkManager[1523]: <info>  [1725527643.9564] device (veth525fcc3): released from master device docker0
Sep  5 10:14:03 terra systemd[1]: Unnecessary job was removed for /sys/subsystem/net/devices/vethf22baba.
Sep  5 10:14:03 terra systemd[1]: Started Netscript ifup for vethf22baba.
Sep  5 10:14:03 terra systemd[1]: Stopping Netscript ifup for vethf22baba...
Sep  5 10:14:03 terra sh[360381]:   netscript: you must be root to run this command.
Sep  5 10:14:03 terra systemd[1]: [email protected]: Main process exited, code=exited, status=1/FAILURE
Sep  5 10:14:03 terra netscript[360384]:   netscript: you must be root to run this command.
Sep  5 10:14:03 terra systemd[1]: [email protected]: Control process exited, code=exited, status=1/FAILURE
Sep  5 10:14:03 terra systemd[1]: [email protected]: Failed with result 'exit-code'.
Sep  5 10:14:03 terra systemd[1]: Stopped Netscript ifup for vethf22baba.
Sep  5 10:14:03 terra systemd[1]: run-docker-netns-2f7cbad6361c.mount: Deactivated successfully.
Sep  5 10:14:09 terra msgcenter[2364]: |---[message] 192.168.91.4, runtime: 40m7.335455285s, receive: ping

[TMzethar]

We found the situation you mentioned during the validation process and will be investigating this issue in depth.

[alpro]

My NAS also stopped working after the last update. HDD constantly goes into sleep mode after loading TOS and NAS cannot boot correctly.

Could you please add some basic information:.
TNAS model?
TOS version before update?

After the problem occurs, you can try to connect the HDMI and observe what it shows.

F2-424
TOS 6.0.460
on HDMI in log: ata1.0 exception emask... and next line something about sleep mode every 1-2 sec.
HDD constantly parked the heads, then spun up and everything was repeated
TOS was installed on HDD and SSD, booting from HDD. Accordingly, now nginx does not start (error in the logs), both described ways to reset the system do not work, I can only connect to the NAS via ssh with HDD disabled
Connected HDD to another computer, mdadm + lvm2 helped to see files, the disk works fine

[AlexanderSO]

My NAS also stopped working after the last update. HDD constantly goes into sleep mode after loading TOS and NAS cannot boot correctly.

Could you please add some basic information:.
TNAS model?
TOS version before update?

After the problem occurs, you can try to connect the HDMI and observe what it shows.

F2-424
TOS 6.0.460
on HDMI in log: ata1.0 exception emask... and next line something about sleep mode every 1-2 sec.
HDD constantly parked the heads, then spun up and everything was repeated
TOS was installed on HDD and SSD, booting from HDD. Accordingly, now nginx does not start (error in the logs), both described ways to reset the system do not work, I can only connect to the NAS via ssh with HDD disabled
Connected HDD to another computer, mdadm + lvm2 helped to see files, the disk works fine

В английском не силён, пишу как могу
Похожая проблема с постоянным засыпанием дисков случилась после обновления на "безвозвратную" версию TOS 6, точный номер не помню. При установке в настройках питания времени засыпания дисков в положение "никогда" диски отключались мгновенно, и никогда не просыпались. Были непрекращающиеся циклы старт-стоп. Соответственно система была крайне не отзывчивой, если можно так выразиться Установка любого другого временного интервала на сон дисков работает корректно. А режим "никогда" мне был нужен при проведении длинного SMART-теста, что бы он не был "прерван хостом". Сообщение в ТМ было отправлено, проблема подтвердилась, обещали устранить.

[alpro]

Could you please add some basic information:.
TNAS model?
TOS version before update?

After the problem occurs, you can try to connect the HDMI and observe what it shows.

F2-424
TOS 6.0.460
on HDMI in log: ata1.0 exception emask... and next line something about sleep mode every 1-2 sec.
HDD constantly parked the heads, then spun up and everything was repeated
TOS was installed on HDD and SSD, booting from HDD. Accordingly, now nginx does not start (error in the logs), both described ways to reset the system do not work, I can only connect to the NAS via ssh with HDD disabled
Connected HDD to another computer, mdadm + lvm2 helped to see files, the disk works fine

В английском не силён, пишу как могу
Похожая проблема с постоянным засыпанием дисков случилась после обновления на "безвозвратную" версию TOS 6, точный номер не помню. При установке в настройках питания времени засыпания дисков в положение "никогда" диски отключались мгновенно, и никогда не просыпались. Были непрекращающиеся циклы старт-стоп. Соответственно система была крайне не отзывчивой, если можно так выразиться Установка любого другого временного интервала на сон дисков работает корректно. А режим "никогда" мне был нужен при проведении длинного SMART-теста, что бы он не был "прерван хостом". Сообщение в ТМ было отправлено, проблема подтвердилась, обещали устранить.

Да, сценарий именно такой, отключил засыпание дисков. К сожалению вернуть уже невозможно, видимо придется ставить ubuntu и настраивать все руками, т.к. не нашел способа сбросить настройки TOS через терминал.

[alpro]

My NAS also stopped working after the last update. HDD constantly goes into sleep mode after loading TOS and NAS cannot boot correctly.

Could you please add some basic information:.
TNAS model?
TOS version before update?

After the problem occurs, you can try to connect the HDMI and observe what it shows.

F2-424
TOS 6.0.460
on HDMI in log: ata1.0 exception emask... and next line something about sleep mode every 1-2 sec.
HDD constantly parked the heads, then spun up and everything was repeated
TOS was installed on HDD and SSD, booting from HDD. Accordingly, now nginx does not start (error in the logs), both described ways to reset the system do not work, I can only connect to the NAS via ssh with HDD disabled
Connected HDD to another computer, mdadm + lvm2 helped to see files, the disk works fine

in log:
Sep 6 09:31:09 TNAS kernel: [ 147.547122] ata1.00: exception Emask 0x0 SAct 0x4 SErr 0x0 action 0x6
Sep 6 09:31:09 TNAS kernel: [ 147.547170] ata1.00: waking up from sleep
Sep 6 09:31:09 TNAS kernel: [ 147.547180] ata1: hard resetting link
Sep 6 09:31:10 TNAS kernel: [ 147.853341] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Sep 6 09:31:10 TNAS kernel: [ 147.883695] ata1.00: configured for UDMA/133
Sep 6 09:31:10 TNAS kernel: [ 147.883727] ata1: EH complete
The problem occurred after setting the "never turn off drives" option in the power settings
How can I disable this option through the terminal?

[AlexanderSO]

F2-424
TOS 6.0.460
on HDMI in log: ata1.0 exception emask... and next line something about sleep mode every 1-2 sec.
HDD constantly parked the heads, then spun up and everything was repeated
TOS was installed on HDD and SSD, booting from HDD. Accordingly, now nginx does not start (error in the logs), both described ways to reset the system do not work, I can only connect to the NAS via ssh with HDD disabled
Connected HDD to another computer, mdadm + lvm2 helped to see files, the disk works fine

В английском не силён, пишу как могу
Похожая проблема с постоянным засыпанием дисков случилась после обновления на "безвозвратную" версию TOS 6, точный номер не помню. При установке в настройках питания времени засыпания дисков в положение "никогда" диски отключались мгновенно, и никогда не просыпались. Были непрекращающиеся циклы старт-стоп. Соответственно система была крайне не отзывчивой, если можно так выразиться Установка любого другого временного интервала на сон дисков работает корректно. А режим "никогда" мне был нужен при проведении длинного SMART-теста, что бы он не был "прерван хостом". Сообщение в ТМ было отправлено, проблема подтвердилась, обещали устранить.

Да, сценарий именно такой, отключил засыпание дисков. К сожалению вернуть уже невозможно, видимо придется ставить ubuntu и настраивать все руками, т.к. не нашел способа сбросить настройки TOS через терминал.

Меня спасло то, что система была на HDD и SSD. Удалось запустить без HDD и поменять настройку сна дисков. После этого TOS, с помощью mdadm и fdisk, был полностью изгнан с HDD и остался только на SSD. Если не ошибаюсь, версия была 436. После обновления до 460, система осталась только на SSD. Продолжаю наблюдение. Пока данное вмешательство в системные рейды негативных последствий не выявило. 2xSSD в RAID1, 3xHDD в TRAID.