[PLUGIN] Disk Location


Recommended Posts

I just updated to the latest unRaid, and in turn, had to reinstall Disk Location.

It seemed to work ok, but I apparently only  have the "Devices" and "Information" tabs and can not configure anything.

On the top of the Information tab, I have an error:

Warning: A non-numeric value encountered in /usr/local/emhttp/plugins/disklocation/pages/info.php on line 107

Thoughts? Suggestions?

Link to comment
1 hour ago, jpotrz said:

I just updated to the latest unRaid, and in turn, had to reinstall Disk Location.

It seemed to work ok, but I apparently only  have the "Devices" and "Information" tabs and can not configure anything.

On the top of the Information tab, I have an error:


Warning: A non-numeric value encountered in /usr/local/emhttp/plugins/disklocation/pages/info.php on line 107

Thoughts? Suggestions?

Probably just an undefined variable, nothing to care about.

The configuration is now located under Unraid "Settings" tab, while the plugin view is under "Tools"

  • Like 1
Link to comment
8 minutes ago, olehj said:

Probably just an undefined variable, nothing to care about.

The configuration is now located under Unraid "Settings" tab, while the plugin view is under "Tools"

Excellent. Got it.

If I recall, there was a way now to set different drive orientation in the layout? like 8 vertical, 3 horizontal? 

Link to comment
1 minute ago, ijuarez said:

Deleted my DB and reassigned my colors but I notice with the last update my expander card showed up as a drive. Pretty cool

Sent from my SM-N960U using Tapatalk
 

Yes, this happens now because LUN is ignored when scanning through drives. Earlier it was used to detect if the drive was an actual drive, but some drives doesn't even have LUN's so it had to be removed. At least you can choose to show it or not 😛

Link to comment
16 hours ago, olehj said:

Yes, this happens now because LUN is ignored when scanning through drives. Earlier it was used to detect if the drive was an actual drive, but some drives doesn't even have LUN's so it had to be removed. At least you can choose to show it or not 😛

Awesome feature I think

  • Upvote 1
Link to comment

Hi, @olehj first thanks this great app, but I notice some problem after I install this app. I run LSI HBA with expander, array pool and cache pool was 2 different expander, and problem only at array pool, so problem may expander related but I am not sure.

 

Jul 23 19:47:43 X370 kernel: sd 7:0:8:0: Power-on or device reset occurred
Jul 23 19:48:15 X370 kernel: sd 7:0:8:0: Power-on or device reset occurred
Jul 23 19:48:47 X370 kernel: sd 7:0:8:0: Power-on or device reset occurred
Jul 23 19:49:19 X370 kernel: sd 7:0:9:0: Power-on or device reset occurred
Jul 23 19:49:51 X370 kernel: sd 7:0:9:0: Power-on or device reset occurred
Jul 23 19:50:23 X370 kernel: sd 7:0:9:0: Power-on or device reset occurred
Jul 23 19:51:23 X370 kernel: sd 7:0:8:0: Power-on or device reset occurred
Jul 23 19:51:55 X370 kernel: sd 7:0:8:0: Power-on or device reset occurred
Jul 23 19:52:27 X370 kernel: sd 7:0:8:0: Power-on or device reset occurred
Jul 23 19:52:59 X370 kernel: sd 7:0:9:0: Power-on or device reset occurred
Jul 23 19:53:31 X370 kernel: sd 7:0:9:0: Power-on or device reset occurred
Jul 23 19:54:03 X370 kernel: sd 7:0:9:0: Power-on or device reset occurred
Jul 23 20:10:03 X370 kernel: sd 7:0:7:0: Power-on or device reset occurred
Jul 23 20:10:35 X370 kernel: sd 7:0:7:0: Power-on or device reset occurred
Jul 23 20:11:07 X370 kernel: sd 7:0:7:0: Power-on or device reset occurred

 

The error would happen on every hours ~47min, further trace foud it is a hourly cron job at /etc/cron.hourly/disklocation.sh

 

