OK, I haven’t personally used VMware player but I assume it works similarly to VMware Workstation. In practice you plug your drive in, ensure within the VMware virtual machine settings there’s a “USB Controller” listed under devices (and add it if not).
You can then “assign” the drive by clicking menu > Removable devices > Connect (Disconnect from host) on the relevant entry for the drive.
Once booted and after logging in, cancel the script with
Ctrl + C and you can then locate the drive with
sudo fdisk -l and take note of the path eg:
Following that, gain the UUID with
sudo blkid /dev/sdc and add the drive to your
/etc/fstab file to have it automatically mount to the same mountpoint on every boot (in order to provide NC with a permanent data location for the config file). An example would be:
UUID=02C22F1539D54F25 /mount/point ntfs permissions,rw,uid=33,gid=33,umask=022,locale=en_US.utf8 0 0
UUID= would be the long number you got from running blkid and
/mount/point is the location of where the drive will be accessible. I like to put my drives in
/media/nextcloud. The mount point would need to exist, so you’d first make the directory with
sudo mkdir /media/nextcloud
gid are user and group ID. 33 is that of www-data, the user you want to have access to the directory to be able to read and write, and
umask is the default file permissions when writing to the volume (by default, the owner can read&write, everyone else only read)
This presumably would all need to be done before allowing the setup script to complete, as moving the data directory isn’t supported after setup, but you’ll be able to kick off the script again later.
If the drive is to be permanently allocated to the VM and hasn’t yet got your data on it, formatting it to a linux-preferred filesystem would be advantageous, though if it’s NTFS Ubuntu will support that too with a little more fluff in the fstab entry to set the correct permissions (an example of which I shall be able to provide tomorrow).
… maybe this should be a guide.