Gibbo2787

Thanks that worked a treat I'll make new databases again - If they keep getting corrupted what do you suggest? New drive? I have a second one installed as a second cache and I was about to put it in place of this drive before you gave me this solution.

unraid-diagnostics-20241225-0155.zip

Another one? I ran one when this problem first started. I ran it for hours and it showed no problems with RAM. I mean, I'm happy to do one, but i just feel like I'm going in circles

I appreciate you trying to help, i really do. I ended up getting it going again last night, got everything finally installed - created new databases etc but that was shortlived. Plex went down again after about 6 hours reporting database corruption again. I have also started noticed some media file wont playback, even from a different device say the file itself is corrupted making me think the corruption is a bit deeper than just the cache drive. I've ran checks on all the disks but nothing jumps out - I have been trying to work out what is what by getting chatgpt to dumb it down for me. I can't work out a way to scan my whole media directory to see what else is corrupted, I only notice if i happen to try and play it. I'm sure there is a way, I checked out Dynamix File Integrity, but it looks like I should have had that setup before all this happened so it could compare checksums. I have a second SSD installed, I will backup all files to that and reformat the orginal and see what happens. I just backed up everything - removed the cache from the array and reformatted. Now upon restart its saying - Unmountable: Unsupported or no file system. Is it cactus?

I've got most of my containers reinstalled to some extent - however theres still things going on - Can someone please point me in the right direction. Ive been up for hours trying to get this sorted and its wearing thin. When i go to install my last container (regardless of what it is) I'm met with this error now docker: Error response from daemon: error creating temporary lease: write /var/lib/docker/containerd/daemon/io.containerd.metadata.v1.bolt/meta.db: read-only file system: unknown. I have around 20 containers installed. I increased the docker image from 20gb to 30gb. I read somewhere to perform a balance. I found an option to perform a full balance on the cache but it doesnt appear to do anything. It says above the button "No balance found on '/mnt/cache'". Found a command on another thread to run in terminal - btrfs balance start -dusage=75 /mnt/cache but was met with this message. "ERROR: error during balancing '/mnt/cache': Input/output error There may be more info in syslog - try dmesg | tail" I also just checked the log and its littered with error messages, all relating to btrfs i beleive. I have attached the log and diagnostics, hoping someone with more knowledge can help me out. unraid-syslog-20241223-0226.zip unraid-diagnostics-20241223-1329.zip

Containers not installing now because of an error saying its a read only file system. When I stop and restart the docker service, it fails to start, and I have to recreate it again. How do i nuke this thing and start again

Well i tried. Deleted the docker image and now I'm reinstalling the containers from previously installed app, watching them fail 1 by 1 . Now nothing works FML This always seems to be the problem - not sure why it kept reoccuring

Finally got around to doing the memtest today - Completed 5 passes with 0 errors upon reboot was met again with bzfirmware checksum error - see attached photo recreated the flash drive again and copied over contents of the config folder. Booted back up fine then. Started the array Performed a scrub on the cache pool - 0 errors found. Now do i have to delete the docker image and recreate or is there something else I should test first?

Thanks for the quick reply. -What would cause this? Is it common? Its the second time I've been in this predicament. Along with failing flash drives and bzfirmware firmware checksum errors, I seem to be always trying to keep this system running. Is there something I should be checking to avoid these issues?

Today i noticed i couldnt start my docker containers once stopped. Began receiving a Error 403 message when trying to start them up. I have attached a system log - looks like a lot of errors begin Dec18 at 10:30+ Can someone please make sense of it for me. Am i going to have to nuke the whole docker image file? unraid-syslog-20241218-1221.zip

Today i got home and found my server had crashed again - It happens constantly - probably once every few months. This time I had the syslog writing to the USB flash drive. I was hoping someone could work out why it is happening and what I need to do to fix it. Upon restarting the server i get met with bzfirmware checksum error. I copied all fresh bz files to the root of the USB, but still had errors while trying to reset the GPU driver - I kept getting met with a checksum error there too. The only solution which appears to be a temporary one so far is to write a new flash drive and copy the config folder - even then i still have to redownload the Nvidia GPU driver everytime. Heres hoping someone knows whats happening. Please see the attached file for the logs - The crash happened after 12:30pm on Nov 22 syslog

