dlandon

Read the second post about best practices.

Getting a console error: sh: /usr/local/emttp/plugins/community.applications/scripts/removeCron.php: No such file or directory on 2016.11.11 version.

I thought Bonienl reverted those changes. Sent from my LG-D852 using Tapatalk If he did, I missed the memo on that.

It's a harmless message and occurs from the www.conf file not found in previous versions. I'll update the plugin to not display that message. This change involving the docroot is in anticipation of a change from emhttp. The path to the webgui wouldl change and the plugin will handle emhttp and a newer webgui path by looking it up. If the www.conf file is not found, the docroot defaults to /usr/local/emhttp for backwards compatibility.

UD cannot handle the backslash in the name. You'll have to manually edit the /flash/config/plugins/unassigned.devices/samba_mount.cfg file and remove it manually.

Look at the UD log. There will be a log entry on why is isn't mounting. Probably a permission (credentials?) issue. I clicked on the Log button on the right but nothing appears in the Unassigned Devices Log. I'm able to get into the share from my Windows PC, and the plugin did find the share after I put in my user and pass for that share (located on the Windows PC) but still doesn't mount. Did you let UD find the server and share, or did you manually enter it?

Look at the UD log. There will be a log entry on why is isn't mounting. Probably a permission (credentials?) issue.

Yes, but don't post the same question in multiple threads. sorry... was coming back to edit that i got it changed after stopping the array.. thanks for the lead in the other. You don't need to stop the array. Just unmount the device. Click 'Help' for an explanation. You can hover your mouse over the device name for a tool tip.

Yes, but don't post the same question in multiple threads.

Mounting devices in the cloud is not something I see UD doing. I am concerned about security issues. I am not experienced or qualified to handle the security with this. I'm not sure this is something unRAID should really be doing.

unRAID sees that drive installed in the server. Check your drives and drive bay again. Does the drive bay you are using think the device is still installed? Is the drive mounted in different drive bay? [1:0:2:0] disk ATA ST31000520AS CC38 /dev/sdc /dev/sg3 state=running queue_depth=32 scsi_level=7 type=0 device_blocked=0 timeout=30 dir: /sys/bus/scsi/devices/1:0:2:0 [/sys/devices/pci0000:00/0000:00:15.0/0000:03:00.0/host1/port-1:2/end_device-1:2/target1:0:2/1:0:2:0]

Setting the device to share and setting "No" for SMB security shares the device as public. Root is not a valid SMB user.

Fixed in latest release.

On the UD page there is a log button in the upper right. See what the log shows when trying to mount the network device.

After doing some research on WINS, it seems to be old technology not worth the effort. Forget this request.

Read the second post on this thread about best practices. There is an explanation about UD showing the disk temperature. I think in your case this is what is happening. UD is not monitoring your drive so it looks to be spun down. Based on your quick test, the drive is spun up. You need to see what is spinning it up. If UD is showing '*' then it is not monitoring the disk at all.

What kiind of disk is the UD disk, and what are the array disks?

Some background information. Latest version of Bleeding Edge has made unrestricted reboot and shutdown available. This means you can do a reboot or shutdown at any time without stopping the array first. In this situation the programs /sbin/reboot and /sbin/poweroff are called which initiate a system reboot/shutdown and in the process stop the array (rc.local_shutdown) to ensure a clean finishing. In case the array can't be stopped (meaning emhttp is hanging) the reboot/shutdown process continues with a hard cut-off after 60 seconds (this time is configurable). I really like this new feature. I have seen on my test system where booting in the gui mode would lock up the server when shutting down in any way, whether from the command line or gui. I don't know if this is a bug or an issue with my test server. I don't have the time or desire to try to troubleshoot this because I really don't use the boot gui mode.

I just had an interesting situation happen to me that I've not seen before. I am running the mainline version 6.3.0-rc1 and have found that my Windows 10 VM that I use as a desktop stutters with heavy cache drive activity. My Dockers and VM are on my SSD cache drive. I have 32GB of memory. I set the 'Disk Cache 'vm.dirty_background_ratio' (%):' value to 5% and the 'Disk Cache 'vm.dirty_ratio (%):' to 10%. This is half the default values in both cases. The stuttering stopped. I'm wondering if Linux changed some of the disk buffering that is now causing this issue for me. IMO, I think the default values may have been fine in the single digit GB memory days, but are way too high for large amounts of memory. I think single digit values for these two settings are best. Anyone else have any issues like this?

Confirm whether or not it is in standby with the following command: /usr/sbin/hdparm -C /dev/sdf Then run this command: /usr/sbin/smartctl -A -d sat,12 /dev/sdf | /bin/grep -m 1 -i Temperature_Celsius | /bin/awk '{print $10}' and you'll see the drive is in standby and the temperature is available even when it is in standby. UD chooses to show '*' to indicate that it is not spinning. The pre-clear plugin shows the temperature even if it is not spinning. Just programming preferences. UD shows the status of the disk the same way as the array drives are shown. Yes I'm sure.

Just upgraded to bleeding edge 2016.10.09i and when I reboot the reboot page comes up and then the system hangs hard at "acpid: exiting" on the console. The reset button does not work, only holding the power off button until power goes off. What more information can I provide for you? EDIT: Running 6.3.0-rc1. EDIT: I think I am having hardware issues. It seems to have something to do with booting in the gui mode. I'll work on it some more and see if I find the cause.

Can someone clarify this for me please? The temperature indication will be a '*' when the drive is spun down. If a temperature is shown, the drive is spinning.

It was removed because it doesn't work well with the new builtin powerdown process. LT will be adding in diagnostics when the server is shutdown. I expect more logging and archiving of logs could be added as they get time. You could post a feature request for the log archiving.

Is it appropriate to leave the bleeding edge Dynamix plugin on 6.2.1?

Is anyone having any idea? Thanks a lot. Make a change is the Recycle Bin settings and Apply. The message will go away.