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) Disk suddenly unmountable

Featured Replies

Hello, my data disk is suddenly showing as Unmountable: Unsupported or no file system. I have tried rebooting and replacing the sata cable with no luck. I ran xfs_repair with the -n option and the result is below. Can someone please provide guidance on how I can repair the issue without losing data? I have important files backed up, but would rather save this if possible.

 



    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
    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...
    invalid start block 0 in record 0 of bno btree block 0/1
    invalid start block 0 in record 255 of cnt btree block 0/2068651
    agf_freeblks 108515719, counted 108515715 in ag 0
    agi unlinked bucket 12 is 6212940 in ag 0 (inode=6212940)
    sb_icount 529856, counted 530112
    sb_ifree 318, counted 95
    sb_fdblocks 534365589, counted 533859465
            - 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
    bad nblocks 18446744073709551577 for inode 4701659101, would reset to 0
    data fork in ino 4769315924 claims free block 596172975
            - 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 = 3
            - agno = 1
            - agno = 2
    bad nblocks 18446744073709551577 for inode 4701659101, would reset to 0
    No modify flag set, skipping phase 5
    Phase 6 - check inode connectivity...
            - traversing filesystem ...
            - traversal finished ...
            - moving disconnected inodes to lost+found ...
    disconnected inode 6212940, would move to lost+found
    Phase 7 - verify link counts...
    would have reset inode 6212940 nlinks from 0 to 1
    No modify flag set, skipping filesystem flush and exiting.

 

tower-diagnostics-20241124-2205.zip

Edited by ElTecnico

Solved by JorgeB

  • Community Expert
  • Solution

Run it again without -n, or nothing will be done, and if it asks for -L use it.

  • Author
5 hours ago, JorgeB said:

Run it again without -n, or nothing will be done, and if it asks for -L use it.

This solved my issue, thank you!

  • ElTecnico changed the title to (Solved) Disk suddenly unmountable

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.