[PLUGIN] Disk Location

[LordVader]

Hello,
I'm having this problem with Disk Location.
Both of my nvme cache drives, the manufacturer is not recognized.

I had a pair of Samsung before and I had to replace them.
Now, I can see the model but the manufacturer info is missing (Crucial Drives)
What can I do to force recognition of the manufacturer ?

[FlamongOle]

1 hour ago, LordVader said:

Hello,
I'm having this problem with Disk Location.
Both of my nvme cache drives, the manufacturer is not recognized.

I had a pair of Samsung before and I had to replace them.
Now, I can see the model but the manufacturer info is missing (Crucial Drives)
What can I do to force recognition of the manufacturer ?

No way to force it, just wait for an updated smartmontools to arrive with that info. Maybe next version has it, maybe it won't be added, it's out of my control.

 

You can obviously add that info manually to the database, but next time it updates it will be overwritten again, so no point in that either.

[LordVader]

Thank you for the info.

[FlamongOle]

Update 2024.07.25

• Commit #315 - BUG: Export TSV did not export the list as intended.

 

Update 2024.07.26

• Commit #319 - MINOR: ZFS Hot Spares status was not recognized.
• Commit #318 - FEATURE: Possible to download TSV with RAW data (exception for the units read and written which is already calculated from the logical block size, it will show the actual bytes read and written).
   

Edited July 25 by FlamongOle

[cinereus]

The plugin is saying my drive contents are being emulated (i.e. disk is buggered) even though unraid itself doesn't say this:

 

 

 

What's going on? Do I need to be worried about this disk?

[FlamongOle]

On 7/28/2024 at 4:51 AM, cinereus said:

The plugin is saying my drive contents are being emulated (i.e. disk is buggered) even though unraid itself doesn't say this:

 

What's going on? Do I need to be worried about this disk?

Do a "force update all" and check again. If it's still says it's failing, you might need to look more into the drive. Can be a plugin bug, can be something delayed, can be something unsupported somehow.. there's possibilities. You might send in diagnostics to the unraid guys if it persists (not here). Hopefully you find out about it. Feel free to comment back about it in case I must look more into this later, but that will be after my vacation -- starting now!

[edival]

Hi, I was a dumb-ass and clicked before reading and understanding, and now I've hidden a drive in Disk Location, permanently.

I assumed the — in History would undo/move it back to where I could re-add it to my drives. It hid it permanently.

 

I saw you mention that it's a manual task that needs to be done in the database, which is fine, I'm comfortable working in the database but

1) I have zero clue where to access the Unraid database

2) I have no idea where to access that drive and switch the hidden flag.

 

Can you help?

[FlamongOle]

On 8/16/2024 at 5:07 PM, edival said:

Hi, I was a dumb-ass and clicked before reading and understanding, and now I've hidden a drive in Disk Location, permanently.

I assumed the — in History would undo/move it back to where I could re-add it to my drives. It hid it permanently.

 

I saw you mention that it's a manual task that needs to be done in the database, which is fine, I'm comfortable working in the database but

1) I have zero clue where to access the Unraid database

2) I have no idea where to access that drive and switch the hidden flag.

 

Can you help?

 

EDIT:

Did you check and try the "Undelete all devices" under "System"? Would be my first thing, before "Force update all". If you don't see that button, then likely it's not in the database at all and are lost forever.

 

Original answer:

After removing it from the "History" under "Tray Allocations", a "Force update all" should bring it back as long as the drive is still in the system. If it is in fact a history drive, you might need to do a manual database task, unless you can use a backup (if you have). Backup the current one before restoring an old one or fiddling with it manually.

 

You can enter database by, in terminal:

sqlite3 /boot/config/plugins/disklocation/disklocation.sqlite

 

Then enter this to find your drive:

select id,device,model_name,smart_serialnumber,status from disks;

 

When you have identified your drive, type:

update disks SET status='' WHERE id=<ID OF THE DRIVE>;
  eg.
update disks SET status='' WHERE id=23;

 

End the SQL with

.quit

 

After this, do a "Force update all" and fix the drive as you intend, unless it fixes itself. 

Edited August 29 by FlamongOle
Added another answer

[berrybites]

When I add some drives to a tray allocation, it crashes the gui for the disk location and the gui for the unraid dashboard until i uninstall the plugin and remove the disklocation directory in boot/config/plugins. The specific drives that cause this issue are old seagate drives. All other drives add nicely. Ive tested this to be sure, and have added the drives in multiple different orders to the tray allocation (uninstalling the plugin and removing directory each time), and it only fails when either of the two seagate drives are added. Any assistance in fixing this issue would be much appreciated! Ive attached images of the existing drive structure and the failed images.

[berrybites]

On 8/19/2024 at 12:22 PM, berrybites said:

