30021190

Mine worked for months and then one day just never worked again. I have 6 of them as a test cluster for work, only 4 ever went weird. All the same drives, bios etc etc

The server refused to boot and the ILO logs reported the error. It’s a false sensor 31.

Looks like Three doesn’t block it…

Mine rejected sata ssds with something like sensor 41 overheating but that sensor doesn’t exist…

Statping-ng has had some updates beyond the base.

Snorkeling is probably your best choice as it did show latency overall and not just up/down.

Just be cautious that the HP backplane can sometimes reject non-hp drives at random with a sensor error for a sensor that doesn’t exist…

Write your own selinux module with audit2allow.

I’m not at work so I can’t find the guides I use but this looks similar https://danwalsh.livejournal.com/24750.html

Start one? What you seeking and where…

Myself over NFS can have serious latency issues. Some software can’t correctly file lock over NFS too which will cause write latency or just full blown errors.

iSCSI drops however can be really really bad and cause full filesystem corruption. Also backing up iSCSI volumes can be tricky. Software will likely work better and feel happy however and underlying issues may be masked until they’re unfixable. (I had an iSCSI volume attached to vmware silently corrupt for months before it failed and lost the data even though all scrubs/checksums were good until the very least moment).

You can make your situations with with either technology, both are just as correct. Would get a touch more throughput on iSCSI simply down to the write confirmation being drive based and not filesystem locks / os based.

YMMV

I’ve had issues with this too and reverted back to rooted docker. I even tried podman and system NFS mounts that it binds too with varying issues.

It looks like you can’t actually do this with podman for varying reasons.

Power line adaptors

If the motherboard has a built in 2d video card you’ll be fine, otherwise you can try via serial which will be slow. Ipmi can sometimes do video or it’s serial over Lan.

Serial bit will be slow and might not be default so the first bit night be really tricky. Also some systems won’t post with a video card, especially in the consumer world.

I’d personally boot with a GPU then swap it out once the system is correctly configured for ssh access.

Why not just clone the boot partition after an install and then change the mount points in the fstab?

Or even just install grub or pxelinux onto the SD that then just directs you somewhere else.

Clover always felt very unstable and messy.

DL380 G9. Those bioses don’t support booting from PCIe at all.

They actually do but it can only be a HPE supported BootROM… anything non-HPE is ignored (weirdly, some Intel and Broadcom cards PXE boot without the HPE firmware but not all).

Most of these boards have internal USB and internal SD slots which you can boot from with any media, intact HPE sell a USB SD card raid adaptor for the usb slot. So I would recommend using SD card for this…

There might also be some magic/weirdness with IP routing in the kernel. Have a look at net.ipv4.ip_forward system variable.

Are you sure you’re not using local hostnames / DNS resolution?

You may also need to updates your nfs exports file for the new subnet. And also update systems on the fstab changes (daemon-reload).

My guess with that TDP is yes. Iirc it’s about 100W per connector.

Ports 80 and 443.

The cli is easy and you could just Cron (scheduled task) a bunch of commands to open the firewall, renew cert and close the firewall. It’s how I do it for some internal systems.

I’m not sure about anything you’re running but I would look into certbot.

Either using the basic web plugin or DNS plugin. Nginx would be simpler, you’d just have to open your web ports on certificate generation to pass the challenge.

I know some proxy tools have let’s encrypt support, such as traefik.

SQLite doesn’t like NFS, the file locking isn’t stable/fast enough so any latency in the storage can cause data loss, corruption or just slow things down.

However SQLite to MySQL is relatively peanuts, Postgres less so…

Still it’s a nice move for those that don’t run containers on a single host with local filesystems.