Some unpredictable output via hdsentinel on MegaRAID

Experiences with hard disks, SSDs, USB devices, hard disk controllers, motherboards and so.
klbblk72
Posts: 3
Joined: 2024.03.02. 11:19

Some unpredictable output via hdsentinel on MegaRAID

Post by klbblk72 »

Hard Disk Sentinel for LINUX console 0.20b-x64.10851
CentOS 7.4 with LSI MegaRAID Tri-Mode SAS3508 connected to MegaRAIDSAS9460-8i

Physical Drives = 24
PD LIST :
=======
----------------------------------------------------------------------------------------
EID:Slt DID State DG Size Intf Med SED PI SeSz Model Sp Type
----------------------------------------------------------------------------------------
65:0 10 Onln 0 1.090 TB SAS HDD N N 512B AL15SEB120N U -
65:1 9 Onln 0 1.090 TB SAS HDD N N 512B AL15SEB120N U -
65:2 22 Onln 1 893.750 GB SATA SSD N N 512B SAMSUNG MZ7LH960HAJR-00005 U -
65:3 20 Onln 1 893.750 GB SATA SSD N N 512B SAMSUNG MZ7LH960HAJR-00005 U -
65:4 23 Onln 2 1.636 TB SAS HDD N N 512B ST1800MM0129 U -
65:5 12 Onln 3 1.636 TB SAS HDD N N 512B ST1800MM0129 U -
65:6 21 Onln 4 1.636 TB SAS HDD N N 512B ST1800MM0129 U -
65:7 13 Onln 5 1.636 TB SAS HDD N N 512B ST1800MM0129 U -
65:8 16 Onln 6 1.636 TB SAS HDD N N 512B ST1800MM0129 U -
65:9 14 Onln 7 1.636 TB SAS HDD N N 512B ST1800MM0129 U -
65:10 19 Onln 8 1.636 TB SAS HDD N N 512B ST1800MM0129 U -
65:11 17 Onln 9 1.636 TB SAS HDD N N 512B ST1800MM0129 U -
65:12 15 Onln 10 1.636 TB SAS HDD N N 512B ST1800MM0129 U -
65:13 31 Onln 11 1.636 TB SAS HDD N N 512B ST1800MM0129 U -
65:14 8 Onln 12 1.636 TB SAS HDD N N 512B AL15SEB18EQ U -
65:15 27 Onln 13 1.636 TB SAS HDD N N 512B ST1800MM0129 U -
65:16 29 Onln 14 1.636 TB SAS HDD N N 512B ST1800MM0129 U -
65:17 32 Onln 21 1.636 TB SAS HDD N N 512B HUC101818CS4200 U -
65:18 30 Onln 15 1.636 TB SAS HDD N N 512B ST1800MM0129 U -
65:19 28 Onln 16 1.636 TB SAS HDD N N 512B ST1800MM0129 U -
65:20 24 Onln 17 1.636 TB SAS HDD N N 512B ST1800MM0129 U -
65:21 11 Onln 18 1.636 TB SAS HDD N N 512B ST1800MM0129 U -
65:22 25 Onln 19 1.636 TB SAS HDD N N 512B ST1800MM0129 U -
65:23 18 Onln 20 1.636 TB SAS HDD N N 512B ST1800MM0129 U -
----------------------------------------------------------------------------------------

Virtual Drives :
==============
---------------------------------------------------------------
DG/VD TYPE State Access Consist Cache Cac sCC Size Name
---------------------------------------------------------------
0/0 RAID1 Optl RW Yes RWBD - ON 1.090 TB
1/1 RAID1 Optl RW Yes RWBD - ON 893.750 GB
2/2 RAID0 Optl RW Yes RWBD - ON 1.636 TB
3/3 RAID0 Optl RW Yes RWBD - ON 1.636 TB
4/4 RAID0 Optl RW Yes RWBD - ON 1.636 TB
5/5 RAID0 Optl RW Yes RWBD - ON 1.636 TB
6/6 RAID0 Optl RW Yes RWBD - ON 1.636 TB
7/7 RAID0 Optl RW Yes RWBD - ON 1.636 TB
8/8 RAID0 Optl RW Yes RWBD - ON 1.636 TB
9/9 RAID0 Optl RW Yes RWBD - ON 1.636 TB
10/10 RAID0 Optl RW Yes RWBD - ON 1.636 TB
11/11 RAID0 Optl RW Yes RWBD - ON 1.636 TB
12/12 RAID0 Optl RW Yes RWBD - ON 1.636 TB
13/13 RAID0 Optl RW Yes RWBD - ON 1.636 TB
14/14 RAID0 Optl RW Yes RWBD - ON 1.636 TB
15/15 RAID0 Optl RW Yes RWBD - ON 1.636 TB
16/16 RAID0 Optl RW Yes RWBD - ON 1.636 TB
17/17 RAID0 Optl RW Yes RWBD - ON 1.636 TB
18/18 RAID0 Optl RW Yes RWBD - ON 1.636 TB
19/19 RAID0 Optl RW Yes RWBD - ON 1.636 TB
20/20 RAID0 Optl RW Yes RWBD - ON 1.636 TB
21/21 RAID0 Optl RW Yes RWBD - ON 1.636 TB
---------------------------------------------------------------


