> ## Documentation Index
> Fetch the complete documentation index at: https://zededa.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> Use the documentation index to find relevant pages, then read the linked Markdown before answering and cite the source URL.
> Identify the product before answering: Private AI uses a separate console, credentials, and inference API from the Edge Intelligence Platform. Do not apply instructions from one product to the other.
> Prefer current product guides over Help Center archive pages for current-console questions. Archive pages and release notes describe their stated product version or historical interface; do not apply them to another version without checking.
> Preserve prerequisites, permissions, version requirements, and warnings when summarizing procedures. Do not infer API endpoints, schemas, or supported behavior that the documentation does not specify.

# Collect Logs from an Offline Node

> Use a USB drive to collect EVE-OS logs and diagnostic data from a node that is offline or unreachable remotely.

## Introduction

When a node is offline or otherwise unreachable through Edge Infrastructure Services or EdgeView, you can collect EVE-OS (Edge Virtualization Engine) logs and diagnostic data by inserting a USB drive into the node. EVE-OS detects the USB drive and writes log files to it automatically if the drive is formatted and labeled correctly.

This method is useful when remote access is not available, for example, when the node has no network connectivity, when the EdgeView tunnel cannot be established, or when the node is in a state that prevents it from reaching Edge Infrastructure Services.

### Prerequisites

* Physical access to the node.
* A USB drive formatted as FAT32 or ext4 with at least 1 GB of free space.
* The USB drive must be labeled `LOGS` (case-sensitive) for EVE-OS to recognize it as a log collection target.

## Prepare the USB Drive

Format the USB drive and set its volume label to `LOGS`.

On Linux:

```text theme={"dark"}
mkfs.vfat -n LOGS /dev/sdX
```

Replace `/dev/sdX` with the correct device identifier for your USB drive. Use `lsblk` to identify it.

On macOS:

```text theme={"dark"}
diskutil eraseDisk FAT32 LOGS /dev/diskN
```

Replace `/dev/diskN` with the correct disk identifier. Use `diskutil list` to identify it.

On Windows, use Disk Management or the `format` command with `/V:LOGS` to set the volume label.

## Collect Logs

1. Power on the node, or confirm it is running. Log collection requires EVE-OS to be active.
2. Insert the prepared USB drive into any available USB port on the node.
3. Wait for EVE-OS to detect the drive. This typically takes up to one minute.
4. EVE-OS writes the following to the USB drive:
   * Current EVE-OS system logs.
   * Recent application instance logs (if log forwarding is enabled).
   * Node configuration state.
   * Network and hardware diagnostic snapshots.
5. When the write process completes, EVE-OS unmounts the drive. The activity indicator on the drive (if present) stops blinking.
6. Remove the USB drive safely.

Do not remove the drive while the activity indicator is blinking. Removing the drive mid-write may result in incomplete or corrupt log files.

## Read the Collected Logs

Insert the USB drive into a workstation and open it to view the files. The log directory structure on the drive typically contains:

* `eve.log` or `current.log`: the main EVE-OS system log.
* `apps/`: per-application instance log files (if available).
* `config/`: a snapshot of the current EVE-OS configuration.

Use a text editor or log viewer to open and search the log files.

## When to Use This Method

Use USB log collection when:

* The node has no network connectivity and EdgeView diagnostics are not available.
* The node is in an early boot state where network services have not started.
* You need a full log snapshot for offline analysis or support escalation.

For nodes with working network connectivity, the EdgeView diagnostics panel is faster and does not require physical access. See [Download a Diagnostic Bundle](https://zededa.mintlify.site/new-ui/infrastructure-services/troubleshooting/collect-diagnostic-data.md) for the remote method.

## Next Steps

> [card] [Download a Diagnostic Bundle](https://zededa.mintlify.site/new-ui/infrastructure-services/troubleshooting/collect-diagnostic-data.md)
>
> Remote diagnostics via EdgeView.

> [card] [Monitoring, Logs, Events, Reports, and Jobs](https://zededa.mintlify.site/new-ui/infrastructure-services/monitoring-logs-events-reports-jobs.md)
>
> View logs forwarded to Edge Infrastructure Services.

> [card] [Enable and Disable SSH Access for Nodes](https://zededa.mintlify.site/new-ui/infrastructure-services/troubleshooting/enable-disable-ssh.md)
>
> An alternative remote access method.