JimJamUrUnraid

This did not fix the "not available" message on my official Tautulli docker.

The disks in question haven't spun down in the last 21 hours.

I removed that plugin, we will see in the coming days if those SAS disks go into standby on their own.

I have not loaded any new plugins recently that I recall. This morning I did redo my docker setup.

Yes, multiple times. Diagnostics attached kioshi-diagnostics-20230402-1442.zip

All disks don’t spin up at the same time. Disks will only spin up when they are accessed. But a SAS disk will not go into standby unless the “SPIN DOWN” button is clicked.

I guess I will rephrase this… When I click the green orb next to an individual SAS drive, the SAS disk will not spin down. When I click the “SPIN DOWN” button at the bottom of the Unraid webview for the “Main” tab it will successfully spin down all of my disks, including the SAS disk that would not previously spin down by itself.

Why is it functioning differently than individually spinning down a single disk?

I'm getting some conflicting behavior from this plugin ever since I updated to 6.11.5 My SAS disks refuse to spin down manually or when I click the green orb. If I click the "SPIN DOWN" button at the bottom of the Main array page, the disks will spin down seemingly normally and then wake up whenever accessed.

Is anyone having issues with western digital drives and this plugin? It seems as though all of my western digital drives don’t spin down.

Even on my iPad and Android tablet I have to tap menu items 5-6 times for it to register. Same holds true on my iPhone. It really can’t be that much work for a real web developer.

Please update the web experience to a responsive one. The current web view is unbearable.

I wanted to give the server a few days to see what would happen. I have 2 SAS disks are doing some weird things. Nothing is showing in the open files plugin or the file activity plugin on these drives. Disks 14 and 15 (sdj & sdq) are SAS disks that would spin down before updating to 6.11.5. The syslog does show the disk sometimes spinning down (I have not seen it actually spin down). But most of the time the syslog shows this message and then never spins down: Feb 1 03:34:36 Kioshi SAS Assist v2022.08.02: Spinning down device /dev/sdq Feb 1 03:34:38 Kioshi emhttpd: read SMART /dev/sdq

I jumped the gun removing my diagnostics and claiming it works. I have the same problem, it seems like “read SMART” prevents my SAS drives from spinning down. Certainly whenever I click the green orb, the SAS drive doesn’t spin down followed by the read smart message.

Uninstalled and then reinstalled. Restarted server. Clicked the ball next to the drive to try and spin down the disk. No go. Attached are my diagnostics... Seems to be working now

Hello, this plugin has been saving me about 25 watts regularly, so thank you for creating it! It has been great. I just upgraded from 6.9.2 to 6.11.5 and went from SAS standby working on 6.9.2 to not working on 6.11.5. Can you let me know what logs I need to look at and where they are located to try and track this down? Thank you!

What about how the setting page for the recycle bin doesn't show any thing in the recycle bins across all my shares? It used to show the total space consumed by recycle bins and allow me to empty them... Have those features been taken away? I rebooted the server to do some maintenance and now it is working...

I have attached the output for the above command. I don't see anything pertaining to recycle bin, but it is logging somethings. unraid.txt

Nothing is output when I run that command.

Here is my diganostics. I don't see any deleted files in the log, but I have deleted files in the .Recycle.Bin folder, and I have deleted files recently that show in the .Recycle.Bin folder.

I am having an issue where deleted files are not making the UI show any files to be deleted. Just like this person. What is the fix to make this work again?

A recent update started to force SMB 2.1, which has broken one of my SMB connections (the device does not support anything higher than SMB1). How do I go about forcing SMB 1.0 for that particular connection? I have viewed the settings for this particular connection and it says the script file resides at /boot/config/plugins/unassigned.devices/xxxxxxxxx.sh but there is no such file within that directory. Any guidance would be appreciated.

I just uninstalled and reinstalled the plugin. That seemed to fix the issue.

When trying to update the plugin I am getting this: plugin: updating: unassigned.devices.plg plugin: downloading: "https://github.com/dlandon/unassigned.devices/raw/master/unassigned.devices-2020.12.20a.tgz" ... failed (Invalid URL / Server error response) plugin: wget: "https://github.com/dlandon/unassigned.devices/raw/master/unassigned.devices-2020.12.20a.tgz" download failure (Invalid URL / Server error response) Also, the unassigned devices portion of the main tab in unraid is no longer present. looks like the plugin isn't installed even though it is. The settings page for unassigned devices is just blank... Not sure where to go from here...

Diagnostics attached. I think it is related to the nginx issue above. The web GUI is incredibly slow to respond. kioshi-diagnostics-20201221-1144.zip