Jump to content

BKG

Members
  • Posts

    36
  • Joined

  • Last visited

Everything posted by BKG

  1. Still no go. Before I changed network to HOST it was just not starting and now after I changed it it throws an error
  2. Got it! Now I am obviously having problems starting the container after changing the ports as suggested in the beginning of this thread. Of course the reason for that is my lack of understanding. Can you guide me in the right direction please? I have done the following: changed port 8080 -> 8088 changed port for WEBUI for 8088 created an additional entry path "PORT TYPE" with port 8088 I now can not start the docker. Is this something I have to change in CLI? Thanks,
  3. Thanks wgstarks. If want to modify the location can I provide any path? for example: /mnt/user/Downloads/. Or do I have to create "data" folder in the new path? example: /mnt/user/Downloads/data Thanks again.
  4. Hi, where is the path for the downloads in the template? Thanks,
  5. I have mine setup in the following way, if it helps. Also, I only have 6 cameras. See below: I have created Win10 pro VM with the passthrough for CPU. I have allocated 80GB for the system drive and also it acts as a "NEW FOLDER" with the 10GB limit for the new recorded clips. After the limit is reached the clips are moved to "STORED" folder which is located on the separate 4TB drive. I have 4TB drive setup as "UNALLOCATED DEVICE" in pass-through mode.
  6. Hi guys, I have run into a dead end with this one. I have two NICs. I have one VM - Win10 and two dockers - pihole and UNIFI controller. No matter what I do with the NICs I can;t get it to work on two different subnets. I want my VM and unRAID to be on 192.168.10.0/24 subnet and my dockers on 192.168.0.0/24 subnet. Any help appreciated. Thanks.
  7. Thanks trurl. makes perfect sense! It is all buttoned up now!
  8. I am trying to understand what its the way to make the system (without the use of CLI) to create and keep ISO image share on the chosen disk. For some reason and as a default the system created the ISO share on Disk 1, even though I already had the cache pool when I created the unRAID. So, here is my case represented graphically (see attached PDF). I hope I am not overcomplicating things 🙂 case use (1).pdf
  9. I don't work with disk shares and do work with user shares. I guess I used the wrong wording. At the moment isos share is on - /mnt/disk1 and want it to reside on - /mnt/disk3
  10. Perfect! Thank you Squid and trurl. I didn't know that. I disabled the Docker and VM and ended up having only isos on Disk 1 which is normal since the share is set to CACHE/YES. Now how do I make the isos share reside specifically on Disk 3? Do I just copy the folder on Disk 3 and then place the ISO image there? Also, I made the following settings in the share: Thanks
  11. Hello, I am new to unRAID. I have an array of 4 disks and one SSD for cache pool. After reading the above thread I have two questions. I have noticed the same happening in my case(docker and VM ended up on Disk 1). As I was reading more about it I removed(uninstalled) the dockers and VM and cleaned the /mnt/user/appdata with rm -rfv. I then ran the MOVER but still have two folders on Disk 1. Question 1. Can I manually delete those two folders on Disk 1? Question 2. I want to have a cache pool made from two SSD drives formated in BTRFS. Based on the below quote, should I rename the pool to "cache" after I add the second SSD? Thanks,
×
×
  • Create New...