I noticed this afternoon that one of the 10 disks in my pool changed to "Unmountable: Unsupported or no file system"

 

I followed some of the conversation here: https://www.reddit.com/r/unRAID/comments/16z399w/unmountable_unsupported_or_no_file_system/

 

While running the xfs repair, the browser locked up because of how long the output was.  When I reload the page, it no longer looks like it should.

There doesn't seem to be anything going on as read/write totals on the main tab haven't changed in over an hour.

In the logs, I found

 

Nov  7 16:52:33 Tower kernel: XFS (md9p1): Corruption of in-memory data (0x8) detected at xfs_trans_cancel+0xd6/0x114 [xfs] (fs/xfs/xfs_trans.c:1098).  Shutting down filesystem.
Nov  7 16:52:33 Tower kernel: XFS (md9p1): Please unmount the filesystem and rectify the problem(s)
Nov  7 16:52:33 Tower kernel: XFS (md9p1): Failed to recover intents
Nov  7 16:52:33 Tower kernel: XFS (md9p1): Ending recovery (logdev: internal)
Nov  7 16:52:33 Tower kernel: XFS (md9p1): log mount finish failed
Nov  7 16:52:33 Tower root: mount: /mnt/disk9: mount(2) system call failed: Structure needs cleaning.
Nov  7 16:52:33 Tower root:        dmesg(1) may have more information after failed mount system call.
Nov  7 16:52:33 Tower emhttpd: shcmd (74): exit status: 32
Nov  7 16:52:33 Tower emhttpd: /mnt/disk9 mount error: Unsupported or no file system
Nov  7 16:52:33 Tower emhttpd: shcmd (75): rmdir /mnt/disk9
Nov  7 16:52:33 Tower emhttpd: mounting /mnt/disk10
Nov  7 16:52:33 Tower emhttpd: shcmd (76): mkdir -p /mnt/disk10
Nov  7 16:52:33 Tower emhttpd: shcmd (77): mount -t xfs -o noatime,nouuid /dev/md10p1 /mnt/disk10
Nov  7 16:52:33 Tower kernel: XFS (md10p1): Mounting V5 Filesystem
Nov  7 16:52:33 Tower kernel: XFS (md10p1): Ending clean mount
Nov  7 16:52:33 Tower kernel: xfs filesystem being mounted at /mnt/disk10 supports timestamps until 2038 (0x7fffffff)
Nov  7 16:52:33 Tower emhttpd: shcmd (78): xfs_growfs /mnt/disk10
Nov  7 16:52:33 Tower root: meta-data=/dev/md10p1            isize=512    agcount=13, agsize=268435455 blks
Nov  7 16:52:33 Tower root:          =                       sectsz=512   attr=2, projid32bit=1
Nov  7 16:52:33 Tower root:          =                       crc=1        finobt=1, sparse=1, rmapbt=0
Nov  7 16:52:33 Tower root:          =                       reflink=1    bigtime=0 inobtcount=0 nrext64=0
Nov  7 16:52:33 Tower root: data     =                       bsize=4096   blocks=3418095603, imaxpct=5
Nov  7 16:52:33 Tower root:          =                       sunit=0      swidth=0 blks
Nov  7 16:52:33 Tower root: naming   =version 2              bsize=4096   ascii-ci=0, ftype=1
Nov  7 16:52:33 Tower root: log      =internal log           bsize=4096   blocks=521728, version=2
Nov  7 16:52:33 Tower root:          =                       sectsz=512   sunit=0 blks, lazy-count=1
Nov  7 16:52:33 Tower root: realtime =none                   extsz=4096   blocks=0, rtextents=0
Nov  7 16:52:33 Tower emhttpd: mounting /mnt/cache
Nov  7 16:52:33 Tower emhttpd: shcmd (79): mkdir -p /mnt/cache
Nov  7 16:52:33 Tower emhttpd: shcmd (80): mount -t xfs -o noatime,nouuid /dev/sdj1 /mnt/cache
Nov  7 16:52:33 Tower kernel: XFS (sdj1): Mounting V5 Filesystem
Nov  7 16:52:33 Tower kernel: XFS (sdj1): Ending clean mount
Nov  7 16:52:33 Tower emhttpd: shcmd (81): mount -o remount,discard /mnt/cache
Nov  7 16:52:33 Tower emhttpd: mounting /mnt/torrentcache
Nov  7 16:52:33 Tower emhttpd: shcmd (82): mkdir -p /mnt/torrentcache
Nov  7 16:52:33 Tower emhttpd: shcmd (83): mount -t xfs -o noatime,nouuid /dev/nvme0n1p1 /mnt/torrentcache
Nov  7 16:52:33 Tower kernel: XFS (nvme0n1p1): Mounting V5 Filesystem
Nov  7 16:52:33 Tower kernel: XFS (nvme0n1p1): Ending clean mount
Nov  7 16:52:33 Tower emhttpd: shcmd (84): mount -o remount,discard /mnt/torrentcache
Nov  7 16:52:33 Tower emhttpd: shcmd (85): /usr/sbin/zfs mount -a
Nov  7 16:52:33 Tower emhttpd: shcmd (86): sync
Nov  7 16:52:34 Tower emhttpd: shcmd (87): mkdir /mnt/user0
Nov  7 16:52:34 Tower emhttpd: shcmd (88): /usr/local/bin/shfs /mnt/user0 -disks 2046 -o default_permissions,allow_other,noatime 
Nov  7 16:52:34 Tower shfs: FUSE library version 3.12.0

 

