Hello kind users,

 

I have been trying different solutions on the forums (e.g. 1. unmount the cache drive, start array, mount cache drive; 2. unmount the cache drive, mount as unassigned device read-only) but neither are working. I have tried mounting the cache drive in both regular startup and safe mode, same results.

 

I have downloaded the diagnostics file directly after I tried mounting the cache drive again, where it is stuck. I have attached that to this post.

At this rate I have accepted that the cache drive has been corrupted. I am now desperate to take data off the cache drive, as I stupidly had shares set to cache-only. I also had my appdata and docker image stuff there. I've attached the SMART report for the drive as well.

 

Can someone guide me on how to approach this problem? Thank you so much.

tower-diagnostics-20240807-2358.zip tower-smart-20240808-0000.zip

With the array stopped, post the output from:

 

xfs_repair -v /dev/sdc1

 

With the array stopped, this is the output:

 

Phase 1 - find and verify superblock...
        - block cache size set to 6161560 entries
Phase 2 - using internal log
        - zero log...
zero_log: head block 746056 tail block 594776
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.

 

I also attempted to mount the drive by running:

mkdir /mnt/xfs_drive

mount -t xfs /dev/sdc1 /mnt/xfs_drive

 

And the terminal is frozen after this line -- should I attempt to do an xfs_repair with the -L tag? Will this cause any problems?

Now the output of:

 

xfs_repair -vL /dev/sdc1