Hello, 
When I edit the shown fields <configuration/sorting fields> if I add "device" anywhere, when I view the results it now shows "path" instead. Picture below, but it happens in all the pages, I'm sure it's just mapped incorrectly in the db possibly.

Just checking if it's a bug or if I'm doing something wrong (I was just trying to have the Unraid "device" name shown (disk1, 2, parity if its supported))

Thanks for the amazing plugin!!

 

Edited November 21, 20241 yr by bayn

14 hours ago, bayn said:

Hello, 
When I edit the shown fields <configuration/sorting fields> if I add "device" anywhere, when I view the results it now shows "path" instead. Picture below, but it happens in all the pages, I'm sure it's just mapped incorrectly in the db possibly.

Just checking if it's a bug or if I'm doing something wrong (I was just trying to have the Unraid "device" name shown (disk1, 2, parity if its supported))

Thanks for the amazing plugin!!

 

 

 

device=path

 

If you would have clicked the "help" button described on page 1 in this forum, you would have seen!  

Hello, 

I did see that layout - I didn't "understand" that's what the chart was showing me, guess I was being slow when I reviewed it.

 

I think I've run through all the options now - is there a way to see the unraid assignment (data disk/parity etc) in the information so I can export it and keep as a unraid "layout"?
I can manually update the comments field if we can't export that information, I just can't seem to locate it with any of the current fields, maybe I'm missing that again.

 

Thanks!

On 11/23/2024 at 6:05 PM, bayn said:

Hello, 

I did see that layout - I didn't "understand" that's what the chart was showing me, guess I was being slow when I reviewed it.

 

I think I've run through all the options now - is there a way to see the unraid assignment (data disk/parity etc) in the information so I can export it and keep as a unraid "layout"?
I can manually update the comments field if we can't export that information, I just can't seem to locate it with any of the current fields, maybe I'm missing that again.

 

Thanks!

The unraid layout is not accessible right there as it's not stored in the database. Might implement that in the future.

On 11/25/2024 at 9:20 AM, FlamongOle said:

The unraid layout is not accessible right there as it's not stored in the database. Might implement that in the future.

I think this would be another great feature to add, if you could!  Thanks in Advance!

I found a small issue: any drive part of a ZFS pool is blindly assumed to be cache. This used to be quite a safe assumption, but since a fair while now, it's no longer a 1-to-1 relation.

 

There is probably a better mechanism to ascertain whether a device is used as cache or data.

 

Temporary workaround would be a custom colour, but I'd be happier if this was solved permanently.

 

Edit: scratch that workaround. Custom colours don't work at all. After saving they are all just reset back to defaults. Maybe something to fix.

Edited December 3, 20241 yr by thany
No workaround available.

I found that one of my SSDs is pulsating on the Devices tab and in the dashboard widget. I don't know what this means.

 

It reveals a SMART warning - or so it claims. Because on the dashboard in the disk information widget, they all show up as healthy. So who's to believe?

 

And what do I do about "command timeout is above 5" anyway? This feels like the disk just happened to be under load while a measurement was taken. Is this correct? And does this pulsating thing ever go away then?

 

Lots of questions, ey. Seemingly conflicting information will do that, I suppose.

Feature Request: Ability to sort the "Unassigned Devices" table on the "Tray Allocations" tab. Thank you.

17 hours ago, noski said:

Feature Request: Ability to sort the "Unassigned Devices" table on the "Tray Allocations" tab. Thank you.

It is.

On 12/3/2024 at 4:06 PM, thany said:

I found a small issue: any drive part of a ZFS pool is blindly assumed to be cache. This used to be quite a safe assumption, but since a fair while now, it's no longer a 1-to-1 relation.

 

There is probably a better mechanism to ascertain whether a device is used as cache or data.

 

Temporary workaround would be a custom colour, but I'd be happier if this was solved permanently.

 

Edit: scratch that workaround. Custom colours don't work at all. After saving they are all just reset back to defaults. Maybe something to fix.

 

Things.

 

Custom colors might need to be reset before they actually work, it might be conflicting colors chosen and used based on the new and old color scheme. They should work, make sure you run the newest version too.

Update 2025.01.04 - mostly cosmetic

• Commit #338 - IMPROVEMENT: Made the Dashboard look similar to the rest.
• Commit #337 - IMPROVEMENT/MINOR: Due to confusion in the forums according to DL's SMART handling, the SMART data handling is modified to follow Unraids "acknowledgements". The manual input is removed and warning variables has been reset to the defaults. This will not be configurable anymore within the plugin. Idea is to let Unraids configuration to be in use as much as possible. This might/will be further improved in later versions as this is relatively a quick fix and it won't use other SMART attributes than 5, 187, 197, 198 for now (it is the default (except for 199) and should satisfy the majority).

