Unraid: 6.12.10

Disk Location: 2025.05.25

2 things I am noticing when I looked at this today:

My 'Layout' starts like this:

But if I save the 2.5" Drives then it ends up as 2.5" Drives :

On the 'Tray Allocations' tab, the tray dropdown is empty for all of my drives (for both groups):

And when I try and assign that 'Unassigned' disk to the 2.5" group and click save, it just ends up removing all of my assignments (presumably because the 'Tray' is blank for all of them maybe?):

5 hours ago, devalias said:

Unraid: 6.12.10

Disk Location: 2025.05.25

2 things I am noticing when I looked at this today:

My 'Layout' starts like this:

But if I save the 2.5" Drives then it ends up as 2.5" Drives :

On the 'Tray Allocations' tab, the tray dropdown is empty for all of my drives (for both groups):

And when I try and assign that 'Unassigned' disk to the 2.5" group and click save, it just ends up removing all of my assignments (presumably because the 'Tray' is blank for all of them maybe?):

Haha, whoops!

This likely happens that you have hidden numbers on the trays, and why underneath it can't connect TrayID with Physical tray number :P I didn't have that in my mind, but it should probably be easy to fix.

The 2.5" problem seems to be catching on a htmlspecialchars/htmlentities loop where it tries to format itself. This should be easy enough to fix as well. But I believe the name will extend every time you save it with additonal "amp;".

Update 2025.05.26

• Commit #438 - MINOR: htmlspecialchars duplicate where it tries to format itself in the group names. Removed htmlspecialchars from the variable to be stored in json array, it's not needed as it is read by htmlspecialchars.

• Commit #437 - BUG: Assigning not working and deletes all assigned devices if tray numbers are hidden. Added bypassed variables to the array instead of variables that were unset.

@devalias should be fixed now :)

@FlamongOle I hope you dont mind my @ you.

I am having this issue. the plugin and dashboard was working and then at an unknown time the dashboard failed and now always presents this message - Go to Disk Location -> System and initialize a "Force SMART+DB"

I have tried to follow the instructions you suggested in this post and i see content in the temp dir. I have tried to restart, re-install, delete all backups. Nothing seems to fix it.

I have attached the debug file and devices.json to see if you can help me troubleshoot it.

On 4/27/2025 at 8:18 AM, FlamongOle said:

 

Do you see any files under /tmp/disklocation ? If there's no files, then there might be a write permission issue (should typically not happen, a reboot might solve that as /tmp is recreated every boot)

 

You can check if the nvme drive was seen by the SMART+DB by typing in the terminal:

cat /tmp/disklocation/cron_smart.log

 

then check if it generated a file under smart:

ls /tmp/disklocation/smart/

Feel free to open the file and see if it has any real content (serial number and model name is the most important info)

 

You can manually just delete the disklocation temp folder and run "SMART+DB" again in case there's some corruption involved:

rm -rf /tmp/disklocation

 

 

If nothing above help, try to reset the devices under "System", scroll to the bottom, select "devices" and reset. Then do SMART+DB again.

Otherwise check for Disk Location contents in the PHP log under Unraid Tools. Debugging data might help me as well, but then you must enable debugging, run SMART+DB, disable debugging, then send the file to me, but this is the last thing you should do.

disklocation-2025-05-26.log devices.json

51 minutes ago, grupoleon said:

@FlamongOle I hope you dont mind my @ you.

I am having this issue. the plugin and dashboard was working and then at an unknown time the dashboard failed and now always presents this message - Go to Disk Location -> System and initialize a "Force SMART+DB"

I have tried to follow the instructions you suggested in this post and i see content in the temp dir. I have tried to restart, re-install, delete all backups. Nothing seems to fix it.

I have attached the debug file and devices.json to see if you can help me troubleshoot it.

disklocation-2025-05-26.log devices.json

From what I can see in the logs, disk3 and disk22 is listed but does not have serial number and name, and thus will be missing an ID. Do you know what these are? Is it a controller of some sorts, is it a dead one, CD-drives, is it mapped drives from proxmox?

I have a CD-drive in mine as well, which causes no troubles.

