I would suggest removing the WD Purple for a better model of drive
Incidently thats a very similar build to my HairyNAS - its a solid build - apart from that disk. I used the 10Gb model of motherboard rather than your Quad 1Gb
I would suggest removing the WD Purple for a better model of drive
Incidently thats a very similar build to my HairyNAS - its a solid build - apart from that disk. I used the 10Gb model of motherboard rather than your Quad 1Gb
This particular pool is only for the NVR VM and my Emby media. I don’t need a higher performance drive. They’ll all eventually be replaced with the same Purple while my other pool with all the important (and productive) stuff will stay on the WD Red Pro 10TB drives currently in there.
The old Synology RS820+ (slave NAS for backing up the TrueNAS important pool) still has the Seagate Ironwolf drives, as I like to go with different brands between appliances in case there are batch issues with manufacturers and whatnot.
I’m very happy with this motherboard. I was wanting to stick to an Atom CPU for low power consumption and it fit the bill with its capacity for 12 drives and an M.2 SSD.
I leave the grunt work to the HP DL20 hosting ESXi (eventually Proxmox when ESXi outlives its usefulness and Broadcom’s sales strategies). I’m not one to throw all my eggs in the one basket, as attractive as running VMs in TrueNAS might be.
Ah, now I understand.
No, ZFS will not tell you what files or metadata was affected by recoverable checksum, (or R/W), errors.
In general, ZFS should not care about 1 or more slower disk(s) in the mix. For RAID-Zx reading or writing that goes across the mixture, that will affect speed. Specifically, it will be limited to the slowest disk in the RAID-Zx stripe.
For me, I have a media server with 1 x 1TB mSATA SSD and 1 x 2TB 2.5" laptop HDD, (probably SMR), striped, (no redundancy), with ZFS. A big difference in speed, yet it works fine for media services use. Well, until I loose a block and have to restore a file. But I have good backups. Normally no checksum errors.