mirror of https://github.com/pikvm/pikvm.git
update
This commit is contained in:
parent
036a8afeef
commit
873f4fabea
33
docs/msd.md
33
docs/msd.md
|
|
@ -53,7 +53,7 @@ It is possible to create a shared image storage for an entire fleet of PiKVMs us
|
||||||
If you have some shares, you can easily connect them to PiKVM by creating mount points and adding relevant records to `/etc/fstab`.
|
If you have some shares, you can easily connect them to PiKVM by creating mount points and adding relevant records to `/etc/fstab`.
|
||||||
At the same time, you will be able to upload images via PiKVM Web UI to NFS, and still use local storage.
|
At the same time, you will be able to upload images via PiKVM Web UI to NFS, and still use local storage.
|
||||||
|
|
||||||
!!! example "Step by step: Connecting NFS storage"
|
??? example "Step by step: Connecting NFS storage"
|
||||||
|
|
||||||
1. Make some preparations:
|
1. Make some preparations:
|
||||||
|
|
||||||
|
|
@ -95,6 +95,7 @@ and then connect the second to exchange files.
|
||||||
!!! note
|
!!! note
|
||||||
The first virtual drive is available for management both in the web interface (in the `Drive` menu)
|
The first virtual drive is available for management both in the web interface (in the `Drive` menu)
|
||||||
and using [the console utility](#second-read-write-flash-drive).
|
and using [the console utility](#second-read-write-flash-drive).
|
||||||
|
|
||||||
Additional drives are controlled only from console.
|
Additional drives are controlled only from console.
|
||||||
|
|
||||||
|
|
||||||
|
|
@ -110,7 +111,7 @@ Also additional drives consumes extra endpoints, read more under the spoiler:
|
||||||
|
|
||||||
So, to add a second virtual drive, follow this:
|
So, to add a second virtual drive, follow this:
|
||||||
|
|
||||||
!!! example "Step by step: Enabling the additional drive"
|
??? example "Step by step: Enabling the additional drive"
|
||||||
|
|
||||||
1. Switch the filesystem to read-write mode:
|
1. Switch the filesystem to read-write mode:
|
||||||
|
|
||||||
|
|
@ -147,7 +148,7 @@ So, to add a second virtual drive, follow this:
|
||||||
The `kvmd-otgmsd` console utility is used to manage additional (and the first main one) drives.
|
The `kvmd-otgmsd` console utility is used to manage additional (and the first main one) drives.
|
||||||
The full list of options can be found by running `kvmd-otgmsd --help`.
|
The full list of options can be found by running `kvmd-otgmsd --help`.
|
||||||
|
|
||||||
Below is an example of using it to create an additional flash drive that is writable:
|
??? example "Step by step: Creating the flash drive image to get some files from the target host"
|
||||||
|
|
||||||
1. Switch the filesystem to read-write mode:
|
1. Switch the filesystem to read-write mode:
|
||||||
|
|
||||||
|
|
@ -202,28 +203,44 @@ Below is an example of using it to create an additional flash drive that is writ
|
||||||
```
|
```
|
||||||
|
|
||||||
!!! tip
|
!!! tip
|
||||||
|
|
||||||
The main drive can also be switched to read-write mode, this can be done from the web interface.
|
The main drive can also be switched to read-write mode, this can be done from the web interface.
|
||||||
|
|
||||||
The image will have to be prepared outside of PiKVM, and upload it to use,
|
In this case, the image will have to be prepared outside of PiKVM, and upload it to use,
|
||||||
then download it back to your local host for files extraction.
|
then download it back to your local host for files extraction.
|
||||||
|
|
||||||
|
|
||||||
-----
|
-----
|
||||||
## Disable MSD
|
## Disabling Mass Storage
|
||||||
|
|
||||||
In rare cases, it may be necessary to disable Mass Storage emulation if the BIOS/UEFI
|
In rare cases, it may be necessary to disable Mass Storage emulation if the BIOS/UEFI
|
||||||
does not recognize it correctly and even refuses to work with USB keyboard and mouse.
|
does not recognize it correctly and even refuses to work with USB keyboard and mouse.
|
||||||
|
|
||||||
To permanently disable Mass Storage Drive, add the following section to `/etc/kvmd/override.yaml`:
|
??? example "Step by step: Permanent disabling Sass Storage"
|
||||||
|
|
||||||
|
1. Switch the filesystem to read-write mode:
|
||||||
|
|
||||||
|
```
|
||||||
|
[root@pikvm ~]# rw
|
||||||
|
```
|
||||||
|
|
||||||
|
2. Edit `/etc/kvmd/override.yaml` and add the extra drive config section:
|
||||||
|
|
||||||
```yaml
|
```yaml
|
||||||
kvmd:
|
kvmd:
|
||||||
msd:
|
msd:
|
||||||
type: disabled
|
type: disabled
|
||||||
|
|
||||||
```
|
```
|
||||||
|
|
||||||
After that, perform `reboot` command.
|
3. Perform reboot:
|
||||||
|
|
||||||
|
```
|
||||||
|
[root@pikvm ~]# reboot
|
||||||
|
```
|
||||||
|
|
||||||
|
!!! tip
|
||||||
|
An alternative method may be to use the [dynamic USB configuration](usb_dynamic.md) method,
|
||||||
|
which allows you to temporarily disable any of the emulated devices, including Mass Storage Drive.
|
||||||
|
|
||||||
|
|
||||||
-----
|
-----
|
||||||
|
|
|
||||||
Loading…
Reference in New Issue