Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Parity drive "device disabled"

Featured Replies

Woke up this morning to find that my Parity drive has been disabled.  I have attached a screen shot

 

My system specs are as follows

 

 

Model: N/A

System: ASRock - 990FX Extreme9

CPU: AMD FX-8350 Eight-Core @ 4 GHz

Cache: 384 kB, 8192 kB, 8192 kB

Memory: 16384 MB (max. 32 GB)

Network: eth0: 1000Mb/s - Full Duplex

Kernel: Linux 3.17.4-unRAID x86_64

OpenSSL: 1.0.1j

 

The only thing I have found on how I might be able to resolve this was in the link below

 

http://lime-technology.com/wiki/index.php/Make_unRAID_Trust_the_Parity_Drive,_Avoid_Rebuilding_Parity_Unnecessarily

 

Any help would be great

 

thank you

 

 

 

 

v6.jpg.b1d7b7386bd9c9b7f37a96c2569071ae.jpg

Since you don't have any reason to believe your parity is valid, that link is not the way to go. unRAID says it's invalid for a reason.

 

In fact, you don't actually have a parity drive as far as unRAID is concerned, because it has disabled it, probably due to a failure writing to that drive. Any writes to the array are not updating parity since it is disabled, so any additional writes to the array will mean that the parity disk is even further out-of-sync. If you get that drive working again, you will definitely need to update parity.

 

Post a syslog and a smart report of that drive.

  • Author

Sorry I posted this in the unRAID V5 forum and it should have be in V6 I have recreated it in the connect forum.

  • Author

I stopped the array so I cannot get a smart report for the parity drive. 

 

I guess the question is do I need to get a new drive (this one is less than a month old) or do I enable it and I have no problem re-running a parity check.

See here for getting smart report and here for syslog.

 

Can't advise on whether to get a new drive without these. We need to know why it was disabled. Maybe the drive, maybe something else.

  • Author

When I try to run the smart report command I get the following

 

smartctl -t short /dev/sdk

smartctl 6.2 2013-07-26 r3841 [x86_64-linux-3.17.4-unRAID] (local build)

Copyright © 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org

 

Short INQUIRY response, skip product id

A mandatory SMART command failed: exiting. To continue, add one or more '-T permissive' options.

 

 

As for the syslog the last 100 line are all from 01/10/2015 nothing newer.  And from the looks of things the drive was disabled at around 614 this morning.

 

Jan 10 20:38:05 tower sshd[19919]: Did not receive identification string from 172.17.0.43

Jan 10 20:38:05 tower sshd[19924]: Accepted password for root from 172.17.0.43 port 38620 ssh2

Jan 10 20:38:05 tower sshd[19925]: Accepted password for root from 172.17.0.43 port 38621 ssh2

Jan 10 20:38:05 tower sshd[19924]: error: Received disconnect from 172.17.0.43: 10:

Jan 10 20:38:05 tower sshd[19925]: error: Received disconnect from 172.17.0.43: 10:

Jan 10 20:38:10 tower emhttp: read_line: client closed the connection

Jan 10 20:38:10 tower sshd[20080]: Did not receive identification string from 172.17.0.43

Jan 10 20:38:10 tower sshd[20081]: Did not receive identification string from 172.17.0.43

Jan 10 20:38:10 tower sshd[20086]: Accepted password for root from 172.17.0.43 port 38762 ssh2

Jan 10 20:38:10 tower sshd[20087]: Accepted password for root from 172.17.0.43 port 38763 ssh2

Jan 10 20:38:10 tower sshd[20086]: error: Received disconnect from 172.17.0.43: 10:

Jan 10 20:38:10 tower sshd[20087]: error: Received disconnect from 172.17.0.43: 10:

Jan 10 20:38:15 tower emhttp: read_line: client closed the connection

Jan 10 20:38:15 tower sshd[20203]: Did not receive identification string from 172.17.0.43

Jan 10 20:38:15 tower sshd[20204]: Did not receive identification string from 172.17.0.43

Jan 10 20:38:15 tower sshd[20211]: Accepted password for root from 172.17.0.43 port 38807 ssh2

Jan 10 20:38:15 tower sshd[20210]: Accepted password for root from 172.17.0.43 port 38806 ssh2

Jan 10 20:38:15 tower sshd[20211]: error: Received disconnect from 172.17.0.43: 10:

Jan 10 20:38:15 tower sshd[20210]: error: Received disconnect from 172.17.0.43: 10:

Jan 10 20:38:20 tower emhttp: read_line: client closed the connection

Jan 10 20:38:20 tower sshd[20332]: Did not receive identification string from 172.17.0.43

