On 5/1/2025 at 10:16 AM, FlamongOle said:

Update 2025.05.01

• Commit #414 - MINOR: Empty array error occurs when there's no backup made during auto backup. Creates a new backup if none is found. Should then make auto backups as expected.
• Commit #413 - MINOR: Wrong Power On Hours might be picked up. In some instances the power_on_time could crash the Dashboard because the value was too high for DateTime.
   

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
 

3 hours ago, Thx And Bye said:

 

I've just now fond the time to run the steps with debugging. I've reset devices first and then ran SMART+DB again with debugging enabled. I've send you the .log file via PM.

Thanks, I see that the device is not populated in the array but all data otherwise seems fine. I don't understand really what is happening here, the values and all looks good.

 

I would maybe try to reset the "devices" under "System" tab if you haven't already. Maybe something got corrupted there. Then run a SMART+DB again.

 

If it doesn't help, please send me the devices.json file: /boot/config/plugins/disklocation/devices.json 

 

Thanks

15 minutes ago, smeehrrr said:

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
 

Did you do a SMART+DB? It must be done to change the value in devices.json.

Just now, FlamongOle said:

Did you do a SMART+DB? It must be done to change the value in devices.json.

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

7 minutes ago, smeehrrr said:

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

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.

 

Just now, smeehrrr said:

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.

 

Ah good, thanks! I couldn't figure out why it wouldn't work as it does indeed look correct  

 

Not entirely sure why it would happen. Running just SMART wouldn't change much, but SMART+DB should. All "system" files are deleted before upgrading to make sure all are on the newest version and no conflicting files exists. So it can't run an old cronjob. Just write me again if the error persists in the future, then I'll have another look at it.

 

Thanks for providing me info  

Thanks for the fix and thanks for the plugin!

On 5/4/2025 at 11:04 PM, FlamongOle said:

Thanks, I see that the device is not populated in the array but all data otherwise seems fine. I don't understand really what is happening here, the values and all looks good.

 

I would maybe try to reset the "devices" under "System" tab if you haven't already. Maybe something got corrupted there. Then run a SMART+DB again.

 

If it doesn't help, please send me the devices.json file: /boot/config/plugins/disklocation/devices.json 

 

Thanks

 

So I think I now know what the issue is. After the update to UnRAID 7.1.x the drive didn't show up anymore at all. So its likely that the drive has failed. I don't know why the SSD didn't show up the the UI of unRAID as failed though.
After the update and subsequent reboot the device doesn't show up in the list and unRAID UI anymore. This also means that the plugin is not showing the error anymore and lists the configured slot as unpopulated.

I have a replacement drive ordered and will report back if it shows up correctly in the plugin now too.

Edited May 10, 20251 yr by Thx And Bye

Any update on this issue:

I am experiencing the same issue

51 minutes ago, casperse said:

Any update on this issue:

I am experiencing the same issue

Mentioned several times and are pinned as recommended in this forum thread.

Update 2025.05.15

 

• Commit #418 - MINOR: Fixed a small glitch where the Unraid icons were shown regardless of settings.
• Commit #416 - IMPROVEMENT: Change warning to critical if drive is "faulted"

Edited May 14, 20251 yr by FlamongOle

On 5/10/2025 at 2:32 PM, Thx And Bye said:

I have a replacement drive ordered and will report back if it shows up correctly in the plugin now too.

With all drives working now, the plugin is showing the status on the dashboard as expected.

One odd thing (but nothing critical): My flash is showing a S.M.A.R.T warning while the drive itself reports S.M.A.R.T as passed based on an Attribute check.

 

I understand that a SATA SSD attached to a USB<->SATA adapter isn't the usual setup for the flash. Just an odd thing I've noticed.

 

IB-245-C31-20250515-2100.txt

2 hours ago, Thx And Bye said:

With all drives working now, the plugin is showing the status on the dashboard as expected.

One odd thing (but nothing critical): My flash is showing a S.M.A.R.T warning while the drive itself reports S.M.A.R.T as passed based on an Attribute check.

 

I understand that a SATA SSD attached to a USB<->SATA adapter isn't the usual setup for the flash. Just an odd thing I've noticed.

 

IB-245-C31-20250515-2100.txt 6.63 kB · 1 download

Does it have unacknowledged SMART errors detected? Check SMART tab in Disk Location and check if the device show "NO" under "Acknowledged"

These warnings have higher priorities than the over-all health status.

Update 2025.05.16

• Commit #420 - IMPROVEMENT: If a controller on a device is dead, plugin tries to find related drive and showing it as SMART FAILED and will also display error log in SMART tab if it exists. SMART tab changed slightly, background colors is related to the status of the drive.

 

SMART tab:

 

Dashboard:

 

 

Yes, I have that kind of NVMe drive right now

Hello everyone,

 

I've got this alert and I didn't have it before, so it's not a problem for me. I'm posting a message here to let you know and, if necessary, to help.

 

 

1 hour ago, Midas_Tech said:

Hello everyone,

 

I've got this alert and I didn't have it before, so it's not a problem for me. I'm posting a message here to let you know and, if necessary, to help.

 

 

Thanks, I have reordered some code to prevent that. Next release will hopefully fix this and also add notification to dead drives.

