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.

UNMOUNTABLE: NO POOL UUID

Featured Replies

In an attempt to replace my existing cache pool disks, I seem to have lost the btrfs filesystem and data on the previous cache pool disks. I am hoping someone can assist me in recovering the btrfs filesystem and/or data on the previous pool disks.

 

Details:

  • Previously working cache pool disk: 2 Sandisk 480GB SSDs with btrfs filesystem (device ids: sdc, sdf)
  • New cache pool disks: 2 WD 2TB NVMEs (device ids: nvme0n1, nvme1n1)


Here is what I did to cause this:

  1. Stopped array
  2. Added Cache 3 and Cache 4 devices to the pool, 2TB NVME drives (device ids: nvme0n1, nvme1n1)
  3. Started array (cache healthy and data present)
  4. Waited about an hour for what I thought was a copy of data across all of the new disks
  5. Stopped array
  6. Removed Cache 2 device from cache pool, Sandisk SSD (device id: sdf)
  7. Started array (cache healthy and data present)
  8. Stopped array
  9. Removed Cache 1 device from cache pool, Sandisk SSD (device id: sdc)
  10. Started array (cache unhealthy and data not present)
  11. Stopped array
  12. Noticed that the new NVME disks were not yet formatted, formatted these new disks
  13. Started array (cache healthy and data not present)
  14. Stopped array
  15. Removed the new NVME disks from the cache pool, leaving no cache
  16. Started the array
  17. Stopped the array
  18. Added the old SSD disks back to the cache pool in their original device locations
  19. Started the array (cache unhealthy with error Unmountable: No pool uuid)

 

Investigation/remediation attempts:
 

btrfs fi show

Label: none  uuid: 0ea24342-ffd0-439a-a136-2105a9c78903
        Total devices 1 FS bytes used 684.00KiB
        devid    1 size 1.00GiB used 126.38MiB path /dev/loop2

Label: none  uuid: e2f6c5b4-203f-4e32-ad8f-9c4c99c3f6a3
        Total devices 2 FS bytes used 768.24MiB
        devid    1 size 1.82TiB used 2.03GiB path /dev/nvme0n1p1
        devid    2 size 1.82TiB used 2.03GiB path /dev/nvme1n1p1

 

btrfs check -s1 /dev/sdc1

using SB copy 1, bytenr 67108864
Opening filesystem to check...
warning, device 4 is missing
bad tree block 4770155839488, bytenr mismatch, want=4770155839488, have=0
ERROR: cannot read chunk root
ERROR: cannot open file system

 

btrfs check -s1 /dev/sdf1

using SB copy 1, bytenr 67108864
Opening filesystem to check...
warning, device 4 is missing
bad tree block 4770155741184, bytenr mismatch, want=4770155741184, have=0
ERROR: cannot read chunk root
ERROR: cannot open file system

 

btrfs-select-super -s 1 /dev/sdc1

warning, device 4 is missing
ERROR: cannot read chunk root
ERROR: open ctree failed

 

tower-diagnostics-20230405-2052.zip

Screenshot 2023-04-05 at 9.47.42 PM.png

Edited by mountaindonky
Adding screenshot

  • Community Expert

Diags are after rebooting so can't see exactly what happened, but this was likely the main mistake:

3 hours ago, mountaindonky said:

Noticed that the new NVME disks were not yet formatted, formatted these new disks

This created a new filesystem on those drives, and previous caches devices are still looking for the old one:

3 hours ago, mountaindonky said:
warning, device 4 is missing

Try this on the other device and post the output:

btrfs-select-super -s 1 /dev/sdf1

But most likely you will have to restore the pool from backups, if available

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.