HP Microserver

PhireSide said:
Yip, this is how I would do it if I were you:

  • Mod BIOS to enable OS booting from ODD SATA (https://n40l.fandom.com/wiki/Bios)
  • Install OS of choice to SSD connected to ODD SATA port (for the sake of this example let's use OpenMediaVault - https://www.openmediavault.org/)
  • Setup 2TB in Bay 1 - setup your file shares as preferred
  • Once you get your other drives, setup SnapRAID and use Bay 1 - 3 for data and Bay 4 for the parity drive. Your parity drive needs to be as big as your largest pool drive. So if you have 4TB data drives, your parity drive needs to be the same size
  • Setup Mergerfs to pool the three drives together as a single mount point
  • I used some tutorials from TechnoDadLife aka Kiefer Sutherland's stunt double - he is active on YouTube and has some nice, clear tutorials that you can follow if you get stuck. He also has a very nice setup video for OMV specifically -
Click to expand...
Thanks, will try it out tonight
 
@IceQB I also highly recommend you install Krusader once you are up and running. It is a lot like Total Commander, inside a VNC session or NoVNC session inside a web browser which makes interfacing with files much easier when working on a headless system:

1616183996460.png

Obligatory YT vid:

 
Anyone got the UniFi controller to work in OMV docker container?
 
IceQB said:
Anyone got the UniFi controller to work in OMV docker container?
Click to expand...
Yes, I'll post up my docker run command in a sec

Code: 
docker run -d -p 10001:10001/udp -p 3478:3478/udp -p 5514:5514 -p 6789:6789 -p 8080:8080 -p 8443:8443 -p 8843:8843 -p 8880:8880 -e PGID=100 -e PUID=1000 --name=unifi --restart=unless-stopped -v /home/docker/unifi/config:/config linuxserver/unifi-controller

It's worth noting that it takes around 3 minutes for the container to load fully on my system.
 
Last edited:
Thanks, will give it a shot when I get back home.
Been running in circles trying it get it working today
 
IceQB said:
Thanks, will give it a shot when I get back home.
Been running in circles trying it get it working today
Click to expand...
No problem.

Are you receiving any error messages? I had an issue with the adoption of my one AP initially. I had to use the set-inform command to get it to see my controller on the first startup
 
PhireSide said:
No problem.

Are you receiving any error messages? I had an issue with the adoption of my one AP initially. I had to use the set-inform command to get it to see my controller on the first startup
Click to expand...
No matter which way I try installing I end up with same problem. Login incorrect error
 
IceQB said:
No matter which way I try installing I end up with same problem. Login incorrect error
Click to expand...
Post up the output of the Docker logs and I'll have a look and see if I can spot anything. Also the Docker run cmd.

Do you have write permissions on the directory that you're storing the data in?
 
PhireSide said:
Post up the output of the Docker logs and I'll have a look and see if I can spot anything. Also the Docker run cmd.

Do you have write permissions on the directory that you're storing the data in?
Click to expand...
Code: 
---
version: "2.1"
services:
  unifi-controller:
    image: ghcr.io/linuxserver/unifi-controller
    container_name: unifi-controller
    environment:
      - PUID=998
      - PGID=100
      - MEM_LIMIT=1024M #optional
    volumes:
      - /config/unifi:/config
    ports:
      - 3478:3478/udp
      - 10001:10001/udp
      - 8088:8080
      - 8443:8443
    restart: unless-stopped

Yes have right permissions
Using stack to run containers in portainer
 
IceQB said:
Code: 
---
version: "2.1"
services:
  unifi-controller:
    image: ghcr.io/linuxserver/unifi-controller
    container_name: unifi-controller
    environment:
      - PUID=998
      - PGID=100
      - MEM_LIMIT=1024M #optional
    volumes:
      - /config/unifi:/config
    ports:
      - 3478:3478/udp
      - 10001:10001/udp
      - 8088:8080
      - 8443:8443
    restart: unless-stopped

Yes have right permissions
Using stack to run containers in portainer
Click to expand...
A few things to check:

Login to the server as your default account and type id and hit enter. That should give you your UID and GID. That should match the settings above to make sure that the container is running as the correct user. If you have another user (non-root, for example) then it needs to match that user's UID and GID. An easy way to retrieve that is by typing cat /etc/passwd and hitting enter. Look for your username and make sure the digits after the colon matches the settings in the container. UID should match PUID and GID should match GUID.

An example user would look like this:

phireside:x:1000:100

where phireside is the username, 1000 is the UID and 100 is the GID.

I also see the port mapped to 8080 is 8088 on the exposed port; is this intentional or perhaps a typo? I haven't used Stack before but the syntax just looks like a normal docker-compose.yml file so it shouldn't matter at all.

Everything else looks fairly normal. Are you seeing the initial config screen upon the first login and is it failing to log you in once the setup is complete?
 
IceQB said:
Code: 
---
version: "2.1"
services:
  unifi-controller:
    image: ghcr.io/linuxserver/unifi-controller
    container_name: unifi-controller
    environment:
      - PUID=998
      - PGID=100
      - MEM_LIMIT=1024M #optional
    volumes:
      - /config/unifi:/config
    ports:
      - 3478:3478/udp
      - 10001:10001/udp
      - 8088:8080
      - 8443:8443
    restart: unless-stopped

Yes have right permissions
Using stack to run containers in portainer
Click to expand...
Take this from whence it comes - i.e. a total Docker noob (read: idiot) - but when recently setting up a HTPC on a Pi I had problems with the pulling of incorrect images from ghcr.io.

The problems were resolved by pulling the images from linuxserver (rather than gchr.io/linuxserver).
 
PhireSide said:
A few things to check:

Login to the server as your default account and type id and hit enter. That should give you your UID and GID. That should match the settings above to make sure that the container is running as the correct user. If you have another user (non-root, for example) then it needs to match that user's UID and GID. An easy way to retrieve that is by typing cat /etc/passwd and hitting enter. Look for your username and make sure the digits after the colon matches the settings in the container. UID should match PUID and GID should match GUID.

An example user would look like this:

phireside:x:1000:100

where phireside is the username, 1000 is the UID and 100 is the GID.

I also see the port mapped to 8080 is 8088 on the exposed port; is this intentional or perhaps a typo? I haven't used Stack before but the syntax just looks like a normal docker-compose.yml file so it shouldn't matter at all.

Everything else looks fairly normal. Are you seeing the initial config screen upon the first login and is it failing to log you in once the setup is complete?
Click to expand...
GID I have there is correct for account used.
Using different as 8080 being used by another container.
 
rrh said:
Take this from whence it comes - i.e. a total Docker noob (read: idiot) - but when recently setting up a HTPC on a Pi I had problems with the pulling of incorrect images from ghcr.io.

The problems were resolved by pulling the images from linuxserver (rather than gchr.io/linuxserver).
Click to expand...
I'll give this a go, see if it works
 
Was bit busy, decided to give it a go today.
Worked first time
Now I have problem adopting my AP's, stuck on adding...
 
IceQB said:
Fixed last night
Port assignment problem
Click to expand...
Great to hear that you managed.

Mine is still chugging along nicely. I turned off some unused containers, but have around 10 running at any given time. It handles it all super well still, despite a relatively weak CPU. The initial startup after a reboot does take a while (3 or 4 minutes before I am able to ping the IP) but given the age of the platform, it's probably not too bad.
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X