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.3.4 - Wrong Pool State - Invalid Config

Featured Replies

Hello,

I'm hoping someone here can help.

So I have a couple of zfs pools. One in particular (named Mediafun) is made up of 13 devices. I had some errors show up on one of them, Device 12 (sdn). I kept using it until the system removed the disk.

I ran a quick SMART test on that disk that came back with no errors. I tried to reintroduce it, and the resilver process started but was moving extremely slow (0.3%, 70 days to go) and didn't run for too long before the drive was shown as removed again by the system and seemed to stop the resilver process.

In the meantime I had a second drive, Device 5 (sdt), that started stating it had errors. I decided to shut down the server and check to see if the same breakout cable was connected to both drives as I have had loose/bad cables in the past. Device 12 (that was previously removed by the system) is connected to a breakout cable and Device 5 has a sata cable connected directly to a Sata port on the motherboard. I re-seated only those two sata cables and powered up the server.

Now all drives are showing as offline and when I try to start the array I'm receiving "Wrong Pool State mediafun - invalid config". Device 12 (sde) still shows as unassigned.

I've tried rebooting as well as assigning the drive that was removed (Device 12) back into that same slot. I'm wondering if stopping it during the resilver process was problematic as I'm seeing "sdn1/old" as OFFLINE and "sdn1" as UNAVAIL when I run zpool import.

Any suggestions would be welcome.

*******************************

I ran lsblk -o name,size,model,serial

-Result was all the drives are seen.

When I run "zpool import" I see the below:

pool: mediafun

id: 2954754274543482954

state: DEGRADED

status: One or more devices were being resilvered.

action: The pool can be imported despite missing or damaged devices. The

fault tolerance of the pool may be compromised if imported.

config:

mediafun DEGRADED

raidz2-0 DEGRADED

sde1 ONLINE

sdf1 ONLINE

sda1 ONLINE

sds1 ONLINE

sdt1 ONLINE

sdb1 ONLINE

sdd1 ONLINE

sdj1 ONLINE

sdh1 ONLINE

sdk1 ONLINE

sdo1 ONLINE

replacing-11 UNAVAIL insufficient replicas

sdn1/old OFFLINE

sdn1 UNAVAIL

sdm1 FAULTED corrupted data

When I run zpool status -v mediafun I receive the following:

pool: mediafun

state: DEGRADED

status: One or more devices is currently being resilvered. The pool will

continue to function, possibly in a degraded state.

action: Wait for the resilver to complete.

scan: resilver in progress since Mon Oct 26 07:52:13 2026

0B / 108T scanned, 0B / 108T issued

0B resilvered, 0.00% done, no estimated completion time

config:

NAME STATE READ WRITE CKSUM

mediafun DEGRADED 0 0 0

raidz2-0 DEGRADED 0 0 0

sde1 ONLINE 0 0 4

sdf1 ONLINE 0 0 4

sda1 ONLINE 0 0 4

sds1 ONLINE 0 0 4

sdt1 ONLINE 0 0 4

sdb1 ONLINE 0 0 4

sdd1 ONLINE 0 0 4

sdj1 ONLINE 0 0 4

sdh1 ONLINE 0 0 4

sdk1 ONLINE 0 0 4

sdo1 ONLINE 0 0 4

replacing-11 UNAVAIL 0 0 0 insufficient replicas

sdn1/old OFFLINE 0 0 0

sdn1 REMOVED 0 0 0

7355020672882961856 FAULTED 0 0 0 was /dev/sdm1

I've been trying to work through Claude but things are getting pretty in the weeds for me. Part of what its come back with is it thinks that Device 13 (sdm) somehow had it's label changed so it's GUID is different than the GUID ZFS is expecting. I'm still unsure why anything for that drive may have been changed.

In it's words:

Two different records are involved.

  • The pool’s config (zdb -e -C mediafun) says position 12 is a disk with guid 7355020672882961856 at /dev/sdm1. This is what ZFS expects, and it’s the value we want. The config is read from the labels of the healthy disks, so it is intact. It also shows that the attempted replace on sdm1 never made it into the pool’s config.

  • The label on the disk itself (zdb -l /dev/sdm1) says guid: 8450324955016200314. That is the stub label that overwrote the original.

When ZFS opens sdm1, it compares the guid in the disk’s own label to the guid the config expects. 8450324955016200314 isn’t 7355020672882961856, so ZFS decides this isn’t the right disk and marks it FAULTED with “corrupted data”. The disk is fine. Its label is simply wrong.

This is the mismatch the reconstruction would fix. The goal is to make sdm1’s label say 7355020672882961856, so it matches what the config already says.

I realize this is a dump of info, let me know if I can clarify anything.

Diagnostics are attached.

Screenshot 2026-10-26 125858.png

Screenshot 2026-10-26 125740.png

mediaunraid-diagnostics-20261026-1226.zip

Edited by khior
More information and clarification

  • khior changed the title to Unraid 7.3.4 - Wrong Pool State - Invalid Config
  • Community Expert

The pool should still be recoverable. 11 of the 13 devices are fine and raidz2 can survive two missing devices, but to reimport the the pool using the GUI is best to clear the repoacling line.

With the pool imported using the CLI, post the ouptu from zpool status -g mediafun

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.