mmx01

Looks like either mdcmd or another process waits for attach message for a device sd* or nvme* which fio* is not part of. It is able to report in tools/preclear though Preclear Disk||| DeviceIdentificationTemp.SizeLogPreclear Status fioa_*320 GBDisk mounted How array configurator is enumerating drives? by-id is not the way as otherwise it should pop-up root@unRAID:/boot/files# ls /dev/disk/by-id/ ata-CT500MX500SSD1_1832E14D21D9@ usb-SanDisk_Cruzer_Blade_4C530001280726115430-0:0@ ata-CT500MX500SSD1_1832E14D21D9-part1@ usb-SanDisk_Cruzer_Blade_4C530001280726115430-0:0-part1@ iodrive@ wwn-0x5000c50062e19a17@ iodrive-part1@ wwn-0x5000c50062e19a17-part1@ scsi-35000c50062e19a17@ wwn-0x5000c5006343d327@ scsi-35000c50062e19a17-part1@ wwn-0x5000c5006343d327-part1@ scsi-35000c5006343d327@ wwn-0x5000c5009e743a3f@ scsi-35000c5006343d327-part1@ wwn-0x5000c5009e743a3f-part1@ scsi-35000c5009e743a3f@ wwn-0x5000c5009e743afb@ scsi-35000c5009e743a3f-part1@ wwn-0x5000c5009e743afb-part1@ scsi-35000c5009e743afb@ wwn-0x5000c5009e743f43@ scsi-35000c5009e743afb-part1@ wwn-0x5000c5009e743f43-part1@ scsi-35000c5009e743f43@ wwn-0x500a0751e14d21d9@ scsi-35000c5009e743f43-part1@ wwn-0x500a0751e14d21d9-part1@

