-Daedalus

Members
  • Content Count

    319
  • Joined

  • Last visited

Community Reputation

41 Good

About -Daedalus

  • Rank
    Member

Converted

  • Gender
    Undisclosed

Recent Profile Visitors

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

  1. I like this topic. I've edited your post a little to include some things. I for one would like to know where VM XML lives for example, and if the only things needed to restore VMs are the vDisks and XML.
  2. Yes, please! It would mean not having to jump to XML for a virtualized ESXi install.
  3. So I just checked this after updating to 6.9.1 Two 9207-8i's on P16 firmware. All my SSDs TRIM fine, except for my 850 Evo. Something something zeros after discard? I remember reading this as a reason for issues with Samsung drives, can't find specifics at the moment though. Moved it to one of the motherboard ports and it TRIMs fine again. Haven't tried with P20 fw as of yet.
  4. I figured I should post on AMP about this, except for the big warning on your Git page. I'll go do that, see what they come back with.
  5. Second issue for you Cornelious: I really love the idea of sticky backups. To test this, I created a trigger to run a backup every 10 minutes from within the Minecraft instance under "Schedule". I limited the backups to 12 under "Configuration > Backup limits" (the size options were left extremely large so as not to be a factor) I let the game run to create a couple of automatic backups I created a manual backup called "STARRED" with a description, and Sticky = On. Any ideas as to why my sticky backup is still getting deleted? I
  6. That was it! Thank you, it wasn't immediately obvious that "instance" and "application" are treated differently.
  7. Hi! I'm using your container (thank you!) pretty successfully, except for one weird issue: The main instances page doesn't seem to be able to send start/stop commands to the individual instancs. (other commands seem to work though: I can change port bindings, for example) I had a Minecraft instance set to autostart after 10 seconds. This status is reflected in the main menu, but if I actually open the instance, it's still off. Likewise if I manually start/stop from the main page - when I manage the instance to check, its status hasn't changed. I don't see a
  8. As to your first problem, this is a known issue with RC2. Manually spin up your drives (even if they're already spun up, from what I understand) by clicking the little status LED symbol on the left. The temperatures should display correctly after this.
  9. I completely forgot you can do this through the UI now. Ignore my first post.
  10. Just to be clear here: Pinned != isolated. They're different things. Pinned just means a CPU core that a VM can use, but anything else can also use that core as well if it's free. This is done by pinning the CPU core in the GUI. Isolating a CPU core means unRAID doesn't touch it. This is done by appending "isolcpus="x,y,z" to your syslinux config on Flash > Main. If you want to fully isolate the cores so that only the VM uses them, then you'll need to change your syslinux config from this: To this (for example):
  11. Valid points all. I hadn't considered the fact that no-one has written a plug-in for it yet. That likely does say something to all this. And you're right; I hadn't considered that some people use disk shares/mappings either. I guess we're at the same point: Feature request made, wait and see.
  12. I have to disagree. unRAID is being billed as an appliance that gives you enterprise features for less money, and does lots of things without requiring as much user knowledge as a home-spun setup using a more common distro. If you're saying a regular user should be totally ok with using the terminal zero a drive with dd, then you're kind of missing the point. I could actually see this saving time, in the sense that a user kicks off the drain operation, then comes back a day or two later, can restart the array at a more convenient time, and yank the drive. Ho
  13. I'm not ephigenie, but I liked the idea, so I'll give my two cents on it, for what it's worth: Maybe something like a broad strokes roadmap. Nothing too concrete, but even a post with headings like: Features being worked on for the next major/minor release (multiple cache pools) Bugs being squashed for the next major/minor release (SSD write amplification) Future possibilities currently under investigation (ZFS) You could make the forum visible to community developers only. Or if you're feeling particularly transparent, forum members with enough pos
  14. This is why I don't comment much; I manage to completely miss the obvious most of the time. Reasoning for not including drivers off the bat makes complete sense now, carry on.