Mito17

Okay, then unfortunately I have no idea what else I could try.

So I have installed a new RAM, replaced the network card and in the meantime I have switched from the Trail version to Starter. The failures still occur. I am currently using a USB 3 stick as a boot stick, could the failures be coming from the USB stick? If so, I would create another one with a USB 2 stick. Or can it not be the USB stick anyway, because the operating system runs in RAM after the start anyway?

You mean multiple sticks of RAM? Unfortunately I only have one 8GB stick. But you would start troubleshooting with the RAM?

I already tried that, it also lost the connection. I have 2 LAN connections on my router, I've already tested both, so I don't think it's the router either. What do you think is the best order for troubleshooting the hardware? Test a new network card first? It would at least be cheap, as there are some from TP-Link for 10 euros.

Hi, my Unraid server is always unavailable at irregular intervals. It is displayed as offline in the FritzBox and in Tailscale. Whenever this happens, both HDDs spin continuously even though they were in sleep mode before the connection was lost. I have set a static IP and entered the Google DNS for the second DNS, unfortunately no improvement. I have restarted Docker several times and also deactivated all containers to rule out the possibility that a container is faulty. Unfortunately, no change either. Here are two logs. I always restarted the server and then it worked again. Tonight the server also went down, I can see in the FritzBox that it was last online shortly before 23:00. However, the log is empty today, so no error message was written. Nov 1 00:00:02 Tower emhttpd: read SMART /dev/sdc Nov 1 00:01:04 Tower kernel: docker0: port 5(veth05bd3cd) entered disabled state Nov 1 00:01:04 Tower kernel: veth3bdc010: renamed from eth0 Nov 1 00:01:04 Tower kernel: docker0: port 5(veth05bd3cd) entered disabled state Nov 1 00:01:04 Tower kernel: device veth05bd3cd left promiscuous mode Nov 1 00:01:04 Tower kernel: docker0: port 5(veth05bd3cd) entered disabled state Nov 1 00:01:06 Tower kernel: docker0: port 5(vethaf16d2a) entered blocking state Nov 1 00:01:06 Tower kernel: docker0: port 5(vethaf16d2a) entered disabled state Nov 1 00:01:06 Tower kernel: device vethaf16d2a entered promiscuous mode Nov 1 00:01:06 Tower kernel: docker0: port 5(vethaf16d2a) entered blocking state Nov 1 00:01:06 Tower kernel: docker0: port 5(vethaf16d2a) entered forwarding state Nov 1 00:01:06 Tower kernel: docker0: port 5(vethaf16d2a) entered disabled state Nov 1 00:01:06 Tower kernel: eth0: renamed from vethafd474e Nov 1 00:01:06 Tower kernel: IPv6: ADDRCONF(NETDEV_CHANGE): vethaf16d2a: link becomes ready Nov 1 00:01:06 Tower kernel: docker0: port 5(vethaf16d2a) entered blocking state Nov 1 00:01:06 Tower kernel: docker0: port 5(vethaf16d2a) entered forwarding state Nov 1 00:01:09 Tower kernel: docker0: port 4(veth3ddf24b) entered disabled state Nov 1 00:01:09 Tower kernel: vethfa133b3: renamed from eth0 Nov 1 00:01:09 Tower kernel: docker0: port 4(veth3ddf24b) entered disabled state Nov 1 00:01:09 Tower kernel: device veth3ddf24b left promiscuous mode Nov 1 00:01:09 Tower kernel: docker0: port 4(veth3ddf24b) entered disabled state Nov 1 00:01:09 Tower kernel: docker0: port 4(vethfa43be8) entered blocking state Nov 1 00:01:09 Tower kernel: docker0: port 4(vethfa43be8) entered disabled state Nov 1 00:01:09 Tower kernel: device vethfa43be8 entered promiscuous mode Nov 1 00:01:09 Tower kernel: docker0: port 4(vethfa43be8) entered blocking state Nov 1 00:01:09 Tower kernel: docker0: port 4(vethfa43be8) entered forwarding state Nov 1 00:01:09 Tower kernel: eth0: renamed from veth51aa2a4 Nov 1 00:01:09 Tower kernel: IPv6: ADDRCONF(NETDEV_CHANGE): vethfa43be8: link becomes ready Nov 1 00:01:12 Tower kernel: docker0: port 3(vethbd2c652) entered disabled state Nov 1 00:01:12 Tower kernel: veth1bd9279: renamed from eth0 Nov 1 00:01:12 Tower kernel: docker0: port 3(vethbd2c652) entered disabled state Nov 1 00:01:12 Tower kernel: device vethbd2c652 left promiscuous mode Nov 1 00:01:12 Tower kernel: docker0: port 3(vethbd2c652) entered disabled state Nov 1 00:01:19 Tower kernel: docker0: port 3(vethfdcc221) entered blocking state Nov 1 00:01:19 Tower kernel: docker0: port 3(vethfdcc221) entered disabled state Nov 1 00:01:19 Tower kernel: device vethfdcc221 entered promiscuous mode Nov 1 00:01:20 Tower kernel: eth0: renamed from veth72f789f Nov 1 00:01:20 Tower kernel: IPv6: ADDRCONF(NETDEV_CHANGE): vethfdcc221: link becomes ready Nov 1 00:01:20 Tower kernel: docker0: port 3(vethfdcc221) entered blocking state Nov 1 00:01:20 Tower kernel: docker0: port 3(vethfdcc221) entered forwarding state Nov 1 00:01:22 Tower kernel: docker0: port 2(vethbf1023a) entered disabled state Nov 1 00:01:22 Tower kernel: vethb7f4693: renamed from eth0 Nov 1 00:01:22 Tower kernel: docker0: port 2(vethbf1023a) entered disabled state Nov 1 00:01:22 Tower kernel: device vethbf1023a left promiscuous mode Nov 1 00:01:22 Tower kernel: docker0: port 2(vethbf1023a) entered disabled state Nov 1 00:01:54 Tower kernel: docker0: port 2(veth225892b) entered blocking state Nov 1 00:01:54 Tower kernel: docker0: port 2(veth225892b) entered disabled state Nov 1 00:01:54 Tower kernel: device veth225892b entered promiscuous mode Nov 1 00:01:54 Tower kernel: eth0: renamed from veth2ff4761 Nov 1 00:01:54 Tower kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth225892b: link becomes ready Nov 1 00:01:54 Tower kernel: docker0: port 2(veth225892b) entered blocking state Nov 1 00:01:54 Tower kernel: docker0: port 2(veth225892b) entered forwarding state Nov 1 00:01:56 Tower kernel: docker0: port 1(veth48dc9bc) entered disabled state Nov 1 00:01:56 Tower kernel: vethfda0dfa: renamed from eth0 Nov 1 00:01:56 Tower kernel: docker0: port 1(veth48dc9bc) entered disabled state Nov 1 00:01:56 Tower kernel: device veth48dc9bc left promiscuous mode Nov 1 00:01:56 Tower kernel: docker0: port 1(veth48dc9bc) entered disabled state Nov 1 00:01:56 Tower kernel: docker0: port 1(vethd46d60a) entered blocking state Nov 1 00:01:56 Tower kernel: docker0: port 1(vethd46d60a) entered disabled state Nov 1 00:01:56 Tower kernel: device vethd46d60a entered promiscuous mode Nov 1 00:01:56 Tower kernel: docker0: port 1(vethd46d60a) entered blocking state Nov 1 00:01:56 Tower kernel: docker0: port 1(vethd46d60a) entered forwarding state Nov 1 00:01:57 Tower kernel: eth0: renamed from veth942b1f8 Nov 1 00:01:57 Tower kernel: IPv6: ADDRCONF(NETDEV_CHANGE): vethd46d60a: link becomes ready Nov 1 00:21:44 Tower kernel: traps: .NET TP Worker[4664] general protection fault ip:149b46f6650f sp:1459e7bfcdc0 error:0 in libc.so.6[149b46f66000+155000] Nov 4 08:35:53 Tower emhttpd: spinning down /dev/sdb Nov 4 09:42:37 Tower kernel: docker0: port 2(veth2f44210) entered disabled state Nov 4 09:42:37 Tower kernel: veth8d88aa5: renamed from eth0 Nov 4 09:42:37 Tower kernel: docker0: port 2(veth2f44210) entered disabled state Nov 4 09:42:37 Tower kernel: device veth2f44210 left promiscuous mode Nov 4 09:42:37 Tower kernel: docker0: port 2(veth2f44210) entered disabled state Nov 4 09:42:38 Tower kernel: docker0: port 2(veth351a094) entered blocking state Nov 4 09:42:38 Tower kernel: docker0: port 2(veth351a094) entered disabled state Nov 4 09:42:38 Tower kernel: device veth351a094 entered promiscuous mode Nov 4 09:42:38 Tower kernel: docker0: port 2(veth351a094) entered blocking state Nov 4 09:42:38 Tower kernel: docker0: port 2(veth351a094) entered forwarding state Nov 4 09:42:38 Tower kernel: eth0: renamed from veth202247a Nov 4 09:42:38 Tower kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth351a094: link becomes ready Nov 4 09:44:25 Tower kernel: docker0: port 4(veth64092c0) entered disabled state Nov 4 09:44:25 Tower kernel: vethda4b73e: renamed from eth0 Nov 4 09:44:25 Tower kernel: docker0: port 4(veth64092c0) entered disabled state Nov 4 09:44:25 Tower kernel: device veth64092c0 left promiscuous mode Nov 4 09:44:25 Tower kernel: docker0: port 4(veth64092c0) entered disabled state Nov 4 09:44:25 Tower kernel: docker0: port 4(vetha7f777c) entered blocking state Nov 4 09:44:25 Tower kernel: docker0: port 4(vetha7f777c) entered disabled state Nov 4 09:44:25 Tower kernel: device vetha7f777c entered promiscuous mode Nov 4 09:44:25 Tower kernel: docker0: port 4(vetha7f777c) entered blocking state Nov 4 09:44:25 Tower kernel: docker0: port 4(vetha7f777c) entered forwarding state Nov 4 09:44:25 Tower kernel: eth0: renamed from vethd741acc Nov 4 09:44:25 Tower kernel: IPv6: ADDRCONF(NETDEV_CHANGE): vetha7f777c: link becomes ready Nov 4 14:46:48 Tower root: Delaying execution of fix common problems scan for 10 minutes Nov 4 14:46:48 Tower emhttpd: Starting services...

