Everything posted by beasthouse
-
Time Server
Did you end up figuring this out? I have the same issue, although across VLAN's, but cannot make it work - tried both the servers domain name and IP Address.
-
kernel: BTRFS error - parent transid verify failed
Bingo - Frigate container is restarting over and over.
-
kernel: BTRFS error - parent transid verify failed
Ok so went back to check the logs and now I am getting this repeating again non stop. Any ides? Aug 15 23:16:13 Odin kernel: IPv6: ADDRCONF(NETDEV_CHANGE): vethfb7cb6f: link becomes ready Aug 15 23:16:13 Odin kernel: docker0: port 5(vethfb7cb6f) entered blocking state Aug 15 23:16:13 Odin kernel: docker0: port 5(vethfb7cb6f) entered forwarding state Aug 15 23:16:20 Odin kernel: docker0: port 5(vethfb7cb6f) entered disabled state Aug 15 23:16:20 Odin kernel: veth7497558: renamed from eth0 Aug 15 23:16:20 Odin kernel: docker0: port 5(vethfb7cb6f) entered disabled state Aug 15 23:16:20 Odin kernel: device vethfb7cb6f left promiscuous mode Aug 15 23:16:20 Odin kernel: docker0: port 5(vethfb7cb6f) entered disabled state Aug 15 23:17:20 Odin kernel: docker0: port 5(vethd5d529d) entered blocking state Aug 15 23:17:20 Odin kernel: docker0: port 5(vethd5d529d) entered disabled state Aug 15 23:17:20 Odin kernel: device vethd5d529d entered promiscuous mode Aug 15 23:17:20 Odin kernel: docker0: port 5(vethd5d529d) entered blocking state Aug 15 23:17:20 Odin kernel: docker0: port 5(vethd5d529d) entered forwarding state Aug 15 23:17:20 Odin kernel: docker0: port 5(vethd5d529d) entered disabled state Aug 15 23:17:20 Odin kernel: eth0: renamed from vethe8c8ec8
-
kernel: BTRFS error - parent transid verify failed
curious how you found those errors, would like to become more self sufficient in the future
-
kernel: BTRFS error - parent transid verify failed
UUID: 14fe1259-f0eb-435c-a0e2-6f64f876d8fd Scrub started: Thu Aug 15 21:22:30 2024 Status: finished Duration: 0:01:01 Total to scrub: 267.32GiB Rate: 4.38GiB/s Error summary: no errors found That seems to have sorted it. Now to test the rest I guess.
-
kernel: BTRFS error - parent transid verify failed
New Diagnostics attached and the Scrub results of my Appdata Cache: UUID: 14fe1259-f0eb-435c-a0e2-6f64f876d8fd Scrub started: Thu Aug 15 20:51:52 2024 Status: finished Duration: 0:01:00 Total to scrub: 267.32GiB Rate: 4.46GiB/s Error summary: csum=3 Corrected: 0 Uncorrectable: 3 Unverified: 0 odin-diagnostics-20240815-2054.zip
-
kernel: BTRFS error - parent transid verify failed
Thanks. It rebooted fine. I turned the docker and vm services off and tried updating again and it worked this time. Now to move on to the next steps you recommended.
-
kernel: BTRFS error - parent transid verify failed
Thanks for looking. I started the update but I think it has failed, cannot ping the server anymore so not sure where to go from here 😭 plugin: installing: unRAIDServer.plg Executing hook script: pre_plugin_checks plugin: downloading: unRAIDServer.plg ... done plugin: downloading: unRAIDServer-6.12.11-x86_64.zip ... done plugin: downloading: unRAIDServer-6.12.11-x86_64.md5 ... done Plugin-Update-Helper for 3rd party driver plugins found, updating... writing flash device - please wait... Archive: /tmp/unRAIDServer.zip inflating: /boot/unRAIDServer/bzfirmware inflating: /boot/unRAIDServer/bzfirmware.sha256 inflating: /boot/unRAIDServer/bzimage inflating: /boot/unRAIDServer/bzimage.sha256 inflating: /boot/unRAIDServer/bzmodules inflating: /boot/unRAIDServer/bzmodules.sha256 inflating: /boot/unRAIDServer/bzroot extracting: /boot/unRAIDServer/bzroot-gui inflating: /boot/unRAIDServer/bzroot-gui.sha256 inflating: /boot/unRAIDServer/bzroot.sha256 inflating: /boot/unRAIDServer/changes.txt inflating: /boot/unRAIDServer/license.txt inflating: /boot/unRAIDServer/make_bootable.bat inflating: /boot/unRAIDServer/make_bootable_linux inflating: /boot/unRAIDServer/make_bootable_mac inflating: /boot/unRAIDServer/memtest inflating: /boot/unRAIDServer/syslinux/syslinux.cfg- Did a physical off and on of the server and it booted up fine at v6.12.10. Have attached new diagnostics. Not sure whats going on (IPV6? I turned that on the other day for Matter support) but the logs are spitting this out every minute. Aug 15 19:59:49 Odin kernel: docker0: port 1(veth208483b) entered blocking state Aug 15 19:59:49 Odin kernel: docker0: port 1(veth208483b) entered disabled state Aug 15 19:59:49 Odin kernel: device veth208483b entered promiscuous mode Aug 15 19:59:49 Odin kernel: eth0: renamed from vethb9b7da3 Aug 15 19:59:49 Odin kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth208483b: link becomes ready Aug 15 19:59:49 Odin kernel: docker0: port 1(veth208483b) entered blocking state Aug 15 19:59:49 Odin kernel: docker0: port 1(veth208483b) entered forwarding state Aug 15 19:59:51 Odin dnsmasq[26371]: reading /etc/resolv.conf Aug 15 19:59:51 Odin dnsmasq[26371]: using nameserver 100.100.100.100#53 Aug 15 19:59:56 Odin kernel: docker0: port 1(veth208483b) entered disabled state Aug 15 19:59:56 Odin kernel: vethb9b7da3: renamed from eth0 Aug 15 19:59:56 Odin kernel: docker0: port 1(veth208483b) entered disabled state Aug 15 19:59:56 Odin kernel: device veth208483b left promiscuous mode Aug 15 19:59:56 Odin kernel: docker0: port 1(veth208483b) entered disabled state Aug 15 19:59:56 Odin dnsmasq[26371]: reading /etc/resolv.conf Aug 15 19:59:56 Odin dnsmasq[26371]: using nameserver 100.100.100.100#53 Aug 15 20:00:56 Odin kernel: docker0: port 1(veth2129720) entered blocking state Aug 15 20:00:56 Odin kernel: docker0: port 1(veth2129720) entered disabled state Aug 15 20:00:56 Odin kernel: device veth2129720 entered promiscuous mode Aug 15 20:00:56 Odin kernel: docker0: port 1(veth2129720) entered blocking state Aug 15 20:00:56 Odin kernel: docker0: port 1(veth2129720) entered forwarding state Aug 15 20:00:56 Odin kernel: docker0: port 1(veth2129720) entered disabled state Aug 15 20:00:56 Odin kernel: eth0: renamed from vethc6015ee Aug 15 20:00:56 Odin kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth2129720: link becomes ready Aug 15 20:00:56 Odin kernel: docker0: port 1(veth2129720) entered blocking state Aug 15 20:00:56 Odin kernel: docker0: port 1(veth2129720) entered forwarding state Aug 15 20:00:57 Odin dnsmasq[26371]: reading /etc/resolv.conf Aug 15 20:00:57 Odin dnsmasq[26371]: using nameserver 100.100.100.100#53 Aug 15 20:01:02 Odin kernel: docker0: port 1(veth2129720) entered disabled state Aug 15 20:01:02 Odin kernel: vethc6015ee: renamed from eth0 Aug 15 20:01:02 Odin kernel: docker0: port 1(veth2129720) entered disabled state Aug 15 20:01:02 Odin kernel: device veth2129720 left promiscuous mode Aug 15 20:01:02 Odin kernel: docker0: port 1(veth2129720) entered disabled state Aug 15 20:01:02 Odin dnsmasq[26371]: reading /etc/resolv.conf Aug 15 20:01:02 Odin dnsmasq[26371]: using nameserver 100.100.100.100#53 odin-diagnostics-20240815-1959.zip
-
kernel: BTRFS error - parent transid verify failed
Have been experiencing my server misbehaving the last few days. Things I have changed: Installed Immich (which has been pegging the CPU cores assigned to the container) Added a camera to Frigate which is having its own issues Additionally, my Zigbee USB Adapter keeps dropping and crashing Zigbee2MQTT. Also the Log Bar under the System Info section in the Dashboard has been full at times. I think this is a result of the server misbehaving. The below shows two lines from the logs that start repeating non stop. I have also uploaded my diagnostics. Not quite sure where to go from here. I have stopped Immich for now to see if that is the culprit, but would appreciate some advice if possible. I am not great at identifying stuff in logs. Aug 15 08:00:00 Odin kernel: BTRFS error (device nvme1n1p1: state EA): parent transid verify failed on logical 382166155264 mirror 1 wanted 1541924 found 1541859 Aug 15 08:00:00 Odin kernel: BTRFS error (device nvme1n1p1: state EA): parent transid verify failed on logical 382166155264 mirror 2 wanted 1541924 found 1541859 odin-diagnostics-20240815-0954.zip
-
[Plugin] Appdata.Backup
They are all set to 'Stop, backup, start for each container'. Unless there is another setting I am missing?
-
[Plugin] Appdata.Backup
Hey legends, have a few errors popping up in my logs. Not sure what this one means, let alone how to fix it: [10.06.2024 02:28:03][❌][code-server] tar verification failed! Tar said: tar: Removing leading `/' from member names; mnt/user/appdata/homeassistant/home-assistant_v2.db: Mod time differs; mnt/user/appdata/homeassistant/home-assistant_v2.db: Size differs; mnt/user/appdata/homeassistant/home-assistant.log: Mod time differs; mnt/user/appdata/homeassistant/home-assistant.log: Size differs; mnt/user/appdata/homeassistant/home-assistant_v2.db-wal: Mod time differs; mnt/user/appdata/homeassistant/home-assistant_v2.db-wal: Contents differ; mnt/user/appdata/homeassistant/home-assistant_v2.db-shm: Contents differ As above: [10.06.2024 02:51:40][❌][imagemaid] tar verification failed! Tar said: tar: Removing leading `/' from member names; mnt/app_cache/appdata/plex/Logs/Plex Media Server.log: Mod time differs; mnt/app_cache/appdata/plex/Logs/Plex Media Server.log: Size differs; mnt/app_cache/appdata/plex/Plug-in Support/Databases/com.plexapp.plugins.library.db: Mod time differs; mnt/app_cache/appdata/plex/Plug-in Support/Databases/com.plexapp.plugins.library.db: Contents differ; mnt/app_cache/appdata/plex/Plug-in Support/Databases/com.plexapp.plugins.library.db-wal: Mod time differs; mnt/app_cache/appdata/plex/Plug-in Support/Databases/com.plexapp.plugins.library.db-wal: Contents differ; mnt/app_cache/appdata/plex/Plug-in Support/Databases/com.plexapp.plugins.library.db-shm: Mod time differs; mnt/app_cache/appdata/plex/Plug-in Support/Databases/com.plexapp.plugins.library.db-shm: Contents differ I have double checked the mappings for this one and it keeps occurring: [10.06.2024 02:26:23][❌][cross-seed-misc] '/mnt/user/data/torrents/misc/cross-seed' does NOT exist! Please check your mappings! Skipping it for now. And last one, and why I am here 😉: [10.06.2024 02:57:10][⚠️][Main] An error occurred during backup! RETENTION WILL NOT BE CHECKED! Please review the log. If you need further assistance, ask in the support forum. Any help would be greatly appreciated.
-
iCloud Picture Downloader Docker Template
I had to run a chown on the directory to get it to work, but now works fine.
-
/var/log is getting full (currently 100 % used)
Awesome, thanks. I will take a look to see if this resolves my issue!
-
[Support] MattFaz Repo
What’s the chances of an Unraid install and config guide in the docs?
-
/var/log is getting full (currently 100 % used)
I think this is a USB dongle BT adapter that I use for Home Assistant…
-
/var/log is getting full (currently 100 % used)
Oh wow - any idea on how to troubleshoot that one?
-
/var/log is getting full (currently 100 % used)
I've just started getting the `/var/log is getting full (currently 100 % used)` error. No idea what is causing it. Have uploaded my diagnostics here. Anyone able to point me in the right direction? odin-diagnostics-20230903-2215.zip
-
[Plugin] Plex Streams
@dorganstill no good for me - or should I be restarting something as well? EDIT: literally started working 2 seconds after I posted this, thanks!!!
-
[Plugin] Plex Streams
Hi, have been using this for a while and it was working fine. However, lately there is nothing coming through. I went into the settings and it just spins indefinitely - does not find my server. Any pointers?
-
Case icon requests
-
[Plug-In] Community Applications
yeah was after the header on the webui. found the settings to change all that around in Display Settings. Thanks.
-
[Support] ich777 - AMD Vendor Reset, CoralTPU, hpsahba,...
-
[SUPPORT] pihole for unRaid - Spants repo
Did you find a solution to this?
-
[SUPPORT] pihole for unRaid - Spants repo
Did you have any luck with this?
-
[6.11.1] VPN Tunnel Failing
I was able to get something working by setting the DNS in Peer Settings and on the Client to 1.1.1.1, then tried my PiHole IP, and that works too. It was 10.253.0.1 that was not working. Issue I had in detail: After upgrade to UNRAID 6.11, Wireguard stopped working. I had followed all advice I could find but none of it worked. What did work was changing the DNS address.