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.

[Solved] Unmountable: Unsupported or no file system

Featured Replies

I screwed up and unintentionally added nvme0n1 to my cache pool when it should only be a single drive - sdf. I removed the nvme drive and set the pool back to 1, however, I get the message "Unmountable: Unsupported or no file system" and can't proceed without it asking me to format. Is there any way around this without losing the data on that drive?

image.thumb.png.abb2d81bcd6b12f24efef1938185e053.png

server-diagnostics-20230201-1958.zip

Edited by squishee

Solved by JorgeB

  • Community Expert
  • Solution

With all the config changes you've made the drive was wiped with wipefs, you can try running xfs_repair to see if it can recover from a backup superblock:

 

xfs_repair -v /dev/sdf1

 

Note the one in the end

  • Author

Thanks Jorge. I'm not completely clear on what to do next. Here's the output:

root@server:~# xfs_repair -v /dev/sdf1
Phase 1 - find and verify superblock...
bad primary superblock - bad magic number !!!

attempting to find secondary superblock...
.found candidate secondary superblock...
verified secondary superblock...
writing modified primary superblock
        - block cache size set to 1530184 entries
sb realtime bitmap inode value 18446744073709551615 (NULLFSINO) inconsistent with calculated value 129
resetting superblock realtime bitmap inode pointer to 129
sb realtime summary inode value 18446744073709551615 (NULLFSINO) inconsistent with calculated value 130
resetting superblock realtime summary inode pointer to 130
Phase 2 - using internal log
        - zero log...
zero_log: head block 232788 tail block 232788
        - scan filesystem freespace and inode maps...
sb_icount 0, counted 254528
sb_ifree 0, counted 146
sb_fdblocks 122036749, counted 3811959
        - found root inode chunk
Phase 3 - for each AG...
        - scan and clear agi unlinked lists...
        - process known inodes and perform inode discovery...
        - agno = 0
        - agno = 1
        - agno = 2
        - agno = 3
        - process newly discovered inodes...
Phase 4 - check for duplicate blocks...
        - setting up duplicate extent list...
        - check for inodes claiming duplicate blocks...
        - agno = 0
        - agno = 1
        - agno = 3
        - agno = 2
Phase 5 - rebuild AG headers and trees...
        - agno = 0
        - agno = 1
        - agno = 2
        - agno = 3
        - reset superblock...
Phase 6 - check inode connectivity...
        - resetting contents of realtime bitmap and summary inodes
        - traversing filesystem ...
        - agno = 0
        - agno = 1
        - agno = 2
        - agno = 3
        - traversal finished ...
        - moving disconnected inodes to lost+found ...
Phase 7 - verify and correct link counts...
Note - stripe unit (0) and width (0) were copied from a backup superblock.
Please reset with mount -o sunit=<value>,swidth=<value> if necessary

        XFS_REPAIR Summary    Thu Feb  2 05:27:55 2023

Phase           Start           End             Duration
Phase 1:        02/02 05:27:54  02/02 05:27:54
Phase 2:        02/02 05:27:54  02/02 05:27:54
Phase 3:        02/02 05:27:54  02/02 05:27:55  1 second
Phase 4:        02/02 05:27:55  02/02 05:27:55
Phase 5:        02/02 05:27:55  02/02 05:27:55
Phase 6:        02/02 05:27:55  02/02 05:27:55
Phase 7:        02/02 05:27:55  02/02 05:27:55

Total run time: 1 second
done

 

  • Community Expert

Re-start array.

  • Author

Thank you so much! I still have one issue that I'm trying to resolve - my Docker containers are missing. I do see my appdata folder and subfolders on the cache drive. How would I go about restoring them?

  • Author

Figured out I could do this in Apps > Previous apps. Thanks again

  • squishee changed the title to [Solved] Unmountable: Unsupported or no file system

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.