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.

Wrong Pool State - too many wrong or missing devices

Featured Replies

I've made a big mistake and I need some help undoing it.

 

I had two 1TB NVME drives ("nvme0n1" and "nvme1n1") in a BTRFS pool ("nvme"). I wanted to separate those two drives into their own individual pools and did it without consulting the docs (big mistake). The steps I took:

1. Stop array

2. Create new pool called "nvmecache"

3. Unassign "nvmen0n1" from "nvme"

4. Assign "nvme0n1" to "nvmecache"

5. Start array

 

After starting the array I started getting warnings about the "nvme" pool missing a device "nvme0n1" and realized I had done this all wrong. So then I took the following steps:

1. Stop array

2. Unassign "nvme0n1" from "nvmecache"

3. Delete "nvmecache" pool

4. Reassign "nvme0n1" to "nvme" pool

 

But now I'm not able to start the array due to the warning in the title: Wrong Pool State - "nvme" - too many wrong or missing devices.

 

How do I get "nvme0n1" back into the "nvme" pool?

 

Output of "btrfs fi show":

warning, device 2 is missing
Label: none  uuid: 22c8d4c7-5b45-4a53-935c-4a3de560b69d
        Total devices 1 FS bytes used 180.03MiB
        devid    1 size 232.89GiB used 4.03GiB path /dev/sdf1

Label: none  uuid: 65338527-9b1d-46b4-bede-49416cdc67c5
        Total devices 2 FS bytes used 477.48GiB
        devid    1 size 931.51GiB used 521.03GiB path /dev/nvme1n1p1
        *** Some devices missing

Label: none  uuid: 651ae8a2-a9c4-4d74-a2f1-b6813c030b32
        Total devices 1 FS bytes used 144.00KiB
        devid    1 size 931.51GiB used 2.02GiB path /dev/nvme0n1p1

 

Solved by PlasmaEye

  • Author
  • Solution

I got it to work. I went into the "nvme" pool config at /boot/config/pools and noticed that the "diskFsProfile" was set to "single". I changed that to "multiple" which was incorrect but that got Unraid to update that profile with the correct value of "raid1". After that it took "nvme0n1" and started a btrfs balance operation and everything came back up. 

 

The "nvme" pool still had a missing device on it so I did have to run "btrfs dev del missing /mnt/nvme" once the array was back up.

 

I've attached the diagnostics as well.

atlas-diagnostics-20250413-0741.zip

Edited by PlasmaEye
added extra step after array was up

  • Community Expert

Looks good at first sight, I assume it's resolved?

  • Author

Yep, resolved.

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.