I know this issue has been posted several times before, but after following those suggestions I haven't been able to resolve the issue. After restarting Unraid my cache drive is coming up as "Unmountable: Unsupported or no file system". 

 

I started the array in maintenance mode and tried using the check filesystem option, but it couldn't find /dev/sdc1 and kept erroring out. I did manage to run it through the console on /dev/sdc and it said "bad primary superblock - bad magic number !!!", then after running for an hour or so it wasn't able to repair anything.

 

One thing I'm seeing that I wasn't expecting is that the drive is showing up in the normal cache spot, but also down in the "Historical Unassigned Devices" section. 

 

I'm hoping somebody might be able to point me in the right direction before I purchase UFS Explorer and try to get some data off the cache drive. 

 

I didn't see any failures on the drive. It's actually only maybe three months old. 

 

I attached my diagnostics file as well. 

 

Thanks!mediaserver-diagnostics-20250101-2009.zip

14 minutes ago, ICYN30 said:

run it through the console on /dev/sdc

This is incorrect.

 

Try again from the webUI and post the results.

I wasn't having any luck through the webUI at all. I keep getting this:

 

/dev/sdc1: No such file or directory

fatal error -- couldn't initialize XFS library

 

It does seem like the array is hanging when I try and stop it. I'm not sure if that would be related or not. 

Post the output from

blkid

 

6 hours ago, JorgeB said:

Post the output from

blkid

 

This is the response:

 

/dev/sda1: LABEL_FATBOOT="UNRAID" LABEL="UNRAID" UUID="2732-64F5" BLOCK_SIZE="512" TYPE="vfat"
/dev/loop1: TYPE="squashfs"
/dev/sdf1: PARTUUID="197f802f-7127-4982-ae99-547cdf4b169e"
/dev/sdd1: UUID="cb992622-2381-41fa-ab83-8f606542af22" BLOCK_SIZE="512" TYPE="xfs" PARTUUID="1cf6d588-19b2-44a0-b7c9-04d43eb8f12b"
/dev/md2p1: UUID="9e314959-825d-4e21-95cb-98c9e2f2d967" BLOCK_SIZE="512" TYPE="xfs"
/dev/sdb1: UUID="dd859987-7b87-4b65-b35f-49dbcc28e2e1" BLOCK_SIZE="512" TYPE="xfs" PARTUUID="4bde6689-0538-4cb4-a5d6-7284911d8cc4"
/dev/md5p1: UUID="6d16c950-1abd-4c1d-8639-dd119466a8e9" BLOCK_SIZE="512" TYPE="xfs"
/dev/sdi1: UUID="9e314959-825d-4e21-95cb-98c9e2f2d967" BLOCK_SIZE="512" TYPE="xfs" PARTUUID="8c94bb05-5505-4f14-ae07-b20bd9dbe54f"
/dev/md1p1: UUID="dd859987-7b87-4b65-b35f-49dbcc28e2e1" BLOCK_SIZE="512" TYPE="xfs"
/dev/sdg1: UUID="6d16c950-1abd-4c1d-8639-dd119466a8e9" BLOCK_SIZE="512" TYPE="xfs" PARTUUID="287bb421-164b-4a5e-a853-2e16fa082a43"
/dev/md4p1: UUID="cb992622-2381-41fa-ab83-8f606542af22" BLOCK_SIZE="512" TYPE="xfs"
/dev/loop0: TYPE="squashfs"
/dev/sde1: UUID="5ee752e2-cb17-4e70-aa98-7d1d353c405a" BLOCK_SIZE="4096" TYPE="xfs"
/dev/md3p1: UUID="b8783ab4-7341-4ffc-abb6-ce769269b9f3" BLOCK_SIZE="512" TYPE="xfs"
/dev/sdh1: UUID="b8783ab4-7341-4ffc-abb6-ce769269b9f3" BLOCK_SIZE="512" TYPE="xfs" PARTUUID="8f9d717f-05a1-4960-a27c-4743c6131acc"

 

No filesystem is being detected on the cache device, post the output from:

 

fdisk -l /dev/sdc

 

4 minutes ago, JorgeB said:

No filesystem is being detected on the cache device, post the output from:

 

fdisk -l /dev/sdc

 

 

Here's what I get for that one:

 

Disk /dev/sdc: 931.51 GiB, 1000204886016 bytes, 1953525168 sectors
Disk model: WDC  WDS100T1R0A
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

 

 

There's no partition, was the device wiped?

You can try this, type

sfdisk /dev/sdc

then type 2048 and hit enter and post the results

21 minutes ago, JorgeB said:

You can try this, type

sfdisk /dev/sdc

then type 2048 and hit enter and post the results

It has not been wiped. Unless something happened when I restarted the server yesterday.

 

Here's the results. I haven't selected anything yet.

 

Created a new DOS disklabel with disk identifier 0x2d84e99d.
Created a new partition 1 of type 'Linux' and of size 931.5 GiB.
Partition #1 contains a xfs signature.

Do you want to remove the signature? [Y]es/[N]o: 

 

Type N and hit enter to keep the signature, then type

write

and enter again.

 

After that, start the array and post new diags.

11 minutes ago, JorgeB said:

Type N and hit enter to keep the signature, then type

write

and enter again.

 

After that, start the array and post new diags.

 

Amazing, that fixed it! Every time I think I know what I'm doing with computers something like this comes along and people way smarter than me know exactly how to fix it.

 

Do you have any insight on what may have caused it to begin with?

 

Thinking I should also install some sort of appdata backup. 

mediaserver-diagnostics-20250102-1223.zip

20 minutes ago, ICYN30 said:

Do you have any insight on what may have caused it to begin with?

Typically, this happens if the device was wiped with wipefs or similar, but I've seen it happen where the device just loses the partition for some reason.

 

20 minutes ago, ICYN30 said:

Thinking I should also install some sort of appdata backup. 

Yep, and any other important data you have there.

17 minutes ago, JorgeB said:

Typically, this happens if the device was wiped with wipefs or similar, but I've seen it happen where the device just loses the partition for some reason.

 

Yep, and any other important data you have there.

 

Weird. I really appreciate the help though!