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.

Unraid 7.2.3 - Disabled drives; What are the troubleshooting steps to determine why?

Featured Replies

What troubleshooting steps should I take to determine if a cable or something else is causing a drive to get disabled while the array is online? Do my logs help show the reason?

I've come across my third disable drive, all connected to the same PSU, power and data cable. My setup is two RSV cages, each with 4 drives connected to the same expander card and PSU. Each drive is connected via a 4-way SF-8087 to SATA to a HP DL380 and 4 connector power cables recommended by Seasonic support. Additionally, there is a second PSU driving 12 drives and connected to the same expander card. I have no issues with those 12 drives.

I've familiarized myself with rebuilding on top of a drive by doing it twice (once was many months ago and the other a few weeks ago) but before I get into the third rebuild, I want to figure out what the real issue is. After just finishing my second rebuild, I started the array and within minutes a different drive got the red x. This third drive is on the same power cable as the previous two drives. I changed out the data cable before the second rebuild. It seems obvious to me that I should change out the power cable this time. I don't want to keep going around guessing at the culprit and am hoping to narrow down the real issue. I asked about this in Discord and reading the logs was the answer. So, my logs are attached because I'm not sure what I'm looking for. These logs are from minutes after the third drive became disabled and even though its been a couple weeks I have only stopped the array (no SMART test and no shutdown at this time). Thank you for reading and I appreciate any help the community can provide.

diagnostics-20260121-1709.zip

Solved by trurl

  • Community Expert
Jan 21 16:33:48 hirsute-theater kernel: critical medium error, dev sdu, sector 0 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2

Add SMART attribute notifications: 1, 200 for each of your WD drives.

Do an extended SMART self-test on disk10

  • Author
16 hours ago, trurl said:

Add SMART attribute notifications: 1, 200 for each of your WD drives.

Do an extended SMART self-test on disk10

I added notifications. When I added those notifications I got:

raw read error rate is 1 for disk10

raw read error rate is 6 for disk12

Around the time the SMART test ended I got:

multi zone error rate is 1 for disk10

Extended SMART results are attached.

smart-20260208-0817.zip

  • Community Expert
  • Solution

Might be OK, but it was a disk problem not a connection problem that caused it to be disabled.

Do you have another disk you could rebuild to?

  • Author

Not currently. The ones giving issue are my first drives from my QNAP. I'd like to replace them, but costs have been a bit high. I'd like to go up to 14TB. I'll start getting more serious on my search instead of looking for a unicorn in this market.

How can you tell it's not a connection problem?

  • Community Expert
14 minutes ago, NAS-t_Hirsute said:

How can you tell it's not a connection problem?

23 hours ago, trurl said:
Jan 21 16:33:48 hirsute-theater kernel: critical medium error, dev sdu, sector 0 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2

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.

Guest
Reply to this topic...

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.