ddumont

From what I read, it was statically linked. Perhaps I'm wrong.

There may be other ways to get at the low level info. This isn't my wheelhouse, so I don't know how involved this will be

From the research I did, the driver is already in the kennel for a while now for their utility to use. Most os' only need their binary to see the drives, smart stats, temps, array configs, etc. I already played with it in unRAID and it seemed to work well. To unRAID, it looks like with this controller the built arrays show up as single drives.

answering myself a little here... this seems like a good example plugin with source: https://github.com/theone11/serverlayout_plugin

I've been poking around for a bit, looking at those plugins in the CA interface... I don't see any links to github or something. The plugin forum has some stickies in it with links to plugin doc and conversations about a template... but I wasn't seeing a good place to just look and see what a plugin is. What is a plg file? is it a renamed tgz? Is there something like a https://gitpod.io workspace that can be used as a demo with common build process or something? I'm curious to play around.

It looks like they show up as drives. (but each entry is a 4x drive RAID 10 array) Their utility is a self contained binary and will list the devices and a ton of information about them including health. I was hoping to pipe some of that health data to any place unRaid currently monitors drive health. On that subject, can I get unraid to send emails on drive health events?

Sure. storage-diagnostics-20220608-2108.zip

Yes and I never implied that it was. I thought I was pretty clear. My question was if I plugins could support adding temp/smart/etc monitoring to the Array UI or not. I am not confusing RAID (which I am doing in hardware) with unRAID's normal array operation (which is not RAID and does not meet my needs for performance, and data security)

Yeah I started with plain drives /w 2x parity and the performance was so incredibly bad that I really had no choice.

I was wondering if I could try to go down this route and package their binary to read the stats and eventually hook it up to something in the array view.

Just picked up one of these from ALLHDD.com for pretty cheap. Got some cheap cables and now I have a nice Raid 10 device to play with. I notice that the drivers for this seem to be in the os already. Also, their CLI tool runs and correctly reports things like logs, status, etc. https://storage.microsemi.com/en-us/downloads/storage_manager/sm/productid=asr-8805&dn=adaptec+raid+8805.php I'd like to be able to at least get SMART error reports, warnings, notifications through unraid. Is this something a plugin could do? Is this something that could go in the actual OS?

I also run a docker container with a dns server, and i point my home router to it as #1 and google's secure dns as #2 This lets me easily define any hostname I want to whatever I want. storage.at.home docker.at.home transmission.at.home plex.at.home etc...

So yeah... it looks like a lot of work, but it's not too bad. What does this get me, you may ask? Well, I have a docker container that runs nginx and actually proxies all of my web traffic on the box and containers (including unraid) with my certificate. I'll attach that here for info... the rules about web sockers are particularly important if you want working console shells on the unraid interface. Now, once you import the root cert into the unraid os as described above, you can have a docker.at.home registry container running to host your own custom images. I hope this helps some folks. nginx.template init.sh

I've been asked by a few how to go about creating the ca and issuing the certs. There's a lot of information online for using openssl and doing this kind of stuff, here's a "short" rundown of what's going on: https://gist.github.com/Soarez/9688998 So... i guess decide what you want your domain to be. Originally I wanted a tld (*.home) but you can't have wildcard certs for a tld, and I didn't want to issue a cert for everything I wanted to host... so I settled for (*.at.home). I call my unraid server storage.at.home. Here are the steps I took to create the ca: # create the CA key (you should put a password on this) openssl genrsa -out home.at.ca.key 4096 # create the CA certificate openssl req -x509 -new -nodes -key home.at.ca.key -days 18262 -sha256 -out home.at.ca.crt # Now import the certificate into your computer's root trust store. On windows, double click the crt file and open it: then click "Install Certificate..." Then pick if you want to install it only for the current user, or for every user on the machine: Then choose to place the cert in the trusted roots: click next, then finish... now you're done importing. One thing to remember, the ca is a root certificate you control and if compromised, it means certificates could be generated for sites like google, facebook, etc... and your computer would trust them. Root CAs are the backbone of the secure internet... make sure to protect your key... with your life! Now we generate our wildcard certificate for our web servers and stuff: # create the certificate key openssl genrsa -out home.at.wildcard.key 4096 # create a file with the following contents called ssl.conf (between the dashes) --- authorityKeyIdentifier=keyid,issuer basicConstraints=CA:FALSE [ req ] default_bits = 4096 distinguished_name = req_distinguished_name req_extensions = req_ext [ req_distinguished_name ] countryName_default = US stateOrProvinceName_default = localityName_default = organizationName_default = at.home commonName_max = 64 commonName_default = wildcard.at.home [ req_ext ] keyUsage = digitalSignature, nonRepudiation, keyEncipherment, dataEncipherment extendedKeyUsage = serverAuth subjectAltName = @alt_names [alt_names] DNS.1 = *.at.home --- # Now let's make a certificate signing request for our wildcard cert openssl req -new -key home.at.wildcard.key -out home.at.wildcard.csr -config ssl.conf # and now let's mint the cert with our CA openssl x509 -req -in home.at.wildcard.csr -CA home.at.ca.crt -CAkey home.at.ca.key -CAcreateserial -out home.at.wildcard.crt -days 18262 -sha256 -extfile ssl.conf -extensions req_ext Now you can use your wildcard cert for any webserver you want in your local deployment, and it will be valid on the computers you install your ca on.

I've seen this elsewhere on the forums that this feature could help people. In my case, I'd really like to be able to specify which nic/ip to bind ports to. If you have multiple nics, or you just want to have several things on port 80 and use all the 127.0.0.0/8 space. Right now, it seems it binds to 0.0.0.0 (all addresses) and I'd really like to be able to choose.