# Site Not Functioning After Attempted Upgrade **URL:** https://meta.discourse.org/t/site-not-functioning-after-attempted-upgrade/135345 **Category:** Self-hosting **Created:** [December 7, 2019, 11:10am UTC](https://meta.discourse.org/t/site-not-functioning-after-attempted-upgrade/135345 "2019-12-07T11:10:37Z") **Posts on this page:** 1 **Showing post:** 7
### Author: ![tomtjes](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/tomtjes/32/131271_2.png) [@tomtjes](https://meta.discourse.org/u/tomtjes) #### Post date: [December 9, 2019, 4:53pm UTC](https://meta.discourse.org/t/site-not-functioning-after-attempted-upgrade/135345/7 "2019-12-09T16:53:22Z")
I ran into the same issue with this upgrade. Moving Docker to a different volume solved it for me. I followed this guide: > [@Docker uses root partition, might need more storage space](https://meta.discourse.org/t/docker-uses-root-partition-might-need-more-storage-space/69298/9): > > Another solution on OS level can be to mount /var/lib/docker on a dedicated partition. To do this, please, stop Docker, make sure that no process accesses /var/lib/docker and do the following: Provide an additional volume. In this example it is /dev/sdx8. Format it accordingly, i.e. mkfs.xfs -n ftype=1 /dev/sdx8 or mkfs.ext4 /dev/sdx8 etc. If it fails in mkfs.xfs you might run a newer version of mkfs.xfs which has ftype=1 already as default. Just issue mkfs.xfs /dev/sdx8 Stop Docker. … --- _[View the full topic](https://meta.discourse.org/t/site-not-functioning-after-attempted-upgrade/135345)._