I can probably fix this issue with ignoring empty inputs (which I though I already had). But would be nice to know if you know what this is.

Update 2025.05.26b

• Commit #440 - BUG: Devices with no serial numbers can create an empty array and cause the plugin to crash. Made adjustments into cronjob, deleting "devices" and running Force SMART+DB required afterwards.

• Commit #438 - MINOR: htmlspecialchars duplicate where it tries to format itself in the group names. Removed htmlspecialchars from the variable to be stored in json array, it's not needed as it is read by htmlspecialchars.

• Commit #437 - BUG: Assigning not working and deletes all assigned devices if tray numbers are hidden. Added bypassed variables to the array instead of variables that were unset.

@grupoleon you can try this. You must likely delete "devices" then run Force SMART+DB afterwards. You should be able to access it via "Disk Location - Recovery" page under Tools. Go to "Reset plugin", select "devices" then "Reset", then do Force SMART+DB.

3 hours ago, FlamongOle said:

From what I can see in the logs, disk3 and disk22 is listed but does not have serial number and name, and thus will be missing an ID. Do you know what these are? Is it a controller of some sorts, is it a dead one, CD-drives, is it mapped drives from proxmox?

I have a CD-drive in mine as well, which causes no troubles.

I can probably fix this issue with ignoring empty inputs (which I though I already had). But would be nice to know if you know what this is.

This is making some sense. I recently reduced the size of the array. this could've caused the issue.

I don't have CDs. My array has 2 parity, 1 cache, 21 HDDs. However as stated I reduced the array and so disk3 is the one currently unassigned (see images.)

As it happens I am now re-adding the drive and i'll report back.

Edited May 26, 20251 yr by grupoleon

11 hours ago, FlamongOle said:

From what I can see in the logs, disk3 and disk22 is listed but does not have serial number and name, and thus will be missing an ID. Do you know what these are? Is it a controller of some sorts, is it a dead one, CD-drives, is it mapped drives from proxmox?

I have a CD-drive in mine as well, which causes no troubles.

I can probably fix this issue with ignoring empty inputs (which I though I already had). But would be nice to know if you know what this is.

tried rebooting unraid, deleting and wiping all data, re-installing app. Nothing clears that dashboard error.

disklocation-2025-05-26(1).log

20 hours ago, FlamongOle said:

This likely happens that you have hidden numbers on the trays, and why underneath it can't connect TrayID with Physical tray number :P I didn't have that in my mind, but it should probably be easy to fix.

The 2.5" problem seems to be catching on a htmlspecialchars/htmlentities loop where it tries to format itself. This should be easy enough to fix as well. But I believe the name will extend every time you save it with additonal "amp;".

14 hours ago, FlamongOle said:

Update 2025.05.26b

@FlamongOle Thanks for looking into that and pushing a fix! I can confirm that both issues I reported seem to no longer be present after updating to 2025.05.26b 🎉

7 hours ago, zdzosel said:

[23-May-2025 19:44:18 America/Chicago] PHP Fatal error: Uncaught TypeError: array_search(): Argument #2 ($haystack) must be of type array, null given in /usr/local/emhttp/plugins/disklocation/pages/system.php:280

Stack trace:

#0 /usr/local/emhttp/plugins/disklocation/pages/system.php(280): array_search('', NULL)

#1 /usr/local/emhttp/plugins/dynamix/include/DefaultPageLayout.php(854) : eval()'d code(11): require_once('/usr/local/emht...')

#2 /usr/local/emhttp/plugins/dynamix/include/DefaultPageLayout.php(854): eval()

#3 /usr/local/emhttp/plugins/dynamix/template.php(94): require_once('/usr/local/emht...')

#4 {main}

thrown in /usr/local/emhttp/plugins/disklocation/pages/system.php on line 280

I just set this up from scratch

3 hours ago, grupoleon said:

tried rebooting unraid, deleting and wiping all data, re-installing app. Nothing clears that dashboard error.

disklocation-2025-05-26(1).log

Any disk location related errors in the PHP log?

6 hours ago, FlamongOle said:

Any disk location related errors in the PHP log?

This is what the PHP log is throwing.

