Sponsored Content
Full Discussion: Booting problem Veritas
Operating Systems Solaris Booting problem Veritas Post 85142 by pressy on Sunday 2nd of October 2005 06:31:18 PM
Old 10-02-2005
have you set the opb variable "boot-device" to your disks?
in obp: setenv boot-device disk0 disk1
in OS: eeprom boot-device=disk0\ disk1
(if disk1 is your second)
you can use any name for the disks, have a look to devalias and nvalias in your obp manual

gP
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Problem with booting

Hi! I installed Slackware on my computer so I thought I could have dual booting with ME, but that didn't work. So I installed another bootmanager that I find on internet. When I startup my computer the second bootmangaer that I did find on internet lets me choose system. When I have choosen... (3 Replies)
Discussion started by: Mr.Rudiment
3 Replies

2. UNIX for Advanced & Expert Users

Booting Problem

Hai I have installed win 98 o.s in my system after that i have installed Red Hat Linux 7.0,there is a problem in dual booting,by default win98 is being booted, when i insert bootable linux floppy linux is loaded My doubt how to overwrite windows MBR and palce the lilo in MBR.so that it... (2 Replies)
Discussion started by: rajashekaran
2 Replies

3. UNIX for Dummies Questions & Answers

<< booting problem with redhat 8.0 >>

i have the Redhat installed in this Hard Drive and i wanna use it in this old computer of mine.. it works fine in my new computer.. but when i put it in my old one.. which is.. P1 150MHz 32MBramz it wont load the kernal and keeps on restarting the computer.. keeps on goin like this.. i get the GRUB... (2 Replies)
Discussion started by: dezithug
2 Replies

4. Solaris

booting problem

any one can help me. my system running on solaris 2.7. recently there is sudden power failure while system running. after that unable to boot the system. it is giving comment that "can not open /etc/path_to_inst" and then returning back to "OK" after comment of termination. The processor is... (10 Replies)
Discussion started by: prabir
10 Replies

5. UNIX for Dummies Questions & Answers

problem booting

Dear List, While I was adding second hard disk to my system, I changed the /etc/fstab file by adding the following line: /mnt/sdb1 /dev/sdb1 ext3 default 2 1 Now system does not boot and gives the following error: Checking filesystems /: Clean, 309260/18495840 files, 1064776/18486790... (2 Replies)
Discussion started by: siavoush
2 Replies

6. Solaris

Veritas Multipathing problem.

Hi, Basically the original configuration on my Solaris 9 server was two LUNs configured as Veritas file systems that were connected to a NetApp filer (filer1). These two LUNs are still configured on the server - but are not being used. They are there as a backup just in case the new... (0 Replies)
Discussion started by: sparcman
0 Replies

7. Solaris

problem in volume resizing in veritas

Hi all i have a veritas volume with the size of 600MB and formatted with vxfs filesystem. I want to grow the filesystem to 700MB. I knew that three ways are there to resize. vxresize, vxvol and vxassit. vxresize works fine. I want to try the same thing with vxvol and vxassist. Can someone tell me... (4 Replies)
Discussion started by: kingston
4 Replies

8. AIX

AIX Booting problem

Hi, I have IBM RS/6000 44P MODEL 170 server with Aix 5.1 Till the morning server is working fine, i turned off properly but now i tried to start it is showing below error on LED and going down (power off) E051 >>>E0E0 >>>> E0E1>>>> 种种种种 >>>> 40210014 P1-C1-F1 ccccccc >>>> 40210014 >>>>E043... (3 Replies)
Discussion started by: ANAND KURADE
3 Replies

9. AIX

Booting problem

Dears, I have a problem when i reboot the machine last time "AIX 5.3", that after rebooting it not login to graphical desktop, it just stop at console login command line. Kindly find the attached screenshot. Anyway to let it login automatically to Desktop? Would appreciate any pointers to... (1 Reply)
Discussion started by: moudmm
1 Replies

10. AIX

Problem to booting up p730

Hi Everyone, We have IBM p730 that I am trying to booting up to AIX 7.1. But it stops at RUNTIME. C7004087 C7004091 C7004091 (show is code number twice) STANDBY RUNTIME The explanation for C7004091 is the final IPL status progress code to be displayed before the system reaches... (5 Replies)
Discussion started by: lilyn
5 Replies
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)
All times are GMT -4. The time now is 06:46 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy