After a restart, my pool status shows as Unhealthy.
Ran a scrub next. The 1 error is a read error on the nvme cache drive.
It’s an about 1 month old drive.
I figured I’d try resetting the error and see if it happens again, for now, since it’s just the cache.
When I run zpool clear tank, the error isn’t cleared from my vdev screen.
So if I intend to attempt to keep using this nvme for now, I kind of just need a advice because I’m unsure.. should I just remove the drive from the pool and re add it in the web ui ?? Or is there another way I can clear this one error.
Not really a great answer… lets assume that OP has a valid use case that benefits from caching.
OP, I think you’ve got the right process… one read error on a drive should raise an eyebrow but doesn’t warrant much more action than that. If it happens again, see about RMA’ing the drive. You can clear the error from the shell, do zpool clear tank - zpool-clear.8 — OpenZFS documentation
Ya even restarted the NAS it still showed the 1 error. I accidentally started another scrub. When it finishes I’m going to try again with the device specified
Look in my signature for the link to Drive Troubleshooting Flowcharts. This should help you identify the issue, or at least allow you to provide some detailed information to the group to help you out.
I’ve had conversations with ChatGPT about doing things with ZFS. We’re still not there yet. Maybe in the near future, but not today. It spits out half truths and mixes legit things with nonsense.
