44p 170 启动故障，跪求解决方法

sunmico

启动以后就报4BA00830 --- BOOT FAIL。WHY？
该机器如何用CDROM启动？

caolifeng

具体是什么服务器，操作系统版本？44p 170我没见过呀？请说的详细点！

xiaoxiaoking

开机后按Ｆ１可以选择启动设备，
按Ｆ５，先从外设启动

xuwelcome

Boot Problems/Concerns
Depending on the boot device, a checkpoint may be displayed on the operator panel for an extended period of time while the boot image is retrieved from the device. This is particularly true for tape and network boot attempts. If booting from CD-ROM or tape,
watch for activity on the drive’s LED indicator. A blinking LED indicates that the loading of either the boot image or additional information required by the operating system being booted is still in progress. If the checkpoint is displayed for an extended period of
time and the drive LED is not indicating any activity, there might be a problem loading the boot image from the device.

Note: For network boot attempts, if the system is not connected to an active network or if the target server is inaccessible (this can also result from incorrect IP parameters being supplied), the system will still attempt to boot. Because time-out durations are necessarily long to accommodate retries, the system may appear to be hung.

This procedure assumes that a CD-ROM drive is connected to internal SCSI connector J30 and a diagnostics CD-ROM is available.

Step 1
Restart the system and access the firmware SMS Main Menu. Select Multiboot.
1. Check if the intended boot device is correctly specified in the boot sequence.
2. If the intended boot device is not correctly identified in the boot sequence, add it to the boot sequence using the SMS menus. If the intended boot device cannot be added to the boot sequence, go to step “Step 3” on page 92.
3. If attempting to boot from the network, go to step “Step 2”.
4. If attempting to boot from a disk drive or CD-ROM, go to step “Step 3” on page 92.

Step 2
If attempting to boot from the network:
1. Verify that IP parameters are correct.
2. Attempt to ²ping² the target server using the SMS Ping utility. If the ping is not successful, have the network administrator verify the server configuration for this client.
3. Check with the network administrator to ensure that the network is up.
4. Check the network cabling to the adapter.
5. Turn the power Off, then On and retry the boot operation.

xuwelcome

Step 3
Try to boot and run standalone diagnostics against the system, particularly against the intended boot device.
1. If the intended boot device is not listed in the ²NEW RESOURCE² list, go to ²MAP 0290: Missing Resource Problem Resolution² in the Diagnostic Information for Multiple Bus Systems.
2. If an SRN, not an 8-digit error code, is reported, go to the Diagnostic Information for Multiple Bus Systemsmanual.
3. If the diagnostics are successful, it may be necessary to perform an operating system-specific recovery process, or reinstall the operating system.
4. If unable to load standalone diagnostics, do the following:
a. Verify proper SCSI bus termination
b. Check SCSI cabling
c. It is possible that another attached SCSI device is causing the problem. Do the following:
1) Disconnect the signal and power cables from the disk drive cage backplane.
2) Disconnect the disk drive(s) in the disk drive cage from the backplane.
3) Disconnect the signal and power cables from any other SCSI devices attached to the SCSI adapter that the CD-ROM drive is attached to.
4) Try to boot the standalone diagnostics again.
5) If you are still unable to load standalone diagnostics go to step “Step 4”.
6) If standalone diagnostics load, one of the disconnected devices is causing the problem. Reconnect the devices one at a time and retry the boot operation until the problem recurs and replace the device that caused the problem. (If the problem appears to be one of the disk drives in the disk drive cage, be aware it could be either the disk drive or the backplane.) Go to "MAP 410: Repair Checkout" in the Diagnostic Information for Multiple Bus Systems.

xuwelcome

Step 4
It is possible that another installed adapter is causing the problem. Do the following:
1. Remove all installed adapters except the one the CD-ROM drive is attached to and the one used for the console.
2. Try to boot the standalone diagnostics again.
3. If unable to load standalone diagnostics go to step 5.
4. If standalone diagnostics load, reinstall adapters (and attached devices as applicable) one at a time and retry the boot operation until the problem recurs. Then replace the adapter or device that caused the problem. (The system board can also cause the device or adapter to fail.) Go to "MAP 410: Repair Checkout" in the
Diagnostic Information for Multiple Bus Systems.

Step 5
The CD-ROM drive, SCSI cable, SCSI adapter, graphics adapter, or the system board is most likely defective. A TTY terminal attached to the serial port also can be used to determine if the graphics adapter is causing the problem. This is done by removing the
graphics adapter, attaching a TTY to the serial port, and retrying standalone diagnostics. If the standalone diagnostics load, replace the graphics adapter.
1. Replace the CD-ROM drive.
2. Replace the SCSI cable.
3. If the CD-ROM drive is attached to a SCSI adapter rather than the integrated SCSI on the system board, replace the SCSI adapter.
4. Replace the system board.
5. If you replaced the indicated FRUs and the problem is still not corrected, or the above descriptions did not address your particular situation, go to “MAP 1540: Minimum Configuration” on page 52.
6. Go to "MAP 410: Repair Checkout" in Diagnostic Information for Multiple Bus Systems