Configure TrieDB (MonadDB)

TrieDB must run on a dedicated NVMe device with no filesystem or RAID.

Identify the NVMe Drive

Verify available NVMe devices:

nvme list
lsblk -o NAME,SIZE,TYPE,MOUNTPOINT,MODEL

Select a drive without mountpoints. Do not use the OS disk.

---

Create Partition

Set the target drive:

TRIEDB_DRIVE=/dev/nvme1n1   # CHANGE THIS

Create GPT and full-size partition:

parted $TRIEDB_DRIVE mklabel gpt
parted $TRIEDB_DRIVE mkpart triedb 0% 100%

---

Create udev Rule

Get the partition UUID:

PARTUUID=$(lsblk -o PARTUUID $TRIEDB_DRIVE | tail -n 1)
echo "Disk PartUUID: ${PARTUUID}"

Create udev rule and symlink /dev/triedb:

echo "ENV{ID_PART_ENTRY_UUID}==\"$PARTUUID\", MODE=\"0666\", SYMLINK+=\"triedb\"" \
 | tee /etc/udev/rules.d/99-triedb.rules

Reload rules and verify:

udevadm trigger
udevadm control --reload
udevadm settle
ls -l /dev/triedb

---

Verify LBA Configuration

Check current LBA format:

nvme id-ns -H $TRIEDB_DRIVE | grep 'LBA Format' | grep 'in use'

Expected output:

Data Size: 512 bytes (in use)

If not set to 512 bytes, reformat:

nvme format --lbaf=0 $TRIEDB_DRIVE

Re-verify:

nvme id-ns -H $TRIEDB_DRIVE | grep 'LBA Format' | grep 'in use'

---

Format TrieDB Partition

Run the one-time TrieDB initialization service:

systemctl start monad-mpt
journalctl -u monad-mpt -n 14 -o cat

This formats the TrieDB partition and prepares it for use.