[27-May-2025 06:42:26 America/Chicago] PHP Fatal error: Uncaught TypeError: array_search(): Argument #2 ($haystack) must be of type array, null given in /usr/local/emhttp/plugins/disklocation/pages/system.php:280

Stack trace:

#0 /usr/local/emhttp/plugins/disklocation/pages/system.php(280): array_search('1', NULL)

#1 /usr/local/emhttp/plugins/dynamix/include/DefaultPageLayout.php(863) : eval()'d code(11): require_once('/usr/local/emht...')

#2 /usr/local/emhttp/plugins/dynamix/include/DefaultPageLayout.php(863): eval()

#3 /usr/local/emhttp/plugins/dynamix/template.php(94): require_once('/usr/local/emht...')

#4 {main}

thrown in /usr/local/emhttp/plugins/disklocation/pages/system.php on line 280

[27-May-2025 06:42:36 America/Chicago] PHP Fatal error: Uncaught TypeError: array_search(): Argument #2 ($haystack) must be of type array, null given in /usr/local/emhttp/plugins/disklocation/pages/system.php:280

Stack trace:

#0 /usr/local/emhttp/plugins/disklocation/pages/system.php(280): array_search('1', NULL)

#1 /usr/local/emhttp/plugins/dynamix/include/DefaultPageLayout.php(863) : eval()'d code(11): require_once('/usr/local/emht...')

#2 /usr/local/emhttp/plugins/dynamix/include/DefaultPageLayout.php(863): eval()

#3 /usr/local/emhttp/plugins/dynamix/template.php(94): require_once('/usr/local/emht...')

#4 {main}

thrown in /usr/local/emhttp/plugins/disklocation/pages/system.php on line 280

[27-May-2025 06:43:02 America/Chicago] PHP Fatal error: Uncaught TypeError: array_search(): Argument #2 ($haystack) must be of type array, null given in /usr/local/emhttp/plugins/disklocation/pages/system.php:280

Stack trace:

#0 /usr/local/emhttp/plugins/disklocation/pages/system.php(280): array_search('1', NULL)

#1 /usr/local/emhttp/plugins/dynamix/include/DefaultPageLayout.php(863) : eval()'d code(11): require_once('/usr/local/emht...')

#2 /usr/local/emhttp/plugins/dynamix/include/DefaultPageLayout.php(863): eval()

#3 /usr/local/emhttp/plugins/dynamix/template.php(94): require_once('/usr/local/emht...')

#4 {main}

thrown in /usr/local/emhttp/plugins/disklocation/pages/system.php on line 280

[27-May-2025 06:48:03 America/Chicago] PHP Warning: Undefined array key "Description" in /usr/local/emhttp/plugins/community.applications/include/helpers.php on line 267

[27-May-2025 06:48:03 America/Chicago] PHP Deprecated: preg_match(): Passing null to parameter #2 ($subject) of type string is deprecated in /usr/local/emhttp/plugins/community.applications/include/helpers.php on line 267

Update 2025.05.27

• Commit #432 - BUG: Further enhancements for checking arrays and variables.

@grupoleon try this update, at least it should get rid of the PHP errors above. You might need to reset "devices" and do Force SMART+DB afterwards.

13 minutes ago, FlamongOle said:

Update 2025.05.27

• Commit #432 - BUG: Further enhancements for checking arrays and variables.

@grupoleon try this update, at least it should get rid of the PHP errors above. You might need to reset "devices" and do Force SMART+DB afterwards.

Thank you for such attention. unfortunately it still has not removed the alert on the dashboard.

I updated the app. wiped all data. went through set up process with no success.

PHP error log
[27-May-2025 07:42:52 America/Chicago] PHP Warning: Undefined array key "backup_file_list" in /usr/local/emhttp/plugins/disklocation/pages/page_system.php on line 354

[27-May-2025 07:42:52 America/Chicago] PHP Deprecated: file_exists(): Passing null to parameter #1 ($filename) of type string is deprecated in /usr/local/emhttp/plugins/disklocation/pages/page_system.php on line 259

Not sure if this helps but when I run a check on the seagate HDDs several don't have poweron time. would this cause the issue (see image)

Attached is also the latest log file

