Boyturtle

Members
  • Posts

    110
  • Joined

  • Last visited

Everything posted by Boyturtle

  1. I've taken your advice and changed the font. I've also done as you've asked and pm'd you the debug output
  2. I can't see Settings>Credits. Here's a screenshot of my Settings menu Sent from my ONEPLUS A6013 using Tapatalk
  3. Thanks, I tried that first, before I posted here. I am able to access the unraid UI from my phone. I can access the plugin UI by either typing in x.x.x.x:2379 or xx.unraid.net:2379; both which go to the Controlr web portal on https. If I type in the same addresses with 2378, (the default port number on plugin config page), it resolves to the https pages, so I guess https it is being forced. I have no ad-blocker on my phone, but I do use Pihole as DNS which is supposed to block ads across the network.
  4. I'm on the same LAN and not on a guest network. I am able to ping the server from my phone Sent from my ONEPLUS A6013 using Tapatalk
  5. I've had your app for several months now and I haven't been able to get it to work as I keep getting the "No servers available" notification when adding server details. I've been too busy to deal with this until now, but I would dearly like to get it fixed and working, so your help would be greatly appreciated. The automatic search just passes my server IP, and the manual does not find it either I have tried port 2378 which is listed in the plugin. I have tried port 80 which is accessible from my LAN (although it resolves to xxx.unraid.net). I have tried with both the Secure switched on and off on all combinations above. I have upped the timeout to 10000 I an running 6.7 and 4.10.0
  6. The 2 main uses of my Unraid box (apart from file storage) are Plex and a Win 10 VM running Blue Iris, both video intensive items that can hammer my CPU (Xeon E3-1230v5) when in high demand. I have been considering upgrading the CPU to Xeon E3-1245v5 to get the added benefit of Quick Sync Video, to take some of the load off the CPU by letting it do hardware encoding, but it turns out that my motherboard (Supermicro X11SSM-F-O) does not support this feature, so this idea is DOA. Could someone tell me if adding a separate graphic card would work in this circumstance, or will it also be precluded as the motherboard doesn't support Quick Sync Video, and would I just be better off getting another motherboard to make this work?
  7. I'm still not sure what is causing this problem, so I've decided to pass through a hardware NIC to the VM. This has been up for a day now without issue, only time will tell if this works.
  8. I'm not sure if this is a Blue Iris, a Win 10 or Unraid issue, or some combination of the 3, but the same problem occurred on a previous install on another dedicated Win 10 VM, also running BI which I couldn't get to the bottom of then and now the same problem has returned to the new install too. Furthermore, I run other Win 10 VMs on the same server with no issues. This VM is fully patched, runs only BI, antivirus and backup software. The VM uses the e1000-82545em driver, the same used on my other machines. The VM has access to 8 logical CPUs and 6 GB RAM. Loss of connectivity seems random and not necessarily tied to to any excessive throughput from my CCTV cameras. It can happen at any time. When I lose connectivity, the only thing I can do to get it back is to either restart the VM or reset the ethernet adapter, which is the fix that the Windows trouble shooter does when run. I've got access to the Network Diagnostic Log, but not sure what to look for to find a more permanent fix. Any suggestions greatly received.
  9. My understanding is that it will not work, which is why I'm looking at alternative ways of doing this. Will the process I outlined above work? My main concern is that unraid will not be able to find the user share if I've moved them to another disk.
  10. I have a 5tb WD Red drive on the array that is failing and needs to be returned to the manufacturer for a replacement under warranty. It contains a total of 2.5tb of data, which is too big to move to the other 5tb Red that already contains 2.6tb of data. So while waiting for the disk to come back from WD, I need to get another disk to copy the data across to. Because WD Red 5tb are end of life now and no longer carry the full 3 year warranty that I need, I will most likely be getting a 4tb Red, so I won't be able to just replace the disk into the array for the faulty device and rebuild it from parity. Consequently, I'm going to have to copy the data across to the new disk and I just want to make sure that I go about doing this in the most efficient and data resilient way, so that I don't break my server or lose my data. My parity drive is 6tb btw. My plan is as follows: Preclear 4tb disk and then add it to the array (it will now become disk3) I need to find a way to stop data being written to the faulty drive while I am copying stuff off of it, would excluding all the user shares from writing to disk2 be sufficient or would I need to do something else? Use krusader to copy the content of the disk share from the faulty drive to the new drive (from /unraid/disk2 to /unraid/disk3) Alternatively, use the copy command in terminal (cp -vRap /mnt/disk2 /mnt/disk3)- I feel this to be more robust. Delete the contents of disk2 Delete the faulty drive from the array Power down server and remove faulty drive. When the replacement drive arrives from WD, preclear it and add it to the array as an altogether new disk. Would the above work? In moving the contents of the disk shares from disk2 to disk3, will unraid still map and link to the shared folders and keep adding to them as if they were on disk2, or is there some other change I need to make?
  11. Thanks for your input. I'll get the disk RMA'd back to WD, my 3 year warranty is out at the beginning of December!
  12. Every now and again, I get an error warning about reading to a hard drive. The System Log show the following error or something similar Oct 24 11:06:32 Speedy kernel: res 51/40:88:a8:65:56/00:00:51:00:00/e0 Emask 0x9 (media error) Oct 24 11:06:32 Speedy kernel: ata7.00: status: { DRDY ERR } Oct 24 11:06:32 Speedy kernel: ata7.00: error: { UNC } Oct 24 11:06:32 Speedy kernel: ata7.00: configured for UDMA/133 Oct 24 11:06:32 Speedy kernel: sd 10:0:0:0: [sdi] tag#1 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 Oct 24 11:06:32 Speedy kernel: sd 10:0:0:0: [sdi] tag#1 Sense Key : 0x3 [current] Oct 24 11:06:32 Speedy kernel: sd 10:0:0:0: [sdi] tag#1 ASC=0x11 ASCQ=0x4 Oct 24 11:06:32 Speedy kernel: sd 10:0:0:0: [sdi] tag#1 CDB: opcode=0x88 88 00 00 00 00 00 51 56 65 a8 00 00 00 88 00 00 Oct 24 11:06:32 Speedy kernel: print_req_error: I/O error, dev sdi, sector 1364616616 Oct 24 11:06:32 Speedy kernel: md: disk2 read error, sector=1364616552 Oct 24 11:06:32 Speedy kernel: ata7: EH complete Oct 24 11:06:32 Speedy kernel: md: disk2 read error, sector=1364616560 Oct 24 11:06:32 Speedy kernel: md: disk2 read error, sector=1364616568 Oct 24 11:06:32 Speedy kernel: md: disk2 read error, sector=1364616576 Oct 24 11:06:32 Speedy kernel: md: disk2 read error, sector=1364616584 Oct 24 11:06:32 Speedy kernel: md: disk2 read error, sector=1364616592 Oct 24 11:06:32 Speedy kernel: md: disk2 read error, sector=1364616600 Oct 24 11:06:32 Speedy kernel: md: disk2 read error, sector=1364616608 Oct 24 11:06:32 Speedy kernel: md: disk2 read error, sector=1364616616 Oct 24 11:06:32 Speedy kernel: md: disk2 read error, sector=1364616624 Oct 24 11:06:32 Speedy kernel: md: disk2 read error, sector=1364616632 Oct 24 11:06:32 Speedy kernel: md: disk2 read error, sector=1364616640 Oct 24 11:06:32 Speedy kernel: md: disk2 read error, sector=1364616648 Oct 24 11:06:32 Speedy kernel: md: disk2 read error, sector=1364616656 Oct 24 11:06:32 Speedy kernel: md: disk2 read error, sector=1364616664 Oct 24 11:06:32 Speedy kernel: md: disk2 read error, sector=1364616672 Oct 24 11:06:32 Speedy kernel: md: disk2 read error, sector=1364616680 This has been ongoing for a few weeks now; it happens once and then doesn't do it again for a number of days, even weeks. I've run the extended SMART test a few times and the history on the disk history page on unraid shows no errors. I've attached below the downloaded report which gives more details; unfortunately, I don't know how to read it and I've been struggling with brain fog a lot recently and trying to work it out is proving difficult, could someone with knowledge of this cast an eye over it to see if in fact there is a disk error or not, as I suspect that the problem lies with either the sata port or the sata cable connecting the drive. I hope that it's the latter as that will be easiest to correct. TIA SmartTest-WDC_WD50EFRX-68MYMN1_WD-WX31D55A4NV4-20181026-2052.txt
  13. Great. So, correct me if I've got the wrong end of the stick, with regard to my issue a couple of nights ago. I typed in https://ip/, the server (by default) redirected to https://name/ and because my router and DNS service were virtualised and not started at this point (because they are living on unraid), my query just went nowhere? So, if this is the case and it happens again, do I fire up my (as yet unconfigured, brand new) bare metal router and will this bypass the problem, or is there something else I should address?
  14. Hmm Hmm. I'm confused. In this instance, the redirect will happen at server end of 192.168.52.170, is that right? If so, how did the redirect happen because the array was down and non of the services would have been running? Does this mean that some services would still be running without the array being up (so, effectively baked into the boot usb and consequent RAM when loaded), or is it that the redirect is cached on the client machines?
  15. Local ip addresses http://192.168.52.170 and https ://192.168.52.170 resolve to FQDN https://$$tring.unraid.net . Resolve in this instance may not be the correct term, but I'm not sure what else to call it
  16. I've tried both iterations and they both resolve to the same address. Very odd. I could not access the web interface from any of the household computers, laptops, ipads or Apple phones, but was able to do so from my android phone as it didn't resolve to the errant .unraid.net address, keeping it local instead for some reason. I have been able to start the array again and start all the VMs and dockers from within my humble android phone. Initially, once started I still couldn't access the server management pages from any device other than my phone; but I was able to access pages with different ports and IP addresses that are served by unraid (Crashplan, Pihole, Plex) and was able to remote into the VMs to, using teamviewer. Fiddling about with the DNS settings seemed to allow me to view pages now. So I don't know if the issue is somehow DNS or even DHCP related? For now, the problem is resolved, albeit in a roundabout and Heath Robinson fashion. I suspect that the problem will return if I stop the array again (so I've added the array autostart as a precaution). I'd like to avoid this in future, can anyone give me any pointers to what I should look at to resolve this?
  17. I turned off my unraid array this afternoon as Pihole wasn’t working properly and I had considered that it may have been conflicting with Privoxy somewhere down the line and just switching off both dockers didn’t seem to fix it. When I switched off the array, I lost connectivity to the server and I have since been unable to connect via the browser. When I put in the local ip address of the browser, it resolves to https://$$tring.unraid.net but then can’t resolve any further, leaving me effectively locked out. I am able to SSH into the server and have changed the ip address from *.*.*.170 to *.*.*.180, restarted the server and tried to access it via the browser again, hoping this time that it won’t resolve to the $$tring.unraid.net address, unfortunately, this did not work and it resolved to the same *.unraid.net. I suspect the problem is probably caused by issues I had while trying to do Spaceinvader One's unRAID 6.4 Overview, How to upgrade, SSL, HTTPS and Disk Encryption video. Fortunately for me at this stage that I didn’t encrypt the drives! I tried to force the resolution by adding the $$tring.unraid.net address to the /etc/hosts file, but that didn’t work either as it removed my changes after reboot. I’m not sure if this is relevant, but, although I can ssh using root privileges, I am unable to get past the login screen when I plug a keyboard and monior into the server directly. I’m a bit at my wits end at the minute and Mr Google has not been very helpful. Should I delete any of the certs in the /boot/config/ssl/certs folder? I’d appreciate any input.
  18. Thanks for the pointer. What I actually needed was to update the DNS with my new IP and had no idea how to do it. Your advice took me to the link I needed and hopefully all should be well now :-)
  19. I am trying to install ssl certificates following Spaceinvager One's unRAID 6.4 Overview, How to upgrade, SSL, HTTPS and Disk Encryption video, but when I get to provision, I get the warning Sorry, an error (403) occurred provisioning your SSL certificate. The error is: Your router or DNS server has DNS rebinding protection enabled, preventing 34796ec30bbdae301e28de01969309cc73848787.unraid.net 192.168.52.170 resolution. See Help for more details and workarounds. I am using PFSense for routing and Pihole for DNS (both virtualised on the unRAID server). Most fixes (including Spaceinvader One's) point to the addition of the line server: private-domain: "unraid.net" in Services/DNS Resolver/General Settings/Custom options. This does not fix the issue for me. Turning off DNS Rebind check in System/Advanced/Admin Access does not fix the issue either. I am unable to ping 34796ec30bbdae301e28de01969309cc73848787.unraid.net (above), as it's resolving to IP 192.168.52.130 and not 192.168.52.170 (the original IP I set the device up with, but changed within a day, long before either Pihole and PFSense were installed), so it seems that some local DNS resolution is fubar . I can't think why this old address persists and I suspect that it may be causing my problems. The server, dockers and VMs have all been started several times since the address change. I'm not sure if this is a PFSense, Pihole or unRAID issue, can anyone give me a pointer on how I may clear this address problem or try to fix this issue a different way
  20. I'd love to see this too. Any idea when you'll be doing the tutorial?
  21. Ownership was set to root:root. I changed it recursively to nobody:users, changed the destination in Device Preferences>Destinations and it is now block syncing. Hooray!! Although it seems to be working correctly now, can you please confirm that these permissions settings are correct? Thanks for the heads up and guidance btw, it's really appreciated :-)