dlandon

I just moved my ownCloud docker to your version and I am very pleased with your implementation. As you know ownCloud does not allow downgrading to an earlier version so updating ownCloud through ownCloud and then re-installing the docker could take the version back if the docker is not updated. I like that your ownCloud docker will update ownCloud when it is started. Including MySql is also a plus so a separate docker does not need to be installed. The placing of apps and other settings outside the docker image prevents breaking ownCloud if the docker is reinstalled. All of this is important to me because I depend on ownCloud in my business for calendars and photo sharing on smart phones. I can't afford for it to break. Nice job! Keep up the good work.

UD and SNAP cannot be run at the same time. Remove SNAP and rely on UD for mounting your devices. SNAP has been deprecated and has not been tested on later versions of unRAID 6.0. If you remove SNAP and the device is still not detected by UD, let me know and we can troubleshoot further.

All devices not assigned to the array are shown in UD. There is no way to block a device.

Only physical devices can be "unshared". Remote SMB/NFS mounts are always shared. I'm not sure why you would want to mount a remote share and not share it on unRAID.

Should be OK, I recently connected one of my UD disks to a different controller and it was detected as usual. UD devices are detected by device serial number and moving to another disk controller/port will not affect the detection of the device.

Set Enable SMB Security to "Yes Hidden" in Settings->Unassigned Devices. All UD shares will be hidden.

Iso files and remote shares are mounted locally on unRAID at /mnt/disks/... and are shared on SMB and NFS if set in Settings->Unassigned Devices. An iso is only shared and VMs can browse the SMB share. It is not presented as a cdrom to a VM. You can mount an iso directly to a VM by editing the VM and adding the iso as a mount. A remote share mounts the NAS/Server on unRAID at /mnt/disks/... and shares it via SMB or NFS if configured.

When UD shares a device, permissions are set to the users defined in unRAID. You will need to provide a user name and password to access the share. This access is controlled in Settings->Unassigned Devices. You grant access to the UD shares based on the user permissions set there. The settings apply to all UD shares.

It sounds as if you are trying to span disks. UD currently cannot handle that, and I don't know how you could develop a script to do what you want.

however my SSD is formatted with btrfs, which i have been lead to believe is better suited for my use case (please correct me if i am wrong). My question is, will trim work with btrfs, or will i need to reformat the drive to xfs or ext4 if i want trim to run? Thank you, Rich Only xfs and ext4 drives are mounted with discard. UD doesn't mount btrfs with discard as an option.

Chill out for a while. Enjoy the weekend.

I have several scripts that I used to schedule by adding a .cron file to dynamix to be added to the crons to be run. Your User Scripts means I can get rid of the .cron file and manage everything with the gui. Nice work! FYI: You are not cleaning up the old .txz files when User Scripts is updated. Not really a problem, just a cleanup issue.

Very nice. You want me to redirect the output of the script to a log file with the option to display it? Hmm. Yes, I like that idea.

Very nice.

echo "Starting the real script" echo "/path/to/the/actual/script.sh" | at NOW -M > /dev/null 2>&1 or echo "Starting the real script" at -f/path/to/the/actual/script.sh now 2>&1 /dev/null

Maybe add a second button to run the script in the background. That way the user could choose how to run the script without having to make script changes.

How about the option to run the script in the background so the webgui does not get tied up with the script. I just created a script to back up my VM and it takes a while. I'd like to be able to run the script and move on to other things while it runs. I will add a notification event to the script let me know it is done.

Only xfs or ext4 formatted disks.

It's automatic.

+1 Drives formatted with xfs or ext4 will be mounted by UD with 'discard' which enables trim on SSD devices.

I just added some additional information to the OP. I see some trying to get performance improvements from a VM when they have not configured the VM properly to start with. In general, you must boot a Windows VM in OVMF, and not over provision CPUs and memory. Get a good performing VM set up before trying to pin CPUs for additional performance.

Since yesterday, after a power failure I can't access the drive. Any idea why I can't access the share and how to solve it? Thankyou Gus Check UD settings. It appears the SMB settings do not have a user defined for access to this drive.

We need more information. What version of unRAID? What does it mean to mount with no permissions? I assume you are mounting the drives NTFS? So Windows can browse to the drive, but not write to it? Check the UD log. It sounds like the drives are mounting read only. The log will give more information about the drives mounting. Sometimes NTFS drives can't be mounted read/write and UD will go ahead and mount them read only so they can at lease be read. The log will give more information.

How are you backing up to the external disks? Why don't you unmount the drives after the backup? There is no reason to leave them mounted for a once a week operation.

Several problems: Fix this: append intel_iommu=on vfio_iommu_type1.allow_unsafe_interrupts=1 pcie_acs_override=downstream isolcpus=8-15,24-31 initrd=/bzroot I don't think the cpus got isolated properly. Why are you adding all the other Linux options? Generally those are not necessary. The SSDs are probably not a problem. Don't be overly concerned with that right now. Is the VM booting in OVMF? Start with getting the VM working this way: Add the isolcpus properly to the syslinux.cfg. Booting with OVMF. The GPU has to support UEFI boot. Don't add any of the Linux options in the syslinux.cfg and just get the VM working with the GPU. Set min and max memory the same. That will turn off ballooning.