jbflix

Thanks, I will look into the setting changes tomorrow. I have recently started using Tdarr and I see that is referenced in the link you provided.

I recently upgraded my Unraid server from an HP DL380e to a Dell R730XD. The migration has gone really smoothly however, I have been experiencing random outages where the Unraid shares become unavailable. Restarting the server is the only solution I have found that works so far, so reaching out to the community to look at my logs to see if anything odd is happening. The only additional hardware, other than the chassis swap, was the addition of the 1Tb NVMe drive which is currently not being used. Diagnostics attached. tower-diagnostics-20211105-1814.zip

Checked my server this morning (6.9.2) and it appeared to be running slow, unable to load Sonarr etc. Stopped all services, rebooted, restarted services. Everything was good, for about 10 minutes. Stopped everything again, rebooted, but this time deleted the docker.img file before restarting services then started recreating the docker containers. Again, everything was OK for a while and I got most of them reinstalled, but then the server stared running really slowly again. Currently unable to do another restart as the second reboot this morning has triggered a parity check. Diags attached if anyone has time to look for any errors.

I've seen this come up a few times in the forums now, but only just started on my machine. No noticeable issues in general use. Diogs attached.

Thanks for the prompt reply as always johnnie.black. I didn't want to proceed any further in case I made matters worse! I'll move the disk into the old server and see what I can find from SMART.

Ok, the story so far: Bought a new server (HP DL380 G8) and moved USB and disks to new chassis. Everything working fine. Added a new larger 6Tb disk as 2nd parity with plan to replace parity 1 (3Tb) with another 6Tb disk once check complete. During the check, Disk 2 (3Tb) has 2 read errors and dropped out of the array. I have other 6Tb disks spare and was going to replace the smaller 2Tb disks once parity was sorted, some of these have been pre-cleared, some not. Now, I cannot add a 6Tb disk to the array as parity 1 is only 3Tb and I didn't want to proceed any further without seeking advice. What are my next best options to get the disk back online and preserve parity? tower-diagnostics-20190301-1827.zip

I think that is a Windows 10 problem as SMB 1.0/CIFS File Sharing support is now disabled by default in W10 v1709 and later. Follow the instructions in the link below to re-enable. http://wdc.custhelp.com/app/answers/detail/a_id/20736/~/how-to-enable-smb-1.0%2Fcifs-file-sharing-support-on-windows-10

I've managed to get it up and running by creating a new W10 VM then renamed the folder within domains to match the new template. I'd still be interested to know if anyone can discover why it wouldn't start originally. I assume its something to do with the USB drive not being available at its old location to find the config folder.

I've just moved my Unraid setup from an old Dell Workstation to a newer HP Gen8 server. All drives, shares, dockers etc. are up and running fine, but I am unable to start my W10 VM. I have copied the .img and libvirt to the relevant locations and all path are the same as the previous set up. I assume that this is due to the hardware change, but I can't find anything that looks out of place. Execution error Device 0000:00:1b.0 not found: could not access /sys/bus/pci/devices/0000:00:1b.0/config: No such file or directory Diagnostic file attached.

Arggggg I've put --link jackett:jackett back it at the end of the extra parameters and it now works fine! Please mark this as solved. Thanks for your help Squid

jackett is always running and the failure only happens when using the start option from the main docker page. As explained, when I go in to the container settings, it does not fail. I have removed --link jackett:jackett from the extra parameters, and it now starts fine using the Start option on the main page. So the issue is definitely the link to jackett

I have a strange problem with my binhex-sonarr docker. If the app is stopped, I cannot start from the main docker page and get an execution error message. However, if I go in to the container settings and change a setting, then change it back (e.g change name to binhex-sonar then change it back to binhex-sonarr) simply to enable the Apply button, the docker will start normally. This issue also means I cannot auto update the docker. Diagnostics attached. tower-diagnostics-20181116-1024.zip

