[Help] I have 2 F5-221 devices but only 1 will update to TOS7 [SOLVED]

[ChadH42]

I have 2 F5-221 NAS devices. I have successfully installed TOS7 on the older device but the newer one will not boot after attempting to install TOS7. I have opened up both units to see what differences there are and here is what I know so far:

Older NAS
1) Older unit has a sticker on the "motherboard" stating TM-J3355-2G2L V2.0 and another sticker with 000-F5221-FBA008-0001
2) Older unit has a MAPL0304V16 BIOS
3) Older unit has no additional RAM
4) Successfully upgraded to TOS7 392

Newer NAS
1) Newer unit has a sticker stating TM-J3355-2G2L V3.0 and another sticker with 000-F5221-FBA002-2000
2) Newer unit has a MAPL0304V22
3) New unit has a 2GB RAM chip installed for 8 months without issue
4) will not re-boot when upgrading to TOS7 392 (tried using both .ins and .bz2 methods over 10 times).

Any idea why the older one works and the newer one doesn't???

[Gremlin]

Why the repost?

[ChadH42]

Why the repost?

I was hoping for a TerraMaster support person to respond as I thought I may have originally posted in the wrong category.

[CursaYang]

Can the new NAS hear a beep sound when starting up? Normally, when powering on an empty machine, you will hear one self-test beep followed by three beeps.

[CursaYang]

As mentioned in the previous post, which image file did you use to create the boot system? When starting up, does the monitor display a prompt indicating 'boot from init'? Please confirm that your current boot order is set to TOS first.

[ChadH42]

As mentioned in the previous post, which image file did you use to create the boot system? When starting up, does the monitor display a prompt indicating 'boot from init'? Please confirm that your current boot order is set to TOS first.

Where do I do that? I installed a monitor and keyboard so I can see the boot & install process. The BIOS boot process list starts with Generic USB, then the last 3 of the 5 drives install then lastly P0 and P1. The boot always says "from INIT unless I select P0: manually on each restart of the system.

[EriChan]

Thanks for your detailed feedback and cooperation. Please try the following steps to help us accurately locate and resolve the issue:

• Start the new TNAS without installing any hard drives. Pay attention to whether there are three consecutive beeps within 1-3 minutes after the first beep.

• Check and compare the BIOS settings between the old and new NAS units, focusing on the following three options. If there are any differences, try to switch the new machine to the same mode as the old one:

Advanced -> SATA Configuration
Boot -> Boot Mode
CSM Support

[ChadH42]

Thanks for your detailed feedback and cooperation. Please try the following steps to help us accurately locate and resolve the issue:

• Start the new TNAS without installing any hard drives. Pay attention to whether there are three consecutive beeps within 1-3 minutes after the first beep.

• Check and compare the BIOS settings between the old and new NAS units, focusing on the following three options. If there are any differences, try to switch the new machine to the same mode as the old one:

Advanced -> SATA Configuration
Boot -> Boot Mode
CSM Support

the older NAS has BIOS V16 and does have CSM Support but the newer NAS has BIOS V22 and it does not list CSM in the BIOS settings. All SATA & Boot options and the same on both NAS'

[TMzethar]

The problem may be coming from the boot partition. You can connect an HDMI monitor before you boot NAS and see where it gets stuck after a restart or boot failure.

[ChadH42]

The problem may be coming from the boot partition. You can connect an HDMI monitor before you boot NAS and see where it gets stuck after a restart or boot failure.

I did this and the last step in the boot process is to execute a script called "UTOS-X86-S64" (see pictures.) On the failing NAS this script always branches to "Booting from INIT System". The working NAS branches to "Booting from RAID System"