Luca1201
Members
-
Joined
-
Last visited
Everything posted by Luca1201
-
After my cache NVMe dropped offline once again (this has happened several times already), I did a power cycle as i have always done when this happened. Unforunately this time the ssd did not come back. I already put nvme_core.default_ps_max_latency_us=0 and pcie_aspm=off in my syslinux config, but this did not help either. The memory controller is still visible under system devices, though at startup you can see an error in the log: kernel: nvme nvme0: Device not ready; aborting reset, CSTS=0x1 kernel: nvme nvme0: Removing after probe failure status: -19 I also tried switching the slot on my mb but this did not do anything either. Unfortunately i forgot to get diagnostics before rebooting so this is the only thing i got.
-
i got the same issue since upgrading to 6.11
-
after upgrading to os version 6.11.1 i noticed my wireguard tunnel is not autostarting anymore. trying to start it manually over wireguard settings in the webgui results in it being disabling itself immediately. i can start the tunnel as long as there are no peers added, with peers i get the following error trying to start it over cli: root@Tower:~# wg-quick up wg0 [#] ip link add wg0 type wireguard [#] wg setconf wg0 /dev/fd/63 [#] ip -4 address add 10.253.0.1 dev wg0 [#] ip link set mtu 1420 up dev wg0 [#] ip -4 route add 192.168.178.56/32 dev wg0 [#] ip -4 route add 10.253.0.4/32 dev wg0 [#] ip -4 route add 10.253.0.3/32 dev wg0 [#] ip -4 route add 10.253.0.2/32 dev wg0 [#] logger -t wireguard 'Tunnel WireGuard-wg0 started' [#] ip -4 route flush table 200 [#] ip -4 route add default via 10.253.0.1 dev wg0 table 200 [#] ip -4 route add 192.168.178.0/24 via 192.168.178.1 dev table 200 Error: either "to" is duplicate, or "200" is a garbage. [#] ip link delete dev wg0 i also have my diagnostics attached. thank you in advance tower-diagnostics-20221007-2128.zip
