Jump to content

dan91

Members
  • Content Count

    16
  • Joined

  • Last visited

Community Reputation

0 Neutral

About dan91

  • Rank
    Member
  1. Hi, are you experiencing high CPU usage after disconnecting from RDP to the VM? If so its likely a problem due to the 1903 update in windows. See link below for a work around; https://borncity.com/win/2019/08/28/windows-10-v1903-rdp-dwm-exe-causes-high-cpu-load-freezes-vms/ If thats not the issue then ignore this post. I had this issue with 3 of my VM's so just making people aware!
  2. Hi, are they windows VM's? Just double check your not experiencing this issue; https://borncity.com/win/2019/08/28/windows-10-v1903-rdp-dwm-exe-causes-high-cpu-load-freezes-vms/
  3. Wrong or Long? 🤣😂 After the problem I had with the 512 char limit ive shortened it now to under 260!
  4. Hi, It doesnt do anything unfortunately it seems to just hang. tower-diagnostics-20191016-1851.zip
  5. Hi please see diagnostics attached but that is as far as it gets it just hangs. Would it be anything to do with i'm using the second password on my LUKS volume due to the post I made in the main thread? tower-diagnostics-20191016-0642.zip
  6. Hi, Sorry I mean the unraid web page encryption passphrase limits it to 512 characters (Or did on the old version) any extra is not included so when I created the encrypted array even though I pasted more than that it was chopped to 512 chars. Which is why I struggled to get the paste into a file and mount using the keyfile command working as I was entering the full password. I first had to mount the array normally (entering the passphrase in the web ui) and look at the keyfile it made and see what was chopped off the end. After doing that I was able to mount it fine using a copy pasted into a file and using the keyfile what I meant by 2 was something in my old passphrase stops the new way you are doing it from working. I confirmed this seems to be a problem with cryptosetup as I tried to mount one of my unassigned devices manually using the cryptsetup luksOpen command. When prompted to enter the password and I enter the password which is now correct and works fine in the keyfile it fails to load. Leaving me to think that something in my password is not supported using that method and which is why unraid fails to mount using the new method of not making a keyfile. Hopefully this makes a bit more sense? Thanks
  7. Had an issue with the change to encryption away from the entering you passphrase makes a keyfile and mounts using that. It seems my passphrase is; 1) too long 2) has characters that dont translate into the standard password prompt luks would provide these are some characters which were in my password as an example; Ö®ëÆ This doesnt really seem to be a bug in unraid as after testing I cannot mount the drive by running it manually on the disk with this password it has to go into a keyfile first (even though i normally just paste the phrase into the webui) which would normally put it in a keyfile and mount that way up until this version which is why ive only just noticed the problem. Just spent 5 mins adding another key to all my disks and now no issues except for unassigned devices which i posted in the other thread. This is more of an info post for anyone else who may experience the issue!
  8. Hi, I have updated to the newiest version of Unassigned devices and on RC1 When it trys to map my unassigned devices it does the following but then does not do anything, the array does not finish mounting so none of my services start. Oct 15 19:17:36 Tower unassigned.devices: Mounting 'Auto Mount' Devices... Oct 15 19:17:36 Tower unassigned.devices: Adding disk '/dev/mapper/Crucial_1TB'... Oct 15 19:17:36 Tower unassigned.devices: luksOpen: key file not found - using emcmd to open: 'cmdCryptsetup=luksOpen /dev/sdk1 Crucial_1TB --allow-discards'
  9. Hi, For me I found the issue seemed to be the plugin Dynamix Cache Dirs once i removed that i was ok.
  10. Hi all hope someone can help, having an issue where SMB stops responding. This can easily be seen on a VM which uses network drives as a seed location. It will be seeding at full speed then simply halt seeding. This also co-insides with the network shares not responding on other machines and files playing in kodi stopping. This lasts a few seconds to a few minutes then everything resumes. Ive read about some issue's being file system and XFS not supposedly having this issue however all my disks are using XFS. Also attached the diagnostics thanks. i5-3570K 32 GB Ram 14 3TB drives (2 Parity) 500GB SSD cache Couple of unassigned drives 1TB x2. pluto-diagnostics-20180521-1702.zip
  11. @NeoDudeHi, this is required as i wish to cache requests on port 80 but simply proxy requests on SSL. (Steamcache essentialy). They do this with two different docker images one caching the requests the other running sniproxy on 443. I need to be able to assign them the same IP so things like the steam store and friends lists function but game downloads go though the cache.
  12. Sorry to bump this but anyone have any input?
  13. Hi all hope someone can maybe point me in the right direction. I can see you can assign a specific IP to a docker image however you cannot then use this same ip on another for a different port. I have groups of 2 docker images that need to be on the same IP but different IP's between groups. Example Docker 1 - 192.168.0.4:80 Docker 2 - 192.168.0.4:443 Docker 3 - 192.168.0.5:80 Docker 4 - 192.168.0.5:443 I thought maybe assigning these IP addresses to unraid then choosing to bridge to them rather than the default IP of unraid. Although honestly i'm kind of stumped on Unraid. On a general Linux system you can add extra IP's to interfaces and then pass them through to docker. e.g. doing this on the host iface eth0 inet static address 192.168.0.4 netmask 255.255.255.0 gateway 192.168.0.1 iface eth0:0 inet static address 192.168.0.5 netmask 255.255.255.0 Then starting the dockers like so docker run (whatever it is your running) -p 192.168.0.4:80:80 docker run (whatever it is your running) -p 192.168.0.4:443:443 docker run (whatever it is your running) -p 192.168.0.5:80:80 docker run (whatever it is your running) -p 192.168.0.5:443:443 Is it possible to do something like this on Unraid? Anyone point me in the right direction, Thanks!
  14. Moving my appdata / config folders from an unattached device to the cache ssd seems to have solved the issue. Although i'm unsure why it would be an issue? Thanks for your help
  15. Hi thanks for the reply hope this helps pluto-diagnostics-20180404-0021.zip