-
Notifications
You must be signed in to change notification settings - Fork 28
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[FEATURE] Possible to enumerate the drives as /dev/sd* or /dev/nvme* #74
Comments
There's no way to do this. It's hardcoded in the firmware driver, and we
don't have the source code for that.
…On Mon, Dec 28, 2020 at 6:35 PM cmc0619 ***@***.***> wrote:
I'd like to use these drives in an Unraid server but their software only
looks for devices named under /dev/sd* or /dev/nvme*. Is there a way to
change how these drives present? Maybe something "simple" as a udev rule
file that could be created? Or a barring that switch that could be
specificied on module load?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#74>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AO7IG5BRP7VAZRACFA7NXZ3SXEI43ANCNFSM4VMSZKJQ>
.
|
Hi @cmc0619 as @Tourman36 pointed out we're not in full control of that atm. The easiest way to do this is with have udev trigger and create a symlink or something probably. You can find an example here: https://unix.stackexchange.com/questions/119593/is-there-a-way-to-change-device-names-in-dev-directory#:~:text=1%20Answer&text=According%20to%20udev%20manual%2C%20there's,additional%20symlinks%20can%20be%20created. |
This is best left to the Unraid folks... they are the ones making assumptions about what a device is named. I'd go as far as saying "lsblk correctly identifies /dev/fio* as block devices, why doesn't UNRAID" and let them sort it out. That's a bug! |
@cmc0619 I did some digging, the main issue is that unraid uses In the example above the ID is set by a program, for a fio device this could be Let me know if this helps? |
This is what FOSS is all about 😀 Happy new year! |
you will need fio-utils installed, but this seems to create some disk/by-id and disk/by-path nodes:
if you would rather use the serial numbers of the fio than the formatted UUID, replace iom.format_uuid with iom.fio_serial_number |
@cmc0619 the file is merged into the main branch, if you could check if it solves your problem that would be great? |
You guys are amazing. Unfortunately, I'm away from my server for a few weeks. I've updated the thread on the lime technologies webpage to ask if anyone else can confirm. |
Thanks everyone for the hard work on getting this going! Just a question, does the above go into the /lib/udev/rules.d ? |
@jcarron2 typically I think you'd place it in |
closing this as there is a udev rules file now. |
I'd like to use these drives in an Unraid server but their software only looks for devices named under /dev/sd* or /dev/nvme*. Is there a way to change how these drives present? Maybe something "simple" as a udev rule file that could be created? Or a barring that switch that could be specificied on module load?
The text was updated successfully, but these errors were encountered: