dlandon

Or send me an old/cheap disk formatted apfs.

The remote shares are unmounted with the force switch set and will always unmount.

I was told it didn’t work.

I was told it didn’t work.

Done.

Or, upgrade to 6.9 and move the disk to the Pool. You'll then have all the settings for temperatures you want.

Click on Help and you'll see the commands.

I am building a preliminary machine learning Docker for testing. PM me and I'll make arrangements for you to access the Private Docker. Access and support for this preliminary version will be very limited until the GoFundMe is successful.

No. See here and read the release notes; https://forums.unraid.net/bug-reports/prereleases/unraid-os-version-690-beta25-available-r990/page/9/?tab=comments#comment-10413&searchlight=1

Sounds like the package I put in UD+ was not the right one. Slackware packages are a bit hard to find. Let me do some research.

What is it you don't like? You change the switches that often? Why? Maybe you shouldn't be doing this on a mobile device, or get a better data plan. Not worth the effort for very little gain. The UD page refreshes the same way as the array disk pages. The refresh is to keep the remote shares online status up to date, to refresh the GUI so it reflects the proper server online status for remote shares, and the disk status like preclearing and scripts running for physical disks. I worked very hard to get the refresh working so the GUI would show the correct status of UD devices, and now it appears you are wanting to go back. I'm really not too keen on doing that, even as an option.

I added a package that should allow mounting of APFS. Update UD+ and see if you can mount an APFS disk. I do not have any way of testing.

Did you look at the help on the UD page? There is a UD command to do the disk spin down that is respected by Unraid: '/usr/local/sbin/rc.unassigned spindown devX' - spin down a disk. The devX is the device name in the UD page. If the device name is 'Dev 1', then use dev1 as the device to spin down. SSDs will not spin down. Just be sure to synch the mount point so all writes are done, then maybe wait a short amount of time, then issue the UD spin down command.

Sorry, I just thought of an answer. Look at the help on the UD page. There is a command you can issue to spin down a disk. You could add it to the end of your script.

Yes, the minimum is 15. You can't change that for UD disks.

Unraid 6.9 takes over the disk spin down and any commands you issue for spin down will be removed.

UD mounts and unmounts disks. It does not have anything to do with read/write operations.

What version of Unraid?

I'm going to issue a new release today that will implement the change of UUID on an encrypted disk.