Jan 10 20:38:20 tower sshd[20333]: Did not receive identification string from 172.17.0.43

Jan 10 20:38:20 tower sshd[20338]: Accepted password for root from 172.17.0.43 port 38837 ssh2

Jan 10 20:38:20 tower sshd[20339]: Accepted password for root from 172.17.0.43 port 38840 ssh2

Jan 10 20:38:20 tower sshd[20338]: error: Received disconnect from 172.17.0.43: 10:

Jan 10 20:38:20 tower sshd[20339]: error: Received disconnect from 172.17.0.43: 10:

Jan 10 20:38:25 tower emhttp: read_line: client closed the connection

Jan 10 20:38:25 tower sshd[20491]: Did not receive identification string from 172.17.0.43

Jan 10 20:38:25 tower sshd[20490]: Did not receive identification string from 172.17.0.43

Jan 10 20:38:25 tower sshd[20496]: Accepted password for root from 172.17.0.43 port 38872 ssh2

Jan 10 20:38:25 tower sshd[20497]: Accepted password for root from 172.17.0.43 port 38873 ssh2

Jan 10 20:38:25 tower sshd[20496]: error: Received disconnect from 172.17.0.43: 10:

Jan 10 20:38:25 tower sshd[20497]: error: Received disconnect from 172.17.0.43: 10:

Jan 10 20:38:30 tower emhttp: read_line: client closed the connection

Jan 10 20:38:30 tower sshd[20597]: Did not receive identification string from 172.17.0.43

Jan 10 20:38:30 tower sshd[20598]: Did not receive identification string from 172.17.0.43

Jan 10 20:38:30 tower sshd[20603]: Accepted password for root from 172.17.0.43 port 38897 ssh2

Jan 10 20:38:30 tower sshd[20604]: Accepted password for root from 172.17.0.43 port 38898 ssh2

Jan 10 20:38:30 tower sshd[20603]: error: Received disconnect from 172.17.0.43: 10:

Jan 10 20:38:30 tower sshd[20604]: error: Received disconnect from 172.17.0.43: 10:

Jan 10 20:38:35 tower emhttp: read_line: client closed the connection

Jan 10 20:38:35 tower sshd[20762]: Did not receive identification string from 172.17.0.43

Jan 10 20:38:35 tower sshd[20763]: Did not receive identification string from 172.17.0.43

Jan 10 20:38:35 tower sshd[20768]: Accepted password for root from 172.17.0.43 port 38924 ssh2

Jan 10 20:38:35 tower sshd[20769]: Accepted password for root from 172.17.0.43 port 38925 ssh2

Jan 10 20:38:35 tower sshd[20769]: error: Received disconnect from 172.17.0.43: 10:

Jan 10 20:38:35 tower sshd[20768]: error: Received disconnect from 172.17.0.43: 10:

Jan 10 20:38:40 tower emhttp: read_line: client closed the connection

Jan 10 20:38:40 tower sshd[20871]: Did not receive identification string from 172.17.0.43

Jan 10 20:38:40 tower sshd[20870]: Did not receive identification string from 172.17.0.43

Jan 10 20:38:40 tower sshd[20876]: Accepted password for root from 172.17.0.43 port 38949 ssh2

Jan 10 20:38:40 tower sshd[20877]: Accepted password for root from 172.17.0.43 port 38952 ssh2

Jan 10 20:38:40 tower sshd[20876]: error: Received disconnect from 172.17.0.43: 10:

Jan 10 20:38:40 tower sshd[20877]: error: Received disconnect from 172.17.0.43: 10:

Jan 10 20:38:45 tower emhttp: read_line: client closed the connection

Jan 10 20:38:45 tower sshd[21003]: Did not receive identification string from 172.17.0.43

Jan 10 20:38:45 tower sshd[21004]: Did not receive identification string from 172.17.0.43

Jan 10 20:38:45 tower sshd[21009]: Accepted password for root from 172.17.0.43 port 38962 ssh2

Jan 10 20:38:45 tower sshd[21010]: Accepted password for root from 172.17.0.43 port 38963 ssh2

Jan 10 20:38:45 tower sshd[21009]: error: Received disconnect from 172.17.0.43: 10:

Jan 10 20:38:45 tower sshd[21010]: error: Received disconnect from 172.17.0.43: 10:

Jan 10 20:38:50 tower emhttp: read_line: client closed the connection

Jan 10 20:38:50 tower sshd[21144]: Did not receive identification string from 172.17.0.43

Jan 10 20:38:50 tower sshd[21145]: Did not receive identification string from 172.17.0.43

Jan 10 20:38:50 tower sshd[21150]: Accepted password for root from 172.17.0.43 port 39079 ssh2

