endystrike

Hi @JorgeB, Is there any particular risk in updating also the UEFI like this (without erasing anything) from a Windows machine? I feel more confident in flashing those cards from a Windows environment and later to move the card to the Unraid server sas3flash.exe -o -f SAS9300-16i_IT.bin -b mptsas3.rom -b mpt3x64.rom Thank you!

have you already tried to reboot the server after installing the plugin? Initially it wasn't working on my server too, but after a reboot the plugin started working fine and since then I had no issue!

what do you mean exactly? I cannot understand... This plugin just adds the possibility to spin down SAS drives too, because Unraid natively supports spin down only for SATA drives... But the spinning down mechanism once you've installed this plugin is the same...

imho that's what spin down mechanism is meant to be and to do... it's a stort of "standby" and then when you access those drives they spin up again until when due to inactivity (aka "Default spin down delay" setting in Settings > disk settings) occurs again they spin down again and so on!

any idea @JorgeB? Thanks for your help!

Hello, since a couple of days, I started noticing a couple of issues on my server: when I edit a share, it takes a long time to restart services and so on Cannot do a graceful shutdown, even if I increased the timeout from 90s to 300s Plex stopped transcoding correctly. Instead of using GPU, it freezes or uses CPU, but keeping GPU used as well Also terminal windows doesn't show up correctly anymore and I have to refresh the page to get it working Thanks for your kind help! Here are attached my diagnostic report and Plex configuration as well. Terminal endys-diagnostics-20230310-0254.zip

I've installed SAS spindown on my Unraid 6.11.5 and it works fine. I just have to say initially it wasn't working at all then I just reinstalled the plugin and rebooted the server and since then it started working perfectly... I'd just suggest to reinstall and reboot the server, then try to spin down a SAS drive while the syslog is open and you should see something as follows. Btw, the log you've to check is this one. PS I don't know for other users if it's the same, but some drives' models require more time to spin down, but it's not a problem for sure... Here I tried to spin up and then spin down all the drives, you can test if everything works doing the same. I'm really thankful to the creator of this plugin, I have 8 SAS drives in my build and I'm constantly saving 80w!

try disabling other dockers, sut down VMs, ensure mover is not running and make sure you're not accessing the drives from elsewhere during the benchmark... This is the main reason why speed gap detection occurs. By the way, I still get that alert but with that box flagged, the test continues anyway.

I got that alert too, I just disabled flagging the correct box and no other issue appeared after...

Guys for anyone having the issue of some HDD models recognized as SSD, I found a temporary fix: rollback to version 2.10. How to do that? Just edit the docker settings and set this field as follows: if the issue still persists, just remove the docker, delete the following folder "/mnt/user/appdata/DiskSpeed/" or wherever you've saved the app data of this docker, then when you reinstall the docker, set the repository field as "jbartlett777/diskspeed:2.10". In the future, when the bug will be fixed you'll just have to edit the docker again and set the repository to pull the latest version as follows: "jbartlett777/diskspeed". Hope this will help!

Unfortunately, it seems recently some HDD models get recognized as SSD and I'm unable to bench them...

just to be sure 100% have you configured as follows? Mount script example (to be scheduled when array starts): mkdir -p /mnt/disks/google rclone mount --max-read-ahead 1024k --allow-other google: /mnt/disks/google & Unmount script (to be scheduled when the array stops): fusermount -u /mnt/disks/google and to sync Google to your share (i.e. "Google_local"). This can be scheduled every 24h or whenever you wanna sync google data with your local data. rsync -a -v -P /mnt/disks/google/* /mnt/user/Google_local/

nice, I'll try that solution too! I tested mine one at the moment in the meanwhile with another account where there's no important data and it seems it works without any issue!

thank you, that's a very nice and super safe idea! 🙌