Thank you again!

disklocation-2025-05-27(1).log

11 minutes ago, grupoleon said:

Thank you for such attention. unfortunately it still has not removed the alert on the dashboard.

I updated the app. wiped all data. went through set up process with no success.

PHP error log
[27-May-2025 07:42:52 America/Chicago] PHP Warning: Undefined array key "backup_file_list" in /usr/local/emhttp/plugins/disklocation/pages/page_system.php on line 354

[27-May-2025 07:42:52 America/Chicago] PHP Deprecated: file_exists(): Passing null to parameter #1 ($filename) of type string is deprecated in /usr/local/emhttp/plugins/disklocation/pages/page_system.php on line 259

Not sure if this helps but when I run a check on the seagate HDDs several don't have poweron time. would this cause the issue (see image)

Attached is also the latest log file

Thank you again!

disklocation-2025-05-27(1).log

Nah, that script is an entire separate thing.

What do you get if you type:

ls /tmp/disklocation/smart/

and

cat /tmp/disklocation/powermode.json

13 minutes ago, FlamongOle said:

Nah, that script is an entire separate thing.

What do you get if you type:

ls /tmp/disklocation/smart/

and

cat /tmp/disklocation/powermode.json

ls /tmp/disklocation/smart/
ST3000VN000-1HJ166_W6A145X3.json ST4000VN008-2DR166_ZDH5QQ0L.json ST6000VN001-2BB186_ZR15J46R.json

ST4000DM000-1F2168_W300CA87.json ST4000VN008-2DR166_ZGY3R3TK.json ST6000VN001-2BB186_ZSC0529F.json

ST4000VN000-2AH166_WDH0XAGB.json ST4000VN008-2DR166_ZGY3Y5BC.json ST6000VN0033-2EE110_ZAD9CMHG.json

ST4000VN008-2DR166_ZDH467P3.json ST4000VN008-2DR166_ZM404FQ1.json ST6000VN0033-2EE110_ZAD9CV9S.json

ST4000VN008-2DR166_ZDH490PY.json ST4000VX000-1F4168_Z306QHG4.json ST6000VN0033-2EE110_ZADABWH9.json

ST4000VN008-2DR166_ZDH4A71P.json ST6000VN001-2BB186_ZR10EE6B.json ST6000VN006-2ZM186_ZPV02C47.json

ST4000VN008-2DR166_ZDH4P7VS.json ST6000VN001-2BB186_ZR14NF8B.json TOSHIBA_HDWG460_7190A02MFR1H.json

ST4000VN008-2DR166_ZDH5QLYQ.json ST6000VN001-2BB186_ZR150H65.json WD_Blue_SA510_2.5_1000GB_23450W800709.json


cat /tmp/disklocation/powermode.json
{

"0:0:0:0": "UNKNOWN",

"16:0:0:0": "ACTIVE",

"36:0:0:0": "ACTIVE",

"36:0:1:0": "ACTIVE",

"36:0:2:0": "ACTIVE",

"36:0:3:0": "ACTIVE",

"36:0:4:0": "IDLE",

"36:0:5:0": "IDLE",

"36:0:6:0": "ACTIVE",

"36:0:7:0": "ACTIVE",

"36:0:8:0": "ACTIVE",

"36:0:9:0": "ACTIVE",

"36:0:10:0": "ACTIVE",

"36:0:11:0": "IDLE",

"36:0:12:0": "ACTIVE",

"36:0:13:0": "IDLE",

"36:0:14:0": "ACTIVE",

"36:0:15:0": "ACTIVE",

"36:0:16:0": "ACTIVE",

"36:0:17:0": "ACTIVE",

"36:0:18:0": "IDLE",

"36:0:19:0": "ACTIVE",

"36:0:20:0": "ACTIVE",

"36:0:21:0": "ACTIVE",

"36:0:22:0": "ACTIVE",

"36:0:23:0": "ACTIVE"

}

4 minutes ago, grupoleon said:

ls /tmp/disklocation/smart/
ST3000VN000-1HJ166_W6A145X3.json ST4000VN008-2DR166_ZDH5QQ0L.json ST6000VN001-2BB186_ZR15J46R.json

