01-28-2013
What is the boot device displayed on the screen? Maybe it is trying to boot from network not from disks?
Was that server boots without troubles before?
10 More Discussions You Might Find Interesting
1. Solaris
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
2. AIX
I've got an RS6K B50, and i've installed AIX 5.3, TL5. It installs fine, the only customisations i make to the BOS are to change the locale / keyboard layout to UK, and to choose not to install graphical software.
I have no video card in this box, and i connect via a serial console (null modem... (4 Replies)
Discussion started by: craigp84
4 Replies
3. Solaris
Hi all,
I have a SUN server Sun-Fire-V890 running solaris 9, with a remote system console .
Both the IP adresses of the server and the console are in a private network (address 10.67.xxx).
For some reasons I need to give the access to the server from outside address 194.xxx, but I prefer that... (2 Replies)
Discussion started by: aribault
2 Replies
4. AIX
Hi guys,
Got a tiny bit of a problem on one of our servers here at work. I installed AIX 5.3 on the server and that went fine. Then I upgraded to ML 5300-05-01, but now the system just hangs on boot.
The system starts up and the monitor comes on in few minutes, but a few seconds later when... (6 Replies)
Discussion started by: drchris
6 Replies
5. AIX
To All:
I have this AIX machine (see boot process below). The problem was it hangs at:
The ctrmc Subsystem has been started. Subsystem PID is 11906..
I checked with other forums but their advise were just "strong punches in the air" with no specific explanation.
I really appreciate if... (6 Replies)
Discussion started by: aix_xia
6 Replies
6. Ubuntu
Boot process hangs after reaching the following line:
Adding 5853176k swap on /dev/mapper/mch-swap_1. Priority:-1 extents:1 across:5853176kUsing knoppix 6.2 as LiveCD, and mounting the partitions, I got the following:
# /etc/fstab: static file system information.
#
# Use 'blkid -o value -s... (0 Replies)
Discussion started by: fzaker
0 Replies
7. AIX
Hi all,
We have a old Power4 server with AIX version 5.3 installed. Upon boot up, it hangs right after the AIX welcome screen. On the diagnostic load progress LED indicator, I saw that it stopped at '0c32' then after awhile the LED would be blank. The screen on the monitor will hang at the black... (15 Replies)
Discussion started by: a_sim
15 Replies
8. Solaris
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)
Discussion started by: hemalsid
9 Replies
9. Solaris
Got a strange problem.
I have 4 Solaris servers all configured the same, Solaris 10 x86 update 10.
When I try to ssh from one Solaris 10 server to another server ssh hangs.
I have an identical server and when I try this everything works fine.
The weird thing is if I am root on the server... (1 Reply)
Discussion started by: ccj4467
1 Replies
10. Solaris
Hi Guys,
I have a SunBlade 1500 which I use to practice at home. Suddenly when I power on the server it just displays the solaris banner and Boot device: disk File and args: Then it stops and says " rebooting with command: boot"
It doesn't boot to the kernel. Is there anyway I can possibly... (5 Replies)
Discussion started by: cjashu
5 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)