Sponsored Content
Full Discussion: hp-ux 10.20 boot issue
Operating Systems HP-UX hp-ux 10.20 boot issue Post 302196000 by davel1000 on Friday 16th of May 2008 11:38:10 AM
Old 05-16-2008
Hello and thank you.

When I type "bo p3" system returns:

ERROR: Not a boot path

When I type "bo fwscsi.6.0" system returns:

IPL error: bad LIF magic: not a valid LIF volume

When I type "sea p3" system returns:

ERROR: Unknown device

When I type "sea fwscsi.6.0" system returns:

Path Number Device Path Device Type
P0 FWSCSI.6.0 HP 36.4GMAN3367MC

Thanks in advance.

Quote:
Originally Posted by vbe
And what does bo p3 give you now?
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

boot up issue

Could somone please tell me what happened when I reboot my computer, it take too long to pass the part it said "starting sendmail" I only changed the server name and when I reboot the server, all of the services are running except when it got to : starting sendmail it take toooo long to... (1 Reply)
Discussion started by: lapnguyen
1 Replies

2. UNIX for Advanced & Expert Users

Dual boot issue

Hi All, 1st HDD is loaded with Windows 2000 Professional and I have installed Red Hat ES 3.0 on second HDD(80GB). After linux installation failed to load windows and boot stucks with displaying only L How to fix this issue Thanks in advance for your valuable answer. Regards, Bachegowda (1 Reply)
Discussion started by: bache_gowda
1 Replies

3. HP-UX

PXE boot port issue

Hi,all: I want to boot an IA unix box from network, I am sure I set the DHCP and boot server, but it still failed ! It says : Client MAC Address: 00 18 FE 28 91 82 .....- PXE-E16: Valid PXE offer not received. Load of Core LAN Gb A failed: Not Found I use the nettl command to trace the UDP... (0 Replies)
Discussion started by: bluepluto
0 Replies

4. Solaris

boot-archive issue

I had logged into Server via ALOM and was placed into runlevel 5 other than 3 which is default. I did a svcadm delete boot-archive, and was promptly placed in runlevel 3. Now, I am unable to do a telnet or login into the server through any other service. bash-3.00# svcs -a svcs -a STATE ... (3 Replies)
Discussion started by: praveenr
3 Replies

5. Solaris

Solaris-RHEL5 Dual boot issue

Machine: x86 OS : Dualboot Solaris and RHEL5 -Solaris 10 in first fdisk partition. RHEL5 - /boot in partition2 / in partition3 swap in 1st... (1 Reply)
Discussion started by: saagar
1 Replies

6. Red Hat

Dual boot issue .....

Hi, I have a laptop with two os running in it, Windows XP & RHEL5. Accidentally, we have deleted the windows entry in grub.conf file. Later we connected the hard disk of laptop to another system & deleted the linux partitions from the disk management tool of windows. Now the issue is, the... (7 Replies)
Discussion started by: Amol21
7 Replies

7. Solaris

Boot parameter issue

Hi all i have an issue when i change auto-boot?=false and reboot it again it is going to auto-boot?=true can any one tell that what should i do for auto-boot?=false for permanently thank you in advance (11 Replies)
Discussion started by: wkbn86
11 Replies

8. Solaris

Persistent boot disks issue

Hi all, please i need your help urgently I am faced to a serious boot disks issue on an Sun Fire E2900. The system run with two disque in zpool . The operating system is Solaris 10 (ZFS) The first time the issue occured, i got the error below on the two disks: Apr 7 08:04:33... (0 Replies)
Discussion started by: saki_jumeau
0 Replies

9. Solaris

V100 boot issue

In the server room at my new job, there is a V100 with a problem. When power is turned on, the machine goes to the lom prompt. Entering poweron yields an endless supply of this message with no way to break out of it. ********************************************** PSTATE=0000000000000015... (3 Replies)
Discussion started by: chilinski
3 Replies

10. SCO

Issue during boot

Hi, I am using SCO OpenServer 5 During boot I get this message: PANIC: HTFS: Bad directory ino 2 (offset 0) on HTFS dev hd (1/42) Cannot dump 8095 pages to dumpdev hd (1/41): Space for only 0 pages Dump not completed How can I fix this? I have no boot/root floppy. If it is a "disk... (8 Replies)
Discussion started by: nubian_sundance
8 Replies
set_parms(1M)															     set_parms(1M)

