Unable to write to cache error

[MothyTim]

Rebooted system and updated bios, now cache drive is read only and btrfs errors in log! Has bios update done something that Unraid doesn't like or is this something else? System shows cache drive as ok. Attached diagnostics.

Cheers,

Tim

tower-diagnostics-20200304-1354.zip

[JorgeB]

Cache filesystem is corrupt, best bet is to backup, re-format and restore the data.

[MothyTim]

Oh! What did I do to cause that? 🤯

[JorgeB]

Can't say, whatever happened it happened before this boot, it won't hurt to run memtest.

[MothyTim]

Ok will do, thanks for your help.

[MothyTim]

Ok, so memtest passed, so I reinstalled all my vm's and dockers from backups etc, did a reboot to check all is ok and all my dockers have gone!!! Whats that about?

[JorgeB]

Did you re-format cache? Also please post current diags.

[MothyTim]

Hi yes I reformatted cache to XFS and then formatted again back to btrfs?

tower-diagnostics-20200305-1553.zip

[MothyTim]

Should I have deleted the docker image or did the system create a new one anyway?

 

[JorgeB]

7 minutes ago, MothyTim said:

Should I have deleted the docker image or did the system create a new one anyway?

If it was on cache it would have been re-created, but since you're using /mnt/user paths you might have two images, what's the output of:

 

find /mnt -name docker.img

 

[MothyTim]

Hi looks like there are 2! How did that happen, best way to fix?

 

Linux 4.19.98-Unraid.
root@Tower:~# find /mnt -name docker.img
/mnt/user/system/docker/docker.img
/mnt/cache/system/docker/docker.img
root@Tower:~# 

 

[Squid]

2 minutes ago, MothyTim said:

Hi looks like there are 2! How did that happen, best way to fix?

 

Linux 4.19.98-Unraid.
root@Tower:~# find /mnt -name docker.img
/mnt/user/system/docker/docker.img
/mnt/cache/system/docker/docker.img
root@Tower:~# 

 

There's only the one of them present.  You're good to go

[JorgeB]

Those are the same, still recommend changing the paths to /mnt/cache instead of /mnt/user, no idea what happened to the dockers since there weren't any errors I could see, but that image looks brand new based on the transid, you can quickly add them back using the CA previous apps function.

[MothyTim]

Ok, so change the path in docker settings? Or somewhere else?

[MothyTim]

Or set share to cache only?

[JorgeB]

8 minutes ago, MothyTim said:

so change the path in docker settings?

^this

[MothyTim]

Ok Thanks again 😀

[itimpi]

2 hours ago, MothyTim said:

Hi looks like there are 2! How did that happen, best way to fix?

 

Linux 4.19.98-Unraid.
root@Tower:~# find /mnt -name docker.img
/mnt/user/system/docker/docker.img
/mnt/cache/system/docker/docker.img
root@Tower:~# 

 

Those are two different views of the same file!    The /mnt/user location is looking at the virtual file system used to implement User Shares, while /mnt/cache is referring to the physical device holding the file.