Jump to content

Duggie264

Members
  • Posts

    42
  • Joined

  • Last visited

Everything posted by Duggie264

  1. Ahh cool, I'll keep waiting for e release that works then, cheers John ie!
  2. Is that an unraid kernel issue, or a controller kernel issue?
  3. Thanks, I just find it strange that I have had no issues under 6.6.7 and below? Now I have reverted, it is all working fine, as it was before the upgrade.
  4. was working fine on latest stable (6.6.7) closed down all of my VMs and containers. ensured mover had finished. backed up flash stopped array and then updated to next 6.7.0-rc6. b Better than previous attempts to upgrade, as far as on reboot all drives were detected in correct slots, however on starting array errors everywhere. log is full of errors: Mar 30 23:26:05 TheNewdaleBeast emhttpd: error: get_filesystem_status, 6474: Input/output error (5): scandir Mar 30 23:26:05 TheNewdaleBeast kernel: XFS (md2): metadata I/O error in "xfs_trans_read_buf_map" at daddr 0x15d508f48 len 32 error 5 Mar 30 23:26:05 TheNewdaleBeast kernel: XFS (md2): xfs_imap_to_bp: xfs_trans_read_buf() returned error -5. Mar 30 23:26:06 TheNewdaleBeast emhttpd: error: get_filesystem_status, 6474: Input/output error (5): scandir Mar 30 23:26:06 TheNewdaleBeast kernel: XFS (md2): metadata I/O error in "xfs_trans_read_buf_map" at daddr 0x15d508f48 len 32 error 5 Mar 30 23:26:06 TheNewdaleBeast kernel: XFS (md2): xfs_imap_to_bp: xfs_trans_read_buf() returned error -5. Mar 30 23:26:07 TheNewdaleBeast emhttpd: error: get_filesystem_status, 6474: Input/output error (5): scandir Mar 30 23:26:07 TheNewdaleBeast kernel: XFS (md2): metadata I/O error in "xfs_trans_read_buf_map" at daddr 0x15d508f48 len 32 error 5 ............................ screenshot shows five appearing as unmountable (were mounted and functioning with no problem in stable 6.6.7) also attached is the diagnostics log. going to revert back again to a functioning system! thenewdalebeast-diagnostics-20190330-2333.zip
  5. Generating some 4096 RSA certs - should more than one thread be getting allocated? Cheers Duggie
  6. Hi, Installed this plugin on 6.6.7, and after changing the settings to what I require, am unable to get a client to connect - I will continue fault finding, but in the meantime, if you set LZO compression to No in the Server Config page, whenever you create files, line 17 is simply a 0. should it be "comp-LZO No" or "comp-LZO 0"?
  7. Just updated 6.6.6 to 6.6.7, stable with no issues. I then updated to 6.7 rc5, and suffered the same problem as when I tried to update from 6.6.6 to 6.7 rc2 (although I didn't post at the time for various reasons) When I reboot, Multiple drives show as failed/unassigned. I reverted back to 6.6.7, now my second parity, and one of my data drives (drive 2), show as disabled. (in the previously unreported instance this was parity 2 and Drive 6). I have attached the diagnostic log in case it is of use. cheers Duggie thenewdalebeast-diagnostics-20190225-2307.zip - failed 6.7rc5 install - FS not present, array in tatters thenewdalebeast-diagnostics-20190225-2329.zip - restore to 6.6.7 - 1 parity and 1 array drive borked
  8. Query - installed SABNZBVPN, have it all up and woirking except.... files are downloading to /config/downloads instad of /data/downloads. When I look in SABNZB settings the default user folder has a "Default Base Folder: /config" which I am not able to change (within SABNZBVPN). This is the same as the system folders. Should the default base folder for User not be /data ? Cheers Duggie OK cancel this, just had to go back to root then select data instead of config, then my downloads/complete and incomplete folder! Still think the default folder for User should be Data though, would provide consistency with other containers? Cheers Duggie
  9. Thanks, that has got me past that hurdle, although for some reason it sill wants the protocol name on a separate line OK, so after a little more work, I was able to get it up and running. 1. Had to add username and password within the docker settings itself. From the ovpn config file; 2. Remove the "proto udp" line 3. Add " 443 udp" to end of remote line. 4. Change "ns-cert-type server" to "--remote-cert-tls server" [removes warning of deprecated command from log file] Seems to be good at the moment, so thanks again!
  10. Binhex, Hello, and thank you for your enormous amount of very fine work! I am running UnRAID 6.3.5, with DelugeVPN docker (yours, obviously - have an issue I have mentioned in that support thread) and PlexPass docker. When I click on the Photos library I get the following error; There was an error loading the timeline for this library The photos timeline requires Plex Media Server 1.5.4 or higher Media Server installed version is: Version 1.11.0.4633 - and when I click for update version it tells me it is up to date. I suspect that I am missing somethin obvious, can you assist? Regards Duggie Just got the update - Many Thanks BinHex!
  11. Hi, Relative n00b here, just setting up Deluge VPN, have installed the docker, and added my VPN providers .opvn file to \\........\appdata\binhex-delugevpn\openvpn it contains the folowing lines: client dev tun reneg-sec 0 persist-tun persist-key ping 5 ping-exit 30 nobind comp-lzo adaptive remote-random ns-cert-type server route-metric 1 CERT HERE CERT HERE PK HERE remote REMOTE VPN SERVER DN proto udp (items in bold altered for privacy) When I attempt to start DVPN, the log states " VPN_PORT not found in /config/openvpn/OPVNFILENAME.ovpn I have tried adding "port 443" after the remote line, but this seems to have no effect. Am I missing something really obvious, before I start deep diving into the issue? Thanks, Duggie
×
×
  • Create New...