Symptom will be if any of array disk in read or write will trigger it. If no disk in R/W then no problem.

 

Below are dmesg detail FYI, thanks

[ 1715.748840] sd 7:0:7:0: attempting task abort! scmd(00000000fe995705)
[ 1715.748844] sd 7:0:7:0: [sdi] tag#0 CDB: opcode=0x88 88 00 00 00 00 02 b3 48 e9 40 00 00 04 00 00 00
[ 1715.748846] scsi target7:0:7: handle(0x0011), sas_address(0x3474f4f5849ab507), phy(7)
[ 1715.748848] scsi target7:0:7: enclosure logical id(0x3474f4f5849ab51e), slot(7)
[ 1716.216232] sd 7:0:7:0: task abort: SUCCESS scmd(00000000fe995705)
[ 1716.965334] sd 7:0:7:0: Power-on or device reset occurred
[ 1747.492764] sd 7:0:7:0: attempting task abort! scmd(0000000054852aa3)
[ 1747.492768] sd 7:0:7:0: [sdi] tag#0 CDB: opcode=0x88 88 00 00 00 00 02 b3 49 19 40 00 00 04 00 00 00
[ 1747.492771] scsi target7:0:7: handle(0x0011), sas_address(0x3474f4f5849ab507), phy(7)
[ 1747.492772] scsi target7:0:7: enclosure logical id(0x3474f4f5849ab51e), slot(7)
[ 1747.967971] sd 7:0:7:0: task abort: SUCCESS scmd(0000000054852aa3)
[ 1748.717068] sd 7:0:7:0: Power-on or device reset occurred
[ 1779.748692] sd 7:0:7:0: attempting task abort! scmd(00000000d4b9b663)
[ 1779.748696] sd 7:0:7:0: [sdi] tag#0 CDB: opcode=0x88 88 00 00 00 00 02 b3 49 25 40 00 00 04 00 00 00
[ 1779.748699] scsi target7:0:7: handle(0x0011), sas_address(0x3474f4f5849ab507), phy(7)
[ 1779.748701] scsi target7:0:7: enclosure logical id(0x3474f4f5849ab51e), slot(7)
[ 1780.219660] sd 7:0:7:0: task abort: SUCCESS scmd(00000000d4b9b663)
[ 1780.968812] sd 7:0:7:0: Power-on or device reset occurred

Edited by Benson
Link to comment
1 hour ago, Benson said:

Hi, @olehj first thanks this great app, but I notice some problem after I install this app. I run LSI HBA with expander, array pool and disk pool was 2 different expander, and problem only at array pool, so problem may expander related but I am not sure.

 

Jul 23 19:47:43 X370 kernel: sd 7:0:8:0: Power-on or device reset occurred
....

The error would happen on every hours ~47min, further trace foud it is a hourly cron job at /etc/cron.hourly/disklocation.sh

 

Symptom will be if any of array disk in read or write will trigger it. If no disk in R/W then no problem.

 

Below are dmesg detail FYI, thanks

[ 1715.748840] sd 7:0:7:0: attempting task abort! scmd(00000000fe995705)
[ 1715.748844] sd 7:0:7:0: [sdi] tag#0 CDB: opcode=0x88 88 00 00 00 00 02 b3 48 e9 40 00 00 04 00 00 00
[ 1715.748846] scsi target7:0:7: handle(0x0011), sas_address(0x3474f4f5849ab507), phy(7)
[ 1715.748848] scsi target7:0:7: enclosure logical id(0x3474f4f5849ab51e), slot(7)
[ 1716.216232] sd 7:0:7:0: task abort: SUCCESS scmd(00000000fe995705)
[ 1716.965334] sd 7:0:7:0: Power-on or device reset occurred
...

Hi, thanks!

 

