Everything posted by ipreferpie
-
Help diagnosing key failure point
Just after several troubleshooting procedures back and forth in trying cables, PDU, repasting, adding fans and HBA, I discovered the issue. It’s the firmware on my LSI 9405-24i. After updating from 16.00.01 to 16.00.12 everything works now. Before, it was the ZFS and BTRFS SSD trim commands that caused the drops. Thank you for all the forum help in helping me narrow it down! Pls mark as solved.
-
Help diagnosing key failure point
Here’s the updated most recent diagnostics. I’ve turned on syslog to flash. What happened this time was slightly different in that there were no temperature blanks, dropped/failed array disks; instead, just a full crash and system reboot. But I’m still very certain it has something to do with the HBA, cables, or power. Many thanks! hk-homelab-diagnostics-20250220-0854.zip
-
Help diagnosing key failure point
Ok I’ll try to replicate the problem and have enabled syslog to flash. Will post new diagnostics once I start getting problems again. Many thanks
-
Help diagnosing key failure point
Right now, I had rebooted and rebuilt the failed disks, so none show failed disks. But around 2 failures ago, I remember was Disk 5 & 11. I’ve have run through around 6-7 disk failure/rebuild scenarios over the past 2 weeks. The most recent one was strange is that unRAID just hanged w/o disk failures and I’m just doing a parity check now.
-
Help diagnosing key failure point
Hi there, I’m using unRAID 7 currently and have been using my system for nearly 9 years. Recently, I’ve been having disk errors that are repeating and need some help to fine tune how I should diagnose the cause of this. Typically, the problem starts like this: 1) Array HDD disk temperatures start turning to “*” 2) These disks eventually start looking like they’re spun down with the grey circle icon, but can’t be spun up 3) Eventually, unRAID will see errors coming out and will mark them as failed disks 4) If I keep letting unRAID run, the system will lock up and I need to force a system restart Usually this happens over a period of 12-24hr to my array of 17 disks, and ONLY if my Docker *arr stack is running on my SSD cache pool. About 1-2 disks would have errors/failure, but the pattern is random within the set of 17 disks after I restart the array. As a background, the HDD array disks are connected to a Supermicro SAS backplane, which is connected to a LSI 9305-24i HBA PCIe card. I’ve been running this hardware configuration with same cables stably over the past 5+ years. In addition, I connect around 3 SATA SSDs to the LSI SATA card for my ZFS mirror SSD cache pool. What I did to figure out the problem were these steps: 1) Ran Memtest86+ successfully and changed to new PSUs 2) Reattached my 3 SATA SSDs to a separate LSI2008 8i card with different cables. Once that was done, the system runs stably. It looks like it’s either a problem with the SATA connectors or the LSI 9405-24i. The LSI runs well when only the backplane and HDD are attached, and if the SSDs are attached onto another separate HBA. 3) So basically, I can solve this problem by separating the cache SSDs onto a different HBA; or, if I don’t run my Docker *arr stack. At this point, I’m trying to see based on the diagnostics, is it likely a HBA card, SATA cables or power connector failure? Can anyone point me on the next steps to figure out which is the exact cause of my problems? Many thanks! hk-homelab-diagnostics-20250218-1533.zip
-
Mixed ZFS vdev types in same zpool problem
Well noted and thanks for clarifying on this.
-
Mixed ZFS vdev types in same zpool problem
Hi there, I’ve been trying to import several zpools from TrueNAS mostly successfully. Namely, I can import both my zpools with multiple mirror vdevs (mirror-0 + mirror-1) without any problems. But when I try to import a mixed vdev pool (mirror-0 + raidz1-1), it shows that the drives are unmountable during import. Is there a way for unRAID to allow/override this limitation? Many thanks!
-
unRAID hangs 1-2 days after upgrading from 6.9.3 to 6.12.4
Thank you for the tip on that. I’ll give that a try and report back soon. Another thing I notice is that when I do a Macrium backup from my laptop to my unRAID server, the GUI hangs until the backup is finished. I checked my CPU and mem load it never goes above 60%. I wonder if it can be I/O or network issue? But then, the max transfer rate is only around 90MB/s on a 10GBps network & SSD cache.
-
unRAID hangs 1-2 days after upgrading from 6.9.3 to 6.12.4
Hi, my apologies for the delay. It took some time for me to address the issue. My SD card died, so I found a replacement. After which, I also fixed up having the docker system in folder format in a ZFS drive and changed it to a docker BTRFS image. Unfortunately, the system still hangs after ~48 hours. I've attached my diagnostics and log for review. Many thanks for your help! hk-homelab-diagnostics-20231002-1040.zip syslog-127.0.0.1.log
-
unRAID hangs 1-2 days after upgrading from 6.9.3 to 6.12.4
I recently updated my server to 6.12.4, but it seems to hang after 1-2 days of normal operation. I've rebooted it to safe mode while running a parity check in maintenance mode, which was stable for 3 days. It seems like it may be a plug-in issue but can't find the root. I've attached diagnostics for referral. Many thanks in advance! hk-homelab-diagnostics-20230915-1548.zip
-
The Complete UnRAID reverse proxy, Duck DNS (dynamic dns) and letsencrypt guide
@Fma965, thanks so much! forgot that one little thing and now it works well
-
The Complete UnRAID reverse proxy, Duck DNS (dynamic dns) and letsencrypt guide
I set up DuckDNS but am having troubles with Letsencrypt. In my logs, it just keeps repeating -- In my site-confs/default file, this is what I have for sonarr: Did I do something wrong? Any help would be great! Thanks so much!