ST4000DM000-1F2168_W300CA87.json ST4000VN008-2DR166_ZGY3R3TK.json ST6000VN001-2BB186_ZSC0529F.json

ST4000VN000-2AH166_WDH0XAGB.json ST4000VN008-2DR166_ZGY3Y5BC.json ST6000VN0033-2EE110_ZAD9CMHG.json

ST4000VN008-2DR166_ZDH467P3.json ST4000VN008-2DR166_ZM404FQ1.json ST6000VN0033-2EE110_ZAD9CV9S.json

ST4000VN008-2DR166_ZDH490PY.json ST4000VX000-1F4168_Z306QHG4.json ST6000VN0033-2EE110_ZADABWH9.json

ST4000VN008-2DR166_ZDH4A71P.json ST6000VN001-2BB186_ZR10EE6B.json ST6000VN006-2ZM186_ZPV02C47.json

ST4000VN008-2DR166_ZDH4P7VS.json ST6000VN001-2BB186_ZR14NF8B.json TOSHIBA_HDWG460_7190A02MFR1H.json

ST4000VN008-2DR166_ZDH5QLYQ.json ST6000VN001-2BB186_ZR150H65.json WD_Blue_SA510_2.5_1000GB_23450W800709.json


cat /tmp/disklocation/powermode.json
{

"0:0:0:0": "UNKNOWN",

"16:0:0:0": "ACTIVE",

"36:0:0:0": "ACTIVE",

"36:0:1:0": "ACTIVE",

"36:0:2:0": "ACTIVE",

"36:0:3:0": "ACTIVE",

"36:0:4:0": "IDLE",

"36:0:5:0": "IDLE",

"36:0:6:0": "ACTIVE",

"36:0:7:0": "ACTIVE",

"36:0:8:0": "ACTIVE",

"36:0:9:0": "ACTIVE",

"36:0:10:0": "ACTIVE",

"36:0:11:0": "IDLE",

"36:0:12:0": "ACTIVE",

"36:0:13:0": "IDLE",

"36:0:14:0": "ACTIVE",

"36:0:15:0": "ACTIVE",

"36:0:16:0": "ACTIVE",

"36:0:17:0": "ACTIVE",

"36:0:18:0": "IDLE",

"36:0:19:0": "ACTIVE",

"36:0:20:0": "ACTIVE",

"36:0:21:0": "ACTIVE",

"36:0:22:0": "ACTIVE",

"36:0:23:0": "ACTIVE"

}

I am mostly curious of what 16:0:0:0 (possibly still "sdb") is. I'm not sure if it's related, but it the only thing that doesn't make any sense here for me. It's detected as ACTIVE, but yet give no serial number.

What happens if you do a

lsscsi -bg | grep "16:0:0:0"

Insert /dev/sdX from above, eg.:
smartctl -x --all /dev/sdb

10 minutes ago, FlamongOle said:

I am mostly curious of what 16:0:0:0 (possibly still "sdb") is. I'm not sure if it's related, but it the only thing that doesn't make any sense here for me. It's detected as ACTIVE, but yet give no serial number.

What happens if you do a

lsscsi -bg | grep "16:0:0:0"

Insert /dev/sdX from above, eg.:
smartctl -x --all /dev/sdb

lsscsi -bg | grep "16:0:0:0"
[16:0:0:0] /dev/sdb /dev/sg1

Insert /dev/sdX from above, eg.:

smartctl -x --all /dev/sdb
bash: Insert: command not found

smartctl 7.4 2023-08-01 r5530 [x86_64-linux-6.12.24-Unraid] (local build)

Copyright (C) 2002-23, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===

Vendor: VMware

Product: Virtual disk

Revision: 2.0

Compliance: SPC-4

User Capacity: 33,554,432 bytes [33.5 MB]

Logical block size: 512 bytes

LU is thin provisioned, LBPRZ=1

Rotation Rate: Solid State Device

Device type: disk

Local Time is: Tue May 27 08:45:36 2025 CDT

SMART support is: Unavailable - device lacks SMART capability.

Read Cache is: Unavailable

Writeback Cache is: Unavailable

