beanmeister

I guess my upgrade path has hit a brick wall. CPU is Pentium® Dual-Core CPU E6500.

I too would need to continue using the Docker container until I can upgrade my hardware to be able to run a VM without overtaxing my 16 years old system.

Upgraded from 9.5.21 to 10.0.162 using method 1 on page 32 without any issues.

Just curious if you are still using this Unifi Reborn docker since you have two gateways (assuming they are cloud gateways vs. UXG) running the Unifi Network server. How does that work having two instances running on your network? Did you have to update your APs to inform to the gateway instances? I am just trying to understand how the Cloud gateways works with or eliminate the need of running a Unifi Controller docker. I will be deploying a UXG-Lite since I did not quite understand how I would manage the cloud gateways from my current Docker Unifi Controller since they run their own Unifi network server.

Don't know if you have this resolved yet, but yes it is possible to load a self-signed P12 certificate into the Docker container using the keytool command (inside the Docker container) to import the certificate into the Unifi keystore. I believe this is the general commands I used (sorry it has been awhile since I imported my self-signed certificate) ###Runinng shell in docker container docker exec -it container-name sh ### Create a P12 file for Unifi openssl pkcs12 -export -out {your desired pfx/p12 file} -inkey {your private key} -in {your certificate file} -certfile {the signing intermediate} -password pass:{your desired pfx/p12 password} ### Backup the old cert and install the new one sudo mv /usr/lib/unifi/data/{pfx/p12 name as above} /usr/lib/unifi/data/{pfx/p12 name as above}.old sudo cp {pfx/p12 name as above} /usr/lib/unifi/data/{pfx/p12 name as above} ### Backup the old keystore and install the new one sudo mv /usr/lib/unifi/data/keystore /usr/lib/unifi/data/keystore.old keytool -importkeystore -destkeystore /usr/lib/unifi/data/keystore -srckeystore {pfx/p12 name as above} -srcstoretype PKCS12 -srcstorepass {pfx/p12 password as above} -deststorepass aircontrolenterprise -srcalias 1 -destalias unifi

@JorgeB I only plan to replace the one failed data drive. So I will just proceed with the parity swap for just one parity drive and once the failed drive is replaced, I will just replace the second parity with a larger drive. Thank you for the advice.

I have two parity drives (2TB) and one of my data disk (2TB) has failed. I would like to replace the two parity drives with new larger drives and then use one of 2TB parity drives to replace the failed data drive. How can I do a parity swap of the two parity drives and then replace the failed data drive? I see the procedure to swap one parity drive, do I just follow that for each of the parity drive or can I do them both at the same time?

So I found two sources regarding a SFF-8654 8i to 2x SFF-8087 cable by CableCC that may work. In this ServeTheHome thread and a user review of the CableCC on Amazon.

Wow, that would mean 6 adapters for me, too messy. What 8087 backplane are you using (make and model)?

Thank you @Wody for testing the Genuine Modules CAB-8654i8-2x8087 cable and verifying that going directly from a Broadcom 9500-16i and 9600-24i to a 8087 backplane does not work. I will try to email Genuine Modules to let them know. By any chance can you post a picture and information about the 6843+6843-8087 adapter in the working scenario?

Cool! Looking forward to your findings.

@Wody Can this cable be trusted to support SAS/SATA? This is a response to an inquiry I emailed to sales of GenuineModules regarding if their SFF-8654 to 2x SFF-8087 cable supports SAS/SATA or just NVMe.

Wow, I did not realized SFF-8654 to 2x SFF-8087 cable for SAS/SATA were non-existent. I guess I will look at the 9400-8i instead since I do not want to deal with adapters.

