vBulletin Search Engine Optimization
| |||||||
| Register | FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| Currently trying to install AIX 5.2 on an F50. The install from CD works fine until the very end, where after creating the boot image the install process reboots the server. The reboot fails and the server just shuts down with the 20EE000B LED code. The code, to the best of my knowledge, says that no boot image was found from the bootlist. The install process always fails. Have tried to install to different disks and scsi controllers thinking maybe that was the culprit. The install process should be establishing the correct bootlist, yet it acts as though it can't find the boot image. I've reduced the server to one disk and controller and still the install process fails at the reboot. Any help would be greatly appreciated. Thanks |
| |||
| On 7/10/04 7:01 pm, in article 623b7a42.0410071001.1488ec96@posting.google.com, "Rick" <rnaquin@ashp.org> wrote: > Currently trying to install AIX 5.2 on an F50. The install from CD > works fine until the very end, where after creating the boot image the > install process reboots the server. The reboot fails and the server > just shuts down with the 20EE000B LED code. The code, to the best of > my knowledge, says that no boot image was found from the bootlist. > The install process always fails. Have tried to install to different > disks and scsi controllers thinking maybe that was the culprit. The > install process should be establishing the correct bootlist, yet it > acts as though it can't find the boot image. I've reduced the server > to one disk and controller and still the install process fails at the > reboot. Any help would be greatly appreciated. > > Thanks Do you have the latest version of the microcode for this machine installed? Might be worth a try... |
| |||
| rnaquin@ashp.org (Rick) wrote in message news:<623b7a42.0410071001.1488ec96@posting.google. com>... > Currently trying to install AIX 5.2 on an F50. The install from CD > works fine until the very end, where after creating the boot image the > install process reboots the server. The reboot fails and the server > just shuts down with the 20EE000B LED code. The code, to the best of > my knowledge, says that no boot image was found from the bootlist. > The install process always fails. Have tried to install to different > disks and scsi controllers thinking maybe that was the culprit. The > install process should be establishing the correct bootlist, yet it > acts as though it can't find the boot image. I've reduced the server > to one disk and controller and still the install process fails at the > reboot. Any help would be greatly appreciated. > > Thanks You are correct..the code means unable to find a boot device. I upgraded an F50 from 4.3.3 to 5.2 quite a while back, as a test before doing that to the production F80. It worked fine for me, although I upgraded the firmware to the latest, just to be safe. I don't remember that being a requirement, and it may not be your problem, but I thought I'd mention it. Steve |
| ||||
| Resolution: Re-installed the L04197 system firmware and the system booted successfully!!!! Thanks for the help! Rick midrangeguy@hotmail.com (Steve) wrote in message news:<4dfd3c0d.0410071525.46037c56@posting.google. com>... > rnaquin@ashp.org (Rick) wrote in message news:<623b7a42.0410071001.1488ec96@posting.google. com>... > > Currently trying to install AIX 5.2 on an F50. The install from CD > > works fine until the very end, where after creating the boot image the > > install process reboots the server. The reboot fails and the server > > just shuts down with the 20EE000B LED code. The code, to the best of > > my knowledge, says that no boot image was found from the bootlist. > > The install process always fails. Have tried to install to different > > disks and scsi controllers thinking maybe that was the culprit. The > > install process should be establishing the correct bootlist, yet it > > acts as though it can't find the boot image. I've reduced the server > > to one disk and controller and still the install process fails at the > > reboot. Any help would be greatly appreciated. > > > > Thanks > > You are correct..the code means unable to find a boot device. I > upgraded an F50 from 4.3.3 to 5.2 quite a while back, as a test before > doing that to the production F80. It worked fine for me, although I > upgraded the firmware to the latest, just to be safe. I don't > remember that being a requirement, and it may not be your problem, but > I thought I'd mention it. > > Steve |