Hi all,

 

I recently upgraded my unRAID server to 6.8.2 and I noticed that I have an "Unmountable disk present" and cache disk won't mount. I have a cache pool with 2 SSDs and one disc log information says:

Jan 28 10:31:53 Storage kernel: sd 1:0:1:0: [sdc] 468862128 512-byte logical blocks: (240 GB/224 GiB)
Jan 28 10:31:53 Storage kernel: sd 1:0:1:0: [sdc] Write Protect is off
Jan 28 10:31:53 Storage kernel: sd 1:0:1:0: [sdc] Mode Sense: 7f 00 10 08
Jan 28 10:31:53 Storage kernel: sd 1:0:1:0: [sdc] Write cache: enabled, read cache: enabled, supports DPO and FUA
Jan 28 10:31:53 Storage kernel: sdc: sdc1
Jan 28 10:31:53 Storage kernel: sd 1:0:1:0: [sdc] Attached SCSI disk
Jan 28 10:31:53 Storage kernel: BTRFS: device fsid eccfaaa2-5017-4960-9d5b-d1a07443a421 devid 1 transid 11830033 /dev/sdc1
Jan 28 10:32:05 Storage emhttpd: KINGSTON_SA400S37240G_50026B76827CCB3E (sdc) 512 468862128
Jan 28 10:32:06 Storage emhttpd: import 30 cache device: (sdc) KINGSTON_SA400S37240G_50026B76827CCB3E
Jan 28 10:32:13 Storage kernel: BTRFS info (device sdc1): disk space caching is enabled
Jan 28 10:32:13 Storage kernel: BTRFS info (device sdc1): has skinny extents
Jan 28 10:32:13 Storage kernel: BTRFS info (device sdc1): enabling ssd optimizations
Jan 28 10:32:13 Storage kernel: BTRFS warning (device sdc1): sdc1 checksum verify failed on 55373398016 wanted 9086B0CB found 48F5F7D4 level 0
Jan 28 10:32:13 Storage kernel: BTRFS error (device sdc1): bad tree block start, want 55373414400 have 1222961048758584978
Jan 28 10:32:13 Storage kernel: BTRFS error (device sdc1): Error removing orphan entry, stopping orphan cleanup
Jan 28 10:32:13 Storage kernel: BTRFS error (device sdc1): could not do orphan cleanup -22
Jan 28 10:32:13 Storage root: mount: /mnt/cache: wrong fs type, bad option, bad superblock on /dev/sdc1, missing codepage or helper program, or other error.
Jan 28 10:32:13 Storage kernel: BTRFS error (device sdc1): open_ctree failed

 

All the SMART data says that nothing is wrong however a parity check completed 31/12 returned with "0 errors" (I don't know if this is related or not).

How can I fix it?

 

Thanks in advance.

storage-diagnostics-20200129-0948.zip

Cache filesystem is corrupt, best bet it to re-format, if there's any important data there you can try these recovery options.

Thank you very much for your reply.

After I post it I found this very useful FAQ of yours and I managed to mount cache drive and I proceed with copying cache data to the array.

 

By the way what do you think, is it a good advice for appdata, domains and system shares to use Prefer setting for cache pool?

"prefer" or "no" (assuming all data on those shares is already on cache)

Right now all these shares are on the array.

So you mean that I must copy them to the cache pool before enable Prefer option?

You can enable "prefer" and then run the mover (docker and VM services need to be stopped first), once the mover finishes you can change to cache="no", but it can also be left as "prefer", enable GUI help for a detailed explanations of the differences.

Thank very much.

 

1 hour ago, johnnie.black said:

You can enable "prefer" and then run the mover (docker and VM services need to be stopped first), once the mover finishes you can change to cache="no", but it can also be left as "prefer", enable GUI help for a detailed explanations of the differences.

What is the rationale for using Cache=No rather than Cache=Only once mover has completed?

11 minutes ago, itimpi said:

What is the rationale for using Cache=No rather than Cache=Only once mover has completed?

I meant cache="only"

Just now, johnnie.black said:

I meant cache="only"

Fair enough - I get days like that as well     I was just wondering if there was something profound that I had missed

On 1/29/2020 at 8:17 PM, babis2k said:

Thank you very much for your reply.

After I post it I found this very useful FAQ of yours and I managed to mount cache drive and I proceed with copying cache data to the array.

 

By the way what do you think, is it a good advice for appdata, domains and system shares to use Prefer setting for cache pool?

Hey guys, So I've just run into the same problem as you, I know this was a while ago for you but if you can remember what you did could you please share? I was hoping that you linked to the FAQ you mentioned but it's not there.

Thanks heaps!

19 minutes ago, Rattus said:

I was hoping that you linked to the FAQ you mentioned but it's not there.

It is:

 

On 1/29/2020 at 9:03 AM, JorgeB said:

you can try these recovery options.

 

23 minutes ago, Rattus said:

Hey guys, So I've just run into the same problem as you, I know this was a while ago for you but if you can remember what you did could you please share? I was hoping that you linked to the FAQ you mentioned but it's not there.

Thanks heaps!

 

I've marked the above post as the "Solution" for my problem.

Thanks for that guys, sorry to be so nieve, i guess i was just panicking. I've started a new issue so that I don't clutter this one.

 

 

Any chance of getting some help? I've put in the post the terminal commands and outputs.

 

Thanks again guys, last post here.

On 1/29/2020 at 4:03 AM, JorgeB said:

you can try these recovery options.

Are there similar options for an encrypted BTRFS drive?

 

Getting the error:

root@Unraid:~# mount -o rescue=all,ro /dev/sdb1 /temp
mount: /temp: unknown filesystem type 'crypto_LUKS'

 

Edited July 3, 20224 yr by robertomano24_24

4 hours ago, robertomano24_24 said:

Are there similar options for an encrypted BTRFS drive?

First you must decrypt the device, then it's the same just add mapper to the device path, e.g.:

 

mount -o rescue=all,ro /dev/mapper/sdb1 /temp