tower-syslog-20241108-0157.zip tower-diagnostics-20241107-1956.zip

Edited November 8, 20241 yr by christhompsontldr

There are ATA errors on disk9, replace the cables for that disk, then post new diags after array start.

I replaced the SATA cable on disk9.  Attached are the logs and diagnostic after booting.

tower-syslog-20241108-1410.zip tower-diagnostics-20241108-0810.zip

No ATA errors so far, now check filesystem on disk9, run it without -n

@JorgeB thanks for all the help so far.  I started running xfs_repair.  I can't tell if it is finished or not.  The read/write values haven't changed in about 20 minutes.

 

Edited November 8, 20241 yr by christhompsontldr

There should be an output in the GUI, you can run from the CLI:

 

xfs_repair -v /dev/md9p1

 

P.S. did you notice that disk4 is disabled now? 

 

 

I did notice that disk4.  I haven't gotten around to figuring out what happened.

Here's the output of the CLI run of xfs_repair.  Is the next step to stop the array and restart it in normal mode?

 

Phase 6 - check inode connectivity...
        - resetting contents of realtime bitmap and summary inodes
        - traversing filesystem ...
        - agno = 0
        - agno = 1
        - agno = 2
        - agno = 3
        - agno = 4
        - agno = 5
        - agno = 6
        - agno = 7
        - agno = 8
        - agno = 9
        - agno = 10
        - agno = 11
        - agno = 12
        - traversal finished ...
        - moving disconnected inodes to lost+found ...
Phase 7 - verify and correct link counts...

        XFS_REPAIR Summary    Fri Nov  8 11:04:22 2024

Phase           Start           End             Duration
Phase 1:        11/08 10:58:39  11/08 10:58:39
Phase 2:        11/08 10:58:39  11/08 10:58:44  5 seconds
Phase 3:        11/08 10:58:44  11/08 11:01:32  2 minutes, 48 seconds
Phase 4:        11/08 11:01:32  11/08 11:01:33  1 second
Phase 5:        11/08 11:01:33  11/08 11:01:39  6 seconds
Phase 6:        11/08 11:01:39  11/08 11:04:21  2 minutes, 42 seconds
Phase 7:        11/08 11:04:21  11/08 11:04:21

Total run time: 5 minutes, 42 seconds
done

 

32 minutes ago, christhompsontldr said:

Is the next step to stop the array and restart it in normal mode?

Yep.

@JorgeB thank you so much for all your assistance.  Disk 9 is healthy and back in the array.  Disk 4 is rebuilding from parity.

 

I think it's something wrong with the SATA controller I have.  I'm going to review https://forums.unraid.net/topic/102010-recommended-controllers-for-unraid/ to ensure I have a quality controller.