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.

Unraid 6.9.2 - Issue With 4 Disks – Reporting Unmountable:not mounted

Featured Replies

Currently, four disks in the array report the error message “Unmountable:not mounted”.  I tried to repair the disks via the GUI in maintenance mode using reiserfs and xfs_repair but did not succeed. 

 

Also, Disk 5 and Parity 2 report as disabled after last reboot.

 

I don’t know what is wrong?  I have run the system over 40 days and have seen no other disk fallouts.  Any ideas?

 

 

 

sanblaster-diagnostics-20210727-1744.zip

Unraid_6.9.2_Array_Errors.png

Edited by shado
Incorrect Image

  • Author

I followed the guidelines of the wiki.  I have ran the checks again and posted the results for disks 5, 6, 7 and 11.

 

Disk 5

reiserfsck

reiserfsck 3.6.27

 

Will read-only check consistency of the filesystem on /dev/md5

Will put log info to 'stdout'

Failed to open the device '/dev/md5': Unknown code er3k 127

 

=====================================================================

 

Disk 6

xfs_repair -n

Phase 1 - find and verify superblock...

Phase 2 - using internal log

        - zero log...

Log inconsistent or not a log (last==0, first!=1)

empty log check failed

zero_log: cannot find log head/tail (xlog_find_tail=22)

        - scan filesystem freespace and inode maps...

sb_icount 64, counted 32

sb_ifree 61, counted 29

sb_fdblocks 2424059642, counted 2441087411

        - 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

        - agno = 8

        - agno = 9

        - 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 = 1

        - agno = 3

        - agno = 4

        - agno = 6

        - agno = 5

        - agno = 8

        - agno = 9

        - agno = 7

No modify flag set, skipping phase 5

Phase 6 - check inode connectivity...

        - traversing filesystem ...

        - traversal finished ...

        - moving disconnected inodes to lost+found ...

Phase 7 - verify link counts...

Maximum metadata LSN (1:78) is ahead of log (0:0).

Would format log to cycle 4.

No modify flag set, skipping filesystem flush and exiting.

 

=====================================================================

 

Disk 7

Phase 1 - find and verify superblock...

bad primary superblock - bad CRC in superblock !!!

 

attempting to find secondary superblock...

....................................

 

Note:  The disk check has been running for over six hours

 

=====================================================================

 

Disk 11

Phase 1 - find and verify superblock...

bad primary superblock - bad CRC in superblock !!!

 

attempting to find secondary superblock...

.found candidate secondary superblock...

verified secondary superblock...

would write modified primary superblock

Primary superblock would have been modified.

Cannot proceed further in no_modify mode.

Exiting now.

 

Edited by shado

  • Community Expert

Disks 6 and 11 should be fixable if you run xfs_repair again without -n, the other two don't look so good, for disk5 you can check if the actual disk mounts.

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.