Sponsored Content
Operating Systems SCO stage 1 boot failure: error loading hd (40)/boot Post 302441439 by jgt on Friday 30th of July 2010 05:44:45 PM
Old 07-30-2010
Deeper doodoo.
The 5.0.6 Media kit is not available on SCO's web site.
Download the 5.0.7 CD, and install it. You can install it for a 30 day evaluation, then follow the instructions to add a second disk.
Once you have salvaged the data that you need from the old disk, you will have to decide what to do if you don't have a 5.0.6 media kit, and or license data.
5.0.7 includes the program 'cdrecord' which will allow you to create standard CD or DVD disks. You can write to dual layer DVD's (9.4GB) using an LG brand DVD writer that sells for about 25 dollars US.
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Loading windows on a dual boot

I want to dual-boot Windows 98 and Redhat 7. My scheme for doing this is to partition into: A FAT32 partition for windows A Linux partition for root A swap partition A boot partition My question is: At what point do I setup windows on the FAT partition? Would I do it from the command line... (5 Replies)
Discussion started by: Furtoes00
5 Replies

2. Solaris

solaris boot problem boot error loading interpreter(misc/krtld)

When I installed the SOLARIS 10 OS first time, the desktop would not start up, this was because of network setup. Reinstalled worked. After a week due to some problem I had to reinstall OS, installation went fine and but when i reboot I get this error. cannot find mis/krtld boot error loading... (0 Replies)
Discussion started by: johncy_j
0 Replies

3. Solaris

Solaris 10 - boot CD not loading

I recently downloaded solaris 10 disk images and I am trying to load it onto my system. I cannot get the PC to load off of the disk 1 image. I created the disk using windows easy cd creator just like the download instructions said, but i get a boot failure. :eek: Any ideas??? ( BIOS ok !!! ) ... (10 Replies)
Discussion started by: spider123
10 Replies

4. Linux

Boot failure

Hi all I used a dual boot operating system and it works fine for me. Now , i install a Ati radeon 9250 Agp card on my system and this results in boot failure of fedora 6. The graphics card is working fine with windows XP , i.e i have no compatibility issues.The system also refuses to boot when i... (2 Replies)
Discussion started by: joshighanshyam
2 Replies

5. Solaris

INT18 boot failure

I installed solaris virtually and tried to format the partitions .. I dont know what went wrong, It got rebooted and hangs in the screen "No partitions" and after pressing Enter button it goes to "INT18 boot failure" and hangs there once again . Could any one of you suggest why this has happened... (3 Replies)
Discussion started by: priky
3 Replies

6. Solaris

Boot failure

I have installed Solaris 10 OS in Sun Virtual Box that uses x86 32 bit system. After an abnormal shutdown i'm getting the following message on the console when i try to boot. SunOS Release 5.10 Version Generic_127128_11 32-bit Copyright 1983-200 Sun Microsystems, Inc. All rights reserrved. Use... (3 Replies)
Discussion started by: Sesha
3 Replies

7. Solaris

Loading Kernel module at boot

Is there any link/tutorial on loading Solaris kernel modules at boot time?? (0 Replies)
Discussion started by: unisolin
0 Replies

8. Solaris

Failure to boot v445

Hi Guys, I have a small problem with a v445 which I have been informed will only boot with the reconfigure option enabled. It is attached to HP SAN storage using qla2300 FCA's with a Veritas encapsulated rootvoldg (No Laughing here please) when I try a reboot I get the following error. ... (5 Replies)
Discussion started by: gull04
5 Replies

9. UNIX for Dummies Questions & Answers

boot up failure unix sco after power failure

hi power went out. next day unix sco wont boot up error code 303. any help appreciated as we are clueless. (11 Replies)
Discussion started by: fredthayer
11 Replies

10. SCO

FATAL BOOT ERROR: Can’t load stage 3

