Sponsored Content
Full Discussion: boot failure-init died
Operating Systems HP-UX boot failure-init died Post 302169504 by mrviking on Thursday 21st of February 2008 01:03:36 PM
Old 02-21-2008
during boot, choose to go to IPL.
choose hpux -iS
with interactive IPL help.

same problem.
HPUX10.20
hp9000/800 k class server.

trying to boot from ignite tape gives me ipl error: bad LIF magic.
tape seems to be readable (cleaned drive to be sure).

gonna try & find older ignite for booting as well...
any other suggestions?
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

WARNING - exit init (PID1) died.

Hi, Today, on one of my SCO machines, i was getting the following: PANIC : exit cannot exec /etc/init (PID1). I used two floppy boot/root disks to boot from floppy. I followed the procedures to restore the files: /usr/lib/libc.so.1 and /etc/init. When I reached the part of making... (6 Replies)
Discussion started by: BAM
6 Replies

2. HP-UX

What file contains boot up init details?

I want to get my telnetd to run on startup and was wondering where it was? im used to having it in /etc/init.d/rc.d but it is not the same in hp-ux :( thanks all (4 Replies)
Discussion started by: emplate
4 Replies

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

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. Boot Loaders

PXE boot not taking the init= option

Hi Experts, I am doing PXE boot for my GNU/Linux device and pxelinux.0 loads the kernel as well as initrd images I have mentioned in the config file but it looks like it is not considering the init= option. Instead it starts the default INIT program. I wanted my customized init program to be... (3 Replies)
Discussion started by: learn more
3 Replies

7. Solaris

Solaris 10 init 0 and boot disk1 on same command line

Hello all, Fairly simple question here. I know that in Solaris 10 there is a way to tell a system running solaris 10 to init 0 and then boot disk1 all in the same command line from a SSH window. That way once you hit enter it then performs the init 0 and then does the boot disk1. ... (2 Replies)
Discussion started by: tording99z28
2 Replies

8. AIX

what user executes init on boot?

I have a command in init that trys to start a daemon and open a log, but a get an error error that the file access permissions do not allow the specified action. My permissions on the log file are: -rw-r--r-- 1 root system 4434 Mar 22 15:13 dsmerror.log The logfile is written to... (2 Replies)
Discussion started by: pong3d
2 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

10. Solaris

Solaris 10 boot failed init

Dear all, I have a solaris 10 in my environment (VMware virtual machine). recently I increased the harddisk size from the VMware and reboot my server. after reboot the os is unable to boot and gives the below error message. exec(/sbin/init) file not found press any key to restart ... (3 Replies)
Discussion started by: krishna001
3 Replies
IPL(4)							     Kernel Interfaces Manual							    IPL(4)

NAME
ipl - IP packet log device DESCRIPTION
The ipl pseudo device's purpose is to provide an easy way to gather packet headers of packets you wish to log. If a packet header is to be logged, the entire header is logged (including any IP options - TCP/UDP options are not included when it calculates header size) or not at all. The packet contents are also logged after the header. If the log reader is busy or otherwise unable to read log records, up to IPLLOGSIZE (8192 is the default) bytes of data are stored. Prepending every packet header logged is a structure containing information relevant to the packet following and why it was logged. The structure's format is as follows: /* * Log structure. Each packet header logged is prepended by one of these. * Following this in the log records read from the device will be an ipflog * structure which is then followed by any packet data. */ typedef struct iplog { u_long ipl_sec; u_long ipl_usec; u_int ipl_len; u_int ipl_count; size_t ipl_dsize; struct iplog *ipl_next; } iplog_t; typedef struct ipflog { #if (defined(NetBSD) && (NetBSD <= 1991011) && (NetBSD >= 199603)) u_char fl_ifname[IFNAMSIZ]; #else u_int fl_unit; u_char fl_ifname[4]; #endif u_char fl_plen; /* extra data after hlen */ u_char fl_hlen; /* length of IP headers saved */ u_short fl_rule; /* assume never more than 64k rules, total */ u_32_t fl_flags; } ipflog_t; When reading from the ipl device, it is necessary to call read(2) with a buffer big enough to hold at least 1 complete log record - reading of partial log records is not supported. If the packet contents are more than 128 bytes when log body is used, then only 128 bytes of the packet contents are logged. Although it is only possible to read from the ipl device, opening it for writing is required when using an ioctl which changes any kernel data. The ioctls which are loaded with this device can be found under ipf(4). The ioctls which are for use with logging and don't affect the filter are: ioctl(fd, SIOCIPFFB, int *) ioctl(fd, FIONREAD, int *) The SIOCIPFFB ioctl flushes the log buffer and returns the number of bytes flushed. FIONREAD returns the number of bytes currently used for storing log data. If IPFILTER_LOG is not defined when compiling, SIOCIPFFB is not available and FIONREAD will return but not do any- thing. There is currently no support for non-blocking IO with this device, meaning all read operations should be considered blocking in nature (if there is no data to read, it will sleep until some is made available). SEE ALSO
ipf(4) BUGS
Packet headers are dropped when the internal buffer (static size) fills. FILES
/dev/ipl IPL(4)
All times are GMT -4. The time now is 01:22 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy