T0a

Members
  • Posts

    149
  • Joined

  • Last visited

Everything posted by T0a

  1. I see, then I had the wrong suspect here, sry. Should have read the code in more depth to get a better grasp. Okay, any ideas what could be improved to prevent the wake up then? Do you think disabling of checking the size when PASS THRU is enabled would be a good solution? People might want to see the disk usage even if they pass-through the drive. Can you point me to the code part? Would it be an option to make it optional to show the "Unassigned Devices" section in the main tab? For the time being I removed the "Unassigned Devices" section from the main tab by editing the header of "UnassignedDevices.page". The change will be reverted when I update the plugin though.
  2. I got an external USB hard drive (WD Elements). When I put it to sleep via 'hdparm -y /dev/sdb' and click on the main tab (or refresh it), the 'Unassigned Devices' section refreshes (takes a few seconds) and wakes up the external drive again. I can reproduce this, pinning the wake up of the drive exactly to the time refreshing the main tab. * The drive is formatted with ZFS * "PASS THRU" is enabled * Auto Mount USB Devices set to No Why does the plugin wake up the drive? After troubleshooting the issued rescan command on refresh here (/sbin/udevadm trigger --action=change 2>&1) wakes up the drive. Can I exclude the drive from the plugin without removing the plugin? I don't want the plugin to interact with this respective drive. Is it possible to disable rescan on page refresh? Can I remove the "Unassigned devices" section from the main tab only displaying it in the plugin section? Other solutions?
  3. Playing around with ZFS in Unraid the for a few days now. Thanks for keeping the Plugin up-to-date! I created a single zpool on an external USB disk using the commands mentioned in the first post. The device name changed however from 'sdb' to 'sdg' and the pool was not loaded automatically any more. Thus, I exported the pool and imported the device via its unique UUID i.e (source) : root@server:~# zpool export extdrive root@server:~# zpool list -v no pools available root@server:~# zpool import -d /dev/disk/by-id extdrive root@server:~# zpool list -v NAME SIZE ALLOC FREE CKPOINT EXPANDSZ FRAG CAP DEDUP HEALTH ALTROOT extdrive 928G 139G 789G - - 0% 15% 1.00x ONLINE - usb-WD_Elements_25A2_575833314142354837365654-0:0 928G 139G 789G - - 0% 15.0% - ONLINE root@server:~# This makes sure the pool is loaded, even if the device name changed. For me it looks like it is recommended to create the pool using the unique UUIDs rather than device names. What do you guys think? Edit: Seems like it does not work well. After reboot another device name is assigned and despite the fact that the pool is mounted via UUID, commands like 'zpool list -v' stuck Edit2: Looks like that the "stuck" behaviour occurs, when the device labels changes (e.g. re-plug USB drive) while the pool is still loaded. Thus, I ended up doing the following via UD plugin: #!/bin/bash PATH=/usr/local/sbin:/usr/sbin:/sbin:/usr/local/bin:/usr/bin:/bin case $ACTION in 'ADD' ) ;; 'UNMOUNT' ) ;; 'REMOVE' ) ;; 'ERROR_MOUNT' ) DEST=/mnt/extdrive zpool import -d /dev/disk/by-id extdrive zfs mount -a if mountpoint -q $DEST; then rsync -a -v --delete a b 2>&1 [...] sync ud_backup_exit=$? if [ ${ud_backup_exit} -eq 0 ]; then echo "Completed UD backup" else echo "UD backup failed" fi else echo "Backup drive not mounted, exiting" exit 1 fi zfs umount /mnt/extdrive zpool export extdrive if mountpoint -q $MOUNTPOINT; then echo "Error while un-mounting ZFS drive" else echo "Device can be removed" fi ;; 'ERROR_UNMOUNT' ) ;; esac I assigned this script via the UD plugin and configured auto-mount for the device. Now I can plug in my ZFS USB device and remove it once the backup is finished. Using the "ERROR_MOUNT" state is kind of a hack. Would love to have the "ADD" state renamed to "MOUNTED". Then an additional state "ADD" would allow to just indicate the occurrence of new devices. Maybe also custom mount commands for the UD plugin would be cool for kind of scripting with ZFS drives. How do you guys handle such cases?
  4. Pretty cool post - will take some time to work me through. Wanted to post a comment after reading the first few paragraphs. I have a failover pihole setup in place utilizing keepalived. Two pihole instances, each on a separate Rpi. When one goes down, the floating IP switches in an instant to the other instance. You might want to check it out, so your family can browse the web while you work on your server.
  5. Good news, localization is coming with Unraid 6.9 (English Master). In this context, Limetech were looking for professional translators in Arabic, French, Mandarin and Spanish here. Let's see what is coming. Maybe we can add more languages with a community-driven approach in the future.
  6. * Do you access your VM from another device via VNC? * Have you tried a wired connection? * Have you tested other remote accessing software such as nomachine, splashtop or parsec? * Do you have the same bad experience when you plug in a monitor directly to your MB port and use an attached keyboard and mouse? * Does Windows recognize your UHD 630 in the device manager with correct drivers loaded? * Have you tried to download the latest UHD 630 drivers from Intels Website? They usually perform better than the one shipped with Windows.
  7. Unraid: 6.8.3 Component: Docker, UX Type of issue: cosmetic, minor 1. Using the update button from the context menu (see docker-update-0.png) does not open the "Are you sure" dialog window (see docker-update.png). However, when using the update button from the docker overview, the dialog window pops up just fine. 2. Once a docker update is available, the update entry in the context menu is placed first (see docker-update-0.png). Usually, there is the start entry (docker-update-2.png). From an UX perspective, reordering the entries in the list is misleading for the user. The user is used to have the start button placed first, he has the intention to start a stopped container, muscle memory kicks, he accidentally clicks on update. No dialog window warned him due to issue (1). Impact of this issue: Both issues in combination will cause accidental updates of docker containers. docker-update.png docker-update-0.png docker-update-2.png
  8. This sounds like some sort of reset bug with the graphics card. What graphics card are you using (AMD)? This would be cool as I don't own the hardware to try it myself. Have a look at this video. You need to do some sort of transfer here as you want to passthrough your Thunderbold controller instead of the USB controller. To briefly summarize: * Install VFIO PCIE Config plugin from the Apps store * The plugin should list your IOMMU groups and also show the connected devices such as your eGPU * Tick the Thunderbold controller that has the eGPU connected to its port. This will blacklist the whole controller from the host (make sure you don't tick the device with your Unraid flash drive. Otherwise you cannot boot anymore). You may need to reboot. * Add the thunderbold controller to your VM template as shown in the video linked above ** For troubleshooting please add the VM template XML and the issues that occur while starting the VM (if so) in your next post * When booted, make sure Windows uses the correct Thunderbold driver (Devices Manager) Using this method, we will rule out Unraid as the culprit as we blacklist the whole controller from the host. I'm curious if that works for you! Feel free to reach back, if you have any problems.
  9. Can you reference the source of your finding?
  10. Hi @Malaga, by passing through the eGPU i.e. ticking the device in the VM template, Unraid adds a hostdev section to your Windows 10 template. When you now turn off your device, it is no longer available to the host. But the hostdev section remains in your Windows 10 template. When you start the VM then, it will try to find the device (which is turned off) and throw an error. I think this is expected behaviour. However, sad to hear that Unraid does not recognize the device when you turn the eGPU on again resulting in a VM startup issue. I guess this is truly an issue with Unraid as both utilize KVM under the hood. Haven't used Proxmox myself, so please correct me if I'm wrong. Thunderbold support can still be considered as experimental in Unraid. Personally, I'm also interested in eGPU support. Some people where able to run Unraid as VM in Proxmox [1] - in case you are missing Unraid features in Proxmox. A solution might be passing through the Thunderbold controller to the the VM. Why? Search for posts in the forum where people have problems with passing through USB devices (crackling sounds with USB sound cards, etc.). The solution to all of these problems is to pass through the whole USB controller. That also allows them to use the USB hot plug feature in their VM. In your case, it could solve the issues you observe with Thunderbold. It's just a theory. You would be one of the first Unraid users experimenting with thunderbold passthrough. cheers [1] https://forums.unraid.net/topic/29679-guide-virtualizing-unraid-on-proxmox-31/
  11. Thanks @testdasifor your input. I got my hands on a used Xeon-2146G for about 200 Euro on Ebay - waiting for it to arrive. For all that are interested in a comparison: Intel Xeon E-2146G Benchmarks (Idle is around 32W and maximum power consumption hits just under 109W) Intel Core i3-9100F Benchmarks (Idle Power (Performance Mode): 31W, STH 70% Load: 75W, STH 100% Load: 92W) Note that I ruled out the Core i7 option, because it does not support ECC RAM.
  12. Had the same problem with the rclone plugin today. Can't figure out what might caused this. Maybe another plugin update? Anyway, the workaround mentioned here works for me. Hopefully, this issue will not occur in the future as it breaks my offsite backup. In the Plugins tab select 'remove' for rclone. Then go to the Apps tab and search for rclone and reinstall it there.
  13. I assume that your VM does not have the driver support for the IGD yet. Either do a Windows update after the passthrough via RDP - you can also open the device manager, click on your graphics adapter and update the driver. Or even better (because most of the time more up-to-date) install the latest driver from Intel via their website. After you where able to passthrough you might still not see any output on your monitor (depending on VM Bios, maschine type, host boot mode etc.). Then take a look at this thread. I assume you already blacklisted the IGD via the known methods (i.e. vfio pci stubbing, kernel parameter etc.).
  14. I was wrapping my head around this solution for a few days now. In order to use legacy passthrough "The IGD device must have a VGA ROM, either provided via the romfile option or loaded automatically through vfio (standard)." [0]. From my understanding the iGPU does not expose a ROM via PCI when the host is booted in UEFI mode [1]. Thus, you probably where able to access the VM via remote access with full GPU support, but got no signal from the port. The symptom in most cases is the following error "vfio-pci: Cannot read device rom at 0000:00:02.0 Device option ROM contents are probably invalid" in the VM log. Further telling that the legacy pass through mode [2] [3] is disabled. To solve the issue you need to manually provide a ROM as vfio is not able to provide it. In your case, your MB is capable to boot in legacy mode that allows to expose the ROM via PCI. Sadly, I cannot go this route for my UHD 630 as my MB does not support legacy mode (probably the standard in the future). In this case I think, you need either a second GPU (don't own one) to dump the IGD ROM or ask someone with the same CPU to dump the ROM for you in legacy mode (a collection of IGD ROMs would be really nice): Update 14-05-2020: Finally, found a working solution for UEFI only MB owners out there that works with legacy GVT-G passthrough and OMVF Bios [6,7]. Following, the setup that resolved the black screen issue with an Intel Core i3-8100 (UHD 630). The trick for me made the "vbios_gvt_uefi.rom" (see [7]; disclaimer: be warned to use a random ROM file from the Internet): Unraid Settings: - Host boots in UEFI (no legacy mode no CSM) - "Unraid OS" boot mode - Permit UEFI boot: Yes - Kernel parameter: append video=efifb:off,vesafb:off modprobe.blacklist=i2c_i801,i2c_smbus,snd_hda_intel,snd_hda_codec_hdmi,i915,drm,drm_kms_helper,i2c_algo_bit - VFIO-PCI Config to stub 00:02.0 VM Settings: - Windows 10 OS, OMVF Bios, i44fx-4.2, Hyper-V: Yes PCI Passthrough cheers, - stay home and don't eat bats [0] https://github.com/qemu/qemu/blob/master/docs/igd-assign.txt [1] https://www.redhat.com/archives/vfio-users/2018-April/msg00022.html [2] https://unraid.net/blog/unraid-server-os-6-3-released (Legacy and UTP mode) [3] https://vfio.blogspot.com/2016/07/intel-graphics-assignment.html [4] https://github.com/qemu/qemu/blob/master/docs/igd-assign.txt [5] https://forums.unraid.net/topic/83802-intel-gvt-g-support-multiple-virtual-intel-igpus-we-already-have-gvt-d/?tab=comments#comment-776192&searchlight=1 [6] https://www.reddit.com/r/VFIO/comments/fzje5x/no_output_from_igpu_when_passed_through/ [7] https://github.com/intel/gvt-linux/issues/23 PS: I think the IGD passthrough will be more popular in the future as services like Stadia and Geforce Now will emerge and improve. This allows casual gamer to enjoy a gaming session with their IGD driven Windows 10 VM. Also GVT-D is a thing [5]. However, I think we will not see this in Unraid in the near future since its focus are NAS features.
  15. Have you already searched the forum? More Information is required to help.
  16. Does maybe this thread help: Symptoms are the same
  17. Seems like a duplicate of
  18. Which device did you exactly checked (8086:1539 or 8086:10bc)? Note, when ticking the wrong one, Unraid has no access to this device such as the eth controller, which could be the cause for your ping issues. The "ACS Override" option shouldn't be required as the device you want to pass through resides in its own IOMMU group, right? In case you haven't changed something else, you should be fine with only removing the pcie-vfio config file from the flash drive as you did. Can you attach a monitor to your server? Then pls look for any printed issues. Also try to boot in "save mode" (with disabled plugins and a virgin sys config file). Does this work? I'm so thankful that limetech put their OS on a flash drive with easy access in case of such a problem.
  19. I think we need more information from you to troubleshoot this: IOMMU groups (Tools -> System Devices) OS you are trying to install The full VM template XML configuration Your current Unraid boot mode with parameter (Main->Flash->Syslinux Configuration) In order to pass-through the graphics card, you need to take it away from Unraid. How did you do this? Was your system able to boot when you blacklisted the card? From what I can tell your CPU has no integrated GPU and when your system does not boot when blacklisting the GTX 1080 you might not be able to pass it through to a VM.
  20. What Unraid version are you using? There is a new vfio-bind method in Unraid 6.7 and upwards. Also check out the VFIO-PCI Config Plugin in this context. Please use the code tags for configuration snippets next.
  21. Passthrough solved for Windows: Passthrough for Linux: Unraid Settings: - Host boots in UEFI (no legacy mode no CSM) - "Unraid OS" boot mode - Permit UEFI boot: Yes - Kernel parameter: append video=efifb:off,vesafb:off modprobe.blacklist=i2c_i801,i2c_smbus,snd_hda_intel,snd_hda_codec_hdmi,i915,drm,drm_kms_helper,i2c_algo_bit - VFIO-PCI Config to stub 00:02.0 VM Settings: - Linux Mint 19.3, SeaBIOS, q35-4.2 PCI Passthrough
  22. Hi @Dal1980 take a look at the following three things: Get Channel-ID (This is how I got mine. This was the only way for me to get the correct channel ID) https://github.com/limetech/webgui/pull/512(i.e. change ID from user id to group id in file /boot/config/plugins/dynamix/telegram/chatid ; mine is -100XXXXXXXXX) My Unraid Telegram notification settings contain the telegram bot token though This is how I got Telegram notifications working.
  23. To all Android paperless users who are keen to experiment, there is now a mobile app in pretty early development stage. Feel free to give the developer some feedback in order to improve the app. @OOmatrixOO seems like the PR got merged You should have access to the new feature after a container update via the UI. For now you need to add the env variable `PAPERLESS_FILENAME_FORMAT` yourself to the docker template. Will update the template soon. I only had a glance at the code yet. There is a migration script that might rename already imported documents as well. Give it a try.
  24. I would like to propose two feature requests. Let me describe the use cases in more detail. Feel free to ask additional questions about both use cases and let me know what you think. Use case 1 As a user of the plugin, I want to schedule the backup right after my server booted, so my array disks can go back to sleep after the backup is completed I backup appdata from a cache drive to the array I start (WOL) and stop (via sleep) my server on different schedules (during the week, weekend), due to rather high energy costs in the EU. Thus, I cannot use the custom cron schedule as it only allows a single cron entry. Using the time presets is likewise not possible. I want to do the backup during the week in the afternoon (where my server starts) and at the weekend in the morning (where my server starts) Possible solutions: (1) add schedule 'At startup of array' as an indicator of booted (similar to the user script plugin) (2) allow multiple cron entries or multiple triggers in general Use case 2 As a user of the plugin, I want to run a custom script after the backup is done and before the docker containers are restarted, so I can inject my custom offsite backup I perform custom offsite backups from my appdata folder via rclone and gdrive The backup is implemented via a custom user script The script stops the docker container with access to appdata folders and executes the rclone task The feature would allow me to use the docker start/stop mechanism of your plugin, so I can throw away my custom code The feature would allow me to schedule my other backup jobs in accordance with your plugin. Making the backup process more transparent. Example: The backup job of your plugin triggers when the server is booted (see first use case). It performs the backup of appdata as *.tar(.gz) and the flashdrive as folder to the array. Then the hook is executed, uploads the latest flashdrive backup from the array and the appdata folder from the cache drive to the cloud. Finally your plugin restarts the container. Possible solutions: (1) add a hook script field similar to "Custom stop (start) script" that is executed after the backup is done and before the docker container are restarted Is it possible to execute the CA backup plugin with its configuration from a user scripts? Then I would create two user scripts triggering the CA backup having different cron entries. I still would have to duplicate the scripts as the user scripts plugin is also not able to have multiple triggers. But, I would have a workaround. Edit: Found it! /usr/local/emhttp/plugins/ca.backup2/scripts/backup.sh /usr/local/emhttp/plugins/ca.backup2/scripts/backup.php # for a blocking call