Einzigstes

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

Oh, ok thank you! I'll try using just my 500GB, if I need more I'll have a look at @Atreya's solution!

ok, can I change it to raid0? I don't keep important files on the cache, so I don't need the redundancy. //I will probably just remove the smaller drive using this tutorial, as 500GB should be enough cache for me. Thanks!

Hi, I noticed, that my cache is constantly full when I'm downloading something etc. So I checked which shares use all my space, but only 111,98GB are listed in the "compute all" tab. This would pretty much fill my 120GB 2nd Cache drive. However, I also have a 500GB SSD assigned to the cache pool. There should be plenty of space free but "Fix common problems" tells me, that my cache is full sometimes and read/write speeds are very slow and dockers stopp working when I try to copy some files. Is something wrong with the configuration of my 500GB SSD? server1-diagnostics-20190409-2042.zip

No, never made any How would I recreate it? --UPDATE Switched vm's off & on. Now, my windows vm appears to be running. I hope that everything is ok now. Thanks for your help!

Ok, thanks anyways! //do you think I can install my dockers now, or should I wait?

OK, I enabled the vm & tried to set up my Windows vm as usual. Now, there is no execution Error like before. But it won't start. It only shows me a terminal when I use vnc. Vm-Log: ErrorWarningSystemArrayLogin qxl_cursor: not implemented: type 1 qxl_cursor: not implemented: type 1 qxl_cursor: not implemented: type 1 qxl_cursor: not implemented: type 1 qxl_cursor: not implemented: type 1 qxl_cursor: not implemented: type 1 qxl_cursor: not implemented: type 1 qxl_cursor: not implemented: type 1 qxl_cursor: not implemented: type 1 qxl_cursor: not implemented: type 1 qxl_cursor: not implemented: type 1 qxl_cursor: not implemented: type 1 qxl_cursor: not implemented: type 1 2019-03-26T18:49:01.833348Z qemu-system-x86_64: terminating on signal 15 from pid 12580 (/usr/sbin/libvirtd) 2019-03-26 18:49:02.059+0000: shutting down, reason=shutdown 2019-03-27 20:01:04.999+0000: starting up libvirt version: 4.7.0, qemu version: 3.0.0, kernel: 4.18.20-unRAID, hostname: Server1 LC_ALL=C PATH=/bin:/sbin:/usr/bin:/usr/sbin HOME=/ QEMU_AUDIO_DRV=none /usr/local/sbin/qemu -name 'guest=Windows 10,debug-threads=on' -S -object 'secret,id=masterKey0,format=raw,file=/var/lib/libvirt/qemu/domain-2-Windows 10/master-key.aes' -machine pc-i440fx-3.0,accel=kvm,usb=off,dump-guest-core=off,mem-merge=off -cpu host,hv_time,hv_relaxed,hv_vapic,hv_spinlocks=0x1fff,hv_vendor_id=none -drive file=/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd,if=pflash,format=raw,unit=0,readonly=on -drive file=/etc/libvirt/qemu/nvram/4f89194b-cfee-a0e1-c769-dd2db0317b61_VARS-pure-efi.fd,if=pflash,format=raw,unit=1 -m 4096 -realtime mlock=off -smp 4,sockets=1,cores=2,threads=2 -uuid 4f89194b-cfee-a0e1-c769-dd2db0317b61 -no-user-config -nodefaults -chardev socket,id=charmonitor,fd=27,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=localtime -no-hpet -no-shutdown -boot strict=on -device ich9-usb-ehci1,id=usb,bus=pci.0,addr=0x7.0x7 -device ich9-usb-uhci1,masterbu0,id=serial0 -chardev socket,id=charchannel0,fd=31,server,nowait -device virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=org.qemu.guest_agent.0 -device usb-tablet,id=input0,bus=usb.0,port=1 -vnc 0.0.0.0:1,websocket=5701 -k de -device qxl-vga,id=video0,ram_size=67108864,vram_size=67108864,vram64_size_mb=0,vgamem_mb=16,max_outputs=1,bus=pci.0,addr=0x2 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x6 -sandbox on,obsolete=deny,elevateprivileges=deny,spawn=deny,resourcecontrol=deny -msg timestamp=on 2019-03-27 20:01:04.999+0000: Domain id=2 is tainted: high-privileges 2019-03-27 20:01:04.999+0000: Domain id=2 is tainted: host-cpu 2019-03-27T20:01:05.043084Z qemu-system-x86_64: -chardev pty,id=charserial0: char device redirected to /dev/pts/2 (label charserial0) 2019-03-27 20:01:14.203+0000: shutting down, reason=failed 2019-03-27 20:02:38.643+0000: shutting down, reason=failed 2019-03-27 20:03:48.392+0000: shutting down, reason=failed 2019-03-27 20:04:07.083+0000: shutting down, reason=failed 2019-03-27 20:05:44.669+0000: shutting down, reason=failed 2019-03-27 20:10:15.128+0000: shutting down, reason=failed 2019-03-27 20:10:17.735+0000: shutting down, reason=failed 2019-03-27 20:11:24.939+0000: shutting down, reason=failed 2019-03-29 07:16:15.710+0000: starting up libvirt version: 4.7.0, qemu version: 3.0.0, kernel: 4.18.20-unRAID, hostname: Server1 LC_ALL=C PATH=/bin:/sbin:/usr/bin:/usr/sbin HOME=/ QEMU_AUDIO_DRV=none /usr/local/sbin/qemu -name 'guest=Windows 10,debug-threads=on' -S -object 'secret,id=masterKey0,format=raw,file=/var/lib/libvirt/qemu/domain-1-Windows 10/master-key.aes' -machine pc-i440fx-3.0,accel=kvm,usb=off,dump-guest-core=off,mem-merge=off -cpu host,hv_time,hv_relaxed,hv_vapic,hv_spinlocks=0x1fff,hv_vendor_id=none -drive file=/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd,if=pflash,format=raw,unit=0,readonly=on -drive file=/etc/libvirt/qemu/nvram/e5246ee0-d6b9-d344-1b89-953e4f233599_VARS-pure-efi.fd,if=pflash,format=raw,unit=1 -m 4608 -realtime mlock=off -smp 4,sockets=1,cores=2,threads=2 -uuid e5246ee0-d6b9-d344-1b89-953e4f233599 -no-user-config -nodefaults -chardev socket,id=charmonitor,fd=26,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=localtime -no-hpet -no-shutdown -boot strict=on -device ich9-usb-ehci1,id=usb,bus=pci.0,addr=0x7.0x7 -device ich9-usb-uhci1,masterbu0,id=serial0 -chardev socket,id=charchannel0,fd=30,server,nowait -device virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=org.qemu.guest_agent.0 -device usb-tablet,id=input0,bus=usb.0,port=1 -vnc 0.0.0.0:0,websocket=5700 -k de -device qxl-vga,id=video0,ram_size=67108864,vram_size=67108864,vram64_size_mb=0,vgamem_mb=16,max_outputs=1,bus=pci.0,addr=0x2 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x6 -sandbox on,obsolete=deny,elevateprivileges=deny,spawn=deny,resourcecontrol=deny -msg timestamp=on 2019-03-29 07:16:15.710+0000: Domain id=1 is tainted: high-privileges 2019-03-29 07:16:15.710+0000: Domain id=1 is tainted: host-cpu 2019-03-29T07:16:15.754041Z qemu-system-x86_64: -chardev pty,id=charserial0: char device redirected to /dev/pts/0 (label charserial0) 2019-03-29T07:24:06.973386Z qemu-system-x86_64: terminating on signal 15 from pid 487 (/usr/sbin/libvirtd) 2019-03-29 07:24:07.173+0000: shutting down, reason=destroyed 2019-03-29 07:26:07.985+0000: starting up libvirt version: 4.7.0, qemu version: 3.0.0, kernel: 4.18.20-unRAID, hostname: Server1 LC_ALL=C PATH=/bin:/sbin:/usr/bin:/usr/sbin HOME=/ QEMU_AUDIO_DRV=none /usr/local/sbin/qemu -name 'guest=Windows 10,debug-threads=on' -S -object 'secret,id=masterKey0,format=raw,file=/var/lib/libvirt/qemu/domain-2-Windows 10/master-key.aes' -machine pc-i440fx-3.0,accel=kvm,usb=off,dump-guest-core=off,mem-merge=off -cpu host,hv_time,hv_relaxed,hv_vapic,hv_spinlocks=0x1fff,hv_vendor_id=none -drive file=/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd,if=pflash,format=raw,unit=0,readonly=on -drive file=/etc/libvirt/qemu/nvram/2c128405-9d4a-3e78-8c2a-fb11412148a7_VARS-pure-efi.fd,if=pflash,format=raw,unit=1 -m 5632 -realtime mlock=off -smp 6,sockets=1,cores=3,threads=2 -uuid 2c128405-9d4a-3e78-8c2a-fb11412148a7 -no-user-config -nodefaults -chardev socket,id=charmonitor,fd=26,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=localtime -no-hpet -no-shutdown -boot strict=on -device ich9-usb-ehci1,id=usb,bus=pci.0,addr=0x7.0x7 -device ich9-usb-uhci1,masterbul0,id=serial0 -chardev socket,id=charchannel0,fd=30,server,nowait -device virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=org.qemu.guest_agent.0 -device usb-tablet,id=input0,bus=usb.0,port=1 -vnc 0.0.0.0:0,websocket=5700 -k en-us -device qxl-vga,id=video0,ram_size=67108864,vram_size=67108864,vram64_size_mb=0,vgamem_mb=16,max_outputs=1,bus=pci.0,addr=0x2 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x6 -sandbox on,obsolete=deny,elevateprivileges=deny,spawn=deny,resourcecontrol=deny -msg timestamp=on 2019-03-29 07:26:07.985+0000: Domain id=2 is tainted: high-privileges 2019-03-29 07:26:07.985+0000: Domain id=2 is tainted: host-cpu 2019-03-29T07:26:08.028318Z qemu-system-x86_64: -chardev pty,id=charserial0: char device redirected to /dev/pts/0 (label charserial0) And the diagnostics: server1-diagnostics-20190329-0845.zip

Ok, my appdata, domains, and system shares are now only on the cache: New diagnostics file: server1-diagnostics-20190328-2313.zip