• Content Count

  • Joined

  • Last visited

Community Reputation

18 Good

About AgentXXL

  • Rank

Recent Profile Visitors

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

  1. As @TexasUnraid said, the CLI tools have no issue. So for now I select the Krusader Docker container and open a console vs the web GUI. From the console it's easy enough to use 'unrar e myfile.rar' which has worked perfectly every time I've needed it. I'm curious though - as I'm still running unrar from the Krusader container, you would think that using the console and the CLI tools would have the same memory issue but they don't. At least there's a simple workaround and it's rarely needed anyhow. I'll also occasionally use Windows and the old standby QuickPAR to try and repair a r
  2. It's interesting to note that after finding the memory fault mentioned above, these messages are no longer showing up in the syslog. Hopefully that will remain the case and/or the author of the GPU Stats plugin is eventually able to correct it. Thanks!
  3. As an electronics tech who has worked in essentially an IT role for most of my career, I often tell friends/family/clients to do a RAM test if you start seeing crashes/lockups that started 'out of the blue'. I followed that advice myself after my panic posting here and in a FB group and sure enough, the issue appears to be a RAM failure. Memtest86 (v5.01 on the unRAID flash device) found errors almost immediately. Through process of elimination I've tracked it down to 1 of the 4 x 16GB sticks in my system. As my system doesn't support operation with 3 DIMMs, I've pulled one of the
  4. UPDATE: it just happened again a few moments ago. The 1st sign of it not responding was Plex not being able to find the server. I checked my firewall and again it was listed as offline. Tried a momentary press of the power button and waited 5 mins but no shutdown so I was again forced to hard reset. UPDATE 2: It crashed/locked up again within minutes of the last hard reset. I've now started the system in safe mode with no plugins loaded. If I can't retrieve the logs from the Flash drive before it crashes again, I'll try exploring the Flash drive on another computer. UPD
  5. [SOLVED] Cause was RAM failure. Removed faulty RAM and so far problem has not re-occurred. Last night I went to bed with the Plex client on my Nvidia Shield Pro playing music from my media server called AnimNAS (specs in signature). At some point the music stopped but as I was drifting in and out of sleep I just left it until this morning. Upon investigation, the server appeared to have crashed hard. The WebGUI was not accessible and my Plex and other Docker containers were offline. I also couldn't ping the IP and the system was shown as 'offline' in the pfSense firewall (running o
  6. [SOLVED] I waited until the preclears were finished before restarting. Both preclears were successful and after the reboot have been added to the array. As expected after a reboot, my /var/log folder is now only using 1% of available space. Still wish I could figure out why the log was considered full even though I had plenty of available RAM. Start of Original Message: I started a zero-only pass of preclear on two new 16TB drives yesterday evening. When I woke this morning I had a message from Fix Common Problems about an error with my setup. That error is a full /var/
  7. Just to help anyone else looking to do a Fractal Design Define 7XL build, here's the build info I used to fully equip it for maximum storage: Solid black model with 6 HDD/SSD trays + 2 SSD brackets + 2 Multibrackets included 5 x 2-pack HDD trays (10 additional trays) 2 x 2-pack multibrackets (4 additional multibrackets)
  8. Yes, both methods work to prevent the DNS rebinding issue. I did add the custom option lines to that section on my pfSense box, but it didn't resolve the DNS rebinding issue. Even after waiting an hour for things to clean up. Only when I added it to the section I mentioned did the provisioning work. What's unusual is that one of my unRAID systems is being seen as available (green in My Servers) whereas the other one is still red. Yet the port forward rules are identical other than the port number. I haven't had the time to play with it anymore yet, but will soon. I'll t
  9. I installed the plugin on both of my servers. When I went to Management Access under settings, my initial attempt to provision the Let's Encrypt certificates failed, indicating that it was likely my firewall's DNS rebinding protection. To resolve the DNS rebinding issue I went into my firewall config (pfSense) and under DNS Resolver I added the domain to the 'Domain Overrides' section. One thing I'm not sure about is where pfSense asks me to provide the DNS 'Lookup Server IP Address' so I just set it to a Cloudflare one for now, as shown on the attached pic. Cloudflare r
  10. So still no luck... the 'Check' function fails on both of my servers. Tried the 'unraid-api restart' on both, rebooted, still no go. One of the servers shows up as available for remote access when I go to the url using my cell network, but it won't actually connect. After a reboot both servers show up in the My Servers section, one with a checkmark and the other with a red X. The one with the checkmark is the one that shows remote access as available, but won't connect. I'll potentially try the full reset method mentioned but I'll need to let my users finish their Plex sessions.
  11. That's why you use a complex password and hopefully eventual 2FA.
  12. OK, have added the plugin to both of my servers, configured my firewall to port forward a custom port to each server and added the '' domain to my DNS resolver. I was able to provision with Let's Encrypt and the flash drive backup activation appears successful. Alas even after trying the 'unraid-api restart' in a terminal on each server, I'm still unable to get remote access working. When I try the 'Check' function it fails. When attempting it from a phone using my cellular providers networks (WiFi turned off), I get a 'You do not have permissions to view this page' error for the htt
  13. It only needs the bootable partition if your VM is setup to use it for booting. If it's just for data, that 200mb partition is not required.
  14. The disk was likely GPT formatted with the vfat 200mb partition left on it. This partition is normally only needed for bootable media, i.e. it's commonly used for the EFI partition on UEFI bootable devices. You can unmount the drive and then you can click on the red 'X' beside the vfat partition to remove it. To be entirely safe, you may want to backup your drive again, remove both partitions, re-format and then re-copy your required data. Note that when you reformat, if the disk is going to be for data storage only, you can change it from GPT to MBR so you'll only have 1 partition. You'll lik
  15. Just a quick update - the 3rd 'false' parity check completed with 0 errors found, as I expected. I've increased the timeout to 120 seconds as @JorgeB suggested. I've also just successfully upgraded to 6.9.1 and hope that these 'false' unclean shutdowns won't re-occur. Also, just to confirm - 6.9.1 shows the correct colors for disk utilization thresholds on both the Dashboard and Main tabs. My OCD thanks you @limetech for correcting this. 🖖