• Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About CrimsonTide

  • Rank
  1. That doesn't seem to work for the deconz docker. It can't "see" the USB dongle unless I use the /dev/ttyACM0 path.
  2. I have USB keys for deconz and zwave, and I am sick of having to reassign the dockers path to the USB every reboot when they are randomly assigned ttyACM0, 1,2,3 etc. I set up the 99-usb-serial.rules to try to makes symbolic links per the tutorials: /etc/udev/rules.d/99-usb-serial.rules SUBSYSTEM=="tty", ATTRS{idVendor}=="1cf1", ATTRS{idProduct}=="0030", ATTRS{serial}=="DE2149591", SYMLINK+="deconz" SUBSYSTEM=="tty", ATTRS{idVendor}=="0658", ATTRS{idProduct}=="0200", ATTRS{serial}=="0000:00:2d.7", SYMLINK+="zwave" it appears that it's working, I see a link /dev/d
  3. Swapped out the power supply and it's been up now for 3 days. Hopefully that was the issue!
  4. I'm tempted to replace the power supply since that seems to usually be the culprit in random-shutdowns in the past on other systems. I'm just a little skeptical it's a hardware issue since it only happens overnight. I stress the server during the day with high CPU usage and it does fine. Memtest was fine also. Edit - crashing randomly during the day now too.
  5. Docker vDisk location: /mnt/user/DockerImg/docker.img Default appdata storage location: /mnt/user/appdata/ How do I tell what disk /mnt/user is on, since it's not on a share?
  6. Tonight it crashed as usual - I had docker service enabled but all dockers off.
  7. Ok, with docker disabled it didn't crash overnight. However, when I enabled docker in the morning, it crashed immediately. Yet, when it reboots, docker comes up normally.
  8. I can try disabling dockers overnight. What is the issue with running the mover hourly? I figured it kept the cache drive at low use in case there was an incoming large file. It looks like all the mover syslog entries are terminating without error.
  9. Update - disabling trim didn't help, still crashed overnight. Nothing else is in the scheduler as far as I can tell that would occur every overnight.
  10. Hello! My server is crashing nearly every night. Not sure the exact time, but I always wake up and it crashed overnight. Things I've tried so far: 1) Switching from DVB version of 6.8.3 to 6.9.0-rc1 2) Run syslog tail - last few entries before connection closed is: Dec 15 23:00:16 SkynetUNRAID crond[2217]: exit status 1 from user root /usr/local/sbin/mover &> /dev/null Dec 16 00:00:12 SkynetUNRAID crond[2217]: exit status 1 from user root /usr/local/sbin/mover &> /dev/null Dec 16 01:00:12 SkynetUNRAID crond[2217]: exit status 1 from
  11. Will this work if I am using the DVB plugin - which is already installing a custom bzroot and bzimage files?