jbeazies

Hello fellow unraiders. Came across trash-guides : Unraid - TRaSH Guides (trash-guides.info) and hoping for some insight before I potentially cause some unrecoverable problems. Current folder structure: Media --Movies --TV Shows Storage --torrents ----Completed ----Incomplete My Storage share is actually a single 250GB drive sitting outside the array and used merely for storage of downloads. The way that trash-guides appears to recommend folder structure is for all content to be underneath a root 'data' folder. Unless I'm misunderstanding shares, would this not put all content within the raid array? Ultimately I'm looking for guidance on how to make the transition safely, not lose any of my media, and hopefully repair some issues I've been having where the autodownload primarily on TV Series in Sonarr doesn't generally work and move the files requiring me to manually move them using the Manual Import button. If there's a better way to fix that I'm all ears.

Following up - Just got a kernel panic sometime early this morning despite reconfiguring my only static ip'd docker to a br0.4 vlan.

Chiming in - also experienced more frequent kernel panics after update to 6.9.1. I only had 1 docker assigned to a static IP on br0 (Unifi controller). Followed the instructions Network isolation in unRAID 6.4 because luckily capable of configuring vlans due to unifi equipment. Haven't had any panics since.

Appreciate the feedback everyone. The btrfs restore options never worked so I ended up formatting the cache entirely and restoring from my CA appdata backup. Everything seems fine with the exception of my proxynet config - which is now gone.

Thanks, I attempted that with no success. Initially with the array started kept receiving nvme0n1 already mounted or busy. Stopped the array tried again and got a wrong fs, wrong option, bad superblock message.

btrfs

Unraid: 6.8.3 Plugins: CA, CA Backup, Fix common problems, Nerd Tools, Speedtest, Unassigned Devices Hardware: Intel Xeon D-1541 Super Micro X10SDV-TLN4F 32GB Crucial ECC Samsung 500GB NVMe Discovered plex was down, decided to reboot the whole system due to a 403 error when attempting to restart the docker, only to find serious potential issue with my nvme cache drive. I probably got ahead of myself by deleting the docker image and trying to remake it, only to discover additional errors relating to cache filesystem. Cache settings - File system status - Unmountable: No file system. Jul 6 19:11:05 Tower root: Fix Common Problems: Error: Share storagecache set to use cache only, but the cache drive is not present Jul 6 19:11:05 Tower root: Fix Common Problems: Error: Share system set to use cache only, but the cache drive is not present I can confirm the nvme0n1 drive is being seen and all smarts point to a good drive. Attempted to follow some recommendations in the FAQ but didn't get very far. I can't start the docker service because its supposed to be on my nvme cache along with all my appdata. I hope I haven't lost my dockers & config due to something silly on my part, but I believe most of the content is backed up. tower-diagnostics-20200706-1917.zip

Thanks all! This was primarily for my Unifi controller docker. I suppose I could slowly start migrating my other dockers over, but for now those remain on a combination of bridge/host network types. I'll monitor the status of the unifi docker and fingers cross, hope this resolves the issue. Now that I think about it, I'm wondering if this had anything to do with my original issue. I set a static IP to my primary network via USG for the controller docker. I also set the custom br0 within unraid docker config to that same static IP. I wonder if this somehow caused the conflict, resulting in unraid sys locking up?

Are there any instructions on creating and assigning VLAN to a docker container? Is it just setting VLAN on and putting the 169.x address into the custom br0 docker config?

@kingfetty - What did you do as a workaround? I still want to use static IP for my unifi-controller docker.

Frank I just happened to find these threads: I too had the unificontroller set to custom br0 with fixed ip. I'll work on altering those settings to host for the time being.