Hey, I've had my setup working for a good year or 3 now - but today I came home to notice my qbittorent had failed. It appears to be the vpn failing in some way. Ive always had it setup with PIA with ovpn - although its never been perfect (always seems to drop once every few days). Today it had failed completely and no matter which ovpn config file I use, I am met with this error in the logs which I have never seen before. 2024-07-05 19:25:40.956943 [info] Host is running unRAID 2024-07-05 19:25:40.971183 [info] System information Linux 230c4a41d578 6.1.79-Unraid #1 SMP PREEMPT_DYNAMIC Fri Mar 29 13:34:03 PDT 2024 x86_64 GNU/Linux 2024-07-05 19:25:40.987430 [info] SHARED_NETWORK not defined (via -e SHARED_NETWORK), defaulting to 'no' 2024-07-05 19:25:41.003490 [info] PUID defined as '99' 2024-07-05 19:25:41.021934 [info] PGID defined as '100' 2024-07-05 19:25:41.050518 [info] UMASK defined as '000' 2024-07-05 19:25:41.066275 [info] Permissions already set for '/config' 2024-07-05 19:25:41.085321 [info] Deleting files in /tmp (non recursive)... 2024-07-05 19:25:41.107493 [info] VPN_ENABLED defined as 'yes' 2024-07-05 19:25:41.124685 [info] VPN_CLIENT defined as 'openvpn' 2024-07-05 19:25:41.140824 [info] VPN_PROV defined as 'pia' 2024-07-05 19:25:41.164674 [info] OpenVPN config file (ovpn extension) is located at /config/openvpn/au_sydney.ovpn 2024-07-05 19:25:41.199526 [info] VPN remote server(s) defined as 'au-sydney.privacy.network,' 2024-07-05 19:25:41.214292 [info] VPN remote port(s) defined as '502,' 2024-07-05 19:25:41.229797 [info] VPN remote protcol(s) defined as 'tcp-client,' 2024-07-05 19:25:41.246745 [info] VPN_DEVICE_TYPE defined as 'tun0' 2024-07-05 19:25:41.263928 [info] VPN_OPTIONS not defined (via -e VPN_OPTIONS) 2024-07-05 19:25:41.280084 [info] NAME_SERVERS defined as '1.1.1.1,1.0.0.1,8.8.8.8,8.8.4.4,' Error: error sending query: Error creating socket Error: error sending query: Error creating socket Has anyone got this error - Or have an idea how to fix it?

I finally got the chance to shut down my server and perform a memtest. Everything looked ok after several passes. I then performed the scrub on the pool. (Its just the cache right?) This resulted in multiple BTRFS errors and one the says "xhci_hcd 0000:01:00.2: xHC error in resume, USBSTS 0x401, Reinit". Please see the attached log for the errors. (At the bottom) Can i correct these by enabling "repair corrupted blocks" and performing the scrub again? EDIT* - Tried the scrub with repair corrupted blocks and they appear to be uncorrectable Or should I manually find the file in question and delete it? EDIT* - I just went through and deleted all the corrupted files and its flagging no errors during the scrub now. I'll see how it goes in the coming weeks/months - hopefully that has sorted out the issue. Now to sort out the Prowlarr connectivity issue and I won't have to spend so much time checking the server. syslog.txt

Cheers, appreciate the reply. Its just running a parity check after the reboot. Once its completed, I'll run a memtest. Not entirely sure how to perform a scrub, but I'll work it out. I'll post results once completed. Thanks again

I have been using unraid for a couple years now. But I've never been able to get it completely stable. I have 2 major problems. The first being with the prowlarr container. For some reason it always disconnects every few days and I have to manually restart the container and test all indexers to get everything working again for the next few days until it happens again. I think it may have something to do with openvpn that i am running it behind - My assumption is the vpn loses connectivity and then can not connect again after that - saying that, my assumption isn't based on much. I'm not even sure the syslog will show anything regarding this. But maybe someone has some ideas? The second and more major is the constant crashes, which result in me having to create a new USB flash drive and drag/drop the config folder over to get it going again. My server just had the longest runtime of its life of about 40 days, but this time I have had the syslog enabled and backing up to my flash drive so it was recoverable after the crash. However I need help decoding what's actually going on. I have attached the syslog file, hopefully someone could skim over it and identify the problem(s) I am experiencing. Any help would be greatly appreciated. syslog