Questo sito utilizza cookie di profilazione (propri e di terze parti) per ottimizzare la tua esperienza online e per inviarti pubblicità in linea con le tue preferenze. Continuando a utilizzare questo sito senza modificare le tue preferenze acconsenti all’uso dei cookie. Se vuoi saperne di più o negare il consenso a tutti o ad alcuni cookie clicca qui>
The website that you are visiting also provides Arabian language. Do you wish to switch language version?
يوفر موقع الويب الذي تزوره المحتوى باللغة العربية أيضًا. هل ترغب في تبديل إصدار اللغة؟
The website that you are visiting also provides Russia language Do you wish to switch language version?
Данный сайт есть в английской версии. Желаете ли Вы перейти на английскую версию?
Customer's question as below :-
We are observing lsscsi ports mismatch in a few Huawei servers.
We should be seeing the nomenclature of lsscsi port of Huawei servers as below:
For 4TB HDD's:
For SSD HDD's:
But in a few servers, we are getting a different nomenclature of lsscsi port. Because of this, our disk monitoring is failing and it is not able to catch the HDD data.
There is no alarm in iBMC.
Collect iBMC and OS logs from both good and problem server to check the disk lsscsi ports.
The example for the abnormal system:
When the system initializing, the AHCI initialized earlier than RAID Card, so the AHCI device used the SCSI0 and the RAID card used the SCSI4, so this server disks ordered by 4:0:0:0
The good server system:
When the system initializing, the AHCI initialized later than RAID Card, so the RAID card used the SCSI0, so this server disks ordered by 0:0:0:0.
There is 2 option to solve this issue. By following this 2 method, the AHCI initialized later than RAID Card, so the RAID card used the SCSI0, so this server disks ordered by 0:0:0:0.
1) Login to OS with root
2) Add the rdloaddriver=mpt3sas in the /boot/grub/menu.lst (as shown below)
3) Reboot the server.
1) Reboot server and login to BIOS
2) Disable the SATA controller in BIOS as shown below
3) Reboot the server and check disk order
After performing above steps(Customer choose option 2) the disk boot normal with order 0:0:0:0. Screen shot as below :-
1) In such situation we need to collect OS logs to analysis the issue.
Path :- \disk\sys_block.txt