Jan 10 20:38:50 tower sshd[21151]: Accepted password for root from 172.17.0.43 port 39080 ssh2

Jan 10 20:38:50 tower sshd[21150]: error: Received disconnect from 172.17.0.43: 10:

Jan 10 20:38:50 tower sshd[21151]: error: Received disconnect from 172.17.0.43: 10:

Jan 10 20:38:55 tower emhttp: read_line: client closed the connection

Jan 10 20:38:55 tower sshd[21251]: Did not receive identification string from 172.17.0.43

Jan 10 20:38:55 tower sshd[21252]: Did not receive identification string from 172.17.0.43

Jan 10 20:38:55 tower sshd[21260]: Accepted password for root from 172.17.0.43 port 39117 ssh2

Jan 10 20:38:55 tower sshd[21259]: Accepted password for root from 172.17.0.43 port 39116 ssh2

Jan 10 20:38:55 tower sshd[21260]: error: Received disconnect from 172.17.0.43: 10:

Jan 10 20:38:55 tower sshd[21259]: error: Received disconnect from 172.17.0.43: 10:

Jan 10 20:39:00 tower emhttp: read_line: client closed the connection

Jan 10 20:39:00 tower sshd[21421]: Did not receive identification string from 172.17.0.43

Jan 10 20:39:00 tower sshd[21422]: Did not receive identification string from 172.17.0.43

Jan 10 20:39:00 tower sshd[21423]: Accepted password for root from 172.17.0.43 port 39141 ssh2

Jan 10 20:39:00 tower sshd[21428]: Accepted password for root from 172.17.0.43 port 39142 ssh2

Jan 10 20:39:00 tower sshd[21428]: error: Received disconnect from 172.17.0.43: 10:

Jan 10 20:39:00 tower sshd[21423]: error: Received disconnect from 172.17.0.43: 10:

Jan 10 20:39:05 tower emhttp: read_line: client closed the connection

Jan 10 20:39:05 tower sshd[21593]: Did not receive identification string from 172.17.0.43

Jan 10 20:39:05 tower sshd[21594]: Did not receive identification string from 172.17.0.43

Jan 10 20:39:05 tower sshd[21597]: Accepted password for root from 172.17.0.43 port 39177 ssh2

Jan 10 20:39:05 tower sshd[21600]: Accepted password for root from 172.17.0.43 port 39178 ssh2

Jan 10 20:39:05 tower sshd[21597]: error: Received disconnect from 172.17.0.43: 10:

Jan 10 20:39:05 tower sshd[21600]: error: Received disconnect from 172.17.0.43: 10:

Jan 10 20:39:10 tower emhttp: read_line: client closed the connection

Jan 10 20:39:10 tower sshd[21769]: Did not receive identification string from 172.17.0.43

Jan 10 20:39:10 tower sshd[21768]: Did not receive identification string from 172.17.0.43

Jan 10 20:39:10 tower sshd[21775]: Accepted password for root from 172.17.0.43 port 39336 ssh2

Jan 10 20:39:10 tower sshd[21770]: Accepted password for root from 172.17.0.43 port 39334 ssh2

Jan 10 20:39:10 tower sshd[21775]: error: Received disconnect from 172.17.0.43: 10:

Jan 10 20:39:10 tower sshd[21770]: error: Received disconnect from 172.17.0.43: 10:

Jan 10 20:39:15 tower sshd[21869]: Did not receive identification string from 172.17.0.43

Jan 10 20:39:15 tower sshd[21870]: Did not receive identification string from 172.17.0.43

Jan 10 20:39:15 tower sshd[21875]: Accepted password for root from 172.17.0.43 port 39385 ssh2

 

How did you get this syslog? I'm pretty sure stopping the array as you said you did should result in syslog entries.

 

How did you determine the drive was disabled around 614 this morning?

  • Author

I putty'ed into the system and

 

cat /var/log/syslog

 

On the image I posted the first box on the right sees 6:14am.  Also I have the notifications setup and I received an e-mail at:615am saying

 

Event: unRAID Parity disk SMART failure

Subject: Alert: Parity disk failed SMART health check

Description: HGST_HMS5C4040ALE640_PL2331LAGUHAUJ (sdk)

Importance: alert

 

Well, the usual advise is to replace the drive, and then see if you can get the old drive to pass a preclear before you try to use it again. I was just trying to make sure you didn't have a loose connection or something.

  • Author

I was thinkinthe same thing that a connector might not be connected properly.  I will get another drive and see what I can do. when I get home and am able to physicaly look at the machine.

 

I really appricate all the help as always everyone here is very helpful.

 

Thank you

Archived

This topic is now archived and is closed to further replies.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.