So, I replied to the previous error mounting disk thread but received no replies, so I'm hoping to get some more eyeballs on it here.
The last thread suggested using gdisk to format the drive, then use the OMV control panel to make it EXT4. I did that to no avail.
I am running OMV 5 and have OMV installed on a 250GB Samsung SSD. I started with two drives, a WD Red and WD White (both 8TB) and used mergerfs to 'create' a single, 16TB drive. That drive has since been filled, so I recently added a 16TB Seagate Exos drive to my server.
Unfortunately, when I installed it, formatted it through OMV (EXT4), etc., I can't get it to mount. It formats fine, it's detected by the OS, but when I try to mount, I get the same error 100% of the time:
OMV\ExecException: 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 --no-color fstab 2>&1' with exit code '1': debian: Data failed to compile:Traceback (most recent call last): File "/usr/lib/python3/dist-packages/salt/utils/templates.py", line 497, in render_jinja_tmpl output = template.render(**decoded_context) File "/usr/lib/python3/dist-packages/jinja2/asyncsupport.py", line 76, in render return original_render(self, *args, **kwargs) File "/usr/lib/python3/dist-packages/jinja2/environment.py", line 1008, in render return self.environment.handle_exception(exc_info, True) File "/usr/lib/python3/dist-packages/jinja2/environment.py", line 780, in handle_exception reraise(exc_type, exc_value, tb) File "/usr/lib/python3/dist-packages/jinja2/_compat.py", line 37, in reraise raise value.with_traceback(tb) File "<template>", line 25, in top-level template code File "/usr/lib/python3/dist-packages/jinja2/sandbox.py", line 385, in getattr value = getattr(obj, attribute) File "/usr/lib/python3/dist-packages/openmediavault/collectiontools.py", line 126, in __getitem__ return dict.__getitem__(self, key)#0 /usr/share/php/openmediavault/engine/module/serviceabstract.inc(62): OMV\System\Process->execute()#1 /usr/share/openmediavault/engined/rpc/config.inc(167): OMV\Engine\Module\ServiceAbstract->deploy()#4 /usr/share/php/openmediavault/rpc/rpc.inc(86): OMV\Rpc\ServiceAbstract->callMethod('applyChanges', Array, Array)#5 /usr/share/openmediavault/engined/rpc/filesystemmgmt.inc(917): OMV\Rpc\Rpc::call('Config', 'applyChanges', Array, Array)#8 /usr/share/php/openmediavault/rpc/rpc.inc(86): OMV\Rpc\ServiceAbstract->callMethod('mount', Array, Array)
The people in r/selfhosted (reddit and Discord) have told me there's a salt issue, but I've tried all sorts of omv-salt commands to rectify that to no avail. I stumbled upon this post and it sounded SO similar to mine, so I used gdisk, created a partition table, etc., then deleted and re-added the drive through the OMV GUI. It formatted fine, so once it was done initializing, I tried mounting it and got this error AGAIN.
I'm hoping to finally get it mounted so I can add its absolute path to mergerfs and open up another 16TB. Otherwise, my drives are full.
If anyone can help, I would be indebted to you. Soma?