Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

17 Good

About -Daedalus

  • Rank
    Advanced Member


  • Gender

Recent Profile Visitors

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

  1. +1 Would absolutely love to see this. I imagine it won't show up until 6.8 or later, registering interest none-the-less.
  2. Nope, they're all spinning. I've been running this same hardware for a few months now and haven't had issues previously. Also, the array starts fine in maintenance mode, with the disks unmounted, so I don't think it's a power issue. Edit: 4U systems are bloody heavy... After some hardware troubleshooting, looks like I've either got two defective DIMM slots, or an issues with the CPU's IMC. Doesn't seem to be an OS issue after all!
  3. Happened again. This time, I can't start the array without the server rebooting within a few seconds. I can start it in maintenance mode, but I'm not sure where the logs would be. The system was set to log the syslog to /mnt/user/logs, but obviously I can't get there in maintenance mode. There is a syslog in /boot/logs, but it doesn't look like there's much there, attached anyway. Anyone able to offer advice on where to look for logs during the crash? logs.log
  4. You'd swear it was in an obscure place.... Thanks, I don't know how I managed to miss that, plain as day. Enabled. We'll see if this happens again. Cheers!
  5. Hi all, My server rebooted at some point between last night and this afternoon, cause unknown. I have diags attached, but I doubt they'll be much help considering there's nothing from before the reboot. I remember a request being made for unRAID to be its own logging server, but unless I'm mistaken this hasn't been implemented yet? It's an extremely humid, and pretty hot day here, so it could have just been a thermal shutdown, but it would be nice to have an idea as to the cause. Any help would be great. server-diagnostics-20190530-1605.zip
  6. Bumping this as it's the first result I found while searching. Would it be possible to get an option for this in the UI? Maybe something about setting a default location under the Date/Time settings?
  7. That was a mighty fast reply! You're right, of course. I was initially going to say that setting a daily move through cron would mean that the mover would run during a parity check (for some reason I assumed the "don't move during parity" option was only for the x% move), but on reflection, that would be nonsensical. Dumb-ass satisfied. Carry on.
  8. Simple question, unless I'm missing something: It looks like with this plug-in enabled, the default daily mover operation gets overridden, correct? I always thought MT ran in addition to schedule. For my use-case, I'd like the mover to still run daily, but also have this set to move at x%, just in case the cache gets full from a busy day. I realise I could force this via cron, but then it would also trigger during a parity check, which I would rather not happen. If I'm missing something obvious, please let me know. Otherwise, would it be possible to include this option in an update?
  9. Since then, there's a second one in there as well. Both rock solid. On 3.50 BIOS.
  10. +1 from me. Would be very handy.
  11. While the CPU pinning page is definitely an excellent step forward, I'd argue it's use case is config, rather than monitoring. What they're asking for can be solved for using top or CAdvisor or something, but it would be nice to have an output in the GUI somewhere of who is doing what. Resource monitoring is one area where unRAID definitely has room to grow. Especially when you consider the system stats plug-in isn't included by default.
  12. Thanks for the reply. I absolutely have put my +1 (more than once, heh) in that request. But what I'm asking isn't creating a second cache pool from terminal, but rather making a RAID1 using the BIOS first, then passing that to UD. Your option is probably a slightly better in that it keeps everything managed within unRAID. I will have to have a think on which I'll go for. Do you know if trim is properly support with NVME drives created in a secondary pool like this? Maybe @johnnie.black does? Thanks again!
  13. Quick one for any of the Threadripper users on here: Has anyone tried passing through an NVME RAID1 to unRAID? I have no idea if this would work or not. From what I can see, the only drivers AMD has for it are Windows. I'm looking to have SATA SSD for cache, Docker, etc. and a separate pool for VMs. I was thinking a motherboard-driven RAID1 passed through to UD would be an ideal solve for this, but don't have any NVME drives lying around. Has anyone tried this with any success? (ASRock Taichi here) Cheers!
  14. Just an FYI: The plugin "Server layout" does much of what you want (though I agree, something like this would be great to have natively). You can pick in what orientation your drives show up (columns and rows), then assign a drive to each slot. It will give you all the information on the drive (serial number, letter, firmware version, etc.), and there's also a "Notes" section for anything custom you might want to include.
  15. Ok, since this hasn't really gotten any feedback, let me distil it down to my most important question at the moment: Can I change my passphrase/keyfile (or switch from one to the other) later on, without having to reformat any disks?