accumulated collection of notes about my server shenanigans
initial commit
+109
+1
.gitignore
+1
.gitignore
···
1
+
.obsidian
+44
pihole/setup.md
+44
pihole/setup.md
···
1
+
2
+
# Basic setup
3
+
4
+
Basic compose file, as found in the [PiHole docs](https://docs.pi-hole.net/docker/)
5
+
```yaml
6
+
services:
7
+
pihole:
8
+
container_name: pihole
9
+
image: pihole/pihole:latest
10
+
ports:
11
+
- "53:53/tcp"
12
+
- "53:53/udp"
13
+
- "8080:80/tcp"
14
+
environment:
15
+
TZ: 'Europe/Berlin'
16
+
WEBPASSWORD: 'TULLESACHE'
17
+
FTLCONF_LOCAL_IPV4: '192.168.178.3' # Replace with your IP of choice
18
+
DNSMASQ_LISTENING: 'all'
19
+
volumes:
20
+
- './etc-pihole:/etc/pihole'
21
+
- './etc-dnsmasq.d:/etc/dnsmasq.d'
22
+
- './resolv.conf:/etc/resolv.conf'
23
+
restart: unless-stopped
24
+
```
25
+
26
+
> [!NOTE]
27
+
> You might get the `failed to bind port 0.0.0.0:53/tcp: Error starting userland proxy: listen tcp4 0.0.0.0:53: bind: address already in use` error.
28
+
> In that case run:
29
+
> ```sh
30
+
> sudo lsof -i -P -n | grep LISTEN
31
+
> ```
32
+
>
33
+
>If the service bound to port 53 is systemd-resolved, like this:
34
+
>```sh
35
+
>systemd-r 589 systemd-resolve 15u IPv4 3019 0t0 TCP 127.0.0.53:53 (LISTEN)
36
+
>systemd-r 589 systemd-resolve 17u IPv4 3021 0t0 TCP 127.0.0.54:53 (LISTEN)
37
+
>```
38
+
>Edit `/etc/systemd/resolved.conf` and uncomment the 'DNSStubListener=yes' and change it to 'DNSStubListener=no'. If it doesn't exist, add it.
39
+
>
40
+
>And restart the service using
41
+
>```sh
42
+
>service systemd-resolved restart
43
+
>```
44
+
> It should start without the error now.
primergy-rx300-s8/Intel_OP_Performance_Tuning_UG_H93143_v1_0.pdf
primergy-rx300-s8/Intel_OP_Performance_Tuning_UG_H93143_v1_0.pdf
This is a binary file and will not be displayed.
+13
primergy-rx300-s8/access-bios.md
+13
primergy-rx300-s8/access-bios.md
···
1
+
## Access BIOS
2
+
3
+
> [!NOTE] Disclaimer
4
+
> The lack of video out during bootup may make it seem like nothing is happening
5
+
> This is normal
6
+
> The only video out during normal startup is a temporary Fujitsu flash screen
7
+
8
+
---
9
+
10
+
1. Startup the server
11
+
2. Wait for initial Fujitsu flash screen to pass
12
+
3. (repeatedly)Hit 'del'
13
+
4. Welcome to the BIOS
+17
primergy-rx300-s8/acpi_pad-high-cpu-use.md
+17
primergy-rx300-s8/acpi_pad-high-cpu-use.md
···
1
+
## Fix acpi_pad high cpu use
2
+
3
+
add the line
4
+
`blacklist acpi_pad`
5
+
to
6
+
`/etc/modprobe.d/blacklist.conf`
7
+
8
+
This will keep the acpi_pad driver from loading at boot time.
9
+
10
+
If you need to remove acpi_pad without a reboot you can use:
11
+
`modprobe –r acpi_pad`
12
+
This removes the driver. However, note that the driver will restart upon a reboot.
13
+
14
+
15
+
source:
16
+
- https://www.intel.com/content/dam/support/us/en/documents/network/omni-adptr/sb/Intel_OP_Performance_Tuning_UG_H93143_v1_0.pdf (3.3)
17
+
- [[Intel_OP_Performance_Tuning_UG_H93143_v1_0.pdf]] (3.3)
+7
primergy-rx300-s8/no-auth.md
+7
primergy-rx300-s8/no-auth.md
···
1
+
## No password for iRMC?
2
+
1. [[access-bios|Enter BIOS]]
3
+
2. In 'Server mngmt' look for iRMC / Load Default values
4
+
3. Set to true
5
+
4. Preferably set IPv4, DHCP tends to be spotty with iRMC.
6
+
5. Reboot
7
+
6. iRMC should now be accessible with default login "admin" password "admin" under the configured IPv4
+13
primergy-rx300-s8/remote-access.md
+13
primergy-rx300-s8/remote-access.md
···
1
+
## Mount remote ISO
2
+
1. Access iRMC ServerView
3
+
2. Click "Video Redirection (JWS)" - Downloads 'avr.jnlp'
4
+
3. Run ```sudo javaws 'path-to-jnlp'```
5
+
3.1 'javaws' might not be available; in that case, install it using:
6
+
```
7
+
sudo apt install default-jre
8
+
sudo apt install iceadtea-netx
9
+
```
10
+
4. In the newly opened window look for 'Media' -> 'Virtual Media Wizard'
11
+
5. Select ISO using 'Browse'
12
+
6. Hit 'Connect' - This might take a while
13
+
7. The ISO should now be available to boot
+10
zfs/Add cache drives.md
+10
zfs/Add cache drives.md