jamesp469

Thanks for the nudge here; I have this set up as a static address but somehow one of my APs was given that address via DHCP

I just looked at my switch data, and it looks like for some reason it's reporting that both eth0 and IPMI are running off of the same switch port. Not sure if that's just poor reporting from Ubiquiti (Edgeswitch24 Lite), or if something changed somehow on my motherboard. It's a X11SSM-F with eth0, eth1, and IPIMI all cabled to the switch. Losing GUI access is from multiple computers on my network. I just tried using my attached keyboard/monitor and so far there doesn't appear to be a problem

Hello, after a recent power outage, my server has been experiencing issues. The logs show a graceful shutdown was completed, however after rebooting I lose GUI access after 1-2 minutes. Access will re-enable periodically, however there are extremely long periods where I am unable to access. This is also impacting all docker access, specifically noticed when using SABnzbd and Plex. I was running 6.11 previously, then downgraded back to 6.9 just in case that was a factor. If someone could take a look at my diagnostics and see what I'm missing here I would appreciate it. unraid-diagnostics-20240206-1451.zip

I'm having the same issue, running 6.11.5; GUI access disappears after a few minutes, comes back shortly after. Plex stops playback after 5 minutes, etc. Only change to my network was a safe shutoff (from UPS power) during a long term power outage.

Thanks, I thought I cleared out a decent chunk of space (~100GB) but maybe I'm wrong there. For the high metadata, could that be from Plex?

Hello, hope someone is able to help me figure this one out. I've been having the /var/log full error for a bit of time now; rebooting always kicks the can down the road for a month or two. But now that error is being coupled with some other ones, and I'm not sure where to start looking. Attached is my diagnostics, thanks in advance. unraid-diagnostics-20220302-0840.zip

Thanks, that's exactly what it was. I forgot I had removed a GPU to put this card in, and that GPU was being passed through to my VM. All set now!

I'm having issues adding a second HBA card to my build. I recently purchased a CSE-836 JBOD unit online, as well as a 9207-8e and two SFF-8088 to SFF-8088 cables to connect them. The JBOD (CSE-836E16-R92JBD) has a SAS2 backplane (BPN-SAS2-836EL1). My original build has an E3-1230v5 in a X11SSM-F with a 9201-8i (in CPU Slot7, x8). I've tried adding the 9207-8e to CPU Slot6 (x8 in a x16), and while both are showing as available in the BIOS I'm still running into issues adding it to Unraid. BIOS is 1.0b. When I initially added the internal card, I recall having issues getting it working as well, and believe the solution was getting into the VFIO-PCI config to bind it to the vfio-pci driver. (though this may have been for VM access). With PCIe ACS Override enabled, I'm seeing each card in a separate IOMMU group IOMMU group 11:[1000:0087] 01:00.0 Serial Attached SCSI controller: Broadcom / LSI SAS2308 PCI-Express Fusion-MPT SAS-2 (rev 05) IOMMU group 12:[1000:0072] 02:00.0 Serial Attached SCSI controller: Broadcom / LSI SAS2008 PCI-Express Fusion-MPT SAS-2 [Falcon] (rev 03) When I've attempted to Disable the ACS override, the system wouldn't see any of the drives connected to the original card. When I tried binding both to the vfio-pci driver, I didn't see any of the JBOD drives. Not entirely sure where to go from here, any help would be appreciated. Thanks in advance. unraid-diagnostics-20210111-1539.zip

You need to change "-----BEGIN PRIVATE KEY-----" to "-----BEGIN RSA PRIVATE KEY-----" in your key crt file to get this to work. No idea when the requirement changed, but this fixed the issue for me last night.

I have had this running for years just fine using the docker container. Wonderful tool.

Anyone else having this issue?

I'm having an issue with RSS feeds over VPN. The provider I am pulling the RSS feeds from requires that the same IP address used to set up the feed is the same IP address used to load the feed/download from. I am running this container on my server, and set everything up using my desktop using the VPN feed. The issue I am running into is that, when my desktop is not on VPN and I attempt to reload the feed through the container's GUI (container is on correct VPN IP), I get errors that the IP does not match the VPN ID. I've ran multiple checks with checkmyip.torrentprivacy.com, and the container's external IP is still showing as the correct VPN ID. However, if I log into my VPN service on the desktop and try to reload the feed, it works perfectly. This is only an issue with RSS; when I download torrents off the VPN-connected desktop, disconnect from VPN, and load them to the rTorrent container, they download as expected. I will leave the feed alone for a few weeks to see if it is able to automatically pull from the provider, but am a bit befuddled as to why this isn't working as (I) expected.

