robertomano24

Members
  • Posts

    5
  • Joined

  • Last visited

Everything posted by robertomano24

  1. @johnnie.black Thanks so much for this. I am a noob at Unraid, but not linux. I was able to get my files backed up for later, specifically from appdata. I am reading through some different forum posts now about recreating the pool, as it is not quite intuitive to me yet. Hopefully this will get me back up and running! Thank you again
  2. Hello, I am not sure why, but docker service is failing to start all the sudden. I have never had issues, but reboots do not solve. I have posted diagnostics. Any advice? Previous threads have not been helpful in my case. Thanks! Edit: Diagnostics re-posted AFTER turning docker service back on. Also, logs indicated there is a read-only filesystem issue blocking the creation of the docker.img. This is new. Any ideas? whitehouse-diagnostics-20200517-1759.zip
  3. The post above mine says to delete the container. I am unable to delete the container, as was the original poster. The post above mine does not detail how to resolve the error when deleting the container.
  4. Did you ever find a solution? I am having the same trouble and am unable to delete the container.
  5. I have been working on this with swallace ^ as well. It seems segator had another version of this project at segator/xpenology-docker rather than segator/xepenology. When trying to run the former, there seems to be a qemu compatibility issue with the latest jun loader/synoboot img. The following error occurs: qemu-system-x86_64: /build/qemu-9fqihN/qemu-2.5+dfsg/block/io.c:853: bdrv_aligned_preadv: Assertion `(bytes & (BDRV_SECTOR_SIZE - 1)) == 0' failed. I have tried passing BDRV_SECTOR_SIZE as a docker env var with a value of 1. This has not resolved it yet. I fear incompatibility, but there could be a simple solution to resolve that error.