RevelRob

Ok thank you. I'll have to peruse through RDP Calibre to see what's up. I'm still curious as to how Heimdall can grow to now 9gb. I went through every setting and don't see anywhere where anything could be saved besides what's in /config. My log files are >100mb as well. Edit: I mean <100mb

Thank you for the quick reply. So is going to the respective folders through samba and checking that the files there match what are showing via the container console (navigate to those directories and `ls`) enough? If so, they all show the same file structure. ie. /mnt/user/eBooks/calibre library in samba shows the same files as opening container console, `cd /library`, `ls`. The RDP-Calibre one may be a bit more difficult to figure out; however, with only 1 path mapped in Heimdall (and the contents of /mnt/user/appdata/heimdall via samba matching /config in console... and showing up to date logs), I feel like I'm missing something. Apologies if I'm just not "getting it".

Anyone know why I would be getting this: My Volume Mapping seems to be correct. It reflects what's in the respective folder: Even though it's semi off topic, that RDP-Calibre is the only other container with an abnormal size. Looks like the mappings there are correct too:

Hi, I'm having trouble with reverse proxy-ing the admin page. Is this possible? The following works to access the library: location /ubooquity { proxy_pass http://IPADDRESS:2202/ubooquity; How would I access the admin page? I know that the port is 2203; however, it's the same base url ("reverse proxy prefix"), so I'm not sure what the location block and/or proxy pass should be. I've tried the following variations with no luck. Location: location /ubooquity/admin { location /ubooquity/admin/ { location /ubooquity-admin { location /ubooquity-admin/ { location /admin { location /admin/ { Proxy Pass: proxy_pass http://IPADDRESS:2203 proxy_pass http://IPADDRESS:2203/ proxy_pass http://IPADDRESS:2203/ubooquity; proxy_pass http://IPADDRESS:2203/ubooquity/; proxy_pass http://IPADDRESS:2203/ubooquity/admin; proxy_pass http://IPADDRESS:2203/ubooquity/admin/; Some of them give me this: instead of this: And in the Chrome Console, I get the following: Thanks for any help!

I’d also love to know how to go about doing this. I’d usually just mess around until I got it right, but messing with the boot drive scares the crap outta me.

So I ended up changing all of the controller ports to the default ones and changing the other container ports that were conflicting instead as every morning after an appdata backup, the devices went into the adoption loop and I had to set-inform again. It has been working well ever since; however, I had to take down my server for some hardware maintenance and when it was down, all of my devices lost network connection. I assume that it's because I put my unraid ip in "Networks -> DHCP UniFi Controller" and "Controller -> Controller Hostname/IP", ticked "Override inform host with controller hostname/IP" and un-ticked "Make controller discoverable on L2 network". With these settings, all of my devices obviously think that the unraid IP is the router. So, when unraid is down, no internet. Is this normal? Is there a way to have the USG be the router if the controller/unraid is down? Thanks for the help.

Any way to make this an option? pretty please? So I'm having a situation: Can't open /mnt/cache/appdata/myVPNserver/easy-rsa/easyrsa3/pki/index.txt.attr for reading, No such file or directory 23225341101888:error:02001002:system library:fopen:No such file or directory:crypto/bio/bss_file.c:74:fopen('/mnt/cache/appdata/myVPNserver/easy-rsa/easyrsa3/pki/index.txt.attr','r') 23225341101888:error:2006D080:BIO routines:BIO_new_file:no such file:crypto/bio/bss_file.c:81: Check that the request matches the signature Signature ok The Subject's Distinguished Name is as follows commonName :ASN.1 12:'server' Certificate is to be certified until Oct 22 03:00:00 2021 GMT (1080 days) ... stty: 'standard input': Inappropriate ioctl for device I'm using easy-rsa v3.0.6 Funny thing is I can connect to the server with my iPhone and changing the DNS works, but I can't ping any of my LAN IPs when on a data connection. If I connect to a separate remote Wifi network, everything works as planned.

Any way to make this an option? pretty please?

So I figured it out. Since my ports are different, I had to do it through the command line: ssh ubnt@$AP-IP mca-cli set-inform http://$address:8080/inform Use ubnt as the password to login and $address is the IP address of the host you are running this container on and $AP-IP is the Access Point IP address. i changed 8080 to 5080 (what I set it as), and was good to go. Thanks for the help!

Thanks for the help. So i pulled a new container, stopped the old container, modified the name, appdata location, put in bridge mode and restored it from a backup. I then made sure that "inform" was ticked, "L2" was un-ticked and my unraid machine IP was in the "Controller/Hostname IP". All of the ports you have, I have too; but I had to change some of the host ports as they are in use by other containers. I'm going through the adoption loop . I assume it's because the devices are already adopted to the other controller? I want to forget the devices and try to connect them to the new controller but the fear of losing them and going nuts trying to get them back is killing me.

Thanks for the quick reply. I'm not sure why I assigned it it's own IP as it was awhile ago when i set it up. Probably watched/read a tutorial and they were all based on the cloud key which has it's own ip, so I figured, why not? I also never have any issues with it set up this way. not sure why. How did you end up setting it up if you don't mind me asking?

Hi, I'm trying to use lsio LetsEncrypt in bridge mode to reverse proxy my lsio UniFi controller which I've assigned it's own IP. Is there still an issue with docker where containers can't talk to each other this way? Thanks!

Hi, First off, this plugin is awesome! Hopefully this is the right place for a feature request: I'd like to have a script run on startup/reboot of the server after Docker has finished starting up. The script starts a VM. My workaround: #!/bin/bash sleep 240 && virsh start uuid-of-vm I figure that the "At Startup Of Array" schedule in User Scripts would work; however, it is executed when the array BEGINS starting up and not when the array has COMPLETED starting up. Sure, I can increase the sleep interval to a longer time period but as the array gets larger and I add more containers/VMs, the sleep time would have to be adjusted. TL;DR Can more schedule options be added like: "Array Startup", "Array Startup Complete", "Docker Startup", "Docker Startup Complete", "VMs Startup", "VMs Startup Complete". For now, is there something I can add to the script that would allow it to run after a certain docker container has (or all docker containers have) started? Thanks!

Thanks for the reply johnnie.black. Yeah, I'm a bit ashamed of that setup. I just built a new machine, swapped over everything and ran another parity check. 0 errors! That said, I'm now getting another error on my SSDs: udma crc error count is 5. I got it yesterday too but it said 1 instead of 5 then. I hear it could be because of SATA cables not sitting right? Not sure. I have attached my new diagnostics file. Thanks for your help! tower-diagnostics-20181026-0957.zip

Hi, First off, excuse my ignorance. I'm kinda new to UnRAID and trying to figure this all out as I go. I am having a parity error issue. My last few parity checks had 515 errors so they're not being corrected ("Write corrections to parity" checkbox is checked). From googling, it looks like I have to do some sort of SMART check? I've attached my diagnostics. Thanks so much! tower-diagnostics-20181023-1637.zip

I come bearing pitchforks and hatred! ... for being such a n00b (is that word even used anymore?) So I'm a "spend hours messing with my server then forget about it for a month" type of person so I forget a lot of stuff and just want to confirm something before I do it and really appreciate any help. I am currently using a different repo's container. Not sure why, but I think it was because I was told that a feature I wanted was in the beta, and that repo has a beta branch. When I saw that the feature wasn't there, I didn't bother trying to change it to LSIO since I didn't wanna go through the hassle (and that container just worked). I went to check it out and notice it's still on 5.7.19 (which is definitely not Beta). So they aren't really maintaining it. After reading the last few pages of this thread, it makes a ton of sense to not mess with beta's for something that I'll get a ton of grief for by my family if it breaks the internet worse than Kim K's naked backside. If I want to switch to the LSIO container while keeping everything else the same, would I just have to do the following: Make a backup in the controller. Make note of the IP & Ports of the current container (I'm using br0 as network type and a custom IP). Delete the current container. Install the LSIO container, entering the IP (custom br0 is fine?) & Ports. (I assume that I need to use linuxserver/unifi:unstable as the LTS is older than the backup I'll make and won't work?) Restore the backup in the controller. Profit? Am I missing any crucial steps? Lastly, the current container I am using resets to default after every update. So I turned off auto update on it. Does this one do the same? Sorry again for the ignorance. I usually just mess around until things work (helps with learning... sometimes) but I don't wanna chance it with this. Thanks!

Updated to 07, removed bios, plugged everything in to both cards, prayed a bit to at least 3 deities... And she's good! Thanks so much again!

Ok. Thanks so much again.

Ok awesome. I didn't install a bios on the PERC anyways. And regarding updating the firmware? Should I update to the latest?

So I flashed the PERC with the instructions at the link you provided and it was easy peasy! New Config done and all is back to server goodness. Thanks so much! I was wondering one more thing... The 9201-16e is currently at 20.00.06.00-IT firmware and v7.39.02.00 (2015.08.03) bios. The Broadcom website lists 20.00.07.00 as the latest and I read somewhere that some P20 FW before 07 are not the greatest. Don't remember where I saw it. I am also looking to remove the bios for faster boot. I was searching around the forums for a similar tutorial for the 9201-16e and SAS2116 but could only find the Crossflashing Controllers Wiki which shows only info for the 9201-16i, not 16e; and it lists ooooold P10 & P11 firmwares. TL:DR Is there a tutorial I could follow to update the 9201-16e firmware and remove the bios? Thanks again.

Amazing! Thanks again!

Ok awesome. Thanks! To avoid doing the new config twice, Should I do the following? Remove all drives, flash PERC, attach drives to current (preferred) configuration, New config? Or is there a step in there that would actually make it more difficult as I assume then they'd all show up as wrong? Anything I should bear in mind before I start the process? Lastly, is the FreeDos bootable usb with sas2flash.exe the best way to flash? This T3600 doesn't allow me to go into a UEFI Shell unfortunately (unless I missed something). Any better ways you'd recommend? Maybe an already written tutorial (that LSI thread is a monster)? I went crazy figuring out how to update that dang 2801-16e. I don't have a spare machine with a spare PCIe slot to use to flash so I'd have to use the UnRAID machine. Thanks again and sorry for the ignorance. UnRAID and server hardware is new to me.

Thanks for the quick reply. Should I also flash the PERC to IT mode?

Hi, I have a Dell T3600 that came with a PERC H310. Running latest UnRAID stable. Unfortunately, I have used all of the space in the case for drives and purchased a LSI 9201-16e card to use with a DAS. After installing the LSI card, UnRAID did not recognize any of the drives I attached to it so I had to update the firmware with sas2flash via freedos. I followed this guide (but used freedos instead of UEFI Shell) and used this firmware. It's currently at 20.00.06.00-IT according to the bios which is at v7.39.02.00 (2015.08.03). Unfortunately, the one drive that I connected to the LSI card (which was originally connected to the PERC card) is showing as "Wrong" in the UnRAID Gui (See attached image). I tried removing the PERC card and attaching all of the drives to the 9201-16e; but then they all show as wrong. If I attach them all back to the PERC card, everything works fine. I know that the 9201-16e is IT mode only, so it's not a flashing issue (i think). I don't know what I'm doing wrong here. I know that there is a "New Config" option; however, I'm not sure if that's what I need to do. I have a feeling that it's the PERC card that although was playing fine until now, is not playing well with the 9201 since the 9201 is in IT and the PERC is not... but I'm not entirely sure. I can attach any logs; I just don't know which I'd need to attach. Thanks very much for any help!

I am having a similar issue where I installed an additional raid card in my server and moved one of the disks from the old card to the new one. Unfortunately, I'm getting the "wrong disk" error. Is there anything else I could do or is the New Config Utility the way? If so, what are the steps? start array first? mount disk? don't mount disk? Thanks.