Neostim

Hi all, I'm running unRaid 6.9.2 and have selected "3ware" as my disk controller with twa0 as an additional parameter to get the SMART calls working. more details here: Each drive is showing it's SMART data correctly under it's own device page, one of those drives has failed SMART tests and is showing as an immediate failure however on the dashboard it shows as healthy, I suspect this is because the web ui isn't using the additional parameters set for the controller/disks under settings (same reason I don't see temperature on the dashboard but can see it on the drives device page). Is there any way around this, or a way to get email notifications for failures like this? P.S. I tried installing the latest RC of unRaid (as suggested on another post) however now the custom controller doesn't appear to work, I get an error running the smart command that worked in 6.9.2: smartctl -d 3ware,21 -a /dev/twa0 smartctl 7.2 2020-12-30 r5155 [x86_64-linux-5.14.15-Unraid] (local build) Copyright (C) 2002-20, Bruce Allen, Christian Franke, www.smartmontools.org No major number for /dev/twa listed in /proc/devices. Is the 3w-9xxx driver loaded? Smartctl open device: /dev/twa0 [3ware_disk_21] failed: setup_3ware_nodes("twa", "3w-9xxx") failed

Thanks and yeah I was wrong on the 10TB being an SMR after looking closer -- I guess 9MB/sec will just have to do

Hi all, I just bought 3 WD Red drives (WD40EFAX) and when I started the array they all started clearing at 8mb/sec, I stopped the array and removed 2 of them to see if just having one would go at 24mb/sec but it's currently clearing at 9mb/sec. This is the first time I'm adding new drives to the array with a valid parity so first time clearing but building the parity for the entire array (to a 10TB SMR drive) only took 3 days where as just clearing one of these 4TB drives is quoting 5 days. I I've attached my diagnostics file if anyone is willing to take a look and give me any suggestions to look at to find out why performance is so poor? Thanks! databank-diagnostics-20220101-0917.zip

Old thread, but did you ever figure this out? I'm in the exact same boat.

I've got the same problem as well

I also couldn't login (it hung), logs said it couldn't connect to postgres ... I had to set the postgres user to photonix accidentally, had to delete the postgres docker, clear it's app data, re-install and then it was fine.

I have the exact same issue as you in trying it out just now... glad you submitted the issue at the Github page Edit: Only thing I can think of is if it wants you to use the hostname instead of IP, which in a docker doesn't really work... In the read me it does state: EDIT: For anyone who might run into this, it seems the newest build is broke, I used an older one and got it to run, change repository in the docker to: huginn/huginn:198f0126b8638a39091d4083b03bacd96fca1d1d