How to install ONLY the TOS 6.0 system on NVMe? (+ HDD sound)

[JEG]

Hi, cool people, I'm new to this NAS world.

F6-424
Crucial P3 Plus 500G NVMe
IronWolf Pro 16TB

I initialized the system with only the NVMe inserted, so after it finished installing TOS 6.0 (TRAID), I then inserted a IronWolf Pro 16TB & added it to the Pool with the Nvme (I don't know if I was supposed to create a new Pool for the HDDs). Now I'm waiting for another IronWolf to arrive hopefully by tomorrow, so my question is as follows.

How do I make sure that only TOS 6.0 is on the Nvme & nothing gets transferred to it when adding/moving movies to the NAS? I'm waiting for the next HDD to arrive so I can then start moving data to the NAS & just want to be prepared on what to do so the data only goes to the HDDs.

Extra question. Is it normal for the HDD to make a weird sound exactly every 30 minutes? (I don't know how to describe the sound & if this is normal for a NAS). The NAS says the drive is healthy, vibration/shock is marked as normal, I'm running a bad block scan at the moment. It's a new HDD from Amazon & it was packaged pretty well; I've gotten HDDs in the past where they arrive in a paper bag with no protection at all & I quickly send them back. I'm anxious on moving forward with the setup not knowing if the sound is normal.

Uploaded the sound to Youtube https://youtu.be/TajOXgexBL8
IronWolf Health Manager https://imgur.com/QHZIQDK (i tried using the "postimages dot org" but i get the warning "This website has been reported for potential phishing."

[RyanYang]

If you selected only the NVMe M.2 SSD during the TOS installation, then TOS will be installed exclusively on the NVMe M.2 SSD.

To prevent files from being transferred to the SSD, you can create a new storage pool using only the HDD. Then, create a new volume on that storage pool and set up shared folders on this new volume. As long as you transfer files to these shared folders, you will avoid uploading files to the NVMe M.2 SSD.

Are you using any specific applications or features? Do you hear the hard drive making noise when transferring files to the TNAS? Is your power supply the original one? What is the voltage of the power adapter? When you hear the hard drive noise, you can check the TOS Control Panel to see if any processes are consuming significant hardware resources.

[JEG]

Are you using any specific applications or features? Is your power supply the original one? When you hear the hard drive noise, you can check the TOS Control Panel to see if any processes are consuming significant hardware resources.

I'm not using any applications, the only thing that I have done is installed the system on the NVMe & added the IronWolf afterwards. There's no data on the NAS, still waiting for the 2nd HDD to arrive so I can start adding files to it. Everything is original, brand new from Amazon.

Do you hear the hard drive making noise when transferring files to the TNAS?

I hear the HDD making noise as if I'm transferring something to it (but I'm not). I made a new recording, https://youtu.be/fjNzCwLfaXQ this is the sound that I hear nonstop. And exactly every 30 minutes it makes this sound that I linked previously https://youtu.be/TajOXgexBL8, did you hear it? I'm guessing from your questions, that the sound is not normal? Is that the NAS interacting with the HDD or is the HDD faulty?

The bad block scan just finished & it found 0 bad sectors. https://imgur.com/1R1UedW

A couple of days ago I had initially installed the system on the HDD (I had no NVMe yet). And the sound I'm talking about was also present, I thought it was a normal sound since the system was installed on the HDD (I assumed, since its my first NAS). And Now that I installed the system on the NVMe I can see I was mistaken, and now I'm here trying to figure this out

[TMroy]

Why did you add a 16TB hard drive to the NVMe SSD storage pool? It is recommended that you create a separate storage pool for it.

[JEG]

Why did you add a 16TB hard drive to the NVMe SSD storage pool? It is recommended that you create a separate storage pool for it.

This is my first time creating a NAS (i know it's not the best excuse, but I'm trying to learn). That's why I also initially asked how to make sure that the data i send to the TNAS, to only go to the HDDs. I already deleted the volume & storage pool in order for the NVMe SSD to only have the TOS in it. I'm waiting for a new IronWolf Pro to arrive today & will see if the HDD noise is still present; I already took out the HDD that had the noise & will be sending it back.

The NVMe SSD is currently not part of any storage pool, is it ok to leave it that way? I'm not planning on installing any programs on the TNAS. I just need it for storage so my Plex server can pull the data off of it (Plex server is running on a Beelink S12 Pro).

[RyanYang]

You can keep the SSD without creating any storage pool.

[JEG]

You can keep the SSD without creating any storage pool.

So i just inserted a new IronWolf Pro, & it's also making those sounds from the first. I made sure to only have the new HDD inserted; i just left it on without adding it to a storage pool. Just by the HDD being inside the TNAS it makes both sounds that I linked before (nonstop sound & the every 30 minutes sound). Does this mean that the culprit is the F6-424 itself? I'm thinking of just sending it back

[RyanYang]

You can try going to the hardware and power module of the TOS control panel to modify the sleep settings. Is your hard drive model ST16000NE000? Do you have any other models of hard drives?

[Pulsar]

Hello!

I found that it can be HDD sounds from the mediadb.service and create new topic here:
viewtopic.php?t=7457

I installed and launched this package for monitoring the disk subsystem

Code: Select all

fatrace -f W

so found exactly this type of noises..

[Pulsar]

I also encountered the fact that after upgrading TOS from version 5 (installed ONLY on SD) to 6, the system was also automatically installed on every HDD's.

The only solution I found was to manually remove the HDD drives from the RAID arrays - that created for the system and swap partition.

That is, it is necessary to consistently mark the HDD disks as "failed" for these two RAID arrays (and clean the headers), then it's possible to delete unnecessary partitions, so the system will be installed only on the SSD.

It would definitely be great to get some official instructions on how to perform such actions - in fact, this will provide something like a "transfer" of the system from one to another disk