Drive is showing as "Unmountable: Unsupported or no drive system".

[StephenCND]

Been having issues with this drive lately. Initially there seemed to be a problem with it, but I swapped the drive to a new Sata cable and that fixed that. Now it seems the system doesn't recognize the drive (see photo).

I ran "Fix Common Problems" but nothing came up. I've attached a Diag file  if anyone could be of assistance please.

 

 

nasterminal1-diagnostics-20231011-0914.zip

[JorgeB]

Check filesystem on disk3, run it without -n.

[JorgeB]

12 minutes ago, StephenCND said:

I do not see any "maintenance mode" checkbox as mentioned in the link you provided.

It's next to the start array button.

[StephenCND]

Got the following: "

Phase 1 - find and verify superblock... Phase 2 - using internal log - zero log... ERROR: The filesystem has valuable metadata changes in a log which needs to be replayed. Mount the filesystem to replay the log, and unmount it before re-running xfs_repair. If you are unable to mount the filesystem, then use the -L option to destroy the log and attempt a repair. Note that destroying the log may cause corruption -- please attempt a mount of the filesystem before doing this."

Do I proceed with the instructions or do you advise another course of action?

[JorgeB]

Use -L

[StephenCND]

Got the following:

"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 destroyed because the -L option was used. - scan filesystem freespace and inode maps... clearing needsrepair flag and regenerating metadata sb_ifree 160, counted 108 sb_fdblocks 729008010, counted 730399085 - 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 imap claims a free inode 2238793491 is in use, correcting imap and clearing inode cleared inode 2238793491 - 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 = 2 entry "Backup_Error-24-09-2023_23-26-31.log" at block 0 offset 1152 in directory inode 2147483887 references free inode 2238793491 clearing inode number in entry at offset 1152... - agno = 3 clearing reflink flag on inodes when possible Phase 5 - rebuild AG headers and trees... - reset superblock... Phase 6 - check inode connectivity... - resetting contents of realtime bitmap and summary inodes - traversing filesystem ... bad hash table for directory inode 2147483887 (no data entry): rebuilding rebuilding directory inode 2147483887 - traversal finished ... - moving disconnected inodes to lost+found ... Phase 7 - verify and correct link counts... Maximum metadata LSN (1:288358) is ahead of log (1:2). Format log to cycle 4. done"

Rebooted out of maintenance mode and drive seems to be up and running. No errors. This issue possibly due to a bad sata cable causing corruption?

[JorgeB]

1 minute ago, StephenCND said:

This issue possibly due to a bad sata cable causing corruption?

Could be.

[StephenCND]

Thanks again JorgeB ! Much appreciated.