On 3/10/2026 at 7:43 AM, pete748 said:

I think I spoke too soon.

I don't know why this would continue to fail. It looks like all drives are spun down and this would be the reason why temps are not showing. I probably need a new debug file from this.

I added two drives (all other drives remained the same), and the entire "Define Case Layout" column no longer has my drives assigned.

Will this come back on it's own after the 2 new drives are formatted (disk clear is in progress) or do I need to do something else to restore the config? The two new drives are currently formatting (20+ hours and counting)

Edited April 28Apr 28 by xantari

9 hours ago, xantari said:

I added two drives (all other drives remained the same), and the entire "Define Case Layout" column no longer has my drives assigned.

Will this come back on it's own after the 2 new drives are formatted (disk clear is in progress) or do I need to do something else to restore the config? The two new drives are currently formatting (20+ hours and counting)

New drives must be added under "Tray Allocations", after they are added and saved, they should not dissappear. Doesn't matter what content is on the disks, it only care about the hardware itself.

On 4/17/2026 at 6:07 AM, FlamongOle said:

I can't replicate this, so need a debug file in that case. Make sure the drives are not in standby mode, then temps are not monitored. It does not use same data as Unraid, but probes itself.

Any specific controllers used for drives?

It is going through an LSI controller, but I'm not sure which specific drives are connected to that and which are connected directly to the mainboard. I believe that the array drives are connected through the mainboard. That being said, it appears that all devices across both servers are now properly updating.

Might have been fixed in a recent update?

Thanks!

On 4/17/2026 at 8:29 AM, FlamongOle said:

@Free Man The colors goes in this priority:

disk > group > common

If "disk" has a custom color, then it will override both "group" and "common", regardless what the others are set to. If "group" has a custom color but "disk" doesn't, "group" color will be chosen over "common"

To reset color per disk or group, the "common empty color" should be used to reset. That is whatever the "empty" color is specified as, not the original Disk Location color, unless if that's being used.

Took me about as long to note your reply as it did you to note my post, so I'd say we're even. 😀

Thanks for the info. I'll try to remember that the next time I have an "issue" with DiskLocation. Note that issue is in quotes because I don't think I've had any other than of my own doing.

I had a problem with one my SATA cables so I got a few UDMA CRC errors, all the errors got acknowledged in Unraid but 1 SSD is reporting not as acknowledged in Disk Locations.
How can I fix this?
I deleted everything already from Disk Locations and configured it again but sadly it doesn't work.

On 5/9/2026 at 9:52 AM, Runaljod said:

I had a problem with one my SATA cables so I got a few UDMA CRC errors, all the errors got acknowledged in Unraid but 1 SSD is reporting not as acknowledged in Disk Locations.
How can I fix this?
I deleted everything already from Disk Locations and configured it again but sadly it doesn't work.

These values are not stored within Disk Location, but in an Unraid file.

I would be interested in the debug file and your /var/local/emhttp/monitor.ini

You can also try to "Acknowledge all" under SMART if you enable "Allow editing of Unraid config" under Disk Location -> Configuration. Unless you already tried that.

18 hours ago, FlamongOle said:

These values are not stored within Disk Location, but in an Unraid file.

I would be interested in the debug file and your /var/local/emhttp/monitor.ini

You can also try to "Acknowledge all" under SMART if you enable "Allow editing of Unraid config" under Disk Location -> Configuration. Unless you already tried that.

I'm afraid I destroyed any "evidence" in the monitor.ini, I tried the "Acknowledge all" function and it's fixed now.
Is there still any point in sending the debug file and monitor.ini?

1 hour ago, Runaljod said:

I'm afraid I destroyed any "evidence" in the monitor.ini, I tried the "Acknowledge all" function and it's fixed now.
Is there still any point in sending the debug file and monitor.ini?

nope

But can you tell me what flash2 was? Usually "flash" is the Unraid USB memory, flash2 would then be like a mirror or so, or just another USB drive? Maybe you use Unraid 7.3 already with the system on disks instead?

Reason I ask is if flash2 is a typical device name in Unraid somehow, or if it's sort of "hidden" behind "flash" and that's why it didn't acknowledge it.

Ooh yeah, that makes sense for the full 100%.

I had an failing USB drive with Unraid OS so I had to migrate ASAP to the Internal Boot function in the beta (no worries, no prod or customers env).

Replaced the USB flash disk so it's only being used now for licensing.

Thanks for the help!

2 hours ago, FlamongOle said:

nope

But can you tell me what flash2 was? Usually "flash" is the Unraid USB memory, flash2 would then be like a mirror or so, or just another USB drive? Maybe you use Unraid 7.3 already with the system on disks instead?

Reason I ask is if flash2 is a typical device name in Unraid somehow, or if it's sort of "hidden" behind "flash" and that's why it didn't acknowledge it.

Flash and flash2 will be the drives in an internal mirrored boot pool.

SSD Box disk 3 = Boot data Pool , but has color is of unassigned disk , can be fixed or need plugin updates ?

On 5/14/2026 at 8:17 PM, Masterwishx said:

SSD Box disk 3 = Boot data Pool , but has color is of unassigned disk , can be fixed or need plugin updates ?

Use custom colors, no ETA on implementation yet.

Update 2026.05.23

• Commit #496 - FEATURE: Added Boot/Flash device support for Unraid 7.3.

  • "Temperature N/A" is renamed to "Standby" to clearify difference between "N/A" when in Heat Map view.

  • Adjusted table size for group name in Tray Allocations.

Custom colors must be reset to use the default colors, but that's optional. For split devices between flash/boot and other pools on the same disk, only the "Boot" is listed as the name.

