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] Health disk repoted Unmountable - No file system (32) after reboot

Featured Replies

After a reboot last night, one out my 3 disks is showing unmountable yet has a healthy status and is pretty new.  The filesystem for the good Disk1 is xfs and the unmountable Disk2 is showing xfs also, yet I get the error message in the subject line.

 

Is there a way to manually mount the drive and get it back online or do I need to format it and have it build back over?  Really trying to avoid that, but if I means I can have a "safe" config again that would be okay.

you should post your diagnostics before doing anything

  • Community Expert

Disk may be pretty new but it doesn't look very healthy, there were several read errors and they look a disk problem.

 

Before that there were 2545 sync errors corrected during the parity check, was this expected?

 

If you have a spare use it and then run xfs_repair after the rebuild finishes, if you don't want to rebuild run xfs_repair on disk2.

 

 

Additionally, you are currently under attack.

 

Numerous (and by that I mean ~1000) attempts to ssh into your server from various IP's using the user names:

 

root, user, ubnt, pi, admin, etc etc

 

 

If your server is within a DMZ on your router, remove it.  A dictionary attack will eventually succeed...  (As an aside, fix common problems plugin (even if you ignore everything else it says may or may not be wrong with your setup) will detect and alert you to this kind of attack.

 

 

  • Author

Disk may be pretty new but it doesn't look very healthy, there were several read errors and they look a disk problem.

 

Before that there were 2545 sync errors corrected during the parity check, was this expected?

 

If you have a spare use it and then run xfs_repair after the rebuild finishes, if you don't want to rebuild run xfs_repair on disk2.

 

Can you explain how to run xfs_repair on disk2... I'm assuming I need to run this via ssh into the unraid box?  If there is a document somewhere on how to run this command I'd be more than happy to read that too.

  • Community Expert

But deal with the hack attempts before starting what may be a long process with disk repair.

  • Author

I put Unraid in maintenance mode and ran xfs_repair -v /dev/md2 and got the following

 

xfs_repair -v /dev/md2
Phase 1 - find and verify superblock...
        - block cache size set to 1469768 entries
Phase 2 - using internal log
        - zero log...
zero_log: head block 1150570 tail block 1149908
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.

 

Is there any other way to try to mount that disk aside from just starting the array?  Or is that even something I want to do?

  • Author

But deal with the hack attempts before starting what may be a long process with disk repair.

 

Since I have since removed the server from the outside world so I should be safe.  After this disk issue I plan on setting up a VPN to connect to it.

  • Community Expert

I put Unraid in maintenance mode and ran xfs_repair -v /dev/md2 and got the following

 

xfs_repair -v /dev/md2
Phase 1 - find and verify superblock...
        - block cache size set to 1469768 entries
Phase 2 - using internal log
        - zero log...
zero_log: head block 1150570 tail block 1149908
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.

 

Is there any other way to try to mount that disk aside from just starting the array?  Or is that even something I want to do?

 

Disk doesn't mount, you have to use -L

  • Author

The repair completed, and the disk mounted!  It's running a parity check now.  Looks like I"m making progress but I'm not going to trust that disk and replace it as soon as I can.

 

Thanks a lot for the help!

 

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.