I am not a developer hence have no experience in packaging that stuff Tell me what is needed to progress on this even as a test case. This is totally mock-up manual procedure I have. I was even able to convert debian package to txz and have fio-utils to manage the drive working too. However simple tricks to create links like sds -> fioa, sds1 -> fioa1 do not make the trick. The drive does not come visible in unassigned devices or array configurator. This is why I started looking at udev mappings to convince the drive to attach as sd* rather than fio* Steps to get it working as a drive visible to the OS: 1. You need kernel source first 4.19.88 (linux-4.19.88.tar.xz) & the packages from slackware 14.2 - dkms (and all its deps like ncurses in txz format, easy to install with installpkg) - dev tools plugin to be able to compile 2. Copy .config from existing kernel source to the new one. If you don't set the kernel name correctly which .config does you will end up with insmod complaining about mismatch after io driver build 3. New kernel will be in /usr/src/linux-4.19.88 you need to temporarily move exiting one to old and new one to /usr/src/linux-4.19.88-Unraid so all headers are available for compiling, there is no need to load new kernel at all 4. You need the driver https://github.com/snuf/iomemory-vsl - Follow dkms steps on GitHub to compile the driver 5. Since /lib/modules is a ro/file as squashfs I took the easy path of copying compiled .ko module to /boot and do /boot/config/go insmod /boot/iomemory-vsl.ko.xz. This is not mature enough to go through building new bzmodules. 6. Register to san disk web page and download fio-util_3.2.15.1700-1.0_amd64.deb, deb2tgz will give txz which you can install with installpkg This is not doing any tricks: ln -s /dev/fioa /dev/sds ln -s /dev/fioa1 /dev/sds1 ln -s /dev/sds /dev/disk/by-id/iodrive ln -s /dev/sds1 /dev/disk/by-id/iodrive-part1 Not on lsscsi root@unRAID:/usr/src# lsscsi [0:0:0:0] disk SanDisk Cruzer Blade 1.00 /dev/sda [1:0:0:0] disk SEAGATE ST1000NX0323 K002 /dev/sdb [1:0:1:0] disk SEAGATE ST1000NX0323 K002 /dev/sdc [1:0:2:0] disk SEAGATE ST1000NX0323 K002 /dev/sdd [1:0:3:0] disk SEAGATE ST1000NM0023 0004 /dev/sde [1:0:4:0] disk SEAGATE ST1000NM0023 0004 /dev/sdf [1:0:5:0] disk ATA CT500MX500SSD1 022 /dev/sdg but still there and working root@unRAID:/boot/files# mount /dev/fioa1 /tmp/tmp/ root@unRAID:/boot/files# touch /tmp/tmp/test root@unRAID:/boot/files# ls -la /tmp/tmp/ total 16 drwxr-xr-x 1 root root 8 Feb 16 21:30 ./ drwxrwxrwt 12 root root 240 Feb 16 21:30 ../ -rw-rw-rw- 1 root root 0 Feb 16 21:30 test root@unRAID:/boot/files# blkid /dev/fioa1: UUID="2b299144-f28d-4c06-9884-483586007b02" UUID_SUB="f4b16ba2-5ac7-4162-be24-ee0022d7f0c2" TYPE="btrfs" root@unRAID:/boot/files# fio-status Found 1 ioMemory device in this system with 1 ioDrive Duo Driver version: 3.2.15 build 1700 Adapter: Dual Adapter 640GB High IOPS MLC Duo Adapter for IBM System x, Product Number:81Y4517, SN:90438 External Power: NOT connected PCIe Power limit threshold: 24.75W Connected ioMemory modules: fct0: Product Number:81Y4517, SN:74486 fct0 Attached IBM ioDIMM 320GB, SN:74486 Located in slot 0 Upper of ioDrive Duo HL SN:90438 PCI:15:00.0 Firmware v7.1.17, rev 116786 Public 320.00 GBytes device size Internal temperature: 43.31 degC, max 44.30 degC Reserve space status: Healthy; Reserves: 100.00%, warn at 10.00% Contained VSUs: fioa: ID:0, UUID:e6468008-1eeb-439d-addf-624d70706c56 fioa State: Online, Type: block device ID:0, UUID:e6468008-1eeb-439d-addf-624d70706c56 320.00 GBytes device size [ 154.804222] <6>fioinf ioDrive 0000:15:00.0: Found device fct0 (640GB High IOPS MLC Duo Adapter for IBM System x 0000:15:00.0) on pipeline 0 [ 155.671053] <6>fioinf 640GB High IOPS MLC Duo Adapter for IBM System x 0000:15:00.0: probed fct0 [ 155.675414] <6>fioinf 640GB High IOPS MLC Duo Adapter for IBM System x 0000:15:00.0: sector_size=512 [ 155.675420] <6>fioinf 640GB High IOPS MLC Duo Adapter for IBM System x 0000:15:00.0: setting channel range data to [2 .. 4095] [ 155.685856] <6>fioinf 640GB High IOPS MLC Duo Adapter for IBM System x 0000:15:00.0: Found metadata in EBs 2698-3028, loading... [ 155.805497] <6>fioinf 640GB High IOPS MLC Duo Adapter for IBM System x 0000:15:00.0: setting recovered append point 3028+96796672 [ 155.880346] <6>fioinf 640GB High IOPS MLC Duo Adapter for IBM System x 0000:15:00.0: Creating device of size 320000000000 bytes with 625000000 sectors of 512 bytes (317861 mapped). [ 155.881689] fioinf enable_discard set but discard not supported on this linux version [ 155.881701] fioinf 640GB High IOPS MLC Duo Adapter for IBM System x 0000:15:00.0: Creating block device fioa: major: 254 minor: 0 sector size: 512... [ 155.881984] fioa: fioa1 [ 155.882422] <6>fioinf 640GB High IOPS MLC Duo Adapter for IBM System x 0000:15:00.0: Attach succeeded. [ 158.627521] md: unRAID driver 2.9.13 installed [23744.304519] BTRFS: device fsid 2b299144-f28d-4c06-9884-483586007b02 devid 1 transid 5 /dev/fioa1 [23747.038336] BTRFS info (device fioa1): disk space caching is enabled [23747.038338] BTRFS info (device fioa1): has skinny extents [23747.038338] BTRFS info (device fioa1): flagging fs with big metadata feature [23747.040864] BTRFS info (device fioa1): checking UUID tree

I have managed to get the driver compiled and working. Formatted as xfs and mounted with no issues. The issue is with array configurator not displaying the device, same for unassigned devices plugin. I suspect it is due to the drive reporting as block device but under fio, /dev/fioa, /dev/fioa1 rather than sd*. Udev permanent storage and probably all other unraid specific scripts look for sd* & nvme*. This is what I am trying to establish now.

One culprit I see could be due to this: root@unRAID:~# udevadm info --query=path --name=fioa /devices/virtual/block/fioa Not a real HW path, is that it? How to convince configurator it is okay in fact.