When I add some drives to a tray allocation, it crashes the gui for the disk location and the gui for the unraid dashboard until i uninstall the plugin and remove the disklocation directory in boot/config/plugins. The specific drives that cause this issue are old seagate drives. All other drives add nicely. Ive tested this to be sure, and have added the drives in multiple different orders to the tray allocation (uninstalling the plugin and removing directory each time), and it only fails when either of the two seagate drives are added. Any assistance in fixing this issue would be much appreciated! Ive attached images of the existing drive structure and the failed images.

 

 

 

 

Okay, i think i made progress, but still cant add drives. Both seagate drives are older drives and have been powered on for about 65850hours each, which is more than the 2 byte value maximum of 65536 (2^16) that i believe is causing this issue. So for very old drives, i bet you will see this type of behavior. My theory is there is an overflow issue causing this. I dont have a fix, but maybe increasing the value to 4 bytes for drive power on hours, that could fix this.

 

I noticed an overflow in the Scrutiny docker that was giving me 94584 years for the drive power on age. So maybe same issue is happening here. When running

'''smartctl -a /dev/sde''',

i get

'''9 Power_On_Hours          0x0032   025   025   000    Old_age   Always       -       65850''' .

Edited August 24 by berrybites

[FlamongOle]

On 8/24/2024 at 6:49 PM, berrybites said:

Okay, i think i made progress, but still cant add drives. Both seagate drives are older drives and have been powered on for about 65850hours each, which is more than the 2 byte value maximum of 65536 (2^16) that i believe is causing this issue. So for very old drives, i bet you will see this type of behavior. My theory is there is an overflow issue causing this. I dont have a fix, but maybe increasing the value to 4 bytes for drive power on hours, that could fix this.

 

I noticed an overflow in the Scrutiny docker that was giving me 94584 years for the drive power on age. So maybe same issue is happening here. When running

'''smartctl -a /dev/sde''',

i get

'''9 Power_On_Hours          0x0032   025   025   000    Old_age   Always       -       65850''' .

As long as smartctl outputs something, Disk Location is quite agnostic to the numbers themselves. If it fails with smartmontools, then there's not much I can do.

 

What I find confusing here is that the drives in fact are already added to the database, it just fail being assigned for whatever reason. 

 

Please give the output of these to me:

sqlite3 /boot/config/plugins/disklocation/disklocation.sqlite "select * from disks WHERE model_name LIKE '%ST4000%';"
sqlite3 /boot/config/plugins/disklocation/disklocation.sqlite "select * from location;"
sqlite3 /boot/config/plugins/disklocation/disklocation.sqlite "select * from settings_group;"

 

Run this, it will create a TXT file that you can send to me (one drive is enough):

smartctl -x --all --json /dev/sdb > /tmp/dl_debug_sdb.txt

You might want to choose another output location if you want to grab the file easier, like somewhere on you array.

 

[berrybites]

On 8/29/2024 at 4:36 PM, FlamongOle said:

As long as smartctl outputs something, Disk Location is quite agnostic to the numbers themselves. If it fails with smartmontools, then there's not much I can do.

 

What I find confusing here is that the drives in fact are already added to the database, it just fail being assigned for whatever reason. 

 

Please give the output of these to me:

sqlite3 /boot/config/plugins/disklocation/disklocation.sqlite "select * from disks WHERE model_name LIKE '%ST4000%';"
sqlite3 /boot/config/plugins/disklocation/disklocation.sqlite "select * from location;"
sqlite3 /boot/config/plugins/disklocation/disklocation.sqlite "select * from settings_group;"

 

Run this, it will create a TXT file that you can send to me (one drive is enough):

smartctl -x --all --json /dev/sdb > /tmp/dl_debug_sdb.txt

You might want to choose another output location if you want to grab the file easier, like somewhere on you array.

 

Here is the output. Text file is attached. Gui failed after allocating all drives (specifically the seagate ones)

 

Before allocating any drives:

sqlite3 /boot/config/plugins/disklocation/disklocation.sqlite "select * from disks WHERE model_name LIKE '%ST4000%';"

1|1:0:0:0|sdb|5 3152 1952939168|Seagate Constellation ES.3|ST4000NM0033-9ZM170|1|S1Z02RXX|38|829121594|273|4000787030016|128|7200|3.5 inches|0|0|0|0|0|512||||||h|||||||||||7188dcf85b0bf9bc5eb9e75e35611f911d8b2b9a9b8fe8672bc78f34a520a769

4|4:0:0:0|sde|5 3152 1702654746|Seagate Constellation ES.3|ST4000NM0033-9ZM170|1|Z1Z2N1B1|37|829121404|250|4000787030016|128|7200|3.5 inches|0|0|0|0|0|512||||||h|||||||||||7a031baba6459e6253cd96f09039e75606346675d18fb0d38def5b7e178a19a6

sqlite3 /boot/config/plugins/disklocation/disklocation.sqlite "select * from location;"

