FlamongOle

never removed? check above commands if they get detected or not?

Some RAID cards might do weird stuff, can't guarantee they all will work with this plugin. Do you see all the drives with this command: lsscsi -u -b If no: nothing I can do. If yes, run this command on a drive that shows up in the plugin and one which doesn't: smartctl -x --json /dev/sg<X> where <X> is a drive number found from "lsscsi" command. Post these in a text file or on pastebin etc. From the smart output, it has to post a "model name" and a unique "serial number" from each drive as a minimum.

Cool, thanks. It will be included in the next update.

I don't see this warnings myself, but please try to replace the "!isset" with "!is_numeric" instead, and see if that helps? Do not reboot, this will just reinstall plugins and all changes you have manually done.

Try to write "0" (zero without quotes) instead of "null" on that line and see if it disappears, then I'll update that on next release

Update 2022.06.10 Commit #185 - BUG: json output of smartctl varies between SCSI protocols, checking for multiple variables instead. @jlficken

Update 2022.06.07 Commit #182 - BUG: Picked up wrong array from SMART data, Commit #182 should work now (hopefully). Added additional debugging lines and made NVMe drives be ignored from the standby check during scanning. @BlinkerFluid try now, thanks!

No reboots required. Can you check using SMART that "model name" and "serial number" is different from drive to drive, and not the same as getting info from the drive controller? Made sure the plugin is actually updated, and refreshed page before running "force scan"? You could also try to delete the database (back it up first just in case if you have put some work into it).

Update 2022.06.05 Commit #182 - BUG: With SCSI enclosures/SAS drives, SMART data behaves slightly different and ignores the drives as the plugin couldn't find them. Added new variables required to detect disks in enclosures. @BlinkerFluid

Had a quick look before I'm heading out getting drunk, don't understand why it doesn't work. Everything's in place for it to work, but hold on a couple of weeks and I'll have more thorough look when the 1) weather is shitty 2) I'm not drunk 3) have time to read my own code 4) remembering what I did with my code 5) hopefully find something useful 6) fix it: ETA: hopefully.

I have looked at it a bit, didn't find anything obvious yet with the first function loop. But I don't really have so much time maintaining this plugin anymore, it happens in sudden cycles. For the sake of it, can you post output of "lsscsi -u -b" as well (which is the actual output the plugin uses now)? Just wanna see if there's something different with that output with you SAS drives. In worst case I might need your database file, which contains all data as serial numbers etc., but I'll ask for that later (private download) if I need and you approve it. Else try this command on one disk you know works, and one that doesn't: smartctl -x --json /dev/sg<id> It's important that you use the "sg" assignment.

what does "lsscsi -ug" output?

As far as I can see from the logs, Disk Location installs as it should. However, I see some weirdness with whatever this is: "Mercury Elite Pro Elite Pro" Does not seem related with this plugin, and I can't recreate the problem. The S.M.A.R.T. data on that disk, or kontroller, or whatever it is, is likely causing the issue. Sorry, nothing I can do.

Super old thread, but I have the same problem. I just do exactly that myself. Sometimes it drops out because of another config somewhere in Unraid. And Samba I wanna use less possible.

Try the fix and see if it helped you. The override was part of the initial release before the groups were even added to provide with some alternative. There's no overkill, speed limits, or excessive data involved creating multi-groups. Override has mainly stayed there for backwards compatibility really. - I do consider deleting it in the future.

Update 2022.05.03 Commit #180 - BUG: Wrong numbering in the layout if using tray override - and please don't use tray override, just add another group. Count assignment still bugged if not using default, but won't affect assigned drives. @aglyons

Update 2022.04.22 Commit #177 - FEATURE: Added status indicator for ZFS drives. (*) Update 2022.04.25 Commit #177b - BUG: Fixed an issue where the indicator for ZFS would fail. Nobody asked for it, so here it is! Nothing else fixed or added. * This only works if the drives in a pool are created by using disk/by-id, and not the sd[X] crap.

Ok - read first page

It reset if you choose the "empty" color, if it doesn't work it might be an FF issue - which in case I can't be bothered to fix. That if you have updated the plugin to recent versions.

It should force use the date set by Unraid variables if I remember correctly. If it doesn't, it's a bug - maybe the unraid devs suddenly changed something behind the scene. Maybe I look into it one day.

Is the: Set warranty date entry: Set to "Unraid" and not "Manual ISO"?

It mainly should do exactly that if you have entered the data already in UNRAID. However, try "force update all" and see if it updates it. If not.. maybe the UNRAID dev's changed something in the system. The documentation against plugin creators are appalling, I considered multiple times to just shut down the project entirely. Not the answer you want maybe, but the versioning and documentation updates are really crap with UNRAID.. and this is a paid licensed product..

REQUEST FROM THE USERS Hey all! I consider modifying the core of the plugin for disk assignments and how they are bound, but I need some help/input from you guys. NB! I need info only from originally configured servers (not including non storage related devices)! Do not post from DIY servers! 1) I need the screenshot of the actual layout of the disks in a server. 2) Brand of the server and model. 3) The output of these two commands: lsscsi -g lshw -class disk -class storage -quiet -short 4) If possible, please attach the point 1-3 with a different disk configuration (like one less disk in the system, or positioned in a different slot), then post and describe the difference. Alternatively... If you can document the behavior of the kernel and storage devices path to be static, unique and reliable with the same assignment during reboots and that disks can be moved from one slot to another getting the correct assigned slot for it. Then that can be enough for my planning as well. So far I haven't found any proper information about it on google.. maybe I look for the wrong question? Any help appreciated! Thanks!

I have no idea if I will.. there's a lot of requests about it, but still not really the intention with the plugin

Yeah, can collapse a bit, but not entirely. Anyway, no big problem.