--- title: "Storage Manager" description: "Manage the storage on your ARX device — expand the System and Data Volumes and their disks, and connect a NAS for your applications" canonical_url: "https://docs.ardge.com/en/guide/connect-your-data/storage-manager" --- # Storage Manager > Manage the storage on your ARX device — expand the System and Data Volumes and their disks, and connect a NAS for your applications ## Overview Storage Manager does two things that matter most: 1. **Manages ARX's own storage** — capacity, disk health, and expanding or replacing disks when you need to. 2. **Connects a NAS or other remote storage to ARX** — so supported apps can read your existing company data directly, or write large output to the NAS. **ARX local storage** holds the system, the models, the apps and local data. **Remote storage / NAS** is the shared data you already have, mounted for ARX apps to use. ARX-100 doesn't support local storage management (**Storage** and **Disks**). Upcoming x86 models with expandable disks will. ![The Storage page in Storage Manager](https://docs.ardge.com/screenshots/guide/storage-manager-storage.webp) ## Storage: check and expand ARX's local capacity The device's storage is divided into two volumes, both created by the system and neither able to be created or deleted: - **System Volume** — RAID 1, holds the system's own data - **Data Volume** — Longhorn, backs the storage of every container, so your applications and models grow into this one. It's usually the one that grows fastest What you do here is watch how full each one is and expand it — **Manage Disks** adds a disk to a volume or takes one out. Each volume shows how full it is, its used, free and total capacity, and a health status: - **Healthy** — normal - **Degraded** — a member disk is down but the data is still readable; schedule a check - **Rebuilding** — the system is rebuilding the data - **Failed** — something serious is wrong and needs attention ## Disks: look at the physical disks Check the health of every disk in the device, which volume it belongs to, and which physical slot it sits in. Use it to spot a disk that needs replacing, and to identify the right slot before you open the device. Disks are grouped into **Unassigned**, **System Volume** and **Data Volume**, and each row shows the slot, manufacturer, model, capacity and status. Disk status:
Status Meaning
Online Working normally
Initializing Just added to a volume, being prepared
Rebuilding Data is being rebuilt onto this disk
Removing Longhorn is migrating this disk's data elsewhere; the row shows progress
Failed The volume has marked the disk as dead
Absent Pulled from its slot, or no longer detected
Not Initialized Not used by any volume
### Adding a disk Add a disk when a volume is running short of space. Fit the new disk into an empty slot, then use **Add Disks** on the volume you want to expand — its capacity grows by what you add. - **Data Volume** — the one that usually fills up, since your applications and models live on it. Any unassigned disk works, with no minimum capacity - **System Volume** — only a disk in a system-disk slot can join it, and it must be at least as large as the existing system disk, because RAID 1 mirrors the same data onto every member A disk you've just added shows **Initializing** while the system prepares it, then **Online** once it's part of the volume. ### Removing or replacing a disk Remove a disk when you're retiring one that still works, or swapping out one that has failed. The data is handled before the disk leaves: the System Volume rebuilds its mirror, and the Data Volume moves the disk's data onto the remaining disks. Disk I/O rises while that runs. - **System Volume** — you can remove a disk when the volume is **Healthy** and holds more than one system disk. While it's **Degraded**, only the **Failed** or **Absent** disk can be removed, so you can swap in a replacement and rebuild - **Data Volume** — the system first checks whether the remaining disks can hold the data. If they can't, the removal doesn't start — expand the volume first, then remove the disk. If they can, the disk goes to **Removing** and Longhorn starts migrating **Wait for the migration before you pull the disk:** A disk in **Removing** still holds data. It's only safe to physically remove once it appears under **Unassigned** with the status **Not Initialized**. **Cancel Remove** stops the migration and returns the disk to service — replicas that already moved stay where they are. ## Mount Points: connect a NAS to ARX Most enterprise data already lives on a NAS, and you don't need to copy all of it onto ARX. Create a mount point and ARX can treat the remote shared folder as usable storage, then hand it to supported apps. **Create a shared folder on the NAS → export it over NFS → create a mount point on ARX → test and mount → pick it in the app** Two protocols are available: **NFS**, and **NFS over RDMA** for higher throughput when both your network interface and your NAS support it. RDMA is an advanced option — only use it when both ends support it. ![The Mount Points page in Storage Manager](https://docs.ardge.com/screenshots/guide/en/storage-manager-mount-points.webp) ![The Add Mount Point dialog](https://docs.ardge.com/screenshots/guide/en/sto-07.webp) Deleting a mount point restarts every application that uses it, and disconnects those applications from the storage. The confirmation dialog lists them by name. Deletion is blocked while a mount point is still mounting. See [Mount remote storage for an application in Storage Manager](https://docs.ardge.com/en/knowledge/arx-os/mount-remote-storage) for the full setup, including the NFS configuration on the NAS side. ## Files: confirm ARX can actually see the remote data Check that a mount point really brought your data in, and find the folder you want to hand to an application. Browse a mount point's directory tree, where each entry shows its name, its size, and when it was created and updated. ![The Files page in Storage Manager](https://docs.ardge.com/screenshots/guide/en/sto-08.webp) ## Application Storage Settings: where each app reads from and writes to Point each installed application at the storage it should use — where it writes what it produces, and where it reads source data from. One row per application, with two settings: - **Application Data Storage** — where the application writes the files it generates. Either **ARX Local Storage** or a mount point with write access - **Files Source Folder** — an existing folder the application reads as a data source A grayed-out value means the application doesn't support that path. Not every application does — it depends on what the application itself declares. ![The Application Storage Settings page in Storage Manager](https://docs.ardge.com/screenshots/guide/en/sto-09.webp) Saving a change restarts the application, so its service drops briefly. Switching **Application Data Storage** from local storage to a remote mount point **permanently deletes** what was in local storage. ## I just want to give my NAS documents to an AI — which steps? 1. Prepare a shared folder on the NAS 2. Create the connection in **Storage Manager > Mount Points** 3. Confirm you can see the data in **Storage Manager > Files** 4. Set the Files Source Folder in **Application Storage Settings** or in the app itself 5. Go back to the app and start the sync, import or indexing ## Sitemap See the full [sitemap](https://docs.ardge.com/sitemap.md) for all pages.