Jump to content

mlapaglia

Members
  • Content Count

    49
  • Joined

  • Last visited

Community Reputation

7 Neutral

About mlapaglia

  • Rank
    Advanced Member

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. i guess wireguard doesn't do a cleanup if you uninstall it: ip link delete wg0 deleting this wg0 made everything start working again
  2. i can't get unraid to connect to the internet, installing docker containers etc fails, viewing the app store fails. when i try to ping google.com i see that it resolves the DNS correctly, but it can't reach it: root@Tower:~# ping google.com PING google.com (172.217.6.14) 56(84) bytes of data. From 10.253.0.1 (10.253.0.1) icmp_seq=1 Destination Host Unreachable ping: sendmsg: Destination address required ^CFrom 10.253.0.1 icmp_seq=2 Destination Host Unreachable ping: sendmsg: Destination address required --- google.com ping statistics --- 2 packets transmitted, 0 received, +2 errors, 100% packet loss, time 5018ms pinging the router, or other devices on the network works fine: root@Tower:~# 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.240 ms ^C --- 192.168.1.1 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.240/0.240/0.240/0.000 ms this morning i installed the wireguard plugin, could that have broken something? i have since uninstalled it. tower-diagnostics-20201020-2338.zip
  3. i think installing wireguard messed with my network settings, is anyone else seeing errors when looking at apps?
  4. well i just ran a memtest and got 240 errors within a minute, so it's probably that. EDIT: 1x16GB stick out of 4 was bad, luckily hyperx has a lifetime warranty
  5. I've been getting errors with my cache drive since i upgraded to a ryzen 3900x and the x570 aorus pro. i have two 500gb nvme drives in the cache pool: i have these issues on the latest stable and the new beta 30 unraid tower-diagnostics-20201017-2258.zip
  6. upgrading from latest stable to 29, it's happening on 30 also. i'll try disabling plugins
  7. i've got an issue with sshfs segfaults after i upgraded, bringing down docker containers etc. restarting brings the user shares back. after upgrade to beta 30 getting even more right after a restart tower-diagnostics-20201007-1132.zip tower-diagnostics-20201007-1142.zip
  8. Has anyone had issues with using both nvme slots for their cache? When I use either one separately the cache works but once I try to use both at once I get IO errors.
  9. So this might have something to do with the board and RAID1. On the suspect drive I formatted it as btrfs separately from the cache and used it as an unassigned device. I copied the entire appdata folder over to it for testing. It copied without any io errors. Since there were no issues here I put the drive back into the cache array. It formatted and set up the RAID1 without any errors. After a restart though, it started throwing IO errors again until I removed the 2nd drive.
  10. Definitely install the "CA Backup / Restore Appdata" plugin and backup your cache drive regularly! Saved me today.
  11. Ok I booted up with the `624` drive inserted by itself and immediately got an IO error and the drive being put into read only mode. I put `552` in by itself and it passes the scrub check with no errors. The btrfs command gives this though: root@Tower:~# btrfs dev stats /mnt/cache [/dev/nvme0n1p1].write_io_errs 6455 [/dev/nvme0n1p1].read_io_errs 5533 [/dev/nvme0n1p1].flush_io_errs 22 [/dev/nvme0n1p1].corruption_errs 0 [/dev/nvme0n1p1].generation_errs 0 It was like this right after boot up, and the value hasn't changed in 15 minutes. VMs and docker are running off of this drive, they all appear to be functioning. I looks like it is re-balancing now since the other drive was removed. Should I try and format the `624` drive and put it back into the array? Is anything like an "IO Error" indicative of a hardware error?
  12. Thanks @johnnie.black, i swapped the drives on the motherboard, it looks like the problem is with the nvme drive since I am now seeing errors about nvme1n1p1? tower-diagnostics-20200224-0816.zip
  13. After moving to my new server, Aorus x570 Pro with a 3900X, my cache is throwing lots of BTRFS errors. I reformatted the cache drive and restored by appdata but am still getting this issue. The cache drives are two nvme drives attached to the motherboard. I've tried reseating them. tower-diagnostics-20200224-0156.zip