Eysenor

I have a follow up question on the topic, I want to change the default volume of a container from the default in the docker-compose file (should have done from the beginning) to a location in the appdata. the volume is now: volumes: - pgdata:/var/lib/postgresql/data I want to have something like: volumes: - mnt/user/appdata/container/pgdata:/var/lib/postgresql/data I expected that using the docker cp command: docker cp immich_postgres:pgdata /mnt/user/appdata/container/pgdata would copy all the content from wherever the default volume is and move it to the new location. Then I could just point the docker-compose to the new location and it should work. But when I do that the container does not work anymore. Is there a way to do this or is remaking everything from the start the only option? Thanks!

I ended up reinstalling the container with the previous settings and now the container starts but I cannot access the webUI. I'm using port 7282 as webui like default but that does not work. Even if I try to open the AIO from nextcloud it does not connect. Nextcloud has been working fine all this time. The log for the master container is like this now: WARNING: No swap limit support WARNING: No swap limit support /usr/lib/python3.12/site-packages/supervisor/options.py:13: UserWarning: pkg_resources is deprecated as an API. See https://setuptools.pypa.io/en/latest/pkg_resources.html. The pkg_resources package is slated for removal as early as 2025-11-30. Refrain from using this package or pin to Setuptools<81. import pkg_resources {"level":"info","ts":1755281567.649624,"msg":"maxprocs: Leaving GOMAXPROCS=6: CPU quota undefined"} {"level":"info","ts":1755281567.6498203,"msg":"GOMEMLIMIT is updated","package":"github.com/KimMachineGun/automemlimit/memlimit","GOMEMLIMIT":30181456281,"previous":9223372036854775807} {"level":"info","ts":1755281567.6498535,"msg":"using config from file","file":"/Caddyfile"} {"level":"info","ts":1755281567.6509106,"msg":"adapted config to JSON","adapter":"caddyfile"} {"level":"info","ts":1755281567.6616337,"msg":"serving initial configuration"} [Fri Aug 15 18:12:47.712314 2025] [mpm_event:notice] [pid 150:tid 150] AH00489: Apache/2.4.65 (Unix) OpenSSL/3.5.1 configured -- resuming normal operations [Fri Aug 15 18:12:47.712365 2025] [core:notice] [pid 150:tid 150] AH00094: Command line: 'httpd -D FOREGROUND' [15-Aug-2025 18:12:47] NOTICE: fpm is running, pid 156 [15-Aug-2025 18:12:47] NOTICE: ready to handle connections Trying to fix docker.sock permissions internally... Creating docker group internally with id 281 The environmental variable TZ has been set which is not supported by AIO since it only supports running in the default Etc/UTC timezone! The correct timezone can be set in the AIO interface later on! Initial startup of Nextcloud All-in-One complete! You should be able to open the Nextcloud AIO Interface now on port 8080 of this server! E.g. https://internal.ip.of.this.server:8080 ⚠️ Important: do always use an ip-address if you access this port and not a domain as HSTS might block access to it later! If your server has port 80 and 8443 open and you point a domain to your server, you can get a valid certificate automatically by opening the Nextcloud AIO Interface via: https://your-domain-that-points-to-this-server.tld:8443 It says that I should use port 8080 but, even using that port does not connect to the master container. I'm kind of not sure now what could I do more. If I unistall all the containers and try to install the master container again I have no idea if it would actually work. At least for now nextcloud still works.

I think after the last update of the master container, all the other containers are working fine and I can use nextcloud. Took me sometime to realize that the master container was not started because everything looked fine. When I check the logs I get this message: Could not reach https://ghcr.io. Most likely is something blocking access to it. You should be able to fix this by following https://dockerlabs.collabnix.com/intermediate/networking/Configuring_DNS.html Another solution is using https://github.com/nextcloud/all-in-one/tree/main/manual-install I found somewhere online that the DNS could be the issue, no other containers have issues and I can update them. I setup the DNS in unraid to 1.1.1.1 to make sure that the DNS is working. Does anyone knows what I could do to solve this? Should I just delete the master container and reinstall? Or delete all the containers are recover from the backup? I would like to avoid the backup option if possible because it is always a little scary. Thanks, hopefully here is the correct place to ask this.

I should have know that before deploying the container, clearly. But how do I get the data that is now in the "data" folder so that I can remake the containers with the correct mapping?

I have a question that I cannot find an answer to, how do I access the files created by the compose containers? Like the appdata folder for the other containers. Is there a way to specify that? EDIT: So I kind of understand that the container created with compose will put the data in the volume specified in the compose file. One of mine is: volumes: - data:/data now, how do I access data? Is it possible to just specify the volume on the cache drive for example? When I get to access data and copy the files from it of course.

