dstroot

Members
  • Posts

    79
  • Joined

  • Last visited

Everything posted by dstroot

  1. Awesome Gary! Thanks. May use a Fractal design 804 as the case. Just went on sale...
  2. True ... and many of us who build mini-ITX servers are very focused on keeping our power consumption as low as possible. For example, my Q25B system idles under 20w @garycase - hey Gary if you read this I am building a small system in the next couple weeks. No more than four drives and some headroom for a few docker containers. Just looking for MB/CPU and maybe Power Supply advice. What would be the best low(ish) power bang for the buck MB and CPU these days? Since I know you are an ECC memory fan let's assume ECC RAM as well. Thanks!
  3. What MB/CPU would people recommend if building in this case today?
  4. To improve the copy speed, add -W (--whole-file), to avoid calculating deltas/diffs of the files. This is the default when both the source and destination are specified as local paths, since the real benefit of rsync's delta-transfer algorithm is reducing network usage.
  5. I don't know what teracopy is but I think it's a windows program. Why would I pull all my data over a wire to a windows box and then push it back over the wire to a different disk on my unraid array? Why not ssh into you array and use rsync? Something like: `rsync -aAW --progress disk2 disk3` ?
  6. I keep getting emails with this: error: skipping "/var/log/docker.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation. error: skipping "/var/log/syslog" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation. error: skipping "/var/log/vsftpd.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation. error: skipping "/var/log/wtmp" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation. error: skipping "/var/log/btmp" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation. It was mentioned by others earlier in the thread. Is there a fix? Thanks.
  7. Anyone having difficulty getting cache-dirs to start? I can't seem to get it rolling. I took the script version out of my go file already.
  8. Should I remove the old docker plugin? See attached image.
  9. Before I updated to 10a, version 10 showed I only had one single plugin (unRAID Server OS). After upgrading to 10a the old docker manager plugin seems to have "come back" and says it's out of date. Should I update it or delete it?
  10. FWIW I'd love to see this sooner rather than later!
  11. Ummmm... wow everyone is just way ahead of me. How do I convert my cache drive to btrfs so I can even fire docker up? Getting this error: Jun 19 19:56:36 Tower php: /etc/rc.d/rc.docker start Jun 19 19:56:36 Tower php: ERROR: Docker install path (/mnt/cache/docker) must be off a btrfs device
  12. One more question - I have searched all over and feel really dumb but I cannot figure out how to boot into "Dom 0" mode so Xen is working. I run headless and don't even have a monitor anymore where I could see the boot options - is that what I am missing? Anyway to set to boot with Xen support via .cfg or go files? I really have looked all over but most Xen posts seem to assume you have already booted properly to Xen mode. OK - after more digging I found you can edit syslinux.cfg from the Unraid GUI. Default settings below: default /syslinux/menu.c32 menu title Lime Technology prompt 0 timeout 50 label unRAID OS menu default kernel /bzimage append initrd=/bzroot label unRAID OS Safe Mode (no plugins) kernel /bzimage append initrd=/bzroot unraidsafemode label Memtest86+ kernel /memtest label Xen/unRAID OS kernel /syslinux/mboot.c32 append /xen --- /bzimage --- /bzroot label Xen/unRAID OS Safe Mode (no plugins) kernel /syslinux/mboot.c32 append /xen --- /bzimage --- /bzroot unraidsafemode What do I edit to use Xen?
  13. Quick question - Do the "cache dirs" and "s3 sleep" plugins work with this beta? Anything I need I need to know about installing them if so? Thanks in advance!
  14. +1 Was expecting either the Unraid new WebGUI to be more polished, or the stock webGUI to be basic and SimpleFeatures be the "deluxe" version. At least tell us what the strategy is now.
  15. Anyone have a way I can get back to rc12a? This one will not sleep and resume properly. Once it sleeps and wakes up it is not accessible and I don't have time troubleshoot. 12a worked perfectly for me. Cheers, Dan
  16. Just so folks know... UnRaid has had a race condition problem with the plugin feature. I do not personally think its fixed yet and that is what I believe some of us are running into and why we have run the installer manually. If the network has not yet finished initialization by the time the install runs the installs fail. That's why it works when you run it manually (i.e. by then everything is up). I have a Supermicro board and I use DHCP to hand out addresses (even "static" ones) - it's just easier that way, and I think this slows my network initialization enough that the plugin installer always fails on boot. Hope this helps someone.
  17. Uhhh... I just flew for 7 hours but where do you put the core .tgz file? Nevermind - I see the core is now a plugin in the plugins directory since I downloaded the whole zip archive.
  18. It's because you named your UnRaid server "freenas". It's confused.
  19. Thanks Weebotech - I'll give that a try. Cheers.
  20. My server is supposed to go to sleep each night at 10 pm as long as no one is accessing it. Just noticed in the logs something is croaking everytime the server tries to go to sleep: Jan 5 22:01:08 Tower kernel: PM: Syncing filesystems ... done. Jan 5 22:01:28 Tower kernel: Freezing user space processes ... Jan 5 22:01:28 Tower kernel: Freezing of tasks failed after 20.01 seconds (1 tasks refusing to freeze, wq_busy=0): Jan 5 22:01:28 Tower kernel: find D c14a6fc0 0 17344 17328 0x00800004 Jan 5 22:01:28 Tower kernel: f062fed8 00000082 c14a6fc0 c14a6fc0 c14a2000 f04c269c c14a6fc0 f061c62c Jan 5 22:01:28 Tower kernel: 00000003 f04c2520 00000003 f062fe88 c1025870 f062feac c101f3fa 00000000 Jan 5 22:01:28 Tower kernel: f7546034 f04c2520 f062feb4 c10328d5 00000292 00000292 f04c2520 f062fecc Jan 5 22:01:28 Tower kernel: Call Trace: Jan 5 22:01:28 Tower kernel: [] ? default_wake_function+0xb/0xd Jan 5 22:01:28 Tower kernel: [] ? __wake_up_common+0x34/0x5c Jan 5 22:01:28 Tower kernel: [] ? __set_task_blocked+0x66/0x6c Jan 5 22:01:28 Tower kernel: [] ? set_current_blocked+0x27/0x38 Jan 5 22:01:28 Tower kernel: [] schedule+0x48/0x4a Jan 5 22:01:28 Tower kernel: [] request_wait_answer+0x11d/0x1b5 Jan 5 22:01:28 Tower kernel: [] ? wake_up_bit+0x5b/0x5b Jan 5 22:01:28 Tower kernel: [] fuse_request_send+0x96/0x9c Jan 5 22:01:28 Tower kernel: [] fuse_readdir+0xb9/0x170 Jan 5 22:01:28 Tower kernel: [] ? generic_block_fiemap+0x43/0x43 Jan 5 22:01:28 Tower kernel: [] vfs_readdir+0x53/0x7e Jan 5 22:01:28 Tower kernel: [] ? generic_block_fiemap+0x43/0x43 Jan 5 22:01:28 Tower kernel: [] sys_getdents64+0x63/0xa5 Jan 5 22:01:28 Tower kernel: [] syscall_call+0x7/0xb Jan 5 22:01:28 Tower kernel: Jan 5 22:01:28 Tower kernel: Restarting tasks ... done. Anyone have any ideas? I am using the server only as an SMB server - nothing fancy... Only additions are Joe's cachedirs script, a sleep script, and a script to control the fan. Nothing else. Full log attached. log.txt
  21. Guzzi - yes this will work with your drives and will not spin them up to check temperature.
  22. By setting the lower boundary at the point where the fan won't decrease speed any further I get a nice smooth ramp up: (note the reported 0 rpm is actually hard coded - the fan never goes below about 720rpm) Nov 24 09:07:59 Tower fan_speed.sh: Highest disk drive temp is: 31C Nov 24 09:07:59 Tower fan_speed.sh: Changing disk drive fan speed from: [OFF (0% @ 0 rpm) ] to: [64 (38% @ 746 rpm) ] Nov 24 09:18:07 Tower fan_speed.sh: Highest disk drive temp is: 32C Nov 24 09:18:07 Tower fan_speed.sh: Changing disk drive fan speed from: [64 (38% @ 733 rpm) ] to: [78 (47% @ 774 rpm) ] Nov 24 09:28:15 Tower fan_speed.sh: Highest disk drive temp is: 33C Nov 24 09:28:15 Tower fan_speed.sh: Changing disk drive fan speed from: [78 (47% @ 774 rpm) ] to: [92 (55% @ 819 rpm) ] Nov 24 09:48:26 Tower fan_speed.sh: Highest disk drive temp is: 34C Nov 24 09:48:26 Tower fan_speed.sh: Changing disk drive fan speed from: [92 (55% @ 815 rpm) ] to: [106 (64% @ 907 rpm) ]