History
SANTA CLARA, CA -- May 13, 2002 -- Sun Microsystems, Inc. is making the delivery of network applications simpler and more affordable than ever with the introduction of the Sun Cobalt RaQ(tm) 550 server appliance.
Read more...     
The Strongbolt2 ROM
With the arrival of Strongbolt2, we have a new ROM for Cobalt servers.
The new ROM is based on the source from sourceforge.net, but modified to include a 2.6 kernel. The reason for this is to facillitate booting from USB and support for extra hardware.
Read more...     
Strongbolt 2 upgrade released
A new year sees a completely new release of Strongbolt.
The Strongbolt2 upgrade is an easy process that just involves installing a couple of packages through the package management interface (bluelinq).
Read more...     
Testimonials
Support from OS Office is nothing short of amazing.
Finding companies that stand behind their products these days can be challenging, but the staff at OS Office proves they still exist.
I continue to be stunned by their response times and outstanding service.
 
Jim Murray
Read more...   
Search
Firebolt Install Guide (from SB1)

Firebolt Install Guide (from SB1)

Pre-requisites:

  • A Cobalt RaQ3, RaQ4, Qube3 or RaQ550 with Strongbolt OS installed.

Method:

  1. Purchase the Firebolt installation package from the OS Office online shop.
    The downloaded file is a zipped archive containing all of the files required to update your system.
  2. Unzip the archive file to a local folder. The archive contains several PKG files:

    • sb2_preinstall_patch.pkg
    • sb2_upgrade.pkg
    • sb2_flashdrive_v1.01.pkg

  3. Log onto your server appliance through the BlueQuartz administration area.
  4. Select the BlueQuartz Software Installation area "BlueLinQ".
  5. Select "Third Party Updates"
  6. Click on the "Install Manually" button.
  7. Select "Upload"
  8. Use your file browser to select the location of the first package file.
Note: If you cannot upload the files through a browser, please try installing from a url.


Installation order

Install the package files in the following order:

  1. sb2_preinstall_patch.pkg
  2. sb2_upgrade.pkg (the system update)
    Note: After installing this package, the system will reboot
    Click here for more details
  3. sb2_flashdrive_v1.01.pkg (usb tools)
  4. Repeat the upload procedure until you have installed all of the required package files.
  5. Reboot
  6. Set the server to boot from the appropriate boot device

      For servers with 2 hard drives (RAID1):
    • Turn on your server and hold down 'S' on the LCD control panel. 
    • The LCD will print "Select Option" "Boot from Disk" press 'S' until the LCD prints "Configure boot Disk"
    • Press 'E' The LCD will print "Select Boot Disk"
    • Press 'S' until the LCD prints "md1"
    • Press 'E' The LCD will print "Select Option" "Boot from Disk"
    • Press 'E
    • The system should now boot

      For servers with 1 hard drive:

    • Turn on your server and hold down 'S' on the LCD control panel
    • The LCD will print "Select Option" "Boot from Disk" press 'S' until the LCD prints "Configure boot Disk"
    • Press 'E' The LCD will print "Select Boot Disk"
    • Press 'S' until the LCD prints "hda1"
    • Press 'E' The LCD will print "Select Option" "Boot from Disk"
    • Press 'E'
      The system should now boot

Your system is now running with the SB2 ROM, and you can continue to the next stage "Creating the Firebolt USB Key".


Creating the Firebolt USB key

The following procedure only applies to servers that have had the SB2 update.

Use the following commands to re-install the server from a USB key:

  1. Log into the server using an SSH client (puTTY is a good one for Windows).
  2. Become root (su - root)
  3. Run the following command:

    setup_strongbolt2_drive

    Note: If the setup_strongbolt2_drive command is not there, (some beta testers may find this) please run the following command:
    yum install strongbolt2-flashdrive

    Figure 1 Setting up the USB Key (Part 1)

  4. Once the USB key has been setup with the basic core files, the key still needs to download the disk image.
    Run the following command to download the main operating system image:
    download_firebolt_iso

    Figure 2 Setting up the USB key Part 2



    The program requires you to enter your osoffice.co.uk online shop username and password in order to download the operating system image file.
  5. Enter your username and password.

    This will start the image file downloading process. Once the file has downloaded, the image is checked for corruption and the USB key setup is completed. Once this stage is complete, the program will ask whether or not to set the server to reboot to the USB key on next boot. Type "y" to set the system to re-install on next boot and "n" to keep the system boot settings as they are.
  6. If you had chosen to re-install upon next boot, type the following command:
    reboot

Your Firebolt USB key is now ready to use.



Installing the server from the server from the Firebolt USB key

  1. If you had not chosen to re-instal lthe system upon the next boot, you can set the system to boot from the USB key using the following procedure:
    With the server powered off, turn on your server and hold down S on the LCD control panel.
    The LCD will print "Select Option" "Boot from Disk" press 'S' until the LCD prints "Configure boot Disk"



    Press 'E' The LCD will print "Select Boot Disk"



    Press 'S' until the LCD prints "sda1"
    Press 'E' The LCD will print "Select Option" "Boot from Disk"



    This will boot the system from the USB key and start the installation process.
    Note: You can also run the following commands from a booted server to set the server to boot from USB:
    cmos -c bootdev sda1
    reboot

The Re-Install Process

Re-installation of your server takes approximately 30 Mins. During the course of the installation, the LCD will print:
"Booting Stage 2".

 


 

Notes

SB2 Update

Please note that the server will automatically reboot when you have installed the sb2_upgrade package.This is in order to start the new ROM and new kernel.  If you have any problems after the update, please see our troubleshooting section.