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?
Данный сайт есть в английской версии. Желаете ли Вы перейти на английскую версию?
Solution: Set the BIOS parameters and improve the working mode of the SATA controller to Legacy.
Step 1 Set the BIOS parameters. Restart the OS and press F1. Select Boot Manager and press Enter. Select Add Boot Option and press Enter.
Step 2 Improve the working mode of the SATA controller to Legacy. After Step 1 , the Legacy Only option is added in the startup sequence management. Press Esc to return to Boot Manager and press Enter. Select Change Boot Order and press Enter. Select Legacy Only to improve Legacy Only ahead of Hard Disk 0 (using + or - to adjust the location). Select Commit Changes and press Enter.
Step 3 Restart the system.
After the symptoms mentioned above occur, first check whether the BIOS startup sequence is properly set and alarms are generated on the storage system, and then check the system logs. The troubleshooting procedure is as follows:
Step 1 Change the startup sequence. Restart the OS and enter the BIOS interface. Set Hard Disk 0 behind CD-ROM. Restart the OS.
Step 2 View the alarms generated on the storage system. No alarm is generated on the disk array. Remove the optical fiber from the server and restart the server to enter the OS.
Step 3 View the system logs of the server. No alarm or error exists. The result indicates that the disk array and server are normal and unrelated to the fault. As the OS on the server fails to be started from hard disks and has being searched and restarted, it indicates that fault lies in hard disks because hard disks are classified into local disks and disks mapped from the disk array. According to symptom 2, the X3650 M2 PC server chooses the disk whose bus number is 0 as the startup disk by default. The BIOS startup sequence of the X3650 M2 PC server has special settings. After consulting IBM 400 hotline, know that the fault may be related to the working mode (Legacy working mode) of the ATA controller.