FlamongOle

@shaunmccloud It likely happened because your cache drive is an nvme drive and that unraid uses nvme0n1 device node name for identification. This would be left blank in this plugin as it saved only the device node, and not the scsi generic device node. It will now store scsigen dev node as dev node if it is empty. In other words, should be fixed during next update.

I tried this now and got the same problem, looks like something is partly ignoring the unraid flags, I'll look into it soon

Try to delete it and reinstall it, if it still fails you have to delete the database manually and try again. Be sure to wait until the installation is done and reports it has done so successfully. rm /boot/config/plugins/disklocation/disklocation.sqlite If you did an upgrade and want to keep settings, a backup file of v3 should be in the same folder. Just unpack it and write it over the existing database.

Ah, in the database itself. That flag means "hidden", and simply hides it for assignments. It should be auto detected by force scanning the drives (which it does not do automatically anymore).

What do you mean by identified by "h", like sdh? or does some information lack here? The "sdh" in this case is used to catch data from Unraid-table so we know which disk does what in regard of the Unraid array. Else the most useful information this plugin needs and uses is the information from "lsscsi -g -u" + smartctl. It might be a bug.

The plugin doesn't use the "sdX" for anything other than information (as they are quite useless and unpredictable). But the cache disk has to be set as a cache drive by unraid and recognized as one as well. You can try to reset the specific Cache drive color by choosing one of the pre-defined colors, it should then null out the value in the database.

Unassigned disks and the specific unraid disks (parity, data and cache) will always have a unique color. You can only have a custom color which does not crash with the same color. I guess the best solution is to take "the next color" and assign that, like #FF0000 is the color, then try #FF0001. Most likely you won't notice the difference, try to increase different segment of the color (RGB) if you do. You can either use override, or just add another group. Whatever suits your needs most.

Just in case: The new plugin is split up in two main sections, one for Configuration (located under "Settings") and one for the Information itself (located under "Tools").

It is now updated to work with 6.7.2 and onward, new update is released!

Update 2019.06.28 - Design v2.0 Commit #45 - REQUEST: Different tray count (from @FrackinFrog) Commit #22 - REQUEST: Multiple cases (from tarchive). Add a bunch of cases made available including a bunch of other configuration possibilities. Removed a bunch of bugs, rewrote a lot of code, and has in general made "Design v2.0". Too much to document, most forgotten anyway! But a lot of work has gone into this release. NB! Due to weird Unraid releases and versioning, this plugin will only work from 6.7.2 and onward! 6.7.1 is broken (missing SQLite support). And I can't bothered keeping an eye with older versions as well. Development version is required else (but it will not work with 6.7.1).

It's a teaser for next update

Yes, wait for the next update.

👀

Ok, next release will start from the next SQLite activated release making all previous versions incompatible. It is easier this way, rather than skipping some version in between. Working on something major changesright now

Yes I know, but I don't want to mess up too much with the Dashboard page. The way I have implemented it now is rather a "hack" to make it look like the new dashboard, and not the old style. So far not so much I can do without making some other problems. Sorry

Alright, thanks for clearing things up a bit, I am relatively new to Unraid and what has been going around here in the forums. So for future reference, better not care too much about the versioning and how its done. SQLite is what I define as the opposite of overkill, utilizing a full blown database like MariaDB, PostreSQL etc. would have been. Before I made this plugin, I did check my possibilities, and any SQL database will make the life easier. SQLite - which is the simplest and has less support for most SQL commands, will anyway fit perfect for its task. I am rather surprised no more people uses it, it makes the life a hell lot easier than dealing with text files. And SQLite is rather just a glorified text file in this sense without any real extra bloat. Anyway, I hope this is just temporary (as it seems for now) and I can continue with this plugin the way I started it 6 months ago. I just use the tools which is available, where I can. Tell the users to switch to Emby, better than Plex anyway Anyway, I hope you figure out the problem, and I'll keep a watch on what's happening from release to release. PS! I didn't intend to beat anyone Have a nice day!

Yeah, maybe. Still find it a bit strange that this isn't done in beta and rc releases, but at a stable level.

As @Squid said, you can't use the plugin if the array is stopped. It stops Docker and VM's when you stop the array, so yeah didn't think about that. Looks like they either have to enable SQLite in PHP again, or this plugin is likely dead.

Yes, I would even prefer it over SQLite for the database sake, but for simplicity SQLite is a winner as we don't need to access other databases and setup the connection before we can start using the plugin. But this will rather likely be the future path if SQLite will be permanently disabled. That is your own MariaDB docker + this plugin.

Update 2019.06.23 PFFT¤#"!%" - Currently need to stop support at Unraid 6.7.0 because lack of SQLite support in PHP from and including Unraid 6.7.1. Follow the forums for more information of the future.

I wrote some information about current standing with this plugin and Unraid, it is not optimistic... yet. https://forums.unraid.net/topic/81169-unraid-os-version-671-available/?tab=comments#comment-753703 Please continue writing here on this thread, not at the release thread.

Hi I just received information about this and that they have disabled sqlite from php in 6.7.1. Disk Location will be incompatible until I find another way of implementing another database because I am not dealing with ini/conf files for this. It is seriously annoying, even if it (might) create problems for other users with Unraid, it makes making plugin for Unraid quite annoying. The lack of general documentation and information, and then they suddenly remove support for some major things will destroy the motivation on continuing on the plugin itself. Removing SQLite is one thing, but not adding another SQL database where I can access own created plugin database makes this a very annoying task. So for now, I am sad to say, that the plugin is dead from and including 6.7.1 until SQLite (or any other SQL database) will be accessible for plugins. I am not messing with "text files", it's highly ineffective. Sorry. Anyway, if you have any ideas on how to go on with this, please continue this particular thread in the Disk Location plugin thread at https://forums.unraid.net/topic/77302-plugin-disk-location/

Geez, so I now have to rely on idiotic config/ini files for this? @limetech wtf?

Hot-swapping might be the issue here, I have also "hot-swappable" trays and motherboard/controllers supposedly supporting it. But in the end, it does -work- but the data is often recognized as the first disk which was installed in that specific port. A reboot might solve the issue, then do a force scan all. My two cents though.