Snapraid install fails; no raid0 persistence

Hello,

TL;DR; Raid0 fails after reboot. Snapraid fails to install even after omv update

The following packages have unmet dependencies:
 openmediavault-snapraid : Depends: snapraid (>= 9.1) but it is not installable
E: Unable to correct problems, you have held broken packages.

Goal: To make a RAID0 NAS and seedbox out of 3 usb sticks after HD died on trusty RPi3

Fails:

• Array persistence after reboot. most probably PEBKAC. Please see RAID0 creation commands below
• Snapraid plugin installation

udevadm control --stop-exec-queue
mdadm --create --verbose /dev/md0 --run --level=stripe --raid-devices=3 /dev/sda /dev/sdb /dev/sdc 
mdadm --stop /dev/md0
mdadm --detail --scan >> /etc/mdadm/mdadm.conf #
mdadm -A /dev/md0 /dev/sda /dev/sdb /dev/sdc --homehost=kodukoer --update=homehost
udevadm control --start-exec-queue

I have added the UUID of the array to fstab, but not quite sure either if it's correct. Just in case will bring it up here as well

UUID=77bd567a-a893a0b4-03eac542-27926cc9 /media/kuut ext4 rw,auto,nofail,acl,user_xattr,noexec,async,suid,dev,jqfmt=vfsv0,acl 0 2

Any feedback (pointers, hints, flame etc) is greatly appreciated!

Edit: added mdadm conf line

> Please don't use usb raid on an RPi. Yes, I know it only has usb.
I was sure hoping it can handle raid

> Why are you creating the raid array outside the web interface?
Due to the fact that:

• Cannot install snapraid
• Once raid was created from RAID Management, there was following output:

Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C; omv-mkraid /dev/md0 -l stripe -n 3 -N koerakoon /dev/sda /dev/sdb /dev/sdc 2>&1' with exit code '1': mdadm: chunk size defaults to 512K mdadm: Defaulting to version 1.2 metadata mdadm: failed to open /dev/sdb after earlier success - aborting


Error #0:
exception 'OMV\ExecException' with message 'Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C; omv-mkraid /dev/md0 -l stripe -n 3 -N koerakoon /dev/sda /dev/sdb /dev/sdc 2>&1' with exit code '1': mdadm: chunk size defaults to 512K
mdadm: Defaulting to version 1.2 metadata
mdadm: failed to open /dev/sdb after earlier success - aborting' in /usr/share/php/openmediavault/system/process.inc:175
Stack trace:
#0 /usr/share/openmediavault/engined/rpc/raidmgmt.inc(249): OMV\System\Process->execute()
#1 [internal function]: OMVRpcServiceRaidMgmt->create(Array, Array)
#2 /usr/share/php/openmediavault/rpc/serviceabstract.inc(124): call_user_func_array(Array, Array)
#3 /usr/share/php/openmediavault/rpc/rpc.inc(84): OMV\Rpc\ServiceAbstract->callMethod('create', Array, Array)
#4 /usr/sbin/omv-engined(516): OMV\Rpc\Rpc::call('RaidMgmt', 'create', Array, Array, 1)
#5 {main}

Quote from ryecoaaron

It can handle raid. I just have seen too many problems with it and any problems with raid 0 would cause all data to be lost.

I'm not really worried about data loss at the moment but rather in proof that raid can be created. Raid0 or 5.

Quote from ryecoaaron

Did you try the apt clean button in omv-extras?

I totally missed that. Tried but to no avail. Installing snap gives same error

Quote from ryecoaaron

You don't use snapraid with raid arrays typically.

Indeed it is a backup program for disk arrays. It was mentioned on some forum for creating arrays and I kind of stuck with it.

Also, you were asking for apt-cache snapraid policy output. Here it is:

snapraid:
  Installed: (none)
  Candidate: (none)
  Version table:

cat /etc/apt/sources.list.d/omv-extras-org.list output:

# This is file is generated.
# OMV-Extras repos
# 
# OMV-Extras.org
deb https://dl.bintray.com/openmediavault-plugin-developers/erasmus jessie main
# Debian Backports
deb http://httpredir.debian.org/debian jessie-backports main contrib

looks OK AFAIK

Quote from ryecoaaron

I wasn't thinking.

Happens to the best of us

Quote from ryecoaaron

it takes SOOOOOOOO long on an RPi and no one uses snapraid on an RPi. I will see about compiling it though.

It is not a priority atm but would be a nice feature. Thanks!

Thank you!