Sorry, I posted this in the wrong forum at first!
Truenas CORE 13.0-U3.1
Current pool:
2x 256GB NVMe metadata special device mirror
3x 4TB WD blue in RAID-Z1
51% of ~7.5TiB capacity used
All disks are healthy but I want to replace with SAS drives so I can move the WD Blues to a computer that doesn't support SAS.
I have Dell branded Seagate 4TB SAS self-encrypting drives. I had a hard time making them work, I think related to the SED feature and Truenas Scale, but on CORE at least one seems to be working fine now. In its own single-disk pool I can write data at 150MB/s, scrub without errors, and read data back successfully. Waiting on the results of a long SMART test but I have found no reason yet to think this drive is faulty.
However when I try to Replace one of my existing disks, I have 2 problems:
* Even if I just wiped the drive from the Disk menu in the GUI, it says partitions were found and I need to Force use of the disk as a replacement.
* Resilvering is insanely slow. I've seen posts with "slow" 30MB/s resilvering speeds but their Zpool Status readouts look symmetrical between scanning and issuing- X GB scanned at 30MB/s, X GB issued at 30MB/s. Mine looks like a massive bottleneck writing to the drive. After running overnight for 12 hours it reported roughly 360GB scanned at 55MB/s, 12GB issued at 3.5MB/s. ETA went up to a few weeks before it stopped giving an ETA. Overall resilver progress after 12 hours was 2% at which point I stopped. I don't have enough RAM to read 360GB but not write it out anywhere - in the context of replacing a healthy drive, what is the resilver doing if not writing to the SAS drive?
Basically I am wondering if this is an incompatibility with these weird SAS drives, or a mixed pool of SATA/SAS drives, or if my expectations are just way off for how long this could take. If it is normal that it would take 25 days to replace each of these drives, I'll need to figure out another way to migrate to the SAS drives (likely export this pool to another machine and move the data back over to a new SAS pool).
Thanks in advance for any help!
Truenas CORE 13.0-U3.1
Current pool:
2x 256GB NVMe metadata special device mirror
3x 4TB WD blue in RAID-Z1
51% of ~7.5TiB capacity used
All disks are healthy but I want to replace with SAS drives so I can move the WD Blues to a computer that doesn't support SAS.
I have Dell branded Seagate 4TB SAS self-encrypting drives. I had a hard time making them work, I think related to the SED feature and Truenas Scale, but on CORE at least one seems to be working fine now. In its own single-disk pool I can write data at 150MB/s, scrub without errors, and read data back successfully. Waiting on the results of a long SMART test but I have found no reason yet to think this drive is faulty.
However when I try to Replace one of my existing disks, I have 2 problems:
* Even if I just wiped the drive from the Disk menu in the GUI, it says partitions were found and I need to Force use of the disk as a replacement.
* Resilvering is insanely slow. I've seen posts with "slow" 30MB/s resilvering speeds but their Zpool Status readouts look symmetrical between scanning and issuing- X GB scanned at 30MB/s, X GB issued at 30MB/s. Mine looks like a massive bottleneck writing to the drive. After running overnight for 12 hours it reported roughly 360GB scanned at 55MB/s, 12GB issued at 3.5MB/s. ETA went up to a few weeks before it stopped giving an ETA. Overall resilver progress after 12 hours was 2% at which point I stopped. I don't have enough RAM to read 360GB but not write it out anywhere - in the context of replacing a healthy drive, what is the resilver doing if not writing to the SAS drive?
Basically I am wondering if this is an incompatibility with these weird SAS drives, or a mixed pool of SATA/SAS drives, or if my expectations are just way off for how long this could take. If it is normal that it would take 25 days to replace each of these drives, I'll need to figure out another way to migrate to the SAS drives (likely export this pool to another machine and move the data back over to a new SAS pool).
Thanks in advance for any help!