Hey guys, I'm still having issues with my server becoming unresponsive to anything and stuck with a screen similar to this.. Unable to access the system at all. This is the only notable interaction, a photo of the screen. The only commonality I've found is the Unifi-controller docker. If I enable it then it'll crash my unraid server with the following symptoms intermittently. When I originally observed this behavior I thought I had it narrowed down to this specific docker after many hours of troubleshooting. At the time I thought it was because I attempted to downgrade controller version from v5.9 to the LTS branch (~v5.6). Since then I completely removed the Unifi-controller docker with a clean install and a clean config. Here is my current config - same except for newer version of unraid & lts of unifi. Unraid version: 6.7.2 Plugins: CA Auto updates, CA Backup, Community Applications, FCP, Preclear Disks, Server Layout, Statistics, Unassigned Devices Dockers: binhex deluge, jacket, unificontroller, duckdns, letsencrypt, radar, openvpnas, plex, sabnzbd, sonar, ombi, lazylibrarian Hardware: Supermicro - X10SDV-TLN4F Intel Xeon CPU D-1541 NVM/IOMMU Enabled 32GB ECC Corsair Memory Symptoms : -WebUI not responsive (took to long to respond, site can't be reached) -Ping reply: Destination host unreachable -SSH not responsive (Connection timed out) -SMB Share / Network name via file Explorer unable to access (Network path was not found) Any other suggestions? I can't grab any logs because the system is completely hung

I thought I had this fixed but issue reoccurred last night with the same kworker process utilizing 100% of CPU. Only thing I could do was a hard reset. I did as suggested and everything is pointed to a /mnt directory in docker & plugin configs. Here is something I've been able to catch

Thanks for the feedback Frank. I haven't noticed anything you mentioned out of place but I'll give it another lookover. I did actually find FCP pointing out my two dockers didn't have the Slave option, but adjusted that to the recommended RW/Slave. I had the parity running from yesterday and its at 81% but the CPU usage I just discovered is at 100% and isn't moving. I ran top and the process using my entire cpu is kworker/u32:1+events_power_efficient

