ds679

Looks like there is a v5.5.1 'hot fix' just released: https://pi-hole.net/2021/08/04/hotfix-pi-hole-web-v5-5-1-released/#page-content

Howdy SimonF.....anything to help out the team!

Ding...ding...winner-winner, chicken dinner back to 6.9.1 and it works.......thanks again

Sorry...maybe I misunderstood (I'm still trying to learn even though have been using UnRaid forever.....I have all my SATA drives connected to the LSI HBA....so, I'm guessing this plugin is not the right one. Thanks for letting me know! Yes...running latest/greatest.....sounds like I'm going to go back to 6.9.1 and test (guess things happened at the same time so I thought it was new hardware) Agreed on the weirdness in logs! Thanks again - dave

have the 4-to-1 SATA to SAS cables (I guess technically that whole thing should be reversed) 15 minutes (in Settings --> Disk Settings --> Default spin down delay as an addendum to above.....Enable Spinup Groups is set to 'No' In system logs (from GUI) -- nothing dmesg - nothing of value to drives and....right, no gray ball...just constant green (with drive temp visible).....is it just tricking me? I think it is a bit disturbing to not see anything in the logs (which is where it checks to issue the spindown....hmm). This used to work on the same system with it was direct to the SATA drives? Thanks again -dave P.S. from other posts (and I'm not sure if it is relevant) but I don't have any SATA drives connected to the on-motherboard SATA ports....only other drives are NVMe on motherboard P.S.S after doing the manual shutdown (by clicking on the green ball) - logs show: Apr 11 19:20:34 Tower4 emhttpd: shcmd (144): /usr/local/sbin/set_ncq sdd 1 Apr 11 19:20:34 Tower4 emhttpd: shcmd (145): echo 128 > /sys/block/sdd/queue/nr_requests Apr 11 19:20:34 Tower4 emhttpd: shcmd (146): /usr/local/sbin/set_ncq sdc 1 Apr 11 19:20:34 Tower4 emhttpd: shcmd (147): echo 128 > /sys/block/sdc/queue/nr_requests Apr 11 19:20:34 Tower4 emhttpd: shcmd (148): /usr/local/sbin/set_ncq sde 1 Apr 11 19:20:34 Tower4 emhttpd: shcmd (149): echo 128 > /sys/block/sde/queue/nr_requests Apr 11 19:20:34 Tower4 emhttpd: shcmd (150): /usr/local/sbin/set_ncq sdf 1 Apr 11 19:20:34 Tower4 emhttpd: shcmd (151): echo 128 > /sys/block/sdf/queue/nr_requests Apr 11 19:20:34 Tower4 emhttpd: shcmd (152): /usr/local/sbin/set_ncq sdg 1 Apr 11 19:20:34 Tower4 emhttpd: shcmd (153): echo 128 > /sys/block/sdg/queue/nr_requests Apr 11 19:20:34 Tower4 emhttpd: shcmd (154): /usr/local/sbin/set_ncq sdb 1 Apr 11 19:20:34 Tower4 emhttpd: shcmd (155): echo 128 > /sys/block/sdb/queue/nr_requests Apr 11 19:20:34 Tower4 kernel: mdcmd (37): set md_num_stripes 2048 Apr 11 19:20:34 Tower4 kernel: mdcmd (38): set md_queue_limit 80 Apr 11 19:20:34 Tower4 kernel: mdcmd (39): set md_sync_limit 5 Apr 11 19:20:34 Tower4 kernel: mdcmd (40): set md_write_method Apr 11 19:20:38 Tower4 emhttpd: shcmd (156): /usr/local/sbin/set_ncq sdd 1 Apr 11 19:20:38 Tower4 emhttpd: shcmd (157): echo 128 > /sys/block/sdd/queue/nr_requests Apr 11 19:20:38 Tower4 emhttpd: shcmd (158): /usr/local/sbin/set_ncq sdc 1 Apr 11 19:20:38 Tower4 emhttpd: shcmd (159): echo 128 > /sys/block/sdc/queue/nr_requests Apr 11 19:20:38 Tower4 emhttpd: shcmd (160): /usr/local/sbin/set_ncq sde 1 Apr 11 19:20:38 Tower4 emhttpd: shcmd (161): echo 128 > /sys/block/sde/queue/nr_requests Apr 11 19:20:38 Tower4 emhttpd: shcmd (162): /usr/local/sbin/set_ncq sdf 1 Apr 11 19:20:38 Tower4 emhttpd: shcmd (163): echo 128 > /sys/block/sdf/queue/nr_requests Apr 11 19:20:38 Tower4 emhttpd: shcmd (164): /usr/local/sbin/set_ncq sdg 1 Apr 11 19:20:38 Tower4 emhttpd: shcmd (165): echo 128 > /sys/block/sdg/queue/nr_requests Apr 11 19:20:38 Tower4 emhttpd: shcmd (166): /usr/local/sbin/set_ncq sdb 1 Apr 11 19:20:38 Tower4 emhttpd: shcmd (167): echo 128 > /sys/block/sdb/queue/nr_requests Apr 11 19:20:38 Tower4 kernel: mdcmd (41): set md_num_stripes 2048 Apr 11 19:20:38 Tower4 kernel: mdcmd (42): set md_queue_limit 80 Apr 11 19:20:38 Tower4 kernel: mdcmd (43): set md_sync_limit 5 Apr 11 19:20:38 Tower4 kernel: mdcmd (44): set md_write_method Apr 11 19:20:57 Tower4 emhttpd: spinning down /dev/sdc Apr 11 19:20:58 Tower4 emhttpd: spinning down /dev/sdf Apr 11 19:20:59 Tower4 emhttpd: spinning down /dev/sdg Apr 11 19:21:01 Tower4 emhttpd: spinning down /dev/sdb Apr 11 19:21:03 Tower4 kernel: mdcmd (45): set md_write_method 0

Am the proud new owner of a LSI 9305-16i (my first adventure into HBAs) - I'm super grateful for your plugin but wanted to know if this is common: works great if I manually spin-down the whole array or individual drives does not work when drives 'time out' and should spin down Is this a config error on my part? Not included with normal functionality? Thanks in advance for any help - dave