Does not meet the conditions for updating the TOS 5.1?

[Gremlin]

I am very concerned I have again to backup and erase all my disks, which I did already for TOS5 !

Could you clarify? Are you saying you already deleted ALL partitions from your drives and directly installed 5.1.nnn but you STILL have 2GB system partition? This does not sound normal. Did you install 5.1.nnn with the '.ins' installation file via 'Custom' installation route? Or something else?

[Cis]

I had a clean install done last year for reaching TOS 5x, so I was surprised still not having more than 2GB system partition to do that update..


anyhow, I all good now, will not try to update again

[Cis]

So I guess I am a bit stubborned and went through the process

I am now with an 8GB system partition, on TOS 5.0.176 clean install, which is still not yet finished.

I could land on the TOS UI and I am now in the process of repairing my RAID1 storage pool, which should last maybe a day, but gives me the feeling that my data is still there.

Do you know if this is possible and expected? at least OK ?

After the clean install, I had a notif saying my RAID was degraded, and it looks like the same process to replace a broken disk with a new one.. so I had only one of my disk in the Pool, but all data were accessible at this stage before the raid repairing process.

After that I plan to manually upgrade to 5.1.24 and then 5.1.40 as per OP.

[Cis]

Raid 1 repairing is done now and I can confirm I have all data, nothing wiped, and 7.4Gb of system partition \o/

[uasdfnasfdj]

Hello there,

on my F5-422 the clean installation of TOS 5.0.176 does not work. Although I removed all partitions, after the installation, the second partition is only 2GB and the NAS is not available. Clean install of 4.2.40 works flawlessly.
I also tried TOS 5.1.40 with no success.

Can you please help?

[TMeric]

Hello there,

on my F5-422 the clean installation of TOS 5.0.176 does not work. Although I removed all partitions, after the installation, the second partition is only 2GB and the NAS is not available. Clean install of 4.2.40 works flawlessly.
I also tried TOS 5.1.40 with no success.

Can you please help?

You can refer to the second method of "How to delete all hard disk partitions" in this post to format your hard disk. Then manually install TOS5.1

[uasdfnasfdj]

Thanks for the suggestion. I now deleted the partitions via ssh and installed TOS_X642.0_5.0.176_00227_2210111430.ins. The result is the same. The second partition is always 2GB, not 8GB. Something in the installation routine is wrong.

Who is doing the partitioning? Does it come from the TOS_X642.0_5.0.176_00227_2210111430.ins-File or is it from the TNAS built-in USB boot disk?

[TMzethar]

{L_BUTTON_AT}uasdfnasfdj

Please pay attention to your Initboot (BootLoader) version when installing TOS and tell us.
After installing TOS 5.0.176, the Initboot (BootLoader) version should also be updated. You can delete the partition and try installing TOS again.

[uasdfnasfdj]

If this would work, the Boot Loader must have been updated several times, because I've tried it very often. When I want to initialize via web interface, in the bottom right there is a version info: "J3455_V4.5.5". Is this what you mean?

On the download site for the F5-422, there is a boot loader file: common_bootloader_V5.1.47.img. How do I flash it to /dev/sda?

Addition: I found a /etc/tos.conf with this content:

Code: Select all

[tos]
coresize=2048
swapsize=1024
fireware=https://download2.terra-master.com/TOS_S2.0_Install_JM33_4.2.40_2205181519_2211220940.ins
md5=b781b8bad276242d85945ec5f1da168e
version=4.2.40

Can I simply replace 2048 with 8192 and the 2nd partition will be 8GB? In /etc/tos/scripts there are also various scripts, that seems to have something to do with the sizing of the partitions.

Maybe changing one of the parameters is enough to allow the update to work?

[Gremlin]

Can I simply replace 2048 with 8192 and the 2nd partition will be 8GB? In /etc/tos/scripts there are also various scripts, that seems to have something to do with the sizing of the partitions.

Unfortunately not (even if it were relevant). The partitions are relatively "fixed in space". To make 2nd larger you have to physically move subsequent partitions. Otherwise you will be effectively overwriting partitions 3 + 4.