03-30-2018
Can you put the disk back in the original system, and boot, then look at the last 60 lines of /usr/adm/messages. This file contains the same information as displayed on the screen in the boot process.
You should then be able to tell which piece of hardware is causing the problem.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hi guys,
May I know how to install Solaris 8 in the way that I can triple boot it with my the other two OS: WIndows ME and Windows 2000 Pro.
Can you all please kindly advise me on how to setup the triple boot process inorder to allow Windows ME to be the default OS when being ask to choose... (1 Reply)
Discussion started by: cia
1 Replies
2. Linux
I have a RH 7.3 server that needs a restart today after putting a patch in place. The last time I rebooted this box was almost a year ago and when the uptime is quite long, Linux likes to check all the disks for errors, including the RAID. This adds almost 1.5Hrs to my bootup process:eek: .
Does... (1 Reply)
Discussion started by: turbo90awd
1 Replies
3. UNIX for Advanced & Expert Users
Hello there
I need to run a script whenever i reboot or startup my HP-UX server. This script adds some routes to the route table, and it start third party aplications like "Star Manager".
I thought i could do this simply putting the script in "/sbin/init.d,
and a link to the script in... (7 Replies)
Discussion started by: vascobrito
7 Replies
4. UNIX for Dummies Questions & Answers
Hi all
The following error was displayed when a sco server (5.0.5) was booted. What should be done to overcome the problem. Replies appreciated.
Bios 03.0
0130688 KB memory good
01 processor(s) in system
remote console dialing on, please wait
connect fail : modem off
cpu clock... (6 Replies)
Discussion started by: raguramtgr
6 Replies
5. UNIX for Dummies Questions & Answers
Evry time I start up my mavhine ,have to type in unix at
Boot
:
Is there a way unix should bootup automatically?
Asif (2 Replies)
Discussion started by: asif iqbal
2 Replies
6. AIX
Hi i installed ssh of version v 1.21 and my AIX is of 5.3.
I want to start my ssh deamon at the startup
can any one please help me out reg..
Thanks in advance.. (1 Reply)
Discussion started by: kmalla
1 Replies
7. AIX
Hi,
I've got a recent problem with 2 file systems on an AIX 5.3 server. The fs's are marked to auto mount at startup and do show as being mounted after a a restart however if you cd to the mount point and 'df -g .' it shows the fs hasn't actually mounted.
$ mount |grep SQLT0001.0
... (2 Replies)
Discussion started by: m223464
2 Replies
8. UNIX for Advanced & Expert Users
Hi,
I am using a Linux system running at run level 3. I am finding a wired problem, once the system boots, the system terminal slows down, I need to type the characters repeatedly to enter my login and password info. Also running any commands takes time, it stays in this condition for some... (1 Reply)
Discussion started by: cjjoy
1 Replies
9. UNIX for Dummies Questions & Answers
What is the boot up sequence in UNIX? (2 Replies)
Discussion started by: karthi_g
2 Replies
10. Solaris
Hi Folks,
Has anyone seen these errors on bootup.
Mar 15 12:22:30 svc.startd: svc:/system/device/local:default: Method "/lib/svc/method/devices-local" failed due to signal SEGV.ht (c) 1983, 2010,
Oracle and/or its affiliates. All rights reserved.
Configuring devices. ... (1 Reply)
Discussion started by: ESSTEAM
1 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)