dlandon

So this happens on every page refresh? UD shouldn't be causing this. I have no idea what it could be.

Read/Write only works in 6.9.

It looks like your remote shares are taking a long time to mount: Jan 29 17:34:48 Microserv unassigned.devices: Mounting 'Auto Mount' Remote Shares... Jan 29 17:35:35 Microserv ool www[13880]: /usr/local/emhttp/plugins/dynamix/scripts/emcmd 'cmdStatus=Apply' Jan 29 17:35:35 Microserv emhttpd: Starting services... Jan 29 17:35:35 Microserv emhttpd: shcmd (175): /etc/rc.d/rc.samba restart Turn off auto mount for all your remote shares and see if that fixes the problem. You could mount them one at a time to see which one is taking a long time.

You have some strange stuff going on. None of your temperatures are showing. Preclear is struggling: Jan 30 07:48:02 Cube nginx: 2021/01/30 07:48:02 [error] 12695#12695: *32314906 recv() failed (104: Connection reset by peer) while reading response header from upstream, client: 192.168.1.29, server: , request: "POST /plugins/unassigned.devices/UnassignedDevices.php HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock:", host: "cube", referrer: "http://cube/Main" Jan 30 07:48:02 Cube php-fpm[12669]: [WARNING] [pool www] child 19751 exited on signal 7 (SIGBUS) after 126.218227 seconds from start Jan 30 08:07:02 Cube rc.diskinfo[58387]: SIGHUP received, forcing refresh of disks info. Jan 30 08:15:01 Cube kernel: sde: sde1 Jan 30 08:15:01 Cube rc.diskinfo[58387]: SIGHUP received, forcing refresh of disks info. Jan 30 08:15:01 Cube kernel: sdb: sdb1 Jan 30 08:19:01 Cube kernel: sdc: sdc1 Jan 30 08:19:01 Cube kernel: sdd: sdd1 Jan 30 08:19:01 Cube kernel: sdf: sdf1 Jan 30 08:19:01 Cube rc.diskinfo[58387]: SIGHUP received, forcing refresh of disks info. Jan 30 08:19:01 Cube kernel: sdg: sdg1 Jan 30 08:19:01 Cube nginx: 2021/01/30 08:19:01 [error] 12695#12695: *32332208 recv() failed (104: Connection reset by peer) while reading response header from upstream, client: 192.168.1.112, server: , request: "POST /plugins/unassigned.devices/UnassignedDevices.php HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock:", host: "cube", referrer: "http://cube/Main" Jan 30 08:19:01 Cube php-fpm[12669]: [WARNING] [pool www] child 63666 exited on signal 7 (SIGBUS) after 86.344191 seconds from start Jan 30 08:19:01 Cube nginx: 2021/01/30 08:19:01 [error] 12695#12695: *32332513 recv() failed (104: Connection reset by peer) while reading response header from upstream, client: 192.168.1.112, server: , request: "POST /plugins/unassigned.devices/UnassignedDevices.php HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock:", host: "cube", referrer: "http://cube/Main" Jan 30 08:19:01 Cube php-fpm[12669]: [WARNING] [pool www] child 9694 exited on signal 7 (SIGBUS) after 43.772320 seconds from start Jan 30 08:23:49 Cube kernel: sdg: sdg1 Jan 30 08:23:50 Cube rc.diskinfo[58387]: SIGHUP received, forcing refresh of disks info. ### [PREVIOUS LINE REPEATED 1 TIMES] ### Jan 30 08:23:50 Cube kernel: sdf: sdf1 Jan 30 08:23:50 Cube kernel: sdc: sdc1 Jan 30 08:23:50 Cube kernel: sde: sde1 Jan 30 08:23:51 Cube kernel: sdb: sdb1 Jan 30 08:23:51 Cube kernel: sdd: sdd1 Start by removing the preclear plugin for the moment and then reboot.

What I was trying to ask is why you feel that is important. It is a designation used by Unraid for unassigned disks. It is not something that can be changed. Maybe you need to move the device to the pool where you can name it like you are wanting.

Have you adjusted the shared memory using the new template from CA?

What is it you want to accomplish?

It's on my list of things to look at, but not a high priority.

I've done about the best I can for now. The information in UD is very dynamic and the table columns change width. I don't have the time right now to spend on purely cosmetic issues.

UD handles it when the array is stopped. If you are having trouble with unclean shutdowns, take a look at this:

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.