Hi guys,

 

I had a disk dropped out of the array. I tried to bring it back online by using new-config. I checked "parity is valid" as I do have two parity disks and the checked just finished a couple of hours ago.

Now the disk is "Unmountable: No file system" - what shall I do? have I lost data?

knowlage-diagnostics-20200717-0857.zip

Check filesystem on disk3, but note that a new config is not usually the right thing to after a disk drops, and you now need to run a correcting check.

//going to command line

Edited July 17, 20205 yr by Jaster

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
        - agno = 4
        - agno = 5
        - agno = 6
        - agno = 7
        - 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 = 3
        - agno = 4
        - agno = 1
        - agno = 5
        - agno = 6
        - 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...
No modify flag set, skipping filesystem flush and exiting.

Command line tels me this on a dry run - just run it or?...

You need to run without -n (and possibly need to add  -L)

It's back online - what would be the correct procedure if the disk drops again?

The short SMART looks good, I'm running the extended check now.

If you believe the drive is good you can do a new config but must keep a few things in mind: if it's really a disk problem you'll lose the ability to rebuild it, you should make sure the disk is at least mounting correctly before doing the new config (you can use UD for that), you'll lose any data written to that disk (the emulated disk) once it got disabled and you'll need to re-sync parity or if the "parity is already valid" was checked you need to do a correcting check since a few sync errors are expected.