Scheduled Task Shutdown not working

[Gremlin]

Strangely enough, I have just experienced the same issue. {Note: my F2-424 is working perfectly in this regard}
Just acquired a replacement F2-221. It was a used, bare bones box. Created a new TOS5 legacy 120MB initboot usb.
Installed TOS5.1.145 -> TOS6.0.530 update -> TOS6.0.610 update.
Last night machine did not shutdown on schedule. Browser desktop was running but frozen. Monitor was frozen (apparently).
Performed Ctrl+alt+del on monitor keyboard and system initiated system restart. It was late so had to resort to power off.
As expected (sort of, but I had hope ) system would not start-up this morning. Lost network settings and ip could not be reset
via TNAS-PC.
Did a complete (custom) re-install of TOS6.0.610 direct. (No data to lose). Reset power schedule (amongst usual stuff).
Power shutdown did not function at set time (11:00) {No user logged in}

Should the initboot USB be changed for uefi (126MB) version now that TOS6 is installed. Anything in BIOS to change (reset to optimised defaults)

NB: BIOS is 5.12-MAPL0304V22 from 23/03/2022

[TMtina]

Strangely enough, I have just experienced the same issue. {Note: my F2-424 is working perfectly in this regard}
Just acquired a replacement F2-221. It was a used, bare bones box. Created a new TOS5 legacy 120MB initboot usb.
Installed TOS5.1.145 -> TOS6.0.530 update -> TOS6.0.610 update.
Last night machine did not shutdown on schedule. Browser desktop was running but frozen. Monitor was frozen (apparently).
Performed Ctrl+alt+del on monitor keyboard and system initiated system restart. It was late so had to resort to power off.
As expected (sort of, but I had hope ) system would not start-up this morning. Lost network settings and ip could not be reset
via TNAS-PC.
Did a complete (custom) re-install of TOS6.0.610 direct. (No data to lose). Reset power schedule (amongst usual stuff).
Power shutdown did not function at set time (11:00) {No user logged in}

Should the initboot USB be changed for uefi (126MB) version now that TOS6 is installed. Anything in BIOS to change (reset to optimised defaults)

NB: BIOS is 5.12-MAPL0304V22 from 23/03/2022

When you upgrade from TOS 5 to TOS 6, the USB Initboot will also be updated simultaneously to a version compatible with TOS 6. If you need to reinstall the system, TOS 6 will be installed by default. You do not need to change the USB Initboot or BIOS settings.

[Gremlin]

I hear what you say and, indeed, I thought that would be the case (for usb). However, after the initial update to 6.0.610 as described, I went back and replaced the disks (one had a known 'fault') and then used the 'default' install. It installed 5.1.145 again much to my surprise.

I'll let you work that one out

I am using this unit to try and verify that upgrades do, in fact, work prior to looking at my F5-221.
I take it you have no comment on the failure of auto shutdown.

[TMzethar]

We are still investigating the issue of abnormal scheduled power on/off.
Regarding your failure to upgrade the USB boot drive to the TOS6 dedicated version when upgrading from TOS5 to TOS6, this is a rare occurrence, and we will continue to monitor it.

[FredMutter]

We are still investigating the issue of abnormal scheduled power on/off.

super.
For me it happened 2 weeks ago when I installed a new container (pi-hole).
But as I wrote when docker is down my f2-424 still doesn't want to shutdown

[TMzethar]

super.
For me it happened 2 weeks ago when I installed a new container (pi-hole).
But as I wrote when docker is down my f2-424 still doesn't want to shutdown

Thank you for your feedback.
We have not yet found any correlation between it and Docker.

[Gremlin]

We are still investigating the issue of abnormal scheduled power on/off.
Regarding your failure to upgrade the USB boot drive to the TOS6 dedicated version when upgrading from TOS5 to TOS6, this is a rare occurrence, and we will continue to monitor it.

Follow up:
After 2 further re-installations (for various reasons not directly relevant), I can now confirm that the USB finally defaulted to TOS6 (latest version).

Probably unconnected, but I did observe during boot a reference (via monitor) to GPT error something along lines of "Alternate GPT not at end of disk" (hard to catch). "Use GNU Parted to (fix?)"

Edit: Output from Dmesg:

Code: Select all

[    8.784817] GPT:Primary header thinks Alt. header is not at the end of the disk.
[    8.784938] GPT:245759 != 7864319
[    8.785019] GPT:Alternate GPT header not at the end of the disk.
[    8.785105] GPT:245759 != 7864319
[    8.785217] GPT: Use GNU Parted to correct GPT errors.

Today the unit did power-up on schedule (I reset data after re-installation). I will have to observe if power-off functions in due course.

[Gremlin]

Power-off last night and power-on this morning a success.

[FredMutter]

Power-off last night and power-on this morning a success.

you're lucky.
Still doesn't work for me
I noticed the following errors:

[ 0.248206] ACPI Error: Aborting method \_SB.PC00.XHCI.RHUB.HS01._PLD due to previous error (AE_NOT_FOUND) (20220331/psparse-529)
[ 0.248236] ACPI Error: Aborting method \_SB.PC00.XHCI.RHUB.HS02._PLD due to previous error (AE_NOT_FOUND) (20220331/psparse-529)
[ 0.681568] ACPI Error: Aborting method \_SB.PC00.XHCI.RHUB.HS01._PLD due to previous error (AE_NOT_FOUND) (20220331/psparse-529)
[ 0.681586] ACPI Error: Aborting method \_SB.PC00.XHCI.RHUB.HS01._PLD due to previous error (AE_NOT_FOUND) (20220331/psparse-529)
[ 0.681604] ACPI Error: Aborting method \_SB.PC00.XHCI.RHUB.HS02._PLD due to previous error (AE_NOT_FOUND) (20220331/psparse-529)
[ 0.681618] ACPI Error: Aborting method \_SB.PC00.XHCI.RHUB.HS02._PLD due to previous error (AE_NOT_FOUND) (20220331/psparse-529)
[ 0.694455] platform regulatory.0: Direct firmware load for regulatory.db failed with error -2
[ 50.231818] r8169 0000:01:00.0: Direct firmware load for rtl_nic/rtl8125b-2.fw failed with error -2
[ 50.365470] r8169 0000:02:00.0: Direct firmware load for rtl_nic/rtl8125b-2.fw failed with error -2

[FredMutter]

After a little analysis I think these errors are not related to my problem