Unmountable disk present [SOLVED]

[Homerr]

We had a power outage in our neighborhood Friday.  I restarted the server that night and it ran a parity check which ended last night, it seemed everything was okay.  I was then in the case late last night replacing a case fan (routine, not related to the power outage) and booted the server back up.  It was late and I thought everything was okay initially.

 

This morning I noticed that Disk 2 in unmountable.  I did shutdown and reseat Disk 2's drive cage and unplug/plug the SATA cable that goes to it's backplane.  I did not replace the cable as of yet.

 

This drive is one of the 4 in my system connected to the motherboard via SATA, the others are on an LSI 9201-16i card.  I do have a 12tb disk that I can use if needed and I have one spare port on the 16i setup.

 

I did do some searching on this topic and there were serveral paths taken, I'm not sure exactly what I should do here.  I don't really know the commands in Linux but can follow directions.  

 

Can anyone help me out here?

unraid-diagnostics-20211205-0800.zip

Edited December 5, 2021 by Homerr

[trurl]

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

[Homerr]

Disk is XFS, I restarted in Maintenance mode and ran the check on the disk, result below. 

 

I'm at step 2 of Repairing a File System -

"Add any additional parameters to the Options field required that are suggested from the check phase. If not sure then ask in the forum.

The Help build into the GUI can provide guidance on what options might be applicable."

 

Is it recommended to add any parameters?  (Doing this via GUI, btw.)  Step 4 notes a -L option.

 

 

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...
block (7,74328029-74353290) multiply claimed by cnt space tree, state - 2
block (7,74169449-74170249) multiply claimed by cnt space tree, state - 2
block (7,74169449-74170249) multiply claimed by cnt space tree, state - 2
invalid start block 0 in record 51 of cnt btree block 7/2
invalid start block 0 in record 52 of cnt btree block 7/2
invalid start block 0 in record 53 of cnt btree block 7/2
invalid start block 0 in record 54 of cnt btree block 7/2
invalid start block 0 in record 55 of cnt btree block 7/2
invalid start block 0 in record 56 of cnt btree block 7/2
invalid start block 0 in record 57 of cnt btree block 7/2
invalid start block 0 in record 58 of cnt btree block 7/2
invalid start block 0 in record 59 of cnt btree block 7/2
agf_freeblks 207015525, counted 194421230 in ag 7
agi unlinked bucket 39 is 130200423 in ag 7 (inode=15162585959)
sb_ifree 8809, counted 8862
sb_fdblocks 576670704, counted 604659013
        - 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
data fork in ino 15040730579 claims free block 1953203817
data fork in ino 15162585949 claims free block 1953077194
        - 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 = 3
        - agno = 6
        - agno = 1
        - agno = 7
        - agno = 5
        - agno = 4
        - agno = 8
        - agno = 9
        - agno = 2
No modify flag set, skipping phase 5
Phase 6 - check inode connectivity...
        - traversing filesystem ...
        - traversal finished ...
        - moving disconnected inodes to lost+found ...
disconnected inode 15162585959, would move to lost+found
Phase 7 - verify link counts...
would have reset inode 15162585959 nlinks from 0 to 1
No modify flag set, skipping filesystem flush and exiting.

 

[Squid]

58 minutes ago, Homerr said:

No modify flag set, skipping filesystem flush and exiting.

 

59 minutes ago, Homerr said:

Is it recommended to add any parameters? 

 

you have to remove the -n flag

 

59 minutes ago, Homerr said:

Step 4 notes a -L option.

Only if after removing the -n it suggests to add the -L

[Homerr]

Thenks Squid!  I ran it, no errors and restarted in normal array mode and everything looks to be as it should.