I realized that the default docker compose project directory is in the /boot, and that is on the USB drive if I'm not mistaken. I would like to change that to a pool where also the appdata is but I'm not sure what happens if I change the default folder in the compose options. How do I change that folder for the compose stacks that I already have running? EDIT: I found where the /boot location is, it is easier than I was thinking. In there the docker compose plugin stores just the compose and ENV files. Where are the files that the containers created with the compose make? Like the appdata for the containers from the store. Thanks!

Thanks a lot for taking the time to help, the disk is now rebuilding, hopefully all is back to work tomorrow when it is done. Btw, for the next time, how do I identify if a disk has issues with connections and not with the disk itself? beside the SMART test passing.

Thanks for the answer, I'll try that. The only issue still is that the array is not stopping and keeps being stuck at the retry to unmount user shares. How do I get the array to stop properly? I'm getting this error in the log: Dec 6 13:08:05 Homeserver root: rmdir: failed to remove '/mnt/user': Device or resource busy Dec 6 13:08:05 Homeserver emhttpd: shcmd (591): exit status: 1 Dec 6 13:08:05 Homeserver emhttpd: shcmd (593): rm -f /boot/config/plugins/dynamix/mover.cron Dec 6 13:08:05 Homeserver emhttpd: shcmd (594): /usr/local/sbin/update_cron Dec 6 13:08:05 Homeserver emhttpd: Retry unmounting user share(s)... How do I force stop the mnt/user?

I tried to detach and reconnect all the cables to the missing drive and still it shows as disabled. I attached the new diagnostics. Also this time, if I try to stop the array it gets stuck to "retry to unmount user shares". And in the drive log it has errors like this: Dec 5 21:06:17 Homeserver kernel: I/O error, dev sdd, sector 15628052934 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 Dec 5 21:06:17 Homeserver kernel: Buffer I/O error on dev sdd1, logical block 15628052870, async page read Dec 5 21:06:17 Homeserver kernel: Buffer I/O error on dev sdd1, logical block 15628052871, async page read I run a SMART fast diagnostic and it passed. So could it be that the HBA card is somehow acting weirdly? It was working fine before I added another drive and then the drive failure happen (few days later though). If the drive is broken that is fine, I can get another. Mostly I want to be sure I take care of the data correctly. For example, is it possible to move the data from that drive to another that has space from the parity? homeserver-diagnostics-20241205-2138.zip

Here are the diagnostics homeserver-diagnostics-20241205-1422.zip

Hi, I'm sure this has been asked many times but it is scary the first time this happens and I want to make sure that everything is done correcly. During the night a disk had read errors (more than 2000) and is now marked in error. I turned off the array but it is still saying " Array Stopping• Retry unmounting user share(s)..." after few hours. Of course I added a disk yesterday and moved some things around in the case so that could be causing the issue but the disk is still pre-clearing so I cannot turn off the server to check the cables. I have questions on how to proceed properly: - check the cables when I can turn off the server - IF not working still do I do some checks on the disk? Do I keep the array down until I know what is wrong with the disk? Also, if the disk is just broken, can I take it out and still use the server without the disk whitout losing the data on it (from parity)? Last question is, can I change that disk with a bigger one and then rebuild the array with all the data being written on the new drive? Thanks for the help!

For me, unraid worked fine before installing the drivers and, now, works fine also without the drivers so I'm not really sure if they are needed. I have a PCIe nic in the server but it does not work, it is also realtek and I never managed to make unraid to work with it. Might be worth to get an Intel based nic eventually to see if that solves it.

Thanks a lot, that solved it. Booted into the GUI mode and uninstalled the realtek drivers plugin, after a reboot everything is back to normal. Much easier than expected and I learned about the GUI option when directly accessing the server. Never checked too well when booting up. The one thing was that it was trying to connect to https://localhost and did not work, changing to http worked fine.

I will post the diagnostic when I get some time to operate directly to the server, I have the realtek drivers installed. Is there an easy way to revert back from before the update?

Hi, I updated to the 6.12.14 yesterday and, after reboot, the GUI did not load properly, only the top menu was loading. I went to sleep then and hoped it needed some more time to load. This morning I could access the GUI anymore, and still can't. The server is working, hardware is fine and boots correctly. Then Unraid boots "fine" until when it asks for login and the IP of the server is correct (I attached a picture of the screen with unraid booting). Is the USB stick corrupted somehow? I have no idea how to proceed now. If the solution is to just get the USB back to before the update, that would be very nice. I guess I learned my lesson to not update the server when it works, but it should not be like this, either the server works or it is up to date. Not the first time that an update breaks something, this is by far the worse though. Thanks!