There would be some "strange" and "incorrect" outputs mapping relationship between all the VDs and the PDs ...
1). Why would all the PDs just only corresponding to the same VD /dev/sda, versus others null ?
2). Why would every one VD "span across" all the PDs, despite each VD using just only one PD ?

#
# /HDSentinel -solid
/dev/sda 27 100 29592 TOSHIBA_AL15SEB18EQ 79V0A013FE5G 1144127
25 100 29592 TOSHIBA_AL15SEB120N 2080A288FDWG 1144127
25 100 29592 TOSHIBA_AL15SEB120N 2080A2E1FDWG 1144127
27 100 29595 SEAGATE_ST1800MM0129 WBN3D321 1144127
26 100 29596 SEAGATE_ST1800MM0129 WBN3D2YW 1144127
27 100 29595 SEAGATE_ST1800MM0129 WBN3D4A0 1144127
28 100 29595 SEAGATE_ST1800MM0129 WBN3CZW7 1144127
29 100 29595 SEAGATE_ST1800MM0129 WBN3DAPQ 1144127
28 100 29595 SEAGATE_ST1800MM0129 WBN3CZT8 1144127
29 100 29595 SEAGATE_ST1800MM0129 WBN3D2L3 1144127
27 100 29595 SEAGATE_ST1800MM0129 WBN3D4W1 1144127
28 100 29595 SEAGATE_ST1800MM0129 WBN3DA7G 1144127
25 99 29592 SAMSUNG_MZ7LH960HAJR-00005 S45NNA0N352928 915715
27 100 29595 SEAGATE_ST1800MM0129 WBN3D4FY 1144127
25 92 29592 SAMSUNG_MZ7LH960HAJR-00005 S45NNE0N220217 915715
27 100 29595 SEAGATE_ST1800MM0129 WBN3D45E 1144127
27 100 29596 SEAGATE_ST1800MM0129 WBN3D186 1144127
27 100 29595 SEAGATE_ST1800MM0129 WBN3CZDY 1144127
28 100 29595 SEAGATE_ST1800MM0129 WBN2DY0Y 1144127
26 100 29595 SEAGATE_ST1800MM0129 WBN2E2GJ 1144127
28 100 29595 SEAGATE_ST1800MM0129 WBN2FH34 1144127
28 100 29595 SEAGATE_ST1800MM0129 WBN26AKT 1144127
29 100 29595 SEAGATE_ST1800MM0129 WBN2E6WJ 1144127
30 100 4207 HGST____HUC101818CS4200 08H9DSBA 1144127
/dev/sdb ? ? -1 LSI_virtualSES ? 915199
/dev/sdc ? ? -1 LSI_virtualSES ? 1716415
/dev/sdd ? ? -1 LSI_virtualSES ? 1716415
/dev/sde ? ? -1 LSI_virtualSES ? 1716415
/dev/sdf ? ? -1 LSI_virtualSES ? 1716415
/dev/sdg ? ? -1 LSI_virtualSES ? 1716415
/dev/sdh ? ? -1 LSI_virtualSES ? 1716415
/dev/sdi ? ? -1 LSI_virtualSES ? 1716415
/dev/sdj ? ? -1 LSI_virtualSES ? 1716415
/dev/sdk ? ? -1 LSI_virtualSES ? 1716415
/dev/sdl ? ? -1 LSI_virtualSES ? 1716415
/dev/sdm ? ? -1 LSI_virtualSES ? 1716415
/dev/sdn ? ? -1 LSI_virtualSES ? 1716415
/dev/sdo ? ? -1 LSI_virtualSES ? 1716415
/dev/sdp ? ? -1 LSI_virtualSES ? 1716415
/dev/sdq ? ? -1 LSI_virtualSES ? 1716415
/dev/sdr ? ? -1 LSI_virtualSES ? 1716415
/dev/sds ? ? -1 LSI_virtualSES ? 1716415
/dev/sdt ? ? -1 LSI_virtualSES ? 1716415
/dev/sdu ? ? -1 LSI_virtualSES ? 1716415
/dev/sdv ? ? -1 LSI_virtualSES ? 1716415
#
#
# ./HDSentinel -dev /dev/sdp <<< here just using the /dev/sdp VD output for an example...
Hard Disk Sentinel for LINUX console 0.20b-x64.10851 (c) 2023 info@hdsentinel.com
Start with -r [reportfile] to save data to report, -h for help

