If you ever end up there and looking for a disks mount point you can navigate around using these commands. Can you believe that it actually worked? In the end, in desperation, we swapped the bay over with the one that worked. Tech Stuff and random observations on life as I see it…. Resetting the boot point for the blade didnt make any difference so it was back to the web for another solution. Ever tried to use Serial over Ethernet before? Sorry, your blog cannot share posts by email.
Uploader: | Vuzilkree |
Date Added: | 15 November 2018 |
File Size: | 49.26 Mb |
Operating Systems: | Windows NT/2000/XP/2003/2003/7/8/10 MacOS 10/X |
Downloads: | 80104 |
Price: | Free* [*Free Regsitration Required] |
Actually no, I'm not facecrooks.
JS21 | Ramblings of this guy you know!
It went on sweet as anything and installed with no issues. If you ever end up there and looking for a disks mount point you can navigate around using these commands Once at an Open Firmware prompt, to display current device aliases use the devalias command.
By firmwate to use this website, you agree to their use. Finally, in defeat we resorted to RHEL5.
Fix Central
Can you believe that it actually worked? Once at an Open Firmware prompt, to display current device aliases use the devalias command. So we tried ignoring the toolkit installer and looked to install the IBM goodies later. Ramblings of this guy you know! Each time we tried it, looking for why it was failing took up a significant portion of time as the bladecenter we have is served by a central USB DVD drive which it seems only supports USB1.
Enter your email address to subscribe to this blog and receive notifications of new posts by email.
If you ever end up there and looking for a disks mount point you can navigate around using these commands. It should show a table of your bays and blade servers.
A small flathead screwdriver would be useful. Should booting off this device fail, your system will fallback to the next device listed in the boot-device Open Firmware settings. Look on the bottom of the page. Server 2 should have been simple, a re-install of RHEL5 is all that was required. We tried reviving the old version of RHEL via the old toolkit installed but still no success.
Tech Stuff and random observations on life as Firmwage see it…. Post was not sent - check your email addresses! Success,we can now toolkit install version 6. Email Subscription Enter your email address to subscribe to this blog and receive notifications of new posts by email. You should be good to go. From now on I will be doing death metal only!! That was server 1.
The same happened with servers 3 and 4… That Bladecenter is in for a kicking… Sorry, reboot at the next available point. Blog Stats 13, Visitors. To find out more, including how to control cookies, see here: Resetting the boot point for the blade didnt make any difference so it was back to the web for another solution.
This site uses cookies. Remove the battery from the server for five minutes. After the failed boot you get thrown into an OpenFirmware prompt. I have moved on from this climate thing Sorry, your blog cannot share posts by email.
Slide out the blade, open the server, frmware an anti-static wristband if you worry about these thingsand remove the nickel-sized battery. How to Connect to the Console.
No comments:
Post a Comment