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 drive "Unmountable: unsupported or no file system" after upgrade from 7.0.1 to 7.2.3

Featured Replies

I've been trying to upgrade to 7.2.3, but kept getting an error indicating that my USB flash drive is likely failing. I upgraded to a new SD Card/USB Reader, transferred the license, and everything seemed to be working fine.

I ended up upgrading to 7.2.3, but then when I tried to start the array, all my dockers disappeared. My cache drive is now showing as unmountable. I tried stopping the array, removing the cache, starting, then stopping and adding the drive again, with no luck. I also tried a suggestion from fix common problems while running the array in maintenance mode, and got the following error:

mount -o rescue=all,ro /dev/sde1 /temp

mount: /temp: wrong fs type, bad option, bad superblock on /dev/sde1, missing codepage or helper program, or other error.

dmesg(1) may have more information after failed mount system call.

Any help would be really appreciated.

image.png

tower-diagnostics-20251222-2136.zip

Solved by JorgeB

  • Community Expert

Post the output from

btrfs fi show

and

fdisk -l /dev/sde

and

blkid /dev/sde1

  • Author

This is what I get when the array is started:

image.png

  • Community Expert

The device has no partition. Any idea how that happened?

If it's just the partition missing, and the device wasn't wiped, it may be recoverable.

Type sfdisk /dev/sde and then type 2048 and hit enter and post the output; don't type anything else for now.

  • Author

I have no idea how this happened. I was using my dockers just fine earlier in the day. Restored my flash drive backup to the new drive, installed it, started the array, everything was fine. After the upgrade to 7.2.3 I started having this issue.

This what I get when executing the commands above:

image.png

  • Community Expert
  • Solution

Certainly not the update; it could have been the reboot

Type N and enter to keep the signature, then type write and enter to save the changes, and post again the output from btrfs fi show

  • Author

Thanks for the help. Here's what it's showing:

image.png

  • Community Expert

Now reimport that pool

on main click on the first device for that pool and then "remove pool"

back on main, create a new pool with the same name and 1 slot

assign the pool device, leave the filesystem set to auto

start the array to import the pool and post new diags

  • Author

That worked! Thank you so much. The cache drive is visible again and I'm able to access my dockers. Not sure if anything else is broken along the way, but uploading the diagnostics for reference.

Happy holidays and appreciate the help on this.

tower-diagnostics-20251224-1343.zip

  • Community Expert

Looks OK, but btrfs is detecting some data corruption on the pool. Recommend scrubbing it and also running memtest

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.