is a command-line program used to interact with the
Shows high-level information about disk drives and block devices.
Shows detailed information about
Mounts a device. The device will be mounted in a subdirectory in the
hierarchy - upon successful completion, the mount point will be printed to standard output.
Filesystem type to use. If not specified, autodetected filesystem type will be used.
The device will be mounted with a safe set of default options. You can influence the options passed to the
command using this option. Note that only safe options are allowed - requests with inherently unsafe options such as
that would allow the caller to gain additional privileges, are rejected.
Unmounts a device. This only works if the device is mounted. The option
can be used to request that the device is unmounted even if active references exists.
Lazy unmount. Detach the filesystem from the file hierarchy now, and clean up all references to this filesystem as soon as it is not busy anymore.
Unlocks an encrypted device. The passphrase will be requested from the controlling terminal and upon successful completion, the cleartext device will be printed to standard output.
Read passphrase from the given file.
Locks a device. This only works if the device is a cleartext device backed by a cryptotext device.
Sets up a loop device backed by
File to set up a loop device for.
Set up a read-only loop device.
The data start is moved
bytes into the specified file.
The data end is set to no more than
bytes after the data start.
Tears down a loop device.
Arranges for the drive to be safely removed and powered off. On the OS side this includes ensuring that no process is using the drive, then requesting that in-flight buffers and caches are committed to stable storage. The exact steps for powering off the drive depends on the drive itself and the interconnect used. For drives connected through USB, the effect is that the USB device will be deconfigured followed by disabling the upstream hub port it is connected to.
Note that as some physical devices contain multiple drives (for example 4-in-1 flash card reader USB devices) powering off one drive may affect other drives. As such there are not a lot of guarantees associated with performing this action. Usually the effect is that the drive disappears as if it was unplugged.
Sets SMART data from the libatasmart blob given by
for blobs shipped with libatasmart. This is a debugging feature used to check that applications act correctly when a disk is failing.
File with the libatasmart blob.
Monitors the daemon for events.
Prints the current state of the daemon.
Prints help and exit.
For commands that require a device as an argument following options can be used to specify it.
Specify a device by its device file path. For example
Specify a device by the UDisks internal object path without the /org/freedesktop/UDisks2 prefix. For example
Specify a drive by name, for example
VirtIO_Disk. This can be currently used only together with the
can be used to request that no interaction (such as the user being presented with an authentication dialog) must occur when checking with
whether the caller is authorized to perform the requested action.
This program does not assume that the caller is the super user - it is intended to be used by unprivileged users and authorizations are checked by the udisks daemon using
polkit(8). Additionally, this program is not intended to be used by scripts or other programs - options/commands may change in incompatible ways in the future even in maintenance releases. See the
for more information.
ships with a bash completion script to complete commands, objects, block devices and some options.
This man page was originally written for UDisks2 by David Zeuthen
with a lot of help from many others.
Please send bug reports to either the distribution bug tracker or the upstream bug tracker at