i Just wanted to say thank you so much for this i downsized from 45 to 25 hdds because of the difficulty of locating the failing hdds and was about to again until i saw your plugin now i am able to swap a drive in 30 seconds 😁

Update 2026.06.02

• Commit #499 - MINOR: Incorrect power_on_hours value could occur. Declared more variables to prevent picking up invalid values.

On 2/19/2026 at 4:48 PM, pete748 said:

Hi team,

Is anyone else seeing an issue where most of their disks are marked as a SMART fail (Red in the dashboard), but when they go into the SMART detail,s it says passed?

I have been dealing with this issue for a while now. I believe this happens at least in my case because I have drives set to spin down after x minutes. Presumably, if SMART check happens right when the disk is about to spin down it flags as failed which is 'technically' true. But, much like you mentioned, running the test manually will spin up the drive and pass normally

8 hours ago, Lean_ said:

I have been dealing with this issue for a while now. I believe this happens at least in my case because I have drives set to spin down after x minutes. Presumably, if SMART check happens right when the disk is about to spin down it flags as failed which is 'technically' true. But, much like you mentioned, running the test manually will spin up the drive and pass normally

Can't do much without debugging file. I would also like a screenshot of your "Configuration" page please. I'm unable to reproduce this without any additional information.

On 6/4/2026 at 4:37 PM, FlamongOle said:

Can't do much without debugging file. I would also like a screenshot of your "Configuration" page please. I'm unable to reproduce this without any additional information.

disklocation-2026-06-05.log
Understood, Here you go. Disk8 is currently flashing but will actually pass SMART.

Edited June 8Jun 8 by Lean_

On 6/4/2026 at 4:37 PM, FlamongOle said:

Can't do much without debugging file. I would also like a screenshot of your "Configuration" page please. I'm unable to reproduce this without any additional information.

Just happened again with two other drives, here is an updated debug file. Hope this helps.
disklocation-2026-06-05 (1).log

On 6/6/2026 at 4:08 AM, Lean_ said:

Just happened again with two other drives, here is an updated debug file. Hope this helps.
disklocation-2026-06-05 (1).log

What does this output when you enter it in the terminal:

smartctl -x /dev/sdj | grep health

smartctl -x /dev/sdn | grep health

smartctl -x /dev/sdw | grep health

Edited June 7Jun 7 by FlamongOle

5 hours ago, FlamongOle said:

What does this output when you enter it in the terminal:

smartctl -x /dev/sdj | grep health

smartctl -x /dev/sdn | grep health

smartctl -x /dev/sdw | grep health

Sorry I am just seeing this.


They don't return anything, presumably because they are SAS drives? I'm also using an LSI HBA 9300 8i to a supermicro backplane.

sdx is a SATA drive that passes as expected.

5 minutes ago, Lean_ said:

Sorry I am just seeing this.


They don't return anything, presumably because they are SAS drives? I'm also using an LSI HBA 9300 8i to a supermicro backplane.

sdx is a SATA drive that passes as expected.

Have you tried with (or without) any of these settings:

-d TYPE, --device=TYPE

Specify device type to one of:

• ata, scsi[+TYPE], nvme[,NSID], sat[,auto][,N][+TYPE], usbasm1352r,N, usbcypress[,X], usbjmicron[,p][,x][,N], usbprolific, usbsunplus[/sat], sntasmedia[/sat], sntjmicron[,NSID [/sat], sntrealtek[/sat], jmb39x[-q[2]],N[,sLBA][,force][+TYPE], jms56x,N[,sLBA][,force][+TYPE], areca,N/E, 3ware,N, hpt,L/M/N, megaraid,N, aacraid,H,L,ID, sssraid,E,S, cciss,N, auto, test

These can be saved in each device in Unraid (click a disk name). Check SMART controller type if you figure out which device might work.

smartctl -H /dev/sd* should work too to give you a PASSED or FAILED (or nothing).

You might wanna try this first, but then try any other that might fit your controller (this is an example, dunno if it works):

smartctl -H -d sat,auto /dev/sdn

I might add a way to ignore empty SMART outputs, but I guess they should be retrievable with the correct setting.

Edited June 7Jun 7 by FlamongOle

1 minute ago, FlamongOle said:

Have you tried with (or without) any of these settings:

-d TYPE, --device=TYPE

Specify device type to one of:

• ata, scsi[+TYPE], nvme[,NSID], sat[,auto][,N][+TYPE], usbasm1352r,N, usbcypress[,X], usbjmicron[,p][,x][,N], usbprolific, usbsunplus[/sat], sntasmedia[/sat], sntjmicron[,NSID [/sat], sntrealtek[/sat], jmb39x[-q[2]],N[,sLBA][,force][+TYPE], jms56x,N[,sLBA][,force][+TYPE], areca,N/E, 3ware,N, hpt,L/M/N, megaraid,N, aacraid,H,L,ID, sssraid,E,S, cciss,N, auto, test

These can be saved in each device in Unraid (click a disk name). Check SMART controller type if you figure out which device might work.

smartctl -H /dev/sd* should work too to give you a PASSED or FAILED (or nothing).


I might add a way to ignore empty SMART outputs, but I guess they should be retrievable with the correct setting.

This does work. also "smartctl -x /dev/sdw -d scsi" provides ALL of the HDD info.


I just checked in unraid my SMART controller type was set to "use default". I should change all of the SAS drives to use "SCSI" or "Automatic" you think?

Edited June 7Jun 7 by Lean_

5 minutes ago, Lean_ said:

This does work. also "smartctl -x /dev/sdw -d scsi" provides ALL of the HDD info.

Then changing the "SMART controller type" to "SCSI" under device settings in Unraid should fix your issue. Is that set, or is it "default/auto"?