Release Notes for x86 Series TOS Update!

[TMzethar]

Thanks, for the replay,
but why but is stuck from TOS 5.1.24 to TOS 5.1.145 uploading the software package... 83%

Please see the screenshot posted.

This is likely due to the small partition capacity of your system, which may not be able to receive larger upgrade packages
You can consider reinstalling directly to the latest TOS 5.1.145.

[Dennis_H]

I have an F2-221 running TOS 4.2.44 with 10 GB RAM.
SN is S/N-A1T200101164
How far can I go for an upgrade? Will it go to TOS 6?
Want to run Jellyfin, but see no support pre TOS 5. Docker has cert error, so can't grab container.
Data is backed up to USB HD. Will I have to wipe everything?

[crisisacting]

have an F2-221 running TOS 4.2.44 with 10 GB RAM.
SN is S/N-A1T200101164
How far can it go for an upgrade? Will it go to TOS 6?

It can go to the current TOS 7 betas if its UEFI BIOS is up to date to support it; based on that serial number, it's manufactured in early 2020, so it might already be on a compatible BIOS revision (connect an HDMI display & load into BIOS to check or might be able to check the BIOS version by going to TOS Control Panel > System > Update > BIOS/InitBoot) for TOS 6.× & all you'd need to do is update or possibly replace the initboot USB drive @ viewtopic.php?t=6433

Want to run Jellyfin, but see no support pre TOS 5. Docker has cert error, so can't grab container.
Data is backed up to USB HD. Will I have to wipe everything?

It's best to have a fresh start for all the partitions to be set-up (a larger 8 GB system partition is necessary for newer TOS builds), since you have a backup & could restore it after you've reconfigured it to closely match your previous TOS setup (if you'd like the TNAS to be accessible by whichever existing connected devices you have).

You'd need to secure erase your existing drives (on another device unless you're willing/technically capable to boot into a temporary live Linux environment on your TNAS to do so) if you'd like to reuse them with the newer TOS builds.

[Dennis_H]

Moved question to another thread... viewtopic.php?p=55151#p55151

Thank you for the info. So if I get a 16GB flash drive, flash the USB Initboot Image (TOS 6 Legacy 126MB), pull the drives, it will then be on TOS 6? Re-init the drives on my PC, add them back (using JBOD), restore all the data, and I should be running 6.0 correctly? May be the best way to do a fresh install. Currently running Plex but wanted to go Jellyfin and can't load it natively or on docker due to some weird docker certificate issues that seem to not be resolved.

I saw the update all these different versions one at a time routine, but wasn't sure if that worked based on my current bios, or if it retains data. I'll try to see what the version is, but how do I know whether that works if I find the version?

Edit: Hooked up monitor and boot screen shows American Megatrends
Version 2.18.1263 Copyright 2020...
BIOS Date 07/27/2020 16:53:07 Ver MAPL0304V17

did the lsblk and df -h commands also. Does this tell anything about whether it can go to TOS 6 with new initboot image, or is that BIOS controlled? Can BIOS be updated or just bootimage?

[xxx@TNAS-xxxA ~]$ lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 9.1T 0 disk
|-sda1 8:1 0 285M 0 part
|-sda2 8:2 0 1.9G 0 part
| `-md9 9:9 0 1.9G 0 raid1 /
|-sda3 8:3 0 977M 0 part
| `-md8 9:8 0 976.4M 0 raid1 [SWAP]
`-sda4 8:4 0 9.1T 0 part
`-md0 9:0 0 18.2T 0 linear
`-vg0-lv0 252:0 0 18.2T 0 lvm /mnt/md0
sdb 8:16 0 9.1T 0 disk
|-sdb1 8:17 0 285M 0 part
|-sdb2 8:18 0 1.9G 0 part
| `-md9 9:9 0 1.9G 0 raid1 /
|-sdb3 8:19 0 977M 0 part
| `-md8 9:8 0 976.4M 0 raid1 [SWAP]
`-sdb4 8:20 0 9.1T 0 part
`-md0 9:0 0 18.2T 0 linear
`-vg0-lv0 252:0 0 18.2T 0 lvm /mnt/md0
sdc 8:32 0 10.9T 0 disk
`-sdc1 8:33 0 10.9T 0 part /mnt/usb/usbshare1

[xxx@TNAS-xxxA ~]$ df -h
Filesystem Size Used Available Use% Mounted on
/dev/md9 1.8G 747.1M 1.0G 42% /
devtmpfs 4.8G 0 4.8G 0% /dev
tmpfs 4.8G 4.0K 4.8G 0% /dev/shm
tmpfs 4.8G 6.0M 4.8G 0% /tmp
tmpfs 4.8G 224.0K 4.8G 0% /run
tmpfs 4.8G 5.2M 4.8G 0% /opt/var
/dev/mapper/vg0-lv0 18.2T 9.2T 9.0T 51% /mnt/md0
/dev/mapper/vg0-lv0 18.2T 9.2T 9.0T 51% /home
/dev/sdc1 10.9T 6.4T 4.5T 59% /mnt/usb/usbshare1

[crisisacting]

… So get a 16GB flash drive, flash the USB Initboot Image (TOS 6 Legacy 126MB), pull the drives, it will then be on TOS 6? Re-init the drives on my PC, add them back (using JBOD), restore all the data, and I should be running 6.0 correctly?

With the newer initboot drive for TOS 6, it should install the latest 6.× release build if you don't use the custom option (using a .ins).

…

Edit: Hooked up monitor and boot screen shows American Megatrends
Version 2.18.1263 Copyright 2020...
BIOS Date 07/27/2020 16:53:07 Ver MAPL0304V17

did the lsblk and df -h commands also:

[xxx@TNAS-xxxA ~]$ lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 9.1T 0 disk
|-sda1 8:1 0 285M 0 part
|-sda2 8:2 0 1.9G 0 part
| `-md9 9:9 0 1.9G 0 raid1 /
|-sda3 8:3 0 977M 0 part
| `-md8 9:8 0 976.4M 0 raid1 [SWAP]
`-sda4 8:4 0 9.1T 0 part
`-md0 9:0 0 18.2T 0 linear
`-vg0-lv0 252:0 0 18.2T 0 lvm /mnt/md0
sdb 8:16 0 9.1T 0 disk
|-sdb1 8:17 0 285M 0 part
|-sdb2 8:18 0 1.9G 0 part
| `-md9 9:9 0 1.9G 0 raid1 /
|-sdb3 8:19 0 977M 0 part
| `-md8 9:8 0 976.4M 0 raid1 [SWAP]
`-sdb4 8:20 0 9.1T 0 part
`-md0 9:0 0 18.2T 0 linear
`-vg0-lv0 252:0 0 18.2T 0 lvm /mnt/md0
sdc 8:32 0 10.9T 0 disk
`-sdc1 8:33 0 10.9T 0 part /mnt/usb/usbshare1

