[Help] Every night I turn off the NAS I find it on in the morning; after FW update [SOLVED]

[chrisloughnane]

Model: F5-221
TOS version: TOS_X642.0_6.0.694

I have exhausted all obvious reasons that is causing the NAS to boot up on its own. I've unplugged the LAN and it still boots up and I've checked auto-power, scheduled jobs etc. and I've run out of ideas.

This only started after I updated firmware to TOS_X642.0_6.0.694.

Has anyone else had this issue?

[Gremlin]

and I still cannot get mine to turn on on schedule ......

[OrionXie]

I apologize for the poor experience you've had. Please note whether the device automatically turns on after midnight.
You can try turning off the power-on self-test feature in your device's BIOS and then observe if the issue persists.
If it still does, please contact technical support via email at [email protected], providing them with a system report for analysis. (TOS Desktop > Technical Support > Report Issue)，Thank you for your understanding.

[chrisloughnane]

I apologize for the poor experience you've had. Please note whether the device automatically turns on after midnight.
You can try turning off the power-on self-test feature in your device's BIOS and then observe if the issue persists.
If it still does, please contact technical support via email at [email protected], providing them with a system report for analysis. (TOS Desktop > Technical Support > Report Issue)，Thank you for your understanding.

I have gone through all BIOS menus, twice, and I cannot find the power-on self-test feature in your device's BIOS, could you please point the way?

[TMjack]

Hello!
I would like to learn more about the auto-start behavior of the F5-221 device: Does this auto-start phenomenon occur regularly at a fixed time point (00:00:00), or does it happen randomly at irregular intervals? Additionally, was the auto-start issue never observed on the F5-221 when running versions prior to TOS 6.0.694? Furthermore, could you kindly provide the BIOS version information for this device? We will attempt to reproduce the issue internally to verify whether the phenomenon can be replicated.

[chrisloughnane]

@TMjack as requested, unfortunately this board does not support BBCode Table.

Does this auto-start phenomenon occur regularly at a fixed time point (00:00:00), or does it happen randomly at irregular intervals?

- I only "caught" the NAS booting once at exactly 01:00:00, with summer time that would be your sugested time of 00:00:00

Additionally, was the auto-start issue never observed on the F5-221 when running versions prior to TOS 6.0.694?

- No, I never had this issue before TOS 6.0.694.

F5-221

• Current TOS version - 6.0.694-00165

• BIOS/initBoot version - MAPL0304V17

BIOS Information

• BIOS Vendor - American Megatrends

• Core Version - 5.12

• Compliancy - UEFI 2.5; PI 1.4

• Product Name - TM-J3355-2G2L

• BIOS Version - MAPL0304V17

• Build Date and Time - 07/27/2020 16:53:07

• Access Level - Administrator

Platform firmware Information

• BXT SOC - B1

• MRC Version - 0.56

• PUNIT FW - 3C

• PMC FW - 03.33

• TXE FW - 3.1.75.2351

• ISH FW - N/A

• GOP - 0.0.0036

• CPU Flavor - BXT Notebook/Desktop . . .

• Board ID - APL RVP 1A (01)

• Fab ID - FAB1

Memory Information

• Total Memory - 2048 MB

• Memory Speed - 1600 MHz

[CursaYang]

@TMjack as requested, unfortunately this board does not support BBCode Table.

Does this auto-start phenomenon occur regularly at a fixed time point (00:00:00), or does it happen randomly at irregular intervals?

- I only "caught" the NAS booting once at exactly 01:00:00, with summer time that would be your sugested time of 00:00:00

Additionally, was the auto-start issue never observed on the F5-221 when running versions prior to TOS 6.0.694?

- No, I never had this issue before TOS 6.0.694.

F5-221

• Current TOS version - 6.0.694-00165

• BIOS/initBoot version - MAPL0304V17

BIOS Information

• BIOS Vendor - American Megatrends

• Core Version - 5.12

• Compliancy - UEFI 2.5; PI 1.4

• Product Name - TM-J3355-2G2L

• BIOS Version - MAPL0304V17

• Build Date and Time - 07/27/2020 16:53:07

• Access Level - Administrator

Platform firmware Information

• BXT SOC - B1

• MRC Version - 0.56

• PUNIT FW - 3C

• PMC FW - 03.33

• TXE FW - 3.1.75.2351

• ISH FW - N/A

• GOP - 0.0.0036

• CPU Flavor - BXT Notebook/Desktop . . .

• Board ID - APL RVP 1A (01)

• Fab ID - FAB1

Memory Information

• Total Memory - 2048 MB

• Memory Speed - 1600 MHz

Please contact our support email, and we will send you the method for BIOS upgrade. Please attach the link to this post in your email.

[chrisloughnane]

After shutting down last night the next system log starts with a timestamp close to 01:00:00

Code: Select all

Jul  1 01:03:18 pod2 kernel: [    0.000000] Linux version 6.1.120+ (root@3b5a155ad7ad) (x86_64-tnas-linux-gnu-gcc.br_real (Buildroot 2023.08.1) 13.2.0, GNU ld (GNU Binutils) 2.40) #21 SMP PREEMPT_DYNAMIC Thu Apr  3 16:53:04 CST 2025
Jul  1 01:03:18 pod2 kernel: [    0.000000] Command line: BOOT_IMAGE=/boot/bzImage type=raid hpet=disable security=
Jul  1 01:03:18 pod2 kernel: [    0.000000] BIOS-provided physical RAM map:
Jul  1 01:03:18 pod2 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000000000-0x0000000000097bff] usable

I will now contact support as suggested.

[CursaYang]

The relevant BIOS upgrade method has been sent; please check your email.
After the upgrade, observe whether it still automatically starts.

[chrisloughnane]

Hi @CursaYang,

Yes, I got the email thank you.

I read through the instructions but it's a bit of a black box you've sent me.

First line in doc:

1. Please unplug all HDDs and USB disks connected to the TNAS, including the USB boot system disk on the motherboard, which requires you to disassemble the TNAS to take it out.

Could you please forward a link to the instructions or video on what I should expect in here? I have not opened this NAS before and do not know what the "USB boot system disk" looks like. From later in your instructions am I to assume it literally looks like a standard USB key?

Also there is no version/date info on in the doc or readme. Could you please let me know these details for trouble shooting?