So einfach wärs gewesen, vielen Dank Hab jetzt appdata, domains und system data auf Cache. Wenn das alles verschoben wurde, kann ich in den jeweiligen Share settings Array als secondary storage entfernen, richtig?

Hallo zusammen, ich habe Unraid komplett auf einer HDD installiert, heißt Appdata und System Daten waren auch auf der HDD. War blödsinn, ging aber zum Zeitpunkt der Installation leider nicht anders. Jetzt möchte ich alles was Systemdaten betrifft auf eine SSD schieben, sodass die HDD nur noch anläuft, wenn wirklich über Jellyfin o.Ä. was geschrieben oder gelesen werden muss. Ich habe in den Share Settings Primary storage auf Cache, also auf die SSD, gesetzt. Mover action auf Array -> Cache. Danach habe ich alle Docker beendet und unter Settings -> Docker -> Enable Docker auf No gesetzt. Dann hab ich den Mover gestartet. Appdata wurde komplett auf Cache verschoben, System wurde bis auf 1GB auf Cache verschoben. 1GB bleibt leider auf Disk1 (HDD). Gibt es irgendeine Möglichkeit zu prüfen woran das liegt? Scheint ja so als würde da im System noch irgendwas laufen und deswegen nicht verschoben werden können oder?

Hi, I am pretty new to this whole home server / unraid world, so I am sorry if this is a dumb question. I have installed the tailscale plugin, registered the server and everything worked so far. I am able to connect the Unraid via my iPhone, the connection is somehow slow, but maybe thats normal? The main reason why I wanted to use Tailscale is Jellyfin. I managed to get the connection in the Jellyfin App and with Infuse by using the Tailscale IP with Port 8096 for Jellyfin. My library is loading on both Jellyfin and Infuse App, but the movies won't start. I also tried it on my iPad as i thought maybe the iPhone is the problem, but it does't work. I also tried the manage my jDownloader via Tailscale by using a hotspot from my iPhone to my Laptop. It works but it's really very slow, so that might be the problem. I don't know why it is that slow, cause I have 5G on my Phone and Speedtest says 150 Mbps. Is there anything I can do/try?