Sponsored Content
Full Discussion: HPUX Boot failure.
Operating Systems HP-UX HPUX Boot failure. Post 302877232 by vbe on Friday 29th of November 2013 08:20:19 AM
Old 11-29-2013
Well since I dont know what MP uses for memory, one thing I know ( for I had to at a time...) is there is an order in which memory has to be implanted, my idea is that with half the memory it can work if you know the order memory has to be in slots: you remove the bad ones and set what is left as if you had only half, it will then recognize the memory correctly then on ( cross your fingers...)
your issue is as if it removed the bad memory but then what is left isnt installed in the right slots...
 

9 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

HP-UX respawning boot failure

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

Boot failure

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

INT18 boot failure

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

Boot failure

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

stage 1 boot failure: error loading hd (40)/boot

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. Debian

clusterKnoppix Live Cd boot failure

I'm trying to run clusterKnoppix live cd from a couple machines but it only works from one computer. The other three, my toshiba laptop, emachine, and hp machine can't find the filesystem.. the live cd stops booting and gives me a error saying it couldn't find knoppix filesystem and then gives me a... (0 Replies)
Discussion started by: iamhe
0 Replies

7. HP-UX

fail to boot HPUX

HPUX running in D-Class (L1000), pretty old HPUX version - hpux 11.00 Attempt 1 -- To boot from normal (primary) Unable to boot - system complains failure SYSTEM ALERT System Name : uninitialized DATE : 10/22/2011 Time : 03/41:12 Alert Level 15 = Fatal hardware or configuration... (12 Replies)
Discussion started by: ckwan
12 Replies

8. Solaris

Failure to boot v445

Hi Guys, I have a small problem with a v445 which I have been informed will only boot with the reconfigure option enabled. It is attached to HP SAN storage using qla2300 FCA's with a Veritas encapsulated rootvoldg (No Laughing here please) when I try a reboot I get the following error. ... (5 Replies)
Discussion started by: gull04
5 Replies

9. UNIX for Dummies Questions & Answers

boot up failure unix sco after power failure

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
isl(1M) 																   isl(1M)

NAME
isl - initial system loader DESCRIPTION
implements the operating system independent portion of the bootstrap process. It is loaded and executed after self-test and initialization have completed successfully. The processor contains special purpose memory for maintaining critical configuration related parameters (e.g. Primary Boot, Alternate Boot, and Console Paths). Two forms of memory are supported: Stable Storage and Non-Volatile Memory (NVM). Typically, when control is transferred to an sequence takes place. An sequence allows a complete bootstrap operation to occur with no intervention from an operator. executes commands from the file in a script-like fashion. is enabled by a flag in Stable Storage. is a mechanism that automatically locates the boot and console devices. For further information, see pdc(1M). During an sequence, displays its revision and the name of any utility it executes. However, if is disabled, after displays its revision, it then prompts for input from the console device. Acceptable input is any command name or the name of any utility available on the sys- tem. If a non-fatal error occurs or the executed utility returns, again prompts for input. Commands There are several commands available in although not all commads are supported on cellular systems . The following is a list with a short description. Parameters may be entered on the command line following the command name. They must be separated by spaces. prompts for any necessary parameters that are not entered on the command line. Help - List commands and available utilities List available utilities Enable or disable the autoboot sequence Parameter - or Enable or disable the sequence Parameter - or Modify the Primary Boot Path Parameter - Primary Boot Path in decimal Modify the Alternate Boot Path Parameter - Alternate Boot Path in decimal Modify the Console Path Parameter - Console Path in decimal List contents of the file Display the Primary Boot, Alternate Boot, and Console Paths Display the contents of one word of NVM in hexadecimal Parameter - NVM address in decimal or standard hexadecimal notation Display the contents of one word of Stable Storage in hexadecimal Parameter - Stable Storage address in decimal or standard hexadecimal notation DIAGNOSTICS
displays diagnostic information through error messages written on the console and display codes on the LED display. For the display codes, are informative only. and indicate errors, some of which are fatal and cause the system to halt. Other errors merely cause to display a message. Non-fatal errors during an sequence cause the sequence to be aborted and to prompt for input. After non-fatal errors during an interactive session, merely prompts for input. Fatal errors cause the system to halt. The problem must be corrected and the system RESET to recover. is executing. is from the file. Cannot find an file. aborted. No console found, can only Directory of utilities is too big, reads only 2K bytes. file is inconsistent. aborted. Utility file header inconsistent: SOM values invalid. file input string exceeds 2048 characters. aborted. command or utility name exceeds 10 characters. has transferred control to the utility. Internal inconsistency: Volume label - Internal inconsistency: Directory - Error reading file. Error reading from console - Error writing to console - Not an command or utility. Utility file header inconsistent: Invalid System ID. Error reading utility file header. Utility file header inconsistent: Bad magic number. Utility would overlay in memory. Utility requires more memory than is configured. Error reading utility into memory. Incorrect checksum: Reading utility into memory. Console needed - Internal inconsistency: Boot device class - Destination memory address of utility is invalid. Utility file header inconsistent: pdc_cache entry. Internal inconsistency: iodc_entry_init - Internal inconsistency: iodc_entry_init - console - Internal inconsistency: iodc_entry_init - boot device - Utility file header inconsistent: Bad aux_id. Bad utility file type. SEE ALSO
boot(1M), pdc(1M). PA-RISC Systems Only isl(1M)
All times are GMT -4. The time now is 07:10 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy