-
-
/var/log is getting full (currently 51 % used) - v7.0.1
Received the following message "/var/log is getting full (currently 51 % used)" from my Fix Common Reports today. I have the diagnostics attached and would love an extra set of eyes to see what might be the problem. Greatly appreciate any guidance! fmc-diagnostics-20250930-1437.zip
-
Parity Device Is Disabled - First Time Drive Issue
During parity rebuild, the drive errors returned, so time for a new drive. Thank you for ALL for the guidance in getting me to this point. Thanks!!!
-
Parity Device Is Disabled - First Time Drive Issue
Would you mind stepping through that process? I have the array stopped right now and the drive shows in Parity but is disabled.
-
Parity Device Is Disabled - First Time Drive Issue
SMART displaying now for the drive. Here is the updated diags. Thanks all! bob-diagnostics-20240320-1100.zip
-
Parity Device Is Disabled - First Time Drive Issue
Thanks, checked connections on cables and all seemed good. Disconnected and reconnected and brought back online. Disk shows now (disabled). Below are the new diags. Thanks for your time! bob-diagnostics-20240320-1011.zip
-
Parity Device Is Disabled - First Time Drive Issue
Today at 10:45am I received a Parity disk error notification. "Parity disk in error state". I ran a Read-Check on the array and it just finished with 0 errors. This is my first experience with a drive issue so I wanted to reach out for assistance if someone can talk me through next steps please. Thanks, Chris diagnostics-20240319-2335.zip
-
Error: Flash Drive is corrupted or offline
Thanks for the quick response. Definitely in a USB 2.0 port. Shutdown and restarted back fine. Going through parity check now from an unclean shutdown. But back in business. Thanks JorgeB for quick response!
-
Error: Flash Drive is corrupted or offline
Banner error after updating GUI Search plugin this morning. Diagnostics are attached. I have flash backup from two days ago and key back up available as well. Requesting guidance please. Thanks! -Chris diagnostics-20221207-0930.zip
-
[Support] tmchow - n8n workflow automation
Prior to the latest release, I was able to use a manually created path to define access to my unraid system within the container. This latest version seems to now crash and is very unstable for me. Can someone try to add a path and check for stability? When I try to open the logs in the context menu it closes and same true for console. I've re-installed from previous and totally removed and started fresh with same results. If I remove the manually created path, then it seems fine, so definitely points to not accepting the path addition. I appreciate any t-shooting/guidance to help get this up and stable again. Thanks!
ccal12
Members
-
Joined
-
Last visited