Technical article 119107

How do I re-write the Master Boot Record?

OpenServer 6.0.0UnixWare 7.1.1UnixWare 7.1.3UnixWare 7.1.4

Written · Last revised

Problem

I have had to restore my server using the Emergency Recovery Disks and Emergency Recovery Tape onto a fresh disk.

However, when the server boots I get the error message "No OS found" or equivalent, or the cursor just blinks and does not proceed further.

Cause

The emergency recovery restore will restore data to a fresh disk but will not write the Master Boot Record onto the disk.

This is because there may be a boot loader there already in the Master Boot Record, for example, "grub" or System Commander, if there are multiple operating systems on the disk.

Solution

This problem has been reported to SCO Engineering.

A workaround is to use the following steps:

	   a)   Boot from the Emergency Recovery Floppies
	   b)   Mount the filesystems from the Emergency Recovery menu
	   c)	Enter the command:
	# chroot /mnt /bin/sh
	   d)	Enter the command:
		# fdisk

and select option 0 (overwrite system master boot code) to ensure that the Master Boot Record is written again.

e) "exit" the "chroot" and the "exit" the shell.

f) Unmount the filesystems from the Emergency Recovery menu

	   g)	Re-boot the server.
NOTE:	It has also been feature requested that a prompt is presented
        for creation of the Emergency Disks during the initial installation of
        the operating system.

See also

	emergency_disk(1M)
	emergency_rec(1M)
	TA109633, "UnixWare 7 emergency disks."

TA116163, "How do I install UnixWare7 on a Compaq ML Series server?"

TA116882, "How can I improve the restore performance during an emergency recovery procedure?"

From the Xinuos technical article database, record 119107. Reproduced with permission. The original is at www.sco.com/ta/119107, 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.