Installing OMV on a RasPi B via apt on Raspbian fails on package tftpd-hpa

Hi there,

I tried setting up OMV via apt on a fresh install of Raspbian (2015-02-16-raspbian-wheezy) twice without success using this guide here: Install OMV on Debian via apt

Every time it seems to fail when starting/installing HPA's tftpd and therefore it also failes to proccess the OMV package itself.
Running a

apt-get -f install

does not work. Doing a

apt-get install --reinstall openmediavault

doesn't seem to work, either.

Maybe you guys can have a look through the install messages I get and find out what's happening to point me into the right direction.
I pastebinned it here: http://pastebin.com/cHNAtkN8

I think the mess all starts at line 698:

Setting up tftpd-hpa (5.2-4) ...
[....] Starting HPA's tftpd: in.tftpdinvoke-rc.d: initscript tftpd-hpa, action "start" failed.
dpkg: error processing tftpd-hpa (--configure):
 subprocess installed post-installation script returned error exit status 71

It also seems I got trouble with that php5-pam update as can be seen starting at line 730:

Processing triggers for php5-fpm ...
Illegal instruction

This should be counteracted with a
wget http://omv-extras.org/debian/pool/main/p/php5-pam/php5-pam_1.0.3-2_armhf.deb
dpkg -i php5-pam_1.0.3-2_armhf.deb
I guess?
Or could this be the root cause for the problems I described above?

Thank you a lot in advance.
Best regards.

Zitat von ryecoaaron

Why not use my image? There are a bunch of little problems that need to be tweaked with Raspbian.

Thanks for the fast reply, ryecoaaron!

Your image is my "plan b" if the Rasbpian thingy fails too often (and with no chance of success in the near future).
Is your image as open/flexible as an usual installation via apt on Raspbian or are there any limitations (for packages, raspi-config, etc.)?

Sounds like we have a deal
I'm just downloading the omv_1.12_rpi_rpi2 image. Nice job btw for putting things together for us RasPi users. Thank you a lot!

Oh, btw: Does this image use arm-hf?

Thanks again for your fast reply. I'll give it a try and report back.
I think we can call this issue closed for now.