Installing OpenSolaris on Sun v120 Post: 302298875

5 More Discussions You Might Find Interesting

1. Solaris

Weird behavior on a Sun Fire V120 running solaris 10.

All, After a power loss I went to power on our sun fire v120 that is running solaris 10 and now it will not boot. I tried power cycling it from the lom and pulling the cord but nothing works. All it does is after a power cycle it will start to boot and then start to spit out a bunch of hex...

2. Solaris

Help - Accessing Sun Fire V120 A/LOM

Hi All, My company has three V120 servers and two V245 servers. Currently we access ALOM on v245 thru NET MGT port. There are no NET MGT on V120. We use to access A/LOM on the V120s thru Windows Hyper Terminal connected to the Serial A port of v120. Since all of our Windows boxed are...

3. Solaris

Sun Fire v120 memory compatibility

Hi, I recently acquired an old Sun Fire v120 from work. I plan to play around with this at home whilst I'm studying for my SCSA exams. Only problem is it currently has no memory installed. I believe the memory modules required are 168 pin PC133 DIMMs. Unfortunately, the original Sun modules are...

4. Solaris

Error while installing zone in opensolaris

while installing zone this error is coming zoneadm -z test install ERROR: Error: no zonepath dataset. Steps done to create one sample zone zonecfg -z test create set zonepath=/zones/test set autoboot=true verify commit exit zoneadm -z test install ERROR: Error: no zonepath dataset....

5. Solaris

Clone Production Server (Sun v120)

It's a DHCP server. We want to make a clone for fail over purpose since there are some identical systems available here. We do have a secondary DHCP server. Hardware: Sun v120. OS: Solaris 9. Two disks without array, /var and /opt on the secondary disk. How can I clone the system via network...

LEARN ABOUT DEBIAN

installboot

installboot(1M)                                                                                                                    installboot(1M)

NAME

       installboot - install bootblocks in a disk partition

SYNOPSIS

       installboot bootblk raw-disk-device

       The boot(1M) program, ufsboot, is loaded from disk by the bootblock program which resides in the boot area of a disk partition.

       The  ufs  boot objects are platform-dependent, and reside in the /usr/platform/platform-name/lib/fs/ufs directory. The platform name can be
       found using the -i option of uname(1).

       The installboot utility is a SPARC only program. It is not supported on the  architecture.  users should use installgrub(1M) instead.

       bootblk         The name of the bootblock code.

       raw-disk-device The name of the disk device onto which the bootblock code is to be installed; it must be a character device which is  read-
                       able and writable. Naming conventions for a SCSI or IPI drive are c?t?d?s? and c?d?s? for an IDE drive.

       Example 1: Installing UFS Boot Block

       To install a ufs boot block on slice 0 of target 0 on controller 1 of the platform where the command is being run, use:

              example# installboot /usr/platform/`uname -i`/lib/fs/ufs/bootblk 
                   /dev/rdsk/c1t0d0s0

       /usr/platform/platform-name/lib/fs/ufs

           directory where ufs boot objects reside.

       /platform/platform-name/ufsboot

           second level program to boot from a disk or CD

       See attributes(5) for descriptions of the following attributes:

       +-----------------------------+-----------------------------+
       |      ATTRIBUTE TYPE         |      ATTRIBUTE VALUE        |
       +-----------------------------+-----------------------------+
       |Availability                 |SUNWcsu                      |
       +-----------------------------+-----------------------------+

       od(1), uname(1), boot(1M), init(1M), kadb(1M), kernel(1M), monitor(1M), reboot(1M), rpc.bootparamd(1M), init.d(4), attributes(5)

WARNINGS

       The installboot utility fails if the bootblk or openfirmware files do not exist or if the raw disk device is not a character device.

                                                                    11 Apr 2005                                                    installboot(1M)