I'm under huge pressure to recover data from an old server that only gets booted very infrequently. The data on it is urgently required - isn't always??! .. Server is an HP DL380G5 which is running SCO Unixware 7.11 .. It has 3 partitions in a RAID 5 Configuration: 1 of 10GB (I assume it... (19 Replies)
Discussion started by: BernP
19 Replies
re-preinstall(1M)					  System Administration Commands					 re-preinstall(1M)

NAME
re-preinstall - installs the JumpStart software on a system SYNOPSIS
cdrom-mnt-pt/Solaris_XX/Tools/Boot/usr/sbin/install.d/re-preinstall [-m Solaris_boot_dir] [-k platform_name] target-slice DESCRIPTION
re-preinstall installs the JumpStart software (preinstall boot image) on a system, so you can power-on the system and have it automatically install the Solaris software (perform a JumpStart installation on the system). When you turn on a re-preinstalled system, the system looks for the JumpStart software on the system's default boot disk. All new SPARC systems have the JumpStart software already preinstalled. The XX in Solaris_XX is the version number of the Solaris release being used. You can use the re-preinstall command in several ways. The most common way is to run re-preinstall on a system to install the JumpStart software on its own default boot disk. This is useful if you want to restore a system to its original factory conditions. (See the first procedure described in EXAMPLES.) You can also run re-preinstall on a system to install JumpStart software on any attached disk (non-boot disk). After you install the Jump- Start software on a disk, you can move the disk to a different system and perform a JumpStart installation on the different system. (See the second procedure described in EXAMPLES.) re-preinstall creates a standard file system on the specified target-slice (usually slice 0), and re-preinstall makes sure there is enough space on the target-slice for the JumpStart software. If sufficient space is not available, re-preinstall fails with the following message: re-preinstall: target-slice too small xx Megabytes required You can use the format(1M) command to create sufficient space on the target-slice for the JumpStart software. OPTIONS
The following options are supported: -k platform_name Platform name of the system that will use the disk with the JumpStart software. The default is the platform name of the system running re-preinstall. (Use the uname(1) command (-i option) to determine a system's platform name.) -m Solaris_boot_dir Absolute path to the Solaris_XX/Tools/Boot subdirectory of a mounted Solaris CD or a Solaris CD copied to disk that re-preinstall uses to install the JumpStart software. The default is root (/), which is where the Solaris CD is mounted in single-user mode. OPERANDS
The following operands are supported: target-slice Device name of the disk slice where the JumpStart software will be installed (usually slice 0), for example, c0t3d0s0. EXAMPLES
Example 1: Installing the JumpStart Software on a System's Own Default Boot Disk The following procedure installs the JumpStart software on a system's own default boot disk: 1. From the ok prompt, boot the system from the Solaris media CD or DVD in single-user mode: ok boot cdrom -s 2. The following command installs the Jumpstart software on the System default boot disk, c0t0d0s0 on a Solaris 9 system: example# /usr/sbin/install.d/re-preinstall c0t0d0s1 3. Reboot the slice: example# reboot disk:b Example 2: Installing the JumpStart Software on a System's Attached (non-boot) Disk The following procedure installs the JumpStart software on a system's attached (non-boot) disk: 1. Mount the Solaris CD or DVD if vold(1M) is not running or CD or DVD is not mounted. 2. Use the format(1M) command to determine the target-slice where JumpStart will be installed. 3. Use the uname(1) command (-i option) to determine the platform name of the system that will use the re-preinstalled disk 4. Run re-preinstall with the -m Solaris_boot_dir option if the Solaris CD or DVD is not mounted on /cdrom. The following command installs the JumpStart software on the system's attached disk for a system with a Sun4u kernel architecture, and it uses the Solaris CD or DVD mounted with vold(1M) on a Solaris 9 system: example# /cdrom/cdrom/s1/usr/bin/install.d/re-preinstall -m /cdrom/cdrom/s1 -k sun4u c0t2d0s0 EXIT STATUS
The following exit values are returned: 0 Successful completion. 1 An error has occurred. ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWcdrom (Solaris CD, | | |SPARC Platform Edition) | +-----------------------------+-----------------------------+ SEE ALSO
uname(1), eeprom(1M), format(1M), mount(1M), vold(1M), attributes(5) Solaris 10 Installation Guide: Basic Installations SunOS 5.10 9 Apr 2002 re-preinstall(1M)
All times are GMT -4. The time now is 02:48 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy