(SOLVED) Disk 1 is Disabled in Unraid, Contents Emulated

[WolfTech12]

Version of Unraid: 6.8.3 2020-03-05

Plugins:

• Community Applications - 2021.03.02
• Unassigned Devices - 2021.02.21a
• Dynamix System Buttons - 2020.06.20
• Dynamix System Information - 2020.06.21

Hardware:

• AUSTek 970 Pro Gaming/Aura Motherboard
• AMD FX-4300 Quad -Core Processor
• 8 GB DDR3 Memory
• LSI SAS 9211-8i 8-port 6Gb/s PCI-E Internal HBA in IT Mode
• Drives are connected via Mini-SAS to SATA connectors to Rosewill Hot-Swappable Cages.

Problem:

• I decided to check my Unraid dashboard after honestly neglecting it for awhile and noticing I was having a few issues playing music from Plex. I saw that Drive 1 in my array (which holds most of my media) was disabled with a red dot in the GUI. The message said "Device Disabled, Contents Emulated". This drive is one of my newer 4TB WD Red drives too. I'm trying to get some help on what exactly the issue is and how to properly fix it without losing data (if possible).

 

Current Steps Taken:

• Ran a short SMART test on Drive 1; returned with no errors according to GUI.
• Ran a long/full SMART test on Drive 1; returned with no errors according to GUI.
• I stopped the array and restarted it in Maintenance Mode.
• Ran a file system check on Drive 1 with the "-n" modifier/option from the GUI.

  • Phase 1 - find and verify superblock...
    Phase 2 - using internal log
            - zero 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
            - process newly discovered inodes...
    Phase 4 - check for duplicate blocks...
            - setting up duplicate extent list...
            - check for inodes claiming duplicate blocks...
            - agno = 0
            - agno = 1
            - agno = 3
            - agno = 2
    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...
    No modify flag set, skipping filesystem flush and exiting.

     

 

This is all I have done so far. Not sure exactly where to go from here. I appreciate any and all help.

mediaserv-ms2-diagnostics-20210421-1259(anon).zip

Edited April 25, 2021 by WolfTech12
Issue has been SOLVED

[trurl]

3 minutes ago, WolfTech12 said:

check my Unraid dashboard after honestly neglecting it for awhile

You MUST configure Notifications to alert you immediately by email or other agent as soon as a problem is detected. Don't let a neglected problem become multiple problems and data loss.

 

Not clear there was any need to check the filesystem, and we really can't tell much about your filesystems since the Diagnostics you posted are with the array stopped.

 

Start the array and post new diagnostics.

[WolfTech12]

I will make sure to setup notifications after this.

 

I started the array and reran the diagnostics. (1339)

mediaserv-ms2-diagnostics-20210421-1339.zip

 

Edit: I also attached an earlier diagnostic I ran that might help. I think I ran this one before I took the array offline originally, but I'm not 100% sure. (1158)

 

mediaserv-ms2-diagnostics-20210421-1158(anon).zip

Edited April 21, 2021 by WolfTech12
Adding another diag file.

[trurl]

Emulated disk1 mounts and SMART seems OK. Syslog from your earlier diagnostics suggest a connection problem. Check connections, both ends, power and SATA, including splitters.

 

You can rebuild to the same disk if you want or keep the original as it is and rebuild to a spare.

 

https://wiki.unraid.net/Manual/Storage_Management#Replacing_disks

[WolfTech12]

Thank you for your help trurl! I was able to get around to rebuilding the disk yesterday (took the time to do some maintenance on the inside of the box as well).  Array looks happy now and I got notifications setup to warn me of issues like this in future.