landS

Thanks, didn't realize the script and gui was only triggered when the password was typed into the users change password interface. Makes sense though.

Thanks for the heads up. I've updated to a stronger password and reviewed my share securities (these are already OK). Also installed 'Dynamix Password Validator.' and while I see it in the plugins page I seem unable to sus out its location in the gui to actually use it. Some help would be appreciated!

Excellent write up @ljm42 thank you kindly.

Appears to be working Ok. Thanks again Squid!

As always, much obliged Squid! 2 more question then. 1, will the new Sysconfig look like: kernel /bzimage append iommu=pt initrd=/bzroot 2, is it ok to NOT stub the 2 GPUs (which are not currently stubbed) and leave directly assigned within the VM settings like they are now? Sometimes I shutdown a VM and startup a seldom used one or a docker that makes use of a GPU

Good day Unraid, I’ve been using 2 VMs for my daily drivers for years now, rock solid. Update to 6.9.1 and now ‘FixProblems’ is throwing ‘vfio-pci.ids or xen-pciback.hide found within syslinux.cfg.’ Jumping over to Syslinux Config (unRAID OS) I see: kernel /bzimage append iommu=pt vfio-pci.ids=1b21:0612,1b21:1242 isolcpus=2-4,8-10 initrd=/bzroot 1 – Will this actually cause stability issues to leave as is? 2 – Currently IOMMU Group 34 (GeForce 1080) is assigned directly to 1 VM at VM launch, IOMMU Group 36 (GeForce 1060) is assigned directly to a 2nd VM ad VM launch, IOMMU Group 35 1b21:1242 is stubbed for a VM (USB Controller), and IOMMU Group 43 1b21:0612 is stubbed for a VM (Sata Controller). If I remove the stubs from Syslinux, is it OK to just directly stub only the 2 vfio-pci.ids under Tools/SysDevs? 3 – Should isolcpus be moved out of the syslinux config? I show it as stubbed under Settings/CPUSet (2/8, 3/9, 4/10, 5/11) for the VMs and separately (1/7) a Docker app 4 – Should iommu=pt be moved? If so… where? Thanks folks! (its been years since I've touched this config and would hate to mess it up)

Latest stable & gt710. Started up a Windows 10 container. I first updated the Dell bios. I also trimmed the bottom 4 pcie slot so I could fit the longer gpu card in after ensuring I wasn't going to short any pins in doing so. I follow Space-Invaders YouTube videos for the config advice & did not need to jump through many hoops to get it working. Alas, I built this for a local business that wanted some help and as such it is not now accessible for accessing the config settings. (note gpu selection is picky on what works.... And I believe Dell reserves the x16 slot for a SAS card but I could be wrong)

$550 Server Grade Budget Build Specs (including storage) Good day folks, shared here is my latest budget build. Hopefully it helps some of you. Amazon: $066 (x2) HDD: (HGST 4 TB renewed, passed preclear) B0863FS37V $135 (x1) UPS: APC Pure-Sine unit B06VY12HW4 $008 Flash: Sandisk Cruzer Flash Drive B005FYNSZA $013 (x2) Cables: Mini-SAS to Mini-SAS Cables B011W2F626 Ebay: $130 (x1) PC: Dell T410 184283026350 $005 (x4) Hot Swap Trays: HDD Drive Tray Caddy For Dell PowerEdge T320 T410 164200180124 $040 (x1) Data Card: Dell Perc H310 IT mode 143326638593 $060 (x1) Unraid OS PC Includes HVM & IOMMU 2 2 GB of DDR3 ECC ram (in 4 slots) 8 thread E5620 @ 2.40GHz 6 hot-swap 3.5 slots 2 Hot Swap Trays 2 5.25” adjoined slots 2 unused SATA power cables 6 unused SATA data ports 1 16x PCIe slot 4 4x PCIe open CPU slot with matching 4 ram slots 2 250 GB HDDs (passed preclear fine) Note that while passthrough works great, any video card will need to either be powered off of the only 2 SATA power cables, or be powered solely by the PCIe slot.

I would not assign a USB drive to the array long term as the risks to the data integrity are higher than my comfort level. You can shuck the drive and use sata connector (which many here have done). . Alternatively you can use the USB device outside of the array (unassigned devices is the easiest). This can then be used for transferring data, backing up data on the array, etc. User scripts plug helps. . Unraid provides parity protected data. This is not the same as a backup.

@Djoss - you are a saint

Howdy @Djoss Looks like CP is back to wanting an upgrade. Thanks, as always, for your maintaining this most excellent docker.

I haven't hit the limit yet - - - but I believe this means I now have 8gb allocated to Cp and 2 dockers - leaving 8 for Unraid. So, I am at the highest limit I'm conformable on offer cp without adding more ram. It could be unrelated, but when I'd find the limit hit, added new files, and checked online backups the files were not present. Restart Cp and within a day they are uploaded

I have INOTIFY now triggered every 4-6 weeks. I've bumped it up to 8192000 on a machine with 2 always on Windows VMs and 32GB of ECC ram. I'm actually contemplating doubling the memory just to increase INOTIFY further

WSD is also enabled. No worries on further troubleshooting discovery as the IP assignment works great

Thanks dlandon! Alas netbios was already enabled under smb for TOWER Altering the TOWER2's UD mounts to use IP & Altering the TOWER2's User scripts to use IP_Share from Tower_Share Is again working edit - holy cow the transfer is WAY faster using IP over NAME mounts! Enjoy a case on me

Howdy Folks. Any help you may kindly offer would be greatly appreciated I use the most excellent UD to mount SMB shares on my TOWER2 from my TOWER1. Every 2-3 weeks I power up the secondary backup server, update the Plugins if necessary & reboot, then kick of UserScripts of 2 flavors: rsync -av --progress --delete-before /mnt/disks/TOWER_WinVM/ /mnt/user/WinVM rsync -r -v --progress --ignore-existing -s /mnt/disks/TOWER_Media/AudioBooks/ /mnt/user/Media/AudioBooks I update this OS only on occasion as it spends very little time powered up and it has no network shares (it has shares using the same name as the primary TOWER shares, just not shared) Today I powered up TOWER2, noted that the UD mounts were good and proceeded to update - the only updates were 6.8.0-6.9.3OS, User Scripts, Community Apps, Fix Common Probs, & Unassigned Devices. Restarted the server and now the UD shares do not automount. If I press the ‘mount’ button the log shows the following: Mar 25 09:08:41 Tower2 unassigned.devices: Mount SMB share '//TOWER/WinVM' using SMB3 protocol. Mar 25 09:08:41 Tower2 unassigned.devices: Mount SMB command: /sbin/mount -t cifs -o rw,nounix,iocharset=utf8,file_mode=0777,dir_mode=0777,uid=99,gid=100,vers=3.0,credentials='/tmp/unassigned.devices/credentials_WinVM' '//TOWER/WinVM' '/mnt/disks/TOWER_WinVM' Mar 25 09:08:41 Tower2 unassigned.devices: SMB3 mount failed: mount error: could not resolve address for TOWER: Unknown error . Mar 25 09:08:41 Tower2 unassigned.devices: Mount SMB share '//TOWER/WinVM' using SMB2 protocol. Mar 25 09:08:41 Tower2 unassigned.devices: Mount SMB command: /sbin/mount -t cifs -o rw,nounix,iocharset=utf8,file_mode=0777,dir_mode=0777,uid=99,gid=100,vers=2.0,credentials='/tmp/unassigned.devices/credentials_WinVM' '//TOWER/WinVM' '/mnt/disks/TOWER_WinVM' Mar 25 09:08:41 Tower2 unassigned.devices: SMB2 mount failed: mount error: could not resolve address for TOWER: Unknown error . Mar 25 09:08:41 Tower2 unassigned.devices: Mount SMB share '//TOWER/WinVM' using SMB1 protocol. Mar 25 09:08:41 Tower2 unassigned.devices: Mount SMB command: /sbin/mount -t cifs -o rw,nounix,iocharset=utf8,file_mode=0777,dir_mode=0777,uid=99,gid=100,vers=1.0,credentials='/tmp/unassigned.devices/credentials_WinVM' '//TOWER/WinVM' '/mnt/disks/TOWER_WinVM' Mar 25 09:08:41 Tower2 unassigned.devices: SMB1 mount failed: mount error: could not resolve address for TOWER: Unknown error . Mar 25 09:08:41 Tower2 unassigned.devices: Mount of '//TOWER/WinVM' failed. Error message: 'mount error: could not resolve address for TOWER: Unknown error '. Downgraded TOWER2 from 6.8.3 back to 6.8.0 and the problem persists. I see no way to downgrade UD ……. Over at the primary Tower I can access the smb shares just fine from Windows 10 (//TOWER) and just fine from Ubuntu (//192.168.x.xxx) I'm am uncertain what the next steps are --- this process has been rock stable for a long time up until today. Thanks folks!

Thanks @CorneliousJD & @jbuszkie!

Howdy folks An odd behaviour has cropped up recently. After some period of time when I go to the WebUI, CP requires me to log in. Is this just a change by CP to access the application from the (docker'ed) desktop --- or should I be concerned that backups are being impacted? Thanks!

I spent a LOT of time a few years back sussing out a solution as a Windows VM without access to an ODD was then a deal breaker for my use. I found 2 workable solutions 1 – use a USB ODD drive and pass that through AFTER booting the VM if speed is of little concern 2 – Blacklist a PCIe card and pass the PCIe SATA card through. Note that you must either flash the PCIe card for ODD (aka IDE mode) use or select a card that works natively with ODD. Because of using the Asmedia ASM1062 chipset - StarTech’s 2 Port PCI Express SATA 6 Gbps eSATA Controller Card - Works out of the box. https://www.amazon.com/gp/product/B00952N2DQ Under flash you can blacklist the device via: label unRAID OS menu default kernel /bzimage append iommu=pt vfio-pci.ids=1b21:0612 initrd=/bzroot Where vfio-pci.ids=(my [id] info from system devices) IOMMU group 34 [1b21:1182] 0a:03.0 PCI bridge: ASMedia Technology Inc. Device 1182 [1b21:0612] 0b:00.0 SATA controller: ASMedia Technology Inc. ASM1062 Serial ATA Controller (rev 02)

Thank you greatly saarg

Main server upgrade appears good. -Windows 10 VM with 1080 for steam streaming of owned games. -Windows 10 VM with 1060, odd sata card, USB card for software suite use. -Windows 7 VM vnc for legacy software use. -crashplan docker -Makemkv Docker with USB odd -Dual parity -Media links from osmc for owned media consumption -Pre-Clear plugin

Sub'd - thank you greatly. This will come in handy when a system update breaks the gui plugin.

Thanks saarg! The other makemkv does not allow me to consistently pass through the ODD. This RDP one, however, works great.

@Djoss - thanks for keeping this most useful docker up-to-date mate!

I do the same at my home. I eventually added parity to the secondary backup server - not because it was required, but because I desired some faulure tolerance on the backup copies.