Hi All, I realize this is not officially supported hence looking only for pointers. I have ioDrive 640GB version (2x320GB) and wanted to make use of it. Took some effort to have the driver compiled but here I am. The drive is recognized by the OS, I was able to partition and mount it. There is however no way I can convince unraid array configurator to show the drive as either data or cache drive. Any suggestion how this is done would be really appreciated. Is it that configurator looks for /dev/s*? It shows as block device fioa1 (partition 1 on fioa). I load it at boot before md start. Regards, Mariusz root@unRAID:~# mount /dev/fioa1 /tmp/ root@unRAID:~# cd /tmp/ root@unRAID:/tmp# ls -la total 16 drwxr-xr-x 1 root root 0 Feb 14 19:24 ./ drwxr-xr-x 19 root root 400 Feb 14 18:22 ../ root@unRAID:/tmp# touch test root@unRAID:/tmp# ls -la total 16 drwxr-xr-x 1 root root 8 Feb 14 19:24 ./ drwxr-xr-x 19 root root 400 Feb 14 18:22 ../ -rw-rw-rw- 1 root root 0 Feb 14 19:24 test root@unRAID:/tmp# blkid /dev/loop0: TYPE="squashfs" /dev/loop1: TYPE="squashfs" /dev/sda1: LABEL_FATBOOT="UNRAID" LABEL="UNRAID" UUID="272C-EBE2" TYPE="vfat" /dev/sdb1: UUID="c157fef1-c037-4f8b-95c0-de093aeb6fe1" TYPE="xfs" PARTUUID="7efc64e8-e3d3-4f61-b1c3-eb6548190f19" /dev/sdc1: UUID="6c8dddbd-03dd-40f6-8398-b708d100b5c8" TYPE="xfs" PARTUUID="d1c2a76a-2495-458d-94ba-96b2be254cb8" /dev/sdd1: UUID="54b7540e-f3db-43c3-9d21-e81458e64e65" TYPE="xfs" PARTUUID="80e3ca13-ea97-44fd-bad1-14f1bc902128" /dev/sde1: UUID="62dbd8ed-5621-4eb4-bc5a-ceb565864819" TYPE="xfs" /dev/fioa1: UUID="ba5ea1c5-3f8d-4a99-b47b-5648af952df3" UUID_SUB="18fb9b57-2a27-4aba-b3b5-8c8f54befd29" TYPE="btrfs" PARTUUID="0da74ca9-01" root@unRAID:~# fio-status Found 1 ioMemory device in this system with 1 ioDrive Duo Driver version: 3.2.15 build 1700 Adapter: Dual Adapter 640GB High IOPS MLC Duo Adapter for IBM System x, Product Number:81Y4517, SN:90438 External Power: NOT connected PCIe Power limit threshold: 24.75W Connected ioMemory modules: fct0: Product Number:81Y4517, SN:74486 fct0 Attached IBM ioDIMM 320GB, SN:74486 Located in slot 0 Upper of ioDrive Duo HL SN:90438 PCI:15:00.0 Firmware v7.1.17, rev 116786 Public 320.00 GBytes device size Internal temperature: 44.30 degC, max 44.30 degC Reserve space status: Healthy; Reserves: 100.00%, warn at 10.00% Contained VSUs: fioa: ID:0, UUID:e6468008-1eeb-439d-addf-624d70706c56 fioa State: Online, Type: block device ID:0, UUID:e6468008-1eeb-439d-addf-624d70706c56 320.00 GBytes device size [ 151.212896] iomemory_vsl: loading out-of-tree module taints kernel. [ 151.215150] <6>fioinf VSL configuration hash: 50cc3bdba9fe52b90d1821e59d81452e4a6eac09 [ 151.215190] <6>fioinf [ 151.215191] <6>fioinf Copyright (c) 2006-2014 Fusion-io, Inc. (acquired by SanDisk Corp. 2014) [ 151.215191] <6>fioinf Copyright (c) 2014-2016 SanDisk Corp. and/or all its affiliates. All rights reserved. [ 151.215192] <6>fioinf For Terms and Conditions see the License file included [ 151.215192] <6>fioinf with this driver package. [ 151.215192] <6>fioinf [ 151.215193] <6>fioinf ioDrive driver 3.2.15.1700 pinnacles@3dd0050df54c loading... [ 151.215549] iodrive 0000:15:00.0: enabling device (0000 -> 0002) [ 151.216259] <6>fioinf ioDrive 0000:15:00.0: mapping controller on BAR 5 [ 151.216505] <6>fioinf ioDrive 0000:15:00.0: MSI enabled [ 151.216514] <6>fioinf ioDrive 0000:15:00.0: using MSI interrupts [ 151.246696] resource sanity check: requesting [mem 0x000e0000-0x000fffff], which spans more than PCI Bus 0000:00 [mem 0x000e4000-0x000e7fff window] [ 151.246715] caller find_slot_number_bios+0x35/0x13a [iomemory_vsl] mapping multiple BARs [ 151.246824] resource sanity check: requesting [mem 0x000e0000-0x000fffff], which spans more than PCI Bus 0000:00 [mem 0x000e4000-0x000e7fff window] [ 151.246836] caller find_slot_number_bios+0x35/0x13a [iomemory_vsl] mapping multiple BARs [ 151.246877] <6>fioinf ioDrive 0000:15:00.0.0: Starting master controller [ 152.101641] <6>fioinf ioDrive 0000:15:00.0.0: Adapter serial number is 90438 [ 152.956551] <6>fioinf ioDrive 0000:15:00.0.0: Board serial number is 74486 [ 152.956554] <6>fioinf ioDrive 0000:15:00.0.0: Default capacity 320.000 GBytes [ 152.956555] <6>fioinf ioDrive 0000:15:00.0.0: Default sector size 512 bytes [ 152.956556] <6>fioinf ioDrive 0000:15:00.0.0: Rated endurance 4.00 PBytes [ 152.956557] <6>fioinf ioDrive 0000:15:00.0.0: 85C temp range hardware found [ 152.961062] <6>fioinf ioDrive 0000:15:00.0.0: Firmware version 7.1.17 116786 (0x700411 0x1c832) [ 152.961063] <6>fioinf ioDrive 0000:15:00.0.0: Platform version 10 [ 152.961063] <6>fioinf ioDrive 0000:15:00.0.0: Firmware VCS version 116786 [0x1c832] [ 152.961071] <6>fioinf ioDrive 0000:15:00.0.0: Firmware VCS uid 0xaeb15671994a45642f91efbb214fa428e4245f8a [ 152.963680] <6>fioinf ioDrive 0000:15:00.0.0: Powercut flush: Enabled [ 153.064478] <6>fioinf ioDrive 0000:15:00.0.0: PCIe power monitor enabled (master). Limit set to 24.750 watts. [ 153.064480] <6>fioinf ioDrive 0000:15:00.0.0: Thermal monitoring: Enabled [ 153.064482] <6>fioinf ioDrive 0000:15:00.0.0: Hardware temperature alarm set for 85C. [ 153.073850] <6>fioinf ioDrive 0000:15:00.0: Found device fct0 (640GB High IOPS MLC Duo Adapter for IBM System x 0000:15:00.0) on pipeline 0 [ 154.001784] <6>fioinf 640GB High IOPS MLC Duo Adapter for IBM System x 0000:15:00.0: probed fct0 [ 154.004480] <6>fioinf 640GB High IOPS MLC Duo Adapter for IBM System x 0000:15:00.0: sector_size=512 [ 154.004486] <6>fioinf 640GB High IOPS MLC Duo Adapter for IBM System x 0000:15:00.0: setting channel range data to [2 .. 4095] [ 154.015829] <6>fioinf 640GB High IOPS MLC Duo Adapter for IBM System x 0000:15:00.0: Found metadata in EBs 3541-485, loading... [ 154.139779] <6>fioinf 640GB High IOPS MLC Duo Adapter for IBM System x 0000:15:00.0: setting recovered append point 485+96796672 [ 154.216963] <6>fioinf 640GB High IOPS MLC Duo Adapter for IBM System x 0000:15:00.0: Creating device of size 320000000000 bytes with 625000000 sectors of 512 bytes (9144 mapped). [ 154.218287] fioinf enable_discard set but discard not supported on this linux version [ 154.218296] fioinf 640GB High IOPS MLC Duo Adapter for IBM System x 0000:15:00.0: Creating block device fioa: major: 254 minor: 0 sector size: 512... [ 154.218547] fioa: fioa1 [ 154.218721] <6>fioinf 640GB High IOPS MLC Duo Adapter for IBM System x 0000:15:00.0: Attach succeeded. [ 156.583510] md: unRAID driver 2.9.13 installed