IdefixRC
Cadet
- Joined
- Aug 6, 2023
- Messages
- 5
Hello everyone,
I have a very strange IO error on my Truenas scale system.
Note: the system runs virtualized on ESXi 6.7 with a SAS controller on passthrough (yes i know this is not ideal).
I run one Pool with 2 VDEVs.
VDEV 1: 4x 4TB Drives
VDEV 2: 4x 8TB Drives
Both are running RaidZ1
Initially, VDEV2 had 3 Seagate Ironwolf and 1 WD drive.
I started receiving IO errors (always around 248 errors) on one of the Ironwolf drives some weeks into the operation of the NAS.
Swapping cables and moving the disk to a different backplane did not solve the issue. So I replaced it with a Toshiba N300 8TB drive.
As soon as this was done the nextIronwolf threw a similar IO error, again, swapping cables or bays did not make a difference. The error remained with the drive.
Similarly, I replaced the Ironwolf with a N300 8TB and.....bang, the next Ironwolf immediately showed the same issue.
VDEV2 now has no Ironwolf left and the IO error is gone.
BUT.....vDEV1 has one 4TB Ironwolf and as soon as the last Ironwolf was replaced from VDEV2, this drive throw the same error with around 248 errors detected.
The Ironwolfes are not old, some of the ones were replaced with less than 3 months of operation and no new FW could be found (Understand there was some issue in the past with some of them).
Does anyone have an idea what the issue could be?
Memory? (but why only the Ironwolfes are impacted?)
Issues with the SAS controller/MB/CPU? (The SAS controller-HEC310 in IT mode- ran fine with these drives in the old windows server - MB and CPU are new though)
Thanks a lot !
I have a very strange IO error on my Truenas scale system.
Note: the system runs virtualized on ESXi 6.7 with a SAS controller on passthrough (yes i know this is not ideal).
I run one Pool with 2 VDEVs.
VDEV 1: 4x 4TB Drives
VDEV 2: 4x 8TB Drives
Both are running RaidZ1
Initially, VDEV2 had 3 Seagate Ironwolf and 1 WD drive.
I started receiving IO errors (always around 248 errors) on one of the Ironwolf drives some weeks into the operation of the NAS.
Swapping cables and moving the disk to a different backplane did not solve the issue. So I replaced it with a Toshiba N300 8TB drive.
As soon as this was done the nextIronwolf threw a similar IO error, again, swapping cables or bays did not make a difference. The error remained with the drive.
Similarly, I replaced the Ironwolf with a N300 8TB and.....bang, the next Ironwolf immediately showed the same issue.
VDEV2 now has no Ironwolf left and the IO error is gone.
BUT.....vDEV1 has one 4TB Ironwolf and as soon as the last Ironwolf was replaced from VDEV2, this drive throw the same error with around 248 errors detected.
The Ironwolfes are not old, some of the ones were replaced with less than 3 months of operation and no new FW could be found (Understand there was some issue in the past with some of them).
Does anyone have an idea what the issue could be?
Memory? (but why only the Ironwolfes are impacted?)
Issues with the SAS controller/MB/CPU? (The SAS controller-HEC310 in IT mode- ran fine with these drives in the old windows server - MB and CPU are new though)
Thanks a lot !