Marc_G2

Keep in mind, the plug-in is just a front end for executing sleep commands on a schedule. If you initiate sleep via the terminal, I strongly suspect you'll have the same issues waking up. My old system had major problems with its HBA card after waking from S3 sleep. The issue was fixed after updating my motherboard to the newest BIOS. So I suggest seeing if updating all your firmware fixes the issue.

I double checked the firmware on the LSI card and it's 20.00.07.00. Which is the newest as far as I know. (see image of boot screen below). So who knows. Maybe it's a motherboard issue. The one other thing I should've tried is checking the unRAID error log to see if gave any hints. I've crammed the drive into a shucked WD enclosure. And it's not worth the hassle the remove and check it at this point.

I'm having trouble excluding directories from an unassigned device share. Is this the correct input field format for excluding two folders? 'Aux SSD/Priority Share/Folder1', 'Aux SSD/Priority Share/Folder2'

The drive is HUH728080ALE604. The HBA card is SAS 9211-8i.

Before connecting it to the system, I tested the drive over usb and formatted it to NTFS with default parameters. I've put data on it now. So I can't try it unformatted.

Yes I was using the same power connection each time. I also tried a different connector which provides the 3.3V. That didn't help. Also all the disks are sata. I'm using mini sas to sata breakout cables.

The LSI card is powered by the PCIe slot. It's one ATX power supply powering everything. If the firmware version from 2016 is the newest, then I'm on the latest. I couldn't locate anything newer. I decided to use the hard drive as USB backup drive instead of putting in the array. So the issue is largely moot now. I guess I'll avoid enterprise drives for now.

I picked up a used HGST Ultrastar HE8. unRAID doesn't detect it when it's connected via the LSI HBA card. It is detected when it's connected directly via motherboard SATA. Does anyone have an idea why? I tried two different sata connectors coming off the LSI card. One of the 4 connectors was already in use. So I doubt it's the cable. Side note: This drive has a very slow spin-up time. So I don't recommend it for anyone who's set their drives to spin down frequently.

I think you'd need to go back to 6.11.X. But that's not recommended. I would try to make use of the network activity monitor or time of day exclusions.

The disk activity checker function is broken in the current unRAID version. No one knows when or if it will get fixed.

In case anyone's interested, SpaceInvader One did a new video on the topic of sleep/wake with the S3 sleep plugin. Sadly, he did not have any suggestions regarding the disk activity function not working. I'm not sure if he's wasn't affected or he didn't test it thoroughly enough to notice. https://www.youtube.com/watch?v=lBxQcU1MPY0

I plan to upgrade most of my stuff to 2.5 gigabit in the next few months. My server cpu is currently a dual-core i3-6100. That's so low spec, I'm wondering if it will (or currently is) slowing down any kind user or backend NAS functions like parity calculations. Or that it might slow down my network transfer speeds on certain kinds of SSD storage pools. Thoughts on this? I'm currently upgrading another gaming desktop. So I have to choose between selling the old hardware or using it to upgrade my server.

Any Linux experts here? I suspect the problem with the Sleep plugin's disk activity checker is with this function. If so, it may be an easy fix to just modify the plugin file and then repackage it as a txz. HDD_activity() { result= if [[ $checkHDD == yes ]]; then [[ -f /dev/shm/2 ]] && cp -f /dev/shm/2 /dev/shm/1 || touch /dev/shm/1 awk '/(sd[a-z]*|nvme[0-9]n1) /{print $3,$6+$10}' /proc/diskstats >/dev/shm/2 for dev in ${array[@]}; do [[ $monitor -ne 2 ]] && active=$(sdspin /dev/$dev) || active= [[ $monitor -ne 1 ]] && diskio=($(grep -Pho "^$dev \K\d+" /dev/shm/1 /dev/shm/2)) || diskio= if [[ -n $active || ${diskio[0]} != ${diskio[1]} ]]; then result=1 break; fi done fi if [[ -n $result ]]; then log "Disk activity on going: $dev" echo $result fi }

You've confirmed disk activity detection specifically still works? Then I guess it still works some folks on version 6.12.X. So far there's about 5 people in this thread who's found it to be broken.

Disk activity detection is broken on 6.12 for everyone as far as I can tell. The dev has made no comment about when or if it will get fixed.