Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

kylehandy123

Members
  • Joined

  • Last visited

Everything posted by kylehandy123

  1. Updating to 7.1.4 solved the issue. I did check my containers and found the cause of the containers restarting. None appears to be restarting randomly. Closing thread.
  2. New diags attached. I know this was likely not a great move, but I updated to Unraid 7.1.4 which appears to have so far prevented the issue of "The docker server failed to start" despite already running, from occurring again. mainserver-diagnostics-20250927-1555.zip
  3. As the title suggests. The docker service appears to not be running, but I can still access containers that were running before the docker tab reports this. This has been occuring for the last 7-10 days. Diagnostics attached. mainserver-diagnostics-20250927-0235.zip
  4. I went ahead and removed the duplicate files. I was under the impression that mover would skip the files. This did get things moving and mover has moved nearly 3TB of data over the last few days now, so thank you for your advice. I'm attaching new diagnostics moreso for my understanding - mover is being extremely slow compared to what I'm used to, with no changes minus new, identical drives, being added to my server (same drives I already use). This may be my own fault, but nonetheless, I at least want to try to understand what the hold up is. Edit: It appears mover has grinded to a halt again. mainserver-diagnostics-20250604-1917.zip
  5. I updated to Unraid 7.1.2. Although mover does move a handful of files, it eventually stops, despite reporting it's still running. New diagnostics attached. mainserver-diagnostics-20250602-0016.zip
  6. Hi all, I recently added 2 new drives. I've noticed Mover is no longer moving files in any reasonable time frame. I have mover logging enabled, and watching the log, I rarely see any files move. I also realize I do not have a parity drive. I have 2 new Seagate Ironwolf NAS drives waiting to be installed once this problem is solved. Diagnostics are attached. mainserver-diagnostics-20250601-1810.zip
  7. Fair enough! I'll return here when needed if problems continue upon correcting network issues among others. I appreciate both of you for helping up until now.
  8. I had an nginx container running that needed port 80, and would fail consistently without it. @trurl Could you lock this thread? I have discovered further problems outside unraid, so until I resolve those, I won't be able to finish resolving unraid. I apologize.
  9. Tried safe mode. No WebUI on any machines other than the actual Unraid server. Diags attached. mainserver-diagnostics-20250212-1721.zip
  10. Apologies regarding the other category. See attached logs taken immediately after the array reported running. mainserver-diagnostics-20250212-0719.zip
  11. Hey all, I have an open ticket for issues with the docker engine crashing. But as a result of working on fixing that in said other ticket, I'm now unable to access the WebUI after restoring the USB from a backup, or using a fresh USB image with the config files moved over to retain plugin/docker templates and settings. For some reason, when I took diagnostics, two zip files were created. Hence the two attachments. See attached. mainserver-diagnostics-20250211-1716.zip mainserver-diagnostics-20250211-1721.zip
  12. Apologies. Apparently I completely blanked. Attached. Two log files generated back to back, so I've attached them both. I'm not sure why this occurred. mainserver-diagnostics-20250211-1721.zip mainserver-diagnostics-20250211-1716.zip
  13. Final update for the night. I am unable to connect to the webui anymore. I can use the physical server with a monitor to get the GUI up, and it's connected to the network, but I can't connect to the webui from any system. IP and port of the unraid machine is the same as before. I need ideas on how to correct this. Secondly, all docker containers are gone, so I will need to reinstall them all. This is fine, I have the appdata, and everything should work fine. Albeit very frustrating since this will take quite a few hours to do since my backup wasn't super recent, but recent enough it's usable. Any ideas?
  14. Noting new issues, upon rebuilding the USB: I can't access the WebUI but the unraid box does have a working internet connection, and local connection, as far as I can tell. All of my docker containers are gone? So I'll now have to reinstall them all? Trying to troubleshoot the whole no webui issue now.
  15. Making note here that I have just rebuilt the existing USB and am currently booting the server. I'll reply either if it crashes, or stating that its working normally.
  16. I do have backups of my flash. Should I recreate it or swap to a new USB?
  17. Replying again suddenly as the docker service just crashed and failed to restart less than 5 minutes ago. Diagnostics attached. Interestingly, I changed nothing except set system files to remain on cache about 20 minutes ago. mainserver-diagnostics-20250209-1858.zip
  18. Noted. I'll disable that and have files on the cache then.
  19. I have appdata set to only be on my Docker pool, but I do see that it claims to have files on 2 disks, although I haven't been able to locate these files as of yet. System is set to go from Array > Cache, which may explain that. I set the docker.img to 256gb as I do have 84 images, some of which are quite large, and this was just a simple way to ensure as I add more containers that I don't need to constantly increase the docker.img size. I agree it's obnoxiously large, but even when checking file mappings, everything appears to be mapped which should be mapped for each container, although I'll need a lot more time to go through every container I have, it's a lot. Some of my shares are set up to remain empty and are ingress points for data to enter, then be moved by the container controlling it (such as immich_import , which only imports data then moves it to the correct storage) Command output: total 73K drwxrwx--- 1 nobody users 4.0K Feb 9 10:32 ./ drwxr-xr-x 26 root root 520 Feb 9 10:22 ../ drwx------ 1 nobody users 43 Jun 26 2023 .Trash-99/ drwxr-x--- 1 kylehandy123 1000 6 Feb 5 2024 .bzvol/ drwxr-xr-x 1 nobody users 6 Oct 28 03:58 Whisper-Model/ drwxr-xr-x 1 nobody users 74 Feb 9 04:59 appdata/ drwxrwxrwx 1 nobody users 65 Feb 3 17:47 backups/ drwxr-xr-x 1 nobody users 3 Nov 2 19:11 docker_compose/ drwxr-xr-x 1 nobody users 5 Nov 7 01:48 domains/ drwxrwxrwx 1 nobody users 6 Oct 27 06:26 downloads/ drwxrwxrwx 1 nobody users 10 Jun 27 2024 frigate/ drwxrwxrwx 1 nobody users 85 Nov 5 23:36 general_mass_storage/ drwxrwxrwx 1 777 777 109 Aug 14 08:37 immich_data/ drwxrwxrwx 1 nobody users 6 Oct 13 04:01 immich_import/ drwxrwxrwx 1 nobody users 6 Jan 19 16:04 isos/ drwxr-xr-x 1 nobody users 8 Dec 4 18:02 kasm/ drwxrwxrwx 1 nobody users 3 Jan 8 11:33 lxc/ drwxr-xr-x 1 nobody users 46 Oct 12 20:23 mariadb_data/ drwxrwxrwx 1 nobody users 33 Jun 30 2024 media/ drwxrwxrwx 1 nobody users 26 Oct 22 04:46 minio/ drwxr-xr-x 1 nobody users 6 Sep 25 22:17 netbootxyz/ drwxrwxrwx 1 nobody users 26 Nov 7 21:02 nextcloud/ drwxrwxrwx 1 nobody users 62 Oct 31 04:28 paperless-ngx/ drwxrwxrwx 1 nobody users 6 Sep 23 01:44 pirated_software/ drwx------ 1 999 users 85 Feb 8 12:29 postgresql17_data/ drwx------ 1 999 users 103 Feb 8 12:29 postgresql_immich/ drwxrwxrwx 1 nobody users 26 Jun 10 2024 pterodactyl-node/ drwxrwxrwx 1 nobody users 86 Oct 27 04:40 romm/ drwxrwxrwx 1 nobody users 26 Nov 10 02:20 sftpgo/ drwx------ 1 nobody users 64 Oct 17 10:00 syncthing_data/ drwxrwxrwx 1 nobody users 14 Oct 11 07:10 system/ drwxrwxrwx 1 nobody users 6 Nov 13 12:56 temp/ drwxrwxrwx 1 nobody users 2 Jan 7 18:46 zfs_lxccontainers/
  20. Hey @trurl, your solution did work for about 1-2 weeks. Sadly, the problem has emerged once again. Diagnostics attached. I updated plugins again two days ago, which didn't work this time. If there are plugins that should be replaced or removed, would you be able to direct me to which ones in my list? Thanks! mainserver-diagnostics-20250209-1012.zip
  21. Valid point. I will update the plugins now, and leave this open for 1-2 days to verify if the problem continues.
  22. Hey all, Basically, around the same time daily, (4-5am my local time), my docker service will fail to start, but state that it is running. I'm basically clueless on this, so reaching out for help. Diagnostics attached. mainserver-diagnostics-20250110-1926.zip
  23. Hey All! As the title suggests, whenever I start a VM, old or new, their network settings will be wiped out from the Edit option on that VM. This happens for ALL VM's no matter if they're freshly made, or an old VM. This happens upon first booting the VM. Diagnostics attached. All help is appreciated, as this is beyond frustrating and has broken all my VM's. mainserver-diagnostics-20231002-1608.zip
  24. Hi all, As title suggests, I am randomly unable to connect to my unraid webgui on my local network from another computer suddenly. This was all working fine, then out of nowhere I've been unable to connect. I can connect to the webgui on the local unraid machine itself if i boot it into gui mode. Any help is appreciated. mainserver-diagnostics-20230914-2348.zip
  25. Cables shall be replaced as a pre-caution given they're so inexpensive. The drive is going to be replaced with an CMR drive in the very near future as well. This is the second time this drive has randomly been disabled out of nowhere, for no apparent reason, so odd.. The balancing on the pool has been changed to monthly, thanks for pointing that out! The VM page is currently loading rather quick, and VMs themselves are much snappier again. CPU usage for VMs is currently sitting typical, they can be somewhat taxing on the system at times when they're running full tilt. At this point, if nothing seems out of the ordinary minus the odd parity disk issues, I guess I monitor and report back if the same issues pop up again in the future? Thanks again!

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.