[xxx@TNAS-xxxA ~]$ df -h
Filesystem Size Used Available Use% Mounted on
/dev/md9 1.8G 747.1M 1.0G 42% /
devtmpfs 4.8G 0 4.8G 0% /dev
tmpfs 4.8G 4.0K 4.8G 0% /dev/shm
tmpfs 4.8G 6.0M 4.8G 0% /tmp
tmpfs 4.8G 224.0K 4.8G 0% /run
tmpfs 4.8G 5.2M 4.8G 0% /opt/var
/dev/mapper/vg0-lv0 18.2T 9.2T 9.0T 51% /mnt/md0
/dev/mapper/vg0-lv0 18.2T 9.2T 9.0T 51% /home
/dev/sdc1 10.9T 6.4T 4.5T 59% /mnt/usb/usbshare1

Does this tell anything about whether it can go to TOS 6 with new initboot image, or is that BIOS controlled? Can BIOS be updated or just bootimage?

There's no 7.9 GB partition within that list, so not the updated setup. A fresh install is necessary to move to TOS 6+.

Based on this info, V17 is good for TOS 6.× & possibly 7.× builds.

If you'd like to update (as it could be on your build), here is V22, which was posted in a previous TOS 6 release build thread @ viewtopic.php?p=42997#p42997 [the first page of thread mentioned the BIOS revision minimums for that build & it generally still applies for newer builds as well):

Code: Select all

https://download2.terra-master.com/MAPL0304V22.zip

(update at your own risk)

[Dennis_H]

Is there really any reason to go to V22 since V17 is supported? Considering getting new bigger drives when I do the update and use the current ones in my D8 unit. Not the best time to look at drives though...

[Phil]

Is there really any reason to go to V22 since V17 is supported? Considering getting new bigger drives when I do the update and use the current ones in my D8 unit. Not the best time to look at drives though...

The BIOS version V17 is currently running stably and can meet your current usage needs, so there is no need to upgrade to version V22.
The method for upgrading to TOS6 has been explained in another post; please refer to this link: viewtopic.php?t=6809&start=300

[betuning]

Hello, I have an F5-221 with 10GB of RAM, running BIOS 5.12 and TOS 5.1.145, which I want to upgrade to TOS 6.
System partition 7,41 gb

Can I flash the BIOS to a more recent version?

PS: I can completely reset it since I'm upgrading to an F4-425 Plus, but I'd like to use the F5-221 as a backup.

[TMzethar]

Hello, I have an F5-221 with 10GB of RAM, running BIOS 5.12 and TOS 5.1.145, which I want to upgrade to TOS 6.
System partition 7,41 gb
Can I flash the BIOS to a more recent version?
PS: I can completely reset it since I'm upgrading to an F4-425 Plus, but I'd like to use the F5-221 as a backup.

Sorry, BIOS 5.12 is not compatible with TOS6, and this BIOS version cannot be updated to a higher version.

[Cafsenra]

This is really bad news. I also have bios version 5.12 in f2-221 and I am stuck in TOS 5.1.144. Is there any chance in the future this upgrade will be supported? I do not like to be an unlucky consumer. I suggest if you do not provide an software upgrade path then offer a trade program for the hardware.