I haven't made many posts because unraid has been near flawless for many years, but lately I've been having issues that I can't pinpoint and unfortunately I have not done a great job at tracking my changes. Most of the changes include docker updates and downloads. Unraid version: 6.6.7 Plugins: CA Auto updates, CA Backup, Community Applications, FCP, Preclear Disks, Server Layout, Statistics, Unassigned Devices Dockers: binhex deluge, jacket, unificontroller, duckdns, letsencrypt, radar, openvpnas, plex, sabnzbd, sonar, ombi, lazylibrarian VMs: ubuntu, WinServer 2016 essentials *letsencrypt, lazylibrarian, ubuntu, ws2016 are stopped most of the time and not running Hardware: Supermicro - X10SDV-TLN4F Intel Xeon CPU D-1541 NVM/IOMMU Enabled 32GB ECC Corsair Memory Issue: Somewhat randomly (might take a day, might take several), I lose all connectivity to the WebGUI, Dockers, SSH, seemingly everything. What continues to work is the local terminal (via mouse/key). I can't pinpoint what I'm doing at the exact time but generally just watching plex or checking out the unifi controller, so I'm guessing it must be some process happening behind the scenes or potentially something with an automatic downloader. I still can login via root on the local term but get further sometimes and other times not far at all (e.g. sometimes ifconfig will run, othertimes it won't - one of the few Linux commands I know Diagnostics never completes - just stays at collecting... for hours. I managed to collect a syslog a cp /var/log/syslog /boot/syslog command Troubleshooting: MemTest cleared 2 passes, no recent hardware changes, no smart errors that I can tell, parity always passes - and I've ran dozens over the past couple weeks due to the hard shutdowns. Last night I thought I'd boot to SafeMode - It was going smooth until I happened to notice today while I was vpn'd to my server via unraid supervisor app on ios that the memory usage seemed to be at 76% before it crashed this time - I thought that was a bit unusual because I've never seen it reach that high, but could have been a coincidence idk. I appreciate any help/advice. syslog.zip

edit- It's almost as if none of the dockers can communicate. Is there any additional way to confirm this? I can ping all the local internally assigned App IP's of the local dockers (the 172.x addresses) via unraid terminal. Hi unraid warriors, I recently upgraded an apple router to one of those greatly recommended unifi systems - Unifi Gateway + Unifi AP Pro. I believe I've got the router and ap configured correctly with port forwarding and static ip addresses where applicable, but I just recently noticed that several of my dockers namely: Sabnzbd, Sonarr, Radarr are no longer communicating and I can't manually search for content. When manually searching (radarr) I get " There was an error searching for : xxx" The system log (radarr) shows pretty much all the components failing with something resembling : Unable to connect to SABnzbd, please check your settings: Unable to connect to SABnzbd, please check your settings Unable to retrieve queue and history items from deluge-torrent: Error: ConnectFailure (No route to host) A couple things have happened since the router upgrade. I also upgraded from 6.4.1 to 6.5.3 and of course updated to the latest docker versions that were available as of today. I feel like an idiot for not testing the full functionality of all my dockers prior to making any other changes after installing the gateway but now I'm at a loss. It seemed like everything was working - Internet / wifi connectivity on lan and other laptops/desktops, Unifi docker running and reporting everything is fine, OpenVPN and duckdns docker up and connected outside of lan, etc, etc. I do run most default config to keep things simple and supportable but I can't figure out what I'm missing and I fear it's something I've overlooked in the Unifi Gateway? Hoping someone might be able to shed some light on something, or anything at all. I feel I can rule out the upgrades to unraid/dockers because its been 4 days since anything automated got queued and the router went in Sunday (two days ago). I had piHole running but I disabled it for troubleshooting.

Forgive me if this has been asked before, but I was unable to find anything referencing such material. I'm hoping I could find some positive/negative feedback on using my unRAID Network Share (SMB/UNC path) as the primary download directory from my Newsbin Seed PC. I've now discovered (after building a secondary completely silent ATOM SEED PC) there are several SAZNB / Couchpotato available However; rather than messing up my flawless config of uNRAID box, I do not plan on using these plug-ins. Instead I would like to point Newsbin's download directory to the mapped share (ex \\tower\Downloads\ ) Should this be a concern for any reason? Would there be a better way to go about this? The point of this project was to minimize my use on my energy-hungry desktop, and possibly even get rid of it in favor of energy efficient platforms. [An 11w max draw is considerably better than a 250watt idled desktop beast] I also may be using the Seed PC as a Network Video Recorder for Video Insight in the future, which would also use a UNC path as the storage directory Any information would be appreciated

Well I tried removing the 3rd party hotswap bay that was used on my parity drive and rerunning parity check but I still get thousands of those same read errors Trying a new power supply is going to be difficult as all the cables on the MicroServer N40L are neatly cable managed..and I have not been able to find a replacement on the cheap. Do you think this is critical? Will my unraid /data still be able to rebuild in loss of an actual drive? I've been able to copy terrabytes of information without an issue. 5 green drives running on the HP N40L seem to be a common thing users run.. I don't think that should be an issue on the 150w power supply I happened to purchase a second 3TB disk and I will begin preclearing that disk shortly.

Thanks for the tips Joe L , I will certainly be checking this out. Because I have the parity drive currently in a 3rd party hotswap bay, I'm going to remove it from that and connect it directly in hopes it could just be the hotswap bay hardware. If that fails to resolve the errors, I will continue the path to try and exchange the power supply. That is going to be a total pain if it resorts to that, and might be more cost effective to replace the entire MicroServer. Your comments are much appreciated.

Forgot to mention, This is the latest unRAID v5.0rc8 as I needed 3TB support. I am zipping the entire syslog file if that helps. I've also added the smartlog for the 3tb parity drive. syslog.zip smartlog.txt

Forgive me as I am new to the unRAID but not to servers/computers; I've added a newly purchased 3TB Western Digital Green drive to my array on an HP MicroServer N40L as my parity drive (Currently have 1x 3TB Parity, 2x 1TB Data). Before hand I did preclear the drive successfully with no errors. Added it as my parity and ran the Check (originally had the defaulted checkbox of fix parity errors) and it resulted in " Last checked on Mon Nov 10 00:51:43 2012 GMT, finding 0 errors. " I thought all was splending until I looked at the Error colum on my parity drive and it showed 12928. This made me feel uneasy. I read through the forums and looks like we recommend running another Check on parity; I did so but this time unchecking the fix parity errors box. This resulted in "Last checked on Mon Nov 12 00:51:43 2012 GMT, finding 0 errors." Fantastic I thought! But I again go take a glance at the Error column on parity to find the number 6781. Is this an area of concern? I want to make sure my parity is perfect before I go about adding more drives to my array ... Here is the system log I've been able to attach. Any thoughts, comments, ideas, would be extremely helpful. Lately all I've been saying to friends and colleagues is "UnRAID FTW" syslog.txt