exdox77

I am at a loss here. I created a share in Unraid. I can access the share with the username and password given from my computer with no issues. I typed the same IP address, username, and password in Protect and I keep getting Failed to connect to server. Has anyone been successful connect Protect to Unraid for backup? I see a bunch of stuff around Synology but not much around Unraid. To add, the username and password have no special characters or uppercase, everything is lowercase.

I just had the same issue. Updated the plugins and boom, upgrade working. Weird issue.

nevermind, during this whole process the usb drive got corrupt!!! replaced and now doing the sync again.

@JorgeB quick question. i started the array back up the other day and it started the parity sync just fine. everything was working up until yesterday when everything went offline and i wasnt even able to SSH into the server or access the webui. the array seem to be offline as well, but I see disk activity. I will pull the diagnostics in a bit and upload them. But wanted to get this out here to see if you knew something off the top.

alright, i kind of figured that was the case. now we wait for it to rebuild, sigh.... thank you.

ah. makes sense. what would be the recommended solution? replace the parity drive first with one of the newer ones and then replace the drives?

hive-diagnostics-20240530-1242.zip Are you suggesting to remove any existing partitions from the new drives? I did clear the drives from unassigned devices. Attached is the diagnostics file.

I am trying to replace two drives in the array. sdm is the parity drive. sdi and sdj are the new drives replacing two others that i have already taken out. when i go to array operation i get a message stating disk in parity slow is not biggest. but the disk is exact same disk as the two new ones. they were spares. i have already cleared the drives. do i need to format the drive before adding it to the array?

OMG you are a godsend!!! I was panicking for a minute!!!!!

I accidentally selected the wrong preserve settings and lost my array config. I did not back up manually since I am connected to Unraid Connect. Is there a way to go back in Connect to get a config from a previous day? Is there a way to restore the previous settings for the array? I have an image of the array prior to this happening, but it says all data will be lost if the array is started.

Thank you everyone for your support. I purchased new memory yesterday, went with Corsair with the same advertised specs. Ensure the MB was configured correctly and did one last memtest last night. Everything passed with flying colors and Unraid seems to be running great.

No OC on this board. It runs stock config. Memory test failed out because of too many errors.

No OC settings have ever been enabled. The system has been running for years without issues with no changes to the BIOS. The memtest failed out because of too many errors. Running memtest on the new memory now.

@trurl initial results do not look good. Looks like I will be ordering some memory.

I have not. If the USB drive is failing, could this cause these issues?

Yesterday I spent most of the recovering from my cache drive filesystem becoming read only. I recovered and created a new pool with another brand new drive. Moved everything over and everything was working fine. This morning I woke up to the filesystem in the brand drive read only. I am at a loss to why this keeps happening, this is the third time this past couple of months this has happened. I have attached the diagnostics. I do want to mentioned that if I reboot Unraid and restart the array, things work fine for awhile. hive-diagnostics-20221202-0713.zip

I figured it out, it was a config in one of the plugins that I needed to tell it to use the GPU. Working pretty well now.

Everything seems to look correct from configuration, unless I am missing something. Extra Parameters = --runtime=nvidia Variable NVIDIA_VISIBLE_DEVICES = GPU UUID Variable NVIDIA_DRIVER_CAPABILITIES = all Also note that Tdar is currently transcoding with the GPU selected and there is no GPU activity using nvidia-smi.

I have noticed recently that GPU transcoding isn't work in Plex. I also tried GPU transcoding in Tdarr and Tdarr was using a lot of CPU. I have been using GPU on Plex for months now with no issues. I am on Unraid 6.9.2 with Nvidia driver 460.80. I am not sure when GPU transcoding stopped working. I tried removed the variables from the template and adding them. I tried rebooting Unraid and downloading new versions. I cannot seem to get Plex or any container to use GPU.

Crises diverted with proxy server and some SSL certs. Thank you for the feedback.

Just started moving everything other to unraid docker and unifi controller is on the list. The installation was pretty simple, but when I navigate to the WebUI I get an SSL error and chrome won't let me move forward. Running the latest release, since my old controller is on 5.12.xx.