TUMS

Preclearing drives from those supermicro controllers is know to be problematic for some people. Never heard of it locking up a system like that though. It's best to preclear from the onboard controller like you're doing now.

I have an official APC serial cable (AP940-0625A) My supermicro board has an integrated serial port and I can't even get it to recognize my SMC1500 within unraid. I looked in bios and port is definitely active. Go to unraid and try all the different apcupsd settings including specify custom cable. No dice..... USB cable works fine but i'm still missing a bunch of reporting, can't get modbus to work over USB. I will try with my SMT1500 as soon as I can get the firmware updated.

Let me know if it works and if some what you used. sure np.

They sell pcie rs232 cards, i've ordered one so I can update the firmware on my SMT1500. I have a SMC1500 also. I will be testing both of these smart models within unraid soon. I normally run a APC Back-UPS RS 1500 with unraid and it obviously reports fine.

You can review unraid diagnostics and what not but if you don't have a smart-ups that supports MODBUS you're probably always going to get incomplete reporting/stats within apcupsd. You should try and contact APC to see if they have a firmware patch, they have released updates for some of their older model ups's. ....And then MODBUS has to be activated within the APC menu's on the unit itself (off by default see above post)

<snipped from apcupsd manual> MODBUS Driver MODBUS is APC's replacement for the aging 'apcsmart' (aka UPS-Link) protocol. It is recommended for modern (ex: SMT series) Smart-UPS models. As of 3.14.11, apcupsd supports the MODBUS protocol over RS232 serial interfaces. As of 3.14.13, apcupsd supports the MODBUS protocol over USB. Not all APC UPSes support MODBUS. New 2013 year Smart-UPS models are likely to support it out-of-the-box and firmware updates are available for some older models. APC/Schneider tech support is your best point of contact for determining if a certain model will support MODBUS. That said, APC knowledge base article FA164737 indicates MODBUS support is available for the majority of the SMC, SMT, and SMX model lines. The required apcupsd.conf settings for MODBUS are straightforward. For MODBUS serial RS232: ## apcupsd.conf v1.1 ## UPSCABLE smart UPSTYPE modbus DEVICE /dev/ttyS0 LOCKFILE /var/lock UPSCLASS standalone UPSMODE disable The DEVICE setting identifies the serial port to which the UPS is connected. This can take the form of COM1, etc. on Windows or /dev/XXX on UNIX systems. You should use the APC-supplied serial cable (P/N 940-0625A) that ships with the UPS. Other 'smart' type cables may work, but only 940-0625A has been formally tested at this time. For MODBUS USB: ## apcupsd.conf v1.1 ## UPSCABLE usb UPSTYPE modbus DEVICE LOCKFILE /var/lock UPSCLASS standalone UPSMODE disable The DEVICE setting can be left blank or, optionally, set to the serial number of the UPS. If DEVICE is blank, apcupsd will attach to the first APC UPS it finds, otherwise it will attach to the specific UPS identified by the serial number. Note that most UPSes ship with MODBUS support disabled by default. You must use the UPS's front panel menu to enable MODBUS protocol support before apcupsd will be able to communicate with the UPS. You may need to enable the "Advanced" menu option before the MODBUS protocol option will be visible.

I was reading a while back that APC smart-ups is not fully compatible with apcupsd. Something about APC using a proprietary protocol for the smart-ups series? I think the guys at apcupsd were complaining about it. Anyway you might want to try and research more about it. I just vaguely remember reading about it.

LSI.

Correct. Needo docker uses plex pass.

Norco cases are plenty good enough for home Nas/media server use. It might not be as heavily built or have drive failure lights but they are also about 1/3rd the cost.

I disagree that it's an unraid issue. My Synology 1513+ wasn't showing up with Win 10 just like my unraid server. Until I pin it to quick access, then everything is fine.

Yeah when I was running it I had to pin it to quick access to get it to work consistently. I have since gone back to win 7.... 10 is a mess IMO.

My Norco 4224 came stock with SAS3 12Gb backplanes. I think I prefer the norco cases. Plus you get to choose what psu goes into it. If I were to buy a SM case i'd most likely have to swap out the power supply anyway. Just way too noisy.

Or this board... http://www.newegg.com/Product/Product.aspx?Item=N82E16813182959 That has a shared ipmi with one of the lan ports

Send it back and buy a brand new supermicro board. It's what I would do. Your call though... http://www.supermicro.com/products/motherboard/Xeon1333/#1366

v6.1.4 & the tunable setting (md_sync_thresh) should fix parity speed issues. The red ball issues are a totally different problem afaik.

For me plex has been crashing ever since the 0.9.14.4 update. I'm using plex android app and my bluray rips refuse to play. I can play dvd rips but the plex server eventually crashes 5 minutes into a movie.

I also have problems with my AOC-SAS2LP-MV8 cards being able to preclear drives from them I get "A mandatory SMART command failed" error and the preclear will stop. Not a huge issue since I have sata ports on my motherboard I can preclear from. Otherwise the SAS2LP works fine for me since v6.1.4. I get decent parity check speed. If I had it to do over again though I wouldn't have bought them. I think IBM M1015 controllers are a safer bet for all around compatibility in unraid.

Yeah it needs to be IT mode.

Yeah I don't know then. It looks like it's flashed correctly. Maybe somebody else has an idea. You sure the drive is actually spun up? EDIT after looking at your log again it's showing under capabilities RAID. Mine doesn't show that. This is exactly what mine shows. My bet is that your card isn't flashed fully for some reason. Dec 1 08:14:50 Tower kernel: mpt2sas0: LSISAS2008: FWVersion(20.00.04.00), ChipRevision(0x03), BiosVersion(07.39.00.00) Dec 1 08:14:50 Tower kernel: mpt2sas0: Protocol=(Initiator,Target), Capabilities=(TLR,EEDP,Snapshot Buffer,Diag Trace Buffer,Task Set Full,NCQ)

hmmm, boot into unraid with the card installed. Look in tools->system log and make sure it lists a LSI card in "initator target" mode. Should show something like this.... Yours should list FWVersion 19.XXXX Dec 1 08:14:50 Tower kernel: mpt2sas0: LSISAS2008: FWVersion(20.00.04.00), ChipRevision(0x03), BiosVersion(07.39.00.00) Dec 1 08:14:50 Tower kernel: mpt2sas0: Protocol=(Initiator,Target), Capabilities=(TLR,EEDP,Snapshot Buffer,Diag Trace Buffer,Task Set Full,NCQ)

Maybe try a different slot or a different MB.

Yep, that's what you want to use.

Yeah, that's fine. I went straight to P20 on my 2 lsi 9220-8i cards. All is working good.

Appreciate the recommendation. These take new 1151 motherboards........ and I think require DDR4 ram (vs DDR3). Are you aware of any advantages in moving to this generation vs. staying with the last generation? At one time I always had to have the newest/best....now (in my old age of ~40) I try to make sure there is a reason to do it. speedbal DMI 3.0 and support for up to 64GB DDR4 ECC. 14nm chip vs 22nm. Means it should run cooler and faster. Probably draw slightly less power. I haven't seen any passmark scores on them yet. If I was buying an E3 today it's what I would buy. Supermicro should have motherboards out soon if not already.