jowe

No problem, just glad i could help!

I'm not entirely sure what you are trying to do. But unraid dont need to have an IP on that VLAN. If you dont want it to. If unraid needs to talk to CCTV VLAN, it should be done over the firewall. As long as the switch port you are connecting the NVR to are configured on the correct vlan, and the device have the correct IP/mask. It should work. A good start is to ping the firewall and se if you get a block in the pfsense log. Then atleast you have a conection to the firewall.

I get the errors instead if i remove the plugin, so its more of an unraid thing, it tries to spin down the drive again and again... Not a problem for me as i have the disks to never spin down now.

Yes I understand that the message should display, when timer reaches for example 15min. Or hitting spin down button. I did not push the button at all, just waited 15min, and the message loops every second. I could have provided a really long list with same messages. Yes I know, just wanted to give it a go with the latest FW, but unfortunately it didn't work. Nevertheless it's a great project!

Really good work @doron! Just tried the commands against my SAS drives after upgrading firmware of the SAS controller. But "sg_start --readonly --pc=3 /dev/sgX" disables the drive, and i need a reboot to get it back. However, the plugin loops the "drive not supported" messages see below. Nov 18 20:13:45 Tower kernel: mdcmd (931): spindown 3 Nov 18 20:13:45 Tower kernel: mdcmd (932): spindown 4 Nov 18 20:13:45 Tower SAS Assist v0.7: disk 3 (/dev/sdh) not supported by SAS spindown plugin (excluded), not spun down Nov 18 20:13:46 Tower SAS Assist v0.7: disk 4 (/dev/sdi) not supported by SAS spindown plugin (excluded), not spun down Nov 18 20:13:46 Tower kernel: mdcmd (933): spindown 3 Nov 18 20:13:46 Tower kernel: mdcmd (934): spindown 4 Nov 18 20:13:47 Tower SAS Assist v0.7: disk 3 (/dev/sdh) not supported by SAS spindown plugin (excluded), not spun down Nov 18 20:13:47 Tower SAS Assist v0.7: disk 4 (/dev/sdi) not supported by SAS spindown plugin (excluded), not spun down Nov 18 20:13:47 Tower kernel: mdcmd (935): spindown 3 Nov 18 20:13:48 Tower kernel: mdcmd (936): spindown 4 Nov 18 20:13:48 Tower SAS Assist v0.7: disk 3 (/dev/sdh) not supported by SAS spindown plugin (excluded), not spun down Nov 18 20:13:48 Tower SAS Assist v0.7: disk 4 (/dev/sdi) not supported by SAS spindown plugin (excluded), not spun down

A new version has been posted, ls62 and is working (at least for me) So linuxserver/emby:latest Is the one to use if you want to get the latest updates. @jcato @mbc0

With the latest update i cant scan new media. It finds the media, but can't read what kind it is. And it wont play on Shield / Web. Media previously scaned works. I went back to linuxserver/emby:4.5.2.0-ls59 And all is working like before again.

