4 Disks shows "Unmountable: No file system" in 6.9.0 RC2

[ChrisJourdian]

I have 4 disks that shows this error and even running a disk check doesn't help.  I don't understand what's going on,

 

Attached diagnoses to this thread.

cj-nas-01-diagnostics-20210216-1716.zip

[JorgeB]

What options did you use the run the filesystem check? Make sure you do it without -n or nothing will be done, if you did it without -n post the output.

 

Also note that Marvell controllers and SATA port multipliers are not recommend.

[ChrisJourdian]

Hi Jorge,

 

There is what I have as a report:

Phase 1 - find and verify superblock... Phase 2 - using internal log - zero log... - scan filesystem freespace and inode maps... sb_fdblocks 1137992830, counted 1148212762 - 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 - 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 = 4 - agno = 2 - agno = 5 Phase 5 - rebuild AG headers and trees... - reset superblock... Phase 6 - check inode connectivity... - resetting contents of realtime bitmap and summary inodes - traversing filesystem ... - traversal finished ... - moving disconnected inodes to lost+found ... Phase 7 - verify and correct link counts... Maximum metadata LSN (1:15560) is ahead of log (1:15558). Format log to cycle 4. done

 

[JorgeB]

And if you now start the array that disk is still unmountable?

[ChrisJourdian]

It's working now.  Guess I needed to remove the -n and it's all great now.  Thank you so much for helping!

[JorgeB]

No problem, I would recommend getting rid of those controllers though, or you'll likely run into trouble again, see here for as list of recommended ones: