dlandon

Not in the UD plugin.

Next time abort the user script, wait a little bit of time, unmount the disk in UD, and then shutdown the server.

That is an issue to take up with LT. Post a defect report.

A disk that is busy can't be unmounted and unRAID will force a shutdown after the timeout so it can shutdown. You will get an unclean shutdown.

Disks not showing up in UD. I don't know any particulars of what disks did not show.

I am getting an error on the system temperature plugin and it is not installing on boot up. Sep 10 05:49:27 BackupServer root: plugin: creating: /usr/sbin/sensors-detect - downloading from URL https://raw.githubusercontent.com/bergware/dynamix/master/archive/sensors-detect Sep 10 05:49:27 BackupServer root: plugin: downloading: https://raw.githubusercontent.com/bergware/dynamix/master/archive/sensors-detect ...#015plugin: downloading: https://raw.githubusercontent.com/bergware/dynamix/master/archive/sensors-detect ... failed (Network failure) Sep 10 05:49:27 BackupServer root: plugin: wget: https://raw.githubusercontent.com/bergware/dynamix/master/archive/sensors-detect download failure (Network failure) I can re-install it just fine. EDIT: On rc8q.

Ok. I stand corrected.

It does because the partitioning of the disk was accepted by unRAID. The disk is not re-partitioned when it is rebuilt if the partition is already proper, the file system in the partition is rebuilt.

What wgstarks did was not necessary, but helped me confirm that the UD partitioned disk would be accepted into the array. What is important when a disk is rebuilt is the partitioning because the file system in the partition is replaced when the disk is rebuilt to what was on the original disk. If the file system on the original disk was XFS, then the replacement disk will be XFS regardless of what file system UD created on the disk. The format compatibility feature of UD is only to prevent situations where a disk is partitioned and loaded with data and then introduced into the array. It is not a replacement for the normal partitioning of disks for the array, or a way to trick unRAID into changing file systems in a partition. Note: This feature may offer an another way to convert file systems. i.e. converting from ReiserFS to XFS. A new disk could be installed and formatted by UD, data copied from the array disk to be converted, and then inserted into the array and parity rebuilt. Do I see a new opportunity for a User Script to copy data from an array disk to a UD disk?

That command will do what you need. It creates the file in the recycle bin. The command puts an empty string into a newly created file in the .Recycle.Bin folder.

Echo "" > /mnt/user/share/.Recycle.Bin/placeholder.txt

Correct. The criticism was that a disk formatted and partitioned anywhere in the unRAID UI would be compatible with the array. Apparently some users formatted disks with UD, loaded them with data and then expected the disk to be accepted into the array without forcing a re-format. Of course parity would have to be built/rebuilt, but that was not the issue. I had the experience where I formatted a new cache disk in rc7 and installed it in the array as a new cache and it was happily accepted by unRAID, but with rc8 it was rejected as an incompatible format because of the partition format requirements for encrypted disks. unRAID is stricter now about the partition format. The UD partition format will now alleviate this problem. The changes to UD will now alleviate incompatibility issues with partitions, but the preferred method is still installing disks into the array and let unRAID format them.

The .Recycle.Bin folder is removed when the purge procedure sees that the folder is empty, or the recycle bin is forced to empty. I guess I don't understand why you see the .Recycle.Bin folder removed. Are you emptying the recycle bin manually? If you set a long time to age the removed files, chances are the recycle bin will not be empty and the folder will not be removed. Or you could set up a User Scripts cron to create a file in the .Recycle.Bin every day, set the age to purge to be something over 1 day, and the .Recycle.Folder will never be removed unless you force it empty.

It did. UD is partitioning disks exactly the way unRAID does.

It did.

Correct. It doesn't matter. UD formats exactly like unRAID.

UD is now creating the proper partition format for the array and if it was accepted into the array without formatting, it is good to go. What you might be confused about is previously a disk would be accepted in pre rc8 versions that weren't the proper partition format. LT says that because of the encryption on disks, the format is now more strict and disks not properly partitioned will not be accepted into the array without a format.

Excellent. Thank you for the feedback.

Initial testing of the partition compatibility was done by me on a 2TB disk (msdos), and on a 3TB disk (gpt) by @johnnie.black. Looks like the format compatibility is working. Be careful though until some more feedback is provided that the partition incompatibility is solved.

A new version of UD is available. The major feature update is the ability to partition a disk in UD compatible with the array partitioning. I have tested this with a 2TB disk, but I don't have a disk larger than that to test gpt partitions. If anyone is willing, I would appreciate it if you could format a disk larger than 2TB and let me know if unRAID accepts it as properly partitioned. The other change is to add some timeouts to the 'df' commands on remote mounted smb and nfs shares to try to alleviate the hangs when a remote share goes off-line. The smb 'browseable' parameter is now set properly when no smb users are found.

I just looked at the code and I see the situation you are seeing. If you don't have any users defined, the share is always browseable and you'll see in the UD log a message about no valid smb users defined and the share can't be accessed. I will change this so the 'Yes (hidden)' setting will in fact make the share not browseable.

Go to a command line and type: 'nano /etc/samba/unassigned.devices/duplicati' and see what the 'browseable' parameter is set to. If set to 'no' it should not be browseable. i.e it should not show in the 'Network'. @Squid is right. It can take a while for the setting to take effect. I don't see any users listed under the smb settings. Do you have any users set up for your server?

The way it works is: 'Yes' - share shows when 'Network' is clicked in Windows. The samba parameter 'browseable' is set to 'yes' 'Yes (hidden)' - share does not show when 'Network' is clicked in Windows. The samba parameter 'browseable' is set to 'no'. Both are accessible with '\\Tower\slare'. This is how it works for me.

As it turns out this is not the total answer to the format and partition incompatibility. After some testing, I can't format a disk with UD and have it accepted into the array. I'm awaiting some help from LT or others knowledgeable on the format and partition layout for unRAID so I can work this out.

Yes is visible. Yes (Hidden) is not visible. Both have permissions as set in the Settings->Unassigned Devices.