TerraMaster Forum

I am going to lose my mind.

F4-423. The BIOS did not need updating.

I installed a 512GB NVMe to install the latest TOS. All went well, I can boot and I see TOS-7. It updated once more.

I have the NVMe set as boot option #2.

When I add drives to the NAS I get this:



I tried making Boot Option #1 as the NVMe but that didn't work.

If I remove the hard drives, then I can boot without any issues.

How can I fix this?

The hard drives were in this NAS before, I did not format them. The NVMe is brand new, and as I said it works just fine. If I insert the hard drive AFTER I boot from the NVMe, the system sees the hard drives and I can mount them, but if I reboot, I get that error message.

Please help.

Thank you for the detailed information. Based on your description, the issue is most likely caused by the existing hard drives still containing old TOS system partitions from the previous installation.

Since the new NVMe SSD is now the system disk, we recommend removing the old system partitions from the previous system disks. This does not require formatting the hard drives or deleting the existing data.

Please follow these steps:

1. Power off the TNAS and remove the existing hard drives.
2. Leave only the new NVMe SSD installed and boot the TNAS normally.
3. After successfully entering TOS, insert the original hard drives while TOS is running.
4. Wait until TOS detects the hard drives and confirms that the existing data/storage pools are accessible.
Go to: Storage Management → Disks → System Disk

In the System Disk list, identify the non-current/old system disks that still contain the previous TOS system.
Select the old system disk(s) and choose Delete/Remove to remove the old system partition.
Important: Please make sure you select the old system disk/system partition, not the storage pool or data volume. Do not select “Erase Disk,” “Delete Storage Pool,” or format the hard drives.

After the old system partitions have been removed, reboot the TNAS with the NVMe SSD and the hard drives installed.
The purpose of this operation is to make the new NVMe the only active TOS system disk, while keeping the existing data on the hard drives intact.
Please also make sure that the NVMe SSD is selected as the first boot device in the BIOS/UEFI.

F2-423 here.
2x 256gb NVMe.
NVMe1 is the system disk, NVMe2 its for hypercache and the 2xHDDs are for storage. what is the course of action here?

wviegas wrote: ↑03 Sep 2026, 08:36 F2-423 here.
2x 256gb NVMe.
NVMe1 is the system disk, NVMe2 its for hypercache and the 2xHDDs are for storage. what is the course of action here?

This configuration appears to be fully functional with no issues. If you are currently experiencing abnormal operation, you may refer to the method mentioned by Mike: navigate to the Storage Management > Disks > System Disks page, and remove the system installations on all disks except for NVMe1.

Sounds like this company once again created an update that can't be installed by novice users. How about getting an actual team for testing instead of letting your users be the alpha testers. This is the second time since purchasing this unit that I've had to jump through hoops to fix a failed update due to subpar engineering.

tc0566 wrote: ↑20 Oct 2026, 23:06

You seem to be overlooking the thousands of successful updates.

You seem to be ignoring that they have admitted to the problems and have told users work arounds. You are replying to a thread showing one of the problems right now. There are multiple others. Anytime there is a major update this happens. Every security permission is screwed now.Can access media server remotely but can't access files on it.

tc0566 wrote: ↑21 Oct 2026, 00:09

When accessing files on the NAS through the media server, please make sure that the corresponding app user has permission to access the target directory.

CursaYang wrote: ↑21 Oct 2026, 07:48

tc0566 wrote: ↑21 Oct 2026, 00:09

When accessing files on the NAS through the media server, please make sure that the corresponding app user has permission to access the target directory.

Yeah, I figured that out. Been using this since TOS 5 and this have never been needed before. It automatically worked when PLex was installed , now have to give things permission. And even though my computer sees it and remote access says it's good, none of the 3 TV's see it now. I'm so over TOS 7 already. Or should say was available and now can't enable remote access. TOS has it blocked again.

tc0566 wrote: ↑21 Oct 2026, 08:35

This situation may involve multiple factors. Please contact our online support team via the link below so we can assist you with direct troubleshooting: https://salesiq.zohopublic.com/signatur ... 97d0be8892