Unmountable: No file system (SOLVED)

[Prech]

I recently had a 3TB drive fail , and I replaced it with a 4TB drive.  I performed the preclear on the drive and then added the drive to the array and it performed the rebuild.

 

The array shows online with no errors.  The shares are not reporting any errors, but when on the main page I see Unmountable: No file system instead of the drive size and used details.

 

I am not sure what details are important to investigate/resolve this issue. 

I am using Unraid Version 6.8.3 

 

 

If more details are required to investigate, please advise what I need to include.  

 

Thank you

ST4000VN008-2DR166_ZDH7WSPQ-20200509-1457 (sdb).txt

[itimpi]

I suspect the ‘emulated’ disk was showing as unmountable before doing the rebuild?    The rebuild process does not fix file system corruption - you need to follow the procedure shown here in the online documentation to fix file system level corruption.

[Prech]

I ran the XFS_Repair status as outlined and received the below:

 

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...
        - 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 = 3
        - agno = 1
        - agno = 0
        - 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...
Maximum metadata LSN (1:35050) is ahead of log (1:35037).
Would format log to cycle 4.
No modify flag set, skipping filesystem flush and exiting.

sorry, I am not familiar with what this is telling me

 

[itimpi]

That ran a check only as you did not remove the -n flag (which is what the last line tells you), but the output looks good as no serious corruption is being reported.   Rerun without the -n flag and add the -L flag to actually repair the file system.
 

when you have done that stop the array, and restart in normal mode and now you should find the disks mounts normally.

[Prech]

Thank you very much for you help itimpi.