[Unraid OS version 6.12.3-rc3 available]

Just reporting in that this release seems to have fixed the "Retry unmounting shares" issue for me.

 

[Cannot stop array: "cannot unmount '/mnt/cache/appdata': pool or dataset is busy"]

Thanks, that command allowed me to stop the array.

I've just updated to v6.12.3-rc3 and tried stopping the array and it worked without having to issue the command.

I'll report back if it happens again.

[Unraid OS version 6.12.0-rc6 available]

I have a question re exclusive shares:

Are exclusive shares only for shares that reference pools? Or are shares on the array that don't use a (old terminology) cache, and are restricted to a single disk also gain the benefit of transparently bypassing FUSE?

I have all my music on a share restricted to a single disk in the array, and also have my backup share restricted to a single disk in the array.

I currently have disk shares enabled to bypass FUSE in situations where I want a little more speed. Eg running a sync from my Windows machine to a share (scan time drops from 4 minutes to 20 seconds when using a disk share while transfer speed is unaffected); or running a media library scan in Logitech Media Server (twice as fast) or Plex (time drops from a few minutes to a few seconds).

It would be great if shares restricted to a single disk would automatically bypass FUSE and get the speed benefits.

This way I can just reference the "user" share directories (rather than direct disk) and in the future if either share fills up the single disk and I allow it to use another disk I don't have to worry about making sure that I've updated all my scripts and shortcuts to reference "user" shares instead of "disk" shares - the share will just start using FUSE transparently.

Thanks for your input!

[Unraid OS version 6.10.0-rc2 available]

17 hours ago, Sarge said:

Good call, I've looked into it some and know there is a point where the Samsung drives will throttle due to temp so wanted some extra cooling anyway.

I heard that the NAND chips run better hot, so you shouldn't add heatsinks (which is why they don't come with them in the first place).

[[6.9.0 betas & 6.9.1] Apcupsd issue when booting]

Have you tried outlining the problem to the apcupsd mailing list? They might know of other users with the problem, or of a change to APC's USB management.

http://www.apcupsd.org/wordpress/support/

It might be a good place to dig around and start the ball rolling on updates to the daemon/within Unraid.

 

[Dockers wanting to update, but don't in the end?]

Confirming I'm seeing the same issue.