dlandon

Ok.

It is possible, but the plugin does not do that at this time.

Fixed in the next release.

Correct, but the plugin applies the governor to all cores.

Not at this time. The governor applies to all cores.

I'm not sure what you are doing but if UD does not have the disks mounted, you are doing something out of the ordinary and I'm not sure how to help you. Normally you mount the devices with UD and then access the disks through a samba share or directly on the mount point.

You will have that problen until you upgrade to 6.10.

Please post your diagnostics and a screen shot of the device on the UD page. Your explanation doesn't make any sense. If the 'Mount' button is grayed out, how did you mount the device?

What version of Unraid? There is a bug in older versions of Unraid where this would happen. The "Array" designation shows up because the device designation is "sdj" and not "Dev 2" after being plugged back in. That's not supposed to happen and has been fixed in 6.10.

UD sometimes can't delete partitions or the entire disk. Try this: Click on the blank mount point for the partition amd enter a mount point name. This will apply a disk label. Take the disk to a Windows computer and remove the disk partition with Windows.

Your best bet is to format it on a Windows computer.

Windows creates a small recovery partition and that's probably what you see with part1. Just leave it and ignore it.

How did you format the disk? There is a partition, but no file system. Until you get a mountable file system, your script will not work because it is only executed when the disk mounts. The disk will not mount without a valid file system.

It's already in Unraid. Has been for a while.

That happens when the disk is removed (disconnected) before it is unmounted. You'll need to reboot.

Remove the device from your server and it won't show as an unassigned device.

Looks like a disk/controller/cable issue: Apr 24 00:10:02 Tower kernel: blk_update_request: I/O error, dev sdg, sector 72 op 0x0:(READ) flags 0x80700 phys_seg 6 prio class 0 Apr 24 00:11:01 Tower kernel: sd 13:0:2:0: [sdg] tag#917 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s Apr 24 00:11:01 Tower kernel: sd 13:0:2:0: [sdg] tag#917 Sense Key : 0xb [current] Apr 24 00:11:01 Tower kernel: sd 13:0:2:0: [sdg] tag#917 ASC=0x4b ASCQ=0x3 Apr 24 00:11:01 Tower kernel: sd 13:0:2:0: [sdg] tag#917 CDB: opcode=0x28 28 00 91 87 ff 8f 00 00 15 00

New release. Over the last few weeks I have been tracking down a problem where the cron purge of aged files has been failing. I tracked it down to the trashsizes cron and the purge cron both running at the exact time on the hour and conflicting with each other. I've sorted it out, so it works now. This mostly showed up with large recycle bin contents. After upgrading and the cron purge removing aged files, you may see a significant decrease in the size of your Recycle Bin contents. This will happen if the cron purge of aged files has been failing. It will now catch up and purge aged files properly. It is nothing to be concerned about as it is only the aged files being purged catching up.

You have to understand that table management in UD is a total bear, because of the way Unraid is designed and the constant refresh of the UD page to keep information current. I'm not comfortable with any ideas I've come up with yet. I'm also hesitant to do changes to respond to one user's request. I want features to be applicable to all users. That being said, I'll ponder it a bit and see if I can come up with something that might work. Edit: I do see a way you can organize the passed through disks together. Give each disk an alias name like: Pass1, Pass2, Pass3, etc and all the Pass... names will be grouped together on the UD page.

Fix in the next release.

What doesn't work? Post your diagnostics and a screen shot of the settings.

Looks like I don't set up the directory to exclude properly when it's a sub-directory. Looking into it now.

That's built into Unraid. I have no control over it. Feel free to post a feature request.

Click on the 'X' to remove the banner. There is no way to prevent them from showing up.

Click on the double arrows on the UD webpage to refresh the configuration. If that doesn't work, post your diagnostics.