Here’s the English translation for your Unraid help post:

 

I have an SSD that I’ve been using as a cache drive for a long time. Recently, it suddenly failed, so I removed the old SSD and replaced it with a new one (this SSD has been in the machine for a few months but was always listed as unassigned devices and not actually used). The problem now is, I can format it as XFS or Btrfs in the unassigned devices plugin, but I can’t mount it properly. The following error occurs:

 

Feb 17 09:55:23 Tower unassigned.devices: Mounting partition 'sdh1' at mountpoint '/mnt/disks/ZTB401TBA234930BGV'...

Feb 17 09:55:23 Tower unassigned.devices: Mount cmd: /sbin/mount -t 'xfs' -o rw,relatime '/dev/sdh1' '/mnt/disks/ZTB401TBA234930BGV'

Feb 17 09:55:23 Tower kernel: XFS (sdh1): Mounting V5 Filesystem

Feb 17 09:55:23 Tower kernel: XFS (sdh1): Log inconsistent (didn't find previous header)

Feb 17 09:55:23 Tower kernel: XFS (sdh1): failed to find log head

Feb 17 09:55:23 Tower kernel: XFS (sdh1): log mount/recovery failed: error -117

Feb 17 09:55:23 Tower kernel: XFS (sdh1): log mount failed

Feb 17 09:55:24 Tower unassigned.devices: Mount of 'sdh1' failed: 'mount: /mnt/disks/ZTB401TBA234930BGV: mount(2) system call failed: Structure needs cleaning.        dmesg(1) may have more information after failed mount system call.'

Feb 17 09:55:24 Tower unassigned.devices: Partition 'ZTB401TBA234930BGV' cannot be mounted.

 

If I do a “New Config” and place the SSD into the cache (with only this SSD in the cache), before starting the array, the filesystem shows as “auto” (although I just formatted it to XFS in unassigned devices). After starting the array, this new SSD shows “FS: auto”, “Unmountable: Unsupported or no file system”. The “Array Options” shows “Unmountable disk present: Cache • ZHITAI_SC001_XT_1000GB_ZTB401TBA234930BGV (sdh)”. If I check the box next to it and force a format, it changes the filesystem to Btrfs, but it still shows “Unmountable: Unsupported or no file system”.

 

The SMART info looks fine, and the new SSD doesn’t appear to have any issues.

 

Let me know if you need any adjustments!

tower-diagnostics-20250217-1006.zip

ignore the disk sde(ST3000DM001_ZA508NF2) errors, It's already known and existed long long ago

If I format the new ssd to XFS in unassigned devices, it's ok(but still can not be used as a array cache):

Feb 17 10:18:48 Tower unassigned.devices: Removing all partitions from disk '/dev/sdh'.
Feb 17 10:18:54 Tower unassigned.devices: Successfully reloaded partition table on device '/dev/sdh' with partprobe.
Feb 17 10:19:08 Tower unassigned.devices: Formatting device '/dev/sdh'.
Feb 17 10:19:08 Tower unassigned.devices: Device '/dev/sdh' block size: 1953525168.
Feb 17 10:19:08 Tower unassigned.devices: Clearing partition table of disk '/dev/sdh'.
Feb 17 10:19:08 Tower unassigned.devices: Clear partition result: 1+0 records in 1+0 records out 2097152 bytes (2.1 MB, 2.0 MiB) copied, 0.00583462 s, 359 MB/s
Feb 17 10:19:11 Tower unassigned.devices: Successfully reloaded partition table on device '/dev/sdh' with partprobe.
Feb 17 10:19:12 Tower unassigned.devices: Creating Unraid compatible mbr partition on disk '/dev/sdh'.
Feb 17 10:19:12 Tower unassigned.devices: Create mbr partition table result: write mbr signature done
Feb 17 10:19:15 Tower unassigned.devices: Successfully reloaded partition table on device '/dev/sdh' with partprobe.
Feb 17 10:19:15 Tower kernel: sdh: sdh1
Feb 17 10:19:16 Tower unassigned.devices: Format device '/dev/sdh' with 'xfs' filesystem.
Feb 17 10:19:16 Tower unassigned.devices: Format command: /sbin/mkfs.xfs -f '/dev/sdh1' 2>&1
Feb 17 10:19:21 Tower unassigned.devices: Successfully reloaded partition table on device '/dev/sdh' with partprobe.

If I format the new ssd to BTRFS in unassigned devices, it's failed:

 

Feb 17 10:15:13 Tower unassigned.devices: Clear partition result: 1+0 records in 1+0 records out 2097152 bytes (2.1 MB, 2.0 MiB) copied, 0.280056 s, 7.5 MB/s
Feb 17 10:17:34 Tower unassigned.devices: Formatting device '/dev/sdh'.
Feb 17 10:17:34 Tower unassigned.devices: Device '/dev/sdh' block size: 1953525168.
Feb 17 10:17:34 Tower unassigned.devices: Clearing partition table of disk '/dev/sdh'.
Feb 17 10:17:34 Tower unassigned.devices: Clear partition result: 1+0 records in 1+0 records out 2097152 bytes (2.1 MB, 2.0 MiB) copied, 0.00541964 s, 387 MB/s
Feb 17 10:17:37 Tower unassigned.devices: Successfully reloaded partition table on device '/dev/sdh' with partprobe.
Feb 17 10:17:38 Tower unassigned.devices: Creating Unraid compatible mbr partition on disk '/dev/sdh'.
Feb 17 10:17:38 Tower unassigned.devices: Create mbr partition table result: write mbr signature done
Feb 17 10:17:41 Tower kernel: sdh: sdh1
Feb 17 10:17:41 Tower unassigned.devices: Successfully reloaded partition table on device '/dev/sdh' with partprobe.
Feb 17 10:17:42 Tower unassigned.devices: Format device '/dev/sdh' with 'btrfs' filesystem.
Feb 17 10:17:42 Tower unassigned.devices: Format command: /sbin/mkfs.btrfs -f '/dev/sdh1' 2>&1
Feb 17 10:17:42 Tower unassigned.devices: Format failed: checksum verify failed on 1081344 wanted 0x822148f1 found 0xaa961f06 ERROR: cannot read chunk root ERROR: open ctree failed btrfs-progs v6.3.3 See https://btrfs.readthedocs.io for more information.  Performing full device TRIM /dev/sdh1 (931.51GiB) ... NOTE: several default settings have changed in version 5.15, please make sure       this does not affect your deployments:       - DUP for metadata (-m dup)       - enabled no-holes (-O no-holes)       - enabled free-space-tree (-R free-space-tree) 
Feb 17 10:17:45 Tower unassigned.devices: Successfully reloaded partition table on device '/dev/sdh' with partprobe.

 

It looks like a bad device, or the server has other issues, try formatting a different disk or SSD, if you have one available, if it formats it's the device.