Jump to content
Sign in to follow this  

Parity Drive red X

3 posts in this topic Last Reply

Recommended Posts

At about 9am this morning I got an email saying that my parity drive was down.


Event: unRAID Parity disk error
Subject: Alert [NAS1] - Parity disk in error state (disk dsbl)
Description: WDC_WD40EFRX-68WT0N0_WD-WCC4E0ELT95A (sdh)
Importance: alert


I'm home today, so I logged in to see a red x over parity.  I downloaded diagnostics, and tried looking at smart/running smartctl from the command, but no luck. 


root@NAS1:/boot# smartctl -a -A -T permissive /dev/sdh > /boot/paritySMART.txt
root@NAS1:/boot# cat paritySMART.txt
smartctl 6.5 2016-05-07 r4318 [x86_64-linux-4.9.30-unRAID] (local build)
Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org

Short INQUIRY response, skip product id

SMART Health Status: OK
Current Drive Temperature:     0 C
Drive Trip Temperature:        0 C

Read defect list: asked for grown list but didn't get it
Error Counter logging not supported

Device does not support Self Test logging

not getting anything from smart
I then shut the array down, walked down and opened/reseated the connectors to the Parity drive (and all drives) and looked around not seeing anything obviously wrong, so I started it back up.  The drive powered up and appears to be error free from a smart perspective.  smartctl runs and I can see attributes in the UI
Because of this, my opinion was to just unassign, reassign the drive and let it rebuild, but that doesn't seem to be working.   And that's what I'm doing now.  But I'm curious if anyone has any opinion on what might have happened?
Parity rebuild is just over 30% now and no errors detected.  unRaid had been up 31 days, and 0 erros found on 8/1 parity check.  One thing I forgot to check was if the drive was spinning/powered up. I am wondering if somehow it was not spinning which is why smartctl wasn't working, and even trying to through the UI (spin up drive) was failing.



Edited by Dmtalon

Share this post

Link to post

Thanks, that is my opinion as well.  After reseating the connectors, The Parity Sync did complete w/o errors.  Fingers crossed it was a one time issue.


Share this post

Link to post

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Sign in to follow this