sse450

No as far as I see on the backplane. Question: I know that HPE pushes us to use the HPE branded dard disks. My disks are not HPE branded. I use 2x 10T HGST Helium and 2x 512GB Samsung Pro 850. Could the server locks itself up because of the consumer disks? I am aware that non-HPE disks may cause high fan noise. Could my problem be something like that? But, even so, there must be some other similar complaints on the internet. But I have never seen any problem like that.

The firmware is the latest. No. Once the "damage is done", even the B140i doesn't see any LFF HDDs. No problems with SSDs. Frankly speaking, I asked this question on many HPE related forums. Nobody had seen such a problem.This strengthens the idea that it was a DOA. My courage is getting higher to order a new ML150 Gen9.

Yes, of course. Even after replacing the hot swap cage with a new one, the very same LFF drives are detected by the bios. Perhaps this is possible. But, the firmware is the latest. Even, I tried the spare ROM with no solution. I tried with LSI 9207-8i PCIe card. Same problem. To me, the most important clue is replacing the hot swap LFF cage solves the problem, albeit until I insert 2x LFF HDDs and 2x SSDs. As soon as I insert them, I revert back to the square one with a damaged (or somehow corrupted) LFF cage backplane. I am in the eve of a decision. If we believe that my ML150 Gen9 is really DOA, not a design fault, then I will request for another ML150 Gen9.

The problem is not about disappearing after unRAID starts. It is a detection problem by the BIOS. BIOS of the Proliant doesn't see the 3.5" HDDs. unRAID has nothing todo if the BIOS cannot detect the HDDs. Anyway, a couple of weeks ago, I asked this problem on this forum: https://lime-technology.com/forums/topic/71583-my-server-lost-all-35-hdds-but-keep-25-ssds/?tab=comments#comment-657485 There is a diagnostics file attached in my post. It happens in this sequence: 1. Perfectly working order with 2x LFF HDDs + 1x SSD 2. Poweroff the server 3. Insert a 2nd SSD (totalling 2x LFF HDDs + 2x SSD) 4. Power on the server 5. BIOS detects only 2x SDDs. Nothing about LFF HDDs. From this point on, the server is broken somehow. 6. Poweroff server 7. Insert just 1x LFF HDD and nothing else (for testing) 8. The server still cannot detect the HDD. It means the damage is done and irreversible. No way to get it detect any LFF HDD. 9. Poweroff server. 10.Replace the backplane with a new one 11.Insert 2x LFF HDDs + 1x SSD 12.Go to 1st step above. And so on. I have never seen such a problem before. Stumped. Thank you for taking time to help me.

The onboard controller is B140i. But I disabled it and selected AHCI in the BIOS . So, no RAID at all. But just for testing, I installed LSI 9207-8i on PCIe slot. The result was the same, ie. After the problem happens, it showed only the SSds not any of LFF HDDs. It seems to me that something is wrong with hot plug backplane of the HDD cage. But, the replaced backplane showed the same behaviour as well. Thanks for helping.

Dear @1812, I have a problem with my Proliant. I would appreciate if you or any other Proliant user here can shed a light. I have a ML110 Gen9 which is working fine with unRAID and 3x LFF HDDs and 2x SSDs. SSDs are in 2.5"-to-3.5" caddies. I needed a second unRAID server. 3 weeks ago, I bought a ML150 Gen9. Installed unRAID (on USB) with 2x LFF HDDs and 1x SSD (with 2.5" to 3.5" converter). All was fine. I needed to install a second SDD to make a cache pool. As soon as I install the second SSD (the 4th in the cage), something happened to server. From this moment on, the server wouldn't detect any LFF HDD. There is no problem with SSD though. After long conversation with HPE tech and many resets (inc SW6), it was not possible to correct. Then, the HPE tech replaced the backplane. All was fine again (seemingly). As soon as I install 2x LFF HDDs and 2x SSDs, the problem repeated again. HPE had to issue a DOA report. What should I do? I am afraid the problem will repeat if I get another ML150 Gen9. Or should I go for ML110 Gen9 as it is tested. By the way, all HDDs and SSDs are non-HP brands. Thanks for your help.

I now start with the same www.conf which comes in the container. It is mounted and working. There is a minor quirk in the container log though: [cont-init.d] 10-adduser: exited 0. [cont-init.d] 20-config: executing... sed: can't move '/etc/php7/php-fpm.d/www.confLlDcol' to '/etc/php7/php-fpm.d/www.conf': Resource busy sed: can't move '/etc/php7/php-fpm.d/www.confKEBBng' to '/etc/php7/php-fpm.d/www.conf': Resource busy [cont-init.d] 20-config: exited 0. [cont-init.d] 30-keygen: executing... using keys found in /config/keys [cont-init.d] 30-keygen: exited 0. [cont-init.d] 40-config: executing... [cont-init.d] 40-config: exited 0. [cont-init.d] 50-install: executing... [cont-init.d] 50-install: exited 0. [cont-init.d] 60-memcache: executing... [cont-init.d] 60-memcache: exited 0. [cont-init.d] done. [services.d] starting services [services.d] done. Despite the warning, it seems working. Thanks for your help.

