umax
-
Posts
55 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by umax
-
-
Here they are, thanks
-
Hi, I have successfully converted my two new ssd into raid0 btrfs, folowed the step to move appdata onto array and than back to cache pool, but now my dockers are acting up. I only use three of them, deluge, krusader and roon.
Deluge refuses to connect to WebUi, krusader is giving me some vnc error and my roon clients are unable to reach roonserver. What should I do?
-
Thanks! Can I use Btrfs file system on new cache drive and just follow the above steps?
-
My cache drive only has 2GB left since I use it to store Roon library on it. Beside that I use it for 4 docker's and thats it, no mover, etc..
What is the right way to migrate everything from existing ssd to a new one? Is there a line code to clone everything?
I have attached diagnostic file from my server, maybe someone can check if there is something else on the cache drive or/if something could be optimised (docker image allocation size)?
Thanks in advance!
-
19 hours ago, dkerlee said:
@umax there are good resources here:https://community.roonlabs.com/c/support/port-forwarding-resources/104
and here:
https://portforward.com/how-to-port-forward/
If you run into additional problems, post over at the community roonlabs forum and they can help you out. Or maybe I'll help you out over there!
Thank you, got it through by opening ports as per your edit on 1st page! My favourite docker on unraid! Roon rules, now on the go!
-
2
-
-
50 minutes ago, JDGJr said:
Can anyone comment on their success upgrading to Roon 2.0?
It went smooth on my side, updated as usual, I just need to figure out the port forwarding now for the ARC in order to ba able to stream music from outside
-
On 12/5/2020 at 2:49 PM, CS01-HS said:
One of the recommended SMB tweaks is disabling signing. Have you done that? It may require a reboot to take effect:
$ more /etc/nsmb.conf [default] signing_required=noIs that tweak done on the Unraid or Osx via terminal?
-
To not open new thread, will AOC-SASLP-MV8 (not ver. "2") work with Seagate X18 18TB drives? I have 16 x 10TB connected to two of this controllers without issue. Is there anything different regarding drives past 10TB mark?
-
I am struggling to understand how to import from server function works. Whatever path I try to use, lychee is saying; Given path is not a directory (/mnt/user/Pictures)
Also, where does lynchee creates folder for pictures (/uploads)?
This is my lychee log;
2017-09-02 23:41:27 - error - Lychee\Modules\Database::createTables (180) - Table 'lychee.lychee_settings' doesn't exist 2017-09-02 23:41:27 - error - Lychee\Modules\Database::createTables (225) - Table 'lychee.lychee_albums' doesn't exist 2017-09-02 23:41:27 - error - Lychee\Modules\Database::createTables (248) - Table 'lychee.lychee_photos' doesn't exist 2017-09-02 23:42:57 - error - Lychee\Modules\Import::server (106) - Given path is not a directory (/nmt/users/PiCTURES/TEST) 2017-09-02 23:45:22 - error - Lychee\Modules\Import::server (106) - Given path is not a directory (/nmt/users/PiCTURES/TEST) 2017-09-02 23:59:16 - error - Lychee\Modules\Import::server (106) - Given path is not a directory (/mnt/users/PiCTURES/TEST) 2017-09-03 00:00:56 - error - Lychee\Modules\Import::server (106) - Given path is not a directory (/mnt/users/PiCTURES/Thumbs) 2017-09-03 00:01:32 - error - Lychee\Modules\Import::server (106) - Given path is not a directory (/PiCTURES/TEST) 2017-09-03 00:13:43 - notice - Lychee\Modules\Session::login (81) - User (umax) has logged in from 192.168.1.7 2017-09-03 00:14:30 - error - Lychee\Modules\Import::server (106) - Given path is not a directory (/mnt/users/PiCTURES) 2017-09-03 00:15:25 - error - Lychee\Modules\Import::server (106) - Given path is not a directory (/nmt/users/PiCTURES) 2017-09-03 00:21:50 - notice - Lychee\Modules\Session::login (81) - User (umax) has logged in from 192.168.1.7 2017-09-03 00:23:17 - error - Lychee\Modules\Import::server (106) - Given path is not a directory (/mnt/user/Pictures) 2017-09-03 00:26:42 - notice - Lychee\Modules\Session::login (81) - User (umax) has logged in from 192.168.1.15 2017-09-03 00:39:43 - notice - Lychee\Modules\Session::login (81) - User (umax) has logged in from 192.168.1.7 2017-09-03 00:40:58 - error - Lychee\Modules\Import::url (56) - Photo format not supported (/mnt/user/PiCTURES/) 2017-09-03 00:41:24 - error - Lychee\Modules\Import::server (106) - Given path is not a directory (/mnt/user/PiCTURES) 2017-09-03 00:41:50 - error - Lychee\Modules\Import::server (106) - Given path is not a directory (/mnt/user/PiCTURES/boatTrip13-zaGledat) 2017-09-03 00:46:31 - notice - Lychee\Modules\Session::login (81) - User (umax) has logged in from 192.168.1.7 2017-09-03 00:46:53 - error - Lychee\Modules\Import::server (106) - Given path is not a directory (/mnt/user0/PiCTURES) 2017-09-03 00:48:42 - error - Lychee\Modules\Import::server (106) - Given path is not a directory (/mnt/disk7/PiCTURES) 2017-09-03 00:49:17 - error - Lychee\Modules\Import::server (106) - Given path is not a directory (/disk7/PiCTURES) 2017-09-03 00:49:33 - error - Lychee\Modules\Import::server (106) - Given path is not a directory (/PiCTURES) -
Need some help. Can you please let me know how can I mount a Mac OS Extended (Journaled) drive? I am trying to copy some large amount of data over to server that is on a mac formatted drive.
-
That did it, thank you, great plug!
-
Having problem with installing this plugin. When I install via "Install Plugin" it looks like it is installed, but there is no icon under System Information group (I have just "Active Streams" from Dynamix there).
When I try via telnet I get "plugin: run failed: /bin/bash retval: 1"
Any clue what is going on? I have just upgraded to 6.1.3 (from 5.0.6)
root@UNRAiD:~# wget https://github.com/dlandon/open.files/raw/master/open.files.plg --2015-11-07 23:00:18-- https://github.com/dlandon/open.files/raw/master/open.files.plg Resolving github.com (github.com)... 192.30.252.129 Connecting to github.com (github.com)|192.30.252.129|:443... connected. HTTP request sent, awaiting response... 302 Found Location: https://raw.githubusercontent.com/dlandon/open.files/master/open.files.plg [following] --2015-11-07 23:00:19-- https://raw.githubusercontent.com/dlandon/open.files/master/open.files.plg Resolving raw.githubusercontent.com (raw.githubusercontent.com)... 185.31.17.133 Connecting to raw.githubusercontent.com (raw.githubusercontent.com)|185.31.17.133|:443... connected. HTTP request sent, awaiting response... 200 OK Length: 3063 (3.0K) [text/plain] Saving to: ‘open.files.plg.1’ open.files.plg.1 100%[=====================>] 2.99K --.-KB/s in 0s 2015-11-07 23:00:19 (241 MB/s) - ‘open.files.plg.1’ saved [3063/3063] root@UNRAiD:~# installplg open.files.plg plugin: installing: open.files.plg plugin: run failed: /bin/bash retval: 1
-
Been awhile since I have last pre-cleard a drive. Do I still need to use -A option on unRaid 5.0.6 with 4TB drives (HGST Deskstar NAS)?
-
Yeah, this is a known bug. It has been corrected for v6, but needs to be ported to v5 as well.
Thanks! Not a biggie, but good to know so I stop messing with it
Anyway, congrats to all the work you have done -
There is an issue with the CPU and MB temperatures. This line in the SystemTemps.php sorts the temperatures and the lowest one always shows first (left position) on the webpage.
exec("sensors -A|awk '/^CPU Temp/ {print $3*1}; /^M\/?B Temp/ {print $3*1}'",$temp);No matter which temperature is associated with the CPU and MB, the lowest temperature will always show first on the left. In my case the MB temp is lower so it shows in the CPU temperature position.
Really a minor issue, but may cause some consternation when trying to get the temperatures to show in the correct positions.
I have the same problem, no matter how I label temps in sensors_conf, I always get the MB temp is Processor window and vice-versa. Tho my lowest temperature (CPU) is on the right side (see bellow)
-
Use Notepad++ and edit your sensors.conf file and swape the temp1 and temp2 labels. For example, right now you have temp1 as mb and temp2 as cpu. Make temp1 cpu and temp 2 mb, save file and reboot. That should switch them in the gui.
Yes, I have tried this but with no success. See bellow;
sensors_conf
chip "w83627dhg-isa-0a10" label temp1 "MB Temp" label temp2 "CPU Temp"
This is "sensors" output from console;
UNRAiD login: root Linux 3.9.11p-unRAID. root@UNRAiD:~# sensors coretemp-isa-0000 Adapter: ISA adapter Core 0: +33.0 C (high = +89.0 C, crit = +105.0 C) Core 2: +38.0 C (high = +89.0 C, crit = +105.0 C) w83627dhg-isa-0a10 Adapter: ISA adapter Vcore: +0.95 V (min = +0.60 V, max = +1.49 V) in1: +1.82 V (min = +1.62 V, max = +1.99 V) AVCC: +3.25 V (min = +2.98 V, max = +3.63 V) VCC: +3.25 V (min = +2.98 V, max = +3.63 V) in4: +1.53 V (min = +1.35 V, max = +1.65 V) in5: +1.26 V (min = +1.13 V, max = +1.38 V) in6: +1.44 V (min = +1.42 V, max = +1.52 V) 3VSB: +3.23 V (min = +2.98 V, max = +3.63 V) Vbat: +3.17 V (min = +2.70 V, max = +3.30 V) fan1: 0 RPM (min = 753 RPM, div = 128) ALARM fan2: 1591 RPM (min = 712 RPM, div = fan3: 1010 RPM (min = 712 RPM, div = fan4: 0 RPM (min = 753 RPM, div = 128) ALARM fan5: 1035 RPM (min = 712 RPM, div = MB Temp: +40.0 C (high = +60.0 C, hyst = +55.0 C) sensor = thermistor CPU Temp: +33.5 C (high = +95.0 C, hyst = +92.0 C) sensor = CPU diode temp3: +39.0 C (high = +75.0 C, hyst = +70.0 C) sensor = thermistor cpu0_vid: +1.513 V intrusion0: ALARM
And this is how the Dynamix is displaying it (see attachment "sensors_conf"). The temperatures are switched.
I have also tried with;
sensors_conf
chip "w83627dhg-isa-0a10" label temp1 "CPU Temp" label temp2 "MB Temp"
console output is now wrong;
UNRAiD login: root Linux 3.9.11p-unRAID. root@UNRAiD:~# sensors coretemp-isa-0000 Adapter: ISA adapter Core 0: +33.0 C (high = +89.0 C, crit = +105.0 C) Core 2: +37.0 C (high = +89.0 C, crit = +105.0 C) w83627dhg-isa-0a10 Adapter: ISA adapter Vcore: +0.95 V (min = +0.60 V, max = +1.49 V) in1: +1.82 V (min = +1.62 V, max = +1.99 V) AVCC: +3.25 V (min = +2.98 V, max = +3.63 V) VCC: +3.25 V (min = +2.98 V, max = +3.63 V) in4: +1.53 V (min = +1.35 V, max = +1.65 V) in5: +1.26 V (min = +1.13 V, max = +1.38 V) in6: +1.44 V (min = +1.42 V, max = +1.52 V) 3VSB: +3.23 V (min = +2.98 V, max = +3.63 V) Vbat: +3.17 V (min = +2.70 V, max = +3.30 V) fan1: 0 RPM (min = 727 RPM, div = 64) ALARM fan2: 1607 RPM (min = 712 RPM, div = fan3: 1016 RPM (min = 712 RPM, div = fan4: 0 RPM (min = 727 RPM, div = 64) ALARM fan5: 1035 RPM (min = 712 RPM, div = CPU Temp: +40.0 C (high = +60.0 C, hyst = +55.0 C) sensor = thermistor MB Temp: +32.0 C (high = +95.0 C, hyst = +92.0 C) sensor = CPU diode temp3: +39.0 C (high = +75.0 C, hyst = +70.0 C) sensor = thermistor cpu0_vid: +1.513 V intrusion0: ALARM
but dynamix (see attachment "sensors_conf (wrong)")is still showing it the same (temps switched)
-
glad it's working. I assume the temps look correct to you. Some people have to switch the labels around in sensors.conf so cpu is actually the cpu, etc. I didn't have to do that for mine.What is really awesome is the announcement that Dynamix will now be included with V6! That is so cool - this completes unraid IMO.
yea, the labels are switched, not a biggie, but can't figure it out...
tried 3 different sensors_conf;
chip "w83627dhg-isa-0a10" label temp2 "CPU Temp" label temp1 "MB Temp" and chip "w83627dhg-isa-0a10" label temp1 "MB Temp" label temp2 "CPU Temp" and label temp1 "CPU Temp" label temp2 "MB Temp"
And yes, that is awesome news indeed, cant wait for V6 final!
-
thanks to both, that did it!!!
i now have both temps showing up on Dynamix! -
i have manged to install Perl and here is the output of "sensors-detect". I really don't know what to look for tho
UNRAiD login: root
Linux 3.9.11p-unRAID.
root@UNRAiD:~# sensors-detect
# sensors-detect revision 6170 (2013-05-20 21:25:22 +0200)
# System: Supermicro X8SIL [0123456789]
This program will help you determine which kernel modules you need
to load to use lm_sensors most effectively. It is generally safe
and recommended to accept the default answers to all questions,
unless you know what you're doing.
Some south bridges, CPUs or memory controllers contain embedded sensors.
Do you want to scan for them? This is totally safe. (YES/no): Yes
Silicon Integrated Systems SIS5595... No
VIA VT82C686 Integrated Sensors... No
VIA VT8231 Integrated Sensors... No
AMD K8 thermal sensors... No
AMD Family 10h thermal sensors... No
AMD Family 11h thermal sensors... No
AMD Family 12h and 14h thermal sensors... No
AMD Family 15h thermal sensors... No
AMD Family 15h power sensors... No
AMD Family 16h power sensors... No
Intel digital thermal sensor... Success!
(driver `coretemp')
Intel AMB FB-DIMM thermal sensor... No
VIA C7 thermal sensor... No
VIA Nano thermal sensor... No
Some Super I/O chips contain embedded sensors. We have to write to
standard I/O ports to probe them. This is usually safe.
Do you want to scan for Super I/O sensors? (YES/no): Yes
Probing for Super-I/O at 0x2e/0x2f
Trying family `National Semiconductor/ITE'... No
Trying family `SMSC'... No
Trying family `VIA/Winbond/Nuvoton/Fintek'... Yes
Found `Winbond W83627DHG Super IO Sensors' Success!
(address 0xa10, driver `w83627ehf')
Probing for Super-I/O at 0x4e/0x4f
Trying family `National Semiconductor/ITE'... No
Trying family `SMSC'... No
Trying family `VIA/Winbond/Nuvoton/Fintek'... No
Trying family `ITE'... No
Some systems (mainly servers) implement IPMI, a set of common interfaces
through which system health data may be retrieved, amongst other things.
We first try to get the information from SMBIOS. If we don't find it
there, we have to read from arbitrary I/O ports to probe for such
interfaces. This is normally safe. Do you want to scan for IPMI
interfaces? (YES/no): Yes
Found `IPMI BMC KCS' at 0xca2... Success!
(confidence 8, driver `to-be-written')
Some hardware monitoring chips are accessible through the ISA I/O ports.
We have to write to arbitrary I/O ports to probe them. This is usually
safe though. Yes, you do have ISA I/O ports even if you do not have any
ISA slots! Do you want to scan the ISA I/O ports? (yes/NO): Yes
Probing for `National Semiconductor LM78' at 0x290... No
Probing for `National Semiconductor LM79' at 0x290... No
Probing for `Winbond W83781D' at 0x290... No
Probing for `Winbond W83782D' at 0x290... No
Lastly, we can probe the I2C/SMBus adapters for connected hardware
monitoring devices. This is the most risky part, and while it works
reasonably well on most systems, it has been reported to cause trouble
on some systems.
Do you want to probe the I2C/SMBus adapters now? (YES/no): Yes
Using driver `i2c-i801' for device 0000:00:1f.3: Intel 3400/5 Series (PCH)
Module i2c-dev loaded successfully.
Next adapter: SMBus I801 adapter at 0400 (i2c-0)
Do you want to scan it? (YES/no/selectively): Yes
Client found at address 0x18
Probing for `Analog Devices ADM1021'... No
Probing for `Analog Devices ADM1021A/ADM1023'... No
Probing for `Maxim MAX1617'... No
Probing for `Maxim MAX1617A'... No
Probing for `Maxim MAX1668'... No
Probing for `Maxim MAX1805'... No
Probing for `Maxim MAX1989'... No
Probing for `Maxim MAX6655/MAX6656'... No
Probing for `TI THMC10'... No
Probing for `National Semiconductor LM84'... No
Probing for `Genesys Logic GL523SM'... No
Probing for `Onsemi MC1066'... No
Probing for `Maxim MAX1618'... No
Probing for `Maxim MAX1619'... No
Probing for `National Semiconductor LM82/LM83'... No
Probing for `Maxim MAX6654'... No
Probing for `Maxim MAX6690'... No
Probing for `Maxim MAX6680/MAX6681'... No
Probing for `Maxim MAX6695/MAX6696'... No
Probing for `Texas Instruments AMC6821'... No
Probing for `National Semiconductor LM95234'... No
Probing for `National Semiconductor LM95245'... No
Probing for `National Semiconductor LM64'... No
Probing for `SMSC EMC1047'... No
Probing for `SMSC EMC1402'... No
Probing for `SMSC EMC1403'... No
Probing for `SMSC EMC1404'... No
Probing for `ST STTS424'... No
Probing for `ST STTS424E'... No
Probing for `ST STTS2002'... No
Probing for `ST STTS3000'... No
Probing for `NXP SE97/SE97B'... No
Probing for `NXP SE98'... No
Probing for `Analog Devices ADT7408'... No
Probing for `IDT TS3000/TSE2002'... No
Probing for `Maxim MAX6604'... No
Probing for `Microchip MCP9804'... No
Probing for `Microchip MCP98242'... No
Probing for `Microchip MCP98243'... No
Probing for `Microchip MCP98244'... No
Probing for `Microchip MCP9843'... No
Probing for `ON CAT6095/CAT34TS02'... Success!
(confidence 5, driver `jc42')
Probing for `Atmel AT30TS00'... No
Client found at address 0x1a
Probing for `Analog Devices ADM1021'... No
Probing for `Analog Devices ADM1021A/ADM1023'... No
Probing for `Maxim MAX1617'... No
Probing for `Maxim MAX1617A'... No
Probing for `Maxim MAX1668'... No
Probing for `Maxim MAX1805'... No
Probing for `Maxim MAX1989'... No
Probing for `Maxim MAX6655/MAX6656'... No
Probing for `TI THMC10'... No
Probing for `National Semiconductor LM84'... No
Probing for `Genesys Logic GL523SM'... No
Probing for `Onsemi MC1066'... No
Probing for `Maxim MAX1618'... No
Probing for `Maxim MAX1619'... No
Probing for `National Semiconductor LM82/LM83'... No
Probing for `Maxim MAX6654'... No
Probing for `Maxim MAX6690'... No
Probing for `Maxim MAX6680/MAX6681'... No
Probing for `Maxim MAX6695/MAX6696'... No
Probing for `Texas Instruments AMC6821'... No
Probing for `ST STTS424'... No
Probing for `ST STTS424E'... No
Probing for `ST STTS2002'... No
Probing for `ST STTS3000'... No
Probing for `NXP SE97/SE97B'... No
Probing for `NXP SE98'... No
Probing for `Analog Devices ADT7408'... No
Probing for `IDT TS3000/TSE2002'... No
Probing for `Maxim MAX6604'... No
Probing for `Microchip MCP9804'... No
Probing for `Microchip MCP98242'... No
Probing for `Microchip MCP98243'... No
Probing for `Microchip MCP98244'... No
Probing for `Microchip MCP9843'... No
Probing for `ON CAT6095/CAT34TS02'... Success!
(confidence 5, driver `jc42')
Probing for `Atmel AT30TS00'... No
Client found at address 0x48
Probing for `National Semiconductor LM75'... No
Probing for `National Semiconductor LM75A'... No
Probing for `Dallas Semiconductor DS75'... No
Probing for `National Semiconductor LM77'... No
Probing for `Analog Devices ADT7410/ADT7420'... No
Probing for `Analog Devices ADT7411'... No
Probing for `Maxim MAX6642'... No
Probing for `National Semiconductor LM73'... No
Probing for `National Semiconductor LM92'... No
Probing for `National Semiconductor LM76'... No
Probing for `Maxim MAX6633/MAX6634/MAX6635'... No
Probing for `NXP/Philips SA56004'... No
Probing for `SMSC EMC1023'... No
Probing for `SMSC EMC1043'... No
Probing for `SMSC EMC1053'... No
Probing for `SMSC EMC1063'... No
Client found at address 0x50
Probing for `Analog Devices ADM1033'... No
Probing for `Analog Devices ADM1034'... No
Probing for `SPD EEPROM'... Yes
(confidence 8, not a hardware monitoring chip)
Probing for `EDID EEPROM'... No
Client found at address 0x52
Probing for `Analog Devices ADM1033'... No
Probing for `Analog Devices ADM1034'... No
Probing for `SPD EEPROM'... Yes
(confidence 8, not a hardware monitoring chip)
Now follows a summary of the probes I have just done.
Just press ENTER to continue:
Driver `w83627ehf':
* ISA bus, address 0xa10
Chip `Winbond W83627DHG Super IO Sensors' (confidence: 9 )
Driver `jc42':
* Bus `SMBus I801 adapter at 0400'
Busdriver `i2c_i801', I2C address 0x18
Chip `ON CAT6095/CAT34TS02' (confidence: 5)
* Bus `SMBus I801 adapter at 0400'
Busdriver `i2c_i801', I2C address 0x1a
Chip `ON CAT6095/CAT34TS02' (confidence: 5)
Driver `to-be-written':
* ISA bus, address 0xca2
Chip `IPMI BMC KCS' (confidence:
Driver `coretemp':
* Chip `Intel digital thermal sensor' (confidence: 9)
Warning: the required module jc42 is not currently installed
on your system. If it is built into the kernel then it's OK.
Otherwise, check http://www.lm-sensors.org/wiki/Devices for
driver availability.
Note: there is no driver for IPMI BMC KCS yet.
Check http://www.lm-sensors.org/wiki/Devices for updates.
Do you want to generate /etc/sysconfig/lm_sensors? (yes/NO): yes
Copy prog/init/lm_sensors.init to /etc/init.d/lm_sensors
for initialization at boot time.
You should now start the lm_sensors service to load the required
kernel modules.
Unloading i2c-dev... OK
I have accidentally put YES to "Enter [NO] to automatically generate the config file (last prompt)". Is this bad or how can I undo it?
Do you want to generate /etc/sysconfig/lm_sensors? (yes/NO): yes
Copy prog/init/lm_sensors.init to /etc/init.d/lm_sensors
for initialization at boot time.
You should now start the lm_sensors service to load the required
kernel modules.
Unloading i2c-dev... OK
-
Have you read the first post in this thread, which tells you to go read the wiki? I think step 5 talks about what directory the plugin resides. Best if you read and follow the instructions in the wiki.
Not sure if the wiki says this or not, but for my Windows rig I use Notepad++ to edit.
Sure, the step 6 which I posted above talks about installing perl package, this is where I stopped as I dont know how(and where) to edit plugin to force perl installation.
Step 5 in Wiki talks about where to save sensors.conf file.
Ok, I have notepad++ so thanks for letting me know about "go" file.
-
Ok, I have a few basic problems here regarding getting the temp senosors done. I have Supermicro X8SIL board, bellow is console response to "sensors".
root@Tower:~# sensors
coretemp-isa-0000
Adapter: ISA adapter
Core 0: +35.0 C (high = +89.0 C, crit = +105.0 C)
Core 2: +35.0 C (high = +89.0 C, crit = +105.0 C)
Tried installing perl package to get "sensors-detect" output, but I stopped here as I don't know how to successfully install perl package? Where is Dynamix system Temp plugin located and what/how do I edit it as it is explained bellow;
- Or for Dynamix, you can modify the Dynamix System Temp plugin itself, by locating the line ending with "# perl scripting" and replacing "no-install" with "do-install". Then re-install the plugin or reboot.
After that do I need only sensors.conf file or do I need to edit "go" file also? Never done that before, so I feel a bit overwhelmed.
-
Hm, one of my brand new WD20EARS refuse to preclear, it stops at 3% of pre-read. I have tried on mb sata ports, saslp-mv8 and even second unraid server, same thing all the time. It never spits out any error and I can terminate it with ctrl+C. Any other test I could try if the drive is bad?
Anyway, congrats to all the work you have done 
glad it's working. I assume the temps look correct to you. Some people have to switch the labels around in sensors.conf so cpu is actually the cpu, etc. I didn't have to do that for mine.
Recommended controllers for Unraid
in Storage Devices and Controllers
Posted
I need to finally swap out marvel based sas cards. I am using Supermicro X8SIA-F board with PCIe 2.0 slots. On ebay, the cheapest cards are newer PCIe 3.0, specifically 9207-8i can be bought for 20€, while 9211-8i are 30€. Since the difference is minimal, I am leaning more towards 9207 in case I upgrade the MB in the future, but if for any reason 9211 are better performing in native 2.0 slots I would go with that. Any thoughts?