Problem
Is there a way to load an additional BTLD that is not part of the Openserver507 Install CD via CD-ROM during OSr507 installation?
The problem is that I have a server that has no legacy 1.44 MB floppy drive, therefore I can't load the BTLD via the legacy floppy drive.
I also not able to load the BTLD via a USB floppy drive even though trying out TA125420, TA126653 & TA126363 for some reason or other (Might be a BIOS and USB issue).
How can I then in this situation be able to install SCO OpenServer 5.0.7 and be able to load an additional BTLD via CD-ROM?
NOTE: SCO Support have prepared some pre-built CD ISO images to help you
install and these are available from:TA126839, "Where can I get pre-created Openserver 5.0.7 Boot CD image that contains commonly used BTLD?"
However, if you want to or need to build your own please see the following:
Before we go into detailed solution, we need to understand how the Server BIOS boots from a bootable CD.
Background History on PC boot process via CD-ROM:
------------------------------------------------A modern PC BIOS will search for boot code on a ISO 9660 CD according to the El Torito specification.
If the CD contains bootable code, the BIOS will assign a BIOS drive number to the CD drive. The drive number assigned is either 80 (hard disk emulation), 00 (floppy disk emulation) or an arbitrary number if the BIOS should not provide emulation.
Emulation allows older operating systems to be booted from a CD, by making it appear to them as if they were booted from a hard or floppy disk.
More info is about El Torito specification and how booting up (bootstrapping) process that starts operating systems, can be found under:
http://en.wikipedia.org/wiki/El_Torito_(CD-ROM_standard)
http://en.wikipedia.org/wiki/BootingSCO OpenServer 5.0.7 Install boot CD:
-------------------------------------The OpenServer 5.0.7 install CD has a hidden 2.88 MB boot image (boot code).
This boot image contains the following files and directories:
-r--r----- 2 bin bin 52985 May 20 2005 ahslink
-r-------- 1 bin bin 74648 May 20 2005 boot
drwxrwxrwx 3 bin bin 48 May 20 2005 etc
-r--r----- 2 bin bin 52985 May 20 2005 link
drwxrwxrwx 4 bin bin 64 May 20 2005 opt
-rw-r--r-- 1 bin bin 154182 May 20 2005 rootFS
-rw-r--r-- 1 bin bin 1652840 May 20 2005 unix
-rw-r--r-- 1 root sys 648826 May 20 2005 unix.smallmemThe "ahslink, boot, link, rootFS" are all non standard files but machine (BIOS) executable programs.
If you run the file command on one of the files, you will get this output:
# file boot
boot: Microsoft a.out separate pure segmented standalone
word-swapped 86 executableThe "unix" file, 1.6 MB, is OSR507 install kernel that has all the BTLD statically linked for disk controllers that are part of the OSr507 install CD.
(The "unix.smallmem" is used when installing on low memory machine like Notebooks).
When the Server is booted, the OSR507 CD boot image gets get loaded via the server BIOS into the memory and making it appear as if booted via floppy disk "fd(64)".
This is where you get the OSR507 "boot:" prompt.
If you had a disk controller that needed a new or updated BTLD for installation, then you added this boot string:
:defbootstr link=<BTLD Name> btld=fd(64)At this stage of OSR507 Installation, the boot process is still executing programs and instructions that are located in the OSr507 loaded 2.88 MB boot image (boot code).
By adding the defbootstr string with the BTLD link, the boot code process will execute the following instructions:
DEFBOOTSTR=fd(64)unix ramdisk=fd(64)rootFS root=ram(7) ram.preload=7 swap=none dump=none nbuf=3 isl.S=3 isl.pause fdimg btld=fd(64)
From the above, the main points are: fd(64)unix
Load the OSR507 install kernel file "unix" (aprox 1.6 MB) from the loaded 2.88 boot image
ramdisk=fd(64)rootFSRoot filesystem will be created on the RAM disk using the rootFS file located in the boot image.
root=ram(7) Root level will be on the Ram disk.
btld=fd(64) Request a BTLD from the boot image (CD) drive fd(64).
- Note: If "btld=fd(64)" was left out in the defbootstr, then the boot sequence will default loading the BTLD from a floppy disk drive fd(65)
The boot sequence will look for the new BTLD in the 2.88 MB boot image fd(64) and loads / links it to the install kernel.
For more information about the OSr507 boot process, please read:
http://osr507doc.xinuos.com/en/man/html.HW/boot.HW.htmlSo if we want the boot code to load the BTLD from the boot image (not from the floppy drive), then we need to copy the BTLD on to that boot image.
Therefore we need to create a special OSr507 boot CD that will ONLY contain the 2.88 boot image with additional BTLD on it and boot from that CD and load the BTLD from it.
We shall refer to this customized OSR507 boot CD with BTLD in this TA as "BTLD Boot CD"
Solution
These are the steps on how to create a BTLD Boot CD:
- Note: In this example, we will load the latest OSR507
"lsil" BTLD ver. 1.04.09, that supports the LSI
1068 SAS controller, from a CD-ROM.If you do not want to create these yourself then a number of pre prepared images are now available with:
TA126839, "Where can I get pre-created Openserver 5.0.7 Boot CD image that contains commonly used BTLD?"
To build the BTLD Boot CD manually:
1- You need July 2005 cut of OSR507 Install CD Media.
http://www.sco.com/support/update/download/release.php?rid=2182- You need either a UW714 or OSR507 or OSR600 machine with "cdrecord" packages installed on it. As we will need to use the "mkisofs" utility from it.
Cdrecord software is part of: UW714 MP3 OSR600 Base OSR507 MP5
3- You need the "lsil" BTLD (or whatever BTLD you want to use) copied as an 1.44 MB floppy image to one of the above SCO unix boxes.
In our example, the latest "lsil" BTLD ver. 1.04.09 is available to download from:
http://www.sco.com/support/update/download/release.php?rid=192(The latest OSR507 lsil BTLD is on the btld1.img image)
4- Download the extracted 2.88 MB OSr507 boot CD image from:
ftp://ftpput.sco.com/tmp/support/ISO/iso-btld/osr507boot-CD.imgWe have already extracted this hidden boot image from SCO OpenServer 5.0.7 install CD and deleted the unix.smallmem file in order to free 640Kb of disk space on the boot image.
If we have not deleted the unix.smallmem file, the content of the 2.88 MB boot image would add to 2.75 MB in size, thus leaving us with disk space of only 130 Kb, which might not be enough to copy a new BTLD to it.
By deleting the unix.smallmem, we now have 770Kb of free space to play with.
5- Copy the btld1.img (from step 3) to /tmp and osr507boot-CD.img (from step 4) to /tmp/image on one of the SCO Unix boxes in step 2 with cdrecord package installed.
Please Note:If you have the btld1.img already as a floppy image on a floppy disk, then no need to copy the btld1.img to /tmp/image.
6- Marry and mount both of the above images:
# marry -a /tmp/image/osr507boot-CD.img
# mount /dev/marry/tmp/image/osr507boot-CD.img /mnt# mkdir /mnt2 (create a new mnt2 directory)
# marry -a /tmp/btld1.img
# mount -r /dev/marry/tmp/btld1.img /mnt2Please Note: If you have the btld1.img already as a floppy image on a floppy disk, then you only need to run the mount command:
# mount -r /dev/fd0 /mnt27- The list of both /mnt and /mnt2 will look like:
/mnt
-r--r----- 2 bin bin 52985 May 20 2005 ahslink
-r-------- 1 bin bin 74648 May 20 2005 boot
drwxrwxrwx 3 bin bin 48 May 20 2005 etc
-r--r----- 2 bin bin 52985 May 20 2005 link
drwxrwxrwx 4 bin bin 64 May 20 2005 opt
-rw-r--r-- 1 bin bin 154182 May 20 2005 rootFS
-rw-r--r-- 1 bin bin 652840 May 20 2005 unix/mnt2
drwxr-xr-x 5 8888 100 80 Jul 14 2006 aacraid
drwxr-xr-x 5 8888 100 80 Jul 14 2006 ad320
drwxr-xr-x 4 8888 100 64 Jul 14 2006 iir
drwxr-xr-x 2 8888 100 48 Jul 14 2006 install
drwsr-sr-x 4 8888 100 64 Jul 14 2006 lsil
drwxr-xr-x 4 8888 100 64 Jul 14 2006 slha
drwsr-sr-x 5 8888 100 96 Jul 14 2006 wdNow copy the whole "lsil" directory and its contents from /mnt2 to /mnt:
# cp -rp /mnt2/lsil /mnt
# chown -R root:sys /mnt/lsil/mnt will now have the following list:
-r--r----- 2 bin bin 52985 May 20 2005 ahslink
-r-------- 1 bin bin 74648 May 20 2005 boot
drwxrwxrwx 3 bin bin 48 May 20 2005 etc
-r--r----- 2 bin bin 52985 May 20 2005 link
drwsr-sr-x 4 root sys 64 Jul 14 2006 lsil
drwxrwxrwx 4 bin bin 64 May 20 2005 opt
-rw-r--r-- 1 bin bin 154182 May 20 2005 rootFS
-rw-r--r-- 1 bin bin 1652840 May 20 2005 unixPlease Note:If you had a HP Proliant SAS server and needed to add the OSr507 "hpsas" ver. 5.770a on to the boot image. do the same steps as above.
The content (list) of the HP EFS 7.770a BTLD is:
drwx------ 4 root sys 64 Jan 11 2007 ad160
drwx------ 4 root sys 64 Jan 11 2007 ciss
drwx------ 4 root sys 64 Jan 11 2007 CUAD160
drwx------ 3 root sys 48 Jan 11 2007 CUCISS
drwx------ 3 root sys 48 Jan 11 2007 CUHPSAS
drwx------ 4 root sys 64 Jan 11 2007 CULSI
drwx------ 4 root sys 64 Jan 11 2007 hpsas
drwx------ 2 root sys 48 Jan 11 2007 install
drwx------ 4 root sys 64 Jan 11 2007 lsil# cp -rp /<mount point>/hpsas /mnt8- Unmount and de-marry the two images:
# umount /mnt
# marry -d /dev/marry/tmp/image/osr507boot-CD.img
# umount /mnt2
# marry -d /dev/marry/tmp/btld1.img9- After we added the "lsil" BTLD to the boot image, we need to create a bootable iso image using the mkisofs command:
# mkisofs -r -l -v -o /tmp/boot.iso -b osr507boot-CD.img /tmp/imagemkisofs 2.01 (i386-pc-sco3.2v5.0.7)
Scanning /tmp/image
Writing: Initial Padblock Start Block 0
Done with: Initial Padblock Block(s) 16
Writing: Primary Volume Descriptor Start Block 16
Done with: Primary Volume Descriptor Block(s) 1
Writing: Eltorito Volume Descriptor Start Block 17
Size of boot image is 5760 sectors -> Emulating a 2880 kB
floppy
Done with: Eltorito Volume Descriptor Block(s) 1
Writing: End Volume Descriptor Start Block 18
Done with: End Volume Descriptor Block(s) 1
Writing: Version block Start Block 19
Done with: Version block Block(s) 1
Writing: Path table Start Block 20
Done with: Path table Block(s) 4
Writing: Directory tree Start Block 24
Done with: Directory tree Block(s) 1
Writing: Directory tree cleanup Start Block 25
Done with: Directory tree cleanup Block(s) 0
Writing: Extension record Start Block 25
Done with: Extension record Block(s) 1
Writing: The File(s) Start Block 26
Total translation table size: 2048
Total rockridge attributes bytes: 342
Total directory bytes: 0
Path table size(bytes): 10
Done with: The File(s) Block(s) 1441
Writing: Ending Padblock Start Block 1467
Done with: Ending Padblock Block(s) 150
Max brk space used 4000
1617 extents written (3 MB)Take the /tmp/boot.iso file and burn it onto a recordable CD media either using "cdrecord" under UW714/OSr507/OSr600 if the CD drive on the server is a recordable one.
Or copy it to a windows box and use a burning software, like nero, to burn onto a recordable CD media.
We now have created a BTLD Boot CD!INSTALLING SCO OPENSERVER 5.0.7 WITH YOUR NEW BTLD BOOT CD:
10- Now to install SCO OpenServer 5.0.7.
You need both the BTLD Boot CD with the new "lsil" BTLD and the July 2005 cut of SCO OpenServer 5.0.7 install CD.
Boot the server with the BTLD Boot CD.
At the boot prompt, type "dir" to check if "lsil" is there:
boot
: dir ( or dir fd(64) )you should get the following output:/:
. .. boot link unix rootFS etc opt
ahslink lsil .ilog0000 .slog000and "dir lsil" should bring the following output:
boot
: dir lsillsil:
. .. driver installThis confirms that the "lsil" BTLD is on the BTLD Boot CD.
Now add the following install boot stringboot
: defbootstr link=fd(64)lsil <RETURN>Please Note:"link=fd(64)lsil" is equvilant to "link=lsil btld=fd(64)"Should you get:"Sorry, that volume does not contain the lsil package."
Then it could be poor image or try:
boot
: defbootstr link=lsil btld=fd(64)At the message below, just hit the <RETURN>Please insert the fd(64)lsil volume and press <Return> or 'q' to quit: <RETURN>
The boot sequence will then load the "lsil" BTLD from the BTLD Boot CD and you will notice that the "lsil" was successfully loaded and linked to the install Kernel.
The LSI 1068 SAS controller has detected with the attached HD.
Continue the installation and confirm with OK on the screen message:
Please insert (lsil) package BTLD disk into the floppy drive so that it can be extracted onto the hard disk for incorporation into the link-kit.
at the "Media device to be used" screen, remove the BTLD Boot CD and insert the SCO OpenServer 5.0.7 Install CD.
Regardless of any further suggestions, there will be no need to insert the new BTLD Boot CD again.
Continue the installation with keyboard, license and disk configuration....etc
When the installation gets to the point where it wants to load "lsil" BTLD into link-kit, you will then get this error message:
The BTLD package will now be extractedmount: Bad addressPlease select the floppy device you are using(1) /dev/fd0
(2) /dev/fd1choose option (2) and you will be asked to insert the lsil BTLD floppy disk again:
Please insert the floppy for BTLD package: lsil and press <Return>:
Press RETURN and you will then get this message:
mount: Bad address, Could not mount the BTLD floppyYou may:(a) try again (b) abort BTLD load, but continue installation (c) abort the installation
Respond with one of (a,b,c):choose option "b".We will later load the lsil BTLD into the link-kit at the post installation.
The installation will continue and OpenServer 5.0.7 will get installed on to the Hard Drive.
Please Note: The finished installed OpenServer 5.0.7 kernel will not have the "lsil" BTLD linked to it. So if you now try to reboot, OSR507 will fail to boot from the HD.
11- When the installation has finished, remove the SCO
OpenServer 5.0.7 Install CD and insert the BTLD Boot
CD again and reboot the server.At the Boot prompt, enter either one of the following boot string:
boot
: defbootstr link=fd(64)lsil root=hd(42)
Srom=wd(0,0,0,0)Boot using the install unix kernel on the BTLD Boot CD (OSR507 install kernel), bind the lsil to the install kernel, CD-ROM drive attached to PRIM IDE controller as master and use the root filesystem on the Hard Drive hd(42) as the landing level (OSr507 is already installed on the hard drive).
Please Note: The Srom in the boot string is VERY important
to to add. Failing to add it, will result in
failure accessing the CD-ROM device /dev/cd0.Or:boot
: link=fd(64)lsil hd(40)unix.install root=hd(42)
Srom=wd(0,0,0,0)Same as above but using the unix.install kernel on the hard drive hd(40) instead.
Please Note: If you use the regular unix kernel (unix / unix.old or even unix.safe), which all reside in /stand filesystem, you will get this message:
bootlocore: Out of low (below 1Mb) memory! No memory for string table No (or cannot load) kernel hd(40)unix symbol table Link failed, press <Return> to continue or q to quit:
This is because the regular unix kernel is fully linked and you won't have enough memory.
Therefore, we use "unix.install", as it will fit in the memory.
Continue as before and hit RETURN at the message
Please insert the fd(64)lsil volume and press <Return> or 'q' to quit: <RETURN>
to load the "lsil" BTLD.At the INIT: SINGLE USER MODE, enter the root password to enter into system maintenance mode.
Mount the BTLD Boot CD and install the "lsil" BTLD:
# mount /dev/cd0 /mnt(If you see a "Cannot stat" error message attempting to access the cdrom then it is suggested that you may need to run: 'mkdev cdrom' to ensure the cdrom is correctly configured).
# mkdir /mnt2
# marry -a /mnt/osr507boot-CD.img
# mount -r /dev/marry/mnt/osr507boot-CD.img /mnt2
# btldinstall /mnt2You will be given the LSI lsil BTLD on the list. Press RETURN to choose the default "lsil".
The BTLD lsil gets loaded and then OpenServer 5.0.7 will tell you that the "lsil" is already installed and you are requested to proceed with "y" to install and over write the old "lsil" driver or "n" for NO and exit.
Proceed with "y" to update the "lsil" driver and then "y" to relink the kernel if "btldinstall" does this.
If not, run:# /etc/conf/cf.d/link_unix -yto relink the Unix kernel with your btld driver included.
Finally. un-marry and unmount the BTLD Boot CD and reboot:
# umount /mnt2
# marry -d /dev/marry/mnt/osr507boot-CD.img
# umount /mnt
# init 6SCO OpenServer 5.0.7 is now installed on a server where a BTLD was loaded via CD-ROM during installation on a server with no Legacy Floppy drive or USB floppy drive.
TROUBLESHOOTING:After loading the "hwconfig" I see the following error:
/cdromFS/opt/archives/vol.000.000which implies a hardware problem with the CDROM or with the media.
See also
TA126839, "Where can I get pre-created Openserver 5.0.7 Boot CD image that contains commonly used BTLD?"