• Content Count

  • Joined

Community Reputation

2 Neutral

About Pillendreher

  • Rank

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. I've been experiencing the same issue over the last couple of days with the very same behavior. As soon as I put load on the drive, it goes offline and even a reboot doesn't help. I had the same problem a couple of weeks ago back when the drive wasn't housing my Docker files and just acted as a secondary cache drive and iirc I actually managed to fix this, but for the life of me I can't remember what I did...back then it happened when trying to remove unnecessary streams from mkv files - the drive just collapsed. After I changed something though it worked without issue.
  2. Thank you for this. This gets docker going again without having to restart the whole sever.
  3. I went back to Beta 35 to check if the unwanted spin-ups I've experience with RC2 were happening.
  4. I've just experienced the very same issue with Beta35 two days in a row - the Docker service went down while I was at work. Reboot fixed it until the docker service broke again.
  5. Actually they are not. I ran the diagnostics tool right after Docker crashed. I only rebooted afterwards!
  6. Since going from Beta35 to RC2, my Docker service has started crashing irregularly. I have not been able to reproduce it, but this is what I get as an error message when clicking on the Docker tab: Docker Service failed to start. Warning: stream_socket_client(): unable to connect to unix:///var/run/docker.sock (Connection refused) in /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php on line 682 Couldn't create socket: [111] Connection refused Warning: Invalid argument supplied for foreach() in /usr/local/emhttp/plugins/dynamix.docker.manager/inc
  7. Same here. I reckon something went wrong during a modification of how smart information is gathered (If I remember correctly I read something regarding SMART in the changelog)
  8. With the RC2, my drives keep waking up, apparently because Unraid is pulling smart data: Dec 29 00:03:47 Tower emhttpd: spinning down /dev/sdd Dec 29 00:07:22 Tower emhttpd: read SMART /dev/sdd Is there any way to keep this from happening? I didn't have this problem with Beta 35. EDIT: Oh, and another thing: Twice now my Docker image seemed to be broken (got a weird error message that looked like something about the webgui was broken: "Docker service wont start"), but instead of having to rebuild the image, a restart fixed it. That didn't happen ei
  9. Thanks, just got around to enable it - works flawlessly.
  10. Already done this as well. Issues happened on port 4, I switched to port 3. I was away for a couple of hours and the resets keep happening: Dec 13 14:36:00 Tower kernel: ata3: SATA link up 6.0 Gbps (SStatus 133 SControl 300) Dec 13 14:36:00 Tower kernel: ata3.00: supports DRM functions and may not be fully accessible Dec 13 14:36:05 Tower kernel: ata3.00: qc timeout (cmd 0x2f) Dec 13 14:36:05 Tower kernel: ata3.00: failed to get NCQ Send/Recv Log Emask 0x4 Dec 13 14:36:05 Tower kernel: ata3.00: NCQ Send/Recv Log not supported Dec 13 14:36:05 Tower kernel: ata3.00: ATA Id
  11. hdparm shows me this after the drive wakes up: root@Tower:~# hdparm -C /dev/sdd /dev/sdd: drive state is: unknown
  12. I didn't find NCQ as a setting for the individual disk, so I went ahead and disabled it for all disks in the general disk settings. I'll get back to you after a reboot and spindown EDIT: This can't be a coincidence, can it? The system runs for two hours without the drive waking up. I open up the Web Interface, check the log and suddenly the drive spins up: Dec 13 00:18:37 Tower webGUI: Successful login user root from Dec 13 00:19:00 Tower kernel: ata3: SATA link up 6.0 Gbps (SStatus 133 SControl 300) Dec 13 00:19:00 Tower kernel: ata3.00: supp
  13. I'd like to request the New Vegas soundtrack playing in the background when using the Fallout theme These look amazing and I can't wait to use them! Thank you!
  14. Hi there, I'm currently using 4 HDDs. One of them is a shucked WD 14 TB drive. All of them go to sleep when unused, yet the 14TB one keeps waking up without Unraid realizing it - it neither shows the temperature nor turns the grey circle green. This is what shows up in the log every time the drive wakes up (which is irregular - sometimes it stays asleep for multiple hours, sometimes it wakes up every 30 minutes): Dec 12 19:03:20 Tower kernel: ata3: SATA link up 6.0 Gbps (SStatus 133 SControl 300) Dec 12 19:03:20 Tower kernel: ata3.00: supports DRM functions a
  15. Is there any way to get a readout on the actual voltage levels of the CPU? A before/after comparison would be nice when it comes to undervolting.