You are having disk issues that need to be fixed: Jan 15 21:08:02 unCube kernel: print_req_error: I/O error, dev sdam, sector 22319448 Jan 15 21:08:02 unCube kernel: sd 10:0:12:0: [sdam] tag#5046 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 Jan 15 21:08:02 unCube kernel: sd 10:0:12:0: [sdam] tag#5046 Sense Key : 0x2 [current] Jan 15 21:08:02 unCube kernel: sd 10:0:12:0: [sdam] tag#5046 ASC=0x4 ASCQ=0x0 Jan 15 21:08:02 unCube kernel: sd 10:0:12:0: [sdam] tag#5046 CDB: opcode=0x8a 8a 00 00 00 00 00 01 54 95 60 00 00 03 f8 00 00 Jan 15 21:08:02 unCube kernel: print_req_error: I/O error, dev sdam, sector 22320480 Jan 15 21:08:02 unCube kernel: xfs_destroy_ioend: 502 callbacks suppressed Jan 15 21:08:02 unCube kernel: XFS (sdam1): writeback error on sector 22288728 Jan 15 21:08:02 unCube kernel: XFS (sdam1): writeback error on sector 23271504 Jan 15 21:08:02 unCube kernel: XFS (sdam1): writeback error on sector 23361616 Jan 15 21:08:02 unCube kernel: XFS (sdam1): writeback error on sector 23451728 Jan 15 21:08:02 unCube kernel: XFS (sdam1): writeback error on sector 23541840 Jan 15 21:08:02 unCube kernel: XFS (sdam1): writeback error on sector 23601264 Jan 15 21:08:02 unCube kernel: XFS (sdam1): writeback error on sector 23846368 Jan 15 21:08:02 unCube kernel: XFS (sdam1): writeback error on sector 24492552 Jan 15 21:08:02 unCube kernel: XFS (sdam1): writeback error on sector 24874048 Jan 15 21:08:02 unCube kernel: XFS (sdam1): writeback error on sector 26049528 Jan 15 21:08:12 unCube kernel: scsi_io_completion_action: 5387 callbacks suppressed Jan 15 21:08:12 unCube kernel: sd 10:0:12:0: [sdam] tag#4334 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 Jan 15 21:08:12 unCube kernel: sd 10:0:12:0: [sdam] tag#4334 Sense Key : 0x2 [current] Jan 15 21:08:12 unCube kernel: sd 10:0:12:0: [sdam] tag#4334 ASC=0x4 ASCQ=0x0 Jan 15 21:08:12 unCube kernel: sd 10:0:12:0: [sdam] tag#4334 CDB: opcode=0x35 35 00 00 00 00 00 00 00 00 00 Jan 15 21:08:12 unCube kernel: print_req_error: 5387 callbacks suppressed Jan 15 21:08:12 unCube kernel: print_req_error: I/O error, dev sdam, sector 3907018936 Jan 15 21:08:12 unCube kernel: sd 10:0:12:0: [sdam] tag#1785 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 Jan 15 21:08:12 unCube kernel: sd 10:0:12:0: [sdam] tag#1785 Sense Key : 0x2 [current] Jan 15 21:08:12 unCube kernel: sd 10:0:12:0: [sdam] tag#1785 ASC=0x4 ASCQ=0x0 Jan 15 21:08:12 unCube kernel: sd 10:0:12:0: [sdam] tag#1785 CDB: opcode=0x8a 8a 00 00 00 00 00 00 00 00 c0 00 00 00 40 00 00 Jan 15 21:08:12 unCube kernel: print_req_error: I/O error, dev sdam, sector 192 Jan 15 21:08:12 unCube kernel: XFS (sdam1): metadata I/O error in "xlog_iodone" at daddr 0xe8e06078 len 64 error 5 Jan 15 21:08:12 unCube kernel: XFS (sdam1): xfs_do_force_shutdown(0x2) called from line 1271 of file fs/xfs/xfs_log.c. Return address = 000000004922461f Jan 15 21:08:12 unCube kernel: XFS (sdam1): Log I/O Error Detected. Shutting down filesystem Jan 15 21:08:12 unCube kernel: XFS (sdam1): Please umount the filesystem and rectify the problem(s)

It is sticking, but the Edit Settings does not show it correctly. It is fixed in the next release. For the moment, hover your mouse over the edit settings icon and that will display the correct shares status. When UD sets up a SMB share, it can take a few minutes before the share shows up. It is not necessarily immediate. Be careful when making changes to the smb-extras.cfg file. It's easy to break things.

When the share switch is turned on it shows properly in the tool tip. It is not showing properly in the Edit Settings page. This will be fixed in the next release.

You have several options: Upgrade to 6.9 and put the disk in the pool. The encryption will work on that drive just like array disks, Set the password in UD settings, mount the disk, then go back to UD settings and blank the password. Provide the key file and then delete it once the UD disk has mounted. The UD encryption feature was to allow a disk removed from the array to be mounted and data removed as necessary. I'm not sure of your use case, but for what you want, the array encryption is probably a better answer. You do understand that a person needs multiple pieces of the server to be able to access the encrypted disk? Just having the physical disk is useless. If someone takes your whole server, to access your one encrypted disk, you probably have bigger problems.

I have changed the CA template for Zoneminder to include ES and none of the hook processing, It was very complicated with all the environment variables that needed to be set for each person's preferences and was becoming very confusing to users. What I want to do is develop a new Docker Container that will be for Zoneminder, ES, and hook processing pre-configured without all the environment variables. The Yolo models will be installed in the Docker so they don't have to be downloaded. Everything for ML will be pre-configured with the exception of opencv with GPU support and specific hardware support like coral edge tpu. GPU support is unique on each system and Nvidia has licensing restrictions that prevent distribution. I have created a GoFundMe campaign to fund the development, enhancement, maintenance, and support of this new Docker.

The Docker from CA does not include hook processing any longer.