Switch from FreeNAS over to OMV

Hi there, after lots of issues with FreeNAS, after being annoyed of not having the remote shell I am used to from Linux systems, and much more...

...I am thinking of switching my NAS at home to OMV.

Now a big thing ahead: I want my stuff to be encrypted. There seems to be a plugin for that in OMV? I did not find a guide to create the volumes with encryption though?

Any link would be nice here.

About RAID: I have raidz-2 right now, so raid5 would be corresponding. As FN uses the raid card in IT mode, it should be the same for OMV I suppose?

Lots of questions, maybe some are answered already? Sorry for not finding them at this point...

Best regards

David

Thanks for the quick reply!

The thing about ZFS: I don't necessarily need to be on ZFS.

What is the default technology used by OMV? How is it handling the (SW)Raid?

mdadm sounds like a good way to go. Also encryption is easy to implement here?

Then I'll get some big HDDs and copy off all stuff from the current FN setup and start fresh with OMV

So that one should work then? Sounds good! So a setup that is typically seen also on Ubuntu, with LVM -> LUKS -> Filesystem?

Just read about the plugin here on the forum.

So it's time to swap system these days! Thanks for all the input!

Thanks for the hint! Will backup all data, then see what to put where

Hi there, I just created a temporary OMV with some old HDDs to save all stuff for the installation of my main NAS.

Important stuff is backed up already, but lots of big files ~9TB need a temporary NAS...

Now I wanted to create a RAID on the temp NAS but get this 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-mkraid /dev/md0 -l stripe -n 5 -N asd /dev/sdj /dev/sdb /dev/sdd /dev/sdi /dev/sda 2>&1' with exit code '1': mdadm: chunk size defaults to 512K mdadm: super1.x cannot open /dev/sdb: Device or resource busy mdadm: /dev/sdb is not suitable for this array. mdadm: super1.x cannot open /dev/sdd: Device or resource busy mdadm: /dev/sdd is not suitable for this array. mdadm: super1.x cannot open /dev/sdi: Device or resource busy mdadm: /dev/sdi is not suitable for this array. mdadm: super1.x cannot open /dev/sda: Device or resource busy mdadm: /dev/sda is not suitable for this array. mdadm: create aborted

Any hint here?

Thanks!

Hi, I tried to do what you mentioned from console. (tried a couple times to wipefs) Here is also a more detailed error from webUI:

Error #0:
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-mkraid /dev/md0 -l stripe -n 5 -N stripe0 /dev/sda /dev/sdb /dev/sdd /dev/sdi /dev/sdj 2>&1' with exit code '1': mdadm: chunk size defaults to 512K
mdadm: Defaulting to version 1.2 metadata
mdadm: RUN_ARRAY failed: Unknown error 524 in /usr/share/php/openmediavault/system/process.inc:182
Stack trace:
#0 /usr/share/openmediavault/engined/rpc/raidmgmt.inc(300): OMV\System\Process->execute()
#1 [internal function]: Engined\Rpc\RaidMgmt->create(Array, Array)
#2 /usr/share/php/openmediavault/rpc/serviceabstract.inc(123): call_user_func_array(Array, Array)
#3 /usr/share/php/openmediavault/rpc/rpc.inc(86): OMV\Rpc\ServiceAbstract->callMethod('create', Array, Array)
#4 /usr/sbin/omv-engined(537): OMV\Rpc\Rpc::call('RaidMgmt', 'create', Array, Array, 1)
#5 {main}

Does this help?

EDIT: I tried to create RAID then wipe again, getting a weird message on one drive:

root@omv-temp:~# wipefs -a /dev/sda
/dev/sda: 4 bytes were erased at offset 0x00001000 (linux_raid_member): fc 4e 2b a9
root@omv-temp:~# wipefs -a /dev/sdb
/dev/sdb: 4 bytes were erased at offset 0x00001000 (linux_raid_member): fc 4e 2b a9
root@omv-temp:~# wipefs -a /dev/sdi
/dev/sdi: 4 bytes were erased at offset 0x00001000 (linux_raid_member): fc 4e 2b a9
root@omv-temp:~# wipefs -a /dev/sdj
wipefs: error: /dev/sdj: probing initialization failed: Device or resource busy
root@omv-temp:~# wipefs -a /dev/sdd
/dev/sdd: 4 bytes were erased at offset 0x00001000 (linux_raid_member): fc 4e 2b a9

EDIT again as nobody replied yet:

Formatting the drive singularly right now so I am able to move my data from my Freenas.

Will then hopefully work better on the FN box

EDIT once more:

I managed to create RAID and encrypted volumes(?) on it with:

mdadm --zero-superblock /dev/sdX

echo 1 > /sys/module/raid0/parameters/default_layout

Then all seems to work fine!

Thanks for all this support! As soon as I have any news I'll let you know!