Examining hard disk configuration ...

HDD Device 0: /dev/sdp
HDD Model ID : TOSHIBA AL15SEB18EQ
HDD Serial No: 79V0A013FE5G
HDD Revision : 0805
HDD Size : 1716415 MB
Interface : LSI RAID #0/8 [8-0] SAS
Temperature : 27 °C
Highest Temp.: 27 °C
Health : 100 %
Performance : 100 %
Power on time: 1233 days, 0 hours, 44 minutes (estimated)
Est. lifetime: more than 591 days
Total written: 11.62 TB
The status of the hard disk is perfect.
No actions needed.

HDD Device 1: /dev/sdp
HDD Model ID : TOSHIBA AL15SEB120N
HDD Serial No: 2080A288FDWG
HDD Revision : 0807
HDD Size : 1716415 MB
Interface : LSI RAID #0/9 [8-0] SAS
Temperature : 25 °C
Highest Temp.: 25 °C
Health : 100 %
Performance : 100 %
Power on time: 1233 days, 0 hours, 14 minutes (estimated)
Est. lifetime: more than 591 days
Total written: 7.94 TB
The status of the hard disk is perfect.
No actions needed.

HDD Device 2: /dev/sdp
HDD Model ID : TOSHIBA AL15SEB120N
HDD Serial No: 2080A2E1FDWG
HDD Revision : 0807
HDD Size : 1716415 MB
Interface : LSI RAID #0/10 [8-0] SAS
Temperature : 25 °C
Highest Temp.: 25 °C
Health : 100 %
Performance : 100 %
Power on time: 1233 days, 0 hours, 11 minutes (estimated)
Est. lifetime: more than 591 days
Total written: 7.94 TB
The status of the hard disk is perfect.
No actions needed.

HDD Device 3: /dev/sdp
HDD Model ID : SEAGATE ST1800MM0129
HDD Serial No: WBN3D321
HDD Revision : C004
HDD Size : 1716415 MB
Interface : LSI RAID #0/11 [8-0] SAS
Temperature : 27 °C
Highest Temp.: 27 °C
Health : 100 %
Performance : 100 %
Power on time: 1233 days, 3 hours, 43 minutes
Est. lifetime: more than 591 days
Total written: 1.52 TB
The status of the hard disk is perfect.
No actions needed.

HDD Device 4: /dev/sdp
HDD Model ID : SEAGATE ST1800MM0129
HDD Serial No: WBN3D2YW
HDD Revision : C004
HDD Size : 1716415 MB
Interface : LSI RAID #0/12 [8-0] SAS
Temperature : 26 °C
Highest Temp.: 26 °C
Health : 100 %
Performance : 100 %
Power on time: 1233 days, 4 hours, 7 minutes
Est. lifetime: more than 591 days
Total written: 1.16 TB
The status of the hard disk is perfect.
No actions needed.

HDD Device 5: /dev/sdp
HDD Model ID : SEAGATE ST1800MM0129
HDD Serial No: WBN3D4A0
HDD Revision : C004
HDD Size : 1716415 MB
Interface : LSI RAID #0/13 [8-0] SAS
Temperature : 27 °C
Highest Temp.: 27 °C
Health : 100 %
Performance : 100 %
Power on time: 1233 days, 3 hours, 5 minutes
Est. lifetime: more than 591 days
Total written: 1.37 TB
The status of the hard disk is perfect.
No actions needed.

HDD Device 6: /dev/sdp
HDD Model ID : SEAGATE ST1800MM0129
HDD Serial No: WBN3CZW7
HDD Revision : C004
HDD Size : 1716415 MB
Interface : LSI RAID #0/14 [8-0] SAS
Temperature : 28 °C
Highest Temp.: 28 °C
Health : 100 %
Performance : 100 %
Power on time: 1233 days, 3 hours, 11 minutes
Est. lifetime: more than 591 days
Total written: 1.15 TB
The status of the hard disk is perfect.
No actions needed.

