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 6.11.5 - "Disk wrong" error on cache drives after array rebuild started

Featured Replies

Hello friends,

 

I'm hoping you can help me diagnose an issue I'm having with my server. I just finished pre-clearing a replacement disk and stopped the array to add it back in. (I previously physically removed the failing drive while the server was powered off, and inserted the replacement disk in the same slot.)

 

After stopping the array to add the replacement disk, and then starting it again, I now see both my cache drives with red X's. The error "disk wrong" is listed for both, but I have no idea why. I didn't mess with their config or modify them in any way. Here's the exact error notification I received:

 

Event: Unraid Cache 2 error
Subject: Alert [IH-NAS01] - Cache 2 in error state (disk wrong)
Description: Micron_M600_MTFDDAK1T0MBF_160711F4F0BB (sdh)
Importance: alert

 

Here's the full list of steps I took:

 

1. Realized disk 2 was failing, so began copying contents off on to disks 1, 3 and 4 in the array.

2. Was taking forever (10 MB/s), so I canceled the moves and decided to just rely on a rebuild instead.

3. Simultaneously working on upgrading my cache drives from 200 GB SSDs to 1 TB SSDs. Physically moved appdata and system to other disks on the array using unBALANCE. 

4. Stopped the array, unassigned both SSDs from my cache pool, and the failing disk (disk 2).

5. Powered off the server and swapped in the replacement disk 2. Also swapped in the new 1 TB SSDs while I was at it.

6. Powered on the server and re-assigned the new 1 TB SSDs to the cache pool. Note that disk 2's data is now being emulated thanks to parity.

7. Began pre-clearing new replacement disk 2.

8. Moved appdata and system to cache pool drive.

9. Though, "hey, I have TONS of space now on cache! I can move domains there too!" (previously, domains was on array)

10. Copied domains from array to cache drive (including emulated data from disk 2, thanks to parity).

11. Pre-clear finished, and stopped array to add disk back in and begin rebuild.

12. Started array, rebuild began, and that's when I saw the error states on the cache drives.

 

I'm wondering if you can help me figure out why I'm seeing these errors. FWIW, read/writes are still happening on these cache drives, but the status has me concerned. Can you help, please?

 

Diagnostics and a few screenshots (below) attached. Many thanks for your help in advance!

 

image.thumb.png.7a295548d1b4ba8777bd43c3e0839fdf.png

 

image.thumb.png.343b883659f6624a194a0ec55373db59.png

ih-nas01-diagnostics-20230715-1447.zip

Solved by JorgeB

  • Community Expert
  • Solution

You can wait until the rebuild is done, then:

 

Stop array

unassign both pool devices

start array, stop array

re-assign both pool devices

start array

 

That should do it.

  • Author

That did fix it--thank you!

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.