Technical article 127436

How can I create Emergency BOOT/ROOT recovery floppy images for my OpenServer 5.0.7V Virtual Machine and how can I then boot my Virtual Machine using these floppies under VMware ESX 3.5 and ESX(i) 3.5?

OpenServer 5.0.7

Written · Last revised

Problem

How can I create Emergency BOOT/ROOT recovery floppy images for my OpenServer 5.0.7V Virtual Machine and how can I then boot my Virtual Machine using these images?

Solution

This TA is divided into three sections:

1) Assigning a floppy drive to the virtual machine

2) Creation of the OSR507V Emergency BOOT/ROOT Recovery floppies

and

3) Booting from the OSR507V Emergency BOOT/ROOT Recovery floppies

1) Assigning a Floppy Drive to the Virtual Machine:
---------------------------------------------------
Please Note:

Before you start, it is highly recommended to add a Power-on Boot Delay of 10 seconds to the OSR507V VM.

This is important, as it will give us time to press ESC or F2. To do that, edit the OSR507VM VM settings. Under "Option" tab --> Boot Options, add 10000 millsec

1 - The ESX 3.5 Server has a physical attached Floppy drive and you want to connect to it from OSR507V

Note: This is not true in case of ESXi 3.5, as
      VMware ESXi does not support Guest OS VM access
      to its local attached Floppy drive.

- Edit the OSR507V VM Settings - Mark the "Floppy Drive 1" - Under "Device Type", choose "Host Device - /dev/fd0" Check "Connect at Power on" at the "Device Status"

- Then click "OK" to save the settings.

- Power on OSR507V VM and you will now have access to the physical Floppy drives via /dev/fd0

2 - You want to connect to the physical Floppy drive that is
    attached to your windows desktop which is running the VMware
    VI/VC client.
- Edit the OSR507V VM Settings

- Mark the "Floppy Drive 1" Under "Device Type", choose "Client Device"

- Then click "OK" to save the settings.

- Power the OSr507V VM and at the OSR507V VM POST BIOS messages, press the ESC button in order to get the "Boot Menu".

- On the top of the OSR507V Virtual Console, you will see a "Connect Floppy 1" button. Choose "Connect from A: "

- Then from the "Boot Menu", boot from the Hard Drive.

You can now connect to your Desktop Floppy drive via /dev/fd0.

3 -   You want to connect to a Floppy image that
      resides on ESX/ESXi 3.5 server

- Edit the OSR507V VM Settings - Mark the "Floppy Drive 1" Under "Device Type", choose "use existing floppy image in datastore". Then click on the "Browse" button.

A "Browse Datastores" pop up windows will appear.

Browse under vmimages --> Floppies (Or wherever that floppy image "flp extension" resides).

See * below

And choose the Floppy image that you want to access.

The floppy image has to be in "flp" extension.

Check "Connect at Power on" at the "Device Status"

- Then click "OK" to save the settings.

Power on the OSR507V VM and you can now connect to the Floppy image via /dev/fd0.

4 -   You want to connect to a Floppy image that
      resides on your windows desktop which is
      running the VMware VI/VC client.
- Edit the OSR507V VM Settings

- Mark the "Floppy Drive 1" Under "Device Type", choose "Client Device"

- Then click "OK" to save the settings.

- Power the OSr507V VM and at the OSR507V VM POST BIOS messages, press the ESC button in order to get the "Boot Menu".

- On the top of the OSR507V Virtual Console, you will see "Connect Floppy 1" button.

For Floppy, choose "connect to floppy image"

Then browse to the location on your client desktop where the floppy image "flp - extension" file resides.

See * below

- Then from the "Boot Menu", boot from the Hard drive.

You can now connect to the Floppy flp image on your Desktop via /dev/fd0.

* Note, that in this case the floppy image needs be changed because two floppy images are created, boot.flp and root.flp

This will be detailed further in the notes below.

2) Creation of the OSR507V Emergency BOOT/ROOT Recovery floppies: ----------------------------------------------------------------- Please follow the below steps as root:

# mkdev fd

and follow the prompts to create specific Root and Boot Floppies on 1.44MB images as detailed in TA112505.

Differences depending on how you have selected your floppy device in the above Floppy Assignment section:

1 - This is a physical floppy on your VMware server.

2 - This is a physical floppy on your Windows PC.

It is recommended to format the floppy first when prompted during the "mkdev fd" process.

3&4 - This will consistent of two files. "root.flp" and "boot.flp".

It is recommended to touch or create a zero length file first which you can 'connect' your VMware floppy too, as described in the assignment process above.

Once the first "root.flp" has been created by the "mkdev fd" process, "disconnect" this first floppy and re-connect using the second file called "boot.flp".

You can then continue the "mkdev fd" process to create the second floppy.

It is not recommended to format the floppies first.

At the end you should have two flp files greater than zero length now.

Please note that the physical floppy can be a USB connected device as this is transparent to OpenServer5's /dev/fd0.

Once your Emergency Boot and Root disks are created place the Boot disk in your selected floppy drive and reboot your OSR507V VM.

3) Booting from the OSR507V Emergency BOOT/ROOT Recovery floppies:
------------------------------------------------------------------
Ensure the Emergency Boot floppy is in the selected drive and boot
your OSR507V VM.  Once booted, you will be prompted to insert your
second Emergency Root floppy.

Differences depending on how you have selected your floppy device in the above Floppy Assignment section:

1 - This is a physical floppy on your VMware server.

2 - This is a physical floppy on your Windows PC.

3&4 - This will consistent of two files. "root.flp" and "boot.flp".

You will select the first "boot.flp" floppy image, created above and
assigned as described in the first section.  When prompted for the
Root floppy disk during the boot process, "disconnect" this floppy
and "connect" using the "root.flp" floppy image.  Then continue.

If this fails then it's likely the "connection" to the second floppy had not fully completed and time ENTER was pressed to start reading from the second floppy.

When you see the # prompt, you should be able to mount the hard disk with:

# mount /dev/hd0root /mnt
# mkdir /mnt/stand
# mount /dev/boot /mnt/stand

When exiting, remember to "umount" each filesystem before rebooting.

More information can be found at TA104767.

NOTES:    If you have created your floppies on physical media then they can be
          transferred to a floppy image and vice versa with the following
          commands:
From a physical floppy:
# dd if=/dev/fd0 of=[root/boot].flp bs=1440k
To a physical floppy:
# dd if=[root/boot].flp of=/dev/fd0 bs=1440k
NOTES:    If you have not created the OSR507V Emergency Root and Boot Floppies
          and would simply like to have a pre-created set available to you then
          please download them from:
ftp://ftpput.sco.com/tmp/support/OSR507V/fd/OSR507V_lsil_boot.flp
and:
ftp://ftpput.sco.com/tmp/support/OSR507V/fd/OSR507V_lsil_root.flp

From the Xinuos technical article database, record 127436. Reproduced with permission. The original is at www.sco.com/ta/127436, which is reachable but blocked from search engines.

Next step

Need this fixed rather than explained?

Tell us the release, what the system runs and what it is doing. We will reply by email with what we would do next.

  • You deal with the people who do the work
  • No obligation, and no upgrade required before we will help
  • We tell you plainly if something is not worth doing

Send an enquiry

We reply by email. If a server is down, say so in the first line. You can also write to help@scoexpert.com.