HDD Device 7: /dev/sdp
HDD Model ID : SEAGATE ST1800MM0129
HDD Serial No: WBN3DAPQ
HDD Revision : C004
HDD Size : 1716415 MB
Interface : LSI RAID #0/15 [8-0] SAS
Temperature : 29 °C
Highest Temp.: 29 °C
Health : 100 %
Performance : 100 %
Power on time: 1233 days, 3 hours, 22 minutes
Est. lifetime: more than 591 days
Total written: 1.44 TB
The status of the hard disk is perfect.
No actions needed.


#
#
# ./HDSentinel -dev /dev/sdp|grep -E "HDD Device"
HDD Device 0: /dev/sdp
HDD Device 1: /dev/sdp
HDD Device 2: /dev/sdp
HDD Device 3: /dev/sdp
HDD Device 4: /dev/sdp
HDD Device 5: /dev/sdp
HDD Device 6: /dev/sdp
HDD Device 7: /dev/sdp
HDD Device 8: /dev/sdp
HDD Device 9: /dev/sdp
HDD Device 10: /dev/sdp
HDD Device 11: /dev/sdp
HDD Device 12: /dev/sdp
HDD Device 13: /dev/sdp
HDD Device 14: /dev/sdp
HDD Device 15: /dev/sdp
HDD Device 16: /dev/sdp
HDD Device 17: /dev/sdp
HDD Device 18: /dev/sdp
HDD Device 19: /dev/sdp
HDD Device 20: /dev/sdp
HDD Device 21: /dev/sdp
HDD Device 22: /dev/sdp
HDD Device 23: /dev/sdp
HDD Device 24:
#
#
# ./HDSentinel -onlydevs /dev/sdp|grep -E "HDD Seri"
HDD Serial No: 79V0A013FE5G
HDD Serial No: 2080A288FDWG
HDD Serial No: 2080A2E1FDWG
HDD Serial No: WBN3D321
HDD Serial No: WBN3D2YW
HDD Serial No: WBN3D4A0
HDD Serial No: WBN3CZW7
HDD Serial No: WBN3DAPQ
HDD Serial No: WBN3CZT8
HDD Serial No: WBN3D2L3
HDD Serial No: WBN3D4W1
HDD Serial No: WBN3DA7G
HDD Serial No: S45NNA0N352928
HDD Serial No: WBN3D4FY
HDD Serial No: S45NNE0N220217
HDD Serial No: WBN3D45E
HDD Serial No: WBN3D186
HDD Serial No: WBN3CZDY
HDD Serial No: WBN2DY0Y
HDD Serial No: WBN2E2GJ
HDD Serial No: WBN2FH34
HDD Serial No: WBN26AKT
HDD Serial No: WBN2E6WJ
HDD Serial No: 08H9DSBA
HDD Serial No: SERIAL24
#
User avatar
hdsentinel
Site Admin
Posts: 3019
Joined: 2008.07.27. 17:00
Location: Hungary
Contact:

Re: Some unpredictable output via hdsentinel on MegaRAID

Post by hdsentinel »

Yes, I'm afraid this is completely normal and expected, absolutely not a bug/limitation of the Linux version of Hard Disk Sentinel, but a generic bug/limitation of the MegaRAID under Linux (so I moved the topic).

Under Linux, I'm afraid with MegaRAID it is not possible to map which physical drive is associated to which array.
This is exactly why do you see that when Hard Disk Sentinel Linux version detects this controller, then it automatically enumerates all disk drives and show them just like if they would all form a single, big array.
Then, when it finds the next (and any further) array, it does not show the same disk(s) again and again.

There is no such problem under Windows: under Windows, it is possible to find the association between logical and physical drives, so generally things work better, but I'm afraid under Linux, we can work with this limitation.
klbblk72
Posts: 3
Joined: 2024.03.02. 11:19

Re: Some unpredictable output via hdsentinel on MegaRAID

Post by klbblk72 »

It seems that the latest hdsentinel for linux still cannot correctly recognize the mapping reationship between the VDs and PDs on its MegaRAID, versus only using the specical MegaRAID tool of storcli can ...
Last edited by klbblk72 on 2024.03.04. 14:51, edited 1 time in total.
klbblk72
Posts: 3
Joined: 2024.03.02. 11:19

Re: Some unpredictable output via hdsentinel on MegaRAID

Post by klbblk72 »

Would be there any other alternative way to avoid such above limited phenomenon ?
Post Reply