Thank you! This fixed it. Not sure why the default gateway assignment on eth1 was set like that, i don't recall setting that.

I'm seeing this issue as well, plus all of my installed plugins are listed as status "unknown". Diagnostics attached, thanks! unraid-diagnostics-20191211-0917.zip

I'm running into issues where Mylar regularly disables my search providers. After digging into the logs, it looks like it occurs after daily API limits are hit (WARNING DAILY API limit reached. Disabling provider usage until 12:01am) however the provider usage is not automatically re-enabled. I have always had to manually enable the provider. Is this something I should go to the Mylar team on, or something that can be managed at the docker level (force re-enabling search providers)

The repair service recommended cloning/moving the data off of the drive whenever possible. It was only a PCB replacement, so not sure if that was a liability-relief statement or not.

UPDATE: I was able to get one data drive repaired, and I expect it to be delivered back here tomorrow. Can someone point me to the correct process for turning my system back up? I have brand new drives to replace the blown 2nd parity drive and the other data drive that was not repaired, as well as a new drive to replace the repaired drive once my parity is rebuilt.

Thanks, I've sent one of the data drives in to get tested and see if it a PCB replacement would fix it. Hopefully it does, and then I can re-install that plus two drives to replace the parity2 and other data drive and hopefully be back in business.

So, in this situation, I have 5/8 drives in my array still spinning up and presumably with no data issues: dual cache, parity1, and 2of4 disks. Is there any scenario where I could rebuild partial data to a new drive using the parity drive, or should I just clear the drive and start fresh? Also, will i have any issues keeping the existing data on my cache pool and two working drives when i start a new array config? Thanks in advance.

Thanks for responding. The mistake was using a modular PSU cable from my old PSU/build in my new PSU/build, leaving me with five drives that won't spin up (two are net new to the system). So that won't be happening again. But if that's the case regarding repairing the parity drive, then yes it's probably safer to just bite the bullet on repairing the two data drives.

I won't bore anyone with the details, but after some compounding bonehead mistakes I'm currently stuck with some drives that will not spin up (neither in my server nor a USB enclosure). Three drives: two data drives and one of my two parity drives. Not sure if this make sense, but if I wanted to use a data recovery service on that parity drive would I then be able to replace the two dead data drives and not have any data loss?

Glad I misunderstood this, thanks. This should be a fairly painless migration then.

I'm running out of both drive space and drive slots on my current server, and am looking at migrating to a smaller server chassis connected to a DAS unit (Levono SA120). After doing significant research, this appears to be the optimum solution to expand my server in my existing wallmount cabinet (AR112, short depth). I'd be moving 2x parity drives, a 2x SSD cache pool, 3x drives directly connected to the motherboard, and 3x drives connected through an icydock 2x 5.25" to 3x 3.5" backplane cage (MB153SP-B) over to a server that would optimally hold just the parity drives and cache drives; everything else would be housed in the DAS. Any advice on how best to make this transfer without messing up my environment/losing data? I'm reusing the motherboard (X11SSM-F), and it's my understanding that I'd want each drive plugged back into the same SATA port on the MB after migration. This obviously wouldn't be possible if I'm moving the majority of the drives over to the DAS. Also, how much of an extra headache would it be to try to upgrade the parity drives during this migration? Thanks in advance for any guidance.

I'm having issues with my main indexer regularly being disabled in this container. It doesn't disable for a short time period, it disables the indexer permanently until i manually enable it. Anyone else having this issue? 2019-02-28 02:00:15WARNINGUnavailable indexer detected. Disabling for a short duration and will try again. 2019-02-28 02:00:15WARNINGUnable to retrieve search results from dognzb [Status Code returned: 503] 2019-02-27 19:22:19WARNING[ERROR] string index out of range 2019-02-27 18:08:40WARNING[ERROR] string index out of range 2019-02-27 17:37:07WARNING[ERROR] string index out of range 2019-02-27 17:37:07WARNING[ERROR] string index out of range 2019-02-27 17:31:52WARNING[ERROR] string index out of range 2019-02-27 17:16:38WARNING[ERROR] string index out of range 2019-02-27 07:09:26ERRORCould not locate exceptions.csv file. Make sure it is in datadir: /config/mylar