Install problems

Hi all; apologies in advance for my idiocy - I'm having trouble with installing and since I'm not great with command line or linux I'll just provide as much detail as possible.

I'm trying to install OMV on a Raspberry Pi 2 attached to a USB drive and connected directy to my Virgin Superhub. There is no monitor and no peripherals here, so it'll only be remote access.

I hooked it up the TV to install after burning an ISO (omv_2.2.5_rpi2_rpi3.img) to an SD card. It went through a lot of text as it booted and seemed to work fine, eventually arriving at a login prompt - which I couldn't do because I don't have any input peripherals. Assuming it's done, I unplug and put the unit where it's going to sit permanently and try to load the web UI, which returns a 502 Gateway error.

Google led me to: 502 bad gateway

Followed the advice there as best I could, but I don't claim to really understand what I'm doing with most of it.

Now, I'm assuming that I haven't actually completed the installation by not following that command prompt? If so, is there a way to resolve that without access to a keyboard etc? I figure there must be since we're working on the Pi?

Alternatively...help?

Right, I'm off to buy the cheapest USB keyboard and wifi dongle I can find.

I now own a lovely Dell USB keyboard, and my TV is within reach of the router, so Raspberry is connected to internet, TV and keyboard. I ran through the boot procedure again and ended up in the same place, though this time I was able to input the default login details - but this doesn't seem to have changed anything wrt to the error.

I'll try rewriting the ISO now, but is there anything else I could be trying now/once it's done?

A post from the other 502 thread got me access to the GUI, but I'm running omv-update now just in case.

New problem is that the brand new USB HDD I've plugged in doesn't appear to be showing up anywhere in OMV. I plugged it in to my laptop and it turns up there, so the drive seems to work so I suppose I'm missing something else pretty obvious here?

Update complete, which broke the GUI again. Following this:

Installing the php5-pam update is the problem. It only works on true armhf systems.

Login via ssh as root and try:
wget http://omv-extras.org/debian/p…hp5-pam_1.0.3-2_armhf.deb
dpkg -i php5-pam_1.0.3-2_armhf.deb
reboot

seems to get it fixed again, so atleast I have GUI access.

Physical Disks shows:

Whilst File Systems shows this:

Thanks for your help, btw.

It's a 1TB drive. The LED on the drive itself comes on when it's hooked up to the Pi, so it's getting power which was my first (and only) thought.

Hi, I'm back again!

I've now got the Pi using a 2A power supply, so that shouldn't be a problem. I've also got the drive on a powered USB hub, so that should be sorted, too.

Still no sign of the drive on the web GUI. Could it be a formatting issue? I have literally bought the drive, imaged the SD card and plugged the lot in, so...?

Really, any suggestions welcomed. I've got Shell access and Web GUI access, so should be able to run any commands/diagnostics - I just have no idea what they might be myself!