maxi1406

Members
  • Posts

    6
  • Joined

  • Last visited

maxi1406's Achievements

Noob

Noob (1/14)

1

Reputation

  1. The problem was indeed that one memory stick was dead
  2. Today (10:35:39) my unraid stoped working for the 3th time, when i look into the logs i see the following (log's are attached) BTRFS error (device nvme0n1p1): block=4037433589760 write time tree block corruption detected My question is if someone can help me with diagnosing the system. syslog.txt
  3. I just installed nextcloud docker on unraid. When I go to the url I get this message: Internal Server Error The server encountered an internal error and was unable to complete your request. Please contact the server administrator if this error reappears multiple times, please include the technical details below in your report. More details can be found in the server log. When is look at the log of the docker this is what I get: s6-init] making user provided files available at /var/run/s6/etc...exited 0. [s6-init] ensuring user provided files have correct perms...exited 0. [fix-attrs.d] applying ownership & permissions fixes... [fix-attrs.d] done. [cont-init.d] executing container initialization scripts... [cont-init.d] 10-adduser: executing... ------------------------------------- _ () | | ___ _ __ | | / __| | | / \ | | \__ \ | | | () | |_| |___/ |_| \__/ Brought to you by linuxserver.io We gratefully accept donations at: https://www.linuxserver.io/donate/ ------------------------------------- GID/UID ------------------------------------- User uid: 99 User gid: 100 ------------------------------------- [cont-init.d] 10-adduser: exited 0. [cont-init.d] 20-config: executing... [cont-init.d] 20-config: exited 0. [cont-init.d] 30-keygen: executing... using keys found in /config/keys [cont-init.d] 30-keygen: exited 0. [cont-init.d] 40-config: executing... [cont-init.d] 40-config: exited 0. [cont-init.d] 50-install: executing... [cont-init.d] 50-install: exited 0. [cont-init.d] 60-memcache: executing... [cont-init.d] 60-memcache: exited 0. [cont-init.d] 99-custom-files: executing... [custom-init] no custom files found exiting... [cont-init.d] 99-custom-files: exited 0. [cont-init.d] done. [services.d] starting services [services.d] done. I don't know how I can fix it
  4. i want to switch to unraid so I decided to download the software with trail license. After installing everything I need I ran in to a problem. The problem is that nextcloud is installed in a docker and this docker cannot reach the unraid server, but the docker can reach other devices in both networks (VLAN1 & VLAN2) This is a problem because I want to use external storage on the nextcloud docker. The unraid server cannot reach the nextcloud docker Docker vm is in VLAN2 192.168.2.10/24 Unraid server is in VLAN 1 192.168.1.142/24 ping from the docker root@a5cab6469e88:/# ping 192.168.2.1 PING 192.168.2.1 (192.168.2.1): 56 data bytes 64 bytes from 192.168.2.1: seq=0 ttl=64 time=0.374 ms ^C --- 192.168.2.1 ping statistics --- 1 packets transmitted, 1 packets received, 0% packet loss round-trip min/avg/max = 0.374/0.374/0.374 ms root@a5cab6469e88:/# ping 192.168.1.1 PING 192.168.1.1 (192.168.1.1): 56 data bytes 64 bytes from 192.168.1.1: seq=0 ttl=64 time=0.362 ms 64 bytes from 192.168.1.1: seq=1 ttl=64 time=0.407 ms ^C --- 192.168.1.1 ping statistics --- 2 packets transmitted, 2 packets received, 0% packet loss r ound-trip min/avg/max = 0.362/0.384/0.407 ms root@a5cab6469e88:/# ping 192.168.1.203 PING 192.168.1.203 (192.168.1.203): 56 data bytes 64 bytes from 192.168.1.203: seq=0 ttl=63 time=71.704 ms 64 bytes from 192.168.1.203: seq=1 ttl=63 time=158.055 ms ^C --- 192.168.1.203 ping statistics --- 2 packets transmitted, 2 packets received, 0% packet loss round-trip min/avg/max = 71.704/114.879/158.055 ms root@a5cab6469e88:/# ping 192.168.1.142 PING 192.168.1.142 (192.168.1.142): 56 data bytes ^C --- 192.168.1.142 ping statistics --- 6 packets transmitted, 0 packets received, 100% packet loss root@a5cab6469e88:/# Ping from the UnRAID server root@UnRAID:~# ping 192.168.2.10 PING 192.168.2.10 (192.168.2.10) 56(84) bytes of data. ^C --- 192.168.2.10 ping statistics --- 4 packets transmitted, 0 received, 100% packet loss, time 2029ms root@UnRAID:~# ping 192.168.2.1 PING 192.168.2.1 (192.168.2.1) 56(84) bytes of data. 64 bytes from 192.168.2.1: icmp_seq=1 ttl=64 time=0.395 ms 64 bytes from 192.168.2.1: icmp_seq=2 ttl=64 time=0.323 ms ^C --- 192.168.2.1 ping statistics --- 2 packets transmitted, 2 received, 0% packet loss, time 1019ms rtt min/avg/max/mdev = 0.323/0.359/0.395/0.036 ms root@UnRAID:~# ping 192.168.1.1 PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data. 64 bytes from 192.168.1.1: icmp_seq=1 ttl=64 time=0.370 ms 64 bytes from 192.168.1.1: icmp_seq=2 ttl=64 time=0.282 ms ^C --- 192.168.1.1 ping statistics --- 2 packets transmitted, 2 received, 0% packet loss, time 1022ms rtt min/avg/max/mdev = 0.282/0.326/0.370/0.044 ms