3
ZFS says drive is faulted, does that always mean it needs replacing? (lemmy.world)
submitted 1 year ago by Relic5646@lemmy.world to c/selfhosted@lemmy.world
7 comments fedilink hide all child comments

My weekly zpool scrub came back with this:

  pool: blackhole
 state: DEGRADED
status: One or more devices are faulted in response to persistent errors.
    Sufficient replicas exist for the pool to continue functioning in a
    degraded state.
action: Replace the faulted device, or use 'zpool clear' to mark the device
    repaired.
  scan: scrub repaired 0B in 02:01:59 with 0 errors on Tue Jul 11 04:02:09 2023
config:

    NAME                                    STATE     READ WRITE CKSUM
    blackhole                               DEGRADED     0     0     0
      raidz1-0                              DEGRADED     0     0     0
        ata-WDC_WD120EDAZ-11F3RA0_5PG8DYKC  ONLINE       0     0     0
        ata-WDC_WD120EFBX-68B0EN0_5QKJ6M8B  ONLINE       0     0     0
        ata-WDC_WD120EFBX-68B0EN0_5QKJTT8B  FAULTED     51     0     0  too many errors

errors: No known data errors

I only got the drive 6 months ago, well within WD's 3 year warranty so I opened a support case, but do errors like this basically always mean the drive is its way out or is it possible to have false positives?

you are viewing a single comment's thread
view the rest of the comments
[-] ptz@dubvee.org 0 points 1 year ago

Typically, yes. It could be due to either a flaky SATA cable/connection/controller, so you might try moving it to a different port if you are able, clearing the error, and seeing if it reoccurs.

Regardless, just make sure you have a good backup of the data or are confident in the other two disks.

[-] AES@lemmy.ronsmans.eu 2 points 1 year ago

Change cable or re seat sata connector, clear errors and start a scrub is what I always do.

[-] Relic5646@lemmy.world 1 points 1 year ago

I've been suuuuper lazy troubleshooting this so it's been a few weeks, but I talked to WD support, they said to run a full extended S.M.A.R.T. test on the drive, it passed with no issues.

Reconnected it to my server using a different SATA cable on a different port on the motherboard, with a different power connector. It resilvered with no problems, and a zpool scrub returned no errors this time so hopefully I'm in the clear!

I have a script that runs once a week that does a scrub then sends the output of zpool status to a Discord channel. When this first started it had read errors (as mentioned in the post), then checksum errors two weeks later. With there being a couple different errors before troubleshooting, and now with no errors after a scrub I'm hoping this means everything's fine now.

this post was submitted on 11 Jul 2023
3 points (100.0% liked)

Selfhosted

40219 readers
705 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 1 year ago
MODERATORS
ruud@lemmy.world
Loki@lemmy.world
CannaVet@lemmy.world
devve@lemmy.world
HybridSarcasm@lemmy.world
HybridSarcasm@lemmy.hybridsarcasm.xyz