Page 1 of 1

[Help] F6-424 tos 6.0.783 can't set system disks to NVME

Posted: 30 Oct 2025, 03:17
by Tallicia
Under Disk -> System Disk -> migrate to NVMe Disk1 and Disk2 are greyed out and cannot be selected to migrate to as a destination disk for the System disk.

Why? :cry:

This is a F6-424 running TOS 6.0.783

**** The following issue has been corrected with the Network -> Interface -> Edit -> Primary DNS entry changed. Network issues are resolved. The main NVMe system disk inability issue remains****
I also experience an issue currently where it cannot check for TOS version updates successfully or be able to set the TNAS.online remote access, which may or may not be related. Both say operations time out. :shock:

Re: [Help] F6-424 tos 6.0.783 can't set system disks to NVME

Posted: 30 Oct 2025, 17:25
by TMzethar
Please note that SSDs used as Cache cannot be used as system disks. Please check the purpose of the SSD.
This feature will prevent the simultaneous use of HDD and SSD as system disks. If you currently have two HDDs each containing a system, you need to select two SSDs as targets. If the number does not match, you need to first increase or decrease the number of Disks containing systems.

Code: Select all

lsblk
Please log in to the terminal, enter the command to view the storage structure, and then display the output information here.

Re: [Help] F6-424 tos 6.0.783 can't set system disks to NVME

Posted: 02 Nov 2025, 08:24
by Tallicia
I found the solution, it was merely the UI is not intuitive.

I had to check the box in the top left. I had been checking both the HDD3 and HDD4 where the system disks were located. Once clicking the top left box in the header instead The UI allows selection of the NVMe as a destination. That copied it to just one the NVME1 and then I had to do a second step to make sure it was redundant to NVME2 as well.

This was noticed as a possibility from the recent TOS 7 video: https://youtu.be/7_RLvtG-nCI?t=115