Fusion-io ioDrive 2 1.2TB Reference Page

Notice: Page may contain affiliate links for which we may earn a small commission through services like Amazon Affiliates or Skimlinks.
J

Jon

Member
Feb 28, 2016
77
18
8
43
OK trying it out without a card just to see if building the driver still works but running into this?

using: snuf/iomemory-vsl
copied this header into the dirrectory : pve-headers_5.2-2_all.deb (not sure about this step? )

root@pveD1541:~/iomemory-vsl# sudo dpkg-buildpackage
dpkg-buildpackage: info: source package iomemory-vsl
dpkg-buildpackage: info: source version 3.2.15.1800-1.0
dpkg-buildpackage: info: source distribution unstable
dpkg-buildpackage: info: source changed by Support <support@fusionio.com>
dpkg-buildpackage: info: host architecture amd64
dpkg-source --before-build iomemory-vsl
dpkg-checkbuilddeps: error: Unmet build dependencies: debhelper (>= 10) linux-headers
dpkg-buildpackage: warning: build dependencies/conflicts unsatisfied; aborting
dpkg-buildpackage: warning: (Use -d flag to override.)
 
EffrafaxOfWug

EffrafaxOfWug

Radioactive Member
Feb 12, 2015
1,394
512
113
Jon said:
dpkg-checkbuilddeps: error: Unmet build dependencies: debhelper (>= 10) linux-headers
Click to expand...
I'm no proxmox expert but generally this means you're missing the linux-headers package - this is a subset of the kernel source and usually needed to build any kernel modules against it. `aptitude install linux-headers-amd64` or whatever the proxmox equivalent is (proxmox might well use a different name) should install this package if it's possible.

Edit: a wee google says the proxmox package is called `pve-headers`.
 
J

Jon

Member
Feb 28, 2016
77
18
8
43
EffrafaxOfWug said:
Edit: a wee google says the proxmox package is called `pve-headers`.
Click to expand...
You are no proxmox pro and i am no linux pro :)

Think I am getting somewhere?

Using : snuf/iomemory-vsl

Code: 
apt-get update && apt-get upgrade -y
apt-get install dpkg-buildpackage
apt-get install pve-headers
apt-get install pve-headers-4.15.18-3-pve

git clone https://github.com/snuf/iomemory-vsl
cd iomemory-vsl/
git checkout next_generation
sudo cp -r iomemory-vsl/root/usr/src/iomemory-vsl-3.2.15 /usr/src/
sudo mkdir -p /var/lib/dkms/iomemory-vsl/3.2.15/build
sudo ln -s /usr/src/iomemory-vsl-3.2.15 /var/lib/dkms/iomemory-vsl/3.2.15/source
sudo dkms build -m iomemory-vsl -v 3.2.15
sudo dkms install -m iomemory-vsl -v 3.2.15
sudo modprobe iomemory-vsl
Need to figure out how to install utils now and see if I actually buy a card :)

EDIT:

Code: 
%%%%copy the sandisk/WD original utilities to folder first using WinSCP

sudo dpkg -i /root/iomemory-vsl/utilities/fio-common-3.2.15.1700-1.0_amd64.deb
sudo dpkg -i /root/iomemory-vsl/utilities/fio-preinstall-3.2.15.1700-1.0_amd64.deb
sudo dpkg -i /root/iomemory-vsl/utilities/fio-util-3.2.15.1700-1.0_amd64.deb
sudo dpkg -i /root/iomemory-vsl/utilities/fio-sysvinit-3.2.15.1700-1.0_all.deb
 
Last edited:
T

thalooka

New Member
Oct 20, 2018
11
2
3
@acquacow
do you know if its possible to flash an dell branded iodrive2 to hp?
Since HP got this ulgy fan spinning at max with non HP Branded PCI
 
T

thalooka

New Member
Oct 20, 2018
11
2
3
i mean the fans of the HP dl380e
Got an 1.2tb iodrive2 if the HP iLO cant verify its HP Branded firmware the iLO of the HP Server just spins the fans on full speed, cant PWM.
 
acquacow

acquacow

Well-Known Member
Feb 15, 2017
796
447
63
43
You can unzip the HP and Dell drivers, look at the manifest file and move your model into the manifest for the HP driver and re-zip.
 
T

thalooka

New Member
Oct 20, 2018
11
2
3
acquacow said:
You can unzip the HP and Dell drivers, look at the manifest file and move your model into the manifest for the HP driver and re-zip.
Click to expand...
So there is no way in cross flashing the Firmware itself right?
 
