Bug Reports, Operation Guides, and Experience Sharing
https://forum.terra-master.com/en/
Because it is not that simple.
Hello, you need to upgrade to version 145 first before you can proceed with the upgrade to TOS 6. Our system can only be installed on SATA hard drives or NVMe solid-state drives; you cannot select an external hard drive for installation. Additionally, the F4-423 sets up RAID through software.tokingarg wrote: ↑30 Aug 2025, 10:44Because it is not that simple.
I'm just going to explain everything. Thank you both for following up!
My setup is as follows:
F4-423
2 external transcend 128 gb ssd mirrored and backed up to prevent failures like this
2 1tb nvme setup as hypercache and apps
4 16tb seagate ironwolf pro in raid 5
First I thought it was a network issue, but ssh showed that it wasn't and I considered a software issue so I updated everything tnas related.
I knew it was update related, because I could not restore the back of the mirror when it stopped loading
Hardware, I wasn't sure about but I took everything out and reseated it. I was disappointed when zethar told me to take out each drive.
when I d/c the raid array, it finds the nas but I can't initialize anything, it goes to the bootloader screen and fails
then I d/c external ssd, I can initialize, but it sees the nvme drives but not the ext ssd when I plug it back in
So now I removed the nvmes, put them in an external enclosure and I formatted them
I don't want to put the OS on the nvmes because of stability issues with that type
I have now formatted the ext ssd.
Can I go directly to tos6 at this point or do I still need 145?
How can I start with the ssd when the bootloader doesn't find it?
And is the F4 a hardware raid controller?
I thought it was software which is why I was worried about data loss
Thanks again!~
This is an unusual comment since this feature has been specifically requested many times in the past and newer nas setups are built around nvme drives - exactly for the reasons of speed and stability. If you want 'apps' on the nvme, you will, inevitably, want to put the os on the same nvme. The default setup is [OS partitions + Pool1/Volume1] on the nominated drive and 'apps' are also installed on Volume 1 by default.
You can refer to the following upgrade path: viewtopic.php?t=6984. The upgrade sequence is as follows: (TOS 4.2.44---TOS 5.0.XX) → TOS 5.0.176 → TOS 5.1.24 → (TOS 5.1.145---6.0.229) → TOS 6.0.530 → Latest version of TOS 6. The current latest version is TOS 6.0.770, which supports system disk management functionality, allowing you to migrate the system disk from HDD to NVMe. Following the upgrade steps as outlined will not delete data from your hard drives. Please review the release notes for each version.tokingarg wrote: ↑31 Aug 2025, 01:58 Okay, some clarifications.
The OS and apps are on an esata drive that is mirrored. I did it that way so that I could add the nvme and hard drives because I didn't have money for everything in the beginning. I can't find where I read that having the 2 transcend (Transcend TS128GMTS430S) 128 ssds mirrored was better, but I set all this up in 2022-2023. I used balenaetcher to put the image on it. Maybe things have changed. It was more stable raid mirror config, slc cache, and longer lasting than other nvmes.
The 1tb internal NVME's are not mirrored or part of the raid array. 1 is hypercache. The other is additional apps that I play with and for some streaming/video I mess with.
I really appreciate the help and I'm not being adversarial. Everything is formatted except the 64tb raid 5 array. At this point, I would like to start over and get it to the most updated and the most efficient with a high level of data redundancy. If you are recommending that I ditch the eSATA, just go with 1 nvme for os and apps, and the other for hypercache, that is the way I will go.
I asked about raid hardware controller because I know in some cases that you can lose the raid if you change the os. I guess I didn't have to worry about that since it's the same linux distro and would still see it as a single mount. Is this correct?
So I don't mess this up...
leave the hard drives out and disconnect the esata. Initialize the bootloader through tnas-pc. Load TOS 5.1.67 (last working) or load .145(?) on to 1 of the nvmes. Then what do I do next? Plug the drives back in and try to update again? to which version specifically?
Sorry for being such a pain! You both have been great. I was a little panicked if I lost all my backups, security footage, videos etc