Update 2025.05.17

Yes I know, one day too early but who cares? 😛

• Commit #423 - MINOR: Other irrelevant errors occurred in SMART tab. Rearranged the code.
• Commit #422 - ENHANCEMENT: Added notification when a major device error occurs. E.g. If the drive loses it's controller, send an alert notification in Unraid about it.

@Midas_Tech this version, then a SMART update should hopefully fix it!

 

Happy Norwegian Constitution Day release! 🇳🇴🥳 

Hello,

 

Thank you for your message. I've installed this latest version and can confirm that it's OK again!

 

THANK YOU!!!

 

18 hours ago, FlamongOle said:

Does it have unacknowledged SMART errors detected? Check SMART tab in Disk Location and check if the device show "NO" under "Acknowledged"

It does indeed list one value there for the drive (Reallocated_Sector_Ct is 1) but as unRAID shows "No Attributes Available" for the flash there is no way to acknowledge the error.
This SSD is quite old already and also connected via USB. So I'm not sure if it's because of the age, the connection or UnRAID not knowing how to deal with this situation (the flash having attributes in the first place). Starting S.M.A.R.T tests for the flash also doesn't seem to work.
Smartctl is seemingly able to read the values, albeit not absolutely correctly since 109 years of power on time doesn't seem plausible to me.

2 hours ago, Thx And Bye said:

It does indeed list one value there for the drive (Reallocated_Sector_Ct is 1) but as unRAID shows "No Attributes Available" for the flash there is no way to acknowledge the error.
This SSD is quite old already and also connected via USB. So I'm not sure if it's because of the age, the connection or UnRAID not knowing how to deal with this situation (the flash having attributes in the first place). Starting S.M.A.R.T tests for the flash also doesn't seem to work.
Smartctl is seemingly able to read the values, albeit not absolutely correctly since 109 years of power on time doesn't seem plausible to me.

Likely how it's connected or that the controller for it does not pass through Smart or something. Usually Flash is never even included in Disk Location as it's mostly just pen drives. I have no plans to implement it either. 

On 3/11/2025 at 10:30 AM, FlamongOle said:

FOR USERS WITH STUCK UPDATES: Tried to work around a possible flaw where the plugin would not automatically update, it might at some point been headed to the 2024-edition branch instead of the master branch. New installation file in 2024-edition branch will point it back to the master branch, hopefully. Alternatively, re-installation of the plugin might be required if it continues to be stuck on version 2025.02.08. Re-installations/removal will NOT remove any configuration.

I'll be honest - I don't use the info that this plugin holds all that often, but when I do, it's VERY helpful!

 

That said, I just now realized that I was stuck on the 2025.02.08 version. I'm very thankful that you posted & pinned this comment explaining what to do.

I uninstalled and reinstalled and now, all seems good.

 

Thanks for continuing to maintain & evolve this plugin!!

OK, gotta ask... Do these numbers make any sense at all???

 

How is it that an SSD is reading at ~80MB/s while a 5400RPM drive reads more than 2x that speed??

I understand that these may not be the fastest SSDs ever made, but still...

 

Is this an indication that maybe the drive is dying, or was it probably just in use by something else at the time of the speed test?

On 5/16/2025 at 2:35 PM, FlamongOle said:

Update 2025.05.17

Yes I know, one day too early but who cares? 😛

• Commit #423 - MINOR: Other irrelevant errors occurred in SMART tab. Rearranged the code.
• Commit #422 - ENHANCEMENT: Added notification when a major device error occurs. E.g. If the drive loses it's controller, send an alert notification in Unraid about it.

@Midas_Tech this version, then a SMART update should hopefully fix it!

 

Happy Norwegian Constitution Day release! 🇳🇴🥳 

Got this when rebooting today.
 

Quote

Event: Disk Location: sda
Subject: Alert - Device failure
Description:
Importance: alert

/dev/sg0: Unknown USB bridge [0x090c:0x1000 (0x1100)]

There's nothing wrong with sda.

Edit:

Force SMART or SMART+DB will repeat the alert.
 

Checking devices, please wait until it is completed...

SMART: /dev/sg0 FAILED () done in 2430ms.

Edited May 17, 20251 yr by Niklas

6 hours ago, Free Man said:

OK, gotta ask... Do these numbers make any sense at all???

 

How is it that an SSD is reading at ~80MB/s while a 5400RPM drive reads more than 2x that speed??

I understand that these may not be the fastest SSDs ever made, but still...

 

Is this an indication that maybe the drive is dying, or was it probably just in use by something else at the time of the speed test?

Can be several things. If the drive is in use while benchmarking, the values will be lower. 

 

But likely this is the actual speed of the SSD, cache is bypassed (which you'll often see higher speeds from). Some SSDs are in fact just slow in read and write, but they still feel faster than spinning drives because of no seek time. 

3 hours ago, Niklas said:

Got this when rebooting today.
 

There's nothing wrong with sda.

Edit:

Force SMART or SMART+DB will repeat the alert.
 

Checking devices, please wait until it is completed...

SMART: /dev/sg0 FAILED () done in 2430ms.

You can ignore this error for now, I'll find a way to skip memsticks/Flash next update.