What happens during a cronjob is that it looks for SMART activity. The way it works is that it request which state the drive is in before it pulls out the rest of the SMART data. If the drive(s) reports a typical spinning state (ACTIVE/IDLE), then it will request all SMART data from that drive. If this for some reason fails, or the HBA expander always says the drive is ACTIVE/IDLE regardless the real state of the HD, it looks like it will then wake up the drive to get the SMART data.

But I'm not sure about this and I'm not sure how to really test this further. Maybe there's some special SMART override configurations for the HBA controller if it has a BIOS to prevent it from waking up when SMART is requested? Or maybe SMART is getting disabled, overridden or ignored? 

You can check if you trigger the messages from dmesg via these commands:

Check SMART activity, will (should) only post results if the drive is either ACTIVE or IDLE:

smartctl -n standby /dev/<device>

Output should be something like "Device is in IDLE_B mode". If this line is missing, it is detected as standby or sleep (non-spinning).

 

If the drive is detected as ACTIVE or IDLE, then the cronjob will go on and get the rest of the SMART data with this command (except it will get them via --json in the script):

smartctl -n standby -x /dev/<device>

One or both of these command is probably what causes your messages to happen, and be sure to check if the SMART data seems to be correct and not something the controller "makes"

Link to comment

Thanks for the reply, but I observe problem seems if drive in read write and script get smart report concurrent then problem occur.

 

But there are no problem on official unraid to get SMART report. Anyway, I will do more test.

 

You never got this problem ?

 

 Thanks again.

 

Edited by Benson
Link to comment
6 hours ago, Benson said:

Thanks for the reply, but I observe problem seems if drive in read write and script get smart report concurrent then problem occur.

 

But there are no problem on official unraid to get SMART report. Anyway, I will do more test.

 

You never got this problem ?

 

 Thanks again.

 

I'm not sure what you mean when the drive is in read/write, but no, I have no issues with this. I use LSI HBA (IBM 1015 in IT mode without BIOS), onboard SATA and SCU and Adaptec 6805 raid controller. None of them behaves like that.

Edited by olehj
Link to comment
14 hours ago, olehj said:

I'm not sure what you mean when the drive is in read/write

That means disk have read or write activity.

 

21 hours ago, olehj said:

Output should be something like "Device is in IDLE_B mode". If this line is missing, it is detected as standby or sleep (non-spinning).

 

If the drive is detected as ACTIVE or IDLE, then the cronjob will go on and get the rest of the SMART data with this command (except it will get them via --json in the script):


smartctl -n standby -x /dev/<device>

 

I confirm problem could reproduce if report disk have activity and execute above command. This also reproduce in Unraid GUI if click "Download SMART report".

 

This will be hardware related and no problem if get less detail report by " smartctl -n standby -a /dev/<device> ", I found similar case on internet.

 

Does less detail report enough for this plugin to work ? Thanks

 

https://bugzilla.redhat.com/show_bug.cgi?id=870083

 

commit 49bd665c5407a453736d3232ee58f2906b42e83c
Author: Maciej Patelczyk <maciej.patelczyk@intel.com>
Date:   Mon Oct 15 14:29:03 2012 +0200

    [SCSI] isci: copy fis 0x34 response into proper buffer
    
    SATA MICROCODE DOWNALOAD fails on isci driver. After receiving Register
    Device to Host (FIS 0x34) frame Initiator resets phy.
    In the frame handler routine response (FIS 0x34) was copied into wrong
    buffer and upper layer did not receive any answer which resulted in
    timeout and reset.
    This patch corrects this bug.
    
    Signed-off-by: Maciej Patelczyk <maciej.patelczyk@intel.com>
    Signed-off-by: Lukasz Dorau <lukasz.dorau@intel.com>
    Cc: <stable@vger.kernel.org>
    Signed-off-by: James Bottomley <JBottomley@Parallels.com>

 

Edited by Benson
Link to comment
9 hours ago, Benson said:

That means disk have read or write activity.

 

 

I confirm problem could reproduce if report disk have activity and execute above command. This also reproduce in Unraid GUI if click "Download SMART report".

 