Hi, i modified the script, and got it working. It's VERY simplified. And cusom to my setup. I modified 99-spinsasdown.conf to trigger "spindown 3" For my SAS disk 3. :msg,contains,"spindown 3" ^/usr/local/bin/unraid-spinsasdown And in your script unraid-spinsasdown I removed all intelligence and just spin down the correct disk. sg_start --readonly --pc=3 /dev/sg7 Unraid log after spin up / spin down in GUI Oct 21 10:27:41 Tower kernel: mdcmd (99): spinup 3 Oct 21 10:27:41 Tower kernel: md: do_drive_cmd: disk3: ATA_OP e3 ioctl error: -5 Oct 21 10:28:03 Tower kernel: mdcmd (100): spindown 3 Oct 21 10:28:03 Tower emhttpd: error: mdcmd, 2723: Input/output error (5): write Oct 21 10:28:03 Tower kernel: md: do_drive_cmd: disk3: ATA_OP e0 ioctl error: -5 And checking status root@Tower:/# sdparm --command=sense /dev/sdh /dev/sdh: HP MB8000JFECQ HPD7 Additional sense: Standby condition activated by command Edit: Tried again, waited 15 min and got this, and disk not spun down.. Oct 21 10:45:52 Tower kernel: mdcmd (103): spinup 3 Oct 21 10:45:52 Tower kernel: md: do_drive_cmd: disk3: ATA_OP e3 ioctl error: -5 Oct 21 11:00:53 Tower kernel: mdcmd (104): spindown 3 Oct 21 11:00:53 Tower emhttpd: error: mdcmd, 2723: Input/output error (5): write Oct 21 11:00:53 Tower kernel: md: do_drive_cmd: disk3: ATA_OP e0 ioctl error: -5 Oct 21 11:00:54 Tower kernel: mdcmd (105): spindown 3 Oct 21 11:01:10 Tower rsyslogd: program '/usr/local/bin/unraid-spinsasdown' (pid 23020) exited with status 2 [v8.1908.0] Edit 2 If i run /usr/local/bin/unraid-spinsasdown from CLI, the disk spins down root@Tower:/mnt/disk1/media/org.rel# sdparm --command=sense /dev/sdh /dev/sdh: HP MB8000JFECQ HPD7 root@Tower:/mnt/disk1/media/org.rel# /usr/local/bin/unraid-spinsasdown root@Tower:/mnt/disk1/media/org.rel# sdparm --command=sense /dev/sdh /dev/sdh: HP MB8000JFECQ HPD7 Additional sense: Standby condition activated by command

How can I check that? I have disabled my hddtemp script, but i do have "cache dirs" running, can disable that for now.

Hi, the log is empty as soon as i restart rc.rsyslogd. I used that file for an hour or so yesterday, and didn't get a single line in the log. I also went back to 6.8.3 yesterday due to performance problems. But i have the same issue with the log. And no spindown of SAS. I also have the same problem with 3 WD RED SATA drives. On the same controller i have 4 drives that go to standby as they should. They are actually on different channels. So the 4 drives working are on one, and 4 not working are on another. Maybe something there?! I had the same problem years ago with my WD RED not spinning down, but if i remember correctly i solved it somehow. Dont remember how... I have sent the file.

Got some read errors when the disk spun up again, no red X thank god! Nothing in the log unfortunately.

Same again, pasted the text below. And restarted rc.rsyslogd. root@Tower:~# /etc/rc.d/rc.rsyslogd restart Starting rsyslogd daemon: /usr/sbin/rsyslogd -i /var/run/rsyslogd.pid Nothing in the log when i manually spin up / down disks. (And probably not when done automatically either). If i put the disk to sleep more than once it's still in standby. But the first time nothing happened. root@Tower:~# sdparm --command=sense /dev/sdh /dev/sdh: HP MB8000JFECQ HPD7 root@Tower:~# sg_start --readonly --pc=3 /dev/sg7 root@Tower:~# sdparm --command=sense /dev/sdh /dev/sdh: HP MB8000JFECQ HPD7 root@Tower:~# sdparm --command=sense /dev/sdh /dev/sdh: HP MB8000JFECQ HPD7 root@Tower:~# sg_start --readonly --pc=3 /dev/sg7 root@Tower:~# sdparm --command=sense /dev/sdh /dev/sdh: HP MB8000JFECQ HPD7 Additional sense: Standby condition activated by command root@Tower:~# sg_start --readonly --pc=3 /dev/sg7 root@Tower:~# sdparm --command=sense /dev/sdh /dev/sdh: HP MB8000JFECQ HPD7 Additional sense: Standby condition activated by command root@Tower:~# sg_start --readonly --pc=3 /dev/sg7 root@Tower:~# sdparm --command=sense /dev/sdh /dev/sdh: HP MB8000JFECQ HPD7 Additional sense: Standby condition activated by command

