> For the complete documentation index, see [llms.txt](https://docs.verge.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.verge.io/plan-and-deploy/es/guia-de-implementacion/sizing/storage-driver-list.md).

# Controladores de almacenamiento incluidos

Lista de referencia de controladores de almacenamiento incluidos con VergeOS.

VergeOS incluye un amplio conjunto de controladores relacionados con el almacenamiento como parte de su pila de virtualización basada en Linux. Esta página refleja los controladores incluidos en la plataforma para la versión más reciente de VergeOS.

{% hint style="info" %}
**¿Necesita hardware que no se muestra?**

Si no ve una familia de controladoras de almacenamiento que planea usar, contacte con **Ventas de VergeOS** para obtener orientación.\
Pueden ayudarle a evaluar sus requisitos y confirmar si su hardware se ajusta a las prácticas recomendadas de implementación.
{% endhint %}

***

## Controladoras RAID

| Familia                                                                   | Controlador                    |
| ------------------------------------------------------------------------- | ------------------------------ |
| Microchip/Adaptec SmartRAID, SmartHBA, HPE Smart Array Gen10+             | `smartpqi`                     |
| serie Adaptec/Microsemi aacraid                                           | `aacraid`                      |
| HPE Smart Array Gen8/Gen9                                                 | `hpsa`                         |
| Broadcom/LSI MegaRAID SAS — incl. Aero/9560 tri-mode (`1000:10e0`–`10e7`) | `megaraid_sas`                 |
| LSI MegaRAID heredado (mbox/v1)                                           | `megaraid_mbox`, `megaraid`    |
| IBM Power RAID                                                            | `ipr`                          |
| HighPoint RocketRAID (serie IOP)                                          | `hptiop`                       |
| Areca                                                                     | `arcmsr`                       |
| Promise SuperTrak                                                         | `stex`                         |
| 3ware 9xxx / SAS / heredado                                               | `3w-9xxx`, `3w-sas`, `3w-xxxx` |
| ATTO ExpressSAS                                                           | `esas2r`                       |
| Mylex / IBM ServeRAID / Marvell UMI                                       | `myrb`, `myrs`, `ips`, `mvumi` |

***

## Adaptadores de bus host SAS / SATA

| Familia                                              | Controlador                 |
| ---------------------------------------------------- | --------------------------- |
| Broadcom SAS2/SAS3 (9200/9300/9400) y 9500 tri-mode  | `mpt3sas`                   |
| Broadcom tri-mode 24G (9600, SAS40xx/41xx/50xx/51xx) | `mpi3mr`                    |
| PMC/Microsemi PM8001/PM80xx SAS                      | `pm80xx`                    |
| Marvell SAS                                          | `mvsas`                     |
| SAS integrado Intel C600                             | `isci`                      |
| Adaptec SAS                                          | `aic94xx`                   |
| LSI Fusion heredado (SAS/SPI/FC)                     | `mptsas`, `mptspi`, `mptfc` |

***

## Fibre Channel y FCoE

| Familia                                              | Controlador |
| ---------------------------------------------------- | ----------- |
| Emulex LightPulse — hasta LPe35000/LPe36000 (G7/G7P) | `lpfc`      |
| QLogic/Marvell FC — serie 2400/2500/2600/2700/2800   | `qla2xxx`   |
| Chelsio T4/T5/T6 FCoE                                | `csiostor`  |
| Brocade/Cavium                                       | `bfa`       |
| Cisco VIC FC                                         | `fnic`      |
| Marvell FastLinQ FCoE                                | `qedf`      |
| destino Emulex EFCT                                  | `efct`      |

***

## NVMe, SSD PCIe y almacenamiento virtual

| Familia                                                              | Controlador                    |
| -------------------------------------------------------------------- | ------------------------------ |
| Cualquier SSD NVMe                                                   | `nvme` (coincidencia de clase) |
| NVMe detrás de Intel VMD                                             | `vmd`                          |
| SSD PCIe Micron P320/P420                                            | `mtip32xx`                     |
| VMware PVSCSI                                                        | `vmw_pvscsi`                   |
| virtio-scsi (paravirtual, para instalaciones anidadas/virtualizadas) | `virtio_scsi`                  |

***

{% hint style="info" %}
**Variabilidad de la versión**

La disponibilidad de controladores puede variar entre versiones de VergeOS a medida que evoluciona el kernel de Linux.\
Esta lista refleja los controladores incluidos en el momento de la compilación para la versión más reciente.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.verge.io/plan-and-deploy/es/guia-de-implementacion/sizing/storage-driver-list.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.