PebbleRack

Guide 02 of 25 · beginner

Inventory and map what you already own

Make a private inventory and connection map so you can plan safely and troubleshoot later.

Source-verified · Not lab-testedOfficial sources checked 2026-09-29. No PebbleRack hardware compatibility claim.

Outcome

You will know which device is the lab host, how it reaches your router, where the disks and power come from, and which pieces you can replace without affecting the rest of the household.

Before you start

Have physical access to the proposed host, router, switch if present, and power connections. Gather vendor manuals for the exact devices. You do not need to scan your network or install any software. Keep the inventory private; serial numbers, addresses, and account names can aid an attacker.

Steps

  1. Draw the physical path. On paper or in a private file, draw internet connection → router → switch or Wi-Fi → proposed lab host. Include power outlet, power strip or UPS, display/keyboard access, and any external storage. Mark every uncertain cable with a question mark until traced.
  2. Inventory the host. Record make/model, CPU architecture, installed memory, storage devices, network ports, firmware access method, and the precise disk you are willing to erase. If any item is unknown, read the vendor documentation or inspect it locally. Published capacity does not prove your current unit has that configuration.
  3. Inventory the network boundary. Identify which device hands out network addresses (DHCP) and which answers local DNS questions. Often both are the router, but verify in its administration interface. Note whether the host uses Ethernet or Wi-Fi and whether a guest network separates it from your normal computers.
  4. Record the current behavior without changing it. On an Ubuntu host, ip address shows interfaces and assigned addresses, ip route shows the default route, and resolvectl status shows DNS configuration. On a host with another operating system, use that system's network settings. Save the results privately, with a date. Do not publish a screenshot of the router administration page.
  5. Identify dependencies. Ask what stops working if the host is unplugged, the switch is off, or the router reboots. A first lab should not become the only DNS or internet gateway for the household. Mark any device used by other people as shared.
  6. Create a simple change log. Use columns for date, device, old setting, new setting, reason, observed result, and rollback. Leave credential fields out. This is the seed of a runbook for later maintenance and incident response.
  7. List the missing facts. Examples are “unknown router DHCP range” or “unknown disk health.” These become work items before any static addressing, disk formatting, or power planning.

Check it worked

Follow your drawing from a client to the router and to the proposed host. Point to the exact disk that may be erased. Identify the person who can restore router access if a network change fails. If you cannot do all three, the inventory is incomplete.

If it fails / rollback

This guide makes no configuration changes. Correct the map when a cable or setting differs from your assumption. If you find a shared dependency, postpone installation until it has a safe alternative or maintenance window.

Safety and data notes

Never run broad scans against networks you do not own or administer. Store serial numbers, internal addresses, and screenshots in private notes. Do not publish them with a question to a forum.

Sources

  • Ubuntu Server, configuring networks — interfaces, routes, and DNS client behavior; checked 2026-09-29.
  • Ubuntu Server, basic installation — disk-selection and backup cautions; checked 2026-09-29.

Next guide

Continue to guide 03, “Choose hardware, power, and airflow.”