Still no go. Edit: Dumb me! The path was wrong. But still with errors. [15-May-2018 14:20:54] ERROR: [/etc/php7/php-fpm.conf:2] Array are not allowed in the global section [15-May-2018 14:20:54] ERROR: failed to load configuration file '/etc/php7/php-fpm.conf' [15-May-2018 14:20:54] ERROR: FPM initialization failed Edit2: It writes php-fpm.conf, but I have just checked. It is /etc/php7/php-fpm.d/www.conf. How come it changes to php-fpm.conf, I don't know.

Nice to know this, but unfortunately I couldn't mount it. -v '/mnt/user/appdata/nextcloud/php/www.conf':'/etc/php7/php-fpm.d/www.conf':'rw' This gives error. Could you elaborate on this? Thank you.

Dear @CHBMB, is it possible to mount /etc/php7/php-fpm.d/www.conf on host? The default www.conf is pretty limiting.

I think something is wrong with GUI of NFS settings on a share page. If I change Export from No to Yes, nothing happens in /etc/exports. But, If I change Security, from Public to Private and then back to Public, unRAID creates the correct entry in /etc/exports.

I am running 6.5.1-rc5. Settings | NFS | Enable NFS = Yes. On a share page | NFS Security Settings | Export = Yes, Security = Public. It seems all look OK but still I cannot export any NFS share. By the way, /etc/exports and /var/lib/nfs/etab are empty. Is it a bug? Or am I doing something wrong? Thanks.

Thank you for this container. Working nicely without any extra effort. One question though. The user and group ids are 999 in /mnt/user/appdata/postgres. I would like to map them unRAID's 99 and 100 for nobody and users. What are the variables of user and group id inside the container? PUID and PGID?

I had a working letsencrpyt+nextcloud dockers with cloudflare wild card dns cert. I relocated the server to a new physical location with again a static IP. However, lan ip range was also changed from 192.168.1.* to 10.0.0.*. I changed unRAID ip fine. I also changed all A records at cloudflare for the new IP and made the necessary port forward (443 --> 444, 80 --> 81). Restarted the docker without any error. I did also the changes in NC config.php. But, still I cannot access to nextcloud using https://cloud.mydomain.com.The browser says that it is an illegal certificate. What am I missing? Thanks. EDIT: Never mind. The port was wrong. Thanks.

I have seen some other posts in this thread with the below problem: 180318 16:49:39 mysqld_safe Starting mysqld daemon with databases from /config/databases 180318 16:49:42 mysqld_safe Logging to syslog. It is said that this problem is related to an unclean shutdown from which I normally avoid. May I ask how often do users of this container face with this problem? If an "unclean" shutdown corrupts the mariadb so easily, perhaps it is better to use mariadb in a VM at a production setting. Opinions please. Thank you.

Yesterday, I updated mariadb and nextcloud containers, both from LS.io. Today, I noticed that mariadb is corrupted and not starting the dbs. I am not saying that this problem is directly related to updating containers, but it is a chronological fact. I don't have a backup of mariadb (yet). What is the best course of action for me? Delete the mariadb container and db files and reinstall? I can create a new nextcloud database on the new mariadb container. But, how can I get nextcloud to initialize the empty nextcloud database as NC did at the very beginning? Or should I reinstall nextcloud container as well? I am stumped. Please help.

I have the same problem. How can I understand that my cache SSDs are faulty? And what should I do considering I don't backup. It seems, if this problem is associated with the db files, there is no point in deleting the mariadb docker and install again.

Thank you.

@CHBMB, thank you for the command line instructions linked to the first post. Upgraded nextcloud without any problem using your CLI method. I have a question though. nextcloud docker is still marked as "update ready" on Docker page and Fix Common Problems plugin. Should we ignore them? Or should we upgrade the container as well?

Could anybody installed elasticsearch on this container? If so, I would love to hear about your installation. Thank you.

I finally got nextcloud with letsencrypt running following @CHBMB guide on ls.io with nextcloud.mydomain.com subdomain. I would like to change subdomain from nextcloud.mydomain.com to just cloud.mydomain.com. Does it suffice to change all references of nextcloud.mydomain.com to cloud.mydomain.com in site nginx/site-confs/nextcloud and nextcloud's /config/www/nextcloud/config/config.php. Let's assume that I added cloud as an additional subdomain to letsencrypt docker and fixed DNS record. Do I need to change anything else?

My interpretation is that "leave it blank if reverse proxy is used". But, Sonarr didn't work when I left it blank.

That was it. Strange thing is that the question mark next to URL Base says "For reverse proxy support, default is empty". But, it works anyway with /sonarr. Thank you.

Dear friends, I tried to setup this container for a couple of days and arrived at a stupid position. Using https://hme.domain.com, I can connect to my server and see the "Welcome to our server" banner. So, nginx, certs, port forwarding, subdomain setup are all OK. If I use https://hme.domain.com/sonarr, then I just get "Sonarr Ver." in the top left corner and nothing else. Similarly, https://hme.domain.com/radarr prints "Radarr Ver." in the top left corner. Obviously, these are from the very bottom of sonarr and radarr pages. I think this shows that connection from the internet is OK. But, why can't I see the whole page of sonarr and radarr instead of just two words from the very bottom of these pages. The only additions to the /mnt/user/appdata/letsencrypt/nginx/site-confs/default are below: location /sonarr { include /config/nginx/proxy.conf; proxy_pass http://192.168.1.100:8989/sonarr; } location /radarr { include /config/nginx/proxy.conf; proxy_pass http://192.168.1.100:7878/radarr; } Does this problem ring any bell for anybody? Thank you for your support.