aim60

I have a drive in UD formatted NTFS and set to automount and share. During the last boot the drive was disconnected. After hot plugging the drive, it mounts successfully, and I can browse the files from the GUI. However, I can't get it to share. I have tried combinations of replugging the drive, unmounting/remounting, share yes/no, and refreshing the UD disks and configuration. Any suggestions other than rebooting? UD 2022.06.19 and Unraid 6.9.2 Thanks

Items will be added to the display for several days. Then, no additional items will be added till I press clear.

Is there a way to increase the display buffer? Thanks

I ran across an article whose author claimed that on recent versions of qemu, discard=unmap was functional on virtio disks. So I did some testing. I have not run all permutations, but have tested: Unraid 6.9.2 UEFI and Seabios VMs Q35-5.1 and i440fx-5.1 VMs Windows 10 and Windows 11 with the latest virtio drivers, virtio-win-0.1.196.iso Ubuntu 21.4 raw and qcow2 vdisks vdisks on XFS and BTRFS disks vdisks with and without the copy-on-write attribute set In all cases, the virtio disk was functionally equivalent to a virtio-scsi disk. On file deletion, windows unmapped blocks immediately. Linux unmapped blocks after running fstrim. https://chrisirwin.ca/posts/discard-with-kvm-2020

For those of us with removable drive bays, should we be doing anything after unmounting a drive, before physically removing it?

Its for this kind of issue that binhex isolated preclear in a docker.

Once the plexpass is associated with your plex account, connect to your plex server using the web interface. Logout of your plex account, then login again. You’re done. You now have all the features of plexpass. Binhex’s plexpass docker gives you access to beta releases, not additional features.

Was waiting for a 6.8.1 stable that fixed the problem Settings-->VM Manager-->DIsable VM function does not work without stopping the array. If an 6.8.1-RC seems stable, and it is the only way to fix the problem, I'll probably jump early.

I'm running 6.6.7. After running preclear, I am attempting to format a new 8TB drive. I updated UD, installed UD Plus, and enabled Destructive Mode. Clicked the red X, and entered Yes to remove the partition. The log says that the partition is being removed, but it's not. The red X comes back. fdisk -l shows that the partition still exists. Running parted returns "parted: error while loading shared libraries: libreadline.so.8: cannot open shared object file: No such file or directory". I tried removing UD and UD Plus, removing their plugin folders in flash/config/plugins, rebooting, and reinstalling. Same result. Any ideas? tower7-diagnostics-20200107-0943-M.zip

They changed their development plans. AES-NI is no longer a future requirement. Mentioned here: https://www.netgate.com/blog/pfsense-2-5-0-development-snapshots-now-available.html

@binhex, consider adding this information to the first post. It will help new users decide which docker to use.

For experimentation, I'm running two Plex dockers (one LinuxServer and one Binhex), using different appdata folders. Since you can't change the port that Plex listens on (38400), I needed to assign a different IP address to one of the dockers. So the Binhex docker is running on Custom:br0, and a fixed IP address. br0 is a Linux bridge, not a Docker bridge, so port mappings are not required. Its like Host mode. I'm still on 6.6.7, but that shouldn't matter.

While testing the "Virtual Machine Wake On Lan" plugin, I discovered that I had two VMs using the same MAC address (sloppy editing of the XML's). It would be useful if Fix Common Problems could scan the docker configs and VM configs for duplicate MACs, and the docker configs for duplicate IP's.

Hi Thanks for the great work. Could you please add md5deep. Compiled version here: http://packages.slackonly.com/pub/packages/14.2-x86_64/system/md5deep/md5deep-4.4-x86_64-2_slonly.txz Thanks