Overhaul '25 part 1 preview!

 

New customization has been implemented, and more are in the works. This is available in the developer build right now, but it should not be used for production. It should mostly work, but it's not finished. Anyhow, a screenshot attached of one of the implementations made today. If you choose to try it out, limit the testing to "Configuration" and "System" tab only. "Information" (works, but limited) and "Tray Allocation" (have not tested yet, likely broken) are not done.

 

Cleanup of the configuration is taking place as well as the database. Soon the SMART updates will happen just in the "memory", so you don't need to worry about USB drive wear-outs. With that it will be hourly SMART updates on active drives. 

 

The plugin now uses the "ID" set in Unraid for SMART warnings, instead of relying on duplicate and fragmented data.

 

More to come!

 

On 1/4/2025 at 10:51 AM, FlamongOle said:

Update 2025.01.04 - mostly cosmetic

• Commit #338 - IMPROVEMENT: Made the Dashboard look similar to the rest.
• Commit #337 - IMPROVEMENT/MINOR: Due to confusion in the forums according to DL's SMART handling, the SMART data handling is modified to follow Unraids "acknowledgements". The manual input is removed and warning variables has been reset to the defaults. This will not be configurable anymore within the plugin. Idea is to let Unraids configuration to be in use as much as possible. This might/will be further improved in later versions as this is relatively a quick fix and it won't use other SMART attributes than 5, 187, 197, 198 for now (it is the default (except for 199) and should satisfy the majority).

First off, thanks for the plugin, it's great, however I'm facing the issue after this update in which I have a drive flashing yellow from an error that occurred years ago.

Personally I'd want the GUI to flash yellow like this when there is a new un-acknowlaged error and return to green once I acknowledge it. I don't want to disable warning for the particular error, as I want to be notified if the error count increases again.

3 hours ago, Jufy111 said:

First off, thanks for the plugin, it's great, however I'm facing the issue after this update in which I have a drive flashing yellow from an error that occurred years ago.

Personally I'd want the GUI to flash yellow like this when there is a new un-acknowlaged error and return to green once I acknowledge it. I don't want to disable warning for the particular error, as I want to be notified if the error count increases again.

 

First click "Save" under configuration, and see it that changes anything, otherwise:

 

Can you open command line and check the following output:

root@Odin:~# cat /var/local/emhttp/monitor.ini | grep disk2
disk2.199="48"          // SMART UDMA CRC error: 48
disk2.ack="true"        // Error acknowledged
disk2="97"              // Utilization

replace "disk2" with the disk name of you blinking device. 

 

If diskX.ack="true" is NOT displayed there, then that's why your device is still giving warning. I've seen some of my disk did not get "acknowledged", yet they were green. But recent acknowledgements have all been added to the monitor.ini file. Disk Location only care about the diskX.ack="true" and nothing else. The values are irrelevant at this point, and I must check if there's something I have been missing regarding the acknowledging of devices, but I could not see anywhere else this info was stored.

 

I dunno if @Squid (or someone else, dunno who to tag really) know if these acknowledgments are stored somewhere else?

Edited January 8, 20251 yr by FlamongOle
added troubleshooting step

7 hours ago, FlamongOle said:

 

First click "Save" under configuration, and see it that changes anything, otherwise:

 

Can you open command line and check the following output:

root@Odin:~# cat /var/local/emhttp/monitor.ini | grep disk2
disk2.199="48"          // SMART UDMA CRC error: 48
disk2.ack="true"        // Error acknowledged
disk2="97"              // Utilization

replace "disk2" with the disk name of you blinking device. 

 

If diskX.ack="true" is NOT displayed there, then that's why your device is still giving warning. I've seen some of my disk did not get "acknowledged", yet they were green. But recent acknowledgements have all been added to the monitor.ini file. Disk Location only care about the diskX.ack="true" and nothing else. The values are irrelevant at this point, and I must check if there's something I have been missing regarding the acknowledging of devices, but I could not see anywhere else this info was stored.

 

I dunno if @Squid (or someone else, dunno who to tag really) know if these acknowledgments are stored somewhere else?

 Thanks for the repose.

 

This is my only drive with a reallocated sector (error 5). I have other drives with a UDMA errors that are not flashing.

 

Below is the what I got returned. The values match my drive smart data.

cat /var/local/emhttp/monitor.ini | grep disk7
disk7.199="23"
disk7.5="2"
disk7.ack="true"

 

Let me know if I can assist in any other way.

