juchong

I can definitely understand your reaction if the norm on the forums is for folks to "demand the source" and then walk away from the discussion. In contrast, I'm actually serious about trying to understand how the driver enumerates devices. Here's my fork of the driver with modifications specifically intended to allow compilation using the Unraid Kernel Docker Container: https://github.com/juchong/iomemory-vsl4 Edit: Here's the build script for anyone that wants to try it out themselves: https://github.com/juchong/unraid-fusionio-build

This is disappointing. Getting back to the thread topic, can anyone help me identify which section of the code performs the device enumeration? It would help speed up the process significantly.

Hey now, no need to be passive-agressive. I'm trying to help the community. Both of my interactions with moderators in this thread have been met with unwarranted aggression thus far. Reading through the forums, there seems to be a similar pattern in lots of threads where people are asking genuine questions.

Thanks. Would it be possible to point me to the md source code (if available publicly)? I've put together a reliable method of building the driver on 5.x kernels already.

Thanks, but your reply was not helpful. I'm trying to add support for the driver and have been largely successful. The last piece in the puzzle is getting the md driver to detect the drive, hence my question.

I'm trying to understand what UnRAID expects to read from a drive before it will be enumerated by the md driver. I modified the FusionIO driver to enumerate as /dev/hda temporarily and still couldn't get the driver to detect the card. I suspect that the md driver expects the drive to have a serial number (the FusionIO driver does not provide one by default), but I could be wrong. Does anyone have more insight into this?

Update: After a few minutes of sitting on the main page, the CPU meter will start to display data again. Is there a built-in proxy that maybe isn't getting configured properly?

Hi everyone, I'm running Unraid 6.9.0 beta 30 and recently ran into issues with the VNC viewer and CPU meter both refusing to work after I changed the default http port to 8081. I made this change to allow the SWAG to handle requests on port 80. Has anyone ran into issues like this? Is there a setting I can change to get these features back? Thanks!

I've been able to successfully compile and install the latest version of the driver on beta30 using your docker container! I've even gone as far as to add the necessary variables so that the code fits nicely within your current script. I've also been able to move away from using .txz files in favor of dkms. This ended up simplifying the compilation process quite a bit and should hopefully make it somewhat future-proof. I still have to figure out the custom udev rules and perform more testing, but otherwise things look good on the 5.8.13 kernel! /dev/fioa1: Timing cached reads: 25754 MB in 1.99 seconds = 12950.66 MB/sec Timing buffered disk reads: 6038 MB in 3.00 seconds = 2012.51 MB/sec

Hi folks! I've been able to get the driver to compile on 4.x kernels (Unraid 6.8.3) cleanly using the Unraid-Kernel-Helper docker. I'm working out how to get unRAID to recognize the drives now. Stay tuned!

You'd be surprised! There seems to be a lot of interest from folks looking to add these to their servers since the prices have dropped dramatically in the past few years (link). I personally got my hands on a 6.4TB card for ~$400, so I've got a lot of incentive to get this working! It's just a kernel module, but I have to pull a few .txz files needed for the compile. Not a big deal. I'm running tests now, but everything seems to be happy! Do you have a GitHub repo I can make a pull request in?

Thanks! I'm moving over my hacked-together build process into your build script for testing. If this works out, would you consider adding this feature to the Docker?

Thanks, everyone! I'll know a bit more once I do some testing, but I think I might have a reasonable method of enabling the use of the iomemory modules! I personally have a 6.4TB version ready to be used as a cache drive.

I'm working on adding support for iomemory devices (or at least properly documenting the method for building support) and can't figure out how to manually install kernel modules onto the USB drive. Can anyone tell me what the right way to do this is? Thanks!