Leaderboard

Popular Content

Showing content with the highest reputation since 05/19/22 in all areas

  1. LXC LXC is a well-known Linux container runtime that consists of tools, templates, and library and language bindings. It's pretty low level, very flexible and covers just about every containment feature supported by the upstream kernel. This plugin doesn't include the LXD provided CLI tool lxc! This allows you basically to run a isolated system with shared resources on CLI level (without a GUI) on Unraid which can be deployed in a matter of seconds and also allows you to destroy it quickly. Please keep in mind that if you have to set up everything manually after deploying the container eg: SSH access or a dedicated user account else than root ATTENTION: This plugin is currently in development and features will be added over time. LIMITATIONS: Distributions which use systemd (Ubuntu, Debian Bookworm+,...) will not work or not work properly currently. Install LXC from the CA App: Go to the Settings tab in Unraid an click on "LXC" Enable the LXC service, select the default storage path for your images (this path will be created if it doesn't exist and it always needs to have a trailing / ) and click on "Update": ATTENTION: - It is strongly recommended that you are using a real path like "/mnt/cache/lxc/" or "/mnt/diskX/lxc/" instead of a FUSE "/mnt/user/lxc/" to avoid slowing down the entire system when performing heavy I/O operations in the container(s) and to avoid issues when the Mover wants to move data from a container which is currently running. - It is also strongly recommended to not share this path over NFS or SMB because if the permissions are messed up the container won't start anymore and to avoid data loss in the container(s)! - Never run New Permissions from the Unraid Tools menu on this directory because you will basically destroy your container(s)! Now you can see the newly created directory in your Shares tab in Unraid, if you are using a real path (what is strongly recommended) weather it's on the Cache or Array it should be fine to leave the Use Cache setting at No because the Mover won't touch this directory if it's set to No: Now you will see LXC appearing in Unraid, click on it to navigate to it Click on "Add Container" to add a container: On the next page you can specify the Container Name, the Distribution, Release, MAC Address and if Autostart should be enabled for the container, click on "Create": You can get a full list of Distributions and Releases to choose from here The MAC Address will be generated randomly every time, you can change it if you need specific one. The Autostart checkbox let's you choose if the container should start up when the Array or LXC service is started or not (can be changed later). In the next popup you will see information about the installation status from the container (don't close this window until you see the "Done" button) : After clicking on "Done" and "Done" in the previous window you will be greeted with this screen on the LXC page, to start the container click on "Start": If you want to disable the Autostart from the container click on "Disable" and the button will change to "Enable", click on "Enable" to enable it again. After starting the container you will see several information (assigned CPUs, Memory usage, IP Address) about the container itself: By clicking on the container name you will get the storage location from your configuration file from this container and the config file contents itself: For further information on the configuration file see here Now you can attach to the started container by clicking the Terminal symbol in the top right corner from Unraid and typing in lxc-attach CONTAINERNAME /bin/bash (in this case lxc-attach DebianLXC /bin/bash): You can of course also connect to the container without /bin/bash but it is always recommended to connect to the shell that you prefer Now you will see that the terminal changed the hostname to the containers name this means that you are now successfully attached to the shell from the container and the container is ready to use. I recommend to always do a update from the packages first, for Debian based container run this command (apt-get update && apt-get upgrade): Please keep in mind that this container is pretty much empty and nothing else than the basic tools are installed, so you have to install nano, vi, openssh-server,.. yourself. To install the SSH Server (for Debian based containers) see the second post.
    12 points
  2. OK. Not that I use this plugin, but I have forked it so that the logs and the context menus appear. I have temporarily removed the dashboard part of things until I get more time to look at it's display aberrations. Going forward, so long as explicit directions are made as to how to replicate issues on 6.10 I will attempt to fix, but no guarantees will be made, and my goal here is not to continue development on this plugin, but to simply keep it in the same rough state as it was left in when the author stopped development. You will need to uninstall the version from Guild Darts and then reinstall the forked version. I would suggest making a backup of the folder.json file within /config/plugins/docker.folder on the flash drive. If you don't do this, then you will need to recreate your folders.
    6 points
  3. I would recommend anyone running a HP MicroServer Gen8 to not update for now, there have been multiple cases of filesystem corruption after updating, with both XFS and btrfs, looks like the hardware doesn't get along with the new kernel, not clear if it's all models in general or just some specific BIOS/CPU combos, so if anyone updated without issues please post here. Edit to add: The ones I found so far were all using Xeon CPUs with Intel VT-D (IOMMU) enable, I have a suspicion the problem is related to this, it's causing some kind of kernel memory corruption so if you're running one of these with a Pentium or I3 CPU (or a Xeon with VT-D disable) you might be OK. See here for latest update on this: https://forums.unraid.net/topic/123620-unraid-os-version-6100-available/?do=findComment&comment=1129501
    5 points
  4. Install SSH Server in Debian based containers: Method 1 (recommended) : Attach to the container with "lxc-attach DebianLXC /bin/bash" (replace DebianLXC with your container name) : I would first recommend that you add a password for the user root, to do so enter "passwd" and enter your preferred root password two times (there is nothing displayed while typing) : Now Create a user with the command "useradd -m debian -s /bin/bash" (in this case the newly created username is "debian") : In the next step we will create a password for the user "debian" with the command "passwd debian" (replace "debian" with your preferred username) type in the password two times like above for the root user: Now install the openssh-server with "apt-get -y install openssh-server": After it successfully installed you can close the terminal window from the LXC container, connect via SSH to the container via Putty or your preferred SSH client through the IP from your container and the username "debian" and the password set for the user "debian" (in this example we will connect through a Linux shell with the command "ssh debian@10.0.0.237" you see the IP address in the LXC tab in Unraid) : Now you are connected through SSH with the user "debian" to your LXC container. Method 2 (not recommended - root connection) : Attach to the container with "lxc-attach DebianLXC /bin/bash" (replace DebianLXC with your container name): I would first recommend that you add a password for the user root, to do so enter "passwd" and enter your preferred root password two times (there is nothing displayed while typing) : Now install the openssh-server with "apt-get -y install openssh-server": Now issue the command: "sed -i "/#PermitRootLogin prohibit-password/c\PermitRootLogin yes" /etc/ssh/sshd_config" (this will basically change your SSH configuration file so that you can login with the root account through SSH) : Restart the sshd service with the command "systemctl restart sshd" to apply the new settings: After that you can close the terminal window from the LXC container, connect via SSH to the container via Putty or your preferred SSH client through the IP from your container and the username "root" and the password set for the "root" user (in this example we will connect through a Linux shell with the command "ssh root@10.0.0.237" you see the IP address in the LXC tab in Unraid) : Now you see that you are connected through SSH with the user "root" to your LXC container.
    4 points
  5. The amount of brave people without password for the root account is scary.
    4 points
  6. OK we figured it out. There was a bug in 6.9.2 that allowed you to use https://servername.local even though it was not valid for the hash.unraid.net certificate the server was configured to use. And since self-signed certificates also throw errors the browser probably didn't make it clear exactly which error you were accepting. So it would have been tough for you to know that the system was misconfigured in 6.9.2. We are going to tweak the upgrade process so that anyone upgrading from 6.9.2 with USE_SSL=auto will change to USE_SSL=yes in 6.10.0. That will eliminate this problem, and put users in control of whether they want the more secure/restrictive USE_SSL=auto setting.
    4 points
  7. Refer to Summary of New Features for an overview of changes since version 6.9. To upgrade: First create a backup of your USB flash boot device: Main/Flash/Flash Backup If you are running any 6.4 or later release, click 'Check for Updates' on the Tools/Update OS page. If you are running a pre-6.4 release, click 'Check for Updates' on the Plugins page. If the above doesn't work, navigate to Plugins/Install Plugin, select/copy/paste this plugin URL and click Install: https://unraid-dl.sfo2.cdn.digitaloceanspaces.com/stable/unRAIDServer.plg Bugs: If you discover a bug or other issue in this release, please open a Stable Releases Bug Report. Credits Special thanks to all our beta testers and especially: @bonienl for his continued refinement and updating of the Dynamix webGUI. @Squid for continued refinement of Community Apps and associated feed. @dlandon for continued refinement of Unassigned Devices plugin and patience as we change things under the hood. @ich777 for assistance and passing on knowledge of Linux kernel config changes to support third party drivers and other kernel-related functionality via plugins. @SimonF for refinements to System Devices page and other webGUI improvements. @thohell for an extra set of eyes looking at md/unraid driver and for work-in-progress of adding changes to support multiple Unraid arrays. @JorgeB for rigorous testing of storage subsystem
    3 points
  8. 3 points
  9. I guess that you can adjust most of the settings through some trickery in Unraid as well. For any fixes or incompatibility issues however, you will be relying on Unraid/Limetech to update the corresponding components of their system. And from what I read, it can be a hazzle to get TimeMachine up and running reliably as is. Therefore I think there is a certain advantage of running TimeMachine as a Docker image. The docker image used (https://github.com/mbentley/docker-timemachine) is in active development and quick to fix issues. The focus of that project is clear - TimeMachine and nothing but TimeMachine. I have been using this solution for a couple of months and it has been rock solid.
    3 points
  10. I have never had luck using the updater. I recommend following the manual update instructions in post 1; they’ve worked for me for… many iterations.
    3 points
  11. 3 points
  12. VM's are functionally the same as standalone computers from the user standpoint. What you are asking is a function of joining the machine to a windows server domain controller, so that is how you would need to do it with VM's as well.
    3 points
  13. Don't forget to right click on the container -> console and run ` yarn database:setup ` after the rest of the setup. Thanks for the guide looking forward to checking this out!
    3 points
  14. The context is fixed. Feel free to fork https://github.com/Squidly271/docker.folder
    3 points
  15. I fixed it by running the New Permissions tool on the affected folders You can also add this script to user scripts and run it to be more specific on folders instead of shares/disks. Remember to add the path to your folder #!/bin/sh for dir in "/mnt/user/!!you folder path here!!" do echo $dir chmod -R ug+rw,ug+X,o-rwx $dir chown -R nobody:users $dir done
    3 points
  16. Everybody - this thread is meant for comments and simple questions. If you need support, please open a new thread under General Support and include your diagnostics (from Tools -> Diagnostics). It would also be helpful if you can say what version you upgraded from.
    3 points
  17. Or want to keep an absent minded moment from removing the wrong drive, or have kids, etc. It's a very good idea to keep hot swap drives locked, it's not like they are going to be moved that often, and if they are because you are using one of the bays to do backups that you pull, even more reason to lock the rest of the array drives in place. I'd also consider putting a piece of tape on each bay drive slider with the current last 4 serial on it. Makes life less stressful when a drive fails.
    3 points
  18. -Upgraded ✅ -Cert upgraded ✅ make sure you add to pfsense (Services > DNS Resolver > General Settings > Custom Options) private-domain: "myunraid.net" -if you can't access the GUI after cert upgrade. 1 ssh root@SERVERIP 2 use_ssl no then you can log in using the normal ip way. -Root Shares ✅ -File Manager ✅ Thank you for all the hard work, everything is working GUCCI. Disks are finally sleeping!😴😇🤫
    3 points
  19. This thread is meant to provide support for issues related to the Time Machine Application Template view on GitHub
    2 points
  20. I figured it out. There seems to be an issue with how the WebGUI matches usernames. I have a user called "rootshare" which exposes all shares via a custom smb config. When this user account exists, unraid's WebUI attempts to match the password for "rootshare" instead of "root". Using the password for the "rootshare" user then works for the "root" user. Seems like an oversight? (username.startsWith() / username.Contains() or something?)
    2 points
  21. Since the 6.10.0 update, logs are only displayed in black and white via the logterminal pop-up window. Even though this might improve the readability at first glance, the different coloring of info, warn and error messages have unfortunately also disappeared with this change. This made it very easy to see if something is wrong or to filter out relevant info. For me and probably many others, this was a crucial feature that I now miss very much. Now all I see is a pile of text that becomes even more unreadable on longer lines due to the larger font with line breaks. If you go to Tools/System log you can see what it looked like before.
    2 points
  22. I just made the jump from controller version 5.14.23 all the way to 7.1.66 in one step. The upgrade went smoothly and everything came back online. It will take me a while to figure out where everything is now as things are organized differently. There was no compelling reason to do the upgrade other than fear of being left too far behind and making a future upgrade more difficult.
    2 points
  23. Does anyone know if this would be fixed in later versions or is disabling this the proper thing to do, seems like a band-aid. Im asking because i don't think its ready for me to upgrade, just too many various issues all over here and reddit. Are the devs making a list of these issues to address or are we suppose to dive in, update and fix whatever arise's as we find it? Sorry this is not meant to be condescending i just don't know how long i should wait it out or if now is as good as it gets.
    2 points
  24. Already changed the first post, I haven't been able to test everything so far because there are a lot of images... I can so far confirm that Homeassistant Core is working fine, Docker is working fine (with containers who doesn't need privileged rights), I've also made a container that uses noVNC in conjunction with TurboVNC to get a Desktop environment through a browser (xrdp should also work with a few tweaks from what I know).
    2 points
  25. Not yet clear what activities, usually issues start after a few hours of normal use, docker image or any other btrfs filesystem are usually the first to go since they are very susceptible to memory corruption issues, if the pools are btrfs run a scrub, parity check for the array if xfs, though if errors are detected basically you can only correct them, unless you have pre-existing checksums, also note that while some corruption is possible it's not certain, in at least one case btrfs detected some corruption but after disabling VT-d and running scrub no more corruption was found.
    2 points
  26. Hallo, @i-B4se dank dem Workaround konnte ich jetzt auch von 6.9.2 auf 6.10.1 hochziehen 🙂 und mein deConz funktioniert weiter in HA Danke für den Tip
    2 points
  27. You'd want @ich777 not me for helping with the nVidia driver plugin.
    2 points
  28. I can reproduce the issue that udev creates interfaces with duplicated MAC addresses, it is under investigation whether this is particular to the udev version used, or kernel version or network driver.
    2 points
  29. Where is the Changelog, Thread, Blog for 6.10.1?
    2 points
  30. This docker template was created based on an already available official docker image Website: https://www.tinymediamanager.org/ GitLab: https://gitlab.com/tinyMediaManager/tinyMediaManager DockerHub: https://hub.docker.com/r/tinymediamanager/tinymediamanager Documentation: https://www.tinymediamanager.org/docs/ My Repository: https://github.com/SmartPhoneLover/unraid-docker-templates DESCRIPTION tinyMediaManager is a full featured media manager to organize and clean up your media library. It is designed to allow you to create/view/edit the metadata, artwork and file structure for your media files used by Kodi (formerly XBMC), Plex, MediaPortal, Emby, Jellyfin and other compatible media center software. Features: - Automatic updates - GUI and command line interfaces - Metadata scrapers for IMDb, TheMovieDb, TVDb, OFDb, Moviemeter, Trakt and more - Artwork downloaders for TheMovieDb, TVDb and FanArt.tv - Trailer downloads from TheMovieDb and HD-Trailers.net - Subtitles downloaded from OpenSubtitles.org - Manually edit any metadata fields with ease - Automatic file renaming according to any user-defined format - Powerful search features with custom filters and sorting - Saves everything in .nfo files automatically recognized by Kodi and most other media centers - Technical metadata like codecs, duration and resolution extracted from each media file - Group movies into sets with special artwork common to all movies in it - Import TV show collections no matter the file organization style used VERSION 1.0 (2022-05-21) If you are going to report a bug or request something to be added/modified, please, take into consideration that I will only be able to apply changes for the work I own only. For example, if I create a docker template for an already existing docker image (not created by me), I won't be able to do more for that image than forward your report or request to the owner of the project.
    2 points
  31. Posting this here in the hope that it assists someone in the future. I host my instance of HomeAssistant in a VM on unRAID. I have recently purchased a ConBee II USB-Gateway so I can add Zigbee devices. I added the USB using the unRAID VM GUI, like I imagine most would, by just checking the tick box next to the device. This didn't work. While Home Assistant found the device, the integration would not add (there were communication errors). The trick was to add the device as a serial-usb device. AFAIK you cannot do this via the GUI. So I added the following code to my VM config: <serial type='dev'> <source path='/dev/serial/by-id/<yourusbid>'/> <target type='usb-serial' port='1'> <model name='usb-serial'/> </target> <alias name='serial1'/> <address type='usb' bus='0' port='4'/> </serial> I was then able to add the integration easily. Interestingly, it didn't auto discover, but that's just an aside. Note, <yourusbid> can be found via the command line - it contains the device serial so its not to be posted.
    2 points
  32. AFAIK it's only the Microserver Gen8, many people running a Xeon with VT-d enable, including multiple models myself without issues, pretty sure I've also seen other users with different model HP servers running it without problems, of course can't guarantee there's won't be other models affected but seems unlikely, can also add that the issues start immediately after updating, since at least -rc4, so anyone affected would notice after a couple of hours or so, and if it was a more general issue we would have seen a lot of forum posts about it.
    2 points
  33. Actually not true... pre-6.10 the 'udev' subsystem was started very early. This let us look for which device was assigned to the flash by looking at: /dev/disk/by-label/UNRAID which is a symlink which points to a partition, such as 'sda1' or 'sda2' In 6.10 we have to find the flash device before starting 'udev', so we switch to using 'blkid' to find a device with label "UNRAID". However the code only checks partition 1 label on each device because I've never seen a case where anything other than partition 1 was ever used. We will add code to check partitions 1, 2, 3, and 4 in the 6.10.1 release. To get your flash to boot now, you will have to reformat and make sure partition 1 is the boot partition with the UNRAID label.
    2 points
  34. I added a script to enable FTP on boot, seems to be working so far. Enabled FTP Server under "Settings, FTP Server". Check the system log and read the line that Enabled the FTP Server, for mine it was "/usr/local/emhttp/plugins/dynamix/scripts/ftpusers '1' 'root'" Added a new script using the User Scripts plugin, and added that data, and set it to run at "At Startup of Array"
    2 points
  35. Besten Dank, das hat funktioniert. ❤️ Doch, so ist es. Hier nochmal meine "rangehensweise" 1. HA-VM stoppen 2. Den Haken für den Stick im VM GUI entfernen: 3. ID von deinem Conbee mittels Unraid-Console: ls /dev/serial/by-id/ So sieht es bei MIR aus 4. Bearbeitest du deine VM mittels "XML-Ansicht" 5. Dann fügst du folgende Zeilen ein. Einfach unter </memballoon> Also zeimlich weit unten <serial type='dev'> <source path='/dev/serial/by-id/<HierDeineCONBEEID>'/> <target type='usb-serial' port='1'> <model name='usb-serial'/> </target> <alias name='serial1'/> <address type='usb' bus='0' port='4'/> </serial> Dann deine Conbee ID einfügen die du per Console ausgelesen hast OHNE DIE < > und OHNE @ So sieht das ganze bei MIR aus <serial type='dev'> <source path='/dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2417249-if00'/> <target type='usb-serial' port='1'> <model name='usb-serial'/> </target> <alias name='serial1'/> <address type='usb' bus='0' port='4'/> </serial> 6. Die VM starten. Du musst nur bezüglich deinen Addons in HA schauen. Ich nutze Deconz und da musste ich einfach einen neuen Port auswählen und alles läuft wieder.
    2 points
  36. This is already planned but not yet implemented.
    2 points
  37. It's been present in the OS for quite a while now, but YMMV. Known issue
    2 points
  38. It looks like you didn't unmount the disk before you physically removed it. If the mount button shows a not 'Unmount', you'll need to reboot to clear it up. Don't just pull the disk out and expect it to work when you plug it back in.
    2 points
  39. @f.lim & @BennyD & @BSAVAG3 I changed the default path in the template now to /mnt/user/appdata/vrising
    2 points
  40. I also had a couple of broken containers. I would use WinSCP to go into the folders for those containers in appdata, and see if there are any files that have stricter permissions than other. For example some which are owned by "root" while the others is owned by other users. I don't know why upgrading would break this though.
    2 points
  41. @ich777 Good news, seems like problem was related to my Unraid version as well. Here's what I've done. - Updated Unraid to 6.10.0 - Rebooted - V Rising still experiencing the same issue - Removed the container and deleted appdata directory - Pulled fresh from CA and followed @BennyD's solution by remapping /mnt/cache/ to /mnt/user/ It's now working! Thanks for your help @ich777 & @BennyD
    2 points
  42. Hi folks, after spending a fair bit of time hardening my SMB configuration I figured I'd write a quick guide on what I consider the best settings for the security of an SMB server running on Unraid 6.9.2. First, before we get into SMB settings, you may also want to consider hardening the data while it is at rest by specifying an encrypted file-system type for your array (although this isn't a share specific option). For SMB, first set the SMB settings available: I've settled on this as the following block is what I consider to be a hardened SMB configuration for a standalone server that is not domain joined or using Kerberos authentication: server min protocol = SMB3_11 client ipc min protocol = SMB3_11 client signing = mandatory server signing = mandatory client ipc signing = mandatory client NTLMv2 auth = yes smb encrypt = required restrict anonymous = 2 null passwords = No raw NTLMv2 auth = no This configuration block is to be entered into the SMB extras configuration section of the SMB settings page. These settings will break compatibility with legacy clients, but when I say legacy I'm talking like Windows Server 2003/XP. Windows 10+ clients should work without issue as they all support (but are not necessarily configured to REQUIRE) these security features. These settings force the following security options: All communications must occur via SMB v3.1.1 All communications force the use of signing for communications NTLMv2 authentication is required, LanMan authentication is implicitly disabled. All communications must be encrypted Anonymous access is disabled Null session access is disabled NTLMSSP is required for all NTLMv2 authentication attempts In addition, the following security settings are configured for each available share: Also ensure that you create a non-root user to access the shares with and that all accounts use strong passwords (Ideally 12+ complex characters). Finally, a couple of things to note: If you read the release notes for Unraid 6.9.2, you'll see that Unraid uses samba: version 4.12.14. This is extremely important. If you, like me, google SMB configuration settings you'll eventually come across the documentation for the current version of SMB. But! Unraid is not running the latest version, and that's extremely important. The correct documentation to follow is for the 4.12 branch of Samba and the configuration options are significantly different, enough that a valid config for 4.15 will not work for 4.12. With "null passwords = No" you must enable Secure or Private security modes on each exported Unraid share - guest access won't work. There is currently no way to add per-share custom smb.conf settings. So either the server gets hardened or it does not. Do not apply a [share_name] tag as it will not work. It is not possible to specify `client smb3 encryption algorithms` in version 4.12.x of Samba. Kerberos authentication and domain authentication may be preferable in other circumstances, in this instance, additional hardening options may be considered. If you, like me, use VLC media player on mobile devices, you may find that SMBv3 with encryption makes the host inaccessible on IOS devices. The VLC team is aware of this and there is a fix available if you have the bleeding edge/development version of the app, but not if you download the current store version (last I checked, the fix hadn't been released). Should work fine with Android/Windows VLC. If you have any suggestions for other options that I have not included here or that you think are a mistake. Please let me know and I'd be most happy to look into them and adjust. Some other quick hardening suggestions for unraid hardening in general. Disable whatever services you don't need. In my case, that means I: Disable NFS Disable FTP Disable 'Start APC UPS daemon' If you enable Syslog, also enable NTP and configure it. Disable Docker Quick note on docker, having the services enabled allows for 'ip forwarding' which could, in theory, be used to route traffic via the host to bypass firewall rules (depending on your network toplogy obviously) Hope that helps someone else out there. Cheers!
    2 points
  43. Unraid 6.10 is out, could you please update the hardening for samba 4.15? Thanks
    2 points
  44. FYI: Wer das Plugin "Unassigned Devices" installiert hat und auf das heute erschienene Unraid 6.10 umstellen wird, sollte unbedingt neben den Unraid Update Hinweisen vorab den Beitrag zum Update des Unassigned Devices Plugin lesen. Dies vor allen Dingen wenn man mit NVMe oder SSD Devices im Unassigned Devices Plugin arbeitet - wie ich. Üblicherweise aktualisiert man vor einem Upgrade von Unraid die Plugins und Container. Leider fiel eine kritische Änderung am Unassigned Devices Plugin mit dem Release von Unraid 6.10 zusammen. Beides wurde heute zeitgleich veröffentlicht. Beim Start des aktualisierten Unraid 6.10 können NVMe, SSD Devices durch UD neue Bezeichner erhalten, was unter Umständen Auswirkungen auf die Docker und KVM Subsysteme haben kann. In meinem Fall wurden tatsächlich Unassigned Devices unter neuen Bezeichnern aufgeführt und ich musste das Docker Subsystem neu konfigurieren (Passthru Devices, etc.). Beim KVM Subsystem hatte ich vor einiger Zeit auf "bus:device" statt "dev/by-id" umgestellt. Deshalb wurde ich im Falle von VMs vor notwendigen Änderungen verschont. Ich persönlich finde diesen zeitlichen Zusammenhang für extrem unglücklich. Wer schon etwas tiefer in Unraid eingetaucht ist, der wird das sicherlich schnell beheben können. Wer aber ohne weitere Nachforschung die Update Knöpfe drückt, könnte beim nächsten Start überrascht werden. Also unbedingt lesen.
    2 points
  45. Very nice work guys. When are we going to be able to ditch using a USB flash drive for unraid, and move over to something more reliable as a boot device? It also makes it a royal pain to virtualise unraid (i know this isn't technically supported)
    2 points
  46. Great work guys. When can we see an RC for 6.11 ? 😁
    2 points
  47. Has the plan for VM snapshots gone away?
    2 points