On 1/8/2025 at 9:56 PM, Jufy111 said:

 Thanks for the repose.

 

This is my only drive with a reallocated sector (error 5). I have other drives with a UDMA errors that are not flashing.

 

Below is the what I got returned. The values match my drive smart data.

cat /var/local/emhttp/monitor.ini | grep disk7
disk7.199="23"
disk7.5="2"
disk7.ack="true"

 

Let me know if I can assist in any other way.

Did you try to force update all under system tab and also click save on the configuration tab?

Is the drive's SMART marked as "Failed" (red) or "None/Off" (gray)?

 

Could you send me your monitor.ini file if these things above does not work out for you?

1 hour ago, FlamongOle said:

Did you try to force update all under system tab and also click save on the configuration tab?

Is the drive's SMART marked as "Failed" (red) or "None/Off" (gray)?

 

Could you send me your monitor.ini file if these things above does not work out for you?

 

Thanks, that has fixed the issue.

 

The error line item comes up yellow under the drives smart data for both the UDMA error and the reallocated sector error.

8 hours ago, Jufy111 said:

 

Thanks, that has fixed the issue.

 

The error line item comes up yellow under the drives smart data for both the UDMA error and the reallocated sector error.

 

Thanks, then I don't look further into this.

Disk Location 2024 edition

 

The Overhaul '25 is in development and will change quite a lot on how it works as from today (at least under the hood), the database will of course be backed up during installation and migrated to the new one once launched. It will be possible to revert at a later point. However, if you don't want to be the first to get into the newest update (or ever?), I have now created a 2024-branch where the current plugin will be possible to install from.

 

CAUTION! This will not be maintained frequently (or maybe not at all?), but will be here as a choice for older Unraid versions or if you are not ready to migrate to the new Disk Location.

 

This has to be installed manually via plugin installer. Install the 2024 edition of the plugin using this URL in Unraid:
https://raw.githubusercontent.com/olehj/disklocation/2024-edition/disklocation-2024-edition.plg

 

It is possible the Overhaul '25 will be limited for Unraid version 7 and ongoing too, this is yet to be decided and tested depending on when Overhaul '25 will be launched.

Not sure if the new version will change things but one of the things that I'm struggling with right now is a 45 drive Supermicro 847 JBOD.



I'd like to be able to get it to disable 1-3 on JBOD Back rather than 22-24. Not sure if I'm just an idiot or if this actually isn't possible.

4 hours ago, ashtoruin said:

Not sure if the new version will change things but one of the things that I'm struggling with right now is a 45 drive Supermicro 847 JBOD.



I'd like to be able to get it to disable 1-3 on JBOD Back rather than 22-24. Not sure if I'm just an idiot or if this actually isn't possible.

Set tray count start to 4

Edited January 12, 20251 yr by FlamongOle

No the problem is the wrong trays are deleted when I tell it I only want 21 trays.

Compared to server/jbod front I want 1/2/3 removed not 22/23/24 so that it actually matches how the back of the chassis looks in real life. Honestly if I could just tell it to be a 4x6 array and then give it a comma seperated list of trays to black out that would be perfect. Then I could even combine server/jbod and delete the trays in the middle.
 

Edited January 12, 20251 yr by ashtoruin

3 hours ago, ashtoruin said:

No the problem is the wrong trays are deleted when I tell it I only want 21 trays.

Compared to server/jbod front I want 1/2/3 removed not 22/23/24 so that it actually matches how the back of the chassis looks in real life. Honestly if I could just tell it to be a 4x6 array and then give it a comma seperated list of trays to black out that would be perfect. Then I could even combine server/jbod and delete the trays in the middle.
 

Just create a 4x6 and leave 1-3 empty? It's hard to satisfy all possible configurations out there. Maybe I'll look into something later, but not a priority atm.

This isn't the first time I noticed this, so I thought I'd ask...

This plugin sometimes shows the wrong disk during drive swaps, etc...  For example...  I took Drive 7 offline to "no device", shut down and put in a bigger drive, restarted and applied the new drive to Drive 7.  The system is currently rebuilding, but this plugin shows Drive 9 flashing, even though 7 is actually rebuilding...

 

Any ideas?

42 minutes ago, House Of Cards said:

This isn't the first time I noticed this, so I thought I'd ask...

This plugin sometimes shows the wrong disk during drive swaps, etc...  For example...  I took Drive 7 offline to "no device", shut down and put in a bigger drive, restarted and applied the new drive to Drive 7.  The system is currently rebuilding, but this plugin shows Drive 9 flashing, even though 7 is actually rebuilding...

 

Any ideas?

If you are rebuilding then all drives should be flashing as they are all used during a rebuild.