search

jacobbar / fruity-pikvm

Install Pi-KVM on debian SBCs such as Orange Pi, Banana Pi, Mango Pi, etc
GNU General Public License v3.0
165 stars 28 forks source link

If the device restarts and experiences issues due to mounting path problems, it won't function properly. #3

Open nblky opened 1 year ago

nblky commented 1 year ago

When the device is rebooted, the entry in /etc/fstab that mounts /dev/mmcblk1p2 may change to /dev/mmcblk0p2, causing the device to become inaccessible. To resolve this, you need to either modify the corresponding mount entry with the UUID or forcefully power-cycle the device.

Using UUID in /etc/fstab is a better approach. Here's an example:

  1. Obtain the UUID of the MSD path using the following command:

    sudo blkid /dev/mmcblk1p2

    Output:

    /dev/mmcblk1p2: UUID="1xxx89-78c0-4xx51-b470-7618xxxcd1" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="90xx8e6-02"

  2. After obtaining the UUID for the MSD path, modify the mount entry in /etc/fstab using a text editor (e.g., vim):

    sudo vim /etc/fstab

  3. Update the mount entry with the UUID:

    UUID=1xxx89-78c0-4xx51-b470-7618xxxcd1 /var/lib/kvmd/msd  ext4  nodev,nosuid,noexec,ro,errors=remount-ro,data=journal,X-kvmd.otgmsd-root=/var/lib/kvmd/msd,X-kvmd.otgmsd-user=kvmd  0 0

    This change ensures that the device is mounted using the UUID, which is a more stable identifier and should prevent the issue with changing device names on reboot.