Cache Drive Unmountable (Wrong FS Type, Bad Option, Bad Superblock)

[jrdnlc]

Hello
Hoping I can get some help here. My dumbass added my cache drive as cache #2 after replacing it with a ssd but I didn't back up the appdata on the original drive. So far what I have researched, it didn't format it just did some partition changes. I'm trying to follow this guide but it gives me the following error:

 

mount -o rescue=all,ro /dev/sdc1 /temp
mount: /temp: wrong fs type, bad option, bad superblock on /dev/sdc, missing codepage or helper program, or other error.
       dmesg(1) may have more information after failed mount system call.

 

After running blkid, I can see the drive is btrfs

/dev/sdc1: UUID="7f32ae57-0db4-4657-a8b3-5b71bce6f891" UUID_SUB="396da734-dd14-42e4-92e2-a8068c658864" BLOCK_SIZE="4096" TYPE="btrfs"

 

So it doesn't seem to be formatted which is a good thing. I can't mount it as RO using UD it gives me the following error

 

Oct 19 22:37:59 Dusty unassigned.devices: Mounting partition 'sdc1' at mountpoint '/mnt/disks/MN1220FA022ZXD'...
Oct 19 22:37:59 Dusty unassigned.devices: Mount cmd: /sbin/mount -t 'btrfs' -o ro,relatime,space_cache=v2 '/dev/sdc1' '/mnt/disks/MN1220FA022ZXD'
Oct 19 22:37:59 Dusty kernel: BTRFS: device fsid 7f32ae57-0db4-4657-a8b3-5b71bce6f891 devid 2 transid 568 /dev/sdc1 scanned by mount (11399)
Oct 19 22:37:59 Dusty kernel: BTRFS info (device sdc1): using crc32c (crc32c-intel) checksum algorithm
Oct 19 22:37:59 Dusty kernel: BTRFS info (device sdc1): using free space tree
Oct 19 22:37:59 Dusty kernel: BTRFS error (device sdc1): devid 1 uuid d75c6176-730f-4538-8b54-e7a21387b088 is missing
Oct 19 22:37:59 Dusty kernel: BTRFS error (device sdc1): failed to read the system array: -2
Oct 19 22:37:59 Dusty kernel: BTRFS error (device sdc1): open_ctree failed
Oct 19 22:38:01 Dusty unassigned.devices: Mount of 'sdc1' failed: 'mount: /mnt/disks/MN1220FA022ZXD: wrong fs type, bad option, bad superblock on /dev/sdc1, missing codepage or helper program, or other error.        dmesg(1) may have more information after failed mount system call. '
Oct 19 22:38:01 Dusty unassigned.devices: Partition 'MN1220FA022ZXD' cannot be mounted.
Oct 19 22:38:01 Dusty unassigned.devices: Running device script: 'MN1220FA022ZXD.sh' with action 'ERROR_MOUNT'.

 

Any help will be greatly appreciated. Thanks in advance

diagnostics-20231020-0740.zip

[JorgeB]

1 hour ago, jrdnlc said:

mount -o degraded,rescue=all,ro /dev/sdc1 /temp

 

Since it's missing a device see if it mounts with the command above, but data will only be usable if it was a redundant pool.

[jrdnlc]

29 minutes ago, JorgeB said:

Since it's missing a device see if it mounts with the command above, but data will only be usable if it was a redundant pool.

 

It was added as a 2nd cache drive but then I realized i forgot to backup that data. 
 

Looks like it’s mounted but the data is not there? Damn

[JorgeB]

If it was added as the 2nd device to another pool the original filesystem would have been replaced with that one, so it won't have nothing from the old one.

[jrdnlc]

2 minutes ago, JorgeB said:

If it was added as the 2nd device to another pool the original filesystem would have been replaced with that one, so it won't have nothing from the old one.

It was added as a 2nd cache. I don’t have any pools in my configuration

[JorgeB]

29 minutes ago, jrdnlc said:

It was added as a 2nd cache

2nd cache to another pool device correct?

[jrdnlc]

2 minutes ago, JorgeB said:

2nd cache to another pool device correct?

Just a cache drive

[JorgeB]

That's still a pool, it was a single device pool, you added a 2nd device.

[itimpi]

31 minutes ago, jrdnlc said:

It was added as a 2nd cache. I don’t have any pools in my configuration

A bit of a terminology issue here 😒.   By definition a drive set up as a cache is a pool (even if it is a single drive pool).     You should clarify whether you were adding a second pool to be used for caching or adding another drive to the existing cache pool.

[jrdnlc]

Bummer. So i’m screwed then?

[JorgeB]

Yep.

[jrdnlc]

Just now, itimpi said:

A bit of a terminology issue here 😒.   By definition a drive set up as a cache is a pool (even if it is a single drive pool).     You should clarify whether you were adding a second pool to be used for caching or adding another drive to the existing cache pool.

Adding a second drive to use as caching. Didn’t think it would merge them together without confirmation. I thought both would be separate mountable drives 

[JorgeB]

You can try something like UFS explorer, to see if it can find something from the old filesystem, there's a free trial, but the device was likely trimmed, so it would be all gone.

[itimpi]

Just now, jrdnlc said:

Adding a second drive to use as caching. Didn’t think it would merge them together without confirmation. I thought both would be separate mountable drives 

They would be if you put them in separate single-drive pools.

[jrdnlc]

Oh well. I’m screwed

thanks for the help