Last edited:
T

thalooka

New Member
Oct 20, 2018
11
2
3
acquacow said:
There is, I just told you how to do it. You need to update the manifest with the model info for your card.
Click to expand...
ah fine thanks a lot then was confused by the "driver" part but forgot i got firmware/driver bundled here sorry.
would guess the "manifest" is in the "info" file n i gotta seach up the "hp codename" then.

Anyways thanks a lot for your help!
 
lowfat

lowfat

Active Member
Nov 25, 2016
131
91
28
41
Have an ioDrive Duo working Proxmox 5.3-5 using the newest official drivers. Had to rebuild the drivers for the newest kernel.

Code: 
Adapter: Dual Adapter
        HP 320GB SLC PCIe ioDrive Duo for ProLiant Servers, Product Number:600281-B21, SN:418610
        External Power Override: ON
        External Power: NOT connected
        PCIe Power limit threshold: 74.75W
        Connected ioMemory modules:
          fct0: Product Number:600281-B21, SN:423066
          fct1: Product Number:600281-B21, SN:423067

fct0    Attached
        HP ioDIMM 160GB, Product Number:600281-B21, SN:423066
        Located in slot 0 Upper of ioDrive Duo HL SN:418610
        Last Power Monitor Incident: 73 sec
        PCI:08:00.0, Slot Number:3
        Firmware v7.1.17, rev 116786 Public
        160.00 GBytes device size
        Internal temperature: 43.80 degC, max 44.30 degC
        Reserve space status: Healthy; Reserves: 100.00%, warn at 10.00%
        Contained VSUs:
          fioa: ID:0, UUID:01e36bfa-d575-3842-a2c0-ff4272fd4da1

fioa    State: Online, Type: block device
        ID:0, UUID:01e36bfa-d575-3842-a2c0-ff4272fd4da1
        160.00 GBytes device size

fct1    Attached
        HP ioDIMM 160GB, Product Number:600281-B21, SN:423067
        Located in slot 1 Lower of ioDrive Duo HL SN:418610
        PCI:09:00.0, Slot Number:3
        Firmware v7.1.17, rev 116786 Public
        160.00 GBytes device size
        Internal temperature: 50.20 degC, max 50.69 degC
        Reserve space status: Healthy; Reserves: 100.00%, warn at 10.00%
        Contained VSUs:
          fiob: ID:0, UUID:b76d8e72-725a-464b-ac3c-89b9ca66677b

fiob    State: Online, Type: block device
        ID:0, UUID:b76d8e72-725a-464b-ac3c-89b9ca66677b
        160.00 GBytes device size
 
Last edited:
D

DetroitJD

New Member
Jan 9, 2019
6
0
1
Detroit, Mi
This thread has been amazing. I've gotten further than ever before using Proxmox 5.3-6, but I seem to be stuck. I can't seem to get the 4.3.4 official version to build on kernel 4.15-0-43-generic. It seems like there's an issue with missing the x86_64_cc73_libkfio.o. Not sure if you've installed GCC 7.3.0 yet.

@lowfat is this the version you're using?

I have a PX600-1300 and it just seems to be fighting me the entire time.

I see it registered as a PCI device, so there's at least that.
 
lowfat

lowfat

Active Member
Nov 25, 2016
131
91
28
41
I have everything up to date including PVE which is 5.3.7 but GCC is showing "gcc (Debian 6.3.0-18+deb9u1) 6.3.0 20170516"

Have you tried building w/ the snuf drivers? gcc 7.3 · Issue #12 · snuf/iomemory-vsl

Someone there mentions that when using GCC 7.3 they also had a similar issue.
 
D

DetroitJD

New Member
Jan 9, 2019
6
0
1
Detroit, Mi
lowfat said:
I have everything up to date including PVE which is 5.3.7 but GCC is showing "gcc (Debian 6.3.0-18+deb9u1) 6.3.0 20170516"

Have you tried building w/ the snuf drivers? gcc 7.3 · Issue #12 · snuf/iomemory-vsl

Someone there mentions that when using GCC 7.3 they also had a similar issue.
Click to expand...
Yessir. I might need to make some changes to the makefile however, since it does a clean before the compile. Renaming the library from 71 to 73 doesn't work as expected because the object file gets deleted before the compiler runs.

Thanks for the reply Lowfat. I appreciate it!
 
You must log in or register to reply here.
Top Bottom