nuhll

Members
  • Content count

    324
  • Joined

  • Last visited

Community Reputation

7 Neutral

About nuhll

  • Rank
    Advanced Member
  1. Xeoma - Surveillance Software

    Thanks for the docker, now i have another problem Jan 14 02:02:04 Unraid-Server shfs: error: shfs_rmdir, 1517: Directory not empty (39): rmdir: /mnt/disk4/Kamera/somedir/2018-01-12 Jan 14 02:02:04 Unraid-Server shfs: error: shfs_rmdir, 1517: Directory not empty (39): rmdir: /mnt/cache/Kamera/somedir/2018-01-13 Jan 14 02:07:04 Unraid-Server shfs: error: shfs_rmdir, 1517: Directory not empty (39): rmdir: /mnt/disk4/Kamera/somedir/2018-01-12 Jan 14 02:07:04 Unraid-Server shfs: error: shfs_rmdir, 1517: Directory not empty (39): rmdir: /mnt/cache/Kamera/somedir/2018-01-13 Jan 14 02:12:04 Unraid-Server shfs: error: shfs_rmdir, 1517: Directory not empty (39): rmdir: /mnt/disk4/Kamera/somedir/2018-01-12 Jan 14 02:12:04 Unraid-Server shfs: error: shfs_rmdir, 1517: Directory not empty (39): rmdir: /mnt/cache/Kamera/somedir/2018-01-13 Jan 14 02:17:04 Unraid-Server shfs: error: shfs_rmdir, 1517: Directory not empty (39): rmdir: /mnt/disk4/Kamera/somedir/2018-01-12 Jan 14 02:17:04 Unraid-Server shfs: error: shfs_rmdir, 1517: Directory not empty (39): rmdir: /mnt/cache/Kamera/somedir/2018-01-13 Jan 14 02:22:04 Unraid-Server shfs: error: shfs_rmdir, 1517: Directory not empty (39): rmdir: /mnt/disk4/Kamera/somedir/2018-01-12 Jan 14 02:22:04 Unraid-Server shfs: error: shfs_rmdir, 1517: Directory not empty (39): rmdir: /mnt/cache/Kamera/somedir/2018-01-13 server log is full of this, app log doesnt show anything... i created a share for this app /Kamera/ with cache setting "Yes"
  2. U can set the default spin down time, but if im right its 15min with 6.4 I have set it to 15, but most i do anyway on the cache drives, so it really just needs to spin up for mover or if i play a movie (and then it wont spin down anyway) Just btw, i dont think its good if you post to 8 year old threads... bc this information here is very outdated.. it also depends on your energy bill, i have high energy cost here, so i try to save as many watt as possible.
  3. Thanks, i will see if i find something out.
  4. Hmm, ofc i cant be sure, but i dont thin xeoma is accessing old files. Its just writing files when something on camera happens.... Is there a way to check whats happening?
  5. Hi there, since i added my new 9201-e16 i found a problem. Yesterday i added Xeoma as docker for 2 surveilince cams, i set the share to cache yes, still disk 4 (containing atm the footage) and the parity disk ofc is not spinning down, atleast not always. Whats wrong? I thought about maybe bc its opening that directory, but i also have that cache dir plugin, so this shouldnt be the problem? Xeoma is creating many small files 2-3mb usually.
  6. I cant say, it was in the first minutes i used unraid bc i didnt understand how the structure worked...
  7. The simplest and easiest and fastest way probably is to start new i would follow the guides this guy makes
  8. Why dockers cant reach subnet?

    I fixed it. Stupid Google wifi its not able to do correct NAT. I fixed it by telling the draytek router a static route Destination IP Address 192.168.86.0 Subnet Mask 255.255.255.0 Gateway IP Address 192.168.0.102 Network Interface LAN1 (If 192.168.86.* send to 192.168.0.102 < thats the google wifi address) Normal Google Wifi should just accept this and sent it to the correct client, but since google wifi is shit, it doesnt do that. But i fixxed it by adding a port redirection inside google wifi to the correct Google wifi adresses.
  9. Dont know, i did it, without problems, is this still a thing in 6.4?
  10. Hi there, maybe someone know... My unraid server is in 192.168.0 I have 2 cameras in 192.168.86 (Google wifi) I can connect from 192.168.0 to 192.168.86 and the other way around. But the dockers cant, why? Edit: okay i found out 192.168.0 cant reach 192.168.86 Other way around works. Someone has an idea? I have draytek router at 192.168.0 many options, but im no network guru.
  11. As far as i know all dockers are stored inside the docker.img, so all you need to backup and replace is this file. How i added the cache: - stopped server - added ssd - startet server - looked at "MAIN" - there was option to let parity run (or unraid asked me to do so, cant remember) i did - took ~7 h - then i could tick "format?" - clicked start, after some minutes it was finished and all was working... - the whole time all dockers plugins was running, without problems. But i guess all problems startet becase you didnt understand the file structure of unraid. You should put all things in /mnt/user/<name>/ e.g. i have it like this /mnt/user/Archiv (added share with name Archiv) there i have simply created normal directory via SMB /mnt/user/Archiv/Movies /mnt/user/Archiv/Games u get the idea... All dirs in /mnt/user/here u should create via add share Via "use cache disk" you tell the system how to use the directory... e.g. in Archiv i set it to "Yes" = this means fast transfer speeds to the array, and one time a day it gets moved to the real HDDs. "Always" means it stays always at cache (i do it for all VMs, Images, plugins, and so on - so hdds dont need to spin up). "no" wont use cache atall. (but everything is also explainted if you click it in the UI [as i were new i didnt know that!]) For the system /mnt/cache/Archiv is the same like /mnt/user/Archiv Or /mnt/disk1/Archiv But if u put it in /mnt/cache it will stay there, if you put it in /mnt/user/here you can controll it via settings from share. If you dont understand mover, you can also manually transfer the files via "mv" in terminal. (thats how i did it after i initially didnt understand the structure, bc its nothing i ever saw before- but its brilliant!) like "mv /mnt/cache/dir /mnt/user/dir" Will move dir from cache to user directory (but before add a share with that name) But attention, dont write anything in terminal you dont understand and dont write it wrong, one command can delete everything :)) One extra tip: if you put the .imgs on the hdds, then you should delete the .img in the VM (cd drive), else the hdd spins everytime up.
  12. Cheap UPS?

    So i bought hte one i said and installed it some days ago, working like a charm, but best is (i didnt know) u can now read the watt used in interface of unraid... pretty happy, gives me about 20 of downtime, which is more then i need.
  13. CPU freq not stepping down

    r u guys using 6.4? I also thought it wont throttle down, but it was. On 6.4 atleast. If nothing is done my u3 now only takes 65 watt incl. USP Edit: found my thread: Whats the reason some ppl still use old versions of unraid?
  14. Does unraid use PCIe power down?

    Yea, that would m ake sense. I need to look at power because here in ermany power is not cheap. I pay ~0,8usd per kwh. So this make a difference. Before unraid my server took nearly 200 watt now between 60-75 if no work on hdds done.

Copyright © 2005-2017 Lime Technology, Inc. unRAIDĀ® is a registered trademark of Lime Technology, Inc.