jbflix

Members
  • Posts

    26
  • Joined

  • Last visited

Converted

  • Gender
    Undisclosed

jbflix's Achievements

Noob

Noob (1/14)

1

Reputation

  1. 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.
  2. 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
  3. 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.
  4. 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.
  5. 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.
  6. 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
  7. 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
  8. 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.
  9. 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.
  10. 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
  11. 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
  12. 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
  13. 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.
  14. 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.
  15. 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.