-
Notifications
You must be signed in to change notification settings - Fork 1.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Can't resilver WD NAS dirves #15033
Comments
You linked to a previous issue which was closed with "WD's SMR drives are broken and throw errors in this workload". That's still true - AFAIK WD has never fixed this behavior. There's not really anything ZFS can do about drives being broken and throwing errors under load, other than suggest you not use them. |
Just to make sure, I understand this right as I tested the drive, and it seems that is okay: there is nothing wrong with them except they can't work with ZFS and there is no workaround to this issue? |
Yes, this is what I had to do with one of my drives as well. |
Can a company be charged from selling drives advertised as 'CMR' with 'SMR' technology under the hood? |
New drives on order, will update once arrived. Thanks |
The new drives come, WD NAS Plus, and resilvering has completed without errors (as well much faster than Seagate Barracuda). It was definitely drive's firmware issue as mentioned before, therefore I'm closing this issue. |
It looks like I have similar issue to: #10214
This is my third drive I'm trying (other two replaced by manufacture). This time I did some digging and found the above mention. I tried BIOS setting to IDE but no such option. The PSU is way more powerful than it should be, as it was specified with the external GPU I removed. When I replace with Seagate Baracuda - no problem. It seams that it can't handle WD NAS drive:
Smart test seams to pass with no errors:
The text was updated successfully, but these errors were encountered: