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.

cache pool unmountable

Featured Replies

I had a bad upgrade to unraid 6.10.0-rc4, and during so my flash drive failed. Luckily I backed it up and I was able to get unraid 6.9.2 back up. The only problem is that my cache pool is showing up unmountable: no file system. Should I just format the drives and start over? 

cache.jpg

tower-diagnostics-20220321-1725.zip

19 minutes ago, minhquan07 said:

I had a bad upgrade to unraid 6.10.0-rc4, and during so my flash drive failed. Luckily I backed it up and I was able to get unraid 6.9.2 back up. The only problem is that my cache pool is showing up unmountable: no file system. Should I just format the drives and start over? 

Had the same issue yesterday evening doing the update.

 

 

I have the same problem since this night but using 6.9.2. I'm just panicking a bit as I just got all my dockers up for the first time and have no backup yet. Does this sort of "thing" happen often? My cache drives are brand new and I was hoping that two cache drives as RAID should give some security but potentially losing all my app data now and than doesn't seem to be a desirable situation.

  • Community Expert
10 hours ago, minhquan07 said:

up unmountable: no file system.

Mar 21 17:21:37 Tower kernel: BTRFS warning (device sdn1): chunk 5466226688 missing 1 devices, max tolerance is 0 for writable mount

Unraid is only detecting two pool members, the other one is being detected as new, and pool is mount because it wasn't redundant (or at least part of it).

 

Mar 21 17:16:54 Tower kernel: BTRFS: device fsid 80736f28-b651-4f12-a638-45f718b8a9df devid 3 transid 856585 /dev/sdk1 scanned by udevd (1804)
Mar 21 17:16:54 Tower kernel: BTRFS: device fsid f49492cf-a1df-488c-a31a-19d03ad6f2b0 devid 1 transid 38 /dev/sdu1 scanned by udevd (1866)
Mar 21 17:16:54 Tower kernel: BTRFS: device fsid 80736f28-b651-4f12-a638-45f718b8a9df devid 2 transid 856585 /dev/sdn1 scanned by udevd (1822)

 

And the above confirms that sdu is not part of the same pool, fsid is not the same, something happened to this device and it was re-formatted as a different (and newer) filesystem.

  • Community Expert
2 hours ago, KingCrab said:

Does this sort of "thing" happen often?

It doesn't happen without a reason, but would need the diags to see it, and if you want to post that please start your own thread.

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.