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 HPUX
bootconf
bootconf(4) Kernel Interfaces Manual bootconf(4)NAME
bootconf - boot device configuration table
DESCRIPTION
The file contains the address and disk layout type of the system's boot devices or lif volumes. It is used by the and HP-UX kernel control
scripts (fileset to determine how and where to update the initial boot loader. Normally the kernel's script queries the system's hardware
and creates the file. In rare cases when either the system configuration cannot be automatically determined or additional and/or alternate
boot devices should be automatically updated, the administrator must edit the file manually.
There is one line in the file for each boot device. Each line contains the following blank-separated fields in the order shown:
disk type A flag indicating how the file system(s) on the disk are laid out. The flag must be one of the following:
Indicates that the root disk is in LVM or VERITAS Volume Manager
(VxVM) format. If LVM or VxVM mirrors are used, then each of the "mirrors" must have its own line in the file.
Indicates that the root disk is in the
"whole disk" format with no partitions, but boot and swap space are reserved outside the file system.
device file The absolute path of the device special file that accesses the physical device where the boot area is located. For LVM root
disks, the device special file is the physical volume(s) returned by the command. For "whole disks" this is the device file
that references the entire disk.
Blank lines are permitted. Any line beginning with a is considered to be a comment.
DIAGNOSTICS
The Software Distributor log file contains diagnostic messages under the fileset if the file is incorrect. Most of the messages are self-
explanatory; a few warrant additional explanation:
If there are no other messages about
the file is probably empty. Otherwise, the file is not in the proper format, and the other messages will explain what the problem
is.
The specified device file does not point to a disk where there is a
lif which contains the file
Some character other than
or is in the first field of a line.
As of release 10.0, the boot areas in
must all be on the same type of disk layout.
There are characters after the
device file specification.
EXAMPLES
The boot area is on an LVM root disk:
l /dev/disk/disk7_p2
The boot area is on a whole disk layout:
w /dev/disk/disk7
WARNINGS
All of the boot devices in the file must have the same disk layout.
AUTHOR
was developed by the Hewlett-Packard Company.
FILES SEE ALSO mediainit(1), hpux(1M), hpux.efi(1M), mkboot(1M), vgdisplay(1M), lif(4), intro(7).
documentation.
bootconf(4)