thany

Members
  • Content count

    71
  • Joined

  • Last visited

Community Reputation

0 Neutral

About thany

  • Rank
    Advanced Member

Converted

  • Gender
    Undisclosed
  1. Mark VM disk as SSD?

    By now I'm running unraid 6.4.0 and I don't think there's an option to mark a virtual disk as SSD yet. And I also don't see the hypervisor passing on the "SSD or HDD" flag from the physical disks onto the VM. Any chance this might still happen? Maybe I'm thinking too simplistically, but isn't this dead-easy to do? The flag is coming from the BIOS/UEFI, afaik, so if the hypervisor can read that flag, can't it just pass it on into the virtual BIOS, so that the flag ends up in the guest VM? So that the guest OS will optimize itself for SSD usage, rather than HDD usage? Or is it way more complicated?
  2. [Plug-In] Community Applications

    That's the thing. It won't happen again just by doing the same thing. Can you think of *any* reason whatsoever why it might crash the server? Maybe I can diagnose it from that angle.
  3. [Support] Linuxserver.io - Transmission

    Ah, I think you're right Well if nothing else, it's quite hard for me to confirm I've got the latest version. In the client, I'm seeing 2.92 (14714), but I can't find that version number anywhere on the docker hub or the github page, or in this thread. So I feel uncertain whether I'm *actually* up-to-date... /edit When I say "the client", I mean Transmission Remote GUI 5.0.1.
  4. [Plug-In] Community Applications

    I just clicked the Apps tab and my server crashed. It just looked like it was taking a long time, and after a few minutes I just hit F5 and it instantly worked, with a server uptime of 1 minute. It can't be a coincidence - I literally only clicked the Apps tab. Nothing more. And then, crash. Reboot. I'm not sure where to go for logs on what actually happened. Any ideas? As for my server: I'm at 6.4.0. I think everything is up to date.
  5. [Support] Linuxserver.io - Transmission

    I got a notification from unraid there's an update to transmission, but when I go into the Docker tab and hit "check for updates", it says transmission is already up-to-date. I think it hasn't updated for a good number of weeks now, and usually there's an update every week or two... Any ideas?
  6. Mark VM disk as SSD?

    I don't understand your reply. I didn't ask about sparse disk files (mine are thick provisioned), and I didn't ask how to enable trim on WIndows (this happens automatically on detected SSDs). So let me rephrase: How can I tell the hypervisor to mark a disk as SSD so that it'll pass that on to the guest, so that the guest will detect a disk as being SSD instead of HDD?
  7. I've just realized something. So I got unRAID running on an SSD, and I've got a couple of VMs running as well. One of the VMs is a Windows 10 installation, and no problems there as it runs beautifully. However, I realized at one point that it doesn't see the installation disk as an SSD, even though unRAID hosts the disk image on the SSD. So apparently unRAID doesn't pass that information on to the guest. So I guess that's a viable feature request. In the mean time, is there a way to have unRAID tell the guest OS which drive is an SSD? Essentially marking a disk image as SSD? VirtualBox can do this as well, and I believe VMware too. When checking their little checkbox, the guest OS will see the disk as being solid state. And why? Simple. So the guest OS doesn't go out of its way to optimize the file layout for a HDD while idling. Windpows will happily start defragging your disks if they are HDDs. For SSD it does different, much lighter optimizations. And we all know that defragging an SSD will only degrade its performance. Good to know: I'm running unRAID 6.3.5, all plugins are up-to-date. Just in case this matters, the guest OS (Windows 10 in my case) is fully up-to-date as well.
  8. [support] Capt.Insano's Docker Repository

    Good post! Any word about Deluge?
  9. Those two additional scenarios are highly unlikely. 1) My UnRAID box never takes more than a minute or so to reboot. So shutting down is a matter of seconds. 2) I don't have spinning harddisks So anyway, what is the reason UnRAID by default throws away logs? Especially in case of an unclean shutdown, it should be smart enough not to clean out the logs!
  10. Docker appdata files not accessible

    How would you recommend I set it up then? I'm not sure what to enter where, you see...
  11. I can imagine a very small amount, like 1GB, should suffice when unraid is used purely as a fileserver. I personally have got 16GB installed, because I'm running a few VMs and a couple of dockers. I also like the idea of filecache in memory, and a bit of overhead in case when something really needs it, has never hurt anyone. Also, memory is quite cheap, so why not.
  12. Do you use spin up groups?

    I don't use them. My unraid box only has SSD's anyway. Spinning up/down is purely a legacy function from my perspective. On spinning harddisks, this is something that can be automated perfectly. Power management should be able to handle spinning disks up/down when it makes sense. There's absolutely no need for anyone to configure this manually, unless in case of a control freak. Better not clutter unraid with unneccesary functions, iyam.
  13. Got my Transmission docker running absolutely fine. Except for the config. Somewhere along its life, the appdata files have become unreadable over SMB for me. The docker itself seems to be able to read them (I think) but is unable to persist configuration - possibly due to the same permissions problem. Through the web interface, I can read the files (which is fiddly) but I can't see how to upload and overwrite files. Obviously, I already tried stopping the docker, to make sure it isn't locking the files for exclusive use. 1) How can I force unraid to make the files readable/writable? 2) How can I prevent permissions from getting broken again in the future? 2a) Or alternatively, how can I see why & when permissions where altered, and/or by whom?
  14. Apparently, my unraid box recovered from an unexpected shutdown, as if someone cut the power lead (which noone did). This could mean two things. 1. Unlikey, but a power outage may have lasted long enough to drain the UPS, and unraid didn't honour the shutdown settings while running on UPS battery. 2. More likely, the server crashed itself and got itself to reboot automatically. But crashed because of what...? In either case, I don't know where to find out more. I can't find a log for the UPS. I would like to know a date+time of the last outage, or the last outage X seconds ago. Either would be helpful, but I don't know where to get this information. It's an APC Back-UPS ES 550G, connected via USB. I also can't find information on what happened before the unexpected reboot. The server log seems to have been cleared during startup, which is extremely bad practice if this was deliberate. The damage (if any) is already done, so enabling persistent logs is of no use now. More so because I have no way of knowing how to reproduce the problem - I don't even know where to start, it could be literally anything, so far. At any rate, where can I find logging information from before the crash? PS, the reason scenario 2 is more likely, is because other UPS's in the house didn't indicate an outage either, although I'm not sure how good they are at reporting them. My NAS survived the outage if there was one, so that's an indication. I wasn't around to experience it myself, unfortunately.
  15. Sparklyballs' Repo- Sparkly Stuff In Here

    Even so, the default password must be known with *someone*, *somewhere*...

Copyright © 2005-2017 Lime Technology, Inc. unRAIDĀ® is a registered trademark of Lime Technology, Inc.