This will be hardware related and no problem if get less detail report by " smartctl -n standby -a /dev/<device> ", I found similar case on internet.

 

Does less detail report enough for this plugin to work ? Thanks

 

https://bugzilla.redhat.com/show_bug.cgi?id=870083

 


commit 49bd665c5407a453736d3232ee58f2906b42e83c
Author: Maciej Patelczyk <maciej.patelczyk@intel.com>
Date:   Mon Oct 15 14:29:03 2012 +0200

    [SCSI] isci: copy fis 0x34 response into proper buffer
    
    SATA MICROCODE DOWNALOAD fails on isci driver. After receiving Register
    Device to Host (FIS 0x34) frame Initiator resets phy.
    In the frame handler routine response (FIS 0x34) was copied into wrong
    buffer and upper layer did not receive any answer which resulted in
    timeout and reset.
    This patch corrects this bug.
    
    Signed-off-by: Maciej Patelczyk <maciej.patelczyk@intel.com>
    Signed-off-by: Lukasz Dorau <lukasz.dorau@intel.com>
    Cc: <stable@vger.kernel.org>
    Signed-off-by: James Bottomley <JBottomley@Parallels.com>

 

If you see the disk then there's no real problem else - the plugin will mainly work for its main purpose: showing the disk locations. SMART is mainly for information only, so in worst case you will not see "power on hours", smart failures etc.

Link to comment
  • 2 weeks later...
  • 2 weeks later...
On 8/3/2019 at 7:21 PM, sarbian said:

I noticed that the Configuration Page and Tray Allocation page do not show the tray in the same order when I use the "left/bottom" count direction.

 

It is intended for easy setup, you add the drives after the numbers shown in allocation and not the end result/chosen layout.

Link to comment

Update 2019.08.23

  • Commit #102 - IMPROVEMENT: Hints provided by @Squid to improve the dashboard integration. Further changes made to customize it and position it to your own liking.

Check the configuration page to adjust the widget. It can be positioned under "Hardware Information" tab, or the "Disk array" tab, or simply turned off. When the tab has been selected, you can move the widget up and down to your liking.

dashboard_widget2.png

Edited by olehj
  • Like 1
Link to comment

The plugin seems to be working fine with the exception of these identical drives.  If I click Locate, none of these disks show a blue light while all of my other disks worked correctly.  Any thoughts on why this would be?  Thy all have smart enabled.

 

Also, if I click the bottom button, the disk directly above it starts to flash, but not that one.  Again, thoughts?

image.png.61792d7efcfbd92df9fe7c2874fe6297.png

Link to comment
41 minutes ago, smburns25 said:

The plugin seems to be working fine with the exception of these identical drives.  If I click Locate, none of these disks show a blue light while all of my other disks worked correctly.  Any thoughts on why this would be?  Thy all have smart enabled.

 

Also, if I click the bottom button, the disk directly above it starts to flash, but not that one.  Again, thoughts?

 

First of all I see that two has the same path (20:0:0:0), this might cause some issues. So I suggest you run a "Force Scan All" under Configuration->Tray Allocation, this will rescan all drives and also wake them up from standby to get all SMART data. It will also purge invalid configs which might happen when replacing drives or controllers, or maybe other configurations.

Else it might be that these drives simply don't trigger the HDD light when SMART data is requested, like most/all of the SSD's out there. No fix for that in this case.

Link to comment
1 hour ago, mikesp18 said:

I have a server with a configuration like this link (I think it was a 2015 purchase directly from Limetech). What would be a good way to configure this?DriveNumberingScheme3.jpg

First of all, get Unraid 6.7.2 or above and update the plugin to the newest version.

Then you add three groups, 5+4+5 slots, first and last vertical, the middle horizontal with standard count 1->5 on all. Then you can adjust pixel sizes to make a difference for 3,5 and 2,5 manually. Something like this:

dl-5-4-5.png.d691b399c3a6098f6ad1e31980822a31.png

Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.