Your boot device in the OBP still has you booting from the first disk, if you update the boot-device you should boot from the second disk ( the U8 BE ).
My incliniation would be to luactivate again, then check boot-device. If it is not updated then manually update.
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)
Hello,
I started the upgrade using LiveUpgrade. I am using Solaris 10 instalation CDs (5 CDs). My server is Enterprise 3500 - SPARC.
1) lucreate -c first_disk -m /:/dev/dsk/c0t11d0s7:ufs -n second_disk
...
luupgrade -u -n second_disk -s /cdrom/cdrom0/s0
WARNING: <5> packages failed to... (0 Replies)
I got this output from a system running solaris 10 :
# lustatus
BE_name Complete Active ActiveOnReboot CopyStatus
--------------------------------------------------------------------------------
oldvol yes yes yes -
newvol no no no -
bigvol no no no -
#
How do i remove (or... (1 Reply)
I am trying to install Solaris x86 using the Jumpstart server. I run the add_install_client command with appropriate options, and reboot my x86 Target box. The installation starts fine and unattended. After the installation completes and the target goes for a re-boot, it does not boot from the HDD... (9 Replies)
Hi,
I am running into a some problems creating a dual boot system of 2 solaris instances using ZFS file system and I was wondering if someone can help me out.
First some back ground. I have been asked to change the file system of our server from UFS to ZFS. Currently we are using Solaris... (3 Replies)
I am not a Solaris maven.
I've read and read and read the docs, and I just don't get it, so I'm here to ask for clarification.
I have a T2000/Solaris10u8. It has three drives. Drive 0 and Drive 1 are mirrored with metaxxxxx. Drive 2 has some untouchable data. It hasn't been treated nicely... (3 Replies)
After getting the new BE created and activating the new BE with luactivate command, OS is still booting with OLD BE.
Steps followed below..
bash-3.2#
bash-3.2# lustatus
Boot Environment Is Active Active Can Copy
Name Complete Now On Reboot... (3 Replies)
Hi all,
I have got a few questions on the above topic ->
q1) if my intention for creating an ABE is just to use for patching / patchset update -
e.g. ./installpatchset -B secondboot --s10patchset
luactivate secondboot
What is the recommendation that my ABE should consist of ?... (5 Replies)
Hello,
I have a problem with my machine that won't boot properly.
The story is that I installed a software called apcupsd, which is a control application for my APC battery UPS. I have used version 3.14.10 earlier, but as part of restoring my previously crashed os harddrive I wanted to... (18 Replies)
Discussion started by: Zorken
18 Replies
LEARN ABOUT XFREE86
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)