# disk > RouterOS directory reference for /disk. ----------- ## disk **Conditions:** !smips **Type:** Directory The device is disabled and is not used. acquired The slot is empty, with no disk present. After `eject`, the slot stays empty until the disk is rescanned with `scan` or replugged. The device is a block device, that is, it can be used as storage: formatted or used in a RAID array. Devices without this flag only describe the disk layout. The device is mounted and its files appear in `/file`. The device is currently being formatted. Swap is enabled on the device (`swap=yes`); the device is used as swap space, for example by containers. A member of the RAID array is in failed state. The device is a member of a RAID array. The device is encrypted, for example with `type=crypted` (dm-crypt). The device has a GUID partition table (GPT). The device is a partition of a disk. The device is exported as an NVMe-over-TCP target. The device is exported as an iSCSI target. The device is shared through the built-in SMB server. The device is shared with the NFS server. The device is shared through the DLNA media server. self-encrypted-and-locked TCG-Opal self-encryption is active on the drive. The drive supports TCG-Opal self-encryption, but it is not enabled. Type of the item: - `hardware` - a physical disk attached to the router, for example in a USB, SATA or NVMe slot. - `partition` - a partition on a hardware disk (see `parent`). - `file` - a file mounted as a block device (loop), for example a swap file or a mounted `.iso` / `.squashfs` image. - `tmpfs` - a folder in RAM, see [Tmpfs](../../storage/tmpfs). - `ramdisk` - part of RAM used as a block device, see [Ramdisk](../../storage/ramdisk) (storage package). - `raid` - a RAID array built from several disks, see [RAID](../../storage/raid/) (storage package). - `crypted` - a dm-crypt encrypted block device, see [Encrypted storage](../../storage/encrypted-storage) (storage package). - `nvme-tcp` - a disk mounted over NVMe over TCP, see [NVMe over TCP](../../storage/nvme-over-tcp) (storage package). - `iscsi` - an iSCSI target mounted as a disk, see [iSCSI](../../storage/iscsi) (storage package). - `nfs` - an NFS share mounted as a disk, see [NFS](../../storage/nfs) (storage package). - `smb` - an SMB share mounted as a disk, see [SMB](../../storage/smb) (storage package). - `sshfs` - a remote folder mounted over SSH. Name of the disk item, normally based on where the device is physically connected, for example `nvme1` or `usb1`. The name is assigned automatically and can be set manually. Other commands and `parent` refer to the disk by this name. Parent device of the item. On a `type=partition` item it selects the hardware disk the partition is created on, for example `add type=partition parent=nvme9 ...`; on `type=crypted` it is the drive or partition that is encrypted. Template of the mount point, the folder under which the file system appears in `/file`. The following variables are replaced: - `[slot]` (default) - the slot name. - `[model]` - the device model. - `[serial]` - the device serial number. - `[fw-version]` - the device firmware version. - `[fs-label]` - the file system label. - `[fs-uuid]` - the file system UUID. - `[fs]` - the file system type. Variables can be combined, for example `[model]-[fs]`. An empty template is rejected, and `unset mount-point-template` restores the default `[slot]`. The default for newly added disks is set by `default-mount-point-template` in [`settings`](settings). See [Disks](../../hardware/disks/). Whether the device's file system is mounted, so its files are available in `/file`. `mount-filesystem=no` unmounts the file system, which is required before `/disk check` or `/disk repair`. Default: yes. Whether the mounted file system is read-only. Default: no. Whether the device's file system is mounted with compression. Only supported on `btrfs` file systems; RouterOS reports `compression only available for btrfs` when it is set on other file systems. Default: no. Number of the partition on the parent disk, for example `partition-number=1` for the first partition. Start offset of the partition on the disk, in bytes. Use it to adjust where the partition begins. Size of the partition in bytes. When it is not set, the partition takes the remaining space on the disk. See [Disks](../../hardware/disks/). RAID level of the array: - `0` - striping: data is spread evenly over all disks, no fault tolerance, best performance. - `1` - mirroring: the same data is written to all disks, best fault tolerance. - `4` - block-level striping with parity stored on a dedicated disk. - `5` - block-level striping with distributed parity, survives one disk failure. - `6` - block-level striping with double parity, survives two disk failures. - `linear` - the disks are joined into one large disk without redundancy. See [RAID](../../storage/raid/). Number of devices (disks) in the RAID array, set when the array is created. Maximum size of an individual device in the RAID array. Size of the chunks (stripes) written across the disks of the array, for example `1M`. RAID block device a disk belongs to. Set it together with `raid-role` on the member disks to add them to an array created with `add type=raid ...`. On the RAID item itself it is `none`. Position of the disk within the RAID array, set with `raid-master`, starting from 0, or `spare` to mark the disk as a hot spare. Marks a drive as failed in the RAID array. Used when a non-failed drive needs to be replaced. Whether the device is exported as an NVMe-over-TCP target, so other devices can mount it. Default: no. See [NVMe over TCP](../../storage/nvme-over-tcp). Port on which the NVMe-over-TCP server accepts connections from initiators. See [NVMe over TCP](../../storage/nvme-over-tcp). NVMe Qualified Name (NQN) of the exported device, used by initiators to connect. See [NVMe over TCP](../../storage/nvme-over-tcp). Hostnames allowed to connect to the NVMe-over-TCP server, for host-based access control. See [NVMe over TCP](../../storage/nvme-over-tcp). Password the NVMe-over-TCP server requires from initiators. See [NVMe over TCP](../../storage/nvme-over-tcp). IP address of the NVMe-over-TCP target (host) to mount, on the `nvme-tcp` client. See [NVMe over TCP](../../storage/nvme-over-tcp). NVMe Qualified Name (NQN) of the target on the server to mount, on the `nvme-tcp` client. See [NVMe over TCP](../../storage/nvme-over-tcp). Hostname the `nvme-tcp` initiator (client) identifies itself with; used for identification and authentication on the server. See [NVMe over TCP](../../storage/nvme-over-tcp). Password used to authenticate the NVMe-over-TCP connection to the server. See [NVMe over TCP](../../storage/nvme-over-tcp). Port the NVMe-over-TCP target listens on for connections from initiators. Default: 4420. See [NVMe over TCP](../../storage/nvme-over-tcp). Whether the device is exported as an iSCSI target. Default: no. See [iSCSI](../../storage/iscsi). Port the iSCSI server listens on. See [iSCSI](../../storage/iscsi). iSCSI Qualified Name (IQN) of the iSCSI server, by default `iqn.2000-02.com.mikrotik:`. See [iSCSI](../../storage/iscsi). Port the iSCSI target listens on for connections from initiators. Default: 3260. See [iSCSI](../../storage/iscsi). IP address of the iSCSI target (host) to mount, on the `iscsi` client. See [iSCSI](../../storage/iscsi). iSCSI Qualified Name (IQN) of the target to mount, on the `iscsi` client. See [iSCSI](../../storage/iscsi). Whether the device is shared with NFS, so network clients can mount it. Default: no. See [NFS](../../storage/nfs). IP address of the NFS server to mount, on the `nfs` client. See [NFS](../../storage/nfs). Folder to mount on the NFS server, on the `nfs` client. See [NFS](../../storage/nfs). Whether the device is shared through the built-in SMB server (`/ip/smb`) when it is mounted. With `auto-smb-sharing=yes` in [`settings`](settings) it is enabled automatically. Default: no. SMB user of the auto-created share of this disk; the default for new disks is taken from `auto-smb-user` in [`settings`](settings). Password of the SMB user of the auto-created share. Whether connections to the SMB share of this disk must be encrypted. IP address of the SMB server to mount, on the `smb` client. See [SMB](../../storage/smb). Name of the share to mount on the server, on the `smb` client. See [SMB](../../storage/smb). SMB user to authenticate with, on the `smb` client. See [SMB](../../storage/smb). Password of the SMB user, on the `smb` client. Whether the connection to the remote SMB share is encrypted, on the `smb` client. Whether the device is shared through the DLNA media server (`/ip/media`) when it is mounted. With `auto-media-sharing=yes` in [`settings`](settings) it is enabled automatically. Default: no. Interface the DLNA media server uses for the share of this disk, set together with `media-sharing=yes`. Maximum size of a `tmpfs` folder, in decimal units (`100M` is 100 000 000 bytes). The folder uses RAM only for the files stored in it. When the size is not set (it reads `0`), the folder can grow to about half of the RAM. RouterOS adds up the maximum sizes of all tmpfs folders, counting a folder without `tmpfs-max-size` as half of the RAM, and refuses a new size when the total is more than the router can provide (`too much memory requested for tmpfs/ramdisk`). The size in `print` is rounded up to whole 4 KiB memory pages. A new value applies at once, also to a mounted folder. The contents of a `tmpfs` are lost on reboot or power loss. See [Tmpfs](../../storage/tmpfs). Default: not set. Size of the RAM block device created with `type=ramdisk`, rounded up to a multiple of 16 KiB. The RAM is not reserved when the ramdisk is added. A reboot or power loss clears it: the ramdisk stays, but empty and without a file system, so format it again. Needs the `rose-storage` package. See [Ramdisk](../../storage/ramdisk). The drive or partition to encrypt with `type=crypted`. See [Encrypted storage](../../storage/encrypted-storage). The key used to decrypt the `crypted` device. See [Encrypted storage](../../storage/encrypted-storage). Password that enables TCG-Opal self-encryption on a supported (SED) drive; unsetting it disables self-encryption. See [Self-encrypting drives](../../storage/self-encrypting-drives). Address (IP address or hostname) of the SSH server to mount, for `type=sshfs`. See [SSHFS](../../storage/sshfs). Port of the SSH server to connect to, for `type=sshfs` (default: 22). See [SSHFS](../../storage/sshfs). User to log in to the remote SSH server with, for `type=sshfs`. See [SSHFS](../../storage/sshfs). Password of the remote SSH user, for `type=sshfs`. See [SSHFS](../../storage/sshfs). Path on the remote SSH server to mount, for `type=sshfs`. See [SSHFS](../../storage/sshfs). Use the device as swap space. Swap is used only by containers, and its usable size is limited to 10 times the device's RAM. It applies to a whole disk or partition, or to a file with `type=file`. See [Disks](../../hardware/disks/). Path and name of the file mounted as a block device with `type=file`, for example a swap file (`swap=yes`) or a mounted `.iso` / `.squashfs` image. Removing the disk item does not delete the file. See [Disks](../../hardware/disks/). Size of the file, for example `file-size=1G`, when creating a `type=file` device. Offset in the file at which the block device starts, for example `file-offset=0`. Default slot name of the device, shown when no custom `slot` name is set. Label of the file system. Formatting sets it automatically to `-fs`, unless a `label` is given to `/disk format`. UUID of the file system, for example `58470fe2-...`. File system of the device: `ext4`, `btrfs`, `xfs`, `fat32`, `exfat` and `ntfs` for local file systems, `tmpfs` for RAM folders, `nfs`, `smb` and `sshfs` for network mounts, and `iso` / `squashfs` for mounted images. `-` means the device has no recognised file system. The values `wipe`, `wipe-quick`, `discard` and `discard-secure` correspond to the file systems of `/disk format`. Model name of the device, for example `TS1TUTE210T`. Serial number of the device. Firmware version of the device. Total size of the device in bytes. Free space on the mounted file system in bytes. Total number of inodes of the file system. Number of free inodes of the file system. Used space of the file system in percent, for example `4%`. Mount point of the file system, the folder under which it appears in `/file`, driven by `mount-point-template`. Sector size of the device, for example 512 bytes. Interface the device is connected to, for example `PCIe 2x8 GT/s` or `USB 2.00 480Mbps`. Speed of the interface the device is connected to, for example `15.7Gbps`. State of the disk as a member of its RAID array, for example `0:in_sync`; when the disk is not part of an assembled array, the details of the RAID superblock found on it are shown instead. State of a RAID array, for example `clean`. Model and serial number of the disk that last occupied this slot, shown after the disk was ejected or removed, for example `TS1TUTE210T J398770033`. UUID of the RAID array. Secret the NVMe-over-TCP server uses to authenticate connections from initiators. Secret used to authenticate the connection to the NVMe-over-TCP server. Local RouterOS user the SSHFS mount runs under, for example `admin`. Read-only. Total number of I/O operations on the device, as shown by [`monitor-traffic`](monitor-traffic). Total number of I/O errors on the device. Total number of read operations. Number of read operations per second. Total number of bytes read. Rate of reads, for example in bytes per second. Number of adjacent read operations merged. Time spent on read operations. Total number of write operations. Number of write operations per second. Total number of bytes written. Rate of writes, for example in bytes per second. Number of adjacent write operations merged. Time spent on write operations. Number of I/O operations currently in flight. Time the device was busy handling requests. Time requests spent waiting in the queue. Total number of discard (trim) operations. Total number of bytes discarded. Number of adjacent discard operations merged. Time spent on discard operations. Total number of flush operations. Time spent on flush operations. Temperature of the drive in Celsius, reported by S.M.A.R.T. (storage package). See the [S.M.A.R.T. info](../../hardware/disks/smart) guide and [`smart-info`](smart-info). Temperatures of the drive's sensors in Celsius, one entry per sensor slot. Bitmask of critical warnings the drive reports: `spare-space` (available spare is below `available-spare-threshold`), `temperature` (temperature out of range), `reliability-degraded`, `read-only` (the device entered read-only mode) and `volatile-backup-failed`. Remaining spare blocks of the drive in percent, for example 100%. Below `available-spare-threshold` the drive reports a warning. Threshold in percent below which the available spare space of the drive is reported as a warning. Estimated percentage of the drive's life used, based on how many spare blocks have been consumed. Total number of bytes read by the host from the drive. Total number of bytes written by the host to the drive. Total number of read commands the host sent to the drive. Total number of write commands the host sent to the drive. Total time the drive controller was busy with commands. Number of power cycles of the drive. Total time the drive was powered on. Number of unsafe (unexpected) shutdowns of the drive. Number of unrecovered media and data integrity errors of the drive. Temperature in Celsius at which the drive starts reporting a warning. Time the drive spent above `warning-temperature`. Temperature in Celsius at which the drive reports a critical condition. Time the drive spent above `critical-temperature`.