file system showing, but cant create shared folder

Hiya

I've just installed 5.2.1-1 (Usul) on a clean rPi4,4gb, followed the OMV manual to setup, enabled SMB/CIFS, shutdown, connected a working external usb drive and booted the device.

In OMV UI, the drive is listed, as is the filesystem, showing the correct disk usage etc...

Problem is that when I try to create a shared folder, I click on "select a device" and there's a brief flash, but no returned device.

The rpc.php json response is just

{"response":[],"error":null}

SSH commands reveal the drive is mounted correctly.

Is anyone experiencing a similar issue?

I would appreciate some help in overcoming this issue as although I know the device path, partition, UUIDv4, filesystem and so on, there is no way to manually add this to the UI of OVM.

I am willing to follow any steps and provide feedback... providing more info /downgrading OVM / add data to the OVM database / etc... if the issue cannot be resolved via the UI.

Many thanks.

my apologies that I was unclear

The drive was automatically mounted upon reboot, so I did not have to perform a mount inside OVM, logging into OVM for the first time both the drive and its filesystem were picked up perfectly, so I assumed I could just go ahead and create a shared folder, but the device didn't show up there, whereas it did elsewhere.

Thank you for your amazingly fast reply!

@macom

thanks for your fast reply. I understand your point, and the result of the rpc.php script was found using [x] disable cache in the chrome dev inspector. Also I see OVM correctly sets the pragma / cache-control and even the expires headers so sadly it's not a cache issue nice job by OVM by the way!

@crashtest

Ah now we're getting somewhere, thank you.

I rebooted, unmounted, and attempted to remount, which was unsuccessful - an "Error" css pop-up appeared, I hope you don't mind if I quote the whole thing, I've tried to format it appropriately:

I could use a shell to execute

export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C.UTF-8; omv-salt deploy run fstab

to get deeper insight?

Error:

Failed to execute command 


'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C.UTF-8; omv-salt deploy run fstab 2>&1'


with exit code '1': 


/usr/lib/python3/dist-packages/salt/utils/path.py:265: 
DeprecationWarning: Using or importing the ABCs from 'collections' instead of from 'collections.abc' is deprecated, and in 3.8 it will stop working if not isinstance(exes, collections.Iterable): 
/usr/lib/python3/dist-packages/salt/utils/decorators/signature.py:31: DeprecationWarning: `formatargspec` is deprecated since Python 3.5. Use `signature` and the `Signature` object directly *salt.utils.args.get_function_argspec(original_function) raspberrypi: 
---------- 


ID: create_filesystem_mountpoint_725e4fbd-1e86-4ac6-b07f-79d9539f73f5 Function: file.accumulated Result: True Comment: Accumulator create_filesystem_mountpoint_725e4fbd-1e86-4ac6-b07f-79d9539f73f5 for file /etc/fstab was charged by text 
Started: 20:57:28.286548 
Duration: 1.57 ms 
Changes: 
----------
ID: mount_filesystem_mountpoint_725e4fbd-1e86-4ac6-b07f-79d9539f73f5 
Function: mount.mounted 
Name: /srv/dev-disk-by-label-Seagate Wireless 
Result: False 
Comment: mount: bad usage Try 'mount --help' for more information. 
Started: 20:57:28.289745 
Duration: 441.913 ms 
Changes: 
----------


ID: append_fstab_entries 
Function: file.blockreplace 
Name: /etc/fstab 
Result: True 
Comment: No changes needed to be made 
Started: 20:57:28.733778 
Duration: 9.905 ms 
Changes: Summary for raspberrypi 
------------ 


Succeeded: 2 
Failed: 1 
------------ 


Total states run: 3 
Total run time: 453.388 ms

@crashtest

We must have posted at the same time so I missed your comment about HFS+

Thank you for spotting that.

I did suspect it might be something like that as I didn't see HFS+ anywhere either.

One thing I find off though, as mentioned the disk/fs was correctly mounted by raspian and I could access the files in bash.

and despite having hfsplus installed via
[tt]sudo apt-get install hfsplus[\tt]

OVM can't use hfs+ but the OS can.

Are there any plans to allow hfs+ in the UI, I am assuming there are various logic issues with other parts of the software, but I am hoping that it still might be possible to mount it in the OVM UI as read-only rather than having to program against the complexities of a new file system if it hasn't been abstracted away.

Anyway thank you, I am not sure where this leaves me really, apart from converting to another file system, considering the drive came out of a Seagate Wireless device where the files were read/writeable over Wifi all on a 2cm by 5cm board, it would be really nice to think HFS+ is coming soon to OVM

@crashtest

Thank you for that info, you're right, as I have no requirements at all, I will get on with the job of moving the data and reformatting the disk to a native format which will come with other benefits

I really appreciate your help, and have a Happy New Year.