|
|
Sponsored Content
Operating Systems
Solaris
Failure to boot v445
Post 302612285 by gull04 on Sunday 25th of March 2012 02:15:00 PM
03-25-2012
|
|
9 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hello.
System is a HP Visualize C3600 running X11 and after a power failure machine will not boot (see error messages below)
From what I've read, this may be caused by a corrupted etc/inittab file. Solution suggested on other websites is to boot in single user mode and edit file inittab... (2 Replies)
Discussion started by: westcoast
2 Replies
2. Linux
Hi all
I used a dual boot operating system and it works fine for me. Now , i install a Ati radeon 9250 Agp card on my system and this results in boot failure of fedora 6. The graphics card is working fine with windows XP , i.e i have no compatibility issues.The system also refuses to boot when i... (2 Replies)
Discussion started by: joshighanshyam
2 Replies
3. Solaris
I installed solaris virtually and tried to format the partitions .. I dont know what went wrong, It got rebooted and hangs in the screen "No partitions" and after pressing Enter button it goes to "INT18 boot failure" and hangs there once again . Could any one of you suggest why this has happened... (3 Replies)
Discussion started by: priky
3 Replies
4. Solaris
I have installed Solaris 10 OS in Sun Virtual Box that uses x86 32 bit system. After an abnormal shutdown i'm getting the following message on the console when i try to boot.
SunOS Release 5.10 Version Generic_127128_11 32-bit
Copyright 1983-200 Sun Microsystems, Inc. All rights reserrved.
Use... (3 Replies)
Discussion started by: Sesha
3 Replies
5. SCO
hi
SCO Unix 5.0.6 doesn't boot due to this problem:
not a directory
boot not found
cannot open
stage 1 boot failure: error loading hd (40)/boot
Knows someone howto solve it? (16 Replies)
Discussion started by: ccc
16 Replies
6. Solaris
This is what is displayed on the screen as the system tries to boot and then hangs:
0>Test CPU(s)....Done
0>Interrupt Crosscall....|
SC Alert: DHCP negotiation failed, perhaps misconfigured or no DHCP server avail
able
Done
0>Init Memory....|
SC Alert: Host System has Reset
'Done
0>PLL... (2 Replies)
Discussion started by: kenosongo
2 Replies
7. UNIX for Dummies Questions & Answers
hi power went out. next day unix sco wont boot up error code 303. any help appreciated as we are clueless. (11 Replies)
Discussion started by: fredthayer
11 Replies
8. Solaris
Hi,
i am running an old Opensolaris 5.11 snv_111b on an x86 server. After almost 4 years of successful service, last night out of the blue started to refuse all connections to it's services, ssh, http,etc. The only visible solution at that time was a restart. But now instead of booting the... (2 Replies)
Discussion started by: d_oilen
2 Replies
9. HP-UX
When I login to the live console of my server and go to the console, I am getting the below message
Processor is booting from the first available device.
To discontinue, press any key within 10 seconds.
10 seconds expired.
Proceeding...
Trying Primary Boot Path... (11 Replies)
Discussion started by: chacko193
11 Replies
LEARN ABOUT HPUX
vxbootsetup
vxbootsetup(1M) vxbootsetup(1M) NAME
vxbootsetup - set up system boot information on a Veritas Volume Manager disk SYNOPSIS
/etc/vx/bin/vxbootsetup [-g diskgroup] [medianame ... ] DESCRIPTION
The vxbootsetup utility configures physical disks so that they can be used to boot the system. Before vxbootsetup is called to configure a disk, the required volumes, standvol, rootvol and swapvol (and optionally, dumpvol) must be created on the disk. All of these volumes must be contiguous with only one subdisk. The -g option may be used to specify the boot disk group. If no medianame arguments are specified, all disks that contain usable mirrors of the root, swap, /usr and /var volumes are configured to be bootable. If medianame arguments are given, only the disks that are associated with the specified disk names are configured to be bootable. vxbootsetup requires that: o The root volume must be named rootvol and must have a usage type of root. o The swap volume must be named swapvol and must have a usage type of swap. o The volumes containing /usr and /var (if any) must be named usr and var, respectively. See the chapter "Recovery from Boot Disk Failure" in the Veritas Volume Manager Troubleshooting Guide for detailed information on how the system boots and how VxVM impacts the system boot process. The vxmirror, vxrootmir, and vxresize utilities call vxbootsetup automatically. If you use vxassist, or vxmake and vxplex to create mirrors of the root volume on a disk, you must run vxbootsetup explicitly to make the disk bootable. ARGUMENTS
medianame Specifies the disk name (disk media name) of a VM disk that is to be configured as bootable. SEE ALSO
disksetup(1M), edvtoc(1M), vxassist(1M), vxevac(1M), vxinstall(1M), vxintro(1M), vxmake(1M), vxmirror(1M), vxplex(1M), vxresize(1M), vxrootmir(1M) Veritas Volume Manager Troubleshooting Guide VxVM 5.0.31.1 24 Mar 2008 vxbootsetup(1M)