TOS 6.0.420 Beta Is Available for Testing

[Gremlin]

To add:

Code: Select all

######~# fdisk -l
Disk /dev/sda: 5.46 TiB, 6001175126016 bytes, 11721045168 sectors
Disk model: HGST HDN726060AL
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: A7047464-0CB1-40E1-ADD6-D64905CB98F4

Device        Start         End     Sectors  Size Type
/dev/sda1      2048      585727      583680  285M Linux filesystem
/dev/sda2    585728    16586751    16001024  7.6G Linux filesystem
/dev/sda3  16586752    20586495     3999744  1.9G Linux filesystem
/dev/sda4  20586496 11718747911 11698161416  5.4T Linux filesystem


Disk /dev/md9: 7.63 GiB, 8187281408 bytes, 15990784 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/md8: 1.91 GiB, 2045771776 bytes, 3995648 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/md0: 5.45 TiB, 5989324423168 bytes, 11697899264 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/mapper/vg0-lv0: 2.44 TiB, 2684354560000 bytes, 5242880000 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes

[TMlinda]

Yes, this is normal.

[Sparker]

Will there be an upgrade path from TOS 5, or earlier 6 betas with the final TOS 6 release?

I am a bit surprised that TOS 6 does not support upgrading the current system to the new version.

[imranalam]

Rename your TNAS ID and try again.

I already tried with different tnas id, but its same.

[TMroy]

In TOS, the file system is created on logical volumes, rather than directly on disk partitions like in Windows. When your disk is a member of an array, and when viewed as an independent disk, the file system is unrecognizable.

[TMroy]

Yes, when the final version of TOS 6 is released, it can be updated from a specified version of TOS 5.1 to TOS 6.

[fcs001fcs]

In TOS, the file system is created on logical volumes, rather than directly on disk partitions like in Windows. When your disk is a member of an array, and when viewed as an independent disk, the file system is unrecognizable.

Thanks for the quick confirmation.

[bretwashere]

Yes. Once the system is updated to 6.0.420, the USB boot will also be updated, and you will no longer be able to install TOS 5. Please refer to item 16 in the update precautions. Unless you replace it with an earlier USB boot by yourself, you can reinstall TOS 5.

We will release a USB boot burning tool in the near future, which will allow users to easily replace the initboot on the USB.

Let’s say someone performs a backup of their existing 5.x compatible internal USB flash drive. Would restoring that backup work, or are there other checks in place to prevent downgrading?

[TMroy]

Item 16 in precautions should maybe be a lot higher up the list and even up amongst the RED items. I didn't see it. ????? And, if i had I probably would not have presumed that an UPDATE would effectively break the system and be irreversible. This is a BETA situation which imo should always be reversible - because sometimes we find things are broken.

You should know that when too many items are highlighted, there is no focus. Unfortunately, everyone thinks that the problems he encounters should be highlighted in a prominent position beforehand.

[golgoth]

After updating from 249 to 420:

- System is less responsive, both locally and through TNAS Online (i used to select EU server, now i'm bound to US1, god knows why).
- It took like 5 minutes to move few 4-5 GB files, maybe because they had an apostrophe in their names. Other files were transferred in a matter of seconds.
- Today i had to reset the NAS, cause it was stuck with a 80% load, even if nothing unusual was running.
- The reset took 25 minutes.
- At every reset i have to manually start NGINX and TOSDAEMON (bug that was also on 249).

Still asking myself why i didn't install openmediavault or something similar at the first time, now i have 20 TBs of datas to place if i want to change OS.