Download the magnet link from http://checkmytorrentip.upcoil.com and leave it running in your client. On the status tab for the torrent, the tracker status will show you the IP address Deluge is using.

Thanks Johnnie. I'm sure this happened before, but I was reluctant to reboot it again. I will reboot now and restart parity and look at BIOS and slots tomorrow when I have more time.

I currently run 8 x 2Tb disks in my array along with 1 x 2Tb parity disk and 2 x 500Gb Cache pool. I'm planning on upgrading the parity disk so I can begin to replace the data disks with larger drives. Step 1, check parity is not going well! My last check returned a speed of 72.1MB/s and jut under 8 hours. The current check has been running for 13 hours and is only at 5% and a speed of 3.8MB/s. At this rate, the check will take around 6 days so something is clearly not right. All Dockers have been stopped, but I'm not seeing any improvement. Can someone check my diagnostics to see if there is anything awry? Thanks.

Download the egg from http://dev.deluge-torrent.org/wiki/Plugins/YaRSS2#Download to your local machine. On you webgui, Preferences, Plugins, Install, then find the egg you downloaded. I have the YaRSS2 plugin installed and working on mine, but please be aware that you cannot actually configure it from the webgui. I migrated my setup from a Windows box and took ages to work this out. In order to configure the settings on YaRSS2, you will needed to install Deluge on a Windows machine, then remotely connect it to the docker deluge host. All the downloading is still done via the docker deluge host. I still use the webgui day to day and only use the full client to change YaRSS2 settings.

Fix Common Problems warning - Docker Application binhex-sonarr is currently set up to run in host mode I currently have this running in host mode, as running in bridge mode it is not able to access download client binhex-delugevpn using port 8112. Is there a setting I should be changing in either docker to allow them both to communicate running in their native mode? Many thanks and keep up the good work!

Faulty cache drive successfully replaced following the guide. Many thanks for you help btrfs still shows the same 2 profiles as before. Should I do anything else to fix?

Finally found time to get back to this. My current cache drive is a pair of 500Gb HGST drives (sdl and sdm) and one of the drives has pending sectors (48). Following the guide, I have backed up the current cache and now have a pre cleared 500Gb replacement disk in the machine, ready to replace the failing disk. I have issued the btrfs filesystem df /mnt/cache command and it looks like there is more than one data profile, so I am now looking for further help: root@Tower:~# btrfs filesystem df /mnt/cache Data, RAID1: total=136.00GiB, used=116.56GiB Data, single: total=1.00GiB, used=0.00B System, RAID1: total=32.00MiB, used=48.00KiB Metadata, RAID1: total=3.00GiB, used=682.70MiB GlobalReserve, single: total=240.00MiB, used=0.00B Thanks. tower-smart-20170203-1438.zip

Hangs head in shame. No, I'll do it when I get home and report back. Thanks for your advice.

I'm happy to remove the faulty drive from the pool and preclear, but I don't want to proceed any further without ensuring that the data on the drive pool is still usable. Should the good drive mount correctly when btfrs formatted as a single drive? I have already tried stopping the array and allocating only the good cache drive, but it fails to mount. Thanks.

I've started to receive errors that one of my cache drives (btrfs cache pool) has pending sectors. What is the best course of action to take? Can the cache pool be reduced to the single drive that does not have any errors? SMART report and diagnostics attached. Many thanks. tower-smart-20161223-1112.zip

Thanks. Now rebooted and restarted the sync. Now running at 40MB/sec. Much better. Many thanks for your prompt assistance.

Thanks for the advice. Will the rebuild start again from 0 or will it pick up where it left off after a reboot?

Fairly new to UnRAID, but loving the features especially the integraed Docker. My disk 2 failed at the weekend, so I swapped it out with a pre cleared spare, but the data rebuild is running really slowly. Currently running for 1 day and 15 hours at 5.3MB/sec and estimating 2 days and 22 hours to complete the 2Tb rebuild. I am loathe to stop the process, but concerned that there is an underlying issue with the replacement disk that could be the problem. Syslog attached.