(no output)

sqlite3 /boot/config/plugins/disklocation/disklocation.sqlite "select * from settings_group;"

1|array||column|1|8||h|1|1|400|70

2|cache||column|1|1||h|1|1|400|70

 

After allocating all drives (gui fails again):

sqlite3 /boot/config/plugins/disklocation/disklocation.sqlite "select * from disks WHERE model_name LIKE '%ST4000%';"

1|1:0:0:0|sdb|5 3152 1952939168|Seagate Constellation ES.3|ST4000NM0033-9ZM170|1|S1Z02RXX|38|829121594|273|4000787030016|128|7200|3.5 inches|0|0|0|0|0|512|||||||||||||||||7188dcf85b0bf9bc5eb9e75e35611f911d8b2b9a9b8fe8672bc78f34a520a769

4|4:0:0:0|sde|5 3152 1702654746|Seagate Constellation ES.3|ST4000NM0033-9ZM170|1|Z1Z2N1B1|37|829121404|250|4000787030016|128|7200|3.5 inches|0|0|0|0|0|512|||||||||||||||||7a031baba6459e6253cd96f09039e75606346675d18fb0d38def5b7e178a19a6

sqlite3 /boot/config/plugins/disklocation/disklocation.sqlite "select * from location;"

1|1|7188dcf85b0bf9bc5eb9e75e35611f911d8b2b9a9b8fe8672bc78f34a520a769||8

2|1|c34571068a6a2d7be41c5bb8be58f37e4890ccb5e35ac06b745f203eb4b14fe1||7

3|1|79133b9e7b461340c118613acbcc2a7a3da02f40c0174009cd35c59036c571e3||6

4|1|7a031baba6459e6253cd96f09039e75606346675d18fb0d38def5b7e178a19a6||5

5|1|b3e9e72973cf742fee821f8285d22cbce24df1034637fcde4c658c12a8c6b879||4

6|1|e8c9327e867ee3825211a07aa7678ea9d87fd5d0c84af112308ab1487dcd7732||3

7|1|8fe46dbc1ddaa0e5ba2506df07975db8806fed69f75815070730e523ec6f9880||1

8|2|704631c8ba99efd8c0a8992db9d730781e8757956639e975119a545d7f0e6939||1

sqlite3 /boot/config/plugins/disklocation/disklocation.sqlite "select * from settings_group;"

1|array||column|1|8||h|1|1|400|70

2|cache||column|1|1||h|1|1|400|70

 

 

 

Thanks again for any help!

dl_debug_sdb.txt

[FlamongOle]

14 hours ago, berrybites said:

Here is the output. Text file is attached. Gui failed after allocating all drives (specifically the seagate ones)

 

I still can't see why this would fail, everything seems to be in order and added as they should. Even after GUI fails.

 

I think I might need to see a PHP debug:

1) go to Tools -> PHP Settings

2) clear the logs if it contains anything

3) set Error Reporting to "All categories" and "apply"

4) go to Disk Location and setup the drives that fails

5) when GUI fails to load (wait 1 minute or so), delete the database/plugin folder

6) go back to Tools -> PHP Settings

7) view the log and attach it here (check for sensitive data before posting).

8.) set error reporting to "default" and "apply"

 

[Actane727]

My unassigned drive is showing as not present and no SMART data. Not sure what to do. 

[FlamongOle]

5 hours ago, Actane727 said:

My unassigned drive is showing as not present and no SMART data. Not sure what to do. 

Some SMART data is there. What did you try to do?

[Elbinho]

Is there a way to acknowledge a smart warning and have the plugin return to green for that drive?

 

I have a used disk with 2 reported uncorrectable errors, which is why I got it for free. Those errors happened a few thousand runtime hours ago, and since then the drive is operating without a hitch. For the normal Unraid interface, I can just acknowledge the errors, and Unraid will show me a green thumbs up.

 

The only option I found in Disk Location, would be to raise my general limit for UECC, but I don't want to do that for all of my drives, just this one drive

Edited Wednesday at 10:22 AM by Elbinho

[FlamongOle]

1 hour ago, Elbinho said:

Is there a way to acknowledge a smart warning and have the plugin return to green for that drive?

 

I have a used disk with 2 reported uncorrectable errors, which is why I got it for free. Those errors happened a few thousand runtime hours ago, and since then the drive is operating without a hitch. For the normal Unraid interface, I can just acknowledge the errors, and Unraid will show me a green thumbs up.

 

The only option I found in Disk Location, would be to raise my general limit for UECC, but I don't want to do that for all of my drives, just this one drive

Not currently, no

[Actane727]

9 hours ago, FlamongOle said:

Some SMART data is there. What did you try to do?

Just verify no errors on disk and that SMART info is being read outside of plug-in. Then tried to update devices in plug-in a couple times.