diff --git a/common-tasks/block-devices.md b/common-tasks/block-devices.md index 71c22a68..6340dd08 100644 --- a/common-tasks/block-devices.md +++ b/common-tasks/block-devices.md @@ -52,7 +52,7 @@ To specify this device node name, you need to use the command line tool and its #Command Line Tool Guide The command-line tool you may use to mount whole USB drives or their partitions is `qvm-block`, a shortcut for `qvm-device block`. -`qvm-block` only sees device-nodes and may not use names you expect! So make sure to have the drive available in the sourceVM before listing available block devices (step 1.) to find out it's its ID. +`qvm-block` won't recognise your device by any given name, but rather the device-node the sourceVM assigns. So make sure you have the drive available in the sourceVM, then list the available block devices (step 1.) to find the corresponding device-node. In case of a USB-drive, make sure it's attached to your computer. If you don't see anything that looks like your drive, run `sudo udevadm trigger --action=change` in your USB-qube (typically `sys-usb`) diff --git a/configuration/usb-qube-howto.md b/configuration/usb-qube-howto.md index b7b0fbd1..6d3815cd 100644 --- a/configuration/usb-qube-howto.md +++ b/configuration/usb-qube-howto.md @@ -196,7 +196,7 @@ Removing a USB qube [enable your keyboard for login]: #enable-a-usb-keyboard-for-login [2270-comm23]: https://github.com/QubesOS/qubes-issues/issues/2270#issuecomment-242900312 [PCI Devices]: /doc/pci-devices-in-qubes-R4.0/ -[usb-controller]: