Einzigstes

Hi, My Docker service wont start after a reboot. Otherwise the system is running well. I have limited access as I am currently travelling and only habe my phone with vpn access on me. Any help would be appreciated. Thanks. server1-diagnostics-20250911-1553.zip

This worked! There were some weired things going on with my HBA-Card but it's currently doing it's parity check and all dockers seem to be working fine. Thank you!

Hello, today I noticed that my dockers were not operating. This led me to some troubleshooting. I noticed the followting things: My appdata-backup plugin hat a few error alerts in the notification centre (Failure to start some dockers back up) the plugin is set up to stop, backup and update most of my dockers which has worked fine for close to a year now Dockers were displayed as running but were not accessible, some wouldn't start at all Apart from that, everything else seemed fine. I decided to restart the system first. It wouldn't start back up. The error I got was: Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0). I assumed that the usb died. I downloaded a flash drive backup from unraid connect. The backup is from yesterday. I followed the docuementation and created a new stick with the downloaded zip-file and a USB-drive that meets the requirements. Now the server is starting back up and it's displaying the correct IP-Address for the web-ui on the screen. I can ping this address but the Web-UI is not reachable. Nothing else in my network has changed. My router, which also does DHCP detects the device and that it's online. I just get "connection refused" regardless of http or https. I also tried safe mode. In safe mode with gui, I could not get to the webUI on localhost. Before, when I had the Kernel-problem, safe-mode did nothing as well. I attached an image from the kernel-error and a syslog-file that I created after switching to the new Flash drive. I'm unsure how to proceed. Might just be a network config problem. All help would be appreciated. Thanks. tower-diagnostics-20250609-1129.zip

So far there haven't been any crashes. I'll see if this has solved the problem. Thank you!

It did happen again yesterday. I tried to access the GUI at 8:30pm, 25.12.2023 but no response. I looked through the syslog file, but on that day at least, there aren't any Errors at all. Do I need to set up a remote syslog server? In the logs there are a bunch of errors from the cache pool filling up. This is a seperate problem that should already be fixed. syslog-10.10.10.2 - 25.12.2023.log server1-diagnostics-20231226-0916.zip

Ich hänge gerade an einer sehr änlichen Situation. Ich möchte für eine drittperson einen Fernzugang für SMB und 2 Docker einrichten. Die 2 IPs sind in der VPN-Firewall eingetragen. Eigentlich dachte ich, dass es an der liegt, allerdings ist der DelugeVPN Port auch ohne Regeln nicht erreichbar. Ich glaube, dass es früher bei mir mit "remote tunneled access" funktioniert hat auf Deluge zuzugreifen..

Ok, I will. I just had the problem again, but I didn't set the syslog up properly. I will have to wait a couple of days for the crash to happen again. Thanks.

Hello, a few weeks ago, my Unraid server started having the problem that after a while of operating normally it is no longer responsive. The Server ist still running but neither the WebGUI is loading or any of my Docker containers. The only way to regain access is by restarting the system physically. This is obviously not ideal. It happened roughly 4 times in the last 2-3 weeks. There is a disk (Disk3) that has a UDMA CRC error count of 200. However, it does not seem to be increasing. I doubt that this is the main issue, but please correct me if I'm wrong.. I plan on replacing the disk anyway. I will attach a system log that I created shortly after the reboot which was at: Dec 2 18:50:41. I tried to make sense of the logs before that time but I'm not sure what to look for. Any help would be appreciated. Thank you. server1-diagnostics-20231202-1859.zip

Nextcloud automatically created user-data it got from the old database. I deleted the /data folder and now I've got a clean nextcloud installation. Thank you for the help!

Thank you! I was able to do a clean reinstall of mariadb (i think). I got Nextcloud working and everything seemed to work fine. However, as I tried to create a new user, there was an error in nextcloud saying, that files from that account already exist and the user could not be created. I then opend the mariadb shell. There is only one database (that I created), and it's the one after the clean reinstall. (I deleted the docker template file and appdata folder after uninstall). I listed the users within the database and only my admin-user shows up. Now I am unsure on what to do. I could just rename that user and it may be fine but I don't want there to be any problems in the future... Is there any other place, where data could be stored?

Hello. Today, I added a second drive to my chache-Pool to set the drives to a RAID 1 configuration. I noticed, that I needed to format the drive. So I moved most stuff onto the array and used the appdata backup/restore plugin to create a backup of my appdata. I am now trying to set everything up again. Most things seem to be working fine, but there were a few weired things. However, everything is now working fine (Plex, Pihole, Syncthing etc.) and had the right configuration of the template right away (except Plex...). But just now I tried installing Nextcloud with MariaDB (both Linuxserver's Images) and I ran into problems. I then tried removing the docker and deleting the 'nextcloud' and 'mariadb' folder from the appdata directory to do a fresh install, as I wanted to change the data location anyways. But even though, I deleted the Images, deleted the appdata-folders and even changed the installation-path, nextcloud still has traces of the old configuration. This includes files (although they are displayed as offline) and all previous user-accounts are still there, including the admin-user. I think the problem may have been caused by setting all the shares to cache yes and starting the mover before doing the appdata backup. That probably wasn't the best thing to do. I already considered deleting the docker image and starting over. Is there an easier way to reset just those two dockers? Thanks! server1-diagnostics-20230227-2306.zip