I'd already tweaked it to invoke Python 2.7 on my system - first thing
I did. The issues I'm seeing are not a trivial python versioning
issue.

For example, it assumes that logical volumes can be found at
/dev/<vg>/<lv>, a path that's not present on this system. I tweaked it
to use /dev/mapper/<vg>-<lv> path instead, which is present in my
system (Proxmox VE, which is debian-based), and then immediately ran
into another issue. Since that was the third non-trivial issue I'd run
into, I decided to cut my losses at that point - recovering this array
is my first priority. I may come back and file bugs later. Maybe even
learn a little bit of python and submit pull requests :)
- Paul
-- 
http://about.me/paul.chambers


On Sat, Nov 25, 2017 at 3:47 PM, Phil Turmel [off-list ref] wrote:

On 11/25/2017 11:14 AM, Anthony Youngman wrote:

quoted

On 25/11/17 02:54, Paul Chambers wrote:

quoted

Following this script is its output on the system in question. It's
missing the output of lsdrv (sorry), but it has multiple problems
running on my system, and I'm not proficient enough with python to fix
them all.

What's your default Python? 3? Then yes it will blow
up.

I had exactly that problem, and all I did was change the shebang line to
explicitly invoke Python 2.7. It worked perfectly.

Yeah, making it compatible with python3 is on my to-do list.