dlandon

The idea is to support all formats natively supported by Unraid, and add the plus packages for other file format support and disk formatting. Fairly painless.

Post diagnostics.

Like I said a work in progress. Just uploaded the plugin template for testing.

That is in preparation for moving all the packages not normally needed to UD+ for those who use UD skinny. i.e. No hfsplus or exFat format mounting, no nmap for NFS server lookups, and no formatting or deleting partitions. It is still a work in process. UD will not install any of those packages in the upcoming release. UD+ will have to be installed for the additional features. I am not a fan of all of the packages being installed that few people use.

Your log is full of this: Dec 27 22:54:27 someflix-unraid kernel: sd 7:0:2:0: attempting task abort! scmd(00000000f62fb0b3) Dec 27 22:54:27 someflix-unraid kernel: sd 7:0:2:0: [sdd] tag#352 CDB: opcode=0x85 85 06 20 00 d8 00 00 00 00 00 4f 00 c2 00 b0 00 Dec 27 22:54:27 someflix-unraid kernel: scsi target7:0:2: handle(0x000b), sas_address(0x5001438022e4ed89), phy(9) Dec 27 22:54:27 someflix-unraid kernel: scsi target7:0:2: enclosure logical id(0x5001438022e4eda5), slot(42) Dec 27 22:54:29 someflix-unraid kernel: sd 7:0:2:0: task abort: SUCCESS scmd(00000000f62fb0b3) I'm not a disk expert, but it looks like a hardware issue you need to sort out. @johnnie.black is better at this than I am. It looks like your disks are also only at 3Gb when they are capable of 6Gb. That may be why you are getting the lsof timeout issue. As for the remove partition, I don't see an error. You should sort out these issues. It is affecting several disks.

That message is not from the remove partition command. You have a remote mount that has gone off line. Post complete diagnostics.

I've added a log message to the remove partition so we can see any message from the command. Update UD and try again, If it doesn't work, I'll give you a command to run in a terminal session.

Several problems here. I'm going to adjust the time out for nfs unmounts, but you also need to allow enough time for shutdown for the unmounts to time out. You need to adjust the shutdown timers as suggested here: Allow for the unmounts to take about 45 seconds for each remote share you have mounted. Your server would have shut down when the unmounts timed out, but the server array shutdown timer ended first so the shutdown was forced.

Click on the four squares and see if there are issues to be corrected.

I have updated the UD plugin with the following changes: There is a configuration option in the UD settings to add 'discard' to SSD devices. It defaults to 'Yes'. I recommend turning this off if you have set up a periodic trim. The best policy seems to be not mounting disks with 'discard' and do a daily trim. Copy configuration files to tmpfs to cut down on the constant reads of the flash drive for UD configuration parameters. While this doesn't affect the wear on a flash drive, the reads from a flash drive are slower than ram. All configuration changes are copied to the flash drive so it is up to date. The following will be deprecated in UD for Unraid 6.9: hfsplus file format support will be removed from UD. With the extensive capability of remote mounting SMB and NFS shares, there should be minimal need to mount an hfsplus disk in UD. If you have an hfsplus or ext4 backup disk you use for Unraid, I recommend you reformat it or mount it remotely from another computer. The only formats that will be created by UD are xfs, btrfs, and ntfs. The xfs and btrfs formats are native to Unraid. Ntfs is built into Unraid and is a popular disk backup format. Exfat and fat32 can be created on a computer. Mount encrypted disks read only so files from a previous array disk can be extracted. Those of you using encrypted disks for VMs or Dockers will need to move them to a disk in the cache pool in 6.9 or to the cache in previous versions, or don't encrypt them. The minimum version of Unraid supported will be changed to 6.6 or 6.7. It is difficult to test UD for older versions of Unraid and you really should update. For those of you still using an older version of Unraid should upgrade Unraid to the latest stable version. The idea is to get UD back to what it was originally intended for. It was never intended that UD be used for array type operations. i.e. VM and Dockers.

All disks mounted by UD will have a spin down time set at 30 minutes, This cannot be changed.

The issue has been solved.

I updated and can no longer connect. My bad. After updating the Wireguard plugin I reset my router and my IP address changed. Once I fixed that, all is set.

Remove the files at \flash\config\plugins\unassigned.devices\packages\ or go to a terminal session and enter the command: rm /boot/config/plugins/unassigned.devices/packages/* Then attempt install again. If it happens again, check your flash for corruption.

That would not work because UD still has the others recorded in the configuration file. They would all be changed each time one was changed. The drives have to each have a unique ID. I suspect the drives are all in the same model docking station and the disk ids are same. They won't mount because of the duplicate ids. Check in some earlier posts on how to change the disk id and see if they can be changed,

Are those drives in a docking station? All the same kind?

My only concern with the empty partition is the potential delay in mounting that drive. Three minutes for a ntfs disk is a long time! Btrfs can take longer than other formats, but I've not seen a ntfs disk take that long.

That's not what I see. Did you install a skin plugin?

I don't see anything in your log. It works for me Go to the UD web page and click on the '+' and show a screen shot.

I've updated the zmeventnotification server to 5.2 preliminary. Once it is released as stable I'll refresh the docker. There are a lot of changes with this version and the hook processing will fail unless you update the secrets.ini and objectconfig.ini files. The 5.2 defaults are copied into your config folder. I don't use hook processing so I cannot test it. If anyone can check it out and let me know if there are any adjustments I need to make.

Remove the mount time out on physical disks.

'Yes' Capital Y.

Click the 'Format' button?

Set the destructive mode in UD settings.

Thanks. Why is there an empty partition? Can that be deleted? This caused one issue that didn't mean anything, but caused a time out checking for a precleared disk. UD checks for a preclear signature if there is no file system on the partition. After reviewing the log again the I see the mount took over three minutes. I am baffled why a mount would take longer than three minutes.