smeehrrr

Thanks for the fix and thanks for the plugin!

I ran Smart+DB again, and now it seems to be working. I don't know what happened that first time, maybe it still ran on the old version of the code? powerontime for the problematic device is now 27607.

Yes, that's what made it stop working again, I was previously running with the manually edited devices.json.

I picked this change up but I'm still getting the same error in the PHP log. [04-May-2025 13:49:54 America/Los_Angeles] PHP Fatal error: Uncaught DateMalformedIntervalStringException: Unknown or bad format (PT2984736978000S) in /usr/local/emhttp/plugins/disklocation/pages/functions.php:651

Here's the relevant sections from the .json. { "id": 9, "name": "Power_On_Hours", "value": 69, "worst": 69, "thresh": 0, "when_failed": "", "flags": { "value": 50, "string": "-O--CK ", "prefailure": false, "updated_online": true, "performance": false, "error_rate": false, "event_count": true, "auto_keep": true }, "raw": { "value": 27607, "string": "27607" } }, ... "power_on_time": { "hours": 829093510 },

"power_on_time": { "hours": 829093509 }, So it's wrong but it's still increasing.

Yes, devices.json has 829089714 as the powerontime for one drive. The model number is MB2000GCWDA which Google tells me is some HP refurb drive. It's hooked up to a Broadcom / LSI SAS2008 PCI-Express Fusion-MPT SAS-2 card. Just for the hell of it, I went and edited that field in the json field to be something reasonable, and the dashboard came up. The power on hours I see reported in the SMART report in the dash for this drive is 27607, so maybe something just got out of whack with the json file? One additional data point: Running SMART + DB from the disklocation system tab once again read an incorrect value (a different one this time) and bricked the dashboard again. Editing devices.json fixed it this time too.

Upgraded to 7.0.1 today and also picked up the latest version of disklocation (2025.03.18). Dashboard is failing to load now, PHP log is showing: PHP Fatal error: Uncaught DateMalformedIntervalStringException: Unknown or bad format (PT2984722970400S) in /usr/local/emhttp/plugins/disklocation/pages/functions.php:651 Any ideas how to fix? Full stack trace: Stack trace: #0 /usr/local/emhttp/plugins/disklocation/pages/functions.php(651): DateInterval->__construct('PT2984722970400...') #1 /usr/local/emhttp/plugins/disklocation/pages/array_devices.php(91): seconds_to_time(2984722970400) #2 /usr/local/emhttp/plugins/disklocation/pages/devices.php(36): require_once('/usr/local/emht...') #3 /usr/local/emhttp/plugins/dynamix/include/DefaultPageLayout.php(778) : eval()'d code(16): require_once('/usr/local/emht...') #4 /usr/local/emhttp/plugins/dynamix/include/DefaultPageLayout.php(778): eval() #5 /usr/local/emhttp/plugins/dynamix/template.php(94): require_once('/usr/local/emht...') #6 {main} thrown in /usr/local/emhttp/plugins/disklocation/pages/functions.php on line 651

For what it's worth, running ethtool -K eth0 tso off made the problem go away for me. I don't know what I'm giving up in terms for performance but it was a good enough temporary workaround to get all my files copied over. I did not have any of your additional issues with terminal, etc, just a momentary hitch that was long enough to interrupt file copies but not long enough to make ssh drop.

I started hitting this today after upgrading to 6.10.3. Attaching diagnostics just in case that's helpful. nova-diagnostics-20220809-1753.zip

If anyone gets wake-on-ARP working, would you please post your config? This is basically the only feature that I still need out of my Unraid and I'm willing to replace my hardware to get it.

Anyone have a list of NICs that support wake on ARP with Unraid? I desperately want this functionality. I thought wake on unicast was what I needed but that doesn't work.

Can anyone get their Unraid to wake on a unicast packet instead of a magic packet? All of my servers have an E1000 NIC in them and I can't get unicast to work at all. Magic packet works like a champ, but it's not practical to issue magic packets to wake these things due to the usage patterns. I'd be very interested to know if anyone can get unicast working with an E1000 NIC, or if you have a motherboard that does work I'd like to know what NIC is in it and what the model number of the motherboard is. I recently did a calculation of how much these servers are costing me in electricity while idling, and it's become clear that I need to get S3 working.