I just discovered OMV thanks to the wonders of Google and a dying NAS.
I HAD a 2 bay Thecus NAS with the disks setup as JBOD,
Cue a hardware failure and many hours of troubleshooting later and I managed to find OMV. (The disks seem to be fine, the Thecus is toast)
I've installed OMV on a VirtualBox VM (Windows host). I've setup the disks in VirtualBox as raw disks so that the VM has full access to the entire disk. (I did this after attempting to use a USB3 dock and seeing that it wont work thanks to a tooltip in the UI)
Im attempting (hopefully) to get the disks showing but not sure what to do at this point.
When I go to RAID tab, the "members" show up, and (to my understanding) I should be trying to "Recover" to make them visible through OMV - but when I click Recover, no disks show up.
When I go to File Systems tab, and try mount a disk, I get errors:
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/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) debian: ---------- ID: create_filesystem_mountpoint_0d2bc85a-a582-497f-9d35-04233a961d14 Function: file.accumulated Result: True Comment: Accumulator create_filesystem_mountpoint_0d2bc85a-a582-497f-9d35-04233a961d14 for file /etc/fstab was charged by text Started: 19:47:17.890293 Duration: 0.382 ms Changes: ---------- ID: mount_filesystem_mountpoint_0d2bc85a-a582-497f-9d35-04233a961d14 Function: mount.mounted Name: /srv/dev-disk-by-id-md-name-N2310-0 Result: False Comment: mount: /srv/dev-disk-by-id-md-name-N2310-0: wrong fs type, bad option, bad superblock on /dev/md124, missing codepage or helper program, or other error. Started: 19:47:17.891041 Duration: 212.422 ms Changes: ---------- ID: append_fstab_entries Function: file.blockreplace Name: /etc/fstab Result: True Comment: No changes needed to be made Started: 19:47:18.104380 Duration: 2.81 ms Changes: Summary for debian ------------ Succeeded: 2 Failed: 1 ------------ Total states run: 3 Total run time: 215.614 ms
And from the "display":
Not sure where else to go with this, if setting up in a VM is the issue, if the disks are the issue etc etc
Any wizard with some pearls of wisdom?