Minho Ryang minhoryang

NoteAfterNote-7
Reading and writing a USB drive connected to a Linux server using Termux, termux-usb, usbredirect, and QEMU on a smartphone that is not rooted
Published: May 19, 2024
Link: https://gist.github.com/NoteAfterNote/7a197233de3d60ff1e23ca90ed2f595a
Updated: May 29, 2024

Termux: Enable Wake-Lock

Smartphone Configuration

Shopping List

Minisforum MS-01 Barebones

I was looking for mini PCs with SFP+ and found a lot of fairly expensive small servers that were tempting. Then I got lucky and saw a new product coming out from minisforum, the MS-01, which had everything I needed at a much lower pricepoint.

I went with the 20 core intel i9-13900H but I think any of the three would have been fine for my needs.

Fixing device UUIDs in BCD under Linux

Please note, it's easier to just use a recovery flash drive/dvd disk!

I just wanted a new challenge, and I found it:

Info on target system

My friend has switched from Windows to Fedora. Somehow in the process, Windows Bootloader went missing from EFI partition (I would love to know how did that happen as much as you do or don't, but I wasn't supervising at the moment, so... no idea)

Enable IPv6 OSPF Routing on Thunderbolt-Net Mesh

This requires proxmox kernel 6.2.16-14-pve or higher due to bugs in earlier version.s

This will result in a routable mesh network that can survive any one node failure or any one cable failure. Alls the steps in this section must be performed on each node

IPv6 OSPF connectivity over TB cluster network

Enable IPv6 forwarding

Using IPv6 to take advantage of not needing to use addresses - does make things simpler

ProxMox Cluster - Soup-to-Nutz

aka what i did to get from nothing to done.

note: these are designed to be primarily a re-install guide for myself (writing things down helps me memorize the knowledge), as such don't take any of this on blind faith - some areas are well tested and the docs are very robust, some items, less so). YMMV

Purpose of Proxmox cluster project

Required Outomces of cluster project

title

Cloud GPUs: Servers, Providers & Everything You Would Ever Need

Scaling Mastodon down

There is already a guide on scaling your Mastodon server up. This is a short guide on scaling your Mastodon server down.

I.e., maybe you want to run a small instance of <100 active users, and you want to keep your cloud costs reasonable. So you might be running everything on a single machine, with limited memory and CPU. (In my case, I was using a t3.medium instance with 2 vCPUs and 4GB of RAM.) How do you do this?

Note that I'm not a Ruby or Sidekiq expert, and most of this stuff I figured out through trial and error.

Content removed in accordance with GitHub's Terms of Service.

Thank you for your understanding.

Overview

Syncing an Ethereum node is largely reliant on latency and IOPS, I/O Per Second, of the storage. Budget SSDs will struggle to an extent, and some won't be able to sync at all. IOPS can roughly be used as proxy of / predictor for latency. Measuring latency directly is arguably better.

This document aims to snapshot some known good and known bad models.

The drive lists are ordered by interface and then by capacity and alphabetically by vendor name, not by preference. The lists are not exhaustive at all. @mwpastore linked a filterable spreadsheet in comments that has a far greater variety of drives and their characteristics. Filter it by DRAM yes, NAND Type TLC, Form Factor M.2, and desired capacity.

For size, 4TB is a very conservative choice. The smaller 2TB drive should last an Ethereum full node until at least sometime 2026, with the [pre-merge history expiry](https://hackmd.io/@hBXHLw_9Qq2va4pRt

	vSphere 6 Enterprise Plus:
	1C20K-4Z214-H84U1-T92EP-92838
	1A2JU-DEH12-48460-CT956-AC84D
	MC28R-4L006-484D1-VV8NK-C7R58
	5C6TK-4C39J-48E00-PH0XH-828Q4
	4A4X0-69HE3-M8548-6L1QK-1Y240

	vSphere with Operations Management 6 Enterprise:
	4Y2NU-4Z301-085C8-M18EP-2K8M8
	1Y48R-0EJEK-084R0-GK9XM-23R52