AntoninKyrene
Dabbler
- Joined
- Jan 2, 2023
- Messages
- 15
Hello!
I successfully deployed my first TrueNAS CORE unit two weeks ago after months of research and tinkering. So far I am a very satisfied user.
BACKGROUND
I found myself needing to migrate (on somewhat short notice) from a Synology DS1817+ deployed almost exactly 5 years ago. My current TrueNAS setup is 16 drives totaling 60TB Raw / 40.5 Storage across a pair of IBM M5110 controllers. I had a spare AMD Ryzen PRO 4750G processor needing a home and paired it with 32GB of ECC DDR4 memory. The TrueNAS unit is built around 3 storage pools. I started with a single controller and 4 disks, imported a second pool of 4 disks on the same controller, and finally imported 8 disks on a second controller. The first 4 disks are new WD Red Plus 6TB drives. The second 4 disks are WD Red 3TB drives from the original Synology setup (these were used as hot backups connected to the Synology via USB, courtesy of two WD MyBook Duo enclosures). The 8 remaining disks are the WD Red 3TB drives from the original Synology itself. All of this data was backed up to 4 Seagate external HDDs.
WORKFLOW
The TrueNAS is connected to an Intel NUC running Windows 10 Pro via Ethernet, but through a hub rather than a switch or router, a.k.a. no gateway. All data is being imported through the NUC. Data from the Seagate HDDs to the NUC SSD, and then from the NUC SSD to TrueNAS. Speeds between NUC and NAS are rock-solid and at the upper end of the Gigabit limit: 110MB/s to 112 MB/s. Once within the NAS, data is being sorted and repositioned. Movements from NUC to NAS are exclusive of data movements between pools. If one process is moving data, the other is not. Movement from pool to pool reaches speeds in excess of 400MB/s, but the average seems to be about 290 MB/s.
I have a single issue. It is not a showstopper, as I have moved well over 20TB of data so far and continue to move more, but I am stumped as to what could be causing it.
ISSUE
Every 10-12 minutes, when going from NUC to NAS, the transfer speed across the network drops to exactly 5.54 MB/s and then bounces between that number and zero. This bouncing takes places for anywhere from a few seconds to a couple of minutes, and then full-speed transfers resume for another 10-12 minutes. I assumed it was a network issue. No - the exact same phenomenon is also taking place pool-to-pool, whether it be within one controller or across both.
TrueNAS is showing no errors whatsoever at any level of operation. CPU usage across all 16 cores never exceeds 15% and temperatures are under 50 Celsius. I see no SMART errors or anything disk-related that would indicate disk health is problematic.
The only idea I could come up with is pool saturation. Currently ZFS1 and ZFS2 are over 90% - they absorbed the critical data before the 8-disk pool (ZFS3) came online, and they are now relieving themselves of their over-80% status by moving data to ZFS3.
Any thoughts on what might be causing this issue? I did not find anything after considerable searching, but I am not the world's best searcher, either.
-Antonin
I successfully deployed my first TrueNAS CORE unit two weeks ago after months of research and tinkering. So far I am a very satisfied user.
BACKGROUND
I found myself needing to migrate (on somewhat short notice) from a Synology DS1817+ deployed almost exactly 5 years ago. My current TrueNAS setup is 16 drives totaling 60TB Raw / 40.5 Storage across a pair of IBM M5110 controllers. I had a spare AMD Ryzen PRO 4750G processor needing a home and paired it with 32GB of ECC DDR4 memory. The TrueNAS unit is built around 3 storage pools. I started with a single controller and 4 disks, imported a second pool of 4 disks on the same controller, and finally imported 8 disks on a second controller. The first 4 disks are new WD Red Plus 6TB drives. The second 4 disks are WD Red 3TB drives from the original Synology setup (these were used as hot backups connected to the Synology via USB, courtesy of two WD MyBook Duo enclosures). The 8 remaining disks are the WD Red 3TB drives from the original Synology itself. All of this data was backed up to 4 Seagate external HDDs.
WORKFLOW
The TrueNAS is connected to an Intel NUC running Windows 10 Pro via Ethernet, but through a hub rather than a switch or router, a.k.a. no gateway. All data is being imported through the NUC. Data from the Seagate HDDs to the NUC SSD, and then from the NUC SSD to TrueNAS. Speeds between NUC and NAS are rock-solid and at the upper end of the Gigabit limit: 110MB/s to 112 MB/s. Once within the NAS, data is being sorted and repositioned. Movements from NUC to NAS are exclusive of data movements between pools. If one process is moving data, the other is not. Movement from pool to pool reaches speeds in excess of 400MB/s, but the average seems to be about 290 MB/s.
I have a single issue. It is not a showstopper, as I have moved well over 20TB of data so far and continue to move more, but I am stumped as to what could be causing it.
ISSUE
Every 10-12 minutes, when going from NUC to NAS, the transfer speed across the network drops to exactly 5.54 MB/s and then bounces between that number and zero. This bouncing takes places for anywhere from a few seconds to a couple of minutes, and then full-speed transfers resume for another 10-12 minutes. I assumed it was a network issue. No - the exact same phenomenon is also taking place pool-to-pool, whether it be within one controller or across both.
TrueNAS is showing no errors whatsoever at any level of operation. CPU usage across all 16 cores never exceeds 15% and temperatures are under 50 Celsius. I see no SMART errors or anything disk-related that would indicate disk health is problematic.
The only idea I could come up with is pool saturation. Currently ZFS1 and ZFS2 are over 90% - they absorbed the critical data before the 8-disk pool (ZFS3) came online, and they are now relieving themselves of their over-80% status by moving data to ZFS3.
Any thoughts on what might be causing this issue? I did not find anything after considerable searching, but I am not the world's best searcher, either.
-Antonin