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: No file system (XFS)

Featured Replies

Hi,

 

I got the error (Unmountable: No file system) on Disk 2 the same time when Disk 1 was rebuilding. (After facing this issue)

I waited for Disk 1 rebuild to finish, then restart the array/server, but the Unmountable message on Disk 2 still appears.

 

I went through this documentation and executed this command (-nv) in maintenance mode and got the below response:

Phase 1 - find and verify superblock...
        - block cache size set to 707800 entries
Phase 2 - using internal log
        - zero log...
zero_log: head block 654523 tail block 654519
ALERT: The filesystem has valuable metadata changes in a log which is being
ignored because the -n option was used.  Expect spurious inconsistencies
which may be resolved by first mounting the filesystem to replay the log.
        - scan filesystem freespace and inode maps...
        - found root inode chunk
Phase 3 - for each AG...
        - scan (but don't clear) agi unlinked lists...
        - process known inodes and perform inode discovery...
        - agno = 0
        - agno = 1
        - agno = 2
        - agno = 3
        - agno = 4
        - agno = 5
        - agno = 6
        - agno = 7
        - process newly discovered inodes...
Phase 4 - check for duplicate blocks...
        - setting up duplicate extent list...
        - check for inodes claiming duplicate blocks...
        - agno = 0
        - agno = 3
        - agno = 6
        - agno = 1
        - agno = 2
        - agno = 4
        - agno = 7
        - agno = 5
No modify flag set, skipping phase 5
Phase 6 - check inode connectivity...
        - traversing filesystem ...
        - agno = 0
        - agno = 1
        - agno = 2
        - agno = 3
        - agno = 4
        - agno = 5
        - agno = 6
        - agno = 7
        - traversal finished ...
        - moving disconnected inodes to lost+found ...
Phase 7 - verify link counts...
Maximum metadata LSN (1:654601) is ahead of log (1:654523).
Would format log to cycle 4.
No modify flag set, skipping filesystem flush and exiting.

        XFS_REPAIR Summary    Wed Aug  7 21:00:27 2019

Phase		Start		End		Duration
Phase 1:	08/07 21:00:13	08/07 21:00:13
Phase 2:	08/07 21:00:13	08/07 21:00:14	1 second
Phase 3:	08/07 21:00:14	08/07 21:00:21	7 seconds
Phase 4:	08/07 21:00:21	08/07 21:00:21
Phase 5:	Skipped
Phase 6:	08/07 21:00:21	08/07 21:00:27	6 seconds
Phase 7:	08/07 21:00:27	08/07 21:00:27

Total run time: 14 seconds

 

I would like your suggestion in how I can proceed with fixing this issue?

Please let me know if you require any further information.

Thank you.

 

 

Unraid Version: 6.7.2

CPU: AMD Ryzen 7 2700X

Mobo: MSI X470 GAMING PLUS (MS-7B79)

Memory: 16 GiB DDR4

 

image.thumb.png.555c1f194fdddd3542d908da88448eec.png

 

tower-diagnostics-20190807-1747.zip tower-smart-20190807-2047.zip

Edited by HAMANY

  • Community Expert

You should rerun the xfs_repair without the -n option but add the -L option.    After doing that the disk should be mountable again.

  • Author
4 hours ago, itimpi said:

You should rerun the xfs_repair without the -n option but add the -L option.    After doing that the disk should be mountable again.

Thank you.

The disk is back to normal now :)

Archived

This topic is now archived and is closed to further replies.

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.