{
    "mode": "man",
    "parameter": "udisksctl",
    "section": "1",
    "url": "https://www.chedong.com/phpMan.php/man/udisksctl/1/json",
    "generated": "2026-06-14T13:01:36Z",
    "synopsis": "udisksctl status\nudisksctl info {--object-path OBJECT | --block-device DEVICE | --drive DRIVE}\nudisksctl mount {--object-path OBJECT | --block-device DEVICE} [--filesystem-type TYPE]\n[--options OPTIONS...] [--no-user-interaction]\nudisksctl unmount {--object-path OBJECT | --block-device DEVICE} [--force]\n[--no-user-interaction]\nudisksctl unlock {--object-path OBJECT | --block-device DEVICE} [--no-user-interaction]\n[--key-file PATH] [--read-only]\nudisksctl lock {--object-path OBJECT | --block-device DEVICE} [--no-user-interaction]\nudisksctl loop-setup --file PATH [--read-only] [--offset OFFSET] [--size SIZE]\n[--no-user-interaction]\nudisksctl loop-delete {--object-path OBJECT | --block-device DEVICE} [--no-user-interaction]\nudisksctl power-off {--object-path OBJECT | --block-device DEVICE} [--no-user-interaction]\nudisksctl smart-simulate --file PATH {--object-path OBJECT | --block-device DEVICE}\n[--no-user-interaction]\nudisksctl monitor\nudisksctl dump\nudisksctl help",
    "sections": {
        "NAME": {
            "content": "udisksctl - The udisks command line tool\n",
            "subsections": []
        },
        "SYNOPSIS": {
            "content": "udisksctl status\n\nudisksctl info {--object-path OBJECT | --block-device DEVICE | --drive DRIVE}\n\nudisksctl mount {--object-path OBJECT | --block-device DEVICE} [--filesystem-type TYPE]\n[--options OPTIONS...] [--no-user-interaction]\n\nudisksctl unmount {--object-path OBJECT | --block-device DEVICE} [--force]\n[--no-user-interaction]\n\nudisksctl unlock {--object-path OBJECT | --block-device DEVICE} [--no-user-interaction]\n[--key-file PATH] [--read-only]\n\nudisksctl lock {--object-path OBJECT | --block-device DEVICE} [--no-user-interaction]\n\nudisksctl loop-setup --file PATH [--read-only] [--offset OFFSET] [--size SIZE]\n[--no-user-interaction]\n\nudisksctl loop-delete {--object-path OBJECT | --block-device DEVICE} [--no-user-interaction]\n\nudisksctl power-off {--object-path OBJECT | --block-device DEVICE} [--no-user-interaction]\n\nudisksctl smart-simulate --file PATH {--object-path OBJECT | --block-device DEVICE}\n[--no-user-interaction]\n\nudisksctl monitor\n\nudisksctl dump\n\nudisksctl help\n",
            "subsections": []
        },
        "DESCRIPTION": {
            "content": "udisksctl is a command-line program used to interact with the udisksd(8) daemon process.\n",
            "subsections": []
        },
        "COMMANDS": {
            "content": "",
            "subsections": [
                {
                    "name": "status",
                    "content": "Shows high-level information about disk drives and block devices.\n"
                },
                {
                    "name": "info",
                    "content": "Shows detailed information about OBJECT, DEVICE or DRIVE.\n"
                },
                {
                    "name": "mount",
                    "content": "Mounts a device. The device will be mounted in a subdirectory in the /run/media hierarchy\n- upon successful completion, the mount point will be printed to standard output.\n\n-t, --filesystem-type\nFilesystem type to use. If not specified, autodetected filesystem type will be used.\n\n-o, --options\nThe device will be mounted with a safe set of default options. You can influence the\noptions passed to the mount(8) command using this option. Note that only safe options\nare allowed - requests with inherently unsafe options such as suid or dev that would\nallow the caller to gain additional privileges, are rejected.\n"
                },
                {
                    "name": "unmount",
                    "content": "Unmounts a device. This only works if the device is mounted. The option --force can be\nused to request that the device is unmounted even if active references exists.\n\n-f, --force\nLazy unmount. Detach the filesystem from the file hierarchy now, and clean up all\nreferences to this filesystem as soon as it is not busy anymore.\n"
                },
                {
                    "name": "unlock",
                    "content": "Unlocks an encrypted device. The passphrase will be requested from the controlling\nterminal and upon successful completion, the cleartext device will be printed to standard\noutput.\n\n--key-file=PATH\nRead passphrase from the given file.\n"
                },
                {
                    "name": "lock",
                    "content": "Locks a device. This only works if the device is a cleartext device backed by a\ncryptotext device.\n"
                },
                {
                    "name": "loop-setup",
                    "content": "Sets up a loop device backed by FILE.\n\n-f, --file=FILE\nFile to set up a loop device for.\n\n-r, --read-only\nSet up a read-only loop device.\n\n-o, --offset=OFFSET\nThe data start is moved OFFSET bytes into the specified file.\n\n-s, --size=SIZE\nThe data end is set to no more than SIZE bytes after the data start.\n"
                },
                {
                    "name": "loop-delete",
                    "content": "Tears down a loop device.\n"
                },
                {
                    "name": "power-off",
                    "content": "Arranges for the drive to be safely removed and powered off. On the OS side this includes\nensuring that no process is using the drive, then requesting that in-flight buffers and\ncaches are committed to stable storage. The exact steps for powering off the drive\ndepends on the drive itself and the interconnect used. For drives connected through USB,\nthe effect is that the USB device will be deconfigured followed by disabling the upstream\nhub port it is connected to.\n\nNote that as some physical devices contain multiple drives (for example 4-in-1 flash card\nreader USB devices) powering off one drive may affect other drives. As such there are not\na lot of guarantees associated with performing this action. Usually the effect is that\nthe drive disappears as if it was unplugged.\n"
                },
                {
                    "name": "smart-simulate",
                    "content": "Sets SMART data from the libatasmart blob given by FILE - see\n/usr/share/doc/libatasmart-devel-VERSION/ for blobs shipped with libatasmart. This is a\ndebugging feature used to check that applications act correctly when a disk is failing.\n\n-f, --file=FILE\nFile with the libatasmart blob.\n"
                },
                {
                    "name": "monitor",
                    "content": "Monitors the daemon for events.\n"
                },
                {
                    "name": "dump",
                    "content": "Prints the current state of the daemon.\n"
                },
                {
                    "name": "help",
                    "content": "Prints help and exit.\n"
                }
            ]
        },
        "DEVICE SPECIFICATION": {
            "content": "For commands that require a device as an argument following options can be used to specify\nit.\n",
            "subsections": [
                {
                    "name": "-b --block-device=",
                    "content": "Specify a device by its device file path. For example /dev/sda.\n",
                    "flag": "-b"
                },
                {
                    "name": "-p --object-path=",
                    "content": "Specify a device by the UDisks internal object path without the /org/freedesktop/UDisks2\nprefix. For example blockdevices/sda for the /dev/sda disk.\n",
                    "flag": "-p"
                },
                {
                    "name": "-d --drive=",
                    "content": "Specify a drive by name, for example VirtIODisk. This can be currently used only\ntogether with the info command.\n",
                    "flag": "-d"
                }
            ]
        },
        "COMMON OPTIONS": {
            "content": "The option --no-user-interaction can be used to request that no interaction (such as the user\nbeing presented with an authentication dialog) must occur when checking with polkit(8)\nwhether the caller is authorized to perform the requested action.\n",
            "subsections": []
        },
        "AUDIENCE": {
            "content": "This program does not assume that the caller is the super user - it is intended to be used by\nunprivileged users and authorizations are checked by the udisks daemon using polkit(8).\nAdditionally, this program is not intended to be used by scripts or other programs -\noptions/commands may change in incompatible ways in the future even in maintenance releases.\nSee the “API STABILITY” section of udisks(8) for more information.\n",
            "subsections": []
        },
        "BASH COMPLETION": {
            "content": "udisksctl ships with a bash completion script to complete commands, objects, block devices\nand some options.\n",
            "subsections": []
        },
        "AUTHOR": {
            "content": "This man page was originally written for UDisks2 by David Zeuthen <zeuthen@gmail.com> with a\nlot of help from many others.\n",
            "subsections": []
        },
        "BUGS": {
            "content": "Please send bug reports to either the distribution bug tracker or the upstream bug tracker at\nhttps://github.com/storaged-project/udisks/issues.\n",
            "subsections": []
        },
        "SEE ALSO": {
            "content": "udisks(8), udisksd(8), umount.udisks2(8), polkit(8)\n\n\n\nudisks 2.9.4                                 August 2018                                UDISKSCTL(1)",
            "subsections": []
        }
    },
    "summary": "udisksctl - The udisks command line tool",
    "flags": [],
    "examples": [],
    "see_also": [
        {
            "name": "udisks",
            "section": "8",
            "url": "https://www.chedong.com/phpMan.php/man/udisks/8/json"
        },
        {
            "name": "udisksd",
            "section": "8",
            "url": "https://www.chedong.com/phpMan.php/man/udisksd/8/json"
        },
        {
            "name": "umount.udisks2",
            "section": "8",
            "url": "https://www.chedong.com/phpMan.php/man/umount.udisks2/8/json"
        },
        {
            "name": "polkit",
            "section": "8",
            "url": "https://www.chedong.com/phpMan.php/man/polkit/8/json"
        }
    ],
    "tldr": {
        "source": "official",
        "description": "Interact with `udisksd` to query and manipulate storage devices.",
        "examples": [
            {
                "description": "Show high-level information about disk drives and block devices",
                "command": "udisksctl status"
            },
            {
                "description": "Show detailed information about a device",
                "command": "udisksctl info {{-b|--block-device}} {{/dev/sdX}}"
            },
            {
                "description": "Show detailed information about a device partition",
                "command": "udisksctl info {{-b|--block-device}} {{/dev/sdXN}}"
            },
            {
                "description": "Mount a device partition and prints the mount point",
                "command": "udisksctl mount {{-b|--block-device}} {{/dev/sdXN}}"
            },
            {
                "description": "Unmount a device partition",
                "command": "udisksctl unmount {{-b|--block-device}} {{/dev/sdXN}}"
            },
            {
                "description": "Power off a device to safely remove it",
                "command": "udisksctl power-off {{-b|--block-device}} {{/dev/sdX}}"
            },
            {
                "description": "Monitor the daemon for events",
                "command": "udisksctl monitor"
            }
        ]
    }
}