=== START OF READ SMART DATA SECTION ===

Current Drive Temperature: 0 C

Drive Trip Temperature: 0 C

Error Counter logging not supported

Device does not support Self Test logging

Device does not support Background scan results logging

Device does not support General statistics and performance logging

15 minutes ago, grupoleon said:

lsscsi -bg | grep "16:0:0:0"
[16:0:0:0] /dev/sdb /dev/sg1

Insert /dev/sdX from above, eg.:

smartctl -x --all /dev/sdb
bash: Insert: command not found

smartctl 7.4 2023-08-01 r5530 [x86_64-linux-6.12.24-Unraid] (local build)

Copyright (C) 2002-23, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===

Vendor: VMware

Product: Virtual disk

Revision: 2.0

Compliance: SPC-4

User Capacity: 33,554,432 bytes [33.5 MB]

Logical block size: 512 bytes

LU is thin provisioned, LBPRZ=1

Rotation Rate: Solid State Device

Device type: disk

Local Time is: Tue May 27 08:45:36 2025 CDT

SMART support is: Unavailable - device lacks SMART capability.

Read Cache is: Unavailable

Writeback Cache is: Unavailable

=== START OF READ SMART DATA SECTION ===

Current Drive Temperature: 0 C

Drive Trip Temperature: 0 C

Error Counter logging not supported

Device does not support Self Test logging

Device does not support Background scan results logging

Device does not support General statistics and performance logging

what is interesting int he tray allocation screen it finds them all, and displays them in the tray layout.

also if it's the SSD, then it's the cache drive and in the tray layout it finds it well enough.

33 minutes ago, grupoleon said:

what is interesting int he tray allocation screen it finds them all, and displays them in the tray layout.

also if it's the SSD, then it's the cache drive and in the tray layout it finds it well enough.

And if you click on "Dashboard" tab now?

4 hours ago, FlamongOle said:

And if you click on "Dashboard" tab now?

I shouuld've said that it's been this way.

I can assign drives, create groups and see table layout and locate the drives but the dashboard view will not change from from the "...force smart+db" message.

1 hour ago, grupoleon said:

I shouuld've said that it's been this way.

I can assign drives, create groups and see table layout and locate the drives but the dashboard view will not change from from the "...force smart+db" message.

I see what's going on now. It's indeed caused by the 16:0:0:0 virtual device. The problem is that smartctl recognize it as "ACTIVE", then it is cross-checked with the array of missing devices. If it find uneven amount of devices (those with serial numbers and those without) it will post that in the dashboard to warn about incomplete smart data fetch.

I need to find a way to ignore the false devices, likely force them to be "UNKNOWN" during powermode check.

@grupoleon Can you give me the entire output of

smartctl -n standby /dev/sdb

3 minutes ago, FlamongOle said:

@grupoleon Can you give me the entire output of

smartctl -n standby /dev/sdb

smartctl 7.4 2023-08-01 r5530 [x86_64-linux-6.12.24-Unraid] (local build)

Copyright (C) 2002-23, Bruce Allen, Christian Franke, www.smartmontools.org

Device is in ACTIVE mode

SCSI device successfully opened

Use 'smartctl -a' (or '-x') to print SMART (and more) information

Just now, grupoleon said:

smartctl 7.4 2023-08-01 r5530 [x86_64-linux-6.12.24-Unraid] (local build)

Copyright (C) 2002-23, Bruce Allen, Christian Franke, www.smartmontools.org

Device is in ACTIVE mode

SCSI device successfully opened

Use 'smartctl -a' (or '-x') to print SMART (and more) information

Damn. But thanks. I'll find a way to bypass the message. You don't need to delete anything anymore, it's all good under the hood. Just wait until next release some time tomorrow, hopefully.

Update 2025.05.28

• Commit #444 - BUG: Virtual drives causes dashboard issues due to missing SMART data. Made an ignore list for these devices to prevent slower SMART collecting.

• Commit #443 - MINOR: Undefined array key and Passing null to file_exists in page_system.

You can try this @grupoleon , I have not been able to test it, but a Force SMART is required after update. This should be updated every reboot etc., but can cause issues during hot swap (but very unlikely).