Nothing at all Will try again, i used winscp to edit the file. That should work right? I know, it's not updated all the time, but usually when unraid is spinning down the disks, it will change the status. Oct 19 14:40:56 Tower kernel: mdcmd (398): spinup 3 Oct 19 14:40:56 Tower kernel: md: do_drive_cmd: disk3: ATA_OP e3 ioctl error: -5 Oct 19 15:19:03 Tower kernel: mdcmd (409): spindown 3 Oct 19 15:19:03 Tower emhttpd: error: mdcmd, 2783: Input/output error (5): write Oct 19 15:19:03 Tower kernel: md: do_drive_cmd: disk3: ATA_OP e0 ioctl error: -5 Oct 19 15:19:04 Tower kernel: mdcmd (410): spindown 3 Oct 19 15:19:20 Tower SAS Assist v0.6[11358]: spinning down slot 3, device /dev/sdh (/dev/sg7) Oct 19 15:19:20 Tower SAS Assist v0.6[11412]: spinning down slot 3, device /dev/sdh (/dev/sg7)

I have tried it and now i get nothing in the log at all, all disks went down to standby, but the SAS drive. But not a single line in the log. Still showing the "green" button, but no temp. Another thing i saw in the log before changing the 99-spinsasdown.conf file, was that it's trying to spin down disk3 2 times. Maybe that why the 2 lines from the plugin. That might be a problem? I have not changed the rsyslog configuration. Using a LSI SAS 9211-4i Flashed to IT mode.

Same again Oct 19 12:17:52 Tower kernel: mdcmd (74): spindown 3 Oct 19 12:17:52 Tower emhttpd: error: mdcmd, 2783: Input/output error (5): write Oct 19 12:17:52 Tower kernel: md: do_drive_cmd: disk3: ATA_OP e0 ioctl error: -5 Oct 19 12:17:53 Tower kernel: mdcmd (75): spindown 3 Oct 19 12:18:09 Tower SAS Assist v0.6[14705]: spinning down slot 3, device /dev/sdh (/dev/sg7) Oct 19 12:18:09 Tower SAS Assist v0.6[14729]: spinning down slot 3, device /dev/sdh (/dev/sg7) root@Tower:~# sdparm --command=sense /dev/sdh /dev/sdh: HP MB8000JFECQ HPD7 I'll try to reinstall the plugin.

Hi, Manually spinning down sg7 works. root@Tower:~# sdparm --command=sense /dev/sdh /dev/sdh: HP MB8000JFECQ HPD7 root@Tower:~# sg_start --readonly --pc=3 /dev/sg7 root@Tower:~# sdparm --command=sense /dev/sdh /dev/sdh: HP MB8000JFECQ HPD7 Additional sense: Standby condition activated by command When i check the disk right after unraid shows it as spun down with "sdparm --command=sense /dev/sdh" It not in standby even though unraid GUI says it is. Looks just like this. root@Tower:~# sdparm --command=sense /dev/sdh /dev/sdh: HP MB8000JFECQ HPD7 Yes i get that line 2 times. Will check a 3rd time just to be sure.

