Leaderboard

Popular Content

Showing content with the highest reputation on 12/16/20 in all areas

  1. I'm fine with LimeTech charging subscription fees for any kind of service, whether cloud-based backup, priority access to tech support, or any other service for which they incur ongoing costs. I hope such services are made available to licensees as well as future customers who choose to acquire Unraid through subscriptions. As long as LimeTech continues to offer traditional (non-subscription) Unraid OS licenses that include access to all 'core OS features' and upgrades, I will be rooting for them as they expand their customer base and revenue stream through subscription offerings. After all, it's in my best interests as a customer for LimeTech to be a thriving, profitable business.
    6 points
  2. Please try this: Stop array, select each data disk and set its file system type to "xfs". Start array, and then click Format, let it complete and observe that all disks 'mounted', everything looks good. Stop array, select each data disk and set file system type to "xfs-encrypted" (all 3 of them). Start array, observe that all 3 data disks should show 'Unformatted'. Enter your encryption key and click Format. At this point, all should show up as encrypted and mounted. Buf if not, please capture diagnostics at this point and post here.
    2 points
  3. Ich glaub ich werd mal den Hinweis machen, denn nicht jeder braucht den extra Pfad und den kannst ja nicht leer lassen sonst lässt sich der container nicht starten. Freut mich, luckyBackup bietet die möglichkeit über SSH direkt zu syncen und hab auch was eingebaut das noch die Keys für den container erstellt und du dann zu den known hosts hinzufügen kannst (muss noch was ändern aktuell bekommst die nur über das cli).
    2 points
  4. So what is wrong with Unraid charging for cloud based backup. If you want it? Some of you are already paying someone else to to do it.
    2 points
  5. I had the opportunity to test the “real word” bandwidth of some commonly used controllers in the community, so I’m posting my results in the hopes that it may help some users choose a controller and others understand what may be limiting their parity check/sync speed. Note that these tests are only relevant for those operations, normal read/writes to the array are usually limited by hard disk or network speed. Next to each controller is its maximum theoretical throughput and my results depending on the number of disks connected, result is observed parity/read check speed using a fast SSD only array with Unraid V6 Values in green are the measured controller power consumption with all ports in use. 2 Port Controllers SIL 3132 PCIe gen1 x1 (250MB/s) 1 x 125MB/s 2 x 80MB/s Asmedia ASM1061 PCIe gen2 x1 (500MB/s) - e.g., SYBA SY-PEX40039 and other similar cards 1 x 375MB/s 2 x 206MB/s JMicron JMB582 PCIe gen3 x1 (985MB/s) - e.g., SYBA SI-PEX40148 and other similar cards 1 x 570MB/s 2 x 450MB/s 4 Port Controllers SIL 3114 PCI (133MB/s) 1 x 105MB/s 2 x 63.5MB/s 3 x 42.5MB/s 4 x 32MB/s Adaptec AAR-1430SA PCIe gen1 x4 (1000MB/s) 4 x 210MB/s Marvell 9215 PCIe gen2 x1 (500MB/s) - 2w - e.g., SYBA SI-PEX40064 and other similar cards (possible issues with virtualization) 2 x 200MB/s 3 x 140MB/s 4 x 100MB/s Marvell 9230 PCIe gen2 x2 (1000MB/s) - 2w - e.g., SYBA SI-PEX40057 and other similar cards (possible issues with virtualization) 2 x 375MB/s 3 x 255MB/s 4 x 204MB/s IBM H1110 PCIe gen2 x4 (2000MB/s) - LSI 2004 chipset, results should be the same as for an LSI 9211-4i and other similar controllers 2 x 570MB/s 3 x 500MB/s 4 x 375MB/s Asmedia ASM1064 PCIe gen3 x1 (985MB/s) - e.g., SYBA SI-PEX40156 and other similar cards 2 x 450MB/s 3 x 300MB/s 4 x 225MB/s Asmedia ASM1164 PCIe gen3 x2 (1970MB/s) - NOTE - not actually tested, performance inferred from the ASM1166 with up to 4 devices 2 x 565MB/s 3 x 565MB/s 4 x 445MB/s 5 and 6 Port Controllers JMicron JMB585 PCIe gen3 x2 (1970MB/s) - 2w - e.g., SYBA SI-PEX40139 and other similar cards 2 x 570MB/s 3 x 565MB/s 4 x 440MB/s 5 x 350MB/s Asmedia ASM1166 PCIe gen3 x2 (1970MB/s) - 2w 2 x 565MB/s 3 x 565MB/s 4 x 445MB/s 5 x 355MB/s 6 x 300MB/s 8 Port Controllers Supermicro AOC-SAT2-MV8 PCI-X (1067MB/s) 4 x 220MB/s (167MB/s*) 5 x 177.5MB/s (135MB/s*) 6 x 147.5MB/s (115MB/s*) 7 x 127MB/s (97MB/s*) 8 x 112MB/s (84MB/s*) * PCI-X 100Mhz slot (800MB/S) Supermicro AOC-SASLP-MV8 PCIe gen1 x4 (1000MB/s) - 6w 4 x 140MB/s 5 x 117MB/s 6 x 105MB/s 7 x 90MB/s 8 x 80MB/s Supermicro AOC-SAS2LP-MV8 PCIe gen2 x8 (4000MB/s) - 6w 4 x 340MB/s 6 x 345MB/s 8 x 320MB/s (205MB/s*, 200MB/s**) * PCIe gen2 x4 (2000MB/s) ** PCIe gen1 x8 (2000MB/s) LSI 9211-8i PCIe gen2 x8 (4000MB/s) - 6w – LSI 2008 chipset 4 x 565MB/s 6 x 465MB/s 8 x 330MB/s (190MB/s*, 185MB/s**) * PCIe gen2 x4 (2000MB/s) ** PCIe gen1 x8 (2000MB/s) LSI 9207-8i PCIe gen3 x8 (4800MB/s) - 9w - LSI 2308 chipset 8 x 565MB/s LSI 9300-8i PCIe gen3 x8 (4800MB/s with the SATA3 devices used for this test) - LSI 3008 chipset 8 x 565MB/s (425MB/s*, 380MB/s**) * PCIe gen3 x4 (3940MB/s) ** PCIe gen2 x8 (4000MB/s) SAS Expanders HP 6Gb (3Gb SATA) SAS Expander - 11w Single Link with LSI 9211-8i (1200MB/s*) 8 x 137.5MB/s 12 x 92.5MB/s 16 x 70MB/s 20 x 55MB/s 24 x 47.5MB/s Dual Link with LSI 9211-8i (2400MB/s*) 12 x 182.5MB/s 16 x 140MB/s 20 x 110MB/s 24 x 95MB/s * Half 6GB bandwidth because it only links @ 3Gb with SATA disks Intel® SAS2 Expander RES2SV240 - 10w Single Link with LSI 9211-8i (2400MB/s) 8 x 275MB/s 12 x 185MB/s 16 x 140MB/s (112MB/s*) 20 x 110MB/s (92MB/s*) * Avoid using slower linking speed disks with expanders, as it will bring total speed down, in this example 4 of the SSDs were SATA2, instead of all SATA3. Dual Link with LSI 9211-8i (4000MB/s) 12 x 235MB/s 16 x 185MB/s Dual Link with LSI 9207-8i (4800MB/s) 16 x 275MB/s LSI SAS3 expander (included on a Supermicro BPN-SAS3-826EL1 backplane) Single Link with LSI 9300-8i (tested with SATA3 devices, max usable bandwidth would be 2200MB/s, but with LSI's Databolt technology we can get almost SAS3 speeds) 8 x 500MB/s 12 x 340MB/s Dual Link with LSI 9300-8i (*) 10 x 510MB/s 12 x 460MB/s * tested with SATA3 devices, max usable bandwidth would be 4400MB/s, but with LSI's Databolt technology we can closer to SAS3 speeds, with SAS3 devices limit here would be the PCIe link, which should be around 6600-7000MB/s usable. HP 12G SAS3 EXPANDER (761879-001) Single Link with LSI 9300-8i (2400MB/s*) 8 x 270MB/s 12 x 180MB/s 16 x 135MB/s 20 x 110MB/s 24 x 90MB/s Dual Link with LSI 9300-8i (4800MB/s*) 10 x 420MB/s 12 x 360MB/s 16 x 270MB/s 20 x 220MB/s 24 x 180MB/s * tested with SATA3 devices, no Databolt or equivalent technology, at least not with an LSI HBA, with SAS3 devices limit here would be the around 4400MB/s with single link, and the PCIe slot with dual link, which should be around 6600-7000MB/s usable. Intel® SAS3 Expander RES3TV360 Single Link with LSI 9308-8i (*) 8 x 490MB/s 12 x 330MB/s 16 x 245MB/s 20 x 170MB/s 24 x 130MB/s 28 x 105MB/s Dual Link with LSI 9308-8i (*) 12 x 505MB/s 16 x 380MB/s 20 x 300MB/s 24 x 230MB/s 28 x 195MB/s * tested with SATA3 devices, PMC expander chip includes similar functionality to LSI's Databolt, with SAS3 devices limit here would be the around 4400MB/s with single link, and the PCIe slot with dual link, which should be around 6600-7000MB/s usable. Note: these results were after updating the expander firmware to latest available at this time (B057), it was noticeably slower with the older firmware that came with it. Sata 2 vs Sata 3 I see many times on the forum users asking if changing to Sata 3 controllers or disks would improve their speed, Sata 2 has enough bandwidth (between 265 and 275MB/s according to my tests) for the fastest disks currently on the market, if buying a new board or controller you should buy sata 3 for the future, but except for SSD use there’s no gain in changing your Sata 2 setup to Sata 3. Single vs. Dual Channel RAM In arrays with many disks, and especially with low “horsepower” CPUs, memory bandwidth can also have a big effect on parity check speed, obviously this will only make a difference if you’re not hitting a controller bottleneck, two examples with 24 drive arrays: Asus A88X-M PLUS with AMD A4-6300 dual core @ 3.7Ghz Single Channel – 99.1MB/s Dual Channel - 132.9MB/s Supermicro X9SCL-F with Intel G1620 dual core @ 2.7Ghz Single Channel – 131.8MB/s Dual Channel – 184.0MB/s DMI There is another bus that can be a bottleneck for Intel based boards, much more so than Sata 2, the DMI that connects the south bridge or PCH to the CPU. Socket 775, 1156 and 1366 use DMI 1.0, socket 1155, 1150 and 2011 use DMI 2.0, socket 1151 uses DMI 3.0 DMI 1.0 (1000MB/s) 4 x 180MB/s 5 x 140MB/s 6 x 120MB/s 8 x 100MB/s 10 x 85MB/s DMI 2.0 (2000MB/s) 4 x 270MB/s (Sata2 limit) 6 x 240MB/s 8 x 195MB/s 9 x 170MB/s 10 x 145MB/s 12 x 115MB/s 14 x 110MB/s DMI 3.0 (3940MB/s) 6 x 330MB/s (Onboard SATA only*) 10 X 297.5MB/s 12 x 250MB/s 16 X 185MB/s *Despite being DMI 3.0** , Skylake, Kaby Lake, Coffee Lake, Comet Lake and Alder Lake chipsets have a max combined bandwidth of approximately 2GB/s for the onboard SATA ports. **Except low end H110 and H310 chipsets which are only DMI 2.0, Z690 is DMI 4.0 and not yet tested by me, but except same result as the other Alder Lake chipsets. DMI 1.0 can be a bottleneck using only the onboard Sata ports, DMI 2.0 can limit users with all onboard ports used plus an additional controller onboard or on a PCIe slot that shares the DMI bus, in most home market boards only the graphics slot connects directly to CPU, all other slots go through the DMI (more top of the line boards, usually with SLI support, have at least 2 slots), server boards usually have 2 or 3 slots connected directly to the CPU, you should always use these slots first. You can see below the diagram for my X9SCL-F test server board, for the DMI 2.0 tests I used the 6 onboard ports plus one Adaptec 1430SA on PCIe slot 4. UMI (2000MB/s) - Used on most AMD APUs, equivalent to intel DMI 2.0 6 x 203MB/s 7 x 173MB/s 8 x 152MB/s Ryzen link - PCIe 3.0 x4 (3940MB/s) 6 x 467MB/s (Onboard SATA only) I think there are no big surprises and most results make sense and are in line with what I expected, exception maybe for the SASLP that should have the same bandwidth of the Adaptec 1430SA and is clearly slower, can limit a parity check with only 4 disks. I expect some variations in the results from other users due to different hardware and/or tunnable settings, but would be surprised if there are big differences, reply here if you can get a significant better speed with a specific controller. How to check and improve your parity check speed System Stats from Dynamix V6 Plugins is usually an easy way to find out if a parity check is bus limited, after the check finishes look at the storage graph, on an unlimited system it should start at a higher speed and gradually slow down as it goes to the disks slower inner tracks, on a limited system the graph will be flat at the beginning or totally flat for a worst-case scenario. See screenshots below for examples (arrays with mixed disk sizes will have speed jumps at the end of each one, but principle is the same). If you are not bus limited but still find your speed low, there’s a couple things worth trying: Diskspeed - your parity check speed can’t be faster than your slowest disk, a big advantage of Unraid is the possibility to mix different size disks, but this can lead to have an assortment of disk models and sizes, use this to find your slowest disks and when it’s time to upgrade replace these first. Tunables Tester - on some systems can increase the average speed 10 to 20Mb/s or more, on others makes little or no difference. That’s all I can think of, all suggestions welcome.
    1 point
  6. Overview: Support for the docker template and container for Overseerr App: Overseerr - https://github.com/sct/overseerr Docker Hub: https://registry.hub.docker.com/r/sctx/overseerr
    1 point
  7. I believe I remember reading in the first beta that implemented encryption, that there would potentially be a future feature to encrypt an existing disk while keeping all existing data without the need to format it first. Just wondering if this is still on the “near” future road map? I would really like to encrypt my disks but currently they are pretty filled up and the only semi easy way I am aware of would be to make my only parity drive a data drive to copy all the data off a disk, reformat with encryption the old disk, copy back all the data and repeat for each disk. I would prefer not to do this if there is another option on the horizon.
    1 point
  8. As always, prior to updating, create a backup of your USB flash device: "Main/Flash/Flash Device Settings" - click "Flash Backup". Besides bug fixing, most of the work in this release is related to upgrading to the Linux 5.9 kernel where, due to kernel API changes, it has become necessary to move device spin-up/down and spin-up group handling out of the md/unraid driver and have it handled entirely in user space. This also let us fix an issue where device spin-up of devices in user-defined pools was executed serially instead of in parallel. We should also now be able to properly support SAS device spin-up/down (finally) and with extraordinary help from @doron we are almost there. SAS devices are generally designed for enterprise environments where device spin-down is rare, and many devices have inconsistent behavior surrounding this functionality. This release itself does not include SAS device spin handling built-in but @doron is providing a plugin where we continue to address some nagging details. We expect to have this ironed out before stable release. Along with re-work of device spin control, we have also integrated spin-up/down and temperature monitoring for unassigned devices. We have coordinated with @dlandon to ensure proper integration with the Unassigned Devices plugin. If you've read this far, and you are using the Unassigned Devices plugin, please remove it first before upgrading and then re-install UD via Community Apps. Since we have not identified any data loss bugs related to the user-defined pools feature, I have removed the -beta designation and we now enter the -rc phase. Our plan is for this to be relatively short and limited to squashing bugs. We are in the process of writing up more thorough release notes in preparation for stable release. A lot of exciting changes and features are coming to Unraid OS and I want to thank everyone for participating in our Pre-release program! Version 6.9.0-rc1 2020-12-09 (vs -beta35) Base distro: aaa_elflibs: version 15.0 build 27 hdparm: version 9.60 icu4c: version 68.1 intel-microcode: version 20201118 kernel-firmware: version 20201130_7455a36 nginx: version 1.19.5 openssh: version 8.4p1 pam: version 1.5.1 php: version 7.4.13 samba: version 4.12.10 xfsprogs: version 5.9.0 Linux kernel: version 5.9.13 md/unraid: version 2.9.17 removed spinup group spinup/spdindown support (functionality moved to emhttpd) added configurable sync start offset added iSCSI kernel support: CONFIG_ISCSI_TARGET: Linux-iSCSI.org iSCSI Target Mode Stack CONFIG_ISCSI_TARGET_CXGB4: Chelsio iSCSI target offload driver CONFIG_LOOPBACK_TARGET: TCM Virtual SAS target and Linux/SCSI LDD fabric loopback module CONFIG_NVME_TARGET: NVMe Target support CONFIG_NVME_TARGET_LOOP: NVMe loopback device support CONFIG_NVME_TARGET_PASSTHRU: NVMe Target Passthrough support CONFIG_TARGET_CORE: Generic Target Core Mod (TCM) and ConfigFS Infrastructure CONFIG_TCM_FILEIO: TCM/FILEIO Subsystem Plugin for Linux/VFS CONFIG_TCM_IBLOCK: TCM/IBLOCK Subsystem Plugin for Linux/BLOCK CONFIG_TCM_PSCSI: TCM/pSCSI Subsystem Plugin for Linux/SCSI CONFIG_TCM_USER2: TCM/USER Subsystem Plugin for Linux added USB/IP kernel support: CONFIG_USBIP_CORE: USB/IP support CONFIG_USBIP_VHCI_HCD: VHCI hcd Management: emhttpd: implement spinup group spinup/spindown; add spinup/spindown callouts emhttpd: get rid of poll_attributes event emhttpd: fix disk "SMART controller type" not being honored when reading temperatures rsyslog: fix broken "Mirror syslog to flash" webgui: Fix wrong docker run URL reference webgui: Fix crash when reading very large log files (limiting output to 1000 lines). webgui: Fix dismiss all notification webgui: Fix Started VMs not appearing in dashboard webgui: VM manager: add virtio-win-0.1.190-1 webgui: Notifications: Fix gap on white / black webgui: Do not show CA profiles in Add Container list webgui: support spin-up/down and temperature monitoring of unassigned devices webgui: VM manager: Fix: Changing from VM VNC graphics to GPU passthrough webgui: Change Icon for Motherboard Info from cog (settings) to info
    1 point
  9. I know I'm asking a lot. Is it possible to get Unraid 6.9 to LTS kernel 5.10 before full release? Only reason I ask is for the comfort of having an LTS kernel from both support as a user and also for the devs. I'm not gonna be upset if I'm told "no". Just thought I would ask and figured an LTS kernel could benefit the UnRaid team in this release . edit: also, thanks for the RC1 release! it seems to be working well so far! thanks for fixing the dashboard issues!
    1 point
  10. Yeah I see my fault. I just asked a friend to try and he said he could join with no issues. I feel quite stupid now. Sorry for the inconvenience. Thank you so much for your work and thanks for your help.
    1 point
  11. For what it's worth, I just updated the Roon CORE running in this docker container to 1.7 (build 710) via the Roon Remote App running on my Mac without any problems. I've updated my template accordingly, so anyone interested in starting over with the correct mappings can delete their Roon container, delete your appdata directory, and pull the container again using the new template. If you backed up your library via Roon you should be able to restore the backup once you have your new CORE up and running. If you'd prefer to just update your existing container to the correct mappings, see my instructions above. CC @dkerlee Edit: you may need to wait a bit for my template to update in Community Apps.
    1 point
  12. Und ein wenig größeres Gehäuse kommt für dich nicht in Frage? Wenn du dir schon ein "NAS" baust würd ich eher zu sowas greifen: https://www.amazon.de/Eolize-SVD-NC11-4-mini-PC-Gehäuse-System/dp/B005EHRNX6/ref=sr_1_1?__mk_de_DE=ÅMÅŽÕÑ&dchild=1&keywords=eolize&qid=1608151386&sr=8-1 Das ist klein und fein und ein SFF Netzteil is da auch schon drin, sicher ist jetzt nicht günstig aber du hast immerhin 4 Einschübe und kannst wenn es hart auf hart kommt noch eine SSD irgendwo reinlegen/kleben... Das passt zB locker in ein IKEA Kalax rein, glaub da würden sogar 2 reinpassen... Hab schon mehrere solche gebaut und find die wirklich gut und auch leise.
    1 point
  13. Thank you! Thank you! Thank you! That did it and I'm all set now!
    1 point
  14. Ok, I've had to escalate to the dev team as I have no idea what's wrong. Will get back to you.
    1 point
  15. God I sure hope so, just seeing it on and lights and fan and seeing it detected didn't make me think that was even a possibility but I'm sure stranger things are possible
    1 point
  16. OH!! GOD!! I think I solved the problem of Missing GOP in GPU passthrough on my PC. I am very excited at this monment, So let me talk about what I did My MB is MSI B450m Motar MAX, it's doesn't need to close CSM, just boot unraid in UEFI mode My GPU is RX5500 XT so i add agdpmod=pikera in the NVRAM boot-args of the config.plist i have add the vbios in the xml config(but i don't think so it's the reason) from TechpowerUP I append video=efifb:off to syslinux.cfg and reboot, it's like: kernel /bzimage append vfio_iommu_type1.allow_unsafe_interrupts=1 pcie_acs_override=downstream,multifunction video=efifb:off initrd=/bzroot Without this, you will encounter this error message with white apple logo (vfio: unable to power on device stuck in d3) When I finished the configuration, I found a progress bar under the white apple logo, and then! I can enter the MacOS Finally, attach my xml config <?xml version='1.0' encoding='UTF-8'?> <domain type='kvm' id='1' xmlns:qemu='http://libvirt.org/schemas/domain/qemu/1.0'> <name>Macinabox BigSur</name> <uuid>787b7168-23ac-4d73-8789-eb5786b331c3</uuid> <description>MacOS Big Sur</description> <metadata> <vmtemplate xmlns="unraid" name="Windows 10" icon="BigSur.png" os="osx"/> </metadata> <memory unit='KiB'>16777216</memory> <currentMemory unit='KiB'>16777216</currentMemory> <memoryBacking> <nosharepages/> </memoryBacking> <vcpu placement='static'>8</vcpu> <cputune> <vcpupin vcpu='0' cpuset='2'/> <vcpupin vcpu='1' cpuset='8'/> <vcpupin vcpu='2' cpuset='3'/> <vcpupin vcpu='3' cpuset='9'/> <vcpupin vcpu='4' cpuset='4'/> <vcpupin vcpu='5' cpuset='10'/> <vcpupin vcpu='6' cpuset='5'/> <vcpupin vcpu='7' cpuset='11'/> </cputune> <resource> <partition>/machine</partition> </resource> <os> <type arch='x86_64' machine='pc-q35-4.2'>hvm</type> <loader readonly='yes' type='pflash'>/mnt/user/system/custom_ovmf/Macinabox_CODE-pure-efi.fd</loader> <nvram>/etc/libvirt/qemu/nvram/787b7168-23ac-4d73-8789-eb5786b331c3_VARS-pure-efi.fd</nvram> </os> <features> <acpi/> <apic/> </features> <cpu mode='host-passthrough' check='none' migratable='on'> <topology sockets='1' dies='1' cores='4' threads='2'/> <cache mode='passthrough'/> <feature policy='require' name='topoext'/> </cpu> <clock offset='utc'> <timer name='rtc' tickpolicy='catchup'/> <timer name='pit' tickpolicy='delay'/> <timer name='hpet' present='no'/> </clock> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>restart</on_crash> <devices> <emulator>/usr/local/sbin/qemu</emulator> <disk type='file' device='disk'> <driver name='qemu' type='raw' cache='writeback'/> <source file='/mnt/user/domains/Macinabox BigSur/macos_disk.img' index='1'/> <backingStore/> <target dev='hdc' bus='sata'/> <boot order='1'/> <alias name='sata0-0-2'/> <address type='drive' controller='0' bus='0' target='0' unit='2'/> </disk> <controller type='usb' index='0' model='ich9-ehci1'> <alias name='usb'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x7'/> </controller> <controller type='usb' index='0' model='ich9-uhci1'> <alias name='usb'/> <master startport='0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0' multifunction='on'/> </controller> <controller type='usb' index='0' model='ich9-uhci2'> <alias name='usb'/> <master startport='2'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x1'/> </controller> <controller type='usb' index='0' model='ich9-uhci3'> <alias name='usb'/> <master startport='4'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x2'/> </controller> <controller type='pci' index='0' model='pcie-root'> <alias name='pcie.0'/> </controller> <controller type='pci' index='1' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='1' port='0x8'/> <alias name='pci.1'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x0' multifunction='on'/> </controller> <controller type='pci' index='2' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='2' port='0x9'/> <alias name='pci.2'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x1'/> </controller> <controller type='pci' index='3' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='3' port='0xc'/> <alias name='pci.3'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x4'/> </controller> <controller type='pci' index='4' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='4' port='0x13'/> <alias name='pci.4'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x3'/> </controller> <controller type='pci' index='5' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='5' port='0xa'/> <alias name='pci.5'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x2'/> </controller> <controller type='pci' index='6' model='pcie-to-pci-bridge'> <model name='pcie-pci-bridge'/> <alias name='pci.6'/> <address type='pci' domain='0x0000' bus='0x01' slot='0x00' function='0x0'/> </controller> <controller type='pci' index='7' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='7' port='0xb'/> <alias name='pci.7'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x3'/> </controller> <controller type='virtio-serial' index='0'> <alias name='virtio-serial0'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x00' function='0x0'/> </controller> <controller type='sata' index='0'> <alias name='ide'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x1f' function='0x2'/> </controller> <interface type='bridge'> <mac address='52:54:00:86:4c:fc'/> <source bridge='br0'/> <target dev='vnet0'/> <model type='e1000-82545em'/> <alias name='net0'/> <address type='pci' domain='0x0000' bus='0x03' slot='0x00' function='0x0'/> </interface> <serial type='pty'> <source path='/dev/pts/0'/> <target type='isa-serial' port='0'> <model name='isa-serial'/> </target> <alias name='serial0'/> </serial> <console type='pty' tty='/dev/pts/0'> <source path='/dev/pts/0'/> <target type='serial' port='0'/> <alias name='serial0'/> </console> <channel type='unix'> <source mode='bind' path='/var/lib/libvirt/qemu/channel/target/domain-1-Macinabox BigSur/org.qemu.guest_agent.0'/> <target type='virtio' name='org.qemu.guest_agent.0' state='connected'/> <alias name='channel0'/> <address type='virtio-serial' controller='0' bus='0' port='1'/> </channel> <input type='tablet' bus='usb'> <alias name='input0'/> <address type='usb' bus='0' port='1'/> </input> <input type='mouse' bus='ps2'> <alias name='input1'/> </input> <input type='keyboard' bus='ps2'> <alias name='input2'/> </input> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x28' slot='0x00' function='0x0'/> </source> <alias name='hostdev0'/> <rom file='/mnt/user/isos/vbios/Sapphire.RX5500XT.8192.191127.rom'/> <address type='pci' domain='0x0000' bus='0x06' slot='0x01' function='0x0' multifunction='on'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x28' slot='0x00' function='0x1'/> </source> <alias name='hostdev1'/> <address type='pci' domain='0x0000' bus='0x06' slot='0x02' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x046d'/> <product id='0xc08b'/> <address bus='1' device='2'/> </source> <alias name='hostdev2'/> <address type='usb' bus='0' port='2'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x0a12'/> <product id='0x0001'/> <address bus='1' device='3'/> </source> <alias name='hostdev3'/> <address type='usb' bus='0' port='3'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x0c45'/> <product id='0x7603'/> <address bus='1' device='5'/> </source> <alias name='hostdev4'/> <address type='usb' bus='0' port='4'/> </hostdev> <memballoon model='none'/> </devices> <seclabel type='dynamic' model='dac' relabel='yes'> <label>+0:+100</label> <imagelabel>+0:+100</imagelabel> </seclabel> <qemu:commandline> <qemu:arg value='-usb'/> <qemu:arg value='-device'/> <qemu:arg value='usb-kbd,bus=usb-bus.0'/> <qemu:arg value='-device'/> <qemu:arg value='************************'/> <qemu:arg value='-smbios'/> <qemu:arg value='type=2'/> <qemu:arg value='-cpu'/> <qemu:arg value='Penryn,kvm=on,vendor=GenuineIntel,+invtsc,vmware-cpuid-freq=on,+pcid,+ssse3,+sse4.2,+popcnt,+avx,+aes,+xsave,+xsaveopt,check'/> </qemu:commandline> </domain> Thank you for helping me.
    1 point
  17. Okay, via process of elimination, it was my windows PC. Then using a network traffic viewer, it was my browser. Even though I had no tabs open. But... I had an extension that was apparently "incorrectly" hitting my server. I disabled the extension, and no more messages in the log. Thank you for the help!
    1 point
  18. Please don't post about the same problem in multiple places. It makes it impossible to coordinate responses. "Crossposting" has been considered bad form on message boards since before the World Wide Web.
    1 point
  19. The images are really grainy and out of focus Its hard to actually tell what you are talking about.
    1 point
  20. True..and we don't know if it's a problem of the smb kext, or the e1000 driver, or whatever...The only solution should be to contact directly apple and speak at the phone with an expert so that he can see exactly what happens (screen sharing): however, we know what apple thinks about mac os on virtual machines, you can find valuable people willing to help and prepared to solve the issues or others that simply request the log files generated from the apple app, and once they see that mac os runs in an unsupported machine they simply don't bother to solve the issue. It happened to me when I was trying to solve the facetime/imessage login issue (related to apple servers), only at the second phone call the expert solved the issue in less than 30 seconds..but this is a different story.. Btw, this seems to not be an issue related to unsupported machines, I think it was introduced in beta 7 (beta 6 broke smb, beta 1 - 5 were working good), and your issue is exactly the same as mine (stuck at 67,1 or 134,2 mb and then error -8084, or sometimes kernel panic), but this issue as I wrote doesn't apply to all files (it applies only to some files and the transfer always fails for that files) and I think it's independent on the size of the files, in fact I'm able to transfer 3-4gb files, but hangs for a 500mb file.. You also will probably notice that browsing folders/files and transfers are somewhat sluggish compared to Catalina.
    1 point
  21. I can report the same problem. More in detail : Unraid 6.9.0-beta35 VM pc-q35-5.1 BigSur 11.1 / OpenCore 0.6.4 e1000-82545em Copying a 9Gb file from my MacBook Pro (Catalina) connected over wifi works fine (at least the few times I tested) . Copying the same file from the same Macbook connect over ethernet 1Gb/s leads to a halt after exactly 134,2Mo and then error -8084 Copying file directly from Unraid shares leads to kernel panic. The difference on copying over wifi or ethernet would be the speed (and even more copying from unraid shares). From what I understand from the discussions above, there is nothing much to do on our side, right ?
    1 point
  22. ...schau mal hier: Die Einstellung findest Du bei den Volume mappings im jeweiligen Docker...dort im eintrag dann unter "edit -> Access-Mode"
    1 point
  23. It seems you are in the same boat with me.. With Big Sur I'm experiencing smb issue (hangs or kernel panics), and yes I'm using e1000-82545em; not possible for me to use vmxnet3 because, as you also may experience it partially hangs on uploads/downloads. See here also: This refers to another machine I have (look at the last comments): https://discussions.apple.com/thread/252079374 NFS instead of smb seems to work better in big sur. This is one of the reasons I still didn't update to big sur, Catalina has no issue.
    1 point
  24. Ich nutze diesen Docker auch selbst nicht. Mir kam es nur komisch vor, da es ja ein GUI--Werkzeug anbietet, dass nur ein Volume gemappt wird. Mit /mnt/user liegt dann zwangsläufig bei alleiniger GUI Verwendung Quelle und Ziel auf dem lokalen Array, was dem UseCase Backup etwas widersprechen würde. Mein Vorschlag war, analog so wie es@Alphavil gemacht hat, den Pfad für das Ziel (optional) ins Template aufzunehmen. Da kann dann auch ein externer mount eingetragen werden, den man ja auch mit UD erstellen kann. Aber der Hinweis allein ist sicher auch eine Verbesserung. Danke dass Du Dir die Sache ansiehst. Ich denke ich schaue mir den Docker mal über die Feiertage an...mache es aktuell zu Fuss über ssh/rsync auf einen entfernten Server, den UD automatisch einbindet wenn der geweckt ist. Gesendet von meinem SM-G960F mit Tapatalk
    1 point
  25. Somethings else, doesn't look like this folder mapping is doing anything? this container has always used /data/transmission-home as its base directory, I have tried to separate the config files from this folder on my array, to my cache drive where all my other docker files are stored, but I have been unsuccessful so far! check and see if anything is in that folder before removing it just incase.....Git posting on the issue - you may have to set another variable for this to me used you can also remove the 1198 port. The new PIA configs don't use it anymore.
    1 point
  26. Anytime!! Almost every problem it seems is related to some kind of variable / port / path mapping issue!! why it changed.....I can't answer that one!! Cheers!!
    1 point
  27. I believe this should be 'true', not '1' ?
    1 point
  28. Hello! Anyone interested in translating Unraid into Korean is welcome! 안녕하세요! 한국어 번역에 관심 있으신 분들은 어느 분이든 참여해주세요! 🙂
    1 point
  29. 😁...in der Beschreibung zu Deinem LuckyBackup Docker ist für die Daten nur ein Standard Pfad in den Variablen /mnt/user/ - also die Shares auf dem Array gemappt: https://hub.docker.com/r/ich777/luckybackup @Alphavil wollte aber eine externe Disk, via unassigned devices anbinden und hat diese letztlich separat gemappt, also nicht unter /mnt/user sondern unter /mnt/disks (s.o.) ...für mich sieht es so aus, als ob das im Template nicht vorgesehen ist bzw. die Beschreibung im Docker nicht aktuell ist?
    1 point
  30. Mitlesen nur wenn ich Zeit hab... Um was gehts hier?
    1 point
  31. ...OK, so geht es dann wohl auch...hätte ich von der Beschreibung der Variablen im Docker her jetzt nicht vermutet. Evtl. ist diese aber auch nicht aktuell? Macht schon Sinn in einem Backup-System die Quell- und Zielpfade separat, eindeutig zu benennen, damit man da nix verwechselt. Dann gib doch dem Entwickler evtl. mal nen Tipp...der liest hier mit und spricht Deutsch.
    1 point
  32. Hab noch Einiges versucht und nun funktioniert es. Das mit dem zusätzlichen Pfad einbinden war mein Problem, man lernt nie aus. Danke für die Hilfe 🙂 P.S.: Jetzt läuft auch mein Backup auf die Platte, coole Docker muss ich sagen 👍
    1 point
  33. Container is now finished and uploaded, it will take a few hours to show up in the CA App.
    1 point
  34. Hello paperless users, unfortunately, paperless hasn't received a lot of updates and bug fixes in the past few month. Even pull requests are not merged for some time now. Though, paperless runs rocks solid and gets the job done! For some time now, there is a well-maintained fork of paperless out there. It's called paperless-ng and I'm happy to announce that paperless-ng is officially available via Unraids community application store (CA store). Let me briefly outline a few improvements over the existing solution: New front end build with Angular. It features full text search with scored and highlighted results, savable filters, a dashboard, and document uploading on the landing page. Mobile support is also almost there. Some layouts don't work yet on small screens. New mail consumer that supports multiple accounts and custom filters and actions. Fully tested! Paperless-ng trains a neural network on your documents and assigns tags and correspondents automatically, if you instruct it to do so. Updated dependencies. More tests of critical backend parts. A proper task processing queue that can consume multiple documents in parallel. Consumption of many documents is now blazing fast on multi core system. Fixed much of the consumer code, so that it does not block the database during consumption, for instance. Paperless-ng now uses OCRmyPDF to perform OCR on documents. It still uses tesseract under the hood, but the PDF parser of Paperless has changed considerably and will behave different for some documents (also see PAPERLESS_OCR_MODE @bigbangus @vakilando). Compatible with the paperless iOS and Android app There is even more. So, don't miss to check out the documentation too! Jonas, the maintainer of paperless-ng, is a highly motivated dev and currently he works towards the first stable release 1.0. Thus, the current version of paperless-ng is flagged as beta in the CA store. If you are interested in paperless-ng and want to support Jonas, please test paperless-ng and give him feedback. You can find a migration guide here too. Be warned, paperless-ng has received a lot of changes and you might encounter bugs. So, whatever you are doing get your backup right first! Also make sure to read the product vision of paperless-ng first, before submitting feature requests. Things like multi-user support are not in the scope of the project for example. That being said: Issues with paperless-ng go here Issues with the Unraid setup go here Happy testing and stay healthy!
    1 point
  35. Hi @Jagadguru Yes. I use these with great success. See here; https://mediaserver8.blogspot.com/2020/04/unraid-discrete-usb-passthrough-to.html and here; https://mediaserver8.blogspot.com/2020/04/mediaserver-83-bifurcation-edition.html You can even assign cards in each slot to different VMs as they can show up in different IOMMU groups. They work using a technology known as PLX. Essentially, theres a traffic cop chip on them that assigns each slot on the expander board a slice of time on the motherboard slot. In effect, this is transparent and the system sees cards populated in the expander as discrete and additional devices. I've encountered no problems using up to 4x USB 3.0 cards in these expansion devices, all assigned to different VMs simultaneously.
    1 point
  36. I was just watching my syslog being spammed with nginx ... worker process ... exited on signal 6 2-3 times/second, and immediately upon finding and closing four stale Unraid web GUI tabs open across two machines, it stopped. Hope this helps someone.
    1 point
  37. knew before i even clicked on this thread it would be about a molded molex to sata. The old saying holds true: Molex to sata, lose all your data.
    1 point