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.

Array Disk Unmountable: Unsupported or no file system

Featured Replies

Hi everyone,

 

one of my array disks became "Unmountable: Unsupported or no file system". What should i do? There was for sure data on it. Replace the drive an start parity check with corrections on? 

 

I'm running unRAID 6.12.10 on the following hardware:

Dell T430

Intel® Xeon® CPU E5-2690 v3 @ 2.60GHz

4x SK-Hynic HMA42GR7MFR4N-TF, 16 GiB DDR4 @ 2133 MT/s

2x HDD for Parity

19x HDD/SSD Array Disks

2x SSD for Cache

 

diagnostics-20241005-1225.zip

Solved by JorgeB

  • Author

Hi @JorgeB,

 

thanks for replying. I let it run via Webgui.

 

Phase 1 - find and verify superblock...
Phase 2 - using internal log
        - zero log...
ERROR: The filesystem has valuable metadata changes in a log which needs to
be replayed.  Mount the filesystem to replay the log, and unmount it before
re-running xfs_repair.  If you are unable to mount the filesystem, then use
the -L option to destroy the log and attempt a repair.
Note that destroying the log may cause corruption -- please attempt a mount
of the filesystem before doing this.

 

  • Author

Okay, i did. After that, i stopped the array and started it normally.  The disks starts ok for the array. Should i run now a parity check?

 

Phase 1 - find and verify superblock...
Phase 2 - using internal log
        - zero log...
ALERT: The filesystem has valuable metadata changes in a log which is being
destroyed because the -L option was used.
        - scan filesystem freespace and inode maps...
clearing needsrepair flag and regenerating metadata
invalid start block 2563684048 in record 238 of bno btree block 0/27716645
agi unlinked bucket 54 is 29097206 in ag 0 (inode=29097206)
sb_ifree 540, counted 547
sb_fdblocks 54647131, counted 112435777
        - 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 = 2
        - agno = 3
        - agno = 1
Phase 5 - rebuild AG headers and trees...
        - reset superblock...
Phase 6 - check inode connectivity...
        - resetting contents of realtime bitmap and summary inodes
        - traversing filesystem ...
        - traversal finished ...
        - moving disconnected inodes to lost+found ...
disconnected inode 29097206, moving to lost+found
Phase 7 - verify and correct link counts...
Maximum metadata LSN (46:835895) is ahead of log (1:2).
Format log to cycle 49.
done

 

You should now restart the array in normal mode and the drive should now mount.

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.