NAME
set_parms - set system initial identity parameters: hostname, date/time, root password, and networking SYNOPSIS
DESCRIPTION
The command is an interactive system set-up command that allows you to specify various "initial identity parameters" when first booting a newly installed operating system (whether preinstalled, or installed locally from media or an install server), and to revise these parame- ters later on a running system. Initial identity parameters are a minimal set of values required to bring a system to an initially useful state. They include the following: o system hostname o timezone for the system's location o date and time o root password o IP address, netmask o routemask, routing gateway, DNS, and NIS information o local language In a first-boot situation, is invoked automatically by For purposes, "first-boot" is defined as having no hostname set when the system starts up. This causes to step through all of its sub-areas to help you set all of the initial identity parameters. After the system has booted and is running, may also be called directly from the command line to step through all areas (via similar to how it works at first-boot, or to finish setting up a particular sub-area (the latter forms above). There are certain limitations to its actions when it's run after first-boot, as described see below. Note: The command only sets the root (superuser) password during "initial" processing, and then only if it is not already set. If so, it uses the command, so the effect is immediate. See the passwd(1) manpage. The command is also DHCP-aware. If you attempt to change DHCP-supplied data such as the hostname or IP address, issues a warning. If you continue with the changes, relinquishes the DHCP lease. On first-boot, asks if you would like to try getting set-up data from a DHCP server. However invoked, the command often knows and provides default values for many of the initial identity parameters, based on values specified to Ignite-UX in a previous or recent installation of the system or found in system configuration files. The command can be run only by the user with appropriate privilege. Options Each sub-area of is described below. In a first-boot situation all of the sub-areas are run sequentially. Special first-boot behavior is noted below if applicable, along with any special cases when invoking on a running system. When calling a sub-area directly, only a unique portion of the sub-area name is required to be given; for example, This allows the user to sequentially invoke all the sub-areas mentioned below. The user can configure multiple interfaces which are physically connected to the network using the Termi- nal User Interface (TUI). A in the user interface field indicates a lan which is not physically connected to the network. If lan interfaces are configured as DHCP, the options and are skipped. Set the system hostname: Validates a user-supplied hostname according to host-naming conventions and sets various system initialization variables to operate with that hostname. Particularly, edits to associate the new hostname with the current IP address of the system, if that can be determined. Note: It does not notify DNS (Domain Name Servers), etc. This higher level of configuration is handled later by broader configuration tools. WARNING: When changing the hostname, does not know about optionally-installed software. If any such software remembers the previous hostname, it might not work properly after the hostname is changed. A mechanism is provided that helps generalize the hostname changing function. The command calls, in sorted order, any exe- cutable commands found in the directory This occurs for both first-boot and non-first-boot calls. HP may in the future sup- ply special commands in this location. The system administrator may also supply custom commands (programs or scripts) for site installations using, for example, Ignite-UX. The system must be rebooted for any change to take full effect. Select a timezone based on your country of location. Also allows you to set a user-supplied timezone. The system must be rebooted for any change to take effect. Set the system date and time interactively: This is similar to calling as a privileged user, but without having to format a time specification string. The change takes effect immediately. Set or change the IP address and subnet mask for the system. This function edits the file to associate the new IP address with the current hostname. Note: it does not notify DNS (Domain Name Servers), etc. This higher level of configuration is handled later by broader configuration tools. If multiple lan interfaces are present, the user can select each LAN interface (network interface card or NIC) separately to configure it. The system must be rebooted for any change to take effect. Set the route mask (which defines the network and local subnet portions of a network address), set the routing gateway, and define access to the Domain Name System (DNS) and Network Information Service (NIS). First-boot: These changes take effect immediately, without a reboot, because starts networking after setting the parameters. Non-first-boot: A reboot is required for all of these changes to take effect. Allow the user to set the local language settings. The user can either select one of the languages from the menu or they can set new valid language. will verify whether the new language is installed. If it is not installed, the user must install the language before executing this option. set_parms, Ignite-UX or Cold Install After "cold-installing" HP-UX from tape, CD-ROM, or DVD, or using Ignite-UX to install HP-UX from any source including an install server, the file is generally left on the system. This file is used to communicate to and other tools the hostname, networking, and other informa- tion that was used during the installation, to make it easier to use any of these values as final system parameters. In particular, uses as defaults the shell-style variables in this file that begin with For example, indicates which LAN interface was used during a network cold install. This is the LAN interface that configures. In general, first looks in for default information, then in the system configuration files in the directory. If any parameter is defined in both locations, the latter takes precedence. If Ignite-UX is installed on your system, see the manpage entries for ignite(5) and instl_adm(4). In particular, read instl_adm(4) for descriptions of the and variables. Interaction with auto_parms During the boot-up sequence, always invokes which in turn detects the first-boot situation and it calls if either or both of these condi- tions are true. The starts its interface and, based on user input, might call back into to obtain and set up the management of a DHCP lease. After completes this and other system set-up tasks, control passes back to which completes the boot-up sequence using the newly- created system initial identity parameters. See the rc(1M) manpage for information about for invocation context in the first-boot case. If the system has multiple lan interfaces and the user wishes to configure some with DHCP and others with static IP, the user must invoke first to configure all the lan interfaces which they wish to configure as DHCP. The user should not allow the system to be rebooted while doing this configuration. Then the user should invoke to configure the remaining lan interfaces. also allows the user to specify the DHCP server from which to get hostname and networking parameters and Class ID. If multiple interfaces are configured with DHCP, there is a chance that multiple hostnames will be returned through different DHCP enabled lan interfaces. If hostname is not set in and none of the interfaces are configured with addresses, then the hostname returned by the interface is updated in FILES
The command itself. Common subroutines used by and the sub-area commands. Directory holding all of sub-area commands called by which runs them in sorted order. Directory containing any hostname-change commands defined by the user. These are standalone commands run, in sorted order, by when setting or changing the hostname. File set by Ignite-UX or Cold Install that contains networking and other system information used during the installation. System configuration files modified by AUTHOR The command was developed by HP. SEE ALSO
passwd(1), auto_parms(1M), dhcpdb2conf(1M), rc(1M), instl_adm(4), ignite(5). set_parms(1M)
All times are GMT -4. The time now is 08:32 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy