Issues since 6.5.4 now 6.5.5

[rhinoman]

Since upgradeing to 6.5.4 last week my machine has become unstable, first thing noticed was that dockers become unavailable, then the web interface. Hard reset then started a parity check and it froze the web interface again but could get to the shares via another machine so updated to 6.5.5. This time parity completed but  soon after the dockers become unresponsive again. I've rebooted and the dockers remain unavailable with "docker service was unable to start" and when I try to start a VM i get

Quote

Execution error

internal error: process exited while connecting to monitor: 2018-11-15T21:53:40.373025Z qemu-system-x86_64: -drive file=/mnt/cache/domains/Win7 Media Machine/vdisk1.img,format=raw,if=none,id=drive-virtio-disk2,cache=writeback: Could not open '/mnt/cache/domains/Win7 Media Machine/vdisk1.img': Read-only file system

I'm guessing some folder permissions have got messed up somewhere and causing both issues?

Edited November 15, 2018 by rhinoman

[rhinoman]

Fix common problems has just notified me of "unable to write to cache". It's not full by the way.

[Squid]

1 hour ago, rhinoman said:

Read-only file system

Post the diagnostics

[rhinoman]

Cheers for looking.

sun-diagnostics-20181116-0013.zip

[Hoopster]

6 minutes ago, rhinoman said:

Cheers for looking.

sun-diagnostics-20181116-0013.zip

Your cache drive has errors and has been marked read only by BTRFS

 

Nov 15 21:49:24 SUN kernel: BTRFS critical (device sds1): corrupt leaf: root=2 block=1082757414912 slot=131, bad key order, prev (11533745240560926720 7 16777096) current (1082759364608 169 0)
Nov 15 21:49:24 SUN kernel: BTRFS: error (device sds1) in __btrfs_free_extent:6953: errno=-5 IO failure
Nov 15 21:49:24 SUN kernel: BTRFS info (device sds1): forced readonly
Nov 15 21:49:24 SUN kernel: BTRFS: error (device sds1) in btrfs_run_delayed_refs:3057: errno=-5 IO failure
Nov 15 21:49:24 SUN root: truncate: cannot open '/mnt/cache/system/docker.img' for writing: Read-only file system

 

Your best bet may be to make a backup copy of the cache drive, format the drive and restore from the backup.  This has been suggested in other similar cases by the disk/filesystem experts in the forum.

 

[rhinoman]

Wounds like a plan, thanks.