Hi, This is a great initiative! But I'm having some trouble to get my HP SAS drive spun down. The drive looks spun down i unraid, but not when i check in CLI. root@Tower:~# sdparm --command=sense /dev/sdh /dev/sdh: HP MB8000JFECQ HPD7 Then if i manually spin down the drive. root@Tower:~# sg_start --readonly --pc=3 /dev/sdh root@Tower:~# sdparm --command=sense /dev/sdh /dev/sdh: HP MB8000JFECQ HPD7 Additional sense: Standby condition activated by command Looks like it's working, but if i spin up the drive and wait 15min, it's the same over again, looks spun down in unraid, but really isn't It's a HP SAS drive connected to LSI SAS controller. And i have noticed that the drive has different names (power conditions) than other drives (STANDBY_Z) root@Tower:~# sdparm --flexible -6 -p po -l /dev/sdh /dev/sdh: HP MB8000JFECQ HPD7 Direct access device specific parameters: WP=0 DPOFUA=1 Power condition [po] mode page: PM_BG 2 [cha: y, def: 2, sav: 2] Power management, background functions, precedence STANDBY_Y 0 [cha: y, def: 0, sav: 0] Standby_y timer enable IDLE_C 0 [cha: y, def: 0, sav: 0] Idle_c timer enable IDLE_B 0 [cha: y, def: 0, sav: 0] Idle_b timer enable IDLE_A 1 [cha: y, def: 1, sav: 1] Idle_a timer enable STANDBY_Z 0 [cha: y, def: 0, sav: 0] Standby_z timer enable IACT 20 [cha: y, def: 20, sav: 20] Idle_a condition timer (100 ms) SZCT -1 [cha: y, def: -1, sav: -1] Standby_z condition timer (100 ms) IBCT -1 [cha: y, def: -1, sav: -1] Idle_b condition timer (100 ms) ICCT -1 [cha: y, def: -1, sav: -1] Idle_c condition timer (100 ms) SYCT -1 [cha: y, def: -1, sav: -1] Standby_y condition timer (100 ms) CCF_IDLE 2 [cha: y, def: 2, sav: 2] check condition if from idle_c CCF_STAND 2 [cha: y, def: 2, sav: 2] check condition if from a standby CCF_STOPP 2 [cha: y, def: 2, sav: 2] check condition if from stopped Log from unraid spin down. Oct 19 11:14:49 Tower kernel: mdcmd (65): spindown 3 Oct 19 11:14:49 Tower emhttpd: error: mdcmd, 2783: Input/output error (5): write Oct 19 11:14:49 Tower kernel: md: do_drive_cmd: disk3: ATA_OP e0 ioctl error: -5 Oct 19 11:14:50 Tower kernel: mdcmd (66): spindown 3 Oct 19 11:15:07 Tower SAS Assist v0.6[20803]: spinning down slot 3, device /dev/sdh (/dev/sg7) Oct 19 11:15:07 Tower SAS Assist v0.6[20827]: spinning down slot 3, device /dev/sdh (/dev/sg7) Any ideas that could help me? Thanks!

That's strange. I just tried to enable/disable br0, and if i mark the checkbox, and start Docker. It's instantly showing up as a choice in any container. Or disappear if i disable the checkbox. br0 is not a vlan, all other are.

I have set up my VLAN in network settings (without a static IP for unraid server) Then stop docker go to settings / docker, advanced view, and there you should be able to choose vlans for docker. And after that, see them in every container.

The templates in unRAID is OpenELEC 6.0.3 and LibreELEC 7.0.1, thoose are from 2016, and though they should work with your 730. I would try to upgrade anyway. To be on a more current version.

I think most people are using the official install from OpenELEC / LibreELEC, using this guide. Im using a LibreELEC install with Kodi 19. And it's working great! Passing a Geforce GT 1030 and a USB controller card. JoWe

I have 16GB, and it's used to about 60% But i don't have anymore problems since 6.6.4 and now with 6.6.5 all cron jobs work as well JoWe

Updated to unRAID 6.6.4 and problem with spinning up disks is no longer present! But it seems to use alot of CPU, around 10% with plugin disabled. And 30%+ when enabled. Changed to adaptive, and it's sleeping for 10s insted of only 1 with fixed. And the cpu is much less spiky. Thanks for your support @Alex R. Berg

No problem! From what i have read, you might want to include user shares. And set cache pressure to 1. Depending on if you are having problems or not.

Try using this link as @BRiT suggested. From your plugin tab, and "install plugin". https://raw.githubusercontent.com/arberg/dynamix/master/unRAIDv6/dynamix.cache.dirs.plg