FlamongOle

Sorry for necroing the post, but did you ever manage to get this working? I had problems with 9p as well, but I can mount everything, but I just can't create new files into the shared folders. But I can edit, rename and delete existing files and folders (?!). While some other mount shares (with the exact same permissions and setup) working without problems. I had better luck with mounting shares from the array itself, and not the unassigned ones. Now I suddenly struggle a bit with a cache drive, while the regular "user" share works as expected. With one of my VM's I just ended up using NFS, at least it works, but it seems to be limited to 1Gbps which is not ideal for an nvme device. Maybe I should open a virtual network as well and not just passing it through. But 9p would been nice to use and simple in theory.. if it would work as expected.

Update 2019.07.06b Commit #92 - MINOR ISSUE: defined a variable as array(), caused a count() warning message.

Update 2019.07.06 Commit #90 - IMPROVEMENT: Adding a console window for "Force Scan" button, making it easier to see what's going on in the background. Commit #89 - BUG: Cache drive get unassigned color if it is an nvme drive. Use SCSI generic device node name instead if device node name is null.

@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.

Looks like I will just use NFS, at least it works 😛

It's just a number used for positioning of the regular dashboard widget looks. So far as far as I can see, only works with 0 (usually falls at bottom somewhere) or like 10 (goes on top), 1+ usually behaves as 10 if no other plugin widgets are installed. Read further on the plugin forum post itself. Maybe in the future they will make the current dashboard available for widgets in a more proper way, but so far (as I know) this is what we get.

I just use Position 10 and get it on the top instead, but not so much else you can do.

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.

👀

I have struggled with this for a while now, and no matter what I do I seem to fail mounting drives outside unraid array with correct permissions. So for the first and maybe most important question: Is there something that needs to be enabled to be able to use disk mounts outside Unraids array in a VM over 9p? If I mount any of the unraid array folders like /mnt/cache or /mnt/user/, I get expected permissions and can read and write and everything is wonderful. But if I then try to mount something like /mnt/disks/Cache (for a new external cache drive), or another /mnt/disks/Data folder which is both assigned via the "Unassigned devices" plugin, I get only read access except from creating files under root in the VM. I have checked the folders both when mounted and not, they all share the same user:group and chmod values. The fstab and mtab is exactly the same and I can't find any useful information in the log files either. I also tried to make a folder under root, chown it to myself with permissions telling me I should have no problems writing a file in it, but it still denies it. It must be something I really have overlooked, maybe something stupid and tiny - because I feel I've been through more of the "advanced" shit already. FSTAB: storage /mnt/storage 9p trans=virtio,version=9p2000.L,msize=262144,_netdev,rw 0 0 media /mnt/media 9p trans=virtio,version=9p2000.L,msize=262144,_netdev,rw 0 0 scratch /mnt/scratch 9p trans=virtio,version=9p2000.L,msize=262144,_netdev,rw 0 0 cache /mnt/cache 9p trans=virtio,version=9p2000.L,msize=262144,_netdev,rw 0 0 MTAB: storage /mnt/storage 9p rw,sync,dirsync,relatime,trans=virtio,version=9p2000.L,msize=262144 0 0 media /mnt/media 9p rw,sync,dirsync,relatime,trans=virtio,version=9p2000.L,msize=262144 0 0 scratch /mnt/scratch 9p rw,sync,dirsync,relatime,trans=virtio,version=9p2000.L,msize=262144 0 0 cache /mnt/cache 9p rw,sync,dirsync,relatime,trans=virtio,version=9p2000.L,msize=262144 0 0 "cache" is the only one which is troubling, and the only one outside the Unraid array. I have similar problems with another VM where I chose to run NFS instead, but I guess I would prefer to use 9p as long it is on the same machine. I could not find anything more about this specific problem on this forum, and I have been through multiple posts here already and tried like everything as setting gid,uid etc.

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.