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.

Disk2: device is disabled, contents emulated unraid

Featured Replies

As the title says, I get this error.  I accidently pulled out a SATA cord from one of the drive will the computer was on.

So now I am getting this error, even after I plugged the cable back in and rebooted.  I stopped the array, put it in maintenance mode, ran a check, rand smart disk check.  I dont see any errors?  This is what I get when I run repair on it.  Afterwards its still the same.  Even after I start the array no longer in maintenance mode or restart.  What do I do here?

 

 

 

Quote

root@UnRAID:/# xfs_repair -v /dev/md2
Phase 1 - find and verify superblock...
        - block cache size set to 2946456 entries
Phase 2 - using internal log
        - zero log...
zero_log: head block 495024 tail block 495024
        - scan filesystem freespace and inode maps...
        - 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
        - agno = 4
        - agno = 5
        - agno = 6
        - agno = 7
        - agno = 8
        - agno = 9
        - agno = 10
        - agno = 11
        - agno = 12
        - agno = 13
        - agno = 14
        - agno = 15
        - agno = 16
        - agno = 17
        - process newly discovered inodes...
Phase 4 - check for duplicate blocks...
        - setting up duplicate extent list...
        - check for inodes claiming duplicate blocks...
        - agno = 0
        - agno = 7
        - agno = 10
        - agno = 11
        - agno = 6
        - agno = 4
        - agno = 5
        - agno = 8
        - agno = 9
        - agno = 1
        - agno = 2
        - agno = 3
        - agno = 12
        - agno = 13
        - agno = 14
        - agno = 15
        - agno = 16
        - agno = 17
Phase 5 - rebuild AG headers and trees...
        - agno = 0
        - agno = 1
        - agno = 2
        - agno = 3
        - agno = 4
        - agno = 5
        - agno = 6
        - agno = 7
        - agno = 8
        - agno = 9
        - agno = 10
        - agno = 11
        - agno = 12
        - agno = 13
        - agno = 14
        - agno = 15
        - agno = 16
        - agno = 17
        - reset superblock...
Phase 6 - check inode connectivity...
        - resetting contents of realtime bitmap and summary inodes
        - traversing filesystem ...
        - agno = 0
        - agno = 1
        - agno = 2
        - agno = 3
        - agno = 4
        - agno = 5
        - agno = 6
        - agno = 7
        - agno = 8
        - agno = 9
        - agno = 10
        - agno = 11
        - agno = 12
        - agno = 13
        - agno = 14
        - agno = 15
        - agno = 16
        - agno = 17
        - traversal finished ...
        - moving disconnected inodes to lost+found ...
Phase 7 - verify and correct link counts...

        XFS_REPAIR Summary    Mon Jun 12 18:06:33 2023

Phase           Start           End             Duration
Phase 1:        06/12 18:06:18  06/12 18:06:18
Phase 2:        06/12 18:06:18  06/12 18:06:18
Phase 3:        06/12 18:06:18  06/12 18:06:25  7 seconds
Phase 4:        06/12 18:06:25  06/12 18:06:25
Phase 5:        06/12 18:06:25  06/12 18:06:26  1 second
Phase 6:        06/12 18:06:26  06/12 18:06:32  6 seconds
Phase 7:        06/12 18:06:32  06/12 18:06:32

Total run time: 14 seconds
done 


 

 

 

Capture.PNG

Edited by 007craft

  • Author

Replying to myself cause I figured it out from another, slightly different thread.  You need to do these steps to get it working again
 

Stop the array

Set the failed disk to "no device"

Start the array

Stop the array
Now the device will be re-enabled.   Set the disk back to the hard drive

Start the array.  The data on the drive will be rebuilt from the parity

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.