How about this? Supermicro X14SBI-F Intel Xeon 6511P Broadcom 9500-8i (3x) - I prefer to split the drives to 3 of the PCIe 8x slots. SFF-8654 to 2x SFF-8087 cable (3x) for the Norco RPC-4224 6 backplanes SFF-8643 to 4x SATA Forward Breakout Cable (for the 4 onboard SATA ports to 2.5" SSD drive cage) As of now, the only online vendor I can find that sells the motherboard and CPU is NewEggBusiness.

The X14SBI-F looks interesting. I like the fact that the Xeon 6700/6500 series have lower TDP versions than the CPUs supported by the X13SEI-F. I just have to figure out how I am going to connect the 6 backplanes of the Norco RPC-4224 to the X14SBI-F.

Upgraded to 7.1.0 and started the array with the one good device cache pool. Will look into replacing the failed device in the pool when I can physically access the server.

I am on 7.0.1. Should I upgrade to 7.1.0 then start the array? I believe it was a btrfs mirror. Or should I just remove the missing disk in 7.0.1 and start the array?

I have a cache pool of 2 disks. My server rebooted and now one of the disk is missing. Currently I am unable to physically access the server. Is there a way I can revert to a single disk cache and get my array online?

Will this SFF-8654 to SFF-8087 cable support SATA? Supposedly it supports SAS4 so I would assume the cable will work with SATA drives. The X13SEI-TF motherboard has 8x SATA ports via a slimline SAS 8i port. So I would plan to use this cable to connect those eight SATA ports to two of my Norco (SFF-8087) backplanes.

Just found out Norco is no longer in business. I have to rethink if I want to continue using the Norco 4224 chassis or use the opportunity to build a smaller server with bigger drives. I would hate to risk a backplane in the Norco failing and not be able to replace it.

Good catch on the 430-8i cards not being the correct form factor. I almost pulled the trigger and noticed that it was missing the connector tab that usually goes into the PCIe slot. As much as I would like to save on the wattage by going with the 9400-16i, I am trying to not concentrate so many drives on one HBA/PCIe 8X slot for better throughput and to be able to segregate SAS and SATA drives so that they are on separate PCIe/HBA/backplane. For example, one HBA in one PCIe 8X slot for two backplanes that will connect only SATA drives and another that will connect only SAS drives. I don't even know if mixing or segregating SAS from SATA drives matters regarding maximizing throughput, but it seems like something logical to do. It turns out the Xeon Silver 4510 CPU is not available as a retail box, but only as an OEM tray version, meaning no cooling included. Looks like the LGA-4677 CPU also needs a carriage, I am hoping that the carriage comes with the motherboard. Still searching for a SAS/SATA cable to connect the motherboard SFF-8654 (SATA0-7) to my two SFF-8087 backplanes. Can't believe no one else has ever encounter this scenario. Boy this build is starting out to be interesting with all the challenges.

So my current motherboard has two Intel NICs that are set up as a bonded with a static IP. I am using a Norco 4224 case with six SAS/SATA backplanes. 8 onboard SATA ports connected to two backplanes. Two Supermicro SATA2-MV8 HBAs to remaining 4 backplanes. If I replace the motherboard: If the new motherboard also has two Intel NICs, will the network settings carry over and continue to work? If I replace two Supermicro MV8 SATA HBAs with LSI 9400-8i HBAs, but the drives and backplanes remain the same, will the disks/array configuration carry over? Does unRAID cares if I rearrange the drives around in my drive bay? Just planning what to expect when I upgrade my motherboard and CPU.

Just verifying that I should be able to cross flash the Lenovo 430-8i cards to the LSI 9400-8i before I pull the trigger. The Lenovo 430-8i description says "...not compatible with non-ThinkSystem or standard desktop systems." Also, do I have to worry about putting the card in IT mode or is that with older cards?

Yoo hoo! I am now reborn and running my own certificate! I just had to copy over my P12 certificate file and run the keytool command within the docker container to import it into the keystore. Thanks for the help everyone. I am still using the 7.5.187 version, but I did not wanted to migrate and upgrade the version at the same time. Will let this new container run for a week or so before upgrading the version. Now back to reiserfs migration.

Looking to update my current Supermicro X7SBE Norco 4224 server (see signature) of 14 years. I would like to stick with a Supermicro board with IPMI and will be reusing my PSU and Norco 4224 chassis. I would like to use both SAS and SATA drives (segregated by HBA and backplane). Other on being my file server and media server, I currently run one docker (Unifi controller) and one VM (Windows 10 server), but would like a server robust enough to run others as the needs arise. As you can see from my current build, I am the type of build it and forget about it. So it has been 14 years since I last looked at computing technology and here is my first stab at a configuration with something that will remain relevant for the next 5-7 years and last me another 15 years. Proposed Build: Supermicro X13SEI-TF Likes: Plenty of PCIe slots with dedicated paths to CPU, 2x M.2 slots, Dual Intel 10GBase-T NICs, 10 onboard SATA (8 via Slim line SAS) Dislikes: Expensive CPU and memory options. Intel Xenon Silver 4510 Don't know if there's another option that won't break the bank. Will need a CPU cooler since this CPU is only available as OEM tray version. Nemix RAM 16GB RDIMM DDR5 5600MHz PC5-44800 Will get 2x for a total of 32GB of RAM Supposedly compatible with the recommended Supermicro memory LSI 9400-8i or Lenovo 430-8i (cross flashed to LSI 9400-8i) Will get at least 2, may need 3 if I can't find a SATA cable to connect the SFF-8654 SATA0-7 to my two SFF-8087 backplanes. May consider one LSI 9400-16i and one 9400-8i to save on wattage. Cables Needed: Slim line SAS (SFF-8654?) to SFF-8087 to connect onboard SATA0-SATA07 to two backplanes in Norco 4224. Need recommendations where to buy at reasonable price. SFF-8643 to SFF-8087 Is this the cable to connect the